From: Stephan von Krawczynski <skraw@ithnet.com>
To: Alan Cox <alan@redhat.com>
Cc: kimball@serverworks.com, alan@redhat.com,
davej@codemonkey.org.uk, torvalds@transmeta.com,
linux-kernel@vger.kernel.org
Subject: Re: Tighten up serverworks workaround.
Date: Mon, 3 Mar 2003 11:45:04 +0100 [thread overview]
Message-ID: <20030303114504.72f47d0e.skraw@ithnet.com> (raw)
In-Reply-To: <200302261803.h1QI3BT24020@devserv.devel.redhat.com>
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
next prev parent reply other threads:[~2003-03-03 10:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 13:49 Tighten up serverworks workaround davej
2003-02-26 16:27 ` Alan Cox
2003-02-26 16:29 ` Dave Jones
2003-02-26 16:36 ` Alan Cox
2003-02-26 17:27 ` Kimball Brown
2003-02-26 18:03 ` Alan Cox
2003-02-26 18:47 ` Jonathan Lundell
2003-02-27 12:14 ` Ingo Oeser
2003-03-03 9:03 ` Mike A. Harris
2003-03-03 10:45 ` Stephan von Krawczynski [this message]
2003-03-03 12:02 ` Alan Cox
2003-03-03 12:46 ` Stephan von Krawczynski
2003-03-03 14:42 ` Alan Cox
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=20030303114504.72f47d0e.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=alan@redhat.com \
--cc=davej@codemonkey.org.uk \
--cc=kimball@serverworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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