From: Shane Wegner <shane-keyword-kernel.a35a91@cm.nu>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.23 crash on Intel SDS2
Date: Sat, 15 Nov 2003 12:58:28 -0800 [thread overview]
Message-ID: <20031115205828.GA1367@cm.nu> (raw)
In-Reply-To: <Pine.LNX.4.44.0311151029310.10014-100000@logos.cnet>
On Sat, Nov 15, 2003 at 10:31:07AM -0200, Marcelo Tosatti wrote:
>
>
> On Wed, 12 Nov 2003, Shane Wegner wrote:
>
> > On Wed, Nov 12, 2003 at 09:21:59AM -0200, Marcelo Tosatti wrote:
> > > > It's an Intel server board model SDS2 with a dual Pentium
> > > > III tualatin 1.13ghz. I am attaching the dmesg output from
> > > > the kernel in case it is helpful but as there is no panics
> > > > or oops being printed, I am not sure how best I can help
> > > > track this down. If there is anything further I can do or
> > > > any other information needed, let me know.
> > >
> > > > On node 0 totalpages: 262144
> > > > > zone(0): 4096 pages.
> > > > zone(1): 225280 pages.
> > > > zone(2): 32768 pages.
> > >
> > > > What do you (what is your workload) during the few minutes before the
> > > > crash?
> >
> > It's a database machine running MySQL and Postgres. The
> > MySQL server runs about 4 queries/sec and PostGres only as
> > needed. It also does some minor mail service, say 2
> > messages per minute and runs apache at about 10 requests
> > per minute.
> >
> > > > There are no significant driver changes in -pre4 that could affect you.
> > > >
> > > Ah, have you tried to boot with "nmi_watchdog=1" as Mikael suggested?
> >
> > Will try that next, thanks.
>
> Shane,
>
> Have you tried the NMI watchdog?
Hi,
I did and unfortunately, it was of little help. If
anything though, it made the lockup more consistent. The
three times I tried to boot with nmi_watchdog=1, it locked
up when starting SpamAssassin. Nothing special about that
process but just above that it started the hotplug
subsystem which I use to automatically insert various usb
drivers as needed. Could that have anything to do with it?
Shane
Btw, to clarify, when the lockup occurs with nmi_watchdog,
no oops gets printed.
next prev parent reply other threads:[~2003-11-15 20:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 21:05 2.4.23 crash on Intel SDS2 Shane Wegner
2003-11-10 10:46 ` Marcelo Tosatti
2003-11-12 7:07 ` Shane Wegner
2003-11-11 10:46 ` Marcelo Tosatti
2003-11-12 11:02 ` Marcelo Tosatti
2003-11-12 11:21 ` Marcelo Tosatti
2003-11-12 18:22 ` Shane Wegner
2003-11-15 12:31 ` Marcelo Tosatti
2003-11-15 20:58 ` Shane Wegner [this message]
2003-11-15 21:12 ` Willy Tarreau
2003-11-16 0:13 ` Keith Owens
2003-11-16 22:02 ` Shane Wegner
2003-11-17 11:29 ` Marcelo Tosatti
2003-11-17 17:29 ` Shane Wegner
-- strict thread matches above, loose matches on Subject: below --
2003-11-10 11:20 Mikael Pettersson
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=20031115205828.GA1367@cm.nu \
--to=shane-keyword-kernel.a35a91@cm.nu \
--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