Bug 820495 - Cannot boot into Xen hypervisor for Fedora Core 17 Beta on AMD FX (Bulldozer)
Summary: Cannot boot into Xen hypervisor for Fedora Core 17 Beta on AMD FX (Bulldozer)
Keywords:
Status: CLOSED DUPLICATE of bug 801650
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jeff Law
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-10 07:45 UTC by Peter Teoh
Modified: 2016-11-24 15:55 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-05-11 19:03:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Peter Teoh 2012-05-10 07:45:59 UTC
Description of problem:

Install Fedora Core 17 Beta, and then install all the Xen patches via yum, and then reboot into Xen hypervisor. It crashed.

Version-Release number of selected component (if applicable):

Fedora Core 17 Beta 

How reproducible:

Install Fedora Core 17 Beta  (just downloaded and burn into CD few days back)
then install all the Xen patches via yum
Setup machine to log the error output via serial port.   Connect serial port to another machine.
Reboot into Xen hypervisor. It crashed.

The following is output at the console terminal:

[    3.846277] input: Dell Premium USB Optical Mouse as /devices/pci0000:00/0003
[    3.846486] generic-usb 0003:413C:3016.0001: input,hidraw0: USB HID v1.11 Mo0
[    3.883663] Freeing unused kernel memory: 16k freed                          
[    3.889637] Freeing unused kernel memory: 1516k freed                        
[    3.897359] init[1] trap invalid opcode ip:7f8b6dbc8895 sp:7fff46f1a018 erro]
[    3.908805] Kernel panic - not syncing: Attempted to kill init!              
[    3.914881] Pid: 1, comm: init Not tainted 3.3.4-3.fc17.x86_64 #1            
[    3.921127] Call Trace:                                                      
[    3.923722]  [<ffffffff815e221b>] panic+0xba/0x1c6                           
[    3.928665]  [<ffffffff8105aff1>] do_exit+0x8b1/0x8c0                        
[    3.933876]  [<ffffffff81169c90>] ? kmem_cache_free+0x20/0x100               
[    3.939866]  [<ffffffff8105b34f>] do_group_exit+0x3f/0xa0                    
[    3.945419]  [<ffffffff8106b065>] get_signal_to_deliver+0x1a5/0x5b0          
[    3.951846]  [<ffffffff81013228>] do_signal+0x68/0x7c0                       
[    3.957145]  [<ffffffff81009a50>] ? xen_clocksource_read+0x20/0x30           
[    3.963481]  [<ffffffff8108c84f>] ? __dequeue_entity+0x2f/0x50               
[    3.969470]  [<ffffffff81169c90>] ? kmem_cache_free+0x20/0x100               
[    3.975458]  [<ffffffff8108e0a3>] ? pick_next_task_fair+0x63/0x180           
[    3.981796]  [<ffffffff815ea567>] ? __schedule+0x747/0x7b0                   
[    3.987446]  [<ffffffff81013a30>] do_notify_resume+0x90/0xc0                 
[    3.993260]  [<ffffffff815ebd7c>] retint_signal+0x48/0x8c  

my CPU is AMD FX (6-core) and motherboard ASUS M5A97PRO, 8G RAM.

Comment 1 Peter Teoh 2012-05-10 07:49:41 UTC
The full version (not really) of the dmesg is here:

http://pastebin.com/qqXNd0sk

Comment 2 Peter Teoh 2012-05-10 12:43:05 UTC
Upon further analysis of the Xen dmesg (above link http://pastebin.com/qqXNd0sk) I think the problem started here too:

[    3.483814]   Magic number: 12:857:419                                      
[    3.511898] rtc_cmos 00:05: setting system clock to 2012-05-10 07:25:05 UTC )
[    3.520300] powernow-k8: Found 1 AMD FX(tm)-6100 Six-Core Processor         )
[    3.530752] powernow-k8: Core Performance Boosting: on.                      
[    3.536130] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects fou.
[    3.536131] [Firmware Bug]: powernow-k8: Try again with latest BIOS.        
[    3.550228] powernow-k8: invalid pstate 1 - bad value 1.                    
[    3.555693] powernow-k8: Please report to BIOS manufacturer                  
[    3.561416] powernow-k8: invalid pstate 2 - bad value 2.                    
[    3.566882] powernow-k8: Please report to BIOS manufacturer                  
[    3.572602] powernow-k8: invalid pstate 3 - bad value 3.                    
[    3.578068] powernow-k8: Please report to BIOS manufacturer                  
[    3.583790] powernow-k8: invalid pstate 4 - bad value 4.                    
[    3.589250] powernow-k8: Please report to BIOS manufacturer                  
[    3.594971] powernow-k8:    0 : pstate 0 (3300 MHz)                          
[    3.600077] powernow-k8: invalid pstate 1 - bad value 1.                    
[    3.605544] powernow-k8: Please report to BIOS manufacturer                  
[    3.611266] powernow-k8: invalid pstate 2 - bad value 2.                    
[    3.616733] powernow-k8: Please report to BIOS manufacturer                  
[    3.622482] powernow-k8: invalid pstate 3 - bad value 3.                    
[    3.627942] powernow-k8: Please report to BIOS manufacturer                  
[    3.633661] powernow-k8: invalid pstate 4 - bad value 4.                    
[    3.639126] powernow-k8: Please report to BIOS manufacturer                  
[    3.644851] powernow-k8:    0 : pstate 0 (3300 MHz)                          
[    3.649951] powernow-k8: invalid pstate 1 - bad value 1.                    
[    3.655416] powernow-k8: Please report to BIOS manufacturer                  
[    3.659097] usb 8-2: new low-speed USB device number 2 using xhci_hcd        
[    3.667738] powernow-k8: invalid pstate 2 - bad value 2.                    
[    3.673197] powernow-k8: Please report to BIOS manufacturer                  
[    3.678933] powernow-k8: invalid pstate 3 - bad value 3.                    
[    3.684406] powernow-k8: Please report to BIOS manufacturer                  
[    3.690146] powernow-k8: invalid pstate 4 - bad value 4.                    
[    3.695617] powernow-k8: Please report to BIOS manufacturer                  
[    3.701348] powernow-k8:    0 : pstate 0 (3300 MHz)                          
[    3.706395] usb 8-2: New USB device found, idVendor=413c, idProduct=3016    
[    3.706463] powernow-k8: invalid pstate 1 - bad value 1.                    
[    3.706465] powernow-k8: Please report to BIOS manufacturer                  
[    3.706466] powernow-k8: invalid pstate 2 - bad value 2.                    
[    3.706468] powernow-k8: Please report to BIOS manufacturer                  
[    3.706469] powernow-k8: invalid pstate 3 - bad value 3.                    
[    3.706470] powernow-k8: Please report to BIOS manufacturer                  
[    3.706472] powernow-k8: invalid pstate 4 - bad value 4.                    
[    3.706473] powernow-k8: Please report to BIOS manufacturer                  
[    3.706475] powernow-k8:    0 : pstate 0 (3300 MHz)                          
[    3.706537] powernow-k8: invalid pstate 1 - bad value 1.                    
[    3.706538] powernow-k8: Please report to BIOS manufacturer                  
[    3.706540] powernow-k8: invalid pstate 2 - bad value 2.                    
[    3.706541] powernow-k8: Please report to BIOS manufacturer                  
[    3.706543] powernow-k8: invalid pstate 3 - bad value 3.                    
[    3.706544] powernow-k8: Please report to BIOS manufacturer                  
[    3.706545] powernow-k8: invalid pstate 4 - bad value 4.                    
[    3.706547] powernow-k8: Please report to BIOS manufacturer                  
[    3.706548] powernow-k8:    0 : pstate 0 (3300 MHz)

Comment 3 Konrad Rzeszutek Wilk 2012-05-10 16:27:27 UTC

*** This bug has been marked as a duplicate of bug 801650 ***

Comment 4 Peter Teoh 2012-05-11 00:27:04 UTC
are u sure?   the glibc invalid opcode error arises out of Intel AVX instructions, but mine is AMD. I am not sure.

Comment 5 Peter Teoh 2012-05-11 06:06:54 UTC
ok, I am now reading comment #50 of:

https://bugzilla.redhat.com/show_bug.cgi?id=801650

have downloaded the xva and img files, but was not sure how can i apply these downloads?

*** This bug has been marked as a duplicate of bug 801650 ***

Comment 6 Konrad Rzeszutek Wilk 2012-05-11 11:40:05 UTC
Pls try out the RPMs menioned in the other bug. You also need to run dracut -f after the RPM install to recreate initrd.

If it doesn't work it might be that this is needed: https://launchpadlibrarian.net/104512210/fma4-depends-avx.diff to work on AMD machines.

I was hoping I could reproduce it on my boxes but I seem to lack Bulldozer type CPUs.

Comment 7 Jeff Law 2012-05-11 19:03:34 UTC

*** This bug has been marked as a duplicate of bug 801650 ***


Note You need to log in before you can comment on or make changes to this bug.