Re: [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup/ early userspace transition

From: Bernd Schubert
Date: Tue Jul 30 2013 - 14:10:07 EST

On 07/30/2013 01:34 AM, Martin K. Petersen wrote:
"Nix" == Nix <nix@xxxxxxxxxxxxx> writes:


Nix> I can now confirm that reverting this commit causes this problem to
Nix> go away, and my machine boots fine again.

Can you please send me the output of sq_inq with your 1.49 firmware?

I made a tweak that allowed Nix to boot but we're trying to find a good
blacklist trigger. And that's tricky given that Areca allows you
manually specify the SCSI model string for each volume...

Sorry it got a bit late today.

Here it is.

(wheezy)fslab1:~# sg_inq -v /dev/sdc
inquiry cdb: 12 00 00 00 24 00
standard INQUIRY:
inquiry cdb: 12 00 00 00 60 00
PQual=0 Device_type=0 RMB=0 version=0x05 [SPC-3]
[AERC=0] [TrmTsk=0] NormACA=0 HiSUP=0 Resp_data_format=2
SCCS=0 ACC=0 TPGS=0 3PC=0 Protect=0 BQue=0
EncServ=0 MultiP=0 [MChngr=0] [ACKREQQ=0] Addr16=1
[RelAdr=0] WBus16=1 Sync=0 Linked=0 [TranDis=0] CmdQue=1
[SPI: Clocking=0x3 QAS=0 IUS=0]
length=96 (0x60) Peripheral device type: disk
Vendor identification: Hitachi
Product identification: HDS724040KLSA80
Product revision level: R001
inquiry cdb: 12 01 00 00 fc 00
inquiry cdb: 12 01 80 00 fc 00
Unit serial number: KRFS2CRAHXJZVD

Besides the firmware, the difference might be that I'm exporting single disks without any areca-raidset in between.
I can try to confirm that tomorrow, I just need the system as it is till tomorrow noon.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at