From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: kernel BUG at arch/x86/xen/multicalls.c:103! Date: Tue, 04 Aug 2009 16:55:21 -0700 Message-ID: <4A78CA69.3090105@goop.org> References: <481249.38422.qm@web25602.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <481249.38422.qm@web25602.mail.ukl.yahoo.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Olivier NOEL Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 08/03/09 02:44, Olivier NOEL wrote: > Hi, > > I have this bug when I activate java-6-jdk on Tomcat 5.5.26 in a Lenny Guest : > Does it happen immediately, or after a while? Does it happen every time? How many VCPUs are there? > Jul 31 21:24:15 tomcat01 kernel: 1 multicall(s) failed: cpu 3 > Jul 31 21:24:15 tomcat01 kernel: call 1/1: op=14 arg=[b7f1a000] result=-22 > Jul 31 21:24:15 tomcat01 kernel: ------------[ cut here ]------------ > Jul 31 21:24:15 tomcat01 kernel: kernel BUG at arch/x86/xen/multicalls.c:103! > Jul 31 21:24:15 tomcat01 kernel: invalid opcode: 0000 [#1] SMP > Jul 31 21:24:15 tomcat01 kernel: > Jul 31 21:24:15 tomcat01 kernel: Pid: 2467, comm: jsvc Not tainted (2.6.25.7 #1) > Jul 31 21:24:15 tomcat01 kernel: EIP: 0061:[] EFLAGS: 00010202 CPU: 3 > Jul 31 21:24:15 tomcat01 kernel: EIP is at xen_mc_flush+0x16b/0x180 > Jul 31 21:24:15 tomcat01 kernel: EAX: 00000000 EBX: 00000000 ECX: 00000003 EDX: 00000000 > Jul 31 21:24:15 tomcat01 kernel: ESI: 00000000 EDI: 00000001 EBP: c141a060 ESP: deaadedc > Jul 31 21:24:15 tomcat01 kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0069 > Jul 31 21:24:15 tomcat01 kernel: Process jsvc (pid: 2467, ti=deaac000 task=df6e6000 task.ti=deaac000) > Jul 31 21:24:15 tomcat01 kernel: Stack: c05a5848 00000001 00000001 0000000e b7f1a000 ffffffea 00000200 00000065 > Jul 31 21:24:15 tomcat01 kernel: 00000000 00000000 b7f1a000 c02592b4 00000065 00000000 df5c3f50 00000000 > Jul 31 21:24:15 tomcat01 kernel: 000b7f1a 00000000 00000000 de827e34 df616210 de827e00 b7f1b000 df616528 > Jul 31 21:24:15 tomcat01 kernel: Call Trace: > Jul 31 21:24:15 tomcat01 kernel: [] mprotect_fixup+0x4b4/0x610 > Jul 31 21:24:15 tomcat01 kernel: [] sys_mprotect+0x144/0x1d0 > Jul 31 21:24:15 tomcat01 kernel: [] syscall_call+0x7/0xb > Jul 31 21:24:15 tomcat01 kernel: ======================= > Jul 31 21:24:15 tomcat01 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 > Jul 31 21:24:15 tomcat01 kernel: EIP: [] xen_mc_flush+0x16b/0x180 SS:ESP 0069:deaadedc > Jul 31 21:24:15 tomcat01 kernel: ---[ end trace 9edfe58cbc53ddca ]--- > > Do you get any messages on the Xen console (xm dmesg)? J