From: Michael Frank <mhf@linuxmail.org>
To: Vojtech Pavlik <vojtech@suse.cz>,
M?ns Rullg?rd <mru@users.sourceforge.net>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
andre@linux-ide.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG?] SIS IDE DMA errors
Date: Sat, 27 Sep 2003 02:29:23 +0800 [thread overview]
Message-ID: <200309270229.23554.mhf@linuxmail.org> (raw)
In-Reply-To: <20030926175358.GA12072@ucw.cz>
On Saturday 27 September 2003 01:53, Vojtech Pavlik wrote:
> On Fri, Sep 26, 2003 at 07:27:35PM +0200, M?ns Rullg?rd wrote:
> > 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 -
> 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.
>
> Can you send me the output of 'lspci -vvxxx' of the IDE device?
> I'll take a look to see if it looks correct.
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 5332
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128
Interrupt: pin ? routed to IRQ 10
Region 4: I/O ports at 4000 [size=16]
Capabilities: [58] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 39 10 13 55 05 00 10 02 00 80 01 01 00 80 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 40 00 00 00 00 00 00 00 00 00 00 62 14 32 53
30: 00 00 00 00 58 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 06 00 00 00 00 00
50: f2 07 f2 07 ea 96 d5 d0 01 00 02 86 00 00 00 00
60: ff aa ff aa 00 00 00 00 00 00 00 00 00 00 00 00
70: 17 21 06 04 00 60 1c 1e 00 60 1c 1e 00 60 1c 1e
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 ...
Timer interrupts too as clocks seem to run slow only
on a number of machines.
Regards
Michael
Regards
Michael
next prev parent reply other threads:[~2003-09-26 18:29 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
2003-09-26 18:29 ` Michael Frank [this message]
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=200309270229.23554.mhf@linuxmail.org \
--to=mhf@linuxmail.org \
--cc=andre@linux-ide.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 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.