From: "John Stoffel" <john@stoffel.org>
To: devzero@web.de
Cc: Martin Rogge <marogge@onlinehome.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.30.1-4 kernels freezes dual pentium-3 system
Date: Mon, 10 Aug 2009 10:42:23 -0400 [thread overview]
Message-ID: <19072.12751.294751.725334@stoffel.org> (raw)
In-Reply-To: <859079895@web.de>
>>>>> "devzero" == devzero <devzero@web.de> writes:
>> Box works works fine and very stable under 2.6.29.5 kernel, although
>> it is angry of buggy MP table (see app. #2 below). But sometimes, this
>> kernel correctly reboots the system at all, but this happens very
>> rarely. In most cases, nobody detects the box was rebooted. And this
>> is satisfactory for me.
devzero> so, what is it - stable or not stable ?
In my case, it's been stable under 2.6.29 (though with a Raid crash
after 30+ days of uptime...). Under anything newer, it hasn't been
stable, though I admit I haven't tried 2.6.29.x yet, though maybe
2.6.29.1 was ok. Not sure.
devzero> if sometimes "this kernel correctly reboots the system", do
devzero> you mean that happens spontaneously, i.e. without being
devzero> actively triggered ?
Kernel never reboots, the system locks up hard and *nothing* gets it
back beyond the reset button. SysRq is total hosed, doesn't do
anything.
devzero> i think it would be more interesting if there is anything in
devzero> dmesg on such lockup. if not, maybe you can hook up a serial
devzero> console or netconsole and trigger sysrq when you have another
devzero> lockup.
There's notthing in dmesg, nothing on the screen (it's a server and
not usually connected to a screen) and my other main machine is the
NFS client of this box, so it's kinda painful to monitor.
I need to try rigging up a completely standalone system to do both
netconsole and serial port console to see if I catch anything.
John
next prev parent reply other threads:[~2009-08-10 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 22:51 2.6.30.1-4 kernels freezes dual pentium-3 system devzero
2009-08-10 14:42 ` John Stoffel [this message]
2009-08-18 14:40 ` John Stoffel
2009-08-19 14:53 ` Vince Weaver
-- strict thread matches above, loose matches on Subject: below --
2009-08-08 21:25 devzero
2009-08-08 9:49 devzero
2009-08-08 21:03 ` Martin Rogge
2009-08-08 8:19 Martin Rogge
2009-08-03 16:25 Martin Rogge
2009-08-07 20:29 ` Martin Rogge
2009-08-10 14:38 ` John Stoffel
2009-08-03 8:44 Осипов Станислав
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=19072.12751.294751.725334@stoffel.org \
--to=john@stoffel.org \
--cc=devzero@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marogge@onlinehome.de \
/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