From: Michael Frank <mhf@linuxmail.org>
To: M?ns Rullg?rd <mru@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: [BUG?] SIS IDE DMA errors
Date: Thu, 2 Oct 2003 08:32:43 +0800 [thread overview]
Message-ID: <200310020832.43330.mhf@linuxmail.org> (raw)
In-Reply-To: <20030929100130.GA9322@ucw.cz>
On Monday 29 September 2003 18:01, Vojtech Pavlik wrote:
> On Mon, Sep 29, 2003 at 11:22:28AM +0200, M?ns Rullg?rd wrote:
>
> > > 08 - 80-wire cables (needed for UDMA44 and higher) NOT installed.
> > > FIFO threshold set to 3/4 for read and to 1/4 for write.
> > >
> > > 01 - IDE controller in compatibility mode. Native and test modes
> > > disabled. (normal)
> > >
> > > e6 - PCI burst enable, EDB R-R pipeline enable, Fast postwrite enable,
> > > device ID masqueraded as sis5513 (although real is 5517)
> > > channels 0 and 1 enabled in normal mode
> > >
> > > 51 - Postwrite enabled on hda and hdc, prefetch on hda only
> > >
> > > 00 02 - 512 bytes prefetch size for hda
> > > 00 02 - 512 bytes prefetch size for hdc
> > >
> > > All this is OK, possibly except for the 80-wire cable not being present,
> > > but if this is a notebook, there might be a completely different cable
> > > type than what's standard, and the detection might not work there.
> >
> > I've got no idea what the cable is like. Is there anything to be
> > learned from opening the beast? Anything in particular to look for?
>
Notebook drive is plugged streight into a circuit board or connected by a
short cable. The unlikely possibility for hardware is that it is out of spec
and it also could be the drive.
IBM/Hitachi have standalone PCDOS diagnostic floppy disk images and IIRC some
linux based stuff for their drives on their support website. You could run
this diagnostics and see if you learn more.
BTW, as it is in a way an interrupt problem - you tried wo ACPI and IIRC,
you have no APIC?
Regards
Michael
next prev parent reply other threads:[~2003-10-02 0:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 12:30 [BUG?] SIS IDE DMA errors Måns Rullgård
2003-09-26 14:08 ` Michael Frank
2003-09-26 14:07 ` Måns Rullgård
2003-09-26 15:32 ` Michael Frank
2003-09-26 15:38 ` Måns Rullgård
2003-09-26 19:44 ` Michael Frank
2003-09-29 9:23 ` Måns Rullgård
2003-09-29 13:12 ` Michael Frank
2003-09-26 16:59 ` Vojtech Pavlik
2003-09-26 17:27 ` Måns Rullgård
2003-09-26 17:53 ` Vojtech Pavlik
2003-09-26 17:46 ` Måns Rullgård
2003-09-26 18:33 ` Vojtech Pavlik
2003-09-26 19:19 ` Michael Frank
2003-09-27 6:13 ` Vojtech Pavlik
2003-09-27 6:40 ` Michael Frank
2003-09-29 9:22 ` Måns Rullgård
2003-09-29 10:01 ` Vojtech Pavlik
2003-10-02 0:32 ` Michael Frank [this message]
2003-09-26 18:29 ` Michael Frank
2003-09-29 11:18 ` Lionel Bouton
2003-09-26 18:15 ` Michael Frank
2003-09-26 18:22 ` Michael Frank
2003-10-03 8:38 ` [BUG?] lost interrupt (was: SIS IDE DMA errors) David Caldwell
2003-10-03 9:08 ` [BUG?] lost interrupt Måns Rullgård
2003-10-03 20:07 ` David Caldwell
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=200310020832.43330.mhf@linuxmail.org \
--to=mhf@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@users.sourceforge.net \
--cc=vojtech@suse.cz \
/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