From: mru@users.sourceforge.net (Måns Rullgård)
To: Michael Frank <mhf@linuxmail.org>
Cc: andre@linux-ide.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG?] SIS IDE DMA errors
Date: Fri, 26 Sep 2003 17:38:09 +0200 [thread overview]
Message-ID: <yw1xr823k1b2.fsf@users.sourceforge.net> (raw)
In-Reply-To: <200309262332.30091.mhf@linuxmail.org> (Michael Frank's message of "Fri, 26 Sep 2003 23:32:30 +0800")
Michael Frank <mhf@linuxmail.org> writes:
>> > Suspect chipset related issue which should be looked into.
>>
>> That's what someone told me three months ago, too. Nothing happened,
>> though.
>>
>
> OK, now that we are two, we copy the IDE maintainer ;)
>
> I guess it is fair to say that we are happy to test patches.
>
> And here is my lspci -vv.
>
> 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: <available only to root>
Mine looks rather similar, but there are a few differences. Mine has
Mem+ and DEVSEL=fast.
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]
--
Måns Rullgård
mru@users.sf.net
next prev parent reply other threads:[~2003-09-26 16:46 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 [this message]
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
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=yw1xr823k1b2.fsf@users.sourceforge.net \
--to=mru@users.sourceforge.net \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.org \
/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.