On 01/31/2013 08:09 AM, Borislav Petkov wrote: > On Thu, Jan 31, 2013 at 01:54:56AM +0100, Rafael J. Wysocki wrote: >> On Thursday, January 31, 2013 12:47:40 AM Jiri Slaby wrote: >>> On 01/31/2013 12:12 AM, Jiri Slaby wrote: >>>> I think I will start with commenting parts of `power' script to see >>>> exactly which of the power savings cause this. >>> >>> ... NMI watchdog. If I remove it from the script, the problem >>> disappears. If I try it alone, I have those NMIs. >> >> Well, beats me. :-( >> >> I suspect that it doesn't quiesce itself sufficiently before image >> restoration >> and we get some crosstalk between the boot kernel and the image kernel. > > Well, I did what Jiri said causes it: > > echo 0 > /proc/sys/kernel/nmi_watchdog > > No NMI. > > BUT(!), if I start powertop and set all tunables in the "Tunables" tab > to "Good", then suspend to disk, when I resume I get the NMI and this > time the unknown reason is 0x3c. Sounds like this needs bisection... > Btw, this is latest -rc5 + tip/master and Jiri triggers it on 3.7-stable > ...
And 3.6(.0) was the first one I _tried_ and had that issue too. Not sure if there is any bisect-good kernel to start with. > Btw, this e1000e thing has another problem: when I unplug the network > cable and replug it again, it cannot ping local network anymore. > Normally, when you plug the network cable back in, it does some sort if > link detection saying eth link is back up but it doesn't say it on that > box - only a reboot fixes it. Hmm. I think this is what Konstantin fixes with his patches. -- js suse labs -- 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/
