[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <54BFB7B1.5000908@gmail.com>
Date: Wed, 21 Jan 2015 15:29:05 +0100
From: poma <pomidorabelisima@...il.com>
To: Don Zickus <dzickus@...hat.com>
CC: Linux Kernel list <linux-kernel@...r.kernel.org>,
Mailing-List fedora-kernel <kernel@...ts.fedoraproject.org>,
Jeremy Newton <alexjnewt@...mail.com>,
Thomas Koch <linrunner@....net>,
André Erdmann <dywi@...lerd.de>,
Pali Rohár <pali.rohar@...il.com>,
Cyrill Gorcunov <gorcunov@...il.com>
Subject: Re: Uhhuh - Dazed and confused, but trying to continue :)
On 21.01.2015 15:24, Don Zickus wrote:
> On Wed, Jan 21, 2015 at 10:01:32AM +0100, poma wrote:
>> On 19.01.2015 14:49, Don Zickus wrote:
>>
>> Thank you, in the meantime, I've found what causes non-maskable interrupt, [23]d on CPU 0, on resuming S4,
>> on AMD Phenom(tm) II X4 955 Processor.
>>
>> /etc/default/tlp
>> ...
>> # Kernel NMI Watchdog
>> # 0=disable (default, saves power) / 1=enable (for kernel debugging only)
>> NMI_WATCHDOG=0
>>
>> Toggling to 1, messages no longer appear,
>> NMI_WATCHDOG=1
>>
>> $ cat /proc/sys/kernel/nmi_watchdog
>> 1
>> $ sysctl kernel.watchdog
>> kernel.watchdog = 1
>>
>> Isn't it brilliant.
>
>
> Hehe. Ok. All that does is swallow your unknown NMI. But if that makes
> you happy, I am fine with that. :-)
>
> Cheers,
> Don
>
I don't want to bother you for nothing, as long as nothing crashes, it can pass.
Thanks again.
--
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