From: Chris Mason <mason@suse.com>
To: patrick@spacesurfer.com, linux-kernel@vger.kernel.org
Subject: Re: reiserfs problem
Date: Fri, 23 Feb 2001 13:31:24 -0500 [thread overview]
Message-ID: <462990000.982953084@tiny> (raw)
In-Reply-To: <3A9697EC.892E4230@spacesurfer.com>
On Friday, February 23, 2001 05:03:40 PM +0000 Patrick Mackinlay
<patrick@spacesurfer.com> wrote:
> When 2.4.1 was released I reported a kernel oops with reiserfs, I got no
> response.
Hmmm, don't seem to have any other reiserfs mail from you. Sorry I missed
it.
[ ...]
>
> kernel oops report:
>>> EIP; d2cf9db8 <[reiserfs]create_virtual_node+298/490> <=====
We've had a half dozen or so reports so far of this, almost every time it
has been resolved as a compiler issue, usually an unpatched gcc 2.96. One
user was using 2.95.3, but did not report back if switching to 2.95.2 or
egcs fixed the oops.
Anyway, which compiler did you use to compile the kernel?
-chris
next prev parent reply other threads:[~2001-02-23 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 17:03 reiserfs problem Patrick Mackinlay
2001-02-23 18:31 ` Chris Mason [this message]
2001-02-23 18:40 ` Patrick Mackinlay
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=462990000.982953084@tiny \
--to=mason@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@spacesurfer.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox