From: Jens Axboe <jens.axboe@oracle.com>
To: Flavio Curti <fcu@no-way.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Flavio Curti <lists.fcu@no-way.org>,
linux-kernel@vger.kernel.org, promise_linux@promise.com
Subject: Re: panics with 16port Promise Supertrack EX Controller
Date: Mon, 16 Jul 2007 13:17:49 +0200 [thread overview]
Message-ID: <20070716111749.GE5195@kernel.dk> (raw)
In-Reply-To: <20070715080209.GC21260@no-way.org>
On Sun, Jul 15 2007, Flavio Curti wrote:
> Hello
>
> On Mon, Jul 09, 2007 at 11:59:36AM +1000, Nick Piggin wrote:
> > >Jul 8 00:19:13 dorade.cyberlink.ch EFLAGS: 00210046
> > >(2.6.22-rc7-dorade #1)
> > >>The machine panics
> > >>after some days of running fine, the machine inst heavy loaded.
> > >>The Controller detects as stex device:
> > >kernel BUG at block/as-iosched.c:1084!
> > >
> > >BUG_ON(RB_EMPTY_ROOT(&ad->sort_list[REQ_ASYNC]));
> > Could be a bug in the driver that just happens to be caught by AS checks.
> > If you could test another scheduler (boot with elevator=deadline or
> > elevator=cfq),
> > it might help give us an idea.
>
> Ok, I now switched to cfg, and the machine panicd again. Panic attached.
> Any help is appreciated.
It really looks like a stex bug - perhaps it's doing double completions
of a request?
--
Jens Axboe
next prev parent reply other threads:[~2007-07-16 11:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 22:52 panics with 16port Promise Supertrack EX Controller Flavio Curti
2007-07-08 23:20 ` Michal Piotrowski
2007-07-09 1:59 ` Nick Piggin
2007-07-15 8:02 ` Flavio Curti
2007-07-16 11:17 ` Jens Axboe [this message]
2007-07-15 22:51 ` Flavio Curti
2007-07-16 0:35 ` Randy Dunlap
2007-07-16 8:50 ` Flavio Curti
2007-07-09 10:45 ` Flavio Curti
-- strict thread matches above, loose matches on Subject: below --
2007-07-17 1:26 Ed Lin
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=20070716111749.GE5195@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=fcu@no-way.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists.fcu@no-way.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=nickpiggin@yahoo.com.au \
--cc=promise_linux@promise.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