From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86 instability with 2.6.1{8,9}
Date: Tue, 2 Jan 2007 19:34:59 +0000 [thread overview]
Message-ID: <20070102193459.GA19894@deepthought> (raw)
In-Reply-To: <200701021342.32195.lenb@kernel.org>
On Tue, Jan 02, 2007 at 01:42:32PM -0500, Len Brown wrote:
>
> You might remove and re-insert the DIMMS.
> Sometimes there are poor contacts if the DIMMS are not fully seated and clicked in.
>
> The real mystery is the 32 vs 64-bit thing.
> Are the devices configured the same way -- ie are they both in IOAPIC mode
> and /proc/interrupts looks the same for both modes?
>
> -Len
Too late, I've started memtest-86+. If it seems ok after an
overnight run, I'll take a look at /proc/interrupts. How can I tell
it is in IOAPIC mode, please ? Google was not helpful for this, but
if it's an override, the only things on my command lines are root=
and video= settings.
Certainly, it seems likely that the configs could be fairly
different in their detail.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
next prev parent reply other threads:[~2007-01-02 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-01 16:01 x86 instability with 2.6.1{8,9} Ken Moffat
2007-01-01 16:48 ` Alistair John Strachan
2007-01-01 17:07 ` Ken Moffat
2007-01-01 19:13 ` Ken Moffat
2007-01-01 19:45 ` Alistair John Strachan
2007-01-02 17:25 ` Len Brown
2007-01-02 18:04 ` Ken Moffat
2007-01-02 18:42 ` Len Brown
2007-01-02 19:34 ` Ken Moffat [this message]
2007-01-06 22:04 ` Randy Dunlap
2007-01-07 14:26 ` Ken Moffat
2007-01-15 16:29 ` Ken Moffat
2007-01-25 23:56 ` Ken Moffat
2007-01-31 21:36 ` Chuck Ebbert
2007-01-31 23:26 ` Ken Moffat
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=20070102193459.GA19894@deepthought \
--to=zarniwhoop@ntlworld.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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