Re: call traces in xl dmesg during boot

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

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.

~Andrew

Attachment: signature.asc
Description: OpenPGP digital signature