WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/s

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Thu, 22 Apr 2010 13:32:02 -0700 (PDT)
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, KeYu <ke.yu@xxxxxxxxx>
Delivery-date: Thu, 22 Apr 2010 13:44:48 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1271968322; bh=lruWnZIOHhlMDUnarC5cmOc5r4kW4/+j7z7GV7RCe7s=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=FpXiTesqL/pFoeGBdFEd34i5Yo/NlNIETJywIoaGFAqx5P9JQdGNF2TjWCCK0syBj/sxh2Gl6A6wuP/HIbtcXJJpanFHznoQQCuieOorvi1KbdBgeDplls8WX614hKHMm29Yg3RkGtLc/i/sFPqXlekMXm7Ay2xd3A1A70+dqT0=
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=t+Vp+eRI7gdePEFIHRjQsJw9I0gEPWBaIw4npMs4RDmBHaD9gNSyNpti8daRKKctDNOd9a12Yn+Yt0eM7eUXaa0nMieV41Pi9RYh1iP0JY8G78iHkus5yBk8RujapWYMsUhxsMhlXL7UvkPEPUaYM7TfNmT+xDVP/5YUpW6vgVQ=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100422192345.GG31220@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Not sure which one of those :-

LD [M]  drivers/acpi/processor.ko
LD [M]  drivers/xen/acpi_processor.ko

I believe second one causes issue under Xen 4.0 Hypervisor

Boris

--- On Thu, 4/22/10, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:

From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "KeYu" <ke.yu@xxxxxxxxx>
Date: Thursday, April 22, 2010, 3:23 PM

On Thu, Apr 22, 2010 at 09:56:44AM -0700, Boris Derzhavets wrote:
> Disabling option <> processor allows to load 2.6.32.10 on ASUS P5Q-E :-
>
> [*] Power management and ACPI options  ---> 
>    [*] ACPI (Advanced Configuration and Power Interface) Support  --->
>        [*]   Deprecated /proc/acpi files                                                     
>        [*]   Deprecated power /proc/acpi directories                                        
>                 < >   ACPI 4.0 power meter                                                           
>                 [*]   Future power /sys interface                                                    
>                 [*]   Deprecated /proc/acpi/event support                                            
>                 <*>   AC Adapter                                                                     
>                 <*>   Battery                                                                        
>                 <*>   Button                                                                         
>                 <M>   Video                                                                          
>                 <*>   Fan                                                                            
>                 -*-   Dock                                                                           
> ->          < >   Processor                                                                    

Can you make that be a module instead? And when the machine has booted
up, try to load the module (you might need to rename the modele to say
processor.ko.old so that udev won't automatically load it)?

And also compile the kernel with CONFIG_ACPI_DEBUG=y and
CONFIG_ACPI_DEBUG_FUNC_TRACE=y

Lastly, when you boot your machine, please add these flags
to your Linux kernel command line:

acpi.debug_level=0xffffffff acpi.debug_layer=0x2 initcall_debug

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>