All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Burgess <kernel@corrosive.freeserve.co.uk>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: IDE Problems on SIS 735? (continued)
Date: Sun, 9 Sep 2001 21:49:00 +0100	[thread overview]
Message-ID: <20010909214900.A1135@corrosive.freeserve.co.uk> (raw)
In-Reply-To: <20010905085251.A3154@corrosive.freeserve.co.uk> <E15ebN4-0005g4-00@the-village.bc.nu> <20010905185946.A6828@corrosive.freeserve.co.uk>
In-Reply-To: <20010905185946.A6828@corrosive.freeserve.co.uk>

Okay, I've now changed the IDE cable attached to my hard drives twice, and I'm
still getting IDE DMA problems - has anyone else with a SIS 735 based
motherboard been having any problems, because I'm running short of ideas?
Also - what are the chances of data corruption from these errors?
Thanks,
Adrian.


(error report)
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: drive not ready for command
hda: status timeout: status=0xd0 { Busy }
hdb: DMA disabled
hda: drive not ready for command
ide0: reset: success

-- 
PGP Public Key at http://www.corrosive.freeserve.co.uk/text/pubkey.asc

  reply	other threads:[~2001-09-09 20:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05  7:52 IDE Problems on SIS 735? kernel
2001-09-05 12:01 ` Alan Cox
2001-09-05 17:59   ` Adrian Burgess
2001-09-09 20:49     ` Adrian Burgess [this message]
2001-09-11  4:03       ` IDE Problems on SIS 735? (continued) Matthew S. Hallacy

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=20010909214900.A1135@corrosive.freeserve.co.uk \
    --to=kernel@corrosive.freeserve.co.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.