From: Larry Finger <Larry.Finger@lwfinger.net>
To: Darshan Kumar NANDANWAR <Darshan.KN@st.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: insmod RTL8192CE OOPS on 2.6.32.16
Date: Wed, 21 Dec 2011 13:38:33 -0600 [thread overview]
Message-ID: <4EF235B9.3020805@lwfinger.net> (raw)
In-Reply-To: <20111221151605.GA11842@tuxdriver.com>
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
next prev parent reply other threads:[~2011-12-21 19:38 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 ` insmod RTL8192CE OOPS on 2.6.32.16 Larry Finger
2011-12-21 15:16 ` John W. Linville
2011-12-21 19:38 ` Larry Finger [this message]
[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=4EF235B9.3020805@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).