From: Jan Luebbe <jluebbe@lasnet.de>
To: kvm-devel@lists.sourceforge.net
Subject: kvm-67: kernel panic while booting debian-40r3-i386-businesscard.iso
Date: Mon, 28 Apr 2008 18:50:22 +0200 [thread overview]
Message-ID: <1209401422.30950.27.camel@polaris> (raw)
[-- Attachment #1: Type: text/plain, Size: 2546 bytes --]
Hi!
I'm preparing kvm-67 for debian. While testing i noticed a problem:
When booting the debian installer from the official CD [1] this problem:
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
Compat vDSO mapped to ffffe000.
CPU: Intel QEMU Virtual CPU version 0.9.1 stepping 03
Checking 'hlt' instruction... OK.
ACPI: Core revision 20060707
invalid opcode: 0000 [#1]
Modules linked in:
CPU: 0
EIP: 0060:[<c01467be>] Not tainted VLI
EFLAGS: 00010202 (2.6.18-6-486 #1)
EIP is at kmem_cache_zalloc+0x2a/0x53
eax: 0000000a ebx: c7fe75c0 ecx: c7fe9e00 edx: 000000d0
esi: c02c50c0 edi: 00000202 ebp: c036bd20 esp: c030ff80
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, ti=c030e000 task=c02bd7a0 task.ti=c030e000)
Stack: 00000004 c028f968 c029c49a c0146d5b 00000004 00000000 00000014
c029c499
00000046 c030ffc4 00000046 00000046 00000000 00000000 00039100
c0302800
003a7007 c01c7e90 00000000 00000000 00000000 c01db3b5 c0378ce8
c01dcf07
Call Trace:
[<c0146d5b>] kmem_cache_create+0x15e/0x410
[<c01c7e90>] acpi_os_create_cache+0x10/0x1c
[<c01db3b5>] acpi_ut_create_caches+0x19/0x93
[<c01dcf07>] acpi_ut_init_globals+0x5/0x1de
[<c01dc5d1>] acpi_initialize_subsystem+0x1b/0x56
[<c0323a73>] acpi_early_init+0x45/0xfe
[<c03105f5>] start_kernel+0x26b/0x272
Code: c3 57 56 53 89 c6 9c 5f fa 8b 08 83 39 00 74 12 c7 41 0c 01 00 00
00 8b 01
48 89 01 8b 5c 81 10 eb 07 e8 a5 fb ff ff 89 c3 57 9d <0f> 0d 0b 90 85
db 74 1b
8b 56 10 31 c0 89 d1 c1 e9 02 89 df f3
EIP: [<c01467be>] kmem_cache_zalloc+0x2a/0x53 SS:ESP 0068:c030ff80
<0>Kernel panic - not syncing: Attempted to kill the idle task!
Similar errors in acpi-functions also happen with all other linux
kernels i have here (2.6.22-25). -no-acpi makes no difference.
Userspace 66 works (with -66 and -67 kernel module), userspace 67 has
this problem (with -66 and -67 kernel module).
Host is an ThinkPad X60 (Core Duo), kernel 2.6.25.
I've tried to bisect the userspace, but the bug seems to be introduced
with the merge from qemu-cvs. Any tips on how to bisect the individual
commits on the qemu-cvs branch?
Thanks,
Jan Lübbe
[1]: http://cdimage.debian.org/debian-cd/4.0_r3/i386/iso-cd/debian-40r3-i386-businesscard.iso
[-- Attachment #2: Type: text/plain, Size: 320 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
next reply other threads:[~2008-04-28 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 16:50 Jan Luebbe [this message]
2008-04-28 20:06 ` kvm-67: kernel panic while booting debian-40r3-i386-businesscard.iso Joerg Roedel
2008-05-02 10:12 ` Avi Kivity
2008-05-04 22:38 ` Jan Luebbe
2008-05-06 14:32 ` Avi Kivity
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=1209401422.30950.27.camel@polaris \
--to=jluebbe@lasnet.de \
--cc=kvm-devel@lists.sourceforge.net \
/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