mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: zine el abidine Hamid <zine46@yahoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Detecting I/O error and Halting System
Date: Mon, 27 Mar 2006 17:55:56 +0100	[thread overview]
Message-ID: <1143478556.4970.37.camel@localhost.localdomain> (raw)
In-Reply-To: <20060327145501.34766.qmail@web30606.mail.mud.yahoo.com>

On Llu, 2006-03-27 at 16:55 +0200, zine el abidine Hamid wrote:
> hda: status timeout: status=0xd0 { Busy }      adapter
> disque annonce un status busy du DMA

If I'm reading the translation right then your hard disk decided
it was busy and then never came back

> Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel:
> ide0: reset: success             

So the IDE layer tried to reset it

> Feb 12 10:22:38 porte_de_clignancourt_nds_b kernel:
> hda: timeout waiting for DMA

Which didnt help

> Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
> ide0: reset: success

Still trying
      
> Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
> hda: irq timeout: status=0xd0 { Busy }                
> 
> Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
> hda: DMA disabled       

We gave up on DMA to see if PIO would help
>                               
>    
> Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
> ide0: reset timed-out, status=0x80
> Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
> hda: status timeout: status=0x80 { Busy }        
> nouvel échec de reset
> Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
> hda: drive not ready for command
> Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
> ide0: reset: success                  

And reset.. 


> Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
> hda: status timeout: status=0x80 { Busy }
> Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
> hda: drive not ready for command
> Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
> ide0: reset timed-out, status=0x80
> Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
> end_request: I/O error, dev 03:02 (hda), sector 102263
> Feb 12 13:45:38 porte_de_clignancourt_nds_b syslogd:
> /var/log/maillog: Input/output error
> Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
> end_request: I/O error, dev 03:02 (hda), sector 110720
> Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
> end_request: I/O error, dev 03:02 (hda), sector 110728 

Eventually we give up.


First thing to check would be the disk and the temperature, then the
cabling. In particular make sure the *long* part of the cable is between
the drive and the controller.


  parent reply	other threads:[~2006-03-27 16:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27 14:55 zine el abidine Hamid
2006-03-27 15:24 ` linux-os (Dick Johnson)
2006-03-27 16:55 ` Alan Cox [this message]
2006-03-28 15:07   ` zine el abidine Hamid
2006-03-28 15:36     ` Alan Cox
2006-03-30 12:28       ` Bernd Eckenfels
2006-04-02 22:51         ` zine el abidine Hamid
2006-04-02 22:31       ` zine el abidine Hamid
2006-03-28 17:55     ` Gene Heskett
2006-03-30  8:14       ` zine el abidine Hamid

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=1143478556.4970.37.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zine46@yahoo.fr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®