[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush

  • To: Gerry Reno <greno@xxxxxxxxxxx>, Pasi Kärkkäinen <pasik@xxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Thu, 6 May 2010 23:21:37 -0700 (PDT)
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • Delivery-date: Thu, 06 May 2010 23:22:11 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=lxneAnT99avL7NXAxgovTi2NMC+jRUDvOS31PP3ULANSE32qNsZK/BaY+b8BGKh6j/Ngxpa+bb6ZHts66pNeX8SRcLlf1rXMKRdYEu7AuYP6XcgExs/4Wc4yUMtHCKcOzZ1Cgn3A4BV1McZfhvV2mLJVAlvU6L7kft1ifHIY100=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

>> /etc/xen/scripts/network-bridge: line 240: "sigerr" command not found.

apt-get install bridge-utils ( has been done ?)
If yes, you could try remove br0 declaration from /etc/network/interfaces
and edit properly /etc/xen/xend-config.sxp . Xen should bring up bridge
with no pain after reboot. Just service xend restart might not help.
I got this error this error as reaction on any mistake in Xen network config
on Lucid.

P.S. you could keep br0 declaration and commented out network bridging setup
in /etc/xen/xend-config.sxp. It works as well.

--- On Fri, 5/7/10, Pasi Kärkkäinen <pasik@xxxxxx> wrote:

From: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
To: "Gerry Reno" <greno@xxxxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
Date: Friday, May 7, 2010, 2:05 AM

On Thu, May 06, 2010 at 10:22:03PM -0400, Gerry Reno wrote:
> On 05/06/2010 08:21 PM, Gerry Reno wrote:
>> Ok, I tested with the new  (.config same)
>> Case 1:  Xen 4.0.0-rc8 / pv_ops dom0 kernel
>> Still pv_ops dom0 is not working properly.
>> There are still call trace and other errors.  The kernel does boot up 
>> but it takes again a long time to get the login prompt (about 3 mins). 
>> This is far longer than when I used pv_ops dom0.  Networking
>> does not start properly (only see 'lo' and 'virbr0'), so I have to
>> restart it manually and then I see my bridge 'br0' and 'eth0'.
>> Can't find device "br0"
>> /etc/xen/scripts/network-bridge: line 240: "sigerr" command not found.
>> And it is trying unsuccessfully to start some laptop feature like 
>> S99powernap (unknown job) and also S28-libvirt-bin fails (maybe 
>> network related?).
>> Case 2:  pv_ops domU kernel  (no xen dom0):
>> Now the straight linux kernel (no xen dom0) boots right up and goes to 
>> login prompt in normal timeframe.  Networking starts correctly.   
>> Things look pretty normal.
>> Observation:
>> I'm getting slightly different output on console and serial console.   
>> Some errors show on one but not the other.  Shouldn't these be
>> identical?
>> I'm attaching both serial console outputs.
>> menu.lst is same as before (just .12 instead of .10)
>> -Gerry
> And I'm attaching the syslog from Case 1 (pv_ops dom0).

You should be posting two things:

1) xm dmesg
2) dmesg

Aka the full boot log, from both Xen hypervisor and dom0 Linux kernel.

-- Pasi

Xen-devel mailing list

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.