From: Gregor Jasny <gjasny@wh8.tu-dresden.de>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.4 Kernel Oops and ls+rm segfaults
Date: Fri, 1 Jun 2001 11:14:28 +0200 [thread overview]
Message-ID: <01060111142800.00919@backfire> (raw)
In-Reply-To: <Pine.GSO.4.21.0106010451060.20420-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0106010451060.20420-100000@weyl.math.psu.edu>
Am Freitag, 1. Juni 2001 10:52 schrieb Alexander Viro:
> On Fri, 1 Jun 2001, Gregor Jasny wrote:
> > Can anyone tell me, where this oops came from?
> > The machine is a HP NetServer II lc (EISA+PCI architecture).
> > The distribution is a slackware 7.0 with parts of 7.1 and current.
> > gcc: 2.95.4 20010319 (Debian prerelease)
> >
>
> Pagecache corruption somewhere.
> a) what filesystems do you have?
> b) is the thing reproducable?
a) pure ext2-fs (sometimes a mounted nfs)
b) Not really. It happend with earlier kernel revisions, too.
I alredy replaced the fs-utils and compiled the kernel at my workstation
(with gcc-2.95.3)
If it matters: we have the Compushack FDDI driver installed. It can be found
at: http://hell.wh8.tu-dresden.de/~gjadm/csfddi-3.0.0-5.diff.gz
Regards,
-Gregor
prev parent reply other threads:[~2001-06-01 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-01 8:47 2.4.4 Kernel Oops and ls+rm segfaults Gregor Jasny
2001-06-01 8:52 ` Alexander Viro
2001-06-01 9:14 ` Gregor Jasny [this message]
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=01060111142800.00919@backfire \
--to=gjasny@wh8.tu-dresden.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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.