LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Tejun Heo <teheo@suse.de>
To: linux@horizon.com
Cc: dan.j.williams@intel.com, linux-ide@vger.kernel.org,
neilb@suse.de, cebbert@redhat.com, jens.axboe@oracle.com,
linux-kernel@dale.us, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: Re: 2.6.20.3 AMD64 oops in CFQ code
Date: Tue, 03 Apr 2007 14:49:16 +0900 [thread overview]
Message-ID: <4611EADC.3000306@suse.de> (raw)
In-Reply-To: <20070323174630.31051.qmail@science.horizon.com>
[resending. my mail service was down for more than a week and this
message didn't get delivered.]
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).
> > (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
next prev parent reply other threads:[~2007-04-03 5:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 12:38 linux
2007-03-22 18:41 ` Jens Axboe
2007-03-22 18:54 ` linux
2007-03-22 19:00 ` Jens Axboe
2007-03-22 23:59 ` Neil Brown
2007-03-23 0:31 ` Dan Williams
2007-03-23 0:33 ` Dan Williams
2007-03-23 0:44 ` Neil Brown
2007-03-23 17:46 ` linux
2007-04-03 5:49 ` Tejun Heo [this message]
2007-04-03 13:03 ` linux
2007-04-03 13:11 ` Tejun Heo
2007-04-04 23:22 ` Bill Davidsen
2007-04-05 4:13 ` Lee Revell
2007-04-05 4:29 ` Tejun Heo
2007-03-22 18:43 ` Aristeu Sergio Rozanski Filho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4611EADC.3000306@suse.de \
--to=teheo@suse.de \
--cc=cebbert@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@dale.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux@horizon.com \
--cc=neilb@suse.de \
--subject='Re: 2.6.20.3 AMD64 oops in CFQ code' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).