[Xen-bugs] [Bug 1727] Hypevisor hangs on boot.

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1727





------- Comment #3 from dmitry.trikoz@xxxxxxxxxxx  2011-01-25 13:20 -------
I tried booting with 'x2apic=off' or 'iommu=off' with the same result.
also reproduced the issue on xen-unstable.
The problem is easier to reproduce with 'cpuinfo=1' boot option.

After many tries I figured out exact line of code after which the system starts
hanging. So now I am able to expose the bug and reproduce the problem every
time I boot. To do that - just all these lines in xen/arch/x86/smpboot.c

--- xen/arch/x86/smpboot.c.original     2011-01-25 13:35:32.000000000 -0500
+++ xen/arch/x86/smpboot.c      2011-01-25 16:02:20.000000000 -0500
@@ -426,7 +426,9 @@
      */
     apic_icr_write(APIC_INT_LEVELTRIG | APIC_INT_ASSERT | APIC_DM_INIT,
                    phys_apicid);
-
+    for(i=0; i<200;i++) {
+       printk(" %d ====================================================\n",
i);
+    }
     Dprintk("Waiting for send to finish...\n");
     timeout = 0;
     do {

I also tried to force NMI on boot cpu while it's hanging. It appeared that boot
cpu doesn't react to NMIs while it's hanging. eventually it wakes up, and
handles pending NMI. This behaviour make me believe that hang happens in SMM
mode.

Also in the log I can see messages like this:

(XEN) MCE: The hardware reports a non fatal, correctable incident occurred on
CPU 1.
(XEN) Bank 2: d40000c000040150 at         8fbe5ae9

Address 8fbe5ae9 belongs to reserved BIOS area.
Decoding of code d40000c000040150 : Instruction fetch exception at Level 0

I have two machines of this type and I reproduced the problem on both of them.

As I said before, it looks very much like BIOS problem but linux kernel from
Centos 5.5 boots on my machines just fine, even with added printk loop (above).






-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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