From: Lionel Bouton <Lionel.Bouton@inet6.fr>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: M?ns Rullg?rd <mru@users.sourceforge.net>,
Michael Frank <mhf@linuxmail.org>,
andre@linux-ide.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG?] SIS IDE DMA errors
Date: Mon, 29 Sep 2003 13:18:10 +0200 [thread overview]
Message-ID: <3F7814F2.80405@inet6.fr> (raw)
In-Reply-To: <20030926175358.GA12072@ucw.cz>
Vojtech Pavlik said the following on 09/26/2003 07:53 PM:
>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.
>
>
>
>>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 ...
>
>
>
This could explain some odd reports. Amongst the usual causes like flaky
hardware, kernel misconfiguration and the likes, I encountered some
people for which IO-APIC support would throw their data away...
Now I always ask the users to recompile without IO-APIC, this usually
brings other problems (awful ethernet perfs for one user comes to my
mind) but tends to solve IDE instability.
Until today, I've not a single report where lspci -vxxx highlighted any
IDE register misconfiguration, AFAICS your code *is* correct Vojtech.
LB.
--
Lionel Bouton - inet6
---------------------------------------------------------------------
o Siege social: 51, rue de Verdun - 92158 Suresnes
/ _ __ _ Acces Bureaux: 33 rue Benoit Malon - 92150 Suresnes
/ /\ /_ / /_ France
\/ \/_ / /_/ Tel. +33 (0) 1 41 44 85 36
Inetsys S.A. Fax +33 (0) 1 46 97 20 10
next prev parent reply other threads:[~2003-09-29 11:18 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
2003-09-29 11:18 ` Lionel Bouton [this message]
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=3F7814F2.80405@inet6.fr \
--to=lionel.bouton@inet6.fr \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.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.