Re: [Xen-devel] [xen-unstable test] 13677: regressions - FAIL

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 12.09.12 at 12:35, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Wed, 2012-09-12 at 11:12 +0100, Ian Campbell wrote:
>> On Wed, 2012-09-12 at 11:08 +0100, Jan Beulich wrote:
>> > > Is it outside the realms of possibility that the guest has managed to
>> > > limp along with the RTC being broken in some subtle way and only
>> > > eventually trips up when we come to shut down?
>> > 
>> > That's certainly not impossible, but afaik Linux doesn't play with
>> > the RTC unless told to by user space
>> 
>> I did wonder about an /etc/init.d/hwclock type thing, but I think that
>> would have run much earlier than this point.
>> 
>> >  (whereas Windows, as we
>> > know from the reporter of the problem that triggered putting
>> > together these changes, does on its own at least under certain
>> > circumstances, yet the Windows tests all go through fine).
>> > 
>> > Certainly this is the most likely candidate for having broken
>> > something, and hence would be the prime candidate for reverting.
>> > But before doing so, I'd want to see at least another run's results.
>> 
>> Ack. I'm installing a RHEL6.1 HVM guest anyway, since it's handy to have
>> one in my pocket.
> 
> 25876:35fa512c60b2 "gnttab: cleanup of number-of-active-frames
> calculations" for both => hangs:
>         Syncing hardware clock to system time [  OK  ]
>         Turning off swap:  [  OK  ]
>         Unmounting file systems:  [  OK  ]
>         init: Re-executing /sbin/init
>         <silence>
> 
> Reverting just 25843:51090fe1ab97 "x86/HVM: assorted RTC emulation
> adjustments" on top of 35fa... => works again.

In that case I'll just revert it in -unstable too. No idea what's wrong
with it, though.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel