mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* DMA errors, then I/O errors, on 2.6.16
@ 2006-05-27 21:07 Andrew Moise
  2006-05-27 21:18 ` Haar János
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: Andrew Moise @ 2006-05-27 21:07 UTC (permalink / raw)
  To: linux-kernel

  Running 2.6.16 (and some earlier 2.6 kernels as well), I get
occasional DMA failures, which are always followed by the disk not
working at all (any request leads to an I/O error).  The log and whatnot
follows.  Can anyone tell me what the source of this trouble might be
(disk, controller, cable, software)?
  Please CC replies to me, as I'm not on the list.  Thanks.

--- Log:

May 27 16:34:44 vino kernel: hda: dma_intr: status=0x7f { DriveReady DeviceFault
 SeekComplete DataRequest CorrectedError Index Error } 
May 27 16:34:44 vino kernel: hda: dma_intr: error=0x7f { DriveStatusError UncorrectableError SectorIdNotFound TrackZeroNotFound AddrMarkNotFound }, LBAsect=1495
68083689343, high=8914952, low=8355711, sector=356876123 
May 27 16:34:44 vino kernel: ide: failed opcode was: unknown 
May 27 16:34:44 vino kernel: hda: DMA disabled 
May 27 16:34:44 vino kernel: ide0: reset: master: error (0x0a?) 
May 27 16:34:44 vino kernel: hda: task_in_intr: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error } 
May 27 16:34:44 vino kernel: hda: task_in_intr: error=0x7f { DriveStatusError UncorrectableError SectorIdNotFound TrackZeroNotFound AddrMarkNotFound }, LBAsect=
149568083689343, high=8914952, low=8355711, sector=356876123 
May 27 16:34:44 vino kernel: ide: failed opcode was: unknown 
May 27 16:34:44 vino kernel: ide0: reset: master: error (0x0a?) 
May 27 16:34:44 vino kernel: end_request: I/O error, dev hda, sector 356876123 
May 27 16:34:44 vino kernel: end_request: I/O error, dev hda, sector 356876131 

  ... and so on, for many more I/O errors.

--- Version:

Linux version 2.6.16-1-486 (Debian 2.6.16-12) (waldi@debian.org) (gcc version 4.0.4 20060422 (prerelease) (Debian 4.0.3-2)) #2 Thu May 4 18:15:54 UTC 2006

--- Disk controller:

0000:00:11.1 IDE interface: VIA Technologies, Inc.  VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
        Subsystem: VIA Technologies, Inc.: Unknown device aa01
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32
        Interrupt: pin A routed to IRQ 11
        Region 4: I/O ports at e000 [size=16]
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: DMA errors, then I/O errors, on 2.6.16
  2006-05-27 21:07 DMA errors, then I/O errors, on 2.6.16 Andrew Moise
@ 2006-05-27 21:18 ` Haar János
  2006-05-27 21:54   ` Andrew Moise
  2006-05-27 21:20 ` Valdis.Kletnieks
  2006-05-28  8:33 ` Arjan van de Ven
  2 siblings, 1 reply; 5+ messages in thread
From: Haar János @ 2006-05-27 21:18 UTC (permalink / raw)
  To: Andrew Moise; +Cc: linux-kernel

Hi!

I am just a single user, but i have get this too earlier.

If it is a WD hdd, try to use master AND slave on the same cable, or try to
set "cable select" setting on hdd!

This works for me! ;-)

(Only WD made this for me, and only when it is a single master drive.)

Cheers,

Janos
----- Original Message ----- 
From: "Andrew Moise" <chops@demiurgestudios.com>
To: <linux-kernel@vger.kernel.org>
Sent: Saturday, May 27, 2006 11:07 PM
Subject: DMA errors, then I/O errors, on 2.6.16


>   Running 2.6.16 (and some earlier 2.6 kernels as well), I get
> occasional DMA failures, which are always followed by the disk not
> working at all (any request leads to an I/O error).  The log and whatnot
> follows.  Can anyone tell me what the source of this trouble might be
> (disk, controller, cable, software)?
>   Please CC replies to me, as I'm not on the list.  Thanks.
>
> --- Log:
>
> May 27 16:34:44 vino kernel: hda: dma_intr: status=0x7f { DriveReady
DeviceFault
>  SeekComplete DataRequest CorrectedError Index Error }
> May 27 16:34:44 vino kernel: hda: dma_intr: error=0x7f { DriveStatusError
UncorrectableError SectorIdNotFound TrackZeroNotFound AddrMarkNotFound },
LBAsect=1495
> 68083689343, high=8914952, low=8355711, sector=356876123
> May 27 16:34:44 vino kernel: ide: failed opcode was: unknown
> May 27 16:34:44 vino kernel: hda: DMA disabled
> May 27 16:34:44 vino kernel: ide0: reset: master: error (0x0a?)
> May 27 16:34:44 vino kernel: hda: task_in_intr: status=0x7f { DriveReady
DeviceFault SeekComplete DataRequest CorrectedError Index Error }
> May 27 16:34:44 vino kernel: hda: task_in_intr: error=0x7f {
DriveStatusError UncorrectableError SectorIdNotFound TrackZeroNotFound
AddrMarkNotFound }, LBAsect=
> 149568083689343, high=8914952, low=8355711, sector=356876123
> May 27 16:34:44 vino kernel: ide: failed opcode was: unknown
> May 27 16:34:44 vino kernel: ide0: reset: master: error (0x0a?)
> May 27 16:34:44 vino kernel: end_request: I/O error, dev hda, sector
356876123
> May 27 16:34:44 vino kernel: end_request: I/O error, dev hda, sector
356876131
>
>   ... and so on, for many more I/O errors.
>
> --- Version:
>
> Linux version 2.6.16-1-486 (Debian 2.6.16-12) (waldi@debian.org) (gcc
version 4.0.4 20060422 (prerelease) (Debian 4.0.3-2)) #2 Thu May 4 18:15:54
UTC 2006
>
> --- Disk controller:
>
> 0000:00:11.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a
[Master SecP PriP])
>         Subsystem: VIA Technologies, Inc.: Unknown device aa01
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
>         Latency: 32
>         Interrupt: pin A routed to IRQ 11
>         Region 4: I/O ports at e000 [size=16]
>         Capabilities: [c0] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: DMA errors, then I/O errors, on 2.6.16
  2006-05-27 21:07 DMA errors, then I/O errors, on 2.6.16 Andrew Moise
  2006-05-27 21:18 ` Haar János
@ 2006-05-27 21:20 ` Valdis.Kletnieks
  2006-05-28  8:33 ` Arjan van de Ven
  2 siblings, 0 replies; 5+ messages in thread
From: Valdis.Kletnieks @ 2006-05-27 21:20 UTC (permalink / raw)
  To: Andrew Moise; +Cc: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 429 bytes --]

On Sat, 27 May 2006 17:07:15 EDT, Andrew Moise said:
>   Running 2.6.16 (and some earlier 2.6 kernels as well), I get
> occasional DMA failures, which are always followed by the disk not
> working at all (any request leads to an I/O error).

Have you tried running 'badblocks /dev/hda' under a kernel that is
believe to be working?  That looks more like a drive trying to fail
due to hardware causes than a software problem.....

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: DMA errors, then I/O errors, on 2.6.16
  2006-05-27 21:18 ` Haar János
@ 2006-05-27 21:54   ` Andrew Moise
  0 siblings, 0 replies; 5+ messages in thread
From: Andrew Moise @ 2006-05-27 21:54 UTC (permalink / raw)
  To: Haar János; +Cc: linux-kernel

On Sat, May 27, 2006 at 11:18:47PM +0200, Haar János wrote:
> If it is a WD hdd, try to use master AND slave on the same cable, or try to
> set "cable select" setting on hdd!

  Sadly, it's a Maxtor drive, already set to cable select.  When I
opened the case to check the jumper, I noticed that the drive is very
hot; I tried improving the airflow to see if it's caused by the drive
overheating.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: DMA errors, then I/O errors, on 2.6.16
  2006-05-27 21:07 DMA errors, then I/O errors, on 2.6.16 Andrew Moise
  2006-05-27 21:18 ` Haar János
  2006-05-27 21:20 ` Valdis.Kletnieks
@ 2006-05-28  8:33 ` Arjan van de Ven
  2 siblings, 0 replies; 5+ messages in thread
From: Arjan van de Ven @ 2006-05-28  8:33 UTC (permalink / raw)
  To: Andrew Moise; +Cc: linux-kernel

On Sat, 2006-05-27 at 17:07 -0400, Andrew Moise wrote:
>   Running 2.6.16 (and some earlier 2.6 kernels as well), I get
> occasional DMA failures, which are always followed by the disk not
> working at all (any request leads to an I/O error).  The log and whatnot
> follows.  Can anyone tell me what the source of this trouble might be
> (disk, controller, cable, software)?
>   Please CC replies to me, as I'm not on the list.  Thanks.
> 
> --- Log:
> 
> May 27 16:34:44 vino kernel: hda: dma_intr: status=0x7f { DriveReady DeviceFault
>  SeekComplete DataRequest CorrectedError Index Error } 
> May 27 16:34:44 vino kernel: hda: dma_intr: error=0x7f { DriveStatusError UncorrectableError SectorIdNotFound TrackZeroNotFound AddrMarkNotFound }, LBAsect=1495
> 68083689343, high=8914952, low=8355711, sector=356876123 


this tends to be a disk dying.. better run smartctl to check it out...


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2006-05-28  8:33 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-05-27 21:07 DMA errors, then I/O errors, on 2.6.16 Andrew Moise
2006-05-27 21:18 ` Haar János
2006-05-27 21:54   ` Andrew Moise
2006-05-27 21:20 ` Valdis.Kletnieks
2006-05-28  8:33 ` Arjan van de Ven

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®