>>> On 18.04.13 at 13:36, Roger Pau Monné<roger.pau@citrix.com>
wrote:
> Hello,
>
> FreeBSD bootloader is getting stuck with tip of xen-unstable. I've
> bisected the Xen tree and found that the culprit of this is the
> following commit:
>
> 527824f41f5fac9cba3d4441b2e73d3118d98837 is the first bad commit
> commit 527824f41f5fac9cba3d4441b2e73d3118d98837
> Author: Tim Deegan <tim@xen.org>
> Date: Thu Mar 28 11:27:31 2013 +0000
>
> x86/hvm: Centralize and simplify the RTC IRQ logic.
>
> This keeps the behaviour of strobing the IRQ line every time any RTC
> interrupt source is raised. I rather suspect (based on the behaviour
> of the MC146818A RTC) that we ought to be suppressing all subsequent
> interrupts whenever RTC_IRQF is set, but this way avoids making
> guest-visible changes.
>
> Signed-off-by: Tim Deegan <tim@xen.org>
> Acked-by: Jan Beulich <jbeulich@suse.com>
> Acked-by: Keir Fraser <keir@xen.org>
>
> Not sure, but I guess this is probably related to the issues George is
> seeing on Windows 2003:
>
> <CAFLBxZbaggssHmQFpEkreFDsqdu3XPDqd1k4fXQb9k=qSXjMcw@mail.gmail.com>
But George is seeing his issue with a much earlier commit, so the
connection can only be relatively weak.
But both together suggest to me that perhaps a debugging patch
for both of you to try might be more useful at this point than a
partial revert of the bad commit he spotted. Maybe later today,
or if not, then hopefully tomorrow...
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel