From: Ed Tomlinson <edt@aei.ca>
To: Ingo Molnar <mingo@elte.hu>, Matthew <jackdachef@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Fwd: Fwd: laptop / computer hardlocks during execution of 32bit applications(binaries) on 64bit system (Gentoo)
Date: Thu, 10 Jan 2008 21:22:51 -0500 [thread overview]
Message-ID: <200801102122.51507.edt@aei.ca> (raw)
>> - if yes, does booting with "nmi_watchdog=2 idle=poll" give you a
>> working NMI watchdog? (working NMI watchdog means the NMI counts
>> increase for all cores in /proc/interrupts).
> booting with the above gives me an incrementing NMI counter in /proc/interrupts
Ingo,
Is there anything else that needs to be set in the kernel config for the nmi watchdog to trigger?
I ask because I just had a hang but nothing showed on the _serial_ console - I waited a couple
of minutes before rebooting.... Is there any other way to verify the watchdog is working?
I seem to need X active with mix of 32 and 64 bit applications active to get hung here. A massivily
threaded 64 bit java app along with 32 bit firefox and a wine active will eventually trigger things here.
If I had to guess I would say that it the switch from 32 to 64 (or vise versa) that triggers the isuue.
TIA & test/debug patches welcome,
Ed Tomlinson
next reply other threads:[~2008-01-11 2:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 2:22 Ed Tomlinson [this message]
2008-01-14 16:16 ` Fwd: Fwd: laptop / computer hardlocks during execution of 32bit applications(binaries) on 64bit system (Gentoo) Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2007-12-29 19:57 Matthew
2007-12-29 23:04 ` Fwd: " Matthew
2007-12-30 0:28 ` Miguel Botón
2008-01-02 8:40 ` Ingo Molnar
[not found] ` <e85b9d30801080333y3d6668ccgf20f9666d0326884@mail.gmail.com>
2008-01-08 11:40 ` Fwd: " Matthew
2008-01-09 0:58 ` H. Peter Anvin
2008-01-10 9:05 ` Matthew
2008-01-10 9:42 ` Ingo Molnar
2008-01-10 12:43 ` Matthew
2008-01-10 12:48 ` Ingo Molnar
2008-01-10 12:59 ` Matthew
2008-01-10 13:24 ` Ingo Molnar
2008-01-10 13:08 ` Ed Tomlinson
2008-01-10 13:32 ` Ingo Molnar
2008-01-10 15:56 ` Matthew
2008-01-10 16:38 ` Ed Tomlinson
2008-01-10 23:35 ` Zan Lynx
2008-01-10 21:10 ` Matthew
2008-01-10 21:17 ` H. Peter Anvin
2008-01-10 21:52 ` Matthew
2008-01-10 21:57 ` H. Peter Anvin
2008-01-10 22:28 ` Matthew
2008-01-10 22:30 ` H. Peter Anvin
2008-01-10 22:53 ` Matthew
2008-01-14 16:13 ` Ingo Molnar
2008-01-14 16:47 ` Matthew
2008-01-14 17:00 ` Ingo Molnar
2008-01-14 22:16 ` Ed Tomlinson
2008-01-15 17:11 ` Matthew
2008-01-15 22:09 ` Ingo Molnar
2008-01-15 23:41 ` Ed Tomlinson
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=200801102122.51507.edt@aei.ca \
--to=edt@aei.ca \
--cc=hpa@zytor.com \
--cc=jackdachef@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.