Messages in this thread | | | Date | Mon, 3 Mar 2003 11:45:04 +0100 | From | Stephan von Krawczynski <> | Subject | Re: Tighten up serverworks workaround. |
| |
On Wed, 26 Feb 2003 13:03:10 -0500 (EST) Alan Cox <alan@redhat.com> wrote:
> > How can e help? Please give me a configuration and how the bug manifests > > inself. > > OSB4 chipset system, some memory areas marked write combining with the > processor memory type range registers. A long time ago Dell (I > think) reported corruption from this and submitted changes to block the > use of write combining on OSB4. The question has arisen as to whether > thats a known thing, and if so which release of the chipset fixed it so that > people can only apply such a restriction to problem cases not all OSB4. > > Alan
While we are at the topic. What exactly is this:
00:00.2 Host bridge: ServerWorks: Unknown device 0006 (rev 01) 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-
00:00.3 Host bridge: ServerWorks: Unknown device 0006 (rev 01) 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-
00:0f.3 Host bridge: ServerWorks: Unknown device 0225 Subsystem: ServerWorks: Unknown device 0230 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: 0
Taken from an Asus TRL-DLS.
-- Regards, Stephan
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |