linux-kernel - Re: kernel 3.2.1: BUG: scheduling while atomic: swapper/0/0/0x10000100

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Jan 2012 07:11:46 -0500
From:	Josh Boyer <jwboyer@...il.com>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	Francis Moreau <francis.moro@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"John W. Linville" <linville@...driver.com>
Subject: Re: kernel 3.2.1: BUG: scheduling while atomic: swapper/0/0/0x10000100

On Wed, Jan 25, 2012 at 5:00 AM, Arend van Spriel <arend@...adcom.com> wrote:
> On 01/25/2012 09:35 AM, Francis Moreau wrote:
>> Hi Arend,
>>
>> On Wed, Jan 25, 2012 at 9:17 AM, Arend van Spriel <arend@...adcom.com> wrote:
>>> On 01/24/2012 04:59 PM, Francis Moreau wrote:
>>>> Hi,
>>>>
>>>> Just in case someone is interested, I've been hit by this:
>>>>
>>>> [  236.734640] BUG: scheduling while atomic: swapper/0/0/0x10000100
>>>
>>> I hit that problem yesterday as well on 3.3.0-rc1. I suspected it came
>>> from my development changes on brcmfmac, but you are not using that.
>>
>> I'm not sure it's related to the brcmfmac, because the RFKILL switch
>> was off when it happened.
>>
>> Were you writting/reading from/to a SD card by any chances when it did trigger ?
>>
>
> Nope. It was a USB device driver. Maybe it was conincidental that it
> happened shortly after loading the driver, but I tend to mistrust my own
> stuff ;-). I posted a question in my issue yesterday (see [1]).

We've had a few similar issues reported in Fedora yesterday after we
rebased to 3.2.1.
I've not found a common trend yet, but there is definitely an issue on
some hardware in
3.2.1

josh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/