From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: mbs <mbs@mc.com>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
Brien <admin@brien.com>, John Bradford <john@grabjohn.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: my dual channel DDR 400 RAM won't work on any linux distro
Date: 17 Apr 2003 13:45:35 +0100 [thread overview]
Message-ID: <1050583534.31390.5.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <200304171241.IAA08069@mc.com>
On Iau, 2003-04-17 at 13:46, mbs wrote:
> <not flamebait, honest question>
> you hear this all the time, but do we really have any empirical evidence
> proving this, or is it just what we say to make ourselves feel good when
> Linux won't run on hardware that works fine under other os's?
> </not flamebait, honest question>
Yes, both evidence and in some cases explanation. As to the reasons
quoted in the original message those are probably less true now. Linux
has extremely optimised memory copiers - our AMD memory copiers broke
older VIA chipsets, it took several months until photoshop and other
specialist apps hit the same bug with their mmx/3dnow hand tuned effects
tools on windows and VIA actually fixed it.
Linux also allocates memory in very different patterns to Windows. So
a box that shows the odd crash in windows due to a memory error may show
repeated crashes in Linux an vice versa
next prev parent reply other threads:[~2003-04-17 13:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200304161511.h3GFBoe7000614@81-2-122-30.bradfords.org.uk>
2003-04-16 15:41 ` Brien
2003-04-16 15:47 ` Mr. James W. Laferriere
2003-04-16 15:58 ` Charles Cazabon
2003-04-16 16:10 ` Chris Friesen
2003-04-17 12:46 ` mbs
2003-04-17 12:45 ` Alan Cox [this message]
[not found] ` <1050506129.28586.121.camel@dhcp22.swansea.linux.org.uk>
2003-04-16 16:38 ` Brien
2003-04-16 17:01 ` John Bradford
2003-04-16 18:15 ` Brien
2003-04-16 19:28 ` John Bradford
2003-04-16 20:51 ` Brien
2003-04-17 8:12 ` John Bradford
2003-04-20 16:58 Walt H
-- strict thread matches above, loose matches on Subject: below --
2003-04-16 14:59 Brien
2003-04-16 16:51 ` Bruce Harada
2003-04-16 20:53 ` Robert White
2003-04-16 21:01 ` Brien
2003-04-16 22:05 ` root
2003-04-17 1:16 ` Mike Dresser
2003-04-17 5:34 ` Peter Svensson
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=1050583534.31390.5.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=admin@brien.com \
--cc=cfriesen@nortelnetworks.com \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbs@mc.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®