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

Morten Bøgeskov
Fri, 12 Oct 2007 09:46:00 -0000

Quoting Jeremy Fitzhardinge <jeremy@goop.org>:

> Morten Bøgeskov wrote:
>> Quoting Jeremy Fitzhardinge <jeremy@goop.org>:
>>
>>> 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.
>
> Odd.
>
>> I''ve included .config
>
> It seems a bit small.  Can you send your whole .config so I can rebuild
> your kernel?
>

Ah, you don''t have PAE enabled.  Could you try it with (HIGHMEM64G)?  I
do technically support non-PAE kernels, but they''re a bit tricky to
test
(stock Xen doesn''t really support non-PAE any more).

I''ll look at the UP issue too.

     J

New compiled xen-3.1.1-rc3 PAE, 2.6.18-xen (domU) PAE &
2.6.23 PAE (config included) Still no difference.

TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
blkfront: xvda1: barriers enabled
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, rootpathblkfront:
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: 180k freed
------------[ cut here ]------------
kernel BUG at arch/i386/xen/multicalls.c:78!
invalid opcode: 0000 [#1]
SMP
CPU:    0
EIP:    0061:[<c0101a92>]    Not tainted VLI
EFLAGS: 00010002   (2.6.23 #33)
EIP is at xen_mc_flush+0xd2/0xe0
eax: 00000000   ebx: c10c1060   ecx: 00000007   edx: 00000007
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: 000d991c c10c1120 c10c1460 c12d6000 c0102400 c12d5e40 c02c5100 c10eba90
        00000000 c01025d3 c12d5e40 c0161728 c125f49c 00000080 c1240aa0 00000000
        c10ece60 c015cdd0 c02c5ac0 c131d560 c134cbc0 c1141440 c0160ccd c10efd7c
Call Trace:
  [<c0102400>] xen_pgd_pin+0xb0/0x120
  [<c01025d3>] xen_activate_mm+0x13/0x20
  [<c0161728>] flush_old_exec+0x3c8/0x7e0
  [<c015cdd0>] do_sync_read+0x0/0x120
  [<c0160ccd>] kernel_read+0x3d/0x60
  [<c01891e6>] load_elf_binary+0x316/0x1aa0
  [<c0159a16>] kmem_cache_alloc+0x56/0xb0
  [<c01f610c>] xfs_file_aio_read+0x6c/0x80
  [<c0148b3a>] vm_normal_page+0x2a/0xb0
  [<c01492ef>] follow_page+0x1af/0x230
  [<c014ac25>] get_user_pages+0x105/0x360
  [<c016081b>] get_arg_page+0x4b/0xb0
  [<c01609f4>] copy_strings+0x174/0x190
  [<c0160aa4>] search_binary_handler+0x54/0x110
  [<c01624c6>] do_execve+0x166/0x190
  [<c0104bef>] sys_execve+0x2f/0x90
  [<c010663e>] syscall_call+0x7/0xb
  [<c010a98c>] kernel_execve+0x1c/0x30
  [<c0100173>] init_post+0xa3/0xf0
  [<c02e1942>] kernel_init+0x222/0x330
  [<c0119453>] schedule_tail+0x33/0xa0
  [<c01064fa>] ret_from_fork+0x6/0x1c
  [<c0106647>] syscall_exit+0x5/0x1b
  [<c02e1720>] kernel_init+0x0/0x330
  [<c02e1720>] kernel_init+0x0/0x330
  [<c0107213>] 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 27 00 00 00 00 83 ec 0c 89 1c 24 89
EIP: [<c0101a92>] xen_mc_flush+0xd2/0xe0 SS:ESP e021:c10efd1c
Kernel panic - not syncing: Attempted to kill init!