Any jvm (even 32-bit) works on x86-64?
Ok, now I'm desperate. Is anybody using Java, esp. Tomcat or any
servlet container on Opterons? I've tried the IBM jdk that was
shipped with SuSE 8.1, the 64-bit rc1, the latest from IBM, Sun and
blackdown.org and then again on Fedora 0.96 for amd64. And I haven't
found a jvm that works with Tomcat yet.
If anyone has something similar working on x86-64 and is willing to
share their secret with me I would really appreciate it.
The latest error is attached below. This one is from the blackdown.org
1.4.2-rc1-linux-i586-gcc3.2.bin package (on Fedora 0.96) but it's
similar for all the 32-bit jvms I tried. Sometimes the jvm hangs
before the ajp connector even starts, sometimes I get to hit the
server a few times.
Any help or suggestions are welcomed.
Thanks,
Barry Roberts
Jan 31 04:15:35 optitwo kernel: Oops: 0010
Jan 31 04:15:35 optitwo kernel: CPU 1
Jan 31 04:15:35 optitwo kernel: Pid: 18527, comm: java Not tainted
Jan 31 04:15:35 optitwo kernel: RIP: 0010:[<0001801c7fce>]
Jan 31 04:15:35 optitwo kernel: RSP: :010078583e48 EFLAGS: 00010212
Jan 31 04:15:35 optitwo kernel: RAX: RBX: cb5e2d40 RCX:
Jan 31 04:15:35 optitwo kernel: RDX: RSI: 010078583f38 RDI:
cb5e2dd0
Jan 31 04:15:35 optitwo kernel: RBP: R08: 08052b7c R09:
c8988920
Jan 31 04:15:35 optitwo kernel: R10: R11: c898878c R12:
010078583f58
Jan 31 04:15:35 optitwo kernel: R13: 010005412728 R14: 000c R15:
010078582a58
Jan 31 04:15:35 optitwo kernel: FS: 002a95565060() GS:80572880(005b)
knlGS:cb5e4bb0
Jan 31 04:15:35 optitwo kernel: CS: 0010 DS: 002b ES: 002b CR0: 8005003b
Jan 31 04:15:35 optitwo kernel: CR2: 0001801c7fce CR3: 37ffe000 CR4:
06e0
Jan 31 04:15:35 optitwo kernel: Process java (pid: 18527, stackpage=10078583000)
Jan 31 04:15:35 optitwo kernel: Stack: 010078583e48
0001801c7fce 0001
Jan 31 04:15:35 optitwo kernel: 55b37e44
0001 08052b7c
Jan 31 04:15:35 optitwo kernel:8013daaa
3b9ab290 c898878c
Jan 31 04:15:35 optitwo kernel: Call Trace: []{do_signal+158}
[]{compat_sys_futex+202}
Jan 31 04:15:35 optitwo kernel:[]{intret_signal+45}
Jan 31 04:15:35 optitwo kernel:
Jan 31 04:15:35 optitwo kernel: Code: Bad RIP value.
Jan 31 04:15:35 optitwo kernel: RIP [<0001801c7fce>] RSP <010078583e48>
Jan 31 04:15:35 optitwo kernel: CR2: 0001801c7fce
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Any jvm (even 32-bit) works on x86-64?
Barry Roberts <[EMAIL PROTECTED]> writes:
> The latest error is attached below. This one is from the
> blackdown.org 1.4.2-rc1-linux-i586-gcc3.2.bin package (on Fedora
> 0.96) but it's similar for all the 32-bit jvms I tried. Sometimes
> the jvm hangs before the ajp connector even starts, sometimes I get
> to hit the server a few times.
>
> Any help or suggestions are welcomed.
If you get a kernel oops then there's something wrong with your
kernel. Even if there is a problem with the JVMs you've
tested, the kernel shouldn't oops.
> Jan 31 04:15:35 optitwo kernel: Oops: 0010
> Jan 31 04:15:35 optitwo kernel: CPU 1
> Jan 31 04:15:35 optitwo kernel: Pid: 18527, comm: java Not tainted
> Jan 31 04:15:35 optitwo kernel: RIP: 0010:[<0001801c7fce>]
> Jan 31 04:15:35 optitwo kernel: RSP: :010078583e48 EFLAGS: 00010212
> Jan 31 04:15:35 optitwo kernel: RAX: RBX: cb5e2d40 RCX:
>
> Jan 31 04:15:35 optitwo kernel: RDX: RSI: 010078583f38 RDI:
> cb5e2dd0
> Jan 31 04:15:35 optitwo kernel: RBP: R08: 08052b7c R09:
> c8988920
> Jan 31 04:15:35 optitwo kernel: R10: R11: c898878c R12:
> 010078583f58
> Jan 31 04:15:35 optitwo kernel: R13: 010005412728 R14: 000c R15:
> 010078582a58
> Jan 31 04:15:35 optitwo kernel: FS: 002a95565060()
> GS:80572880(005b) knlGS:cb5e4bb0
> Jan 31 04:15:35 optitwo kernel: CS: 0010 DS: 002b ES: 002b CR0: 8005003b
> Jan 31 04:15:35 optitwo kernel: CR2: 0001801c7fce CR3: 37ffe000 CR4:
> 06e0
> Jan 31 04:15:35 optitwo kernel: Process java (pid: 18527, stackpage=10078583000)
> Jan 31 04:15:35 optitwo kernel: Stack: 010078583e48
> 0001801c7fce 0001
> Jan 31 04:15:35 optitwo kernel: 55b37e44
> 0001 08052b7c
> Jan 31 04:15:35 optitwo kernel:8013daaa
> 3b9ab290 c898878c
> Jan 31 04:15:35 optitwo kernel: Call Trace: []{do_signal+158}
> []{compat_sys_futex+202}
> Jan 31 04:15:35 optitwo kernel:[]{intret_signal+45}
> Jan 31 04:15:35 optitwo kernel:
> Jan 31 04:15:35 optitwo kernel: Code: Bad RIP value.
> Jan 31 04:15:35 optitwo kernel: RIP [<0001801c7fce>] RSP <010078583e48>
> Jan 31 04:15:35 optitwo kernel: CR2: 0001801c7fce
Juergen
--
Juergen Kreileder, Blackdown Java-Linux Team
http://www.blackdown.org/java-linux/java2-status/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: x86-64 error workaround?
Barry Roberts <[EMAIL PROTECTED]> writes: > After installing Fedora RC1 on one of my opteron boxen, I can run > Tomcat 4.1.27 with my application for a short period of time before > the attached error occurs. Is there a workaround for this, or is it > a known error? It's a known error. The problem is fixed in the final which will be available next week. Juergen -- Juergen Kreileder, Blackdown Java-Linux Team http://www.blackdown.org/java-linux/java2-status/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
