From: "Cao,Bing Bu" <mars@linux.vnet.ibm.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] x86_64 linux kernel doesn't boot with -icount enabled
Date: Wed, 09 Nov 2011 18:42:56 +0800 [thread overview]
Message-ID: <4EBA5930.6060001@linux.vnet.ibm.com> (raw)
In-Reply-To: <4EBA4AC8.5050303@linux.vnet.ibm.com>
On 11/09/2011 05:41 PM, Cao,Bing Bu wrote:
> On 11/08/2011 11:52 PM, Max Filippov wrote:
>> With kernel command line of 'console=ttyS0 noapic=1 panic=1' patched
>> qemu boots up successfully with -icount, whereas unpatched qemu loops
>> infinitely.
>>
>> Looks like APIC emulation issue to me.
>>
> I'm trying to test issue using a 2.6.38 vmlinuz image.
> The image is a kernel image of a another ubuntu guest. I just copy it
> to host and use it directly.
>
> # /usr/local/bin/qemu-system-x86_64 -enable-kvm -m 1024 -kernel
> vmlinuz-2.6.38-8-generic -append 'ro quiet noacpi=1 ' -chardev
> stdio,id=mon0 -mon chardev=mon0
>
> The kernel can be successfully loaded and run normally until
> kernel_init(),and panic because there is no root file-system supplied.
>
> But add -icount option:
>
> # /usr/local/bin/qemu-system-x86_64 -enable-kvm -m 1024 -kernel
> vmlinuz-2.6.38-8-generic -append
> 'root=UUID=96bc04c5-410e-482a-82bf-95b2355552d6 ro quiet noacpi=1'
> -chardev stdio,id=mon0 -mon chardev=mon0 -icount auto
>
> The kernel can not be loaded successfully.
>
> loop in main_loop_wait().
>
>
When with option -icount,kernel message:
"HPET counter not counting. HPET disabled"
halt not continue running:
normally boot message:
< APIC calibration not consistent with PM-Timer: 92ms instead of 100ms^M
< APIC delta adjusted to PM-Timer: 6250004 (5750429)^M
< Performance Events: unsupported p6 CPU model 2 no PMU driver,
software events only.^M
< Brought up 1 CPUs^M
< Total of 1 processors activated (5183.86 BogoMIPS).^M
< devtmpfs: initialized^M
< print_constraints: dummy: ^M
< Time: 10:32:17 Date: 11/09/11^M
< NET: Registered protocol family 16^M
< EISA bus registered^M
< ACPI: bus type pci registered^M
< PCI: PCI BIOS revision 2.10 entry at 0xffe77, last bus=0^M
< PCI: Using configuration type 1 for base access^M
< bio: create slab <bio-0> at 0^M
< ACPI: Interpreter enabled^M
< ACPI: (supports S0 S3 S4 S5)^M
< ACPI: Using IOAPIC for interrupt routing^M
< ACPI: No dock devices found.^M
< HEST: Table not found.^M
< PCI: Ignoring host bridge windows from ACPI; if necessary, use
"pci=use_crs" and report a bug^M
< ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])^M
< pci 0000:00:01.3: quirk: [io 0xb000-0xb03f] claimed by PIIX4 ACPI^M
< pci 0000:00:01.3: quirk: [io 0xb100-0xb10f] claimed by PIIX4 SMB^M
< ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)^M
< ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)^M
< ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)^M
< ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)^M
< ACPI: PCI Interrupt Link [LNKS] (IRQs 9) *0^M
Maybe right,it is a ACPI issue.
--
Best Regards,
Cao,Bing Bu
next prev parent reply other threads:[~2011-11-09 10:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 13:45 [Qemu-devel] x86_64 linux kernel doesn't boot with -icount enabled Max Filippov
2011-11-08 14:03 ` Max Filippov
2011-11-08 14:14 ` Paolo Bonzini
2011-11-08 14:21 ` Max Filippov
2011-11-08 15:52 ` Max Filippov
2011-11-09 9:41 ` Cao,Bing Bu
2011-11-09 10:42 ` Cao,Bing Bu [this message]
2011-11-09 10:50 ` Max Filippov
2011-11-10 2:54 ` Cao,Bing Bu
2011-11-10 9:05 ` Max Filippov
2011-11-10 9:15 ` Paolo Bonzini
2011-11-10 10:25 ` Max Filippov
2011-11-10 11:25 ` Paolo Bonzini
2011-11-11 7:09 ` [Qemu-devel] [PATCH] Give an error when using -icount option with kvm accelerator Cao,Bing Bu
2011-11-14 6:17 ` Cao,Bing Bu
2011-11-13 21:57 ` [Qemu-devel] x86_64 linux kernel doesn't boot with -icount enabled Benoît Canet
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=4EBA5930.6060001@linux.vnet.ibm.com \
--to=mars@linux.vnet.ibm.com \
--cc=jcmvbkbc@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).