From: poma <pomidorabelisima@gmail.com>
To: Don Zickus <dzickus@redhat.com>
Cc: "Linux Kernel list" <linux-kernel@vger.kernel.org>,
"Mailing-List fedora-kernel" <kernel@lists.fedoraproject.org>,
"Jeremy Newton" <alexjnewt@hotmail.com>,
"Thomas Koch" <linrunner@gmx.net>,
"André Erdmann" <dywi@mailerd.de>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Cyrill Gorcunov" <gorcunov@gmail.com>
Subject: Re: Uhhuh - Dazed and confused, but trying to continue :)
Date: Wed, 21 Jan 2015 15:29:05 +0100 [thread overview]
Message-ID: <54BFB7B1.5000908@gmail.com> (raw)
In-Reply-To: <20150121142423.GC116159@redhat.com>
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.
prev parent reply other threads:[~2015-01-21 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 10:50 Uhhuh - Dazed and confused, but trying to continue :) poma
2015-01-19 13:49 ` Don Zickus
2015-01-21 9:01 ` poma
2015-01-21 14:24 ` Don Zickus
2015-01-21 14:29 ` poma [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54BFB7B1.5000908@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=alexjnewt@hotmail.com \
--cc=dywi@mailerd.de \
--cc=dzickus@redhat.com \
--cc=gorcunov@gmail.com \
--cc=kernel@lists.fedoraproject.org \
--cc=linrunner@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox