linux-kernel - Re: [Opps] Invalid opcode

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]

Message-ID: <454E7008.4020200@vmware.com>
Date:	Sun, 05 Nov 2006 15:13:12 -0800
From:	Zachary Amsden <zach@...are.com>
To:	caglar@...dus.org.tr
Cc:	Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org,
	Gerd Hoffmann <kraxel@...e.de>,
	john stultz <johnstul@...ibm.com>
Subject: Re: [Opps] Invalid opcode

S.Çağlar Onur wrote:
> Hmm, Novell bugzilla seems has similiar issues, 
> https://bugzilla.novell.com/show_bug.cgi?id=204647 and its duplicated ones 
> gaves same or similiar panic outputs.
>
>   
>> Previously we avoided converting i386 cpu bootup fully to the new state
>> machine because it is very fragile, but it's possible that there
>> is no other choice than to do it properly. Or maybe another kludge
>> is possible.
>>     

Yes, this is some kind of softirq race during init.
-
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/