From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Cannot load latest 2.6.32.10 kernel on AMD quad-core Date: Mon, 3 May 2010 16:36:02 -0400 Message-ID: <20100503203559.GA9395@phenom.dumpdata.com> References: <4BD1DDF0.2050503@verizon.net> <20100503161849.GA32462@phenom.dumpdata.com> <4BDF0574.8070503@verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4BDF0574.8070503@verizon.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Gerry Reno Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Mon, May 03, 2010 at 01:18:44PM -0400, Gerry Reno wrote: > On 05/03/2010 12:18 PM, Konrad Rzeszutek Wilk wrote: >> On Fri, Apr 23, 2010 at 01:50:40PM -0400, Gerry Reno wrote: >> >>> 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 >>> >> Gerry, >> >> Can you attach your .config file ? I am not seeing it anywhere in the >> thread. Also is this x86_64 or i386 build? If it is i386 do you have >> CONFIG_NUMA enabled? If so, what happens if you disable that? >> >> Can you also tell me which Phenom it is? 940? >> >> > > Konrad, I attached my .config file and /proc/cpuinfo. The build was > x86_64. The cpu is AMD Phenom II x4 940. When I use your .config I get these: [ 10.781056] ------------[ cut here ]------------ [ 10.785736] WARNING: at /home/konrad/git/neb.64/linux-up/mm/vmalloc.c:1AMD-BOOT #7 [ 10.790016] Call Trace: [ 10.790016] [] warn_slowpath_common+0x7b/0xc0 [ 10.790016] [] warn_slowpath_null+0x14/0x20 [ 10.790016] [] vmap_page_range_noflush+0x2d9/0x370 [ 10.790016] [] ? __vmalloc_area_node+0x5f/0x190 [ 10.790016] [] ? xen_force_evtchn_callback+0xd/0x10 [ 10.790016] [] map_vm_area+0x32/0x50 [ 10.790016] [] __vmalloc_area_node+0x100/0x190 [ 10.790016] [] __vmalloc_area+0x17/0x20 [ 10.790016] [] module_alloc+0x5e/0x60 [ 10.790016] [] module_alloc_update_bounds+0x16/0x50 [ 10.790016] [] load_module+0x989/0x1ce0 [ 10.790016] [] ? vfs_read+0xb5/0x1a0 [ 10.790016] [] sys_init_module+0x79/0x250 [ 10.790016] [] system_call_fastpath+0x16/0x1b [ 10.790016] ---[ end trace a7919e7f17c0a727 ]--- FATAL: Error inserting xen_kbdfront (/lib/modules/2.6.32.12AMD-BOOT/kernel/drivers/input/xen-kbdfront.ko): Cannot allocate memory Is this about the same thing you see? (the calltrace being of interest here).