From: "Kimball Brown" <kimball@serverworks.com>
To: "Alan Cox" <alan@redhat.com>, davej@codemonkey.org.uk
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: RE: Tighten up serverworks workaround.
Date: Wed, 26 Feb 2003 09:27:26 -0800 [thread overview]
Message-ID: <OMEEJAEPHFDBEBPLINBDCELACNAA.kimball@serverworks.com> (raw)
In-Reply-To: <200302261636.h1QGaAv21387@devserv.devel.redhat.com>
How can e help? Please give me a configuration and how the bug manifests
inself.
Kim Brown
VP, Business Development
kimball@serverworks.com
2451 Mission College Blvd
Santa Clara, CA 95054
(408)922-3174
(408)799-3500 (Mobile)
(408)922-3192 (FAX)
-----Original Message-----
From: Alan Cox [mailto:alan@redhat.com]
Sent: Wednesday, February 26, 2003 8:36 AM
To: davej@codemonkey.org.uk
Cc: alan@redhat.com; torvalds@transmeta.com; linux-kernel@vger.kernel.org
Subject: Re: Tighten up serverworks workaround.
> I've reports of people with rev6's who have reported success
> with that workaround commented out. Could be they never
> pushed the machine hard enough to trigger a bug, but I'd
> have thought this breakage would show up pretty quickly.
It doesn't. It requires the right patterns and took Dell quite
some time to identify and pin down. If its like the 450NX one
which I suspect it is then you have to have pending misordered
stores to a write gathering target evicted by another read.
> My attempts to contact serverworks in the past have fallen on
> deaf ears. maybe you have better luck ?
I'll try. I got on ok with them for the OSB4 stuff but thats
a long time ago and they've been eaten since then
[Bcc'd to the person I suspect is the right starting point]
Alan
next prev parent reply other threads:[~2003-02-26 17:15 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 [this message]
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
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=OMEEJAEPHFDBEBPLINBDCELACNAA.kimball@serverworks.com \
--to=kimball@serverworks.com \
--cc=alan@redhat.com \
--cc=davej@codemonkey.org.uk \
--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