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]
Date:	Sun, 5 Nov 2006 21:51:06 +0200
From:	"S.Çağlar Onur" <>
To:	Andi Kleen <>
Cc:, Zachary Amsden <>,
	Gerd Hoffmann <>,
	john stultz <>
Subject: Re: [Opps] Invalid opcode


05 Kas 2006 Paz 20:57 tarihinde, Andi Kleen şunları yazmıştı: 
> Can you test with "noreplacement" to make sure?

I sorry for not to mention that, i tried noreplacement before reporting which 
is also ends up with same panic.

> Anyways I suspect we're just getting back some variant of the old CPU setup
> race.
> Normally CPU booting in Linux follows a special "cpu hotplug" state
> machine, but for historical reasons i386 only implements one state of 
> this. At one point we had a similar bug (but not in the callback on CPU #0,
> but in the timer on newly booted CPU). I don't see currently how it can
> happen (but i haven't thought very deeply about it yet)
> Probably your timing is just unlucky on those simulators.

Hmm, Novell bugzilla seems has similiar issues, 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.

S.Çağlar Onur <>

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists