linux-kernel - Re: panics with 16port Promise Supertrack EX Controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070716111749.GE5195@kernel.dk>
Date:	Mon, 16 Jul 2007 13:17:49 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Flavio Curti <fcu@...way.org>
Cc:	Nick Piggin <nickpiggin@...oo.com.au>,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Flavio Curti <lists.fcu@...way.org>,
	linux-kernel@...r.kernel.org, promise_linux@...mise.com
Subject: Re: panics with 16port Promise Supertrack EX Controller

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/