From: khromy@lnuxlab.ath.cx (khromy)
To: linux-kernel@vger.kernel.org
Subject: Re: Nervous with 2.4.21-pre3 and -pre3-ac*
Date: Mon, 13 Jan 2003 00:47:00 -0500 [thread overview]
Message-ID: <20030113054700.GA949@lnuxlab.ath.cx> (raw)
In-Reply-To: <20030113052151.C4594171B7@bellini.mit.edu>
On Mon, Jan 13, 2003 at 12:21:51AM -0500, ghugh Song wrote:
> BTW, After several segmentation faults from a few repeated tries
> of unsuccessful tar command, the machine got frozen.
I had the same thing happen here using 2.4.21-pre3-ac2. cpio segfaulted
and then the machine hung. I went back to 2.4.21-pre3 and all is well,
so far.
PIII866, 256MB RAM
Bus 0, device 7, function 1:
IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 6).
Master Capable. Latency=32.
I/O at 0xd000 [0xd00f].
--
L1: khromy ;khromy(at)lnuxlab.ath.cx
next prev parent reply other threads:[~2003-01-13 5:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 5:21 Nervous with 2.4.21-pre3 and -pre3-ac* ghugh Song
2003-01-13 5:47 ` khromy [this message]
2003-01-13 14:52 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 7:18 ghugh Song
2003-01-12 18:55 ghugh Song
2003-01-12 20:18 ` Alan Cox
2003-01-13 8:25 ` Dee
2003-01-16 18:16 ` Zed Pobre
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=20030113054700.GA949@lnuxlab.ath.cx \
--to=khromy@lnuxlab.ath.cx \
--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 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.