From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25: random stalls on certain hardware - regression?
Date: Wed, 9 Jul 2008 18:36:32 +0200 [thread overview]
Message-ID: <20080709163618.GA5462@joi> (raw)
In-Reply-To: <4873E27C.6050504@msgid.tls.msk.ru>
On Wed, Jul 09, 2008 at 01:56:12AM +0400, Michael Tokarev wrote:
> No hope to resolve this but still - maybe someone has an idea...
>
> Hardware is -
> AMD Athlon x2-64 system
> Asus M2N-SLI DELUXE motherboard (nvidia MCP55)
> AMD BE-2400 CPU
> 2x 2Gb mem
> Adaptec 3950B Ultra2 SCSI adapter (*)
> 4x 36Gb Seagate SCSI disks
> 2x nvidia GbE ethernet
> rtl8139 nic as 3rd one
>
> When booting 2.6.25 - either 32 or 64 bits - the system freezes/hangs
> at some random point. So far there was about 10 hangs, some after
> several minutes after boot, some are within hours.
>
> The "hang" is a complete system freeze - on the console there's
> still "... login:" prompt, but nothing works - keyboard is stuck
> (numlock doesn't work), and server is not responding over network.
> Sometimes ping to the server itself works, but definitely not routing.
> (it's a server so no fancy stuff is loaded - X isn't even installed).
>
> The kernel is vanilla 2.6.25 - tried several - .5, .8, .10 now -
> the effect is the same.
>
> 2.6.24 and before worked without any glitch (2.6.24 is currently
> running). We tried different versions of BIOS (was 12something
> before, tried 1304 and - currently - 1405, since 1502 is still
> beta) - no difference at all.
>
> The problem is that it is a production machine, and quite some
> people depend on it (it's a remote office with only one server),
> so I've very limited ability to try something. Unfortunately not
> git bisect, -- or at least I'm afraid to try it, both because of
> possibility to have many reboots AND new freezes, and because
> unstable kernel (2.6.25pre stuff) with possibility to break something.
Definitely try 2.6.26-rc9 (which will soon become 2.6.26, so people will
probably ask you to test patches on top of this kernel) and if it will still
lock up, take a look at Documentation/nmi_watchdog.txt and maybe
Documentation/networking/netconsole.txt in kernel sources.
Marcin
next prev parent reply other threads:[~2008-07-09 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 21:56 2.6.25: random stalls on certain hardware - regression? Michael Tokarev
2008-07-09 8:32 ` Oliver Neukum
2008-07-09 9:22 ` Michael Tokarev
2008-07-09 11:37 ` Oliver Neukum
2008-07-10 7:11 ` Michael Tokarev
2008-07-09 16:36 ` Marcin Slusarz [this message]
2008-07-10 7:04 ` Michael Tokarev
2008-08-12 10:21 ` Michael Tokarev
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=20080709163618.GA5462@joi \
--to=marcin.slusarz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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