From: Simon Kirby <sim@netnation.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.24 SMP lockups
Date: Sun, 11 Jan 2004 01:01:35 -0800 [thread overview]
Message-ID: <20040111090135.GB6834@netnation.com> (raw)
In-Reply-To: <Pine.LNX.4.58L.0401101758010.1310@logos.cnet>
On Sat, Jan 10, 2004 at 05:58:18PM -0200, Marcelo Tosatti wrote:
> This sounds like a deadlock. I wonder why the NMI watchdog is not
> triggering.
It appears the box I was expecting it to work onn has issues with the NMI
working properly, so that may explain why nothing was showing up. I'll
try on others.
> Can you share all available SysRQ-P output for the locked CPU ? SysRQ-T if
> possible, too.
Will do, in the next few days.
> Can you please describe the hardware in more detail. Is there any common
> hardware used in these boxes?
The CPUs, motherboards, SCSI, Ethernet, etc., are all different... They
are all SMP, and are fairly busy web servers.
Simon-
next prev parent reply other threads:[~2004-01-11 9:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 19:58 2.4.24 SMP lockups Marcelo Tosatti
2004-01-11 9:01 ` Simon Kirby [this message]
2004-01-14 16:23 ` Marcelo Tosatti
2004-01-15 14:35 ` Thomas Zehetbauer
-- strict thread matches above, loose matches on Subject: below --
2004-01-09 21:04 Simon Kirby
2004-01-09 22:20 ` Arkadiusz Miskiewicz
2004-01-10 15:51 ` Thomas Zehetbauer
[not found] ` <Pine.LNX.4.58L.0401101719400.1310@logos.cnet>
2004-01-10 22:40 ` Andrew Morton
2004-01-11 4:12 ` Rik van Riel
2004-01-11 13:16 ` Marcelo Tosatti
2004-01-12 12:18 ` Marcelo Tosatti
2004-01-12 12:43 ` Thomas Zehetbauer
2004-01-11 8:55 ` Simon Kirby
2004-01-11 9:30 ` Willy Tarreau
2004-01-14 17:07 ` Simon Kirby
2004-01-14 17:56 ` Marcelo Tosatti
2004-01-16 2:34 ` Philippe Troin
2004-01-14 18:28 ` David Woodhouse
2004-01-14 21:01 ` David Woodhouse
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=20040111090135.GB6834@netnation.com \
--to=sim@netnation.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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