NetBSD-Bugs archive

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

Re: kern/55667 (regression: XEN3_DOM0 fails to boot on)

OK, I got some test results:

1) console=pc get a black screen after xen boot output when the kernel starts - regression probably to new drm code

2) boot with SOL on com2 show a quick boot, xen domains start, nvme disks seem to work - good

    3) Networking sporadically 'works'

64 bytes from icmp_seq=1010 ttl=252 time=2808.453569 ms
64 bytes from icmp_seq=1011 ttl=252 time=1807.467048 ms
64 bytes from icmp_seq=1012 ttl=252 time=806.536742 ms
64 bytes from icmp_seq=1013 ttl=252 time=20588.221797 ms
64 bytes from icmp_seq=1014 ttl=252 time=19591.009999 ms
64 bytes from icmp_seq=1015 ttl=252 time=18590.143862 ms
64 bytes from icmp_seq=1016 ttl=252 time=17589.198458 ms
64 bytes from icmp_seq=1017 ttl=252 time=16588.259192 ms
64 bytes from icmp_seq=1018 ttl=252 time=15588.916960 ms
64 bytes from icmp_seq=1019 ttl=252 time=14588.002594 ms
64 bytes from icmp_seq=1020 ttl=252 time=13587.060982 ms
64 bytes from icmp_seq=1021 ttl=252 time=12586.090629 ms
64 bytes from icmp_seq=1022 ttl=252 time=11585.139296 ms
64 bytes from icmp_seq=1023 ttl=252 time=10584.192270 ms
64 bytes from icmp_seq=1024 ttl=252 time=9593.210599 ms
64 bytes from icmp_seq=1025 ttl=252 time=8582.212315 ms
64 bytes from icmp_seq=1026 ttl=252 time=7591.224635 ms
64 bytes from icmp_seq=1027 ttl=252 time=6580.268029 ms
64 bytes from icmp_seq=1028 ttl=252 time=5579.371151 ms
64 bytes from icmp_seq=1029 ttl=252 time=4587.718235 ms
64 bytes from icmp_seq=1030 ttl=252 time=3586.820254 ms
64 bytes from icmp_seq=1031 ttl=252 time=2589.213665 ms
64 bytes from icmp_seq=1032 ttl=252 time=1594.936087 ms
64 bytes from icmp_seq=1033 ttl=252 time=594.329428 ms

ssh logins work, but have long delays (see pings).

shutting down the first xen domain made the SOL link unresponsive.

shutdown takes forever.

So in summary - console screen broken, networking broken, basic xen seems to work again but

the machine is still unusable - probably still issues with interrupts on network (and possible other) devices.

Thanks for the partial progress here.

On 05/19/22 22:20, Frank Kardel wrote:
The following reply was made to PR kern/55667; it has been noted by GNATS.

From: Frank Kardel <>
Subject: Re: kern/55667 (regression: XEN3_DOM0 fails to boot on)
Date: Thu, 19 May 2022 22:15:39 +0200

  As this is a production machine I cannot test right away - will test as
  soon I find a time slot.
On 05/19/22 19:21, wrote:
  > Synopsis: regression: XEN3_DOM0 fails to boot on
  > State-Changed-From-To: open->feedback
  > State-Changed-By:
  > State-Changed-When: Thu, 19 May 2022 17:21:05 +0000
  > State-Changed-Why:
  > Is it fixed with
  > ?

Home | Main Index | Thread Index | Old Index