modify_ldt errors on x86_64

modify_ldt errors on x86_64

[Karl Rister]

I am trying to run some Java tests in a dom0 running on x86_64 and I am 
receiving the following error message:

setupLdt: modify_ldt: Invalid argument

After 2 of these the JVM just hangs and I have to kill it.  This does not 
happen when booting the systerm without Xen.  I have tried several different 
changesets from the past few days and have seen the same thing on all of 
them.  My current changeset is 7746.  Has anyone else seen this?

-- 
Karl Rister

RE: modify_ldt errors on x86_64

[Ian Pratt]

 
> I am trying to run some Java tests in a dom0 running on 
> x86_64 and I am receiving the following error message:
> 
> setupLdt: modify_ldt: Invalid argument
> 
> After 2 of these the JVM just hangs and I have to kill it.  
> This does not happen when booting the systerm without Xen.  I 
> have tried several different changesets from the past few 
> days and have seen the same thing on all of them.  My current 
> changeset is 7746.  Has anyone else seen this?

No, this is the first report.

Which version of Java are you using. Have you a simple test case?

Can you repro in domain0?

Have you modified the default kernel config?

Thanks,
Ian

Re: modify_ldt errors on x86_64

[Karl Rister]

On Saturday 12 November 2005 7:06 am, Ian Pratt wrote:
> > I am trying to run some Java tests in a dom0 running on
> > x86_64 and I am receiving the following error message:
> >
> > setupLdt: modify_ldt: Invalid argument
> >
> > After 2 of these the JVM just hangs and I have to kill it.
> > This does not happen when booting the systerm without Xen.  I
> > have tried several different changesets from the past few
> > days and have seen the same thing on all of them.  My current
> > changeset is 7746.  Has anyone else seen this?
>
> No, this is the first report.
>
> Which version of Java are you using. Have you a simple test case?

"java -version" returns the following on baremetal Linux, this simple test is 
enough to cause the problem in domain0

java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142sr1a-20050209 (JIT 
enabled: jitc))

An strace on the java process shows these two messages being dumped over and 
over again in a loop:

rt_sigprocmask(SIG_UNBLOCK, [ILL TRAP BUS FPE SEGV], ~[KILL USR2 STOP RTMIN 
RT_1], 8) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---

>
> Can you repro in domain0?

As noted above, yes.

>
> Have you modified the default kernel config?

Yes.  The following options were appended to the kernel config file:

CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID5=y
CONFIG_BLK_DEV_DM=y
CONFIG_ACPI=y
CONFIG_AGP=n
CONFIG_SCSI_FC_ATTRS=y
CONFIG_SCSI_QLA2300=y
CONFIG_FUSION=y
CONFIG_FUSION_CTL=y
CONFIG_E1000=m
CONFIG_PROFILING=y
CONFIG_OPROFILE=m
CONFIG_TIGON3=m
CONFIG_CRYPTO=n
CONFIG_CRYPTO_CRC32C=n
CONFIG_CRC32=n
CONFIG_LIBCRC32C=n
CONFIG_SCSI_ADP94XX=y

>
> Thanks,
> Ian
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

-- 
Karl Rister

RE: modify_ldt errors on x86_64

[Nakajima, Jun]

Karl Rister wrote:
> On Saturday 12 November 2005 7:06 am, Ian Pratt wrote:
>>> I am trying to run some Java tests in a dom0 running on
>>> x86_64 and I am receiving the following error message:
>>> 
>>> setupLdt: modify_ldt: Invalid argument
>>> 
>>> After 2 of these the JVM just hangs and I have to kill it.
>>> This does not happen when booting the systerm without Xen.  I
>>> have tried several different changesets from the past few
>>> days and have seen the same thing on all of them.  My current
>>> changeset is 7746.  Has anyone else seen this?
>> 
>> No, this is the first report.
>> 
>> Which version of Java are you using. Have you a simple test case?
> 
> "java -version" returns the following on baremetal Linux, this simple
> test is enough to cause the problem in domain0
> 
> java version "1.4.2"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
> Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142sr1a-20050209
> (JIT enabled: jitc))

I tested "java -version" on x86_64 xenlinux, and got:

java version "1.4.2-02"
Java(TM) 2 Runtime Environment, Standard Edition (build
Blackdown-1.4.2-02)
Java HotSpot(TM) 64-Bit Server VM (build Blackdown-1.4.2-02, mixed mode)

I downloaded it from ftp.tux.org. 

> 
> An strace on the java process shows these two messages being dumped
> over and over again in a loop:
> 
> rt_sigprocmask(SIG_UNBLOCK, [ILL TRAP BUS FPE SEGV], ~[KILL USR2 STOP
> RTMIN RT_1], 8) = 0
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---


Jun
---
Intel Open Source Technology Center

Re: modify_ldt errors on x86_64

[Karl Rister]

On Monday 14 November 2005 5:59 pm, Nakajima, Jun wrote:
> Karl Rister wrote:
> > On Saturday 12 November 2005 7:06 am, Ian Pratt wrote:
> >>> I am trying to run some Java tests in a dom0 running on
> >>> x86_64 and I am receiving the following error message:
> >>>
> >>> setupLdt: modify_ldt: Invalid argument
> >>>
> >>> After 2 of these the JVM just hangs and I have to kill it.
> >>> This does not happen when booting the systerm without Xen.  I
> >>> have tried several different changesets from the past few
> >>> days and have seen the same thing on all of them.  My current
> >>> changeset is 7746.  Has anyone else seen this?
> >>
> >> No, this is the first report.
> >>
> >> Which version of Java are you using. Have you a simple test case?
> >
> > "java -version" returns the following on baremetal Linux, this simple
> > test is enough to cause the problem in domain0
> >
> > java version "1.4.2"
> > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
> > Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142sr1a-20050209
> > (JIT enabled: jitc))
>
> I tested "java -version" on x86_64 xenlinux, and got:
>
> java version "1.4.2-02"
> Java(TM) 2 Runtime Environment, Standard Edition (build
> Blackdown-1.4.2-02)
> Java HotSpot(TM) 64-Bit Server VM (build Blackdown-1.4.2-02, mixed mode)
>
> I downloaded it from ftp.tux.org.

I tried both the 32bit and 64bit Blackdown JVMs as well as a 64bit IBM JVM and 
they do not exhibit this problem.  It seems to be specific to the 32bit IBM 
JVM.  I think that I am going to file this as a bug since Xen should not be 
affecting a userspace app in this manner.

I should also add that in some instances (mostly on a uniprocessor dom0) this 
error renders the box dead and it has to be rebooted through the service 
processor.

>
> > An strace on the java process shows these two messages being dumped
> > over and over again in a loop:
> >
> > rt_sigprocmask(SIG_UNBLOCK, [ILL TRAP BUS FPE SEGV], ~[KILL USR2 STOP
> > RTMIN RT_1], 8) = 0
> > --- SIGSEGV (Segmentation fault) @ 0 (0) ---
>
> Jun
> ---
> Intel Open Source Technology Center
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

-- 
Karl Rister