From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerry Reno Subject: Cannot load latest 2.6.32.10 kernel on AMD quad-core Date: Fri, 23 Apr 2010 13:50:40 -0400 Message-ID: <4BD1DDF0.2050503@verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org I previously had the pv_ops dom0 2.6.31.6 kernel built and running on my hardware (amd phenom ii x4 quad-core) just fine under karmic. But that kernel had issues with rxchecksumming. So I upgraded the server to lucid and am now trying to compile a new pv_ops dom0 kernel for it. Now, yesterday I carefully built the latest 2.6.32.10(xen/stable) pv_ops dom0 kernel twice. Once from the config in the email Lucid pv_ops dom0 howto and once from the lucid server config modified by adding all the XEN configurations. I get the same result both ways. After building the kernel, I try to start the pv_ops dom0 kernel as domU just to make sure it runs and it crashes right at the start of boot complaining like this: __vmallic_node+0xa2/0xb0 ? alloc_large_system_hash+0x15/0x21 ? inet_init+0x0/0x209 __vmalloc+0x22/0x30 alloc_large_system_hash+0x15/0x21a ? inet_init+0x0/0x209 ? inet_init+0x0/0x209 tcp_init+0xa3//0x37e inet_init+0x14b/0x209 do_one_initcall+0x3c/0x10a kernel_init+0x159/0x1af child_rip+0xa/0x20 Code: d0 49 8b 04 24 48 85 c0 75 ec eb c5 55 48 89 e5 48 8.... 9 5d e8 4c 89 65 f0 4c 89 6d f8 0f 1f 44 00 00 48 89 e5 48 8.... RIP [] __free_pages+0x1f/0x90 ---[ end trace e93713a9d40cd06d ]--- Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: swapper Tainted: G D W 2.6.32.10 #4 panic+0x78/0x136 ? mm_release+0x60/0x130 do_exit+0x6ca/0x7f0 oops_end+0xaf/0xf0 die+0x5b/0x90 do_general_protection+0x152/0x160 general_protection+0x25/0x30 ? __free_pages+0x1f/0x90 __vunmap+0x7a/0x110 vfree+0x2a/0x30 __vmalloc_area_node+0x15c/0x190 ? alloc_large_system_hash+0x15a/0x21a __vmalloc_node+0xa2/0xb0 ? alloc_large_system_hash+0x15a/0x21a ? inet_init+0x0/0x209 ? inet_init+0x0/0x209 tcp_init+0xa3//0x37e inet_init+0x14b/0x209 do_one_initcall+0x3c/0x10a kernel_init+0x159/0x1af child_rip+0xa/0x20 ? kernel_init+0x10/0x1af ? child_rip+0x0/0x20 I fired up the old 2.6.31.6 kernel with lucid and it boots just fine as domU. Can anyone shed some light on what may be the problem here and how I can build a working 2.6.32.10 pv_ops dom0 kernel for this hardware? -Gerry