public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <kernel@nn7.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: hda: DMA timeout error
Date: Tue, 10 Oct 2006 16:46:38 +0000	[thread overview]
Message-ID: <1160498799.24402.99.camel@localhost> (raw)

Dear List,

could someone knowledgeable please comment on this ?

I had a working raid-1 setup(tm) with two western digital drives being
connected to a via and a highpoint controller. Now all I did is to
replace ide disks (now hitachi) and suddenly I frequently see disks (on
one of the controllers, sometimes hda sometimes hde) to plop out:

hda: lost interrupt
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }
ide: failed opcode was: unknown
raid1: Disk failure on hda, disabling device. 
        Operation continuing on 1 devices
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }
ide: failed opcode was: unknown
RAID1 conf printout:
 --- wd:1 rd:2
 disk 0, wo:1, o:0, dev:hda
 disk 1, wo:0, o:1, dev:hde
RAID1 conf printout:
 --- wd:1 rd:2
 disk 1, wo:0, o:1, dev:hde

I simply don't understand what's wrong ... when I hot remove the drive
turn on DMA and hot add the drive everything is fine again ... could one
increase timeouts or try some more mature driver which has some more
error recovery ? This is on kernel 2.6.17.13 ... 2.6.18 refuses to boot
(kills the hotplug process repeatedly claiming the machine ran out of
memory).

Any thoughts ?
Soeren
-- 
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962

                 reply	other threads:[~2006-10-11  8:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1160498799.24402.99.camel@localhost \
    --to=kernel@nn7.de \
    --cc=linux-kernel@vger.kernel.org \
    /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