From: Larry Finger <Larry.Finger@lwfinger.net>
To: Shawn Nock <nock@nocko.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: rtlwifi: regression 39-rc5 (rtl8192ce)
Date: Mon, 02 May 2011 09:49:06 -0500 [thread overview]
Message-ID: <4DBEC462.2080805@lwfinger.net> (raw)
In-Reply-To: <m3d3k1b2me.fsf@nocko.org>
On 05/02/2011 09:26 AM, Shawn Nock wrote:
> Larry Finger<Larry.Finger@lwfinger.net> writes:
>
>> On 05/01/2011 12:59 PM, Shawn Nock wrote:
>>> During heavy network traffic (esp. flash video) I see the attached
>>> NULL pointer dereference in 2.6.39-rc5 on an IBM Thinkpad
>>> x120e. Immediately afterward a "scheduling while atomic" bug is
>>> reported and the system becomes unresponsive. I am unable to produce
>>> this problem in 2.6.38.4.
>>> See attached backtrace and dmesg. Please let me know what I can
>>> collect to make this problem easier to troubleshoot.
>>
>> Could you also supply the instruction byte sequence for the oops? It
>> is the "Code:" line of the dump.
>
> I had not been able to capture that, as the scheduler oops was triggered
> during the call stack dump (before the Code line).
>
>> I think you are using a 32-bit system. Is that correct?
>
> Correct.
>
>> Is there one URL that exposes this problem? If so, please sent that as
>> well.
>
> It had been speedtest.net (which *used* to crash this all the
> time). I've since re-configured the kernel to allow it to build faster
> (fedora .config trimmed to remove a lot of the unneeded modules). I can
> no longer trigger this BUG.
>
> I originally thought that this may be because I enabled the 8192CU
> driver, but clean kernel without it also doesn't trigger the bug. My new
> hypothesis is that building the kernel for the AMD processor type was a
> mistake (the only other significant change was that I went back to
> Pentium Pro as the CPU target).
>
> As far as I can tell this problem is resolved (20+ hours without issue,
> less than 20 min previously) and probably due to GCC not being aware of
> this (newish) AMD processor.
>
> Sorry for the false alarm and thanks,
No problem. Let me know if it resurfaces again.
Larry
next prev parent reply other threads:[~2011-05-02 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.edeGRjft5wqQRP07grcwfUVPlIA@ifi.uio.no>
[not found] ` <fa.0KaksBH9ogj3psmzYEvXzvHxClw@ifi.uio.no>
2011-05-02 14:26 ` rtlwifi: regression 39-rc5 (rtl8192ce) Shawn Nock
2011-05-02 14:49 ` Larry Finger [this message]
2011-05-01 17:59 Shawn Nock
2011-05-01 20:06 ` 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=4DBEC462.2080805@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nock@nocko.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