mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Jonathan Lundell <linux@lundell-bros.com>
Cc: Alan Cox <alan@redhat.com>,
	Kimball Brown <kimball@serverworks.com>,
	davej@codemonkey.org.uk, torvalds@transmeta.com,
	linux-kernel@vger.kernel.org
Subject: Re: Tighten up serverworks workaround.
Date: Thu, 27 Feb 2003 13:14:06 +0100	[thread overview]
Message-ID: <20030227131406.Q629@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <p05210508ba82bc0ea504@[207.213.214.37]>; from linux@lundell-bros.com on Wed, Feb 26, 2003 at 10:47:52AM -0800

Hello there,

On Wed, Feb 26, 2003 at 10:47:52AM -0800, Jonathan Lundell wrote:
> At 1:03pm -0500 2/26/03, Alan Cox 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.
> 
> Presumably we're talking about CNB30 (the north bridge) rather than 
> OSB4 (the south bridge).

No it's about CNB20LE. I'm one of the low performance victims.
And this is an ASUS board (CUR-DLS) (which proved not worth its
prices recently).

Regards

Ingo Oeser
-- 
Science is what we can tell a computer. Art is everything else. --- D.E.Knuth

  reply	other threads:[~2003-02-27 13:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26 13:49 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 [this message]
2003-03-03  9:03           ` Mike A. Harris
2003-03-03 10:45           ` Stephan von Krawczynski
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=20030227131406.Q629@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=alan@redhat.com \
    --cc=davej@codemonkey.org.uk \
    --cc=kimball@serverworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@lundell-bros.com \
    --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

all inboxes | Powered by JetHome®