From: "Matthew S. Hallacy" <poptix@techmonkeys.org>
To: Adrian Burgess <kernel@corrosive.freeserve.co.uk>
Subject: Re: IDE Problems on SIS 735? (continued)
Date: Mon, 10 Sep 2001 22:03:10 -0600 [thread overview]
Message-ID: <20010910220310.C8597@techmonkeys.org> (raw)
In-Reply-To: <20010905085251.A3154@corrosive.freeserve.co.uk> <E15ebN4-0005g4-00@the-village.bc.nu> <20010905185946.A6828@corrosive.freeserve.co.uk> <20010909214900.A1135@corrosive.freeserve.co.uk>
In-Reply-To: <20010909214900.A1135@corrosive.freeserve.co.uk>; from kernel@corrosive.freeserve.co.uk on Sun, Sep 09, 2001 at 09:49:00PM +0100
On Sun, Sep 09, 2001 at 09:49:00PM +0100, Adrian Burgess wrote:
> 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.
>
I'm using the SiS 735 motherboard with ATA/100 IDE, I have an Quantum Bigfoot 8.1G drive,
along with two 45G IBM DTLA drives (ATA/100) on controller, I've had no problems beyond
some clicking on one of the IBM drives that also happens on a Promise PCI controller
(no messages to syslog about it, and S.M.A.R.T. reports no errors (I use smartctl))
2.4.9 kernel..
Matthew S. Hallacy
>
> (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
prev parent reply other threads:[~2001-09-11 4:04 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 ` IDE Problems on SIS 735? (continued) Adrian Burgess
2001-09-11 4:03 ` Matthew S. Hallacy [this message]
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=20010910220310.C8597@techmonkeys.org \
--to=poptix@techmonkeys.org \
--cc=kernel@corrosive.freeserve.co.uk \
/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