Rafael J. Wysocki wrote:
No, this isn't the WARN_ON().
this does have the feel of being scheduling related, but are you
absolutely sure about the precise identity of the patch?
Actually, not quite. That's why I have verified it and found that another
patch is really responsible for the issue, namely:
commit 82a1fcb90287052aabfa235e7ffc693ea003fe69
Author: Ingo Molnar <[EMAIL PROTECTED]>
Date: Fri Jan 25 21:08:02 2008 +0100
softlockup: automatically detect hung TASK_UNINTERRUPTIBLE tasks
Are you getting a bunch of prints from the softlockup detector in dmesg?
I wonder if the detector can detect a long timeout caused by suspend and
resume and if not is triggering false positives?
-- Steve
Reverting this commit (it reverts with some minor modifications) fixes the
problem for me.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
