From: jeff@AmeriCom.com
To: nw@codon.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux SMP kernel bug with > 512M ram
Date: 6 Sep 2002 21:49:54 -0000 [thread overview]
Message-ID: <20020906214954.26037.qmail@solo.americom.com> (raw)
In-Reply-To: <fa.hqeru5v.1v6u3h8@ifi.uio.no>
Its a VIA motherboard, and I found the problem:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=47160
Thanks for the help.
Regards,
Jeffrey Moss
jeff@americom.com
> Message-ID: <005a01c255ec$89be7b40$d281f6cc@WEASEL>
> From: "Steve Wolfe" <nw@codon.com>
> To: <jeff@AmeriCom.com>
> References: <fa.hqf5vev.1u6g19e@ifi.uio.no> <fa.hqeru5v.1v6u3h8@ifi.uio.no>
> Subject: Re: Linux SMP kernel bug with > 512M ram
> Date: Fri, 6 Sep 2002 15:29:29 -0600
> MIME-Version: 1.0
>
>
>
> > I don't think its chipset or memory, the machines that crash have
> different brand
> > motherboards with different chipsets, I ran docmem for 24 hours on each
> stick of ram
> > and found no errors. The ram worked fine in my WindowsXP machine, and it
> works fine
> > when I use the non-smp kernel, and/or when I take the ram down to 2
> sticks (512
> > meg). I'm posting here because I believe I have narrowed it down to a
> bug in the
> > kernel.
>
> I've also been bit in the rear-end by memory bugs, and I can assure
> you, they can be devilish to find. First, rather than running a memory
> test on each individual stick, you MUST run the memory test on the actual
> system, with the actual RAM. Often times, weird, bizarre errors crop up
> in certain combinations and not in others.
>
> It's also a little difficult to convince people that it's a bug in the
> kernel, when there is an incredibly number of people who run SMP kernels
> with >512 MB. I maintain a decent number of such machines, and have seen
> absolutely *zero* problems of similar natures that weren't traced back to
> defective or incompatible hardware.
>
> I'm curious - what kinds of motherboards are you using, and what kinds
> of RAM? What kind of memory timings are specified in the BIOS?
>
> steve
>
>
next parent reply other threads:[~2002-09-06 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <005a01c255ec$89be7b40$d281f6cc@WEASEL>
[not found] ` <fa.hqf5vev.1u6g19e@ifi.uio.no>
[not found] ` <fa.hqeru5v.1v6u3h8@ifi.uio.no>
2002-09-06 21:49 ` jeff [this message]
2002-09-06 16:55 jeff
2002-09-06 17:06 ` Martin J. Bligh
2002-09-06 17:07 ` Alan Cox
2002-09-06 20:50 ` jeff
2002-09-06 20:47 ` David S. Miller
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=20020906214954.26037.qmail@solo.americom.com \
--to=jeff@americom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nw@codon.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®