From: Mark Jaffe <wizards@wizdev.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Troubling system freezups...
Date: Wed, 23 Jan 2002 16:20:50 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.3.96.1020123161956.7638C-100000@wizdev.net> (raw)
I am still experiencing system hangs. Kernel is 2.4.18-pre0-benh on
8500/dual-604. I had just rsync'ed the kernel source this afternoon and
launched a build script. Monitored output of the build halted partway
through, indicating frozen state. Unfortunately, I returned it to the
co-lo so this necessitates a visit to reboot and probably baby-sit a
manual fsck of the volume.
Is there some way to see what happened?
Mark
============================================================
Mark Jaffe | (408) 972-9638 (home)
Chief Wizard | (408) 807-1530 (cell/page/voicemail)
Computer Wizards | (425) 795-6421 (FAX)
wizards@wizdev.net | http://www.wizdev.net/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-01-24 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 0:20 Mark Jaffe [this message]
2002-01-23 23:30 ` Troubling system freezups Benjamin Herrenschmidt
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=Pine.LNX.3.96.1020123161956.7638C-100000@wizdev.net \
--to=wizards@wizdev.net \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).