On Wednesday, January 30, 2013 09:33:27 PM Jiri Slaby wrote: > On 01/30/2013 09:00 PM, Borislav Petkov wrote: > > On Wed, Jan 30, 2013 at 08:43:55PM +0100, Jiri Slaby wrote: > >> On 01/30/2013 06:44 PM, Borislav Petkov wrote: > >>> On Wed, Jan 30, 2013 at 10:27:42AM -0700, Bjorn Helgaas wrote: > >>>> You're right, I don't think we're quite ready to merge those patches. > >>>> But if your NMI is easy to reproduce, it might be worth removing > >>>> e1000e altogether to see if it still happens. > >>> > >>> That's the problem - I've seen it only once so far. I'll watch out for > >>> it and do the above when I find a reliable way of reproducing it. Will > >>> keep you posted. > >> > >> It happens here too. Dunno what is the root cause. I *think* that it > >> never happened unless I used ethernet. Other than that I see no pattern. > >> > >> Attaching -C 20 grep of messages over the last half year if there is > >> something that may help somehow. > > > > Cool, so it happens once a day, not every day, everytime during resume, > > and with e1000e. Can you try Bjorn's suggestion to remove e1000e > > altogether and see if it still happens? > > No, e1000e is not to blame at all. I moved e1000e out of /lib/modules > and it still happens. > > What is cool is that I have steps to reproduce: > 1) boot > 2) run the attached script (turn on all possible power savings -- in > fact everything what powertop suggests) > 3) suspend to _disk_ (mem is not enough, BIOS apparently has to > interfere here)
No, I don't think it's the BIOS. Most likely the boot kernel. > 4) resume from disk > 5) boom > > I tried to remove also wireless drivers, no change. Is the resume boot kernel the same as the one in the image? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- 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/
