From: Willy Tarreau <willy@w.ods.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: "Hans-Jürgen Mehnert" <hjmehnert@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel crashes 2.4.31final + 2.4.32rc1
Date: Thu, 27 Oct 2005 06:34:39 +0200 [thread overview]
Message-ID: <20051027043439.GL22601@alpha.home.local> (raw)
In-Reply-To: <20051026083956.GA9473@logos.cnet>
Hi Hans & Marcelo,
On Wed, Oct 26, 2005 at 06:39:56AM -0200, Marcelo Tosatti wrote:
> Hi Hans,
>
> On Mon, Oct 24, 2005 at 05:24:14PM +0200, Hans-Jürgen Mehnert wrote:
> > [1.]
> > PROBLEM: kernel crashes 2.4.31final + 2.4.32rc1
> >
> >
> > [2.]
> > Since kernel version 2.4.31 we have system crashes with
> > blank screen and nothing in logs on at least 5 different
> > Intel and AMD SMP machines. 2.4.32rc1 has the same problem,
> > 2.4.30 is working stable on these machines. We had no crashes
> > with the newer kernel versions on about 100 single-cpu machines
> > so far.
>
> Few questions:
>
> - Can you send dmesg output?
you could also try to get messages on the screen by preventing from blanking
using setterm :
# setterm -blank 0
Also, using a serial console to get and log messages can help.
> - Are you using the ahci driver with the Intel SATA controller? There have
> been some bugfixes in ahci during v2.4.31, although they dont look suspect.
> Is there load on the interface?
>
> - Is the USB UHCI controller being used? There are known SMP problems
> in the usb-uhci driver recently fixed (problem introduced in v2.4.28 though).
>
> - What is the workload on these machines?
>
> - Have you tried v2.4.31-pre1, -pre2, and so on to isolate the possibly problematic
> change?
I also saw that at least the machine shown in the report is using grsec. Are
all machines using grsec ? Although I don't believe it would be the cause,
we cannot exclude that a recent bug could have been introduced in it.
And what's the average time before a crash ? hours, days, weeks ?
Regards,
Willy
prev parent reply other threads:[~2005-10-27 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 15:24 PROBLEM: kernel crashes 2.4.31final + 2.4.32rc1 Hans-Jürgen Mehnert
2005-10-26 8:39 ` Marcelo Tosatti
2005-10-27 4:34 ` Willy Tarreau [this message]
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=20051027043439.GL22601@alpha.home.local \
--to=willy@w.ods.org \
--cc=hjmehnert@gmail.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 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.