#189 PAE host hanged on some platforms while booting guests
Environment:
Hardware: Clovertown/Bensley
Bug detailed description:
With recent commits, on clocertown system, we found that PAE host will hang while booting guests.
On the same machine if install the commit,51727a110220681f6f43b005d069e28c58f5d151, that built on 2007-11-22, the guest could be booted up successfully.
Woodrest system hasn't this problem.
It should be a regression issue introduced during 2007-11-12 to 2007-12-10.
log:
[root@vt-dp2 /]#
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: ------------[ cut here ]------------
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: invalid opcode: 0000 [#1]
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: SMP
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: CPU: 0
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: EIP: 0060:[<c011445d>]</c011445d> Not tainted VLI
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: EFLAGS: 00010206 (2.6.22-rc4 #7)
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: EIP is at kmap_atomic_prot+0x3f/0xa9
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: eax: 00000001 ebx: 00000163 ecx: c34afb80 edx: 00000003
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: esi: 80000000 edi: c0004dc0 ebp: 00000003 esp: ee727c68
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: Process qemu-system-x86 (pid: 6066, ti=ee726000 task=f4da7a90
task.ti=ee726000)
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: Stack: 80000000 00100027 00000100 0000045c c01144e3 00000163
80000000 c34afb80
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: f88a76ca f3434020 00000002 ee727d1c f88a7898 00100007
00100027 0045c027
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: 00000000 001000cf f3434020 00000100 00000007 00000007
0045c400 00000000
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: Call Trace:
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c01144e3>]</c01144e3> kmap_atomic+0x1c/0x20
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<f88a76ca>]</f88a76ca> paging32_cmpxchg_gpte+0x1a/0x47 [kvm]
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<f88a7898>]</f88a7898> paging32_walk_addr+0x11f/0x27f [kvm]
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<f88a833a>]</f88a833a> paging32_page_fault+0x5d/0x283 [kvm]
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<f88a7ece>]</f88a7ece> kvm_mmu_page_fault+0x20/0x9b [kvm]
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<f8832c4b>]</f8832c4b> kvm_handle_exit+0x71/0x8d [kvm_intel]
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<f8832edd>]</f8832edd> vmx_vcpu_run+0x13b/0x14e [kvm_intel]
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<f88a51bf>]</f88a51bf> kvm_arch_vcpu_ioctl_run+0x2a6/0x3ac [kvm]
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<f88a1fd8>]</f88a1fd8> kvm_vcpu_ioctl+0xcb/0x28f [kvm]
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c038bb2d>]</c038bb2d> __alloc_skb+0x49/0xf7
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c03887a7>]</c03887a7> sock_alloc_send_skb+0x6e/0x196
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c0210d43>]</c0210d43> copy_from_user+0x23/0x4f
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c0389b50>]</c0389b50> sock_def_readable+0x12/0x63
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c0161008>]</c0161008> core_sys_select+0x1e8/0x2c3
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c03860bd>]</c03860bd> sock_aio_write+0xc8/0xd4
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c0122969>]</c0122969> __dequeue_signal+0x10/0x11c
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c012274e>]</c012274e> recalc_sigpending+0xb/0x1d
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c0123f22>]</c0123f22> dequeue_signal+0x93/0x10d
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c0124b1b>]</c0124b1b> sys_rt_sigtimedwait+0xe3/0x234
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c012c36b>]</c012c36b> enqueue_hrtimer+0xde/0xe8
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c012ddf2>]</c012ddf2> getnstimeofday+0x30/0xbe
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c012c45e>]</c012c45e> ktime_get_ts+0x16/0x44
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<f88a1f0d>]</f88a1f0d> kvm_vcpu_ioctl+0x0/0x28f [kvm]
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c015ff1d>]</c015ff1d> do_ioctl+0x21/0x9f
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c0129222>]</c0129222> common_timer_get+0xd2/0xfa
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c01601d2>]</c01601d2> vfs_ioctl+0x237/0x249
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c0210f37>]</c0210f37> copy_to_user+0x25/0x3a
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c0160217>]</c0160217> sys_ioctl+0x33/0x4c
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: [<c010305e>]</c010305e> sysenter_past_esp+0x5f/0x85
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: =======================
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: Code: ff ff 40 14 64 a1 08 60 5f c0 6b c0 0d 8b 3d 54 86 60 c0
8d 2c 10 8d 04 ed 00 00 00 00 29 c7 83 3f 00 8b 47 04 75 04 85 c0 74 04 <0f> 0b
eb fe 8b 01 c1 05 80 ad 54 c0 8b
Message from syslogd@vt-dp2 at Wed Dec 12 15:47:56 2007 ...
vt-dp2 kernel: EIP: [<c011445d>]</c011445d> kmap_atomic_prot+0x3f/0xa9 SS:ESP
0068:ee727c68
Message from syslogd@vt-dp2 at Wed Dec 12 15:48:00 2007 ...
vt-dp2 kernel: ------------[ cut here ]------------
Message from syslogd@vt-dp2 at Wed Dec 12 15:48:00 2007 ...
vt-dp2 kernel: invalid opcode: 0000 [#2]
Message from syslogd@vt-dp2 at Wed Dec 12 15:48:00 2007 ...
vt-dp2 kernel: SMP
Message from syslogd@vt-dp2 at Wed Dec 12 15:48:00 2007 ...
vt-dp2 kernel: CPU: 0
Message from syslogd@vt-dp2 at Wed Dec 12 15:48:00 2007 ...
vt-dp2 kernel: EIP: 0060:[<c011445d>]</c011445d> Not tainted VLI
Related
Logged In: YES
user_id=1283543
Originator: YES
This issue is gone.