From: David Golombek <daveg@permabit.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.31 hangs, no information on console or serial port
Date: 21 Feb 2006 10:23:56 -0500 [thread overview]
Message-ID: <7yirr8hh0z.fsf@questionably-configured.permabit.com> (raw)
I have a box running a modified Debian/woody system and 2.4.31. It is
intermittently hanging such that:
* All logging to /var/log ceases.
* Machine is still pingable.
* Machine can be telneted to on time port, but no time is echoed.
* After attaching a console+keyboard, console would not unblank.
* Nothing responded when attaching a serial console.
* Machine does not respond to Ctrl-Alt-Del
* No DMI messages are logged.
* Hang is persistent until physical reboot.
This has happened 4 times, on 2 separate machines (under roughly
similar conditions). Machines are up variable amounts of time before
crashing, between many weeks and less than 1 day. Nothing unusual is
logged in /var/log/{deamon.log,kern.log,messages,syslog} prior the
hang, except that /var/log/messages includes the "TCP: Treason
uncloaked!" warnings that are fixed in 2.4.32. No users were logged
on at the time of 3 of the 4 crashes, and no local user activity was
present at the time of the 4th.
The machines are Intel P4's with 2GB of memory
The machine is under relatively high load and has a custom userspace
nfs server running on it (which is potentially to blame, but we've
been unable to determine how). The custom userspace nfs server and
tomcat4 are the primary applications running.
Any suggestions as to how we might debug this or possible causes would
be greatly appreciated.
Thanks,
Dave
next reply other threads:[~2006-02-21 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 15:23 David Golombek [this message]
2006-02-21 15:29 ` Benjamin LaHaise
2006-02-21 16:04 ` David Golombek
2006-02-21 21:41 ` Willy Tarreau
2006-02-27 16:24 ` David Golombek
2006-02-27 16:39 ` Benjamin LaHaise
2006-02-27 17:48 ` David Golombek
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=7yirr8hh0z.fsf@questionably-configured.permabit.com \
--to=daveg@permabit.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome