|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 1263] New: Xen HV crashes at booting on 32PAE host if vtd is enabled
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1263 Summary: Xen HV crashes at booting on 32PAE host if vtd is enabled Product: Xen Version: unstable Platform: x86 OS/Version: All Status: NEW Severity: blocker Priority: P1 Component: Hypervisor AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx ReportedBy: haicheng.li@xxxxxxxxx Environment: ------------ Service OS (ia32/ia32e/IA64): ia32pae Guest OS (ia32/ia32e/IA64): Change Set: 17731 Hardware: Stoakley/Clovertown mechine total memory: 8G dom0 memory: 1G Bug detailed description: -------------------------- Withe vtd enabled, Xen HV crashes while dom0 is getting IP information for eth0... if set iommu=0 in grub, no crash, dom0 can boot up. Reproduce steps: ---------------- 1. install c/s 17731 on 32pae host on stoakley machine. 2. reboot machine. Current result: ---------------- Expected result: ---------------- Basic root-causing log: ---------------------- INIT: version 2.86 booting Welcome to Red Hat Enterprise Linux Server Press 'I' to enter interactive startup. Real Time Clock Driver v1.12ac Setting clock (utc): Tue May 27 08:51:40 CST 2008 [ OK ] Starting udev: [ OK ] Loading default keymap (us): [ OK ] Setting hostname vt-dp1: [ OK ] No devices found Setting up Logical Volume Management: No volume groups found [ OK ] Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 /: clean, 168071/2560864 files, 1291183/2560351 blocks [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling local filesystem quotas: [ OK ] rm: cannot remove `/var/run/xend/boot': Is a directory Enabling /etc/fstab swaps: [ OK ] INIT: Entering runlevel: 3 Entering non-interactive startup Applying Intel CPU microcode update: FATAL: Module microcode not found. ERROR: Module microcode does not exist in /proc/modules Starting background readahead: [ OK ] Checking for hardware changes [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: Determining IP information for eth0...(XEN) [VT-D]iommu.c:836: iommu_page_fault0 (XEN) [VT-D]iommu.c:808: iommu_fault_status: Primary Pending Fault (XEN) [VT-D]iommu.c:792: iommu_fault:DMA Read: 0:1e.0 addr 200925000 REASON 6 i0 (XEN) print_vtd_entries: iommu = ffbdad00 bdf = 0:1e:0 gmfn = 200925 (XEN) root_entry = fefa9000 (XEN) root_entry[0] = 22b001001 (XEN) context = fefaa000 (XEN) context[f0] = 102_22cafa001 (XEN) l4 = 2bafa000 (XEN) l4_index = 0 (XEN) ----[ Xen-3.3-unstable x86_32p debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) EIP: e008:[<ff1249b3>] print_vtd_entries+0x1f3/0x300 (XEN) EFLAGS: 00010282 CONTEXT: hypervisor (XEN) eax: 00000000 ebx: 2bafa000 ecx: 0000000a edx: 00000000 (XEN) esi: 00000004 edi: 00000000 ebp: fefaa000 esp: ff1efe74 (XEN) cr0: 8005003b cr4: 000026f0 cr3: 00100120 cr2: 2bafa000 (XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ff1efe74: (XEN) ff1985db 00000004 00000000 00000000 2cafa001 00000002 00000000 ff11deda (XEN) ffbd6080 00000008 ff1ffca0 fefa9000 2b001001 00000002 00200925 00000000 (XEN) fefaa000 00000002 00000007 ffbdad00 00000006 00200925 00000000 ff12188b (XEN) ffbdad00 00000000 000000f0 00200925 00000000 0000001e 00000000 00925000 (XEN) 00000002 00000006 fff74000 ffbc3480 ff110e44 ff27380c 000000f0 ffbdad00 (XEN) 00000000 c0000006 00000000 00000000 000000f0 000000c0 00000206 ff1effb4 (XEN) ff1eff78 ffbdbd00 ffbb2080 ff134b85 000000b8 ffbdad00 ff1eff78 0000000c (XEN) ff1298f5 000000b8 ff210100 ff1effb4 0000e010 0000e010 ffbb2080 ff12e592 (XEN) ff1eff78 ff1effb4 00000000 00000000 ff1cb454 ff1e8080 ffbb2080 00000000 (XEN) 00b80000 ff12bf5f 0000e008 00000246 ff12befa ffbb2080 00000000 ff1effb4 (XEN) 00000001 00000000 00000001 00000007 00000000 c03f2180 00000000 000e0014 (XEN) c01013a7 00000061 00000246 ed7b1f88 00000069 0000007b 0000007b 00000000 (XEN) 00000000 00000000 ff1e8080 (XEN) Xen call trace: (XEN) [<ff1249b3>] print_vtd_entries+0x1f3/0x300 (XEN) [<ff11deda>] __putstr+0x4a/0x50 (XEN) [<ff12188b>] iommu_page_fault+0x28b/0x380 (XEN) [<ff110e44>] csched_tick+0x154/0x5e0 (XEN) [<ff134b85>] do_IRQ+0x1b5/0x210 (XEN) [<ff1298f5>] reprogram_timer+0x75/0xd0 (XEN) [<ff12e592>] common_interrupt+0x52/0x60 (XEN) [<ff12bf5f>] default_idle+0x1f/0x30 (XEN) [<ff12befa>] idle_loop+0x3a/0x80 (XEN) (XEN) Pagetable walk from 2bafa000: (XEN) L3[0x000] = 00000000001f4001 55555555 (XEN) L2[0x15d] = 0000000000000000 ffffffff (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) FATAL PAGE FAULT (XEN) [error_code=0000] (XEN) Faulting linear address: 2bafa000 (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... -- 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
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |