From: Nathan Scott <nathans@sgi.com>
To: Chris Seufert <seufert@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Kernel Ooops
Date: Wed, 6 Sep 2006 08:30:28 +1000 [thread overview]
Message-ID: <20060906083028.I3365803@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <2260b150609050427p3123cb85q5af484d8b907e6ac@mail.gmail.com>; from seufert@gmail.com on Tue, Sep 05, 2006 at 09:27:04PM +1000
On Tue, Sep 05, 2006 at 09:27:04PM +1000, Chris Seufert wrote:
> I have had this one before, and i had assumed it had been fixed.
>
> System seems very stable running ext3, so i dont 'think' its hardware
> related, but i am begining to wonder.
This is fixed, what kernel version are you using? (it was fixed
in -rc5/6 IIRC).
> RIP [<ffffffff8031dd16>] xfs_btree_init_cursor+0x48/0x1bd
cheers.
--
Nathan
next prev parent reply other threads:[~2006-09-05 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 11:27 Kernel Ooops Chris Seufert
2006-09-05 22:30 ` Nathan Scott [this message]
2006-09-05 23:30 ` Chris Seufert
2006-09-05 23:31 ` Nathan Scott
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=20060906083028.I3365803@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=seufert@gmail.com \
--cc=xfs@oss.sgi.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