On Sun, Feb 03, 2013 at 09:15:12PM +0100, Rafael J. Wysocki wrote:
> Is suspend-to-RAM triggering that as too?
Nope, not really. But, just to confirm: s2r is
echo "shutdown" > /sys/power/disk
echo "mem" > /sys/power/state
right?
Btw, this bug is very strange. So I did a couple more s2disk runs, i.e.
echo "shutdown" > /sys/power/disk
echo "disk" > /sys/power/state
and it seemed to me that when the eth cable is plugged in, it would
suspend and resume fine. When I then boot, unplug the cable, set all
tunables to "Good", suspend to disk and resume, no NMI message. When I
plug the cable back, only *then* the message triggered.
I need to play with this a bit more to get a better sense of when
exactly it happens.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
