[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4611EADC.3000306@suse.de>
Date: Tue, 03 Apr 2007 14:49:16 +0900
From: Tejun Heo <teheo@...e.de>
To: linux@...izon.com
CC: 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
[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).
> > (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.
Thanks.
--
tejun
-
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