From: Stan Gammons <s_gammons@charter.net>
To: "Mike McCarthy, W1NR" <lists@w1nr.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 64 bit kernel
Date: Mon, 09 Jan 2006 16:47:57 -0600 [thread overview]
Message-ID: <1136846877.6695.44.camel@falklands.home.pc> (raw)
In-Reply-To: <001c01c61520$2cbba6b0$6d0ea8c0@LoJackOne.LoJack.com>
On Mon, 2006-01-09 at 08:25 -0500, Mike McCarthy, W1NR wrote:
> I saw a similar issue many years ago that turned out to be a chipset bug.
> This was a PII system that used 16 bit wide modules. When using only one
> module, the chipset "fooled" the OS into thinking that it was doing 32 bit
> wide operations. However, it failed at full speed. Reducing the memory bus
> speed or installing modules in pairs "fixed" the problem. I suspect a bus
> or memory controller issue rather than the kernel.
>
> The failure mode was exactly as you describe. It manifested itself as disk
> errors or DMA failures. Unfortunately the chipset vendor determined that it
> was a silicon bug and said that they would NOT fix it!
Hi Mike,
What chipset was that?
This board has an nVidia nForce 3 chipset on it. This brings about
another question. What is the consensus on using the amd74xx.c patch for
the nForce 3/4 chipset that nVidia has on their website? It's supposed
to improve HD performance. Any comments on including that patch in the
existing kernel? How about the pros and or cons of adding that patch
and rebuilding a system specific kernel?
Stan
next prev parent reply other threads:[~2006-01-09 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 4:27 Stan Gammons
2006-01-09 13:25 ` Mike McCarthy, W1NR
2006-01-09 15:04 ` Gene Heskett
2006-01-09 22:47 ` Stan Gammons [this message]
2006-01-09 18:25 ` Andi Kleen
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=1136846877.6695.44.camel@falklands.home.pc \
--to=s_gammons@charter.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@w1nr.net \
/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®