From: Florian Manschwetus <florianmanschwetus@gmx.de>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Problem booting xen 4.1.2 on Athlon 64 X2
Date: Thu, 22 Dec 2011 00:49:59 +0100 [thread overview]
Message-ID: <4EF270A7.2010705@gmx.de> (raw)
In-Reply-To: <4EF0B034.1090708@gmx.de>
[-- Attachment #1.1: Type: text/plain, Size: 8990 bytes --]
Sending to devel, maybe a BUG?
Here are the details to the used mobo:
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 1004
Release Date: 03/26/2008
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 512 kB
Characteristics:
ISA is supported
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
BIOS Revision: 8.12
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: M2N-MX
Version: Rev 1.xx
Serial Number: MB-xxxxxxxxxx
Asset Tag: To Be Filled By O.E.M.
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: To Be Filled By O.E.M.
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Am 20.12.2011 16:56, schrieb Florian Manschwetus:
> Ok, I setup a serial so I can, give you a full copy of output (also
> added some debug options I found)
>
> Booting a command list
>
> Loading Xen 4.1.2 ...
> Loading Linux x86_64-3.1.5-gentoo ...
> Loading initial ramdisk ...
> __ __ _ _ _ ____
> \ \/ /___ _ __ | || | / | |___ \
> \ // _ \ '_ \ | || |_ | | __) |
> / \ __/ | | | |__ _|| |_ / __/
> /_/\_\___|_| |_| |_|(_)_(_)_____|
>
> (XEN) Xen version 4.1.2 (@) (gcc-Version 4.6.2 (Gentoo 4.6.2 p1.0,
> pie-0.4.5) ) Thu Dec 15 17:51:19 CET 2011
> (XEN) Latest ChangeSet: unavailable
> (XEN) Console output is synchronous.
> (XEN) Bootloader: GRUB 1.99
> (XEN) Command line: placeholder sync_console console_to_ring
> com1=115200,8n1 console=com1,vga loglvl=all lapic=debug
> apic_verbosity=debug apic=debug
> (XEN) Video information:
> (XEN) VGA is text mode 80x25, font 8x16
> (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds
> (XEN) EDID info not retrieved because no DDC retrieval method detected
> (XEN) Disc information:
> (XEN) Found 1 MBR signatures
> (XEN) Found 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN) 0000000000000000 - 000000000009fc00 (usable)
> (XEN) 000000000009fc00 - 00000000000a0000 (reserved)
> (XEN) 00000000000e0000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 00000000bffc0000 (usable)
> (XEN) 00000000bffc0000 - 00000000bffce000 (ACPI data)
> (XEN) 00000000bffce000 - 00000000bfff0000 (ACPI NVS)
> (XEN) 00000000bfff0000 - 00000000c0000000 (reserved)
> (XEN) 00000000fec00000 - 00000000fec01000 (reserved)
> (XEN) 00000000fee00000 - 00000000fef00000 (reserved)
> (XEN) 00000000ff780000 - 0000000100000000 (reserved)
> (XEN) 0000000100000000 - 0000000140000000 (usable)
> (XEN) ACPI: RSDP 000FB840, 0024 (r2 ACPIAM)
> (XEN) ACPI: XSDT BFFC0100, 004C (r1 A_M_I_ OEMXSDT 3000826 MSFT 97)
> (XEN) ACPI: FACP BFFC0290, 00F4 (r3 A_M_I_ OEMFACP 3000826 MSFT 97)
> (XEN) ACPI: DSDT BFFC05C0, 4E38 (r1 A0557 A0557000 0 INTL 20051117)
> (XEN) ACPI: FACS BFFCE000, 0040
> (XEN) ACPI: APIC BFFC0390, 0070 (r1 A_M_I_ OEMAPIC 3000826 MSFT 97)
> (XEN) ACPI: MCFG BFFC0400, 003C (r1 A_M_I_ OEMMCFG 3000826 MSFT 97)
> (XEN) ACPI: OEMB BFFCE040, 0060 (r1 A_M_I_ AMI_OEM 3000826 MSFT 97)
> (XEN) ACPI: HPET BFFC5400, 0038 (r1 A_M_I_ OEMHPET0 3000826 MSFT 97)
> (XEN) System RAM: 4095MB (4193660kB)
> (XEN) No NUMA configuration found
> (XEN) Faking a node at 0000000000000000-0000000140000000
> (XEN) Domain heap initialised
> (XEN) found SMP MP-table at 000ff780
> (XEN) DMI present.
> (XEN) APIC boot state is 'xapic'
> (XEN) Using APIC driver default
> (XEN) ACPI: PM-Timer IO Port: 0x508
> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[504,0], pm1x_evt[500,0]
> (XEN) ACPI: wakeup_vec[bffce00c], vec_size[20]
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> (XEN) Processor #0 15:3 APIC version 16
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> (XEN) Processor #1 15:3 APIC version 16
> (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 0 dfl dfl)
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
> (XEN) ACPI: IRQ0 used by override.
> (XEN) ACPI: IRQ9 used by override.
> (XEN) ACPI: IRQ14 used by override.
> (XEN) ACPI: IRQ15 used by override.
> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
> (XEN) ACPI: HPET id: 0x10de8201 base: 0xfed00000
> (XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
> (XEN) PCI: Not using MMCONFIG.
> (XEN) Table is not found!
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) mapped APIC to ffff82c3ffffe000 (fee00000)
> (XEN) mapped IOAPIC to ffff82c3ffffd000 (fec00000)
> (XEN) IRQ limits: 24 GSI, 376 MSI/MSI-X
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Detected 2611.867 MHz processor.
> (XEN) Initing memory sharing.
> (XEN) AMD K8 machine check reporting enabled
> (XEN) AMD-Vi: IOMMU not found!
> (XEN) I/O virtualisation disabled
> (XEN) Getting VERSION: 80050010
> (XEN) Getting VERSION: 80050010
> (XEN) Getting ID: 0
> (XEN) Getting LVT0: 700
> (XEN) Getting LVT1: 400
> (XEN) enabled ExtINT on CPU#0
> (XEN) ESR value before enabling vector: 0x00000004 after: 0x00000000
> (XEN) ENABLING IO-APIC IRQs
> (XEN) -> Using new ACK method
> (XEN) init IO_APIC IRQs
> (XEN) IO-APIC (apicid-pin) 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22,
> 2-23 not connected.
> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=0 apic2=-1 pin2=-1
> (XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> (XEN) ...trying to set up timer (IRQ0) through the 8259A ... failed.
> (XEN) ...trying to set up timer as Virtual Wire IRQ... failed.
> (XEN) ...trying to set up timer as ExtINT IRQ... failed :(.
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) IO-APIC + timer doesn't work! Boot with apic_verbosity=debug and
> send a report. Then try booting with the 'noapic'
> option****************************************
> (XEN)
> (XEN) Reboot in five seconds...
>
>
>
> Am 20.12.2011 12:01, schrieb Florian Manschwetus:
>> Adding apic_verbosity=debug gives me that (hope nothing miss-typed as I
>> have no serial console on this box). I found a lot of suggested
>> workarounds:
>> - noapic as suggested in output gives an noapic isn't support
>> - acpi_skip_timer_override has no effect at all
>>
>> Thx,
>> Florian
>>
>> (XEN) Initing memory sharing.
>> (XEN) AMD-Vi: IOMMU not found!
>> (XEN) I/O virtualisation disabled
>> (XEN) Getting VERSION: 8005010
>> (XEN) Getting VERSION: 8005010
>> (XEN) Getting ID: 0
>> (XEN) Getting LVT0: 700
>> (XEN) Getting LVT1: 400
>> (XEN) enabled ExtINT on CPU#0
>> (XEN) ESR value before enabling vector: 0x00000004 after: 0x0000000
>> (XEN) ENABLING IO-APIC IRQs
>> (XEN) -> Using new ACK method
>> (XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
>> (XEN)
>> (XEN) *****************************************************
>> (XEN) Panic on CPU 0:
>> (XEN) IO-APIC + timer doesn't work! Boot with apic_verbosity=debug and
>> send a report. Then try booting with hte 'noapic'
>> option****************************
>>
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
[-- Attachment #1.2: S/MIME Kryptografische Unterschrift --]
[-- Type: application/pkcs7-signature, Size: 2332 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next parent reply other threads:[~2011-12-21 23:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EF06B14.4070106@gmx.de>
[not found] ` <4EF0B034.1090708@gmx.de>
2011-12-21 23:49 ` Florian Manschwetus [this message]
2011-12-22 9:32 ` [Xen-users] Problem booting xen 4.1.2 on Athlon 64 X2 Jan Beulich
2011-12-22 9:49 ` Florian Manschwetus
[not found] ` <4EF2FCED.8010402@gmx.de>
2011-12-22 12:28 ` Jan Beulich
2011-12-22 13:11 ` Florian Manschwetus
2011-12-22 13:28 ` Jan Beulich
2011-12-22 13:32 ` Florian Manschwetus
2011-12-22 12:54 ` Igor Mammedov
2011-12-22 13:16 ` Florian Manschwetus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EF270A7.2010705@gmx.de \
--to=florianmanschwetus@gmx.de \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).