[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] libc issues in kernel 2.6.10

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Hari Kodungallur <hari.mailinglists@xxxxxxxxx>
  • Date: Wed, 25 May 2005 14:04:06 -0700
  • Delivery-date: Wed, 25 May 2005 21:03:29 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=b8W1W8L8S4yje4enxbpx4H7HqunHWeLKpxqcn0QtqQ7HhRbuN3MSXPdAeJ0V7SdltL60Kegt94UDSgAHNhJVxFVgNfjkAl0hA2NW5FsZDYTOZkq/I/VvPn+Py3bjQrzLLNF46FgNA5Q5Ad5medzVCQljGSShX5HXO97T0UFTkHA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


In kernel 2.6.10, we have enountered a problem with libc, and usually
seen when running a Java Virtual Machine; it throws a Signal 11. The
problem was traced back to a bug in the libc library in kernle 2.6.10.

Now we are seeing a similar error from a JVM on a xen image. (I have
attached sample error message).
Xen kernel is using 2.6.10. But the image was created from a 2.6.9-x
installation of FC3. When we login to the running FC3 image, uname -a

   Linux xen-qa1-fc3.spikesource.com 2.6.10-xenU....

Does that mean that even though the FC3 image was kernel 2.6.9, it
somehow uses the underlying xen kernel for processing?
Do you think if I upgrade my xen box to SuSE 9.3 which packages xen
with 2.6.11, and use the existing FC3 image, the problem will go away
(assuming the bug has been fixed post 2.6.10)

Thanks very much!

Hari Kodungallur
SpikeSource Inc.

Attachment: signal11error
Description: Binary data

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.