From: Dan Creswell <dan@dcrdev.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: [Fwd: Re: Hard lock on 2.6-test9]
Date: Sun, 16 Nov 2003 16:58:06 +0000 [thread overview]
Message-ID: <3FB7AC9E.5020502@dcrdev.demon.co.uk> (raw)
-------- Original Message --------
Subject: Re: Hard lock on 2.6-test9
Date: Sun, 16 Nov 2003 13:33:32 +0000
From: Dan Creswell <dan@dcrdev.demon.co.uk>
To: Davide Libenzi <davidel@xmailserver.org>
References:
<Pine.LNX.4.44.0311151501000.1997-100000@bigblue.dev.mdolabs.com>
Davide Libenzi wrote:
>On Sat, 15 Nov 2003, Dan Creswell wrote:
>
>
>
>>Chipset is E7505 with dual Xeons.
>>
>>Under X, I can provoke a lock just by waggling the mouse. I've had the
>>machine connected up to a serial console with nmi_watchdog=1 and, when
>>the machine dies, nothing is printed on the console (I guess that makes
>>it *very* bad :( ).
>>
>>
>
>Is NMI really enabled?
>
>$ cat /proc/interrupts
>
>
>
>- Davide
>
>
>
>
>
Sorry Davide,
I forgot to mention that a UP 2.6-test9 works fine whilst an SMP version
doesn't (unless I use "noapic")
2.4 in dual or UP seems rock-solid (bar one issue which may have been
network card related).
Dan.
next reply other threads:[~2003-11-16 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-16 16:58 Dan Creswell [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-16 16:57 [Fwd: Re: Hard lock on 2.6-test9] Dan Creswell
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=3FB7AC9E.5020502@dcrdev.demon.co.uk \
--to=dan@dcrdev.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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