From: Flavio Curti <lists.fcu@no-way.org>
To: linux-kernel@vger.kernel.org
Subject: Re: panics with 16port Promise Supertrack EX Controller
Date: Mon, 16 Jul 2007 00:51:55 +0200 [thread overview]
Message-ID: <20070715225155.GD21260@no-way.org> (raw)
In-Reply-To: <46919688.1050005@yahoo.com.au>
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
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.
Flavio Curti
--
http://no-way.org/~fcu/
[-- Attachment #2: dorade-kdump --]
[-- Type: text/plain, Size: 1485 bytes --]
blk_queue_end_tag: attempt to clear non-busy tag (1)
------------[ cut here ]------------
kernel BUG at block/ll_rw_blk.c:2758!
invalid opcode: 0000 [#1]
SMP
Modules linked in:
i2c_i801
i2c_core
CPU: 0
EIP: 0060:[<c02a3164>] Not tainted VLI
EFLAGS: 00010002 (2.6.22.1-dorade #1)
EIP is at __blk_put_request+0x74/0x80
eax: 00000000 ebx: dae3e578 ecx: c02ac600 edx: 00000000
esi: 00030784 edi: f7f28b24 ebp: f7f28b24 esp: c0621e50
ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068
Process swapper (pid: 0, ti=c0620000 task=c05d8340 task.ti=c0620000)
Stack:
dae3e578
e2b5aac0
00000001
scsi_end_request+0x94/0xe0
[<c03743c6>]
scsi_io_completion+0x86/0x3e0
[<c012b08a>]
del_timer+0x5a/0x70
[<c038fc7b>]
sd_rw_intr+0x2b/0x200
[<c038bf8e>]
stex_mu_intr+0x12e/0x540
[<c036fe85>]
scsi_finish_command+0x45/0x60
[<c02a4c88>]
blk_done_softirq+0x58/0x70
[<c0126e92>]
__do_softirq+0x82/0x100
[<c0126f47>]
do_softirq+0x37/0x40
[<c0127185>]
irq_exit+0x75/0x80
[<c0106410>]
do_IRQ+0x40/0x80
[<c0139796>]
getnstimeofday+0x36/0xd0
[<c0104503>]
common_interrupt+0x23/0x28
[<c0101d26>]
mwait_idle_with_hints+0x46/0x60
[<c0101e85>]
cpu_idle+0x65/0x90
[<c0628d1f>]
start_kernel+0x2ef/0x370
[<c06284e0>]
unknown_bootoption+0x0/0x250
=======================
Code:
8b
57
24
89
d8
83
e6
01
e8
ca
1b
eb
ff
89
f2
89
f8
89
e9
5b
5e
5f
5d
e9
3b
ff
last message repeated 2 times
89
da
89
next prev parent reply other threads:[~2007-07-15 22:52 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
2007-07-15 22:51 ` Flavio Curti [this message]
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=20070715225155.GD21260@no-way.org \
--to=lists.fcu@no-way.org \
--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