From: Richard Farina <sidhayn@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: rtl8187: kernel oops when leds enabled
Date: Mon, 26 Oct 2009 11:17:00 -0400 [thread overview]
Message-ID: <4AE5BD6C.2050303@gmail.com> (raw)
Using kernel 2.6.31 and compat-wireless stable 2.6.32_rc5 I get this
kernel oops nearly 100% of the time when I unplug the device. I have
tried with the device down, up, and while transmitting, here are the
three oopses. Sorry it took me so long for this report, it is an odd
bug. When I was running older kernel/compat-wireless this oops was
about 4-5 screens longs so I couldn't take a picture. Additionally I
took the advice of a few of the list members to try the crashkernel
feature (which is AWESOME btw) but it doesn't work for this oops. Let
me be more specific, I can trigger an oops and the crash kernel kicks
in, but with this oops the crash kernel never kicks in so I am guessing
this is bad news.
I'm honestly a little surprised that no one has bothered to reproduce
this in the month since I reported it but maybe it is more unique to my
setup than it seems.
Hope these pictures are readable enough to be useful.
http://picpaste.com/pics/cimg1470.1256404028.jpg
http://picpaste.com/pics/cimg1474.1256404126.jpg
http://picpaste.com/pics/cimg1477.1256404170.jpg
I can fairly well generate this error at will and I'm available to test
reproducing the bug in any possible situation which is suggested and/or
test patches to fix.
Thanks,
Rick
next reply other threads:[~2009-10-26 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 15:17 Richard Farina [this message]
2009-10-26 15:50 ` rtl8187: kernel oops when leds enabled Larry Finger
[not found] ` <4AE5CDCB.8090400@gmail.com>
2009-10-26 18:27 ` Larry Finger
2009-11-03 23:22 ` Possible fix for " Larry Finger
2009-11-04 5:50 ` Richard Farina
2009-10-26 18:20 ` Hin-Tak Leung
2009-10-27 16:56 ` 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=4AE5BD6C.2050303@gmail.com \
--to=sidhayn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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).