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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 2 Jan 2007 19:34:59 +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 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
-
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/