[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] "CPU N still not dead..." messages during microcode update stage of boot when smt=0


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
  • Date: Sun, 21 Jul 2019 20:06:23 +0000
  • Delivery-date: Sun, 21 Jul 2019 20:06:28 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Openpgp: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc

Hi,

My first time using smt=0 on hypervisor command line so not sure how
many versions and different pieces of hardware this happens with,
but I noticed this during the microcode update stage of boot:

(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) Adding cpu 1 to runqueue 0
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) Removing cpu 1 from runqueue 0
(XEN) microcode: CPU2 updated from revision 0x2000057 to 0x200005e, date = 
2019-04-02 
(XEN) Adding cpu 2 to runqueue 0
(XEN) Adding cpu 3 to runqueue 0
(XEN) Removing cpu 3 from runqueue 0
(XEN) microcode: CPU4 updated from revision 0x2000057 to 0x200005e, date = 
2019-04-02 
(XEN) Adding cpu 4 to runqueue 0
(XEN) Adding cpu 5 to runqueue 0
(XEN) Removing cpu 5 from runqueue 0
(XEN) microcode: CPU6 updated from revision 0x2000057 to 0x200005e, date = 
2019-04-02 
(XEN) Adding cpu 6 to runqueue 0
(XEN) Adding cpu 7 to runqueue 0
(XEN) Removing cpu 7 from runqueue 0
(XEN) microcode: CPU8 updated from revision 0x2000057 to 0x200005e, date = 
2019-04-02 
(XEN) Adding cpu 8 to runqueue 0
(XEN) Adding cpu 9 to runqueue 0
(XEN) Removing cpu 9 from runqueue 0
(XEN) microcode: CPU10 updated from revision 0x2000057 to 0x200005e, date = 
2019-04-02 
(XEN) Adding cpu 10 to runqueue 0
(XEN) Adding cpu 11 to runqueue 0
(XEN) Removing cpu 11 from runqueue 0
(XEN) microcode: CPU12 updated from revision 0x2000057 to 0x200005e, date = 
2019-04-02 
(XEN) Adding cpu 12 to runqueue 0
(XEN) Adding cpu 13 to runqueue 0
(XEN) Removing cpu 13 from runqueue 0
(XEN) microcode: CPU14 updated from revision 0x2000057 to 0x200005e, date = 
2019-04-02 
(XEN) Adding cpu 14 to runqueue 0
(XEN) Adding cpu 15 to runqueue 0
(XEN) Removing cpu 15 from runqueue 0
(XEN) Brought up 8 CPUs
(XEN) Parked 8 CPUs

It doesn't happen with smt=1 and it also doesn't happen when SMT is
disabled in the BIOS.

Boot does continue normally after this point.

Is this expected? 4.12.

Cheers,
Andy

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.