[lkml]   [2007]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [kvm-devel] [BUG] Oops with KVM-27

    Il Mon, Jun 04, 2007 at 12:35:37PM +0300, Avi Kivity ha scritto:
    > Luca Tettamanti wrote:
    > >Hello,
    > >my kernel just exploded :)
    > >
    > >The host is running 2.6-git-current, with KVM modules from KVM-27
    > >package. kernel is 32bit, SMP, with PREEMPT enabled, no HIGHMEM (but I'm
    > >using CONFIG_VMSPLIT_3G_OPT=y). The CPU is a Core2 (hence I'm using
    > >kvm-intel).
    > >Guest was a Fedora7 setup DVD, which died somewhere during the
    > >installation (anaconda was already active at that point). Bad news is
    > >that I cannot reproduce the bug :|
    > >
    > Fortunately the trace clearly shows the problem (out of mmu working
    > memory on guest context switch). The attached patch should fix it. Let
    > me know if it works for you.

    It turned out that it was somewhat reproducible with fedora installer.
    With your patch it doesn't oops anymore.

    While doing repeated tests with the installer I ran into another
    (unrelated) problem. Sometimes the guest kernel hangs at boot at:

    NET: Registered protocol family 2

    with any kind of networking options (except for -net none, which works).
    With -no-kvm it boots with any networking option.

    The only difference in dmesg is that when KVM is enable the guest uses
    the TSC:

    NetLabel: unlabeled traffic allowed by default
    -Time: tsc clocksource has been installed.
    PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0

    For reference this is the command line that I'm using:

    ./kvm-27/qemu/i386-softmmu/qemu -hda /home/kronos/tmp/fedora.img
    -cdrom /home/kronos/tmp/boot.iso -boot d -net tap -net nic -m 256

    and boot.iso is the fedora7 net install image (you can find it on any
    mirror: fedora/linux/releases/7/Fedora/arch/os/images/boot.iso).

    The guest kernel doesn't respond to sysrq, so I don't known exactly
    where it's hanging. The stack trace on the host seems rather

    qemu S 00000002 2404 18905 7312 (NOTLB)
    dca4db48 00000086 00000000 00000002 b0478900 eec4a0f0 b02f418b b0478900
    0000000a 00000000 eec4a0f0 ef31ca70 267db8c3 000008c7 00003ea3 eec4a1fc
    b1810980 efcc62a0 b0478900 b0129580 00000000 00000292 dca4db58 0023935c
    Call Trace:
    [<b02f418b>] _spin_unlock_irqrestore+0x34/0x58
    [<b0129580>] __mod_timer+0x9d/0xa7
    [<b02f2258>] schedule_timeout+0x70/0x8d
    [<b02f418b>] _spin_unlock_irqrestore+0x34/0x58
    [<b01291e0>] process_timeout+0x0/0x5
    [<b02f2253>] schedule_timeout+0x6b/0x8d
    [<b0171eb1>] do_select+0x399/0x3e7
    [<b0172496>] __pollwait+0x0/0xac
    [<b011c720>] default_wake_function+0x0/0xc
    [<b0171766>] free_poll_entry+0xe/0x16
    [<b0171786>] poll_freewait+0x18/0x4c
    [<b0171abc>] do_sys_poll+0x302/0x327
    [<b0172496>] __pollwait+0x0/0xac
    [<b011c720>] default_wake_function+0x0/0xc
    [<b011b26a>] task_rq_lock+0x36/0x5d
    [<b02f3c59>] _spin_lock+0x33/0x3e
    [<b02f4197>] _spin_unlock_irqrestore+0x40/0x58
    [<b011c716>] try_to_wake_up+0x325/0x32f
    [<b013b017>] mark_held_locks+0x39/0x53
    [<b02f418b>] _spin_unlock_irqrestore+0x34/0x58
    [<b0103ec0>] restore_nocheck+0x12/0x15
    [<b013b1ee>] trace_hardirqs_on+0x11a/0x13d
    [<b010679a>] do_IRQ+0xc4/0xde
    [<b0103ec0>] restore_nocheck+0x12/0x15
    [<b01721ed>] core_sys_select+0x2ee/0x30f
    [<b0103189>] setup_sigcontext+0x105/0x189
    [<b02f41cf>] _spin_unlock_irq+0x20/0x41
    [<b013b1ee>] trace_hardirqs_on+0x11a/0x13d
    [<b0103a56>] do_notify_resume+0x5d1/0x611
    [<b02f41da>] _spin_unlock_irq+0x2b/0x41
    [<b01039b4>] do_notify_resume+0x52f/0x611
    [<b0103ec0>] restore_nocheck+0x12/0x15
    [<b010898b>] convert_fxsr_from_user+0x26/0xe6
    [<b01725e6>] sys_select+0xa4/0x187
    [<b0103ec0>] restore_nocheck+0x12/0x15
    [<b013b1ee>] trace_hardirqs_on+0x11a/0x13d
    [<b0103e78>] syscall_call+0x7/0xb
    qemu S CF9E5DC0 2996 18911 7312 (NOTLB)
    cf9e5dd4 00000082 00000002 cf9e5dc0 cf9e5dbc 00000000 b013b1ee cf9e5ea0
    00000007 00000001 d252b4f0 b194c030 70a8bf29 000008ac 0000a554 d252b5fc
    b181a980 efcc62a0 00232330 00000003 00000000 00000000 cf9e5ea0 efcc62d4
    Call Trace:
    [<b013b1ee>] trace_hardirqs_on+0x11a/0x13d
    [<b013de28>] futex_wait+0x251/0x3ed
    [<b0134156>] hrtimer_wakeup+0x0/0x18
    [<b013de19>] futex_wait+0x242/0x3ed
    [<b011c720>] default_wake_function+0x0/0xc
    [<b013e906>] do_futex+0x6c/0xaad
    [<b012acf7>] sys_rt_sigqueueinfo+0x44/0x4e
    [<b0135a4e>] getnstimeofday+0x30/0xbe
    [<b0134627>] ktime_get_ts+0x16/0x44
    [<b013f40f>] sys_futex+0xc8/0xda
    [<b0103e78>] syscall_call+0x7/0xb

    I'm attaching the dmesg for both -kvm and -no-kvm cases.

    "La teoria e` quando sappiamo come funzionano le cose ma non funzionano.
    La pratica e` quando le cose funzionano ma non sappiamo perche`.
    Abbiamo unito la teoria e la pratica: le cose non funzionano piu` e non
    sappiamo il perche`." -- A. Einstein
    Linux version 2.6.21-1.3194.fc7 ( (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Wed May 23 22:11:19 EDT 2007

    BIOS-provided physical RAM map:

    sanitize start

    sanitize end

    copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1

    copy_e820_map() type is E820_RAM

    copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2

    copy_e820_map() start: 00000000000e8000 size: 0000000000018000 end: 0000000000100000 type: 2

    copy_e820_map() start: 0000000000100000 size: 000000000ff00000 end: 0000000010000000 type: 1

    copy_e820_map() type is E820_RAM

    copy_e820_map() start: 00000000fffc0000 size: 0000000000040000 end: 0000000100000000 type: 2

    BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)

    BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)

    BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved)

    BIOS-e820: 0000000000100000 - 0000000010000000 (usable)

    BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)

    0MB HIGHMEM available.

    256MB LOWMEM available.

    Using x86 segment limits to approximate NX protection

    Entering add_active_range(0, 0, 65536) 0 entries of 256 used

    Zone PFN ranges:

    DMA 0 -> 4096

    Normal 4096 -> 65536

    HighMem 65536 -> 65536

    early_node_map[1] active PFN ranges

    0: 0 -> 65536

    On node 0 totalpages: 65536

    DMA zone: 32 pages used for memmap

    DMA zone: 0 pages reserved

    DMA zone: 4064 pages, LIFO batch:0

    Normal zone: 480 pages used for memmap

    Normal zone: 60960 pages, LIFO batch:15

    HighMem zone: 0 pages used for memmap

    DMI not present or invalid.

    Using APIC driver default

    ACPI: no DMI BIOS year, acpi=force is required to enable ACPI

    ACPI: Disabling ACPI support

    Allocating PCI resources starting at 20000000 (gap: 10000000:effc0000)

    Built 1 zonelists. Total pages: 65024

    Kernel command line: initrd=initrd.img console=tty0 console=ttyS0 debug BOOT_IMAGE=vmlinuz

    Found and enabled local APIC!

    mapped APIC to ffffd000 (fee00000)

    Enabling fast FPU save and restore... done.

    Enabling unmasked SIMD FPU exception support... done.

    Initializing CPU#0

    CPU 0 irqstacks, hard=c076e000 soft=c074e000

    PID hash table entries: 1024 (order: 10, 4096 bytes)

    Detected 2135.363 MHz processor.

    Console: colour VGA+ 80x25

    Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

    Memory: 249556k/262144k available (2037k kernel code, 12036k reserved, 1069k data, 236k init, 0k highmem)

    virtual kernel memory layout:

    fixmap : 0xffc55000 - 0xfffff000 (3752 kB)

    pkmap : 0xff800000 - 0xffc00000 (4096 kB)

    vmalloc : 0xd0800000 - 0xff7fe000 ( 751 MB)

    lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)

    .init : 0xc070e000 - 0xc0749000 ( 236 kB)

    .data : 0xc05fd722 - 0xc0708cb4 (1069 kB)

    .text : 0xc0400000 - 0xc05fd722 (2037 kB)

    Checking if this processor honours the WP bit even in supervisor mode... Ok.

    Calibrating delay using timer specific routine.. 17122.84 BogoMIPS (lpj=8561424)

    Security Framework v1.0.0 initialized

    SELinux: Initializing.

    SELinux: Starting in permissive mode

    selinux_register_security: Registering secondary module capability

    Capability LSM initialized as secondary

    Mount-cache hash table entries: 512

    CPU: After generic identify, caps: 0781abfd 00000000 00000000 00000000 00000001 00000000 00000000

    CPU: L1 I cache: 8K

    CPU: L2 cache: 128K

    CPU: After all inits, caps: 0781a3fd 00000000 00000000 00000040 00000001 00000000 00000000

    Checking 'hlt' instruction... OK.

    SMP alternatives: switching to UP code

    Freeing SMP alternatives: 13k freed

    CPU0: Intel Pentium II (Klamath) stepping 03

    SMP motherboard not detected.

    Brought up 1 CPUs

    sizeof(vma)=84 bytes

    sizeof(page)=32 bytes

    sizeof(inode)=336 bytes

    sizeof(dentry)=132 bytes

    sizeof(ext3inode)=488 bytes

    sizeof(buffer_head)=56 bytes

    sizeof(skbuff)=176 bytes

    sizeof(task_struct)=1376 bytes

    Time: 19:24:25 Date: 05/04/107

    NET: Registered protocol family 16

    PCI: PCI BIOS revision 2.10 entry at 0xf9fa0, last bus=0

    PCI: Using configuration type 1

    Setting up standard PCI resources

    ACPI: Interpreter disabled.

    Linux Plug and Play Support v0.97 (c) Adam Belay

    pnp: PnP ACPI: disabled

    usbcore: registered new interface driver usbfs

    usbcore: registered new interface driver hub

    usbcore: registered new device driver usb

    PCI: Probing PCI hardware

    PCI: Probing PCI hardware (bus 00)

    * Found PM-Timer Bug on the chipset. Due to workarounds for a bug,

    * this clock source is slow. Consider trying other clock sources

    PCI quirk: region b100-b10f claimed by PIIX4 SMB

    Boot video device is 0000:00:02.0

    PCI: Using IRQ router PIIX/ICH [8086/7000] at 0000:00:01.0

    PCI: BIOS reporting unknown device 01:00

    PCI: BIOS reporting unknown device 01:00

    PCI: BIOS reporting unknown device 01:00

    PCI: BIOS reporting unknown device 01:00

    PCI: BIOS reporting unknown device 01:00

    PCI: BIOS reporting unknown device 01:00

    NetLabel: Initializing

    NetLabel: domain hash size = 128

    NetLabel: protocols = UNLABELED CIPSOv4

    NetLabel: unlabeled traffic allowed by default

    PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0

    NET: Registered protocol family 2

     \ /
      Last update: 2007-06-04 22:25    [W:0.040 / U:0.980 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site