Bug#590105: Same problem on LS-WSGL
reopen 590105
thanks
Hi,
Contrary to what the bug title says, Sébastien didn't really want
support for LS-CHL at first, but rather fix its disks not being
recognized. As Antonios says, this disk controller problem also happen
on LS-WTGL, and I confirm it on LS-WSGL too (with the latest installer
from
http://people.debian.org/~joeyh/d-i/armel/images/daily/orion5x/network-console/buffalo/lspro/ with 2.6.37-1), both of which are supported by current (2.6.32) kernel, at least. So I am reopening this bug. If someone think a new bug should be opened, please tell me.
The relevant logs are (same on both .32 and .37):
[ 29.544309] sata_mv sata_mv.0: version 1.28
[ 29.549592] sata_mv sata_mv.0: slots 32 ports 2
[ 29.560892] scsi0 : sata_mv
[ 29.566986] scsi1 : sata_mv
[ 29.571302] ata1: SATA max UDMA/133 irq 29
[ 29.575414] ata2: SATA max UDMA/133 irq 29
[ 29.926337] ata1: SATA link down (SStatus 0 SControl 300)
[ 30.436355] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 30.476402] ata2.00: ATA-8: SAMSUNG HM500LI, 2TF00_00, max UDMA7
[ 30.482417] ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth
31/32)
[ 30.526422] ata2.00: configured for UDMA/133
[ 30.531398] scsi 1:0:0:0: Direct-Access ATA SAMSUNG HM500LI
2TF0 PQ: 0 ANSI: 5
[ 30.690100] sd 1:0:0:0: [sda] 976773168 512-byte logical blocks: (500
GB/465 GiB)
[ 30.702478] sd 1:0:0:0: [sda] Write Protect is off
[ 30.707342] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 30.707664] sd 1:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 31.218218] sda: sda1 sda2 sda4 < sda5 sda6 >
[ 31.229352] sd 1:0:0:0: [sda] Attached SCSI disk
[ 41.447884] ata2: exception Emask 0x10 SAct 0x0 SErr 0x180000 action
0x6 frozen
[ 41.447925] ata2: edma_err_cause=00000020 pp_flags=00000003,
SError=00180000
[ 41.447971] ata2: SError: { 10B8B Dispar }
[ 41.448031] ata2: hard resetting link
[ 41.796329] ata2: SATA link down (SStatus 0 SControl 300)
[ 46.796286] ata2: hard resetting link
[ 47.146330] ata2: SATA link down (SStatus 0 SControl 300)
[ 47.146389] ata2: limiting SATA link speed to 1.5 Gbps
[ 52.145849] ata2: hard resetting link
[ 52.496081] ata2: SATA link down (SStatus 0 SControl 310)
[ 52.496139] ata2.00: disabled
[ 52.496208] ata2: EH complete
[ 52.496270] ata2.00: detaching (SCSI 1:0:0:0)
[ 52.501243] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 52.519709] sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 52.519765] sd 1:0:0:0: [sda] Stopping disk
[ 52.519905] sd 1:0:0:0: [sda] START_STOP FAILED
[ 52.519934] sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
I read here http://marc.info/?l=linux-ide&m=129113801605282&w=3 that it
may be a timing issue. This is only a workaround I think, and this bug
should be properly fixed, but I think it may help for now. But I don't
know how to test that fix…
Regards,
benjamin
Reply to: