[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <510ED6B4.6000405@suse.cz>
Date: Sun, 03 Feb 2013 22:29:24 +0100
From: Jiri Slaby <jslaby@...e.cz>
To: Borislav Petkov <bp@...en8.de>, "Rafael J. Wysocki" <rjw@...k.pl>,
Bjorn Helgaas <bhelgaas@...gle.com>, x86@...nel.org,
lkml <linux-kernel@...r.kernel.org>,
Konstantin Khlebnikov <khlebnikov@...nvz.org>
Subject: Re: Uhhuh. NMI received for unknown reason 2c on CPU 0.
On 01/31/2013 02:18 PM, Borislav Petkov wrote:
> On Thu, Jan 31, 2013 at 09:28:12AM +0100, Jiri Slaby wrote:
>> And, does it happen if you switch all of them but NMI wtd in there?
>
> No, but something else happens. Here's the whole dance:
>
> 1. Switch all tunables except "NMI watchdog should be turned off" to "Good"
> 2. suspend to disk
> 3. resume... all good
> 4. switch "NMI watchdog should be turned off" to "Good"
> 5. suspend to disk
> 6. resume... all good
> 7. start powertop, toggle "Wireless Power Saving for interface wlan0" twice.
> I.e., "Good" -> "Bad"; "Bad" -> "Good".
>
> -> Boom! Unknown reason NMI. It happened right during the toggle because
> it appeared in the framebuffer console (no X) right during me toggling
> this.
Right, for me too. Even if I disable nmi watchdog in both the boot and
image kernel, the NMI eventually occurs (dunno what's the trigger now
though).
Given the above I'm thinking about switching that intel wi-fi card to
ath9k which I have at hand and retest...
--
js
suse labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists