-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 24.09.2011 18:30, schrieb Stanislaw Gruszka: > 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 Hi Stanislaw, the kernel config already has CONFIG_LOCKDEP_SUPPORT=y Is that what you meant? Does it need any extra to activate? meanwhile I had a similar bug on rc6 hours after resuming. This time it had some additional soft lockup messages ontop. see http://www.zq1.de/~bernhard/temp/dmesg.bug Ciao Bernhard M. Wiedemann -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5+JzgACgkQSTYLOx37oWQX1QCghshrnkuGt+CVmvVqlyeAD0wk HMUAoK1GvzR0tvBokCSdZv8elrA2SZCE =6u+w -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
