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

Re: call traces in xl dmesg during boot

  • To: Olaf Hering <olaf@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  • Date: Thu, 29 Oct 2020 09:13:08 +0000
  • Authentication-results: esa1.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none
  • Delivery-date: Thu, 29 Oct 2020 09:13:28 +0000
  • Ironport-sdr: 1oI8sBvQvKbsoecTC6ptYy5NGOnI1E5p9u6brqy1o7+v2L1LoBUeAVablw+uWdQdiWliBHNij1 qNN4GJfs6NJm2xCfOV28Gv8DgEsH8rCdkXyvmOEWZb90lGtbIe/N4gtTynsLFJhxI0KFJ19iPc YRvCK3uux0c6cKrJr4RvaYz6lhRtn4G8peMPXefRzPBQ3mp0qn7gbSrv2ab91SOnGpFIWszJNN tX4czHOoJswuK1UEDbTC495vDo/BCoFYslcSQy/WPmJcOT7xD1MQsuBLyi/QUxyeDvHywsqXIY xEQ=
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 29/10/2020 08:22, Olaf Hering wrote:
> During boot of xen.git#staging, Xen seems to think something pressed debug 
> keys very early, which shows various call traces in 'xl dmesg'. A reboot may 
> "fix" it, and no traces are printed.
> Any idea what may cause this behavior? I do not see it on a slightly smaller 
> box.

That means Xen is receiving real keystrokes on the UART.

I've seen it before on hardware with floating wires in place of a
properly connected UART, but I've also seen it on systems with an
incorrectly configured BAUD rate.  Looking at your command line, you
probably want com1=115200,8n1 although this should also be the default.

Totally unrelated to the problem at hand, but an observation.

(XEN) [000000d6b68c0ecc] WARNING: NR_CPUS limit of 256 reached -
ignoring further processors

You'll need NR_CPUS configured to 512 to boot properly on this system.


Attachment: signature.asc
Description: OpenPGP digital signature



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