hello
I have a problem with a serial ata controller
that uses a SiI 3512 chip.
when I'm trying to add a device thats on the 3512 controller
to the array that I have, it give me lots of errors in dmesg
like this:
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x0
ata3.00: BMDMA2 stat 0x8652001
ata3.00: cmd 35/00:80:3f:5c:03/00:02:00:00:00/e0 tag 0 cdb 0x0 data 327680
out
res 51/04:80:3f:5e:03/00:00:00:00:00/e0 Emask 0x1 (device error)
ata3.00: configured for UDMA/100
ata3: EH complete
sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x2 frozen
ata3.00: cmd 35/00:80:bf:75:03/00:02:00:00:00/e0 tag 0 cdb 0x0 data 327680
out
res 40/00:80:3f:5e:03/00:00:00:00:00/e0 Emask 0x4 (timeout)
ata3: port is slow to respond, please be patient (Status 0xd1)
ata3: device not ready (errno=-16), forcing hardreset
ata3: hard resetting port
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata3.00: configured for UDMA/100
...........
is this a bug, is there a patch, or a workaround ?
I desperately need to grow the array (which is a raid5) with
the new harddrives :(
10x for help
--
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
