Re: panics with 16port Promise Supertrack EX Controller

[Nick Piggin]

Michal Piotrowski wrote:
> Hi Flavio,
>
> On 09/07/07, Flavio Curti <lists.fcu@xxxxxxxxxx> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/