From: Dan Creswell <dan@dcrdev.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Hard lock on 2.6-test9
Date: Sat, 15 Nov 2003 09:53:35 +0000 [thread overview]
Message-ID: <3FB5F79F.703@dcrdev.demon.co.uk> (raw)
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 :( ).
Booting with "noapic" helps stability considerably (though I have had
one lockup with even that this morning). I've also tried disabling AGP
support in-kernel and that makes no difference.
Strangely, 2.4 is considerably more stable (without "noapic") - anybody
have any idea what's going on or what to look at next (I'm happy to roll
my sleeves up and stare at code - just need some pointers)?
If you'd like more details, let me know and I'll post them.
Many thanks,
Dan.
P.S. There appear to have been other recent discussions on this topic
with complaints of IDE (I have an MPT/Fusion SCSI setup) and ethernet
load being enough to cause the hard lock.
next reply other threads:[~2003-11-15 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-15 9:53 Dan Creswell [this message]
2003-11-15 23:01 ` Hard lock on 2.6-test9 Davide Libenzi
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=3FB5F79F.703@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