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/
Home Products Support Community News


[Xen-bugs] [Bug 1353] New: [ACPI] Dom0 hangs while starting CPU T-state

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1353] New: [ACPI] Dom0 hangs while starting CPU T-state
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 18 Sep 2008 23:50:59 -0700
Delivery-date: Thu, 18 Sep 2008 23:51:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: [ACPI] Dom0 hangs while starting CPU T-state
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: blocker
          Priority: P1
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: haicheng.li@xxxxxxxxx

Service OS (ia32/ia32e/IA64): ia32/ia32e
Guest OS (ia32/ia32e/IA64): 
Change Set: 18482/673
Hardware: Stoakley/Clovertown

Bug detailed description:
Dom0 will hang when starting T-state code on Stoakley/Clovertown and call

kernel BUG at /home/nightly/linux-2.6.18-xen.hg/drivers/acpi/osl.c:351!         
invalid opcode: 0000 [#1]                                                       
Modules linked in: processor i2c_ec fan container button battery asus_acpi ac
CPU:    0                                                                       
EIP:    0061:[<c0202e52>]    Tainted: GF     VLI                                
EFLAGS: 00010293   ( #1)                                            
EIP is at acpi_os_read_port+0x34/0x42                                           
eax: 00001010   ebx: 00001010   ecx: 00000005   edx: ec0b1e08                   
esi: ec0b1e08   edi: 00000004   ebp: eb8be000   esp: ec0b1ddc                   
ds: 007b   es: 007b   ss: 0069                                                  
Process modprobe (pid: 5240, ti=ec0b0000 task=eaac4e90 task.ti=ec0b0000)        
Stack: 00000000 00001010 eb8be000 ee337d52 00000001 ec0b1df0 00000001 eaac4e90  
       00000000 00000000 00000001 00000000 00000000 ffffffff eb8be000 ffffffed  
       00000140 ee337995 eb8be000 eb8be3a4 ec73a518 ee338724 00000080 00000008  
Call Trace:                                                                     
 [<ee337d52>] acpi_processor_get_throttling_ptc+0x71/0x184 [processor]          
 [<ee337995>] acpi_processor_get_throttling+0x3b/0x53 [processor]               
 [<ee338724>] acpi_processor_get_throttling_info+0x444/0x503 [processor]        
 [<ee3372ff>] acpi_processor_start+0x2b7/0x4b1 [processor]                      
 [<c021da6b>] acpi_start_single_object+0x1b/0x3b                                
 [<c021ea71>] acpi_bus_register_driver+0x8d/0xb7                                
 [<ee024048>] acpi_processor_init+0x48/0x8e [processor]                         
 [<c014289b>] sys_init_module+0x15b/0x1b60                                      
 [<c01059bf>] syscall_call+0x7/0xb                                              
Code: 85 d2 0f 44 f4 83 f9 10 74 11 83 f9 20 74 15 83 f9 08 75 17 89 da ec 88 0 
EIP: [<c0202e52>] acpi_os_read_port+0x34/0x42 SS:ESP 0069:ec0b1ddc              
 /etc/rc.d/rc.sysinit: line 395:  5240 Segmentation fault      modprobe

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>