From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Jackson <ian.jackson@citrix.com>
Cc: Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu@kernel.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Paul Durrant <paul@xen.org>,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] Stopping much Linux testing in Xen Project CI
Date: Thu, 12 Mar 2020 18:55:00 +0100 [thread overview]
Message-ID: <20200312175500.GL24458@Air-de-Roger.citrite.net> (raw)
In-Reply-To: <24170.26671.783256.460525@mariner.uk.xensource.com>
On Thu, Mar 12, 2020 at 04:49:51PM +0000, Ian Jackson wrote:
> Linux stable branches, and Linux upstream tip, are badly broken and
> have been for months. Apparently no-one is able to (or has time to)
> to investigate and fix.
>
> linux-4.4 218 days to be suspended
> linux-4.9 134 days to be suspended
> linux-4.14 134 days to be suspended
> linux-4.19 134 days to be suspended
> linux-5.4 55 days
> linux-arm-xen up to date
> linux-linus 372 days to be suspended
>
> These are times since the last push - ie, how long it has been broken.
> Evidently no-one is paying any attention to this.[1] I looked at the
> reports myself and:
>
> Nested HVM is broken on Intel in all of the 4.x branches.
FWIW, it's the Debian installer kernel the one that crashes AFAICT,
all the failures are:
[ 0.000000] Linux version 4.9.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
[...]
[ 0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 30580167144 ns
[ 0.000000] tsc: Fast TSC calibration failed
[ 0.000000] tsc: Unable to calibrate against PIT
[ 0.000000] tsc: HPET/PMTIMER calibration failed
[ 0.000000] divide error: 0000 [#1] SMP
[ 0.000000] Modules linked in:
[ 0.000000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.9.0-6-amd64 #1 Debian 4.9.82-1+deb9u3
[ 0.000000] Hardware name: Xen HVM domU, BIOS 4.14-unstable 03/11/2020
[ 0.000000] task: ffffffffab611500 task.stack: ffffffffab600000
[ 0.000000] RIP: 0010:[<ffffffffaaa59e1f>] [<ffffffffaaa59e1f>] pvclock_tsc_khz+0xf/0x30
[ 0.000000] RSP: 0000:ffffffffab603f38 EFLAGS: 00010246
[ 0.000000] RAX: 000f424000000000 RBX: ffffffffffffffff RCX: 0000000000000000
[ 0.000000] RDX: 0000000000000000 RSI: 0000000000000246 RDI: ffffffffab939020
[ 0.000000] RBP: ffff93806e8f1540 R08: 000000003a637374 R09: 6f6974617262696c
[ 0.000000] R10: 00000032f3af6dcd R11: 4d502f5445504820 R12: ffffffffab7dc920
[ 0.000000] R13: ffffffffab7e82e0 R14: 00000000000146f0 R15: 000000000000008e
[ 0.000000] FS: 0000000000000000(0000) GS:ffff93806e600000(0000) knlGS:0000000000000000
[ 0.000000] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.000000] CR2: ffff938065f3a000 CR3: 0000000025c08000 CR4: 00000000000406b0
[ 0.000000] Stack:
[ 0.000000] ffffffffab74b1b6 ffff93806e8f1540 ffffffffab7dc920 ba81e537ba81e512
[ 0.000000] ffffffffffffffff ffff93806e8f1540 ffffffffab73deb6 ffffffffab7e82e0
[ 0.000000] 0000000000000000 0000000000000020 0000ffffffffab73 00000000ffffffff
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffffab74b1b6>] ? tsc_init+0x39/0x25b
[ 0.000000] [<ffffffffab73deb6>] ? start_kernel+0x39f/0x46b
[ 0.000000] [<ffffffffab73d120>] ? early_idt_handler_array+0x120/0x120
[ 0.000000] [<ffffffffab73d408>] ? x86_64_start_kernel+0x14c/0x170
[ 0.000000] Code: a6 bc 00 c0 9d a5 aa 0f 94 c0 c3 90 40 88 3d cd ea cb 00 c3 0f 1f 84 00 00 00 00 00 8b 4f 18 31 d2 48 b8 00 00 00 00 40 42 0f 00 <48> f7 f1 0f b6 57 1c 89 d1 f7 d9 48 89 c6 48 d3 e6 89 d1 48 d3
[ 0.000000] RIP [<ffffffffaaa59e1f>] pvclock_tsc_khz+0xf/0x30
[ 0.000000] RSP <ffffffffab603f38>
[ 0.000000] random: fast init done
[ 0.000000] ---[ end trace 21c3bd5ec174e388 ]---
[ 0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
On all branches it's blocked by 4.9.0-6-amd64 from Debian failing, not
the kernel under test (which could also fail, but we don't even get
there).
I have started a repro and will look into tomorrow.
Regards, Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-03-12 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 16:49 [Xen-devel] Stopping much Linux testing in Xen Project CI Ian Jackson
2020-03-12 16:51 ` Ian Jackson
2020-03-12 17:06 ` Jürgen Groß
2020-03-12 17:55 ` Roger Pau Monné [this message]
2020-03-13 9:13 ` Jan Beulich
2020-03-13 10:21 ` Jürgen Groß
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200312175500.GL24458@Air-de-Roger.citrite.net \
--to=roger.pau@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.jackson@citrix.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=oleksandr_andrushchenko@epam.com \
--cc=paul@xen.org \
--cc=sstabellini@kernel.org \
--cc=wei.liu@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.