All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Parish <srparish@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: hints for pae enabled dom0
Date: Fri, 13 May 2005 07:42:50 +0000	[thread overview]
Message-ID: <20050513074250.GC27910@us.ibm.com> (raw)

I haven't been making much progress on cracking this one and am
interested in collecting suggestions.

The xen/linux26 pair are yesterday's xen-unstable with Gerd's 6th
pae patches, and pae/highmem enabled.

sRp

--

<snip>    ( for full output: http://srparish.net/tmp/xen-87 )

INIT: Entering runlevel: 2
Starting system log daemon: syslogd.
Starting kernel log daemon: klogd
(XEN) __copy_from_user_ll(0xff107f38, 0xfd8aaaa8, 0x8);
(XEN) lpt_start: 0xfd800000, lpt_end: 0xfe000000
(XEN) (file=traps.c, line=342) Page fault: ff1548a6 -> ff156d71, addr = fd8aaaa8
(XEN) CPU:    0
(XEN) EIP:    0808:[<ff1548a6>]      
(XEN) EFLAGS: 00010246   CONTEXT: hypervisor
(XEN) eax: 00000000   ebx: 00000008   ecx: 00000002   edx: 00000000
(XEN) esi: fd8aaaa8   edi: ff107f38   ebp: ff107ef0   esp: ff107ec8
(XEN) ds: 0810   es: 0810   fs: 0810   gs: 0810   ss: 0810   cs: 0808
(XEN) Stack trace from ESP=ff107ec8:
(XEN)    ff16cf84 fd800000 fe000000 00000008 1007c061 00000000 000113cf ffbf8080 
(XEN)    00000000 15555000 ff107f50 [ff12fbb5] ff107f38 fd8aaaa8 00000008 1007c061 
(XEN)    00000000 ff16f600 00000000 ffbf9800 00000120 00000001 00000292 00000000 
(XEN)    00000008 fd8aaaa8 ff107f38 ffbf9800 1007c061 00000000 41848061 ffbf8080 
(XEN)    00000000 15555000 ff107fb0 [ff134784] fd8aaaa8 41848061 00000000 41848061 
(XEN)    00010076 f0000001 00000000 ffbf8080 00000000 00000000 00000000 00000001 
(XEN)    00000000 00000000 f699d7f0 000113aa 000113aa 00000000 ffbf9800 ffbf8080 
(XEN)    41848061 00000000 41848061 [ff151b33] 15555000 41848061 00000000 00000000 
(XEN)    15555000 41848061 0000000e 000e0003 c0115c8a 00000061 00000282 cfbdfd80 
(XEN)    00000069 0000007b 0000007b 00000000 00000000 ffbf8080 
(XEN) Call Trace from ESP=ff107ec8:
(XEN)    [<ff12fbb5>] [<ff134784>] [<ff151b33>] 
(XEN) Pagetable walk from fd8aaaa8:
(XEN)  L3 = 0x0000000000105001
(XEN)  L2 = 0x000000000010a063 
(XEN)  L1 = 0xfd8085c7fffffd7c
Failed update VA mapping: 15555000, (0x80000c07) 41848061, 00000000
kernel BUG at include/asm-xen/asm/hypercall.h:405 (HYPERVISOR_update_va_mapping)!
 [<c0115cdf>] mm_walk+0x229/0x27f
 [<c0115d91>] mm_pin+0x5c/0x171
 [<c016b32c>] exec_mmap+0x14d/0x1fa
 [<c015f0ef>] dentry_open+0xd2/0x266
 [<c0133de8>] autoremove_wake_function+0x0/0x57
 [<c016b58a>] flush_old_exec+0x11f/0x9ea
 [<c015fddb>] vfs_read+0xc5/0x14d
 [<c016b1d0>] kernel_read+0x50/0x5f
 [<c018b48e>] load_elf_binary+0x3ad/0xcc4
 [<c018b0e1>] load_elf_binary+0x0/0xcc4
 [<c016c137>] search_binary_handler+0xbb/0x2ea
 [<c016c4e6>] do_execve+0x180/0x1fa
 [<c0108385>] sys_execve+0x46/0x97
 [<c01098f8>] syscall_call+0x7/0xb
Kernel panic - not syncing: BUG!
 (XEN) Domain 0 shutdown: rebooting machine.

-- 
Scott Parish
Signed-off-by: srparish@us.ibm.com

             reply	other threads:[~2005-05-13  7:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13  7:42 Scott Parish [this message]
2005-05-13  9:47 ` hints for pae enabled dom0 Gerd Knorr
  -- strict thread matches above, loose matches on Subject: below --
2005-05-13 10:28 Scott Parish
2005-05-13 10:43 Scott Parish

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=20050513074250.GC27910@us.ibm.com \
    --to=srparish@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.