From: Patrick Mackinlay <patrick@spacesurfer.com>
To: Chris Mason <mason@suse.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiserfs problem
Date: Fri, 23 Feb 2001 18:40:24 +0000 [thread overview]
Message-ID: <3A96AE98.E7754F9C@spacesurfer.com> (raw)
In-Reply-To: <462990000.982953084@tiny>
Chris Mason wrote:
>
> 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
I didn't want to join the kernel mailing list (too much traffic) so I
sent it to the email address suggested on the reiserfs home page. I
guess it didn't get through.
It seems I am in fact using a buggy compiler (damn RedHat 7, forgot I
had upgraded on this machine) I will try re-compiling with another
compiler and let you know if I still have problems.
regards,
Patrick
--
Patrick Mackinlay patrick@spacesurfer.com
ICQ: 59277981 tel: +44 7050699851
fax: +44 7050699852
SpaceSurfer Limited http://www.spacesurfer.com/
next prev parent reply other threads:[~2001-02-23 18:38 UTC|newest]
Thread overview: 4+ 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
2001-02-23 18:40 ` Patrick Mackinlay [this message]
[not found] <1208801633.20150514020848@vvo.ru>
2015-05-21 1:45 ` Edward Shishkin
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=3A96AE98.E7754F9C@spacesurfer.com \
--to=patrick@spacesurfer.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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.