From: David Vrabel <david.vrabel@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
<boris.ostrovsky@oracle.com>, <david.vrabel@citrix.com>
Cc: <linux-kernel@vger.kernel.org>, <xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] linux 4.4 Regression: 100% cpu usage on idle pv guest under Xen with single vcpu.
Date: Wed, 2 Dec 2015 14:15:42 +0000 [thread overview]
Message-ID: <565EFD0E.4020501@citrix.com> (raw)
In-Reply-To: <80dcf47eb772c65a62652d7a56c8ed26@eikelenboom.it>
On 28/11/15 15:47, Sander Eikelenboom wrote:
>
> -rtc_cmos rtc_cmos: hctosys: unable to read the hardware clock
> +hctosys: unable to open rtc device (rtc0)
>
> -genirq: Flags mismatch irq 8. 00000000 (hvc_console) vs. 00000000 (rtc0)
> -hvc_open: request_irq failed with rc -16.
I have reproduced this issue. We really shouldn't have an RTC device in
a PV guest and I think this irq conflict breaks hvc0.
David
next prev parent reply other threads:[~2015-12-02 14:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 15:47 linux 4.4 Regression: 100% cpu usage on idle pv guest under Xen with single vcpu Sander Eikelenboom
[not found] ` <20151130214513.GF14317@char.us.oracle.com>
2015-11-30 21:46 ` [Xen-devel] " Sander Eikelenboom
2015-11-30 22:54 ` Boris Ostrovsky
2015-11-30 22:55 ` Sander Eikelenboom
2015-12-01 22:47 ` Boris Ostrovsky
2015-12-01 23:00 ` Sander Eikelenboom
2015-12-01 23:19 ` Boris Ostrovsky
2015-12-01 23:30 ` Sander Eikelenboom
2015-12-01 23:41 ` Boris Ostrovsky
2015-12-01 23:44 ` Sander Eikelenboom
2015-12-02 10:04 ` Sander Eikelenboom
2015-12-01 22:51 ` Sander Eikelenboom
2015-12-01 23:05 ` Boris Ostrovsky
2015-11-30 22:47 ` Sander Eikelenboom
2015-12-02 14:15 ` David Vrabel [this message]
2015-12-02 14:55 ` David Vrabel
2015-12-02 17:30 ` Sander Eikelenboom
[not found] <CAPQw5rmKWRoYQa4Lt9ZyBzKuK3kKSXkd_YoYWO_cVfKoL+EMbw@mail.gmail.com>
2015-12-14 21:07 ` Sander Eikelenboom
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=565EFD0E.4020501@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox