From: Michael Buesch <mbuesch@freenet.de>
To: Chris Stromsoe <cbs@cts.ucla.edu>
Cc: linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: lock up with 2.4.23
Date: Thu, 12 Feb 2004 16:34:21 +0100 [thread overview]
Message-ID: <200402121634.32186.mbuesch@freenet.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0402111939370.5221@potato.cts.ucla.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 12 February 2004 06:18, you wrote:
> When the machine locked up, it was not pingable. I connected via serial
> console and used sysrq to sync and remount the disks readonly. I also got
> output from sysrq+t, sysrq+p, and sysrq+m. Output is below.
I had a lockup on 2.4.24 today, too.
The machine was not pingable (suddenly) and all network
access failed (NFS, SSH).
The box had an uptime of aproximately 20 days.
Machine is a pentium 1 75 Mhz with 48MB Ram.
The bad things are:
- - I have no logs. They got lost when I reset the machine.
- - The kernel was tainted with the fritzcard dsl driver.
But exact the same driver had uptimes of over 30 days on
this machine several times in the past.
- - The machine has no peripheral hardware, so I was not
able to test sysrq, catch dmesg or something like that.
I know, that this mail is not very helpfull, but maybe
better than sending no mail at all. :)
- --
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAK50GFGK1OIvVOP4RAhYtAJ4+oiQYelqEB9kS5mjLC+HTHo9gnwCgmpVW
GWYjyRLplaKcY2Rt22cRQIw=
=dyJN
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-02-12 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 5:18 lock up with 2.4.23 Chris Stromsoe
2004-02-12 15:34 ` Michael Buesch [this message]
2004-02-12 17:19 ` Michael Frank
2004-02-12 18:27 ` Michael Buesch
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 21:03 Xose Vazquez Perez
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=200402121634.32186.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--cc=cbs@cts.ucla.edu \
--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.