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

Re: [Xen-devel] Bug: Windows 2003 fails to install on xen-unstable tip

>>> On 17.04.13 at 20:13, George Dunlap <george.dunlap@xxxxxxxxxxxxx> wrote:
> On 17/04/13 09:27, Jan Beulich wrote:
>>>>> On 16.04.13 at 16:35, George Dunlap <george.dunlap@xxxxxxxxxxxxx> wrote:
>>> On 16/04/13 15:34, Jan Beulich wrote:
>>>> Any of the RTC emulation changes since 4.2 would be possible
>>>> candidates, with mine much more likely than Tim's (since his mainly
>>>> fix issues mine introduced).
>>> If you've got a git hash tag for your first change, I can do a quick
>>> test to see if that's it.
>> The first of these commits is 2fe82ac11fd078485388fe7c5e8bc3b6ac9185b0.
> Here are the results of my bisect:
> 620d5dad54008e40798c4a0c4322aef274c36fa3 is the first bad commit
> commit 620d5dad54008e40798c4a0c4322aef274c36fa3
> Author: Jan Beulich <jbeulich@xxxxxxxx>
> Date:   Tue Feb 5 09:44:00 2013 +0100
>      x86/HVM: assorted RTC emulation adjustments

So as indicated yesterday, let's start with a debugging patch for
this and the FreeBSD problems. The patch is pretty trivial for
starters, but helped me spot other related problems with Linux
quite well. On Linux it didn't get very noisy, so output was easy
to collect and not very difficult to analyze - let's see whether
that also holds for Windows and FreeBSD...


--- a/xen/arch/x86/hvm/rtc.c
+++ b/xen/arch/x86/hvm/rtc.c
@@ -451,6 +451,7 @@ static int rtc_ioport_write(void *opaque
     case RTC_REG_B:
+printk("B=%02x [A:%02x B:%02x C:%02x]\n", data, s->hw.cmos_data[RTC_REG_A], 
orig, s->hw.cmos_data[RTC_REG_C]);//temp
         if ( data & RTC_SET )
             /* set mode: reset UIP mode */
@@ -629,6 +630,7 @@ static uint32_t rtc_ioport_read(RTCState
     case RTC_REG_C:
         ret = s->hw.cmos_data[s->hw.cmos_index];
         s->hw.cmos_data[RTC_REG_C] = 0x00;
+printk("C=%02x\n", ret);//temp

Attachment: x86-HVM-RTC.patch
Description: Text document

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.