From: Len Brown <lenb@kernel.org>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86 instability with 2.6.1{8,9}
Date: Tue, 2 Jan 2007 13:42:32 -0500 [thread overview]
Message-ID: <200701021342.32195.lenb@kernel.org> (raw)
In-Reply-To: <20070102180425.GA18680@deepthought>
On Tuesday 02 January 2007 13:04, Ken Moffat wrote:
> On Tue, Jan 02, 2007 at 12:25:57PM -0500, Len Brown wrote:
> > > it's been nothing but trouble in 32-bit mode.
> > > It still works fine when I boot it in 64-bit mode.
> >
> > A shot in the dark at the spontaneous reset issue, but no clue on the 32 vs 64-bit observation...
> >
> > See if ACPI exports any temperature readings under /proc/acpi/thermal_zone/*/temperature
> > and if so, keep an eye on them to see if there is an indication of a thermal problem.
> >
> > ( And if ACPI doesn't, maybe lmsensors can find something.)
> >
> > cheers,
> > -Len
>
> Thanks, but there is nothing there. I never managed to get
> lmsensors configured (as in 'calibrated') for the hardware I tried it
> on, but I was starting to think about retrying it. But first, I'm
> just about to start testing with memtest86+ in case something in the
> memory has gone bad.
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
next prev parent reply other threads:[~2007-01-02 18:43 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 [this message]
2007-01-02 19:34 ` Ken Moffat
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=200701021342.32195.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zarniwhoop@ntlworld.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