From: Larry Finger <Larry.Finger@lwfinger.net>
To: Richard Farina <sidhayn@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: rtl8187: kernel oops when leds enabled
Date: Mon, 26 Oct 2009 10:50:51 -0500 [thread overview]
Message-ID: <4AE5C55B.5070309@lwfinger.net> (raw)
In-Reply-To: <4AE5BD6C.2050303@gmail.com>
On 10/26/2009 10:17 AM, Richard Farina wrote:
> 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.
Your machine seems to be unique in that it happens most of the time.
It took more than 10 tries, but I finally got my copy of the
wireless-testing kernel to oops.
I will be working on a patch.
Larry
next prev parent reply other threads:[~2009-10-26 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 15:17 rtl8187: kernel oops when leds enabled Richard Farina
2009-10-26 15:50 ` Larry Finger [this message]
[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=4AE5C55B.5070309@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sidhayn@gmail.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).