WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [linux bisection] complete test-amd64-i386-win-vcpus1

Ian Jackson writes ("Re: [linux bisection] complete 
test-amd64-i386-win-vcpus1"):
> xen.org writes ("[linux bisection] complete test-amd64-i386-win-vcpus1"):
> > *** Found and reproduced problem changeset ***
> > 
> >   Bug is in tree:  xen http://hg.uk.xensource.com/xen-unstable.hg
> >   Bug introduced:  fbf3768e5934
> >   Bug not present: 3795d79c740b
> > 
> > 
> >   changeset:   23733:fbf3768e5934
> >   user:        Wei Wang <wei.wang2@xxxxxxx>
> >   date:        Thu Jul 21 14:37:47 2011 +0100
> >       
> >       AMD IOMMU: remove global interrupt remapping table
> >       
> >       ...use per-device table instead.
> >       
> >       This should work with per-cpu IDTs.  We are safe to remove global
> >       table since SATA device id issue doee not appear in recent
> >       production BIOS.
> >       
> >       Signed-off-by: Wei Wang <wei.wang2@xxxxxxx>
> 
> This is a bit suspicious.  I'm not sure I believe it.  If nothing
> else, it seems confused about which branch it was testing.

Having looked into this it seems to be true.  This has broken booting
on at least one Intel machine.

Logs here of a failure:

http://www.chiark.greenend.org.uk/~xensrcts/logs/8342/test-amd64-i386-win-vcpus1/

We seem to get this:

Aug  9 06:20:18.307583 (XEN) ENABLING IO-APIC IRQs
Aug  9 06:20:18.311548 (XEN)  -> Using new ACK method
Aug  9 06:20:18.315149 (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 
pin2=-1
Aug  9 06:20:18.323569 (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 
0x00a0, fault address = 0xfdf8f00144
Aug  9 06:20:18.339533 (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 
0x00a0, fault address = 0xfdf8f00144
Aug  9 06:20:18.355630 (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 
0x00a0, fault address = 0xfdf8f00144
Aug  9 06:20:18.367603 (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 
0x00a0, fault address = 0xfdf8f00144
Aug  9 06:20:18.387207 (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 
0x00a0, fault address = 0xfdf8f00144
Aug  9 06:20:18.399137 (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 
0x00a0, fault address = 0xfdf8f00144
Aug  9 06:20:18.407608 (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 
0x00a0, fault address = 0xfdf8f00144
Aug  9 06:20:18.427206 (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 
0x00a0, fault address = 0xfdf8f00144
[ loads more ]

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>