Re: 2.6.20.3 AMD64 oops in CFQ code

Tejun Heo
2007-04-03T13:12:27Z

linux@horizon.com wrote:
> linux@horizon.com wrote:
>>> Anyway, what's annoying is that I can't figure out how to bring the
>>> drive back on line without resetting the box. It's in a hot-swap enclosure,
>>> but power cycling the drive doesn't seem to help. I thought libata hotplug
>>> was working? (SiI3132 card, using the sil24 driver.)
>
>> Yeah, it's working but failing resets are considered highly dangerous
>> (in that the controller status is unknown and may cause something
>> dangerous like screaming interrupts) and port is muted after that. The
>> plan is to handle this with polling hotplug such that libata tries to
>> revive the port if PHY status change is detected by polling. Patches
>> are available but they need other things to resolved to get integrated.
>> I think it'll happen before the summer.
>
>> Anyways, you can tell libata to retry the port by manually telling it to
>> rescan the port (echo - - - > /sys/class/scsi_host/hostX/scan).
>
> Ah, thank you! I have to admit, that is at least as mysterious as any
> Microsoft registry tweak.

Polling hotplug should fix this. I thought I would be able to merge it
much earlier. I apparently was way too optimistic. :-(

>>> (H'm... after rebooting, reallocated sectors jumped from 26 to 39.
>>> Something is up with that drive.)
>
>> Yeap, seems like a broken drive to me.
>
> Actually, after a few rounds, the reallocated sectors stabilized at 56
> and all is working well again. It's like there was a major problem with
> error handling.
>
> The problem is that I don't know where the blame lies.

I'm pretty sure it's the firmware's fault. It's not supposed to go out
for lunch like that even when internal error occurs.

--
tejun