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

Re: [Xen-devel] [xen-unstable test] 8289: tolerable FAIL - PUSHED

To: xen.org <ian.jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [xen-unstable test] 8289: tolerable FAIL - PUSHED
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Mon, 8 Aug 2011 16:04:12 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 08 Aug 2011 08:07:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <osstest-8289-mainreport@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Newsgroups: chiark.mail.xen.devel
References: <osstest-8289-mainreport@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
xen.org writes ("[Xen-devel] [xen-unstable test] 8289: tolerable FAIL - 
PUSHED"):
>  test-amd64-i386-xl         5 xen-boot                  fail    like 8244

This is not a heisenbug.  It is a reproducible failure to boot on
certain hardware.  It just looks like a heisenbug to the tester
because it doesn't runs the test on the same host each time.

It passes on
  earwig, gall-mite, itch-mite               All of which are Intel machines
It fails on
  leaf-beetle, potato-beetle, woodlouse      All of which are AMD machines

Here is an example of a failure:

http://www.chiark.greenend.org.uk/~xensrcts/logs/8289/test-amd64-i386-xl/info.html

The serial log just stops after this:

Aug  3 19:40:02.917190 (XEN) Processor #21 0:8 APIC version 16
Aug  3 19:40:02.924192 (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
Aug  3 19:40:02.932202 (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Aug  3 19:40:02.940214 (XEN) Overriding APIC driver with bigsmp
Aug  3 19:40:02.940234 (XEN) ACPI: IOAPIC (id[0x16] address[0xfec00000] 
gsi_base[0])
Aug  3 19:40:02.948192 (XEN) IOAPIC[0]: apic_id 22, version 17, address 
0xfec00000, GSI 0-15
Aug  3 19:40:02.957194 (XEN) ACPI: IOAPIC (id[0x17] address[0xfec01000] 
gsi_base[16])
Aug  3 19:40:02.968200 (XEN) IOAPIC[1]: apic_id 23, version 17, address 
0xfec01000, GSI 16-31
Aug  3 19:40:02.976203 (XEN) ACPI: IOAPIC (id[0x18] address[0xfec02000] 
gsi_base[32])
Aug  3 19:40:02.977192 (XEN) IOAPIC[2]: apic_id 24, version 17, address 
0xfec02000, GSI 32-47
Aug  3 19:40:02.985195 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 
dfl dfl)
Aug  3 19:40:02.996197 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 
low level)
Aug  3 19:40:03.001201 (XEN) ACPI: IRQ0 used by override.
Aug  3 19:40:03.005185 (XEN) ACPI: IRQ2 used by override.
Aug  3 19:40:03.012196 (XEN) ACPI: IRQ9 used by override.
Aug  3 19:40:03.013185 (XEN) Enabling APIC mode:  Phys.  Using 3 I/O APICs
Aug  3 19:40:03.021188 (XEN) ACPI: HPET id: 0x1166a201 base: 0xfed00000

The test runner's attempt to get debug key output (which start at
19:45:12) didn't succeed.  Results on other machines are similar.

Ian.

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