linux-kernel - Re: x86 instability with 2.6.1{8,9}

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070102180425.GA18680@deepthought>
Date:	Tue, 2 Jan 2007 18:04:25 +0000
From:	Ken Moffat <zarniwhoop@...world.com>
To:	Len Brown <lenb@...nel.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: x86 instability with 2.6.1{8,9}

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.

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/