From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Olivier NOEL <ONOEL@tetra-info.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: kernel BUG at arch/x86/xen/multicalls.c:103!
Date: Thu, 06 Aug 2009 12:35:09 -0700 [thread overview]
Message-ID: <4A7B306D.5080108@goop.org> (raw)
In-Reply-To: <0E87C0E865217944860BB378D2898000E146B1@srv-mail.apnos.int>
On 08/05/09 23:50, Olivier NOEL wrote:
> Update :
>
> Same problem with a simple "javac -version" :
>
Well, that's nice and reproducable. Any chance you could try a more
recent kernel than 2.6.25?
Thanks,
J
> Aug 5 17:18:45 tomcat02 kernel: 1 multicall(s) failed: cpu 1
> Aug 5 17:18:45 tomcat02 kernel: call 1/1: op=14 arg=[b7f9c000] result=-22
> Aug 5 17:18:45 tomcat02 kernel: ------------[ cut here ]------------
> Aug 5 17:18:45 tomcat02 kernel: kernel BUG at arch/x86/xen/multicalls.c:103!
> Aug 5 17:18:45 tomcat02 kernel: invalid opcode: 0000 [#1] SMP
> Aug 5 17:18:45 tomcat02 kernel:
> Aug 5 17:18:45 tomcat02 kernel: Pid: 2284, comm: javac Not tainted (2.6.25.7 #1)
> Aug 5 17:18:45 tomcat02 kernel: EIP: 0061:[<c020248b>] EFLAGS: 00010202 CPU: 1
> Aug 5 17:18:45 tomcat02 kernel: EIP is at xen_mc_flush+0x16b/0x180
> Aug 5 17:18:45 tomcat02 kernel: EAX: 00000000 EBX: 00000000 ECX: 00000001 EDX: 00000000
> Aug 5 17:18:45 tomcat02 kernel: ESI: 00000000 EDI: 00000001 EBP: c140a060 ESP: ddd91edc
> Aug 5 17:18:45 tomcat02 kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0069
> Aug 5 17:18:45 tomcat02 kernel: Process javac (pid: 2284, ti=ddd90000 task=dddf35c0 task.ti=ddd90000)
> Aug 5 17:18:45 tomcat02 kernel: Stack: c05a5848 00000001 00000001 0000000e b7f9c000 ffffffea 00000200 00000065
> Aug 5 17:18:45 tomcat02 kernel: 00000000 00000000 b7f9c000 c02592b4 00000065 00000000 df734890 00000000
> Aug 5 17:18:45 tomcat02 kernel: 000b7f9c 00000000 00000000 dfce6034 ddec2ec8 dfce6000 b7f9d000 ddc8cbb0
> Aug 5 17:18:45 tomcat02 kernel: Call Trace:
> Aug 5 17:18:45 tomcat02 kernel: [<c02592b4>] mprotect_fixup+0x4b4/0x610
> Aug 5 17:18:45 tomcat02 kernel: [<c0259554>] sys_mprotect+0x144/0x1d0
> Aug 5 17:18:45 tomcat02 kernel: [<c0206c22>] syscall_call+0x7/0xb
> Aug 5 17:18:45 tomcat02 kernel: =======================
> Aug 5 17:18:45 tomcat02 kernel: Code: 00 83 c3 20 89 54 24 08 89 74 24 04 c7 04 24 48 58 5a c0 89 44 24 0c e8 84 fc 01 00 8b 95 00 0b 00 00 39 d6 72 c3 e9 25 ff ff ff <0f> 0b eb fe 0f 0b eb fe 8d b6 00 00 00 00 8d bc 27 00 00 00 00
> Aug 5 17:18:45 tomcat02 kernel: EIP: [<c020248b>] xen_mc_flush+0x16b/0x180 SS:ESP 0069:ddd91edc
> Aug 5 17:18:45 tomcat02 kernel: ---[ end trace 8011281f462e176f ]---
>
> Xm dmesg :
>
> (XEN) mm.c:645:d50 Non-privileged (50) attempt to map I/O space 00000000
> (XEN) mm.c:645:d51 Non-privileged (51) attempt to map I/O space 00000000
>
> Javac and java were configured by update-alternatives to use sun-java-5-jdk, but same problem with sun-java-6-jdk and openjdk-6-jdk, the Guest (Lenny or Etch) crash.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2009-08-06 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 9:44 kernel BUG at arch/x86/xen/multicalls.c:103! Olivier NOEL
2009-08-04 23:55 ` Jeremy Fitzhardinge
2009-08-05 7:10 ` Olivier NOEL
2009-08-06 6:50 ` Olivier NOEL
2009-08-06 19:35 ` Jeremy Fitzhardinge [this message]
2009-11-09 23:50 ` mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f995a Konrad Rzeszutek Wilk
2009-11-10 0:20 ` Jeremy Fitzhardinge
2009-12-01 3:11 ` mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f995a + (XEN) mm.c:845:d20 Error getting mfn jd (pfn 84fd) from L1 entry 800000000246d467 for l1e_owner=20, pg_owner=32753 Konrad Rzeszutek Wilk
2009-12-01 6:40 ` Jeremy Fitzhardinge
2009-12-01 21:57 ` Konrad Rzeszutek Wilk
2009-12-01 22:44 ` Jeremy Fitzhardinge
2009-12-01 23:05 ` Konrad Rzeszutek Wilk
2009-12-01 9:26 ` Markus Armbruster
2009-12-01 16:14 ` Konrad Rzeszutek Wilk
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=4A7B306D.5080108@goop.org \
--to=jeremy@goop.org \
--cc=ONOEL@tetra-info.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.