Bug#671689: [regression 3.2->3.3.4] sata_sil (on sil 3512) hotplug broken again
Hi,
sorry that it took so long, but now I have the time to test the
hotplugging with a kernel >= 3.3 :)
dmesg logs directly pasted here. So first, booted with powered down
esata enclosure and now, poweron:
[36997.268364] ata5: exception Emask 0x10 SAct 0x0 SErr 0x50000 action
0xe frozen
[36997.268370] ata5: SError: { PHYRdyChg CommWake }
[36997.268383] ata5: hard resetting link
[37003.032028] ata5: link is slow to respond, please be patient (ready=-19)
[37003.088037] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[37003.112203] ata5.00: ATA-8: VB0250EAVER, HPG0, max UDMA/100
[37003.112206] ata5.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[37003.128213] ata5.00: configured for UDMA/100
[37003.128225] ata5: EH complete
[37003.128354] scsi 4:0:0:0: Direct-Access ATA VB0250EAVER
HPG0 PQ: 0 ANSI: 5
[37003.128550] sd 4:0:0:0: [sdg] 488397168 512-byte logical blocks: (250
GB/232 GiB)
[37003.128597] sd 4:0:0:0: [sdg] Write Protect is off
[37003.128599] sd 4:0:0:0: [sdg] Mode Sense: 00 3a 00 00
[37003.128620] sd 4:0:0:0: [sdg] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[37003.151147] sdg: sdg1
[37003.151688] sd 4:0:0:0: [sdg] Attached SCSI disk
Disk works.
[37339.909515] Btrfs loaded
[37339.921542] device label hp_VB0250EAVER devid 1 transid 107
/dev/mapper/udisks-luks-uuid-23ee789a-0138-4799-81a8-a7286119b712-uid1000
[37339.922224] btrfs: disk space caching is enabled
mounted.... and umount again, now powerdown.
[37437.877977] ata5: exception Emask 0x10 SAct 0x0 SErr 0x10000 action
0xe frozen
[37437.877982] ata5: SError: { PHYRdyChg }
[37437.877995] ata5: hard resetting link
[37438.600030] ata5: SATA link down (SStatus 0 SControl 310)
[37443.604027] ata5: hard resetting link
[37443.924127] ata5: SATA link down (SStatus 0 SControl 310)
[37448.924580] ata5: hard resetting link
[37449.244032] ata5: SATA link down (SStatus 0 SControl 310)
[37449.244043] ata5.00: disabled
[37449.244053] ata5: EH complete
[37449.244062] ata5.00: detaching (SCSI 4:0:0:0)
[37449.245755] sd 4:0:0:0: [sdg] Synchronizing SCSI cache
[37449.245788] sd 4:0:0:0: [sdg] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[37449.245792] sd 4:0:0:0: [sdg] Stopping disk
[37449.245800] sd 4:0:0:0: [sdg] START_STOP FAILED
[37449.245802] sd 4:0:0:0: [sdg] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
Drive gone... now, power-up again.
adrastea:~# dmesg
adrastea:~#
Nothing. I did clear the kernel-message log in between... so module
modprobe-cycling...
[38290.316274] sata_sil 0000:01:01.0: version 2.4
[38290.319815] scsi7 : sata_sil
[38290.319986] scsi8 : sata_sil
[38290.320067] ata7: SATA max UDMA/100 mmio m512@0xbbeffc00 tf
0xbbeffc80 irq 21
[38290.320071] ata8: SATA max UDMA/100 mmio m512@0xbbeffc00 tf
0xbbeffcc0 irq 21
[38290.640039] ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[38290.648208] ata7.00: ATA-8: VB0250EAVER, HPG0, max UDMA/100
[38290.648213] ata7.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[38290.664207] ata7.00: configured for UDMA/100
[38290.664381] scsi 7:0:0:0: Direct-Access ATA VB0250EAVER
HPG0 PQ: 0 ANSI: 5
[38290.664619] sd 7:0:0:0: [sdg] 488397168 512-byte logical blocks: (250
GB/232 GiB)
[38290.664678] sd 7:0:0:0: [sdg] Write Protect is off
[38290.664682] sd 7:0:0:0: [sdg] Mode Sense: 00 3a 00 00
[38290.664709] sd 7:0:0:0: [sdg] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[38290.674683] sdg: sdg1
[38290.674996] sd 7:0:0:0: [sdg] Attached SCSI disk
[38290.984031] ata8: SATA link down (SStatus 0 SControl 310)
and the drve is back. So first, the modprobe-cycling does work with the
neweset kernel 3.3. I guess there was some other hickup the last time
that did prevent the module unloading. But the thing with "notswap
broken" is definitely there. It works only ONE time and all subsequent
hotplug (powerdown or disk pluggin, tested both at least 5 times in a
row, two test-lines, with modprobe-cycling in between) events get ignored.
Running 3.3.0-trunk-686-pae (3.3-1~experimental.1) right now. Oops,
testing with 3.3.4-1~experimental.1 now, but I am sure it will happen
there as well. I will report back after the next reboot. :)
regards
Michael
Reply to: