All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Olivier NOEL <jmoteuchi@wanadoo.fr>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: kernel BUG at arch/x86/xen/multicalls.c:103!
Date: Tue, 04 Aug 2009 16:55:21 -0700	[thread overview]
Message-ID: <4A78CA69.3090105@goop.org> (raw)
In-Reply-To: <481249.38422.qm@web25602.mail.ukl.yahoo.com>

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:[<c020248b>] 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:  [<c02592b4>] mprotect_fixup+0x4b4/0x610
> Jul 31 21:24:15 tomcat01 kernel:  [<c0259554>] sys_mprotect+0x144/0x1d0
> Jul 31 21:24:15 tomcat01 kernel:  [<c0206c22>] 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: [<c020248b>] 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

  reply	other threads:[~2009-08-04 23:55 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 [this message]
2009-08-05  7:10   ` Olivier NOEL
2009-08-06  6:50     ` Olivier NOEL
2009-08-06 19:35       ` Jeremy Fitzhardinge
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=4A78CA69.3090105@goop.org \
    --to=jeremy@goop.org \
    --cc=jmoteuchi@wanadoo.fr \
    --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.