SiS pci target abort?

[Lionel Bouton <Lionel.Bouton@inet6.fr>]

 > I'm running a linux 2.4.18 kernel on a PC with SiS glue chip:
 >
 > cubox2.sj.broadcom.com$ lspci
 > 00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device 
0650 (rev 01)
 > 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP
 > 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513
 > 00:02.2 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07)
 > 00:02.3 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07)
 > 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] 
(rev d0)
 > 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] 
SiS7012 PCI
 > +Audio Accelerator (rev a0)
 > 00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 
10/100
 > +Ethernet (rev 90)
 > 00:0f.0 Network controller: BROADCOM Corporation: Unknown device 4301
 > 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS]: 
Unknown device
 > +6325
 >
 > Reading a Broadcom device register which returns a pci target abort
 > will return the last value read, the SiS chip actually cycles thru the
 > last 4 recently read values, instead of returning 0xffffffff like all
 > other PC system chips I've ever seen.  Is this a known SiS chip bug?
 >
 > Thanks much for any info you could provide.
 >                 
 > neal nuckolls
 > nn@broadcom.com

Not much info as I don't have the hardware here to reproduce your 
config. From your e-mail address I assume you're developing Linux 
drivers for your network cards or debugging a problem with existing ones.
I took the liberty of forwarding your e-mail to the linux-kernel mailing 
list. If this problem is known there are chances one subscriber is aware 
of it (there are SiS people around here).

LB.