From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Flavio Curti <lists.fcu@no-way.org>,
linux-kernel@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: panics with 16port Promise Supertrack EX Controller
Date: Mon, 09 Jul 2007 11:59:36 +1000 [thread overview]
Message-ID: <46919688.1050005@yahoo.com.au> (raw)
In-Reply-To: <6bffcb0e0707081620pf4afd46re9e74e18518b352a@mail.gmail.com>
Michal Piotrowski wrote:
> Hi Flavio,
>
> On 09/07/07, Flavio Curti <lists.fcu@no-way.org> wrote:
>
>> Hello
>>
>> I have a problem with a server running 2.6.22rc4.
>
>
> Jul 8 00:19:13 dorade.cyberlink.ch EFLAGS: 00210046
> (2.6.22-rc7-dorade #1)
>
> Is this a regression?
>
>> The machine panics
>> after some days of running fine, the machine inst heavy loaded.
>>
>> The Controller detects as stex device:
>>
>> scsi0 : stex
>> scsi 0:0:0:0: Direct-Access Promise 1X2 Mirror 1.10 PQ: 0 ANSI: 3
>> scsi 0:0:2:0: Direct-Access Promise 12+2 Disk RAID6 1.10 PQ: 0 ANSI: 3
>> scsi 0:0:16:0: Processor Promise RAID Console 1.00 PQ: 0 ANSI: 3
>> sd 0:0:0:0: [sda] 976642048 512-byte hardware sectors (500041 MB)
>> sd 0:0:0:0: [sda] Write Protect is off
>> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
>> support DPO or FUA
>> sd 0:0:0:0: [sda] 976642048 512-byte hardware sectors (500041 MB)
>> sd 0:0:0:0: [sda] Write Protect is off
>> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
>> support DPO or FUA
>> sda: sda1 sda2
>> sd 0:0:0:0: [sda] Attached SCSI disk
>> sd 0:0:2:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
>> sd 0:0:2:0: [sdb] 11719704576 512-byte hardware sectors (6000489 MB)
>> sd 0:0:2:0: [sdb] Write Protect is off
>> sd 0:0:2:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
>> support DPO or FUA
>> sd 0:0:2:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
>> sd 0:0:2:0: [sdb] 11719704576 512-byte hardware sectors (6000489 MB)
>> sd 0:0:2:0: [sdb] Write Protect is off
>> sd 0:0:2:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
>> support DPO or FUA
>> sdb: sdb1
>> sd 0:0:2:0: [sdb] Attached SCSI disk
>> sd 0:0:0:0: Attached scsi generic sg0 type 0
>> sd 0:0:2:0: Attached scsi generic sg1 type 0
>> scsi 0:0:16:0: Attached scsi generic sg2 type 3
>>
>> Im not sure where the problem is (controller/lvm/ext3), so if anyone has
>> an idea, Im happy to try it out...
>
>
> 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.
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2007-07-09 1:59 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 [this message]
2007-07-15 8:02 ` Flavio Curti
2007-07-16 11:17 ` Jens Axboe
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=46919688.1050005@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists.fcu@no-way.org \
--cc=michal.k.k.piotrowski@gmail.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