From: Jens Axboe <jens.axboe@oracle.com>
To: Arkadiusz Miskiewicz <arekm@maven.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.22 oops kernel BUG at block/elevator.c:366!
Date: Wed, 29 Aug 2007 20:08:01 +0200 [thread overview]
Message-ID: <20070829180800.GC7932@kernel.dk> (raw)
In-Reply-To: <200708292004.36426.arekm@maven.pl>
On Wed, Aug 29 2007, Arkadiusz Miskiewicz wrote:
> On Wednesday 29 of August 2007, Jens Axboe wrote:
> > On Wed, Aug 29 2007, Arkadiusz Miskiewicz wrote:
> > > I guess I should sent these here since it looks like not scsi bug anyway.
> >
> > It's stex, right? It seems to have some issues with multiple completions
> > of commands, which craps out the block layer of course.
>
> Yes, stex. I'm staying with 2.6.19 in that case since it works fine in that
> version.
>
> So scsi bug ... 8-)
And you based that conclusion on what exactly?
--
Jens Axboe
next prev parent reply other threads:[~2007-08-29 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 17:50 2.6.22 oops kernel BUG at block/elevator.c:366! Arkadiusz Miskiewicz
2007-08-29 17:54 ` Jens Axboe
2007-08-29 18:04 ` Arkadiusz Miskiewicz
2007-08-29 18:08 ` Jens Axboe [this message]
2007-08-29 18:11 ` Arkadiusz Miskiewicz
2007-08-29 18:16 ` Jens Axboe
2007-08-30 11:29 ` Arkadiusz Miskiewicz
2007-09-10 9:17 ` Andrew Morton
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=20070829180800.GC7932@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=arekm@maven.pl \
--cc=linux-kernel@vger.kernel.org \
/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