On 12/21/2011 06:06 AM, Darshan Kumar NANDANWAR wrote:
> Larry ,
>
> I am using RTL8192CE driver for 2.6.32.16 for one of the DTV soc(sh4 cpu) ..
> Once I insert it , I get following oops... The same oops is reported by *John
> Linville in https://bugzilla.kernel.org/show_bug.cgi?id=40212 . But
> unfortunately , given link is down ; so I am unable to get into the the
> discussion. Could you please give me the pointers why it?s happening so?*
>
> Lspci is showing me correct vendor and product id which is : *0x10ec 0x8178*
I added the linux-wireless ML to the Cc list so that others will see this thread.
I do not remember the kernel bugzilla. Perhaps John does.
Are you using a recent version of compat-wireless? If not, please do.
I do not know anything about the sh4, but I will try to help.
The only rtl8192ce routine mentioned in the traceback is rtl92ce_module_init. I
see no indication that it got as far as the .probe routine, which is
rtl_pci_probe() in drivers/net/wireless/rtlwifi/pci.c. It might be useful to put
a printk() at the beginning of that routine to see if it is being reached. I
would also suggest that you modprobe the various components separately. First
rtlwifi, then rtl8192c_common, and finally rtl8192ce.
Is the sh4 little- or big-endian? Not all the code has been tested on a BE machine.
Larry
On Wed, Dec 21, 2011 at 08:54:39AM -0600, Larry Finger wrote:
> On 12/21/2011 06:06 AM, Darshan Kumar NANDANWAR wrote:
> >Larry ,
> >
> >I am using RTL8192CE driver for 2.6.32.16 for one of the DTV soc(sh4 cpu) ..
> >Once I insert it , I get following oops... The same oops is reported by *John
> >Linville in https://bugzilla.kernel.org/show_bug.cgi?id=40212 . But
> >unfortunately , given link is down ; so I am unable to get into the the
> >discussion. Could you please give me the pointers why it’s happening so?*
> >
> >Lspci is showing me correct vendor and product id which is : *0x10ec 0x8178*
>
> I added the linux-wireless ML to the Cc list so that others will see this thread.
>
> I do not remember the kernel bugzilla. Perhaps John does.
No, sorry -- I have no idea what that bug was. I don't even think
I have the device in question, so I don't know how I could even have
produced a bug report!
John
--
John W. Linville Someday the world will need a hero, and you
[email protected] might be all we have. Be ready.
On 12/21/2011 09:16 AM, John W. Linville wrote:
> No, sorry -- I have no idea what that bug was. I don't even think
> I have the device in question, so I don't know how I could even have
> produced a bug report!
I found a reference at https://lkml.org/lkml/2011/7/28/42. The bug at b.k.o was
just for tracking.
The fix came with commit b6b67df3f24c45af0012ee, which is dated Jul 29.
This bug is likely not the one causing your problem as the fix should be in
whatever version you are running. In addition, the oops traceback in that
instance came back to _rtl_pci_find_adapter(). Yours fails in rtl_pci_probe().
Any chance of telling me what statement is at rtl_pci_probe+0x652/0x1660? The
source file is drivers/net/wireless/rtlwifi/pci.c.
Larry