From: Larry Finger <Larry.Finger@lwfinger.net>
To: Darshan Kumar NANDANWAR <Darshan.KN@st.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: insmod RTL8192CE OOPS on 2.6.32.16
Date: Wed, 21 Dec 2011 08:54:39 -0600 [thread overview]
Message-ID: <4EF1F32F.8070704@lwfinger.net> (raw)
In-Reply-To: <D6068D304DED1F4FBFC1F56ECFA211D85A1EA7BBF0@EAPEX1MAIL1.st.com>
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
next parent reply other threads:[~2011-12-21 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D6068D304DED1F4FBFC1F56ECFA211D85A1EA7BBF0@EAPEX1MAIL1.st.com>
2011-12-21 14:54 ` Larry Finger [this message]
2011-12-21 15:16 ` insmod RTL8192CE OOPS on 2.6.32.16 John W. Linville
2011-12-21 19:38 ` Larry Finger
[not found] ` <D6068D304DED1F4FBFC1F56ECFA211D85A1EA7BE7A@EAPEX1MAIL1.st.com>
2011-12-22 16:06 ` Larry Finger
2011-12-23 9:02 ` Darshan Kumar NANDANWAR
2011-12-23 16:22 ` Larry Finger
[not found] ` <CAHeY5QcXDdi73nGC5F=-WWHzBzz1W7sj5har4L=_Ah_5xa0yBw@mail.gmail.com>
2011-12-23 20:15 ` Larry Finger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EF1F32F.8070704@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Darshan.KN@st.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.