From: Folkert van Heusden <folkert@vanheusden.com>
To: Jiri Slaby <lnx4us@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.13.3] occasional oops mostly in iget_locked
Date: Thu, 5 Jan 2006 22:43:29 +0100 [thread overview]
Message-ID: <20060105214329.GE10923@vanheusden.com> (raw)
In-Reply-To: <3888a5cd0601050849p6ee4cb48s9cc9c9bd6fd20cc8@mail.gmail.com>
> > 1. occasional oops with 2.6.13.3
> > 2. see 1
> > 3. fs
> > 4. 2.6.13.3
> > 5. 2.6.11.6 (none tested inbetween)
> and what about later kernel?
> Could you try git bisect (or manual) to determine the exactly frist
> "bad" version as accurate as possible?
Well that problem seems to be solved in 2.6.15 so does this problem
matter anymore? I'm a little hesitant to play a lot with that system as
it'll make some people really upset.
Folkert van Heusden
--
Try MultiTail! Multiple windows with logfiles, filtered with regular
expressions, colored output, etc. etc. www.vanheusden.com/multitail/
----------------------------------------------------------------------
Get your PGP/GPG key signed at www.biglumber.com!
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
next prev parent reply other threads:[~2006-01-05 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 19:01 [2.6.13.3] occasional oops mostly in iget_locked Folkert van Heusden
2005-12-19 19:35 ` Folkert van Heusden
[not found] ` <3888a5cd0601050849p6ee4cb48s9cc9c9bd6fd20cc8@mail.gmail.com>
2006-01-05 16:51 ` Folkert van Heusden
2006-01-05 21:43 ` Folkert van Heusden [this message]
2006-01-06 0:31 ` Francois Romieu
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=20060105214329.GE10923@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lnx4us@gmail.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