All of lore.kernel.org
 help / color / mirror / Atom feed
From: "\"T. Eichstädt\"" <abc@digithi.de>
To: xen-devel@lists.xensource.com
Subject: kernel BUG at arch/i386/mm/hypervisor.c
Date: Wed, 10 Sep 2008 17:45:00 +0200	[thread overview]
Message-ID: <48C7EB7C.7080403@digithi.de> (raw)

Hello All,

I have some problems with a 32 Bit DomU Guest under a 64 Bit Dom0: The 
DomU crashes randomly.
The problem only occurs on 32 Bit DomUs, not on 64 Bit DomUs.
I have CentOS 5.2 with a 2.6.18 distro kernel running on DomU and Dom0.

My problem seems to be the same as: 
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=756
Are there already any solutions ?

Kernel output and xm dmesg are attached.

Best regards
  Thimo Eichstädt

---domuU kernel crash: --------------
kernel BUG at arch/i386/mm/hypervisor.c:197!
invalid opcode: 0000 [#1]
SMP
last sysfs file: /block/ram0/range
Modules linked in: ipv6 i2c_dev i2c_core sunrpc xennet ztdummy(U) 
zaptel(U) oslec(U) crc_ccitt fcpci(U) capi capifs kernelcapi dm_mirror 
dm_multipath dm_mod parport_pc lp parport pcspkr xenblk ext3 jbd 
ehci_hcd ohci_hcd uhci_hcd
CPU:    0
EIP:    0061:[<c04151ae>]    Tainted: PF     VLI
EFLAGS: 00010282   (2.6.18-53.1.4.el5xen #1)
EIP is at xen_pgd_pin+0x43/0x51
eax: ffffffea   ebx: c0e9aef4   ecx: 00000001   edx: 00000000
esi: 00007ff0   edi: 00000000   ebp: d4b81550   esp: c0e9aef4
ds: 007b   es: 007b   ss: 0069
Process crond (pid: 1594, ti=c0e9a000 task=c0ea8550 task.ti=c0e9a000)
Stack: 00000002 00078d59 00000000 00318460 00000000 c041230e c0700900 
c0412337
       c06f96a4 c041b793 c0e9afbc bfe34a24 01200011 00000000 d4b81550 
c0ea8550
       c0700900 c0700e40 c06f96b0 c06f96c4 c06f96c0 c0700900 00000001 
00000001
Call Trace:
 [<c041230e>] __pgd_pin+0x2a/0x37
 [<c0412337>] mm_pin+0x1c/0x23
 [<c041b793>] copy_process+0xb63/0x1167
 [<c041bdd8>] do_fork+0x41/0x130
 [<c04031c1>] sys_clone+0x28/0x2d
 [<c040534f>] syscall_call+0x7/0xb
 =======================
Code: 75 0e a1 28 72 74 c0 8b 14 90 81 e2 ff ff ff 7f 89 54 24 04 89 e3 
b9 01 00 00 00 31 d2 be f0 7f 00 00 e8 96 c1 fe ff 85 c0 79 08 <0f> 0b 
c5 00 eb 82 61 c0 83 c4 0c 5b 5e c3 56 89 c2 53 83 ec 0c
EIP: [<c04151ae>] xen_pgd_pin+0x43/0x51 SS:ESP 0069:c0e9aef4
 <0>Kernel panic - not syncing: Fatal exception


--------------- xm dmesg -------------
....
(XEN) mm.c:1904:d10 Dom 10 cannot set foreign dom <-- this is the 32 Bit 
domain
(XEN) mm.c:1904:d10 Dom 10 cannot set foreign dom
(XEN) mm.c:1904:d10 Dom 10 cannot set foreign dom
(XEN) mm.c:1904:d10 Dom 10 cannot set foreign dom
(XEN) mm.c:1904:d10 Dom 10 cannot set foreign dom
(XEN) mm.c:1904:d10 Dom 10 cannot set foreign dom
(XEN) mm.c:1904:d10 Dom 10 cannot set foreign dom
(XEN) mm.c:1904:d10 Dom 10 cannot set foreign dom
(XEN) mm.c:1752:d10 Bad type (saw 00000000e8000001 != exp 
0000000020000000) for mfn 958d2 (pfn 8454)
(XEN) mm.c:644:d10 Attempt to create linear p.t. with write perms
(XEN) mm.c:1069:d10 Failure in alloc_l2_table: entry 7
(XEN) mm.c:1773:d10 Error while validating mfn bd54a (pfn 19b1b) for 
type 0000000040000000: caf=80000003 taf=0000000040000001
(XEN) mm.c:1143:d10 Failure in alloc_l3_table: entry 0
(XEN) mm.c:1773:d10 Error while validating mfn 78d59 (pfn 18c23) for 
type 0000000060000000: caf=80000003 taf=0000000060000001
(XEN) mm.c:2042:d10 Error while pinning mfn 78d59

                 reply	other threads:[~2008-09-10 15:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=48C7EB7C.7080403@digithi.de \
    --to=abc@digithi.de \
    --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.