[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Kernel BUG at "arch/xen/x86_64/mm/hypervisor.c":198

Hello Xen developers!

I finally managed to get my first real box for Xen -- and now I'm in trouble ;-)

run Xen-3.0 on an Dual-Opteron Dual-Core box with SUSE 10.0 kernel/xen RPMs 
from current yast online update packages I get the following system crash 
quite easy within a few minutes (~1-5 min) with only dom0 and running 
~4-5 processes with just a cpu loop ("while (1) ;")

here is the most complete information I got from syslog so far:

        kernel: ----------- [cut here ] --------- [please bite here ] ---------
        kernel: Kernel BUG at "arch/xen/x86_64/mm/hypervisor.c":198
        kernel: invalid operand: 0000 [1] 
        kernel: CPU 0 
        kernel: Modules linked in: bridge ipv6 button battery ac af_packet tg3 
ohci_hcd usbcore i2c_amd8111 i2c_amd756 i2c_core hw_random generic parport_pc 
lp parport ext3 jbd dm_mod reiserfs fan thermal processor sg ide_cd cdrom 
aic79xx scsi_transport_spi amd74xx sd_mod scsi_mod ide_disk ide_core
        kernel: Pid: 7082, comm: mybuffer Not tainted 2.6.13-15-xen
        kernel: RIP: e030:[<ffffffff8011f987>] 
        kernel: RSP: e02b:ffff88000f9b7b28  EFLAGS: 00010282
        kernel: RAX: 00000000ffffffea RBX: ffff88001f08a040 RCX: 
        kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: 
        kernel: RBP: ffff88000f9b7c08 R08: 0000000000000003 R09: 
        kernel: R10: 0000000000007ff0 R11: 0000000000000246 R12: 
        kernel: R13: ffff8800016d77f0 R14: 000000ae03419fd2 R15: 
        kernel: FS:  00002aaaac4001a0(0000) GS:ffffffff804bbe80(0000) 
        kernel: CS:  e033 DS: 0000 ES: 0000
        kernel: Process mybuffer (pid: 7082, threadinfo ffff88000f9b6000, task 
        kernel: Stack: ffff880000000003 00000000000b5eb6 ffff8800016d77f0 
        kernel:        ffff88001a2eb8f8 ffffffff8011ea75 ffff88001f08a040 
        kernel:        00000000000010da ffff88001a2eb6e0 
        kernel: Call Trace:<ffffffff8011ea75>{mm_pin+325} 
        kernel:        <ffffffff801572e0>{sync_page+0} 
        kernel:        <ffffffff8015731b>{sync_page+59} 
        kernel:        <ffffffff8015740f>{__lock_page+95} 
        kernel:        <ffffffff80157685>{find_get_page+21} 
        kernel:        <ffffffff80157860>{file_read_actor+0} 
        kernel:        <ffffffff80159c8b>{generic_file_read+187} 
        kernel:        <ffffffff80115369>{do_IRQ+57} 
        kernel:        <ffffffff80148760>{autoremove_wake_function+0} 
        kernel:        <ffffffff8017b4c3>{sys_read+83} 
        kernel:        <ffffffff80120fa8>{ia32_syscall+0} 
        kernel: Code: 0f 0b a3 58 81 36 80 ff ff ff ff c2 c6 00 48 83 c4 28 c3 
        kernel: RIP <ffffffff8011f987>{xen_pgd_pin+71} RSP <ffff88000f9b7b28>

unfortuneately I didn't yet manage to get the _full_ crash info for both 
the hypervisor _and_ the dom0 kernel in syslog, and I'm still wrestling
with the serial console when using xen.  right now I only have a "real" 
screen shot (4 Mpixel;) which shows both information, if this is needed...

system setup:

        dual-cpu dual-core AMD Opteron 
        8 GB ram
        SUSE 10.0 x86_64 + online update

running 32bit SUSE 10.0 xen-3.0 doesn't show this crash, only the x86_64 system.

which other information do you need ?  
thanks for any pointer & help,

Harald Koenig
"I hope to die                                      ___       _____
before I *have* to use Microsoft Word.",           0--,|    /OOOOOOO\
Donald E. Knuth, 02-Oct-2001 in Tuebingen.        <_/  /  /OOOOOOOOOOO\
                                                    \  \/OOOOOOOOOOOOOOO\
                                                      \ OOOOOOOOOOOOOOOOO|//
Harald Koenig                                          \/\/\/\/\/\/\/\/\/
science+computing ag                                    //  /     \\  \
koenig@xxxxxxxxxxxxxxxxxxxx                            ^^^^^       ^^^^^

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.