public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: mru@users.sourceforge.net (Måns Rullgård)
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Michael Frank <mhf@linuxmail.org>, linux-kernel@vger.kernel.org
Subject: Re: [BUG?] SIS IDE DMA errors
Date: Fri, 26 Sep 2003 19:46:03 +0200	[thread overview]
Message-ID: <yw1x3cejjvdw.fsf@users.sourceforge.net> (raw)
In-Reply-To: <20030926175358.GA12072@ucw.cz> (Vojtech Pavlik's message of "Fri, 26 Sep 2003 19:53:58 +0200")

Vojtech Pavlik <vojtech@suse.cz> writes:

>> > Actually, it's me who wrote the 961 and 963 support. It works fine for
>> > most people. Did you check you cabling?
>> 
>> I'm dealing with a laptop, but I suppose I could wiggle the cables a
>> bit.  I still doubt it's a cable problem, since reading works
>> flawlessly.
>
> Hmm, that's indeed interesting and it'd point to a driver problem -

See, I told you :)

> when reading, the drive is dictating the timing, but when writing, it's
> the controllers turn.
>
> So if the controller timing is not correctly programmed, reads function,
> but writes don't.

Furthermore, short writes work just fine.  The errors usually start
happening after about 100 MB at full speed.  When copying from NFS
over a 100 MB/s network it usually goes a little longer, sometimes
even up to 500 MB.  All this could indicate that there is some error
in the timing, and that it takes some time for it build up enough to
trigger the bad things.  Or am I wrong?

Why can't the drive give notice when it's ready to accept more data?
That would seem like the simple solution, instead of trying to
synchronize the timers.

> Can you send me the output of 'lspci -vvxxx' of the IDE device?
> I'll take a look to see if it looks correct.

Here you go:

00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
        Subsystem: Asustek Computer, Inc.: Unknown device 1688
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 128
        Region 4: I/O ports at b800 [size=16]
00: 39 10 13 55 07 00 00 00 d0 80 01 01 00 80 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 b8 00 00 00 00 00 00 00 00 00 00 43 10 88 16
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 31 81 00 00 31 85 00 00 08 01 e6 51 00 02 00 02
50: 01 00 01 06 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


>> It appears to me that during heavy IO load, some DMA interrupts get
>> lost, for some reason.
>
> Well, I've got this feeling that not just IDE interrupts get lost under
> heavy IO load with recent kernels ...

Like mouse and keyboard...

-- 
Måns Rullgård
mru@users.sf.net

  reply	other threads:[~2003-09-26 18:05 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 [this message]
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
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=yw1x3cejjvdw.fsf@users.sourceforge.net \
    --to=mru@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhf@linuxmail.org \
    --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