On Fri, Sep 23, 2011 at 03:39:03PM -0500, Larry Finger wrote:

A bug was sent to me concerning a scheduling-while-atomic-BUG. This
happened shortly after KDE suspended an eeepc1015PE netbook during
system update over WLAN. Suspend&resume normally worked allright.
The OP is Berhard Wiedemann in the Cc list. Inquiries for more info
go to him.

It looks like we forgot to unlock spinlock somewhere or we do not
use _irqsave version of spinlock where needed, but provided calltrace
is not naught to find the bug.

I suggest compile kernel with CONFIG_LOCKDEP, try to reproduce and see
if we do get some more messages.

Stanislaw