linux-kernel - Re: [3.2+] 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:	Thu, 26 Jan 2012 16:27:39 -0800 (PST)
From:	Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To:	balbi@...com
Cc:	Yves-Alexis Perez <corsac@...ian.org>, Greg KH <greg@...ah.com>,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [3.2+] BUG: scheduling while atomic: swapper/0/0/0x10000100


Hi All

> > > Specially when you consider the fact that
> > > it's very recently that we dropped the ARCH dependency with commit
> > > d242c110c43b55aaf3ebb3ceac1eeab0d452a177
> > > 
> > > > Kuninori, any thoughts about this?  Should I revert this from the
> > > > tree?
> > > 
> > > I don't think so, I think this was a bad bisection.
> > > 
> > Maybe (especially since the first bad commit is a merge commit, so I'm
> > not completely sure I did correctly the second bisect). But I'm puzzled
> > why reverting the commit on top of 3.2.1 fixes that. And now that Felipe
> > mentions it, USB Gadget is not even compiled, so I'm completely lost.
> 
> Hehehe :-) That's fun... Maybe it's some other instability and it just
> didn't kick when you reverted that commit. It could be that the problem
> is somewhere completely different and you just didn't fully debug it yet
> :-)

I was very much surprised at this issue.
As Felipe explained, renesas_usbhs was for SuperH system.
x86 can not use it,
but, if your PC has "renesas_usbhs.ko" as kernel module,
and loaded it somehow...

Best regards
---
Kuninori Morimoto
--
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/