From: Jens Axboe <axboe@suse.de>
To: Anton Altaparmakov <aia21@cantab.net>
Cc: william stinson <wstinsonfr@yahoo.fr>, linux-kernel@vger.kernel.org
Subject: Re: vanilla 2.5.13 severe file system corruption experienced follozing e2fsck ...
Date: Mon, 6 May 2002 10:50:33 +0200 [thread overview]
Message-ID: <20020506085033.GD820@suse.de> (raw)
In-Reply-To: <5.1.0.14.2.20020505200138.00b2d660@pop.cus.cam.ac.uk> <20020505183451.98763.qmail@web14102.mail.yahoo.com> <5.1.0.14.2.20020505200138.00b2d660@pop.cus.cam.ac.uk> <5.1.0.14.2.20020506093027.00aca720@pop.cus.cam.ac.uk>
On Mon, May 06 2002, Anton Altaparmakov wrote:
> At 06:55 06/05/02, Jens Axboe wrote:
> >On Sun, May 05 2002, Anton Altaparmakov wrote:
> >> Note even with that fix IDE (at least TCQ) is really easy to crash when
> >you
> >> put the system under heavier I/O (at least on my via box)...
> >
> >If you have stumpled upon a tcq bug, I'd like to know more about it.
>
> Back trace (sorry didn't have ckermit running so didn't catch the whole
> output and was too lazy to write it all down): blk_queue_invalidate_tags,
> tcq_invalidate_queue, ide_dmaq_complete, ide_dmaq_intr, ata_irq_request,
> ide_dmaq_intr, handle_IRQ_event, do_IRQ, ideprobe_init.
Same problem as Sebastian I'm sure, in which case the backtrace holds no
info for me, the IDE messages printed _before_ the panic would be
helpful though :-)
> At the moment I try to not use 2.5.x as much as possible and only boot into
> it to test ntfs or other changes I make, so when I do that next I will make
> sure I am capturing on the serial console and send you details if I
> experince the panic again...
Sure, I understand. Just hang on, I'll be releasing a tcq backport for
2.4.19-pre8 today that you can test instead.
--
Jens Axboe
next prev parent reply other threads:[~2002-05-06 8:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 18:34 vanilla 2.5.13 severe file system corruption experienced follozing e2fsck william stinson
2002-05-05 19:04 ` Anton Altaparmakov
2002-05-06 5:55 ` Jens Axboe
2002-05-06 8:47 ` Anton Altaparmakov
2002-05-06 8:50 ` Jens Axboe [this message]
2002-05-06 10:02 ` tcq problem details " Anton Altaparmakov
2002-05-06 12:10 ` Jens Axboe
2002-05-06 13:18 ` Jens Axboe
2002-05-06 14:36 ` Anton Altaparmakov
2002-05-06 13:43 ` Sebastian Droege
2002-05-06 13:48 ` Jens Axboe
2002-05-06 15:14 ` Sebastian Droege
2002-05-06 15:17 ` Jens Axboe
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=20020506085033.GD820@suse.de \
--to=axboe@suse.de \
--cc=aia21@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wstinsonfr@yahoo.fr \
/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.