WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [Xen-users] 2.6.23 oops

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: [Xen-users] 2.6.23 oops
From: Morten Bøgeskov <xen-users@xxxxxxxxxxxxxxxxxx>
Date: Thu, 11 Oct 2007 23:21:16 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Delivery-date: Mon, 15 Oct 2007 03:56:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <470E8FE8.6050908@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20071011144817.n5x1drwcgug44sg0@xxxxxxxxxxxx> <200710111629.05457.mark.williamson@xxxxxxxxxxxx> <470E5248.1070502@xxxxxxxx> <20071011210001.cpd3whfy5ogwkwwc@xxxxxxxxxxxx> <470E8FE8.6050908@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) H3 (4.1.3)
Quoting Jeremy Fitzhardinge <jeremy@xxxxxxxx>:

Morten Bøgeskov wrote:
I've applied both, and tried with and without SMP, with exactly the
same result as before.

UP hangs after "installing Xen timer for CPU 0"

Ah, OK.   I'd overlooked this one.  Hm, I probably haven't tried UP in a
while.

SMP the oops'es the same way except the line no. is now 78.

Oh, that's odd.  Could you resend your original bug report?  What kind
of load does it fail under?

I can't really say what load. It doesn't get that far.
I've included .config



config:
kernel = "/usr/src/linux-2.6.23/vmlinux"
memory = 96
name = "foo"
vif = [ 'mac=00:16:3e:00:00:00, bridge=br1' ]
vcpus = 1
disk = [ 'phy:/dev/VOL/foo,hda1,w' ]
root = "/dev/xvda1 ro"
extra = "ip=192.168.0.2::192.168.0.1:255.255.255.0:foo:eth0:"

Output:
Using config file "/etc/xen/foo".
Started domain foo
Reserving virtual address space above 0xfbffe000
Linux version 2.6.23 (root@hobbes) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #32 SMP Thu Oct 11 21:02:46 CEST 2007
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000006000000 (usable)
0MB HIGHMEM available.
96MB LOWMEM available.
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->    24576
  HighMem     24576 ->    24576
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->    24576
DMI not present or invalid.
Allocating PCI resources starting at 10000000 (gap: 06000000:fa000000)
Built 1 zonelists in Zone order.  Total pages: 24384
Kernel command line: root=/dev/xvda1 ro ip=192.168.0.2::192.168.0.1:255.255.255.0:foo:eth0:
Local APIC disabled by BIOS -- you can enable it with "lapic"
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 512 (order: 9, 2048 bytes)
Detected 1666.723 MHz processor.
console [hvc0] enabled
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 94884k/98304k available (1543k kernel code, 3360k reserved, 343k data, 176k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xfbf9d000 - 0xfbffd000   ( 384 kB)
    pkmap   : 0xfb800000 - 0xfbc00000   (4096 kB)
    vmalloc : 0xc6800000 - 0xfb7fe000   ( 847 MB)
    lowmem  : 0xc0000000 - 0xc6000000   (  96 MB)
      .init : 0xc02dd000 - 0xc0309000   ( 176 kB)
      .data : 0xc0281ed6 - 0xc02d7d6c   ( 343 kB)
      .text : 0xc0100000 - 0xc0281ed6   (1543 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
installing Xen timer for CPU 0
Calibrating delay using timer specific routine.. 3341.81 BogoMIPS (lpj=5567710)
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
Compat vDSO mapped to fbffc000.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 9k freed
Brought up 1 CPUs
Booting paravirtualized kernel on Xen
Hypervisor signature: xen-3.0-x86_32
Grant table initialized
NET: Registered protocol family 16
Setting up standard PCI resources
NET: Registered protocol family 2
Time: xen clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 49152 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
SGI XFS with no debug enabled
io scheduler noop registered
io scheduler deadline registered (default)
Initialising Xen virtual ethernet driver.
blkfront: xvda1: barriers enabled
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
XENBUS: Device with no driver: device/console/0
IP-Config: Complete:
      device=eth0, addr=192.168.0.2, mask=255.255.255.0, gw=192.168.0.1,
     host=foo, domain=, nis-domain=(none),
     bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
blkfront: xvda1: write barrier op failed
blkfront: xvda1: barriers disabled
Filesystem "xvda1": Disabling barriers, trial barrier write failed
XFS mounting filesystem xvda1
VFS: Mounted root (xfs filesystem) readonly.
Freeing unused kernel memory: 176k freed
------------[ cut here ]------------
kernel BUG at arch/i386/xen/multicalls.c:78!
invalid opcode: 0000 [#1]
SMP
CPU:    0
EIP:    0061:[<c0101a82>]    Not tainted VLI
EFLAGS: 00010002   (2.6.23 #32)
EIP is at xen_mc_flush+0xd2/0xe0
eax: 00000000   ebx: c10c1060   ecx: 00000003   edx: 00000003
esi: c10c1060   edi: 00000000   ebp: 00000001   esp: c10efd1c
ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: e021
Process swapper (pid: 1, ti=c10ee000 task=c10eba90 task.ti=c10ee000)
Stack: 000d9b10 c10c10a0 c10c1460 c130b000 c01020d0 c1329e40 c02c1100 c10eba90
       00000000 c01021f3 c1329e40 c015e498 c132849c 00000080 c12e0aa0 00000000
       c10ece60 c0159b50 c02c1ac0 c12fa560 c1253c20 c1144440 c015da4d c10efd7c
Call Trace:
 [<c01020d0>] xen_pgd_pin+0xb0/0x120
 [<c01021f3>] xen_activate_mm+0x13/0x20
 [<c015e498>] flush_old_exec+0x3c8/0x7e0
 [<c0159b50>] do_sync_read+0x0/0x120
 [<c015da4d>] kernel_read+0x3d/0x60
 [<c0185ed6>] load_elf_binary+0x316/0x1aa0
 [<c013fe27>] __alloc_pages+0x57/0x2f0
 [<c0156796>] kmem_cache_alloc+0x56/0xb0
 [<c01488eb>] handle_mm_fault+0x52b/0x6f0
 [<c014710b>] vm_normal_page+0x1b/0x80
 [<c014710b>] vm_normal_page+0x1b/0x80
 [<c0147786>] follow_page+0x106/0x180
 [<c0148bb7>] get_user_pages+0x107/0x2d0
 [<c015d59b>] get_arg_page+0x4b/0xb0
 [<c015d774>] copy_strings+0x174/0x190
 [<c015d824>] search_binary_handler+0x54/0x110
 [<c015f236>] do_execve+0x166/0x190
 [<c010460f>] sys_execve+0x2f/0x90
 [<c010605e>] syscall_call+0x7/0xb
 [<c010a3ac>] kernel_execve+0x1c/0x30
 [<c0100173>] init_post+0xa3/0xf0
 [<c02dd942>] kernel_init+0x222/0x330
 [<c0118173>] schedule_tail+0x33/0xa0
 [<c0105f1a>] ret_from_fork+0x6/0x1c
 [<c0106067>] syscall_exit+0x5/0x1b
 [<c02dd720>] kernel_init+0x0/0x330
 [<c02dd720>] kernel_init+0x0/0x330
 [<c0106c33>] kernel_thread_helper+0x7/0x10
 =======================
Code: 89 d8 72 e9 85 ed c7 86 08 07 00 00 00 00 00 00 75 19 5b 5e 5f 5d c3 0f 0b eb fe 8b 96 04 07 00 00 31 ed 85 d2 74 ac 0f 0b eb fe <0f> 0b eb fe 8d 76 00 8d bc
 00 00 00 00 83 ec 0c 89 1c 24 89
EIP: [<c0101a82>] xen_mc_flush+0xd2/0xe0 SS:ESP e021:c10efd1c
Kernel panic - not syncing: Attempted to kill init!


Attachment: config
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel