[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 04 Apr 2007 19:22:32 -0400
From: Bill Davidsen <davidsen@....com>
To: Tejun Heo <teheo@...e.de>
CC: linux@...izon.com, dan.j.williams@...el.com,
linux-ide@...r.kernel.org, neilb@...e.de, cebbert@...hat.com,
jens.axboe@...cle.com, linux-kernel@...e.us,
linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org
Subject: Re: 2.6.20.3 AMD64 oops in CFQ code
Tejun Heo wrote:
> [resending. my mail service was down for more than a week and this
> message didn't get delivered.]
>
> linux@...izon.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).
>
I won't say that's voodoo, but if I ever did it I'd wipe down my
keyboard with holy water afterward. ;-)
Well, I did save the message in my tricks file, but it sounds like a
last ditch effort after something get very wrong.
--
bill davidsen <davidsen@....com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists