> Can you still reproduce this issue with the latest version of QEMU
> (currently 5.0)?
>
> ** Changed in: qemu
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1693649
>
> Title:
> x86 pause misbehaves with -cpu haswell
>
> Status in QEMU:
> Incomplete
>
> Bug description:
> Using qemu-2.9.0
>
> When booting NetBSD using '-cpu haswell -smp 4', the system fails to
> initialize the additional CPUs. It appears as though the "application
> processor" enters routine x86_pause() but never returns.
>
> x86_pause() is simply two assembler instructions: 'pause; ret;'
>
> Replacing the routine with 'nop; nop; ret;' allows the system to
> proceed, of course without the benefit of the pause instruction on
> spin-loops!
>
> Additionally, booting with '-cpu phenom -smp 4' also works, although
> the system does seem confused about the type of CPU being used.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1693649/+subscriptions
>
> !DSPAM:5ec7625658281532840571!
>
>
Seems ok now.
On Fri, 22 May 2020, Thomas Huth wrote:
> Can you still reproduce this issue with the latest version of QEMU /bugs.launchpad .net/bugs/ 1693649 /bugs.launchpad .net/qemu/ +bug/1693649/ +subscriptions 5ec762565828153 2840571!
> (currently 5.0)?
>
> ** Changed in: qemu
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> x86 pause misbehaves with -cpu haswell
>
> Status in QEMU:
> Incomplete
>
> Bug description:
> Using qemu-2.9.0
>
> When booting NetBSD using '-cpu haswell -smp 4', the system fails to
> initialize the additional CPUs. It appears as though the "application
> processor" enters routine x86_pause() but never returns.
>
> x86_pause() is simply two assembler instructions: 'pause; ret;'
>
> Replacing the routine with 'nop; nop; ret;' allows the system to
> proceed, of course without the benefit of the pause instruction on
> spin-loops!
>
> Additionally, booting with '-cpu phenom -smp 4' also works, although
> the system does seem confused about the type of CPU being used.
>
> To manage notifications about this bug go to:
> https:/
>
> !DSPAM:
>
>
+------ ------- ------- +------ ------- ------- ------+ ------- ------- ------- --+ ------- ------- +------ ------- ------- ------+ ------- ------- ------- --+
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired) | FA29 0E3B 35AF E8AE 6651 | <email address hidden> |
| Software Developer | 0786 F758 55DE 53BA 7731 | <email address hidden> |
+------