From: Robert Hancock <hancockrwd@gmail.com>
To: Simon Li <simon.jiyou@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>, Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org
Subject: Re: Pls help for LibATA caused kernel temporary hung.
Date: Mon, 28 Jun 2010 23:11:19 -0600 [thread overview]
Message-ID: <4C298077.6070102@gmail.com> (raw)
In-Reply-To: <AANLkTikwbBANkzepCW1XwbfSi3vvuq8iJNtG0WAZByDV@mail.gmail.com>
On 06/28/2010 03:09 AM, Simon Li wrote:
> We don't expect kernel goes to temporary hung, any ideas for the fix?
It depends what you mean by hanging. Usually if a drive is stuck trying
to read a bad sector it will take quite a while before it gives up, and
during that period all disk access is stalled. The kernel normally
retries several times as well. If a bunch of applications are needing to
access the disk, they'll appear to be hung up during this process.
>
>
> On Mon, Jun 28, 2010 at 5:02 PM, Jeff Garzik<jeff@garzik.org> wrote:
>> On 06/28/2010 03:38 AM, Simon Li wrote:
>>>
>>> May 25 15:55:06 shctc-xq-ems22-me18 kernel: ata3: status=0x25 {
>>> DeviceFault CorrectedError Error }
>>
>>> May 25 15:59:59 shctc-xq-ems22-me18 kernel: ata3: status=0x25 {
>>> DeviceFault CorrectedError Error }
>>
>>> Jun 2 10:54:06 shctc-xm-ems21-me18 kernel: ata2: status=0x25 {
>>> DeviceFault CorrectedError Error }
>>
>>> Jun 2 10:54:08 shctc-xm-ems21-me18 kernel: ata2: status=0x25 {
>>> DeviceFault CorrectedError Error }
>>
>>> Jun 2 10:54:18 shctc-xm-ems21-me18 kernel: ata2: status=0x25 {
>>> DeviceFault CorrectedError Error }
>>
>> Your hardware is returning errors, which libata is dutifully reporting...
>>
>> Jeff
>>
>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-06-29 5:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinbQHdo40Drqc5Ydur5lCrAktHHDig45HDrC6s1@mail.gmail.com>
[not found] ` <4C2777D3.1050208@gmail.com>
2010-06-28 7:38 ` Pls help for LibATA caused kernel temporary hung Simon Li
2010-06-28 9:02 ` Jeff Garzik
2010-06-28 9:09 ` Simon Li
2010-06-29 1:36 ` Marek Vasut
2010-06-29 5:11 ` Robert Hancock [this message]
2010-06-29 7:10 ` Simon Li
2010-06-29 7:20 ` Tejun Heo
2010-06-29 7:27 ` Simon Li
2010-06-29 7:29 ` Tejun Heo
[not found] ` <AANLkTinYbtr1qBLibK7wYizCDq8V0HwFu01NUr-f_KfR@mail.gmail.com>
2010-06-30 0:38 ` Robert Hancock
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=4C298077.6070102@gmail.com \
--to=hancockrwd@gmail.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=simon.jiyou@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.