Hi I just returned that machine as more issues unrelated to the raid-controller started to appear. There is probably some hardware fault. I'll report back once I get it back and if the problems persist Thanks Benjamin Mr. James W. Laferriere wrote: > On Fri, 5 Jun 2009, James Bottomley wrote: >> On Fri, 2009-06-05 at 16:19 +0200, Benjamin Schindler wrote: >>> Hi >>> (I'm not subscribed to this list, so please cc me) >>> >>> I tried to install gentoo linux on a areca ARC-1210 raid controller, >>> but >>> I'm having serious issues. The problem start on more heavy I/O with: >>> >>> arcmsr6: abort device command of scsi id = 0 lun = 0 >>> >>> From this point, the system has serious issues. With xfs for example, >>> the following happens: >>> >>> arcmsr6: abort device command of scsi id = 0 lun = 0 >> >> This is an abort, likely triggered by a timeout. >> >>> sd 6:0:0:0: [sda] Result: hostbyte=DID_OK >>> driverbyte=DRIVER_TIMEOUT,SUGGEST_OK >> >> This looks very suggestive, nothing in the arcmsr ... or indeed any >> driver ever sets DRIVER_TIMEOUT ... it looks like a mangled result code >> somehow. It definitely lead to the resulting failure. >> >> Cc:ing Areca people to see if they have any idea. >> >> James > > I am QUITE sure the .config as shown did not create the kernel > messages as shown . One does have to enable the 'CONFIG_FUSION' in > order to use it . > > ... Snipped to show context . > >>> Fusion MPT base driver 3.04.07 > > ... Snipped to show context . > >>> Copyright (c) 1999-2008 LSI Corporation >>> sda1 sda2 >>> sd 6:0:0:0: [sda] Attached SCSI disk >>> sd 6:0:0:0: Attached scsi generic sg1 type 0 >>> scsi 6:0:16:0: Attached scsi generic sg2 type 3 >>> Fusion MPT SPI Host driver 3.04.07 >>> Fusion MPT FC Host driver 3.04.07 >>> Fusion MPT SAS Host driver 3.04.07 > > ... Snipped to show context . > >>> # CONFIG_FUSION is not set > > ... Snipped to show context . > > Hth , JimL -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
