* Problems with VIA Apollo Pro Chipsets
@ 2002-05-05 11:26 Erich Schubert
2002-05-06 22:21 ` diff NOT needed. " Erich Schubert
0 siblings, 1 reply; 2+ messages in thread
From: Erich Schubert @ 2002-05-05 11:26 UTC (permalink / raw)
To: linux-kernel
I have a system using the Gigabyte GA-6VTXDR-C Motherboard which showed
the VIA Southbridge symptoms with our 3ware Escalade RAID Controller.
On heavy load (such as kernel compilation) i get random segmentation
faults on different places, not reproduceable but every now and then.
I noticed that the quirk_vialatency was not enabled, and modified
quirks.c accordingly - but this did not yet solve the issues :-(
Any idea? (except handing the system back to the manufacturer and
asking for a working system...)
Note for this patch: in the line above my addition, 0x3112 has now an
according definition in include/linux/pci_ids.h, so this "Not out yet"
could be replaced with the Chipset name:
#define PCI_DEVICE_ID_VIA_8361 0x3112
--- /usr/src/linux/drivers/pci/quirks.c Mon Feb 25 20:38:03 2002
+++ /home/erich/coding/v2.4.18/drivers/pci/quirks.c Sun May 5 12:38:07 2002
@@ -487,6 +487,7 @@
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8363_0, quirk_vialatency },
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8371_1, quirk_vialatency },
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, 0x3112 /* Not out yet ? */, quirk_vialatency },
+ { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C598_1, quirk_vialatency },
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C576, quirk_vsfx },
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C597_0, quirk_viaetbf },
{ PCI_FIXUP_HEADER, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C597_0, quirk_vt82c598_id },
Gruss,
Erich Schubert
--
erich@(mucl.de|debian.org) -- GPG Key ID: 4B3A135C
A polar bear is a rectangular bear after a coordinate transform.
Die kürzeste Verbindung zwischen zwei Menschen ist ein Lächeln.
^ permalink raw reply [flat|nested] 2+ messages in thread
* diff NOT needed. Re: Problems with VIA Apollo Pro Chipsets
2002-05-05 11:26 Problems with VIA Apollo Pro Chipsets Erich Schubert
@ 2002-05-06 22:21 ` Erich Schubert
0 siblings, 0 replies; 2+ messages in thread
From: Erich Schubert @ 2002-05-06 22:21 UTC (permalink / raw)
To: linux-kernel
After removing one memory chip that was broken (at least memtest86 found
errors) i got rid of all errors, it seems.
So this diff is NOT needed...
The diff seemed to improve things, but i guess that was just luck...
Sorry for being too fast on that issue.
My current kernel, 2.4.19-pre7-jp10, reports the bridge now as
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 40)
So it probably isn't the known-to-be-broken one...
> --- /usr/src/linux/drivers/pci/quirks.c Mon Feb 25 20:38:03 2002
> +++ /home/erich/coding/v2.4.18/drivers/pci/quirks.c Sun May 5 12:38:07 2002
> @@ -487,6 +487,7 @@
> { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8363_0, quirk_vialatency },
> { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8371_1, quirk_vialatency },
> { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, 0x3112 /* Not out yet ? */, quirk_vialatency },
> + { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C598_1, quirk_vialatency },
> { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C576, quirk_vsfx },
> { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C597_0, quirk_viaetbf },
> { PCI_FIXUP_HEADER, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C597_0, quirk_vt82c598_id },
Gruss,
Erich Schubert
--
erich@(mucl.de|debian.org) -- GPG Key ID: 4B3A135C
A polar bear is a rectangular bear after a coordinate transform.
Die kürzeste Verbindung zwischen zwei Menschen ist ein Lächeln.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-05-06 22:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-05-05 11:26 Problems with VIA Apollo Pro Chipsets Erich Schubert
2002-05-06 22:21 ` diff NOT needed. " Erich Schubert
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox