linux-kernel - Re: Fwd: laptop / computer hardlocks during execution of 32bit applications(binaries) on 64bit system (Gentoo)

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] [day] [month] [year] [list]

Date:	Wed, 2 Jan 2008 09:40:02 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Miguel Botón <mboton.lkml@...il.com>
Cc:	Matthew <jackdachef@...il.com>, linux-kernel@...r.kernel.org,
	roland@...hat.com, tglx@...utronix.de
Subject: Re: Fwd: laptop / computer hardlocks during execution of 32bit
	applications(binaries) on 64bit system (Gentoo)

* Miguel Botón <mboton.lkml@...il.com> wrote:

> These hardlocks start to appear with commit 
> f10c1cfd359660c01446807b6c2bc8ce3aee919a

thanks, that's really useful! I dont see anything obviously wrong with 
the commit though, and cannot (yet) reproduce it, so to help us track it 
down further, could you try to figure out the lockup site? Does the NMI 
watchdog work on your box?

if the NMI watchdog does not work, can you reproduce it on a VGA 
console? If yes, then running the app that does the hard lockup via 
"strace -f <app>" could perhaps show us the last system call that 
happened before the box locked up. If we are lucky it's something 
specific.

here's the guilty commit from latest x86.git#mm:

  commit 81376371f1ca371de54aa4488edc541580d95a01
  Author: Roland McGrath <roland@...hat.com>
  Date:   Tue Jan 1 21:55:28 2008 +0100

      x86 i387 user_regset

	Ingo
--
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/