public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Frank <mhf@linuxmail.org>
To: mru@users.sourceforge.net (Måns Rullgård)
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: [BUG?] SIS IDE DMA errors
Date: Sat, 27 Sep 2003 03:44:11 +0800	[thread overview]
Message-ID: <200309270344.11262.mhf@linuxmail.org> (raw)
In-Reply-To: <yw1xr823k1b2.fsf@users.sourceforge.net>

On Friday 26 September 2003 23:38, Måns Rullgård wrote:
> 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]
> 
> 
> 

Here is my ATA config of 2.6.0-test5. Could you please send same ex your .config. I will build it and see if anything changes.


#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECS=m
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=m
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y

#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
CONFIG_BLK_DEV_OPTI621=y
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDE_TCQ is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
CONFIG_BLK_DEV_AEC62XX=y
CONFIG_BLK_DEV_ALI15X3=y
CONFIG_WDC_ALI15X3=y
CONFIG_BLK_DEV_AMD74XX=y
CONFIG_BLK_DEV_CMD64X=y
CONFIG_BLK_DEV_TRIFLEX=y
CONFIG_BLK_DEV_CY82C693=y
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
CONFIG_BLK_DEV_HPT34X=y
CONFIG_BLK_DEV_HPT366=y
CONFIG_BLK_DEV_SC1200=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_BLK_DEV_NS87415=y
CONFIG_BLK_DEV_PDC202XX_OLD=y
# CONFIG_PDC202XX_BURST is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
# CONFIG_PDC202XX_FORCE is not set
CONFIG_BLK_DEV_SVWKS=y
CONFIG_BLK_DEV_SIIMAGE=y
CONFIG_BLK_DEV_SIS5513=y
CONFIG_BLK_DEV_SLC90E66=y
CONFIG_BLK_DEV_TRM290=y
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set



Regards
Michael


  reply	other threads:[~2003-09-26 19:44 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 [this message]
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=200309270344.11262.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