From: Con Kolivas <kernel@kolivas.org>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: Matthias Andree <matthias.andree@gmx.de>,
Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: post 2.6.7 BK change breaks Java?
Date: Sat, 10 Jul 2004 00:54:42 +1000 [thread overview]
Message-ID: <40EEB1B2.7000800@kolivas.org> (raw)
In-Reply-To: <Pine.LNX.4.56.0407091544170.22376@jjulnx.backbone.dif.dk>
[-- Attachment #1: Type: text/plain, Size: 2404 bytes --]
Jesper Juhl wrote:
> On Tue, 6 Jul 2004, Matthias Andree wrote:
>
>
>>Hi,
>>
>>I've pulled from the linux-2.6 BK tree some post-2.6.7 version, compiled
>>and installed it, and it breaks Java, standalone or plugged into
>>firefox, the symptom is that the application catches SIGKILL. This
>>didn't happen with stock 2.6.7 and doesn't happen with 2.6.6 either.
>>
>
> I'm seeing the same thing. I'm using Eclipse a lot which is Java based,
> and I noticed that wen I went from plain 2.6.7 to 2.6.7-mm3 Eclipse
> started dying shortly after launch (it only manages to get the splash
> screen up) with a message about the JVM dying. Since I had also upgraded
> my Sun Java at the same time I initially suspected that and back down to
> my old version, but the problem persisted. Then I tried the latest Java
> release from Sun, with same result. Then I started suspecting the kernel
> and tried 2.6.7-mm6, 2.6.7-bk20 and 2.6.7-mm7 - all with the same result
> that Java breaks. Finally I went back to a plain 2.6.7 and the problem
> went away - so it certainly looks kernel related.
> I was using the same .config with all kernels (copied from my plain 2.6.7
> kernel to the others and then running 'make oldconfig'), so I'm also
> pretty sure it's not due to some new kernel option I've enabled that I
> don't usually use.
>
> My hardware is AMD Athlon (t-bird) 1.4GHz CPU in a ASUS A7M266 mobo with
> 512MB of DDR266 RAM.
>
>
>
>>Is there any particular change I should try backing out?
>>
>
> I'm looking for the same thing, haven't found it yet unfortunately.
Hello
I've just started having a java application bomb out not long into
running as well where previously it would run for hours without
problems. However, unlike yourselves I'm running -ck and the only
change between the last working -ck and this kernel are the 3 security
patches. I haven't investigated because I cant take the machine offline,
but I suspect it's one of those possibly interfering. Looking at the
patches in question I have no idea how they could do it. I guess if you
can try backing them out it would be helpful. Here are links to the
patches in question.
http://ck.kolivas.org/patches/2.6/2.6.7/2.6.7-ck5/split-out/1100_ip_tables.patch
http://ck.kolivas.org/patches/2.6/2.6.7/2.6.7-ck5/split-out/1105_CAN-2004-0497.patch
http://ck.kolivas.org/patches/2.6/2.6.7/2.6.7-ck5/split-out/1110_proc.patch
Con
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-07-09 14:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 23:11 post 2.6.7 BK change breaks Java? Matthias Andree
2004-07-06 15:55 ` John Richard Moser
2004-07-06 16:14 ` Matthias Andree
2004-07-06 17:49 ` John Richard Moser
2004-07-06 22:45 ` Andy Isaacson
2004-07-09 13:51 ` Jesper Juhl
2004-07-09 14:54 ` Con Kolivas [this message]
2004-07-09 16:37 ` José de Paula
2004-07-09 17:55 ` Jesper Juhl
2004-07-10 11:41 ` Go Taniguchi
2004-07-11 15:16 ` Jesper Juhl
2004-07-11 15:19 ` Con Kolivas
2004-07-11 15:35 ` Jesper Juhl
2004-07-11 15:35 ` Grzegorz Kulewski
2004-07-11 15:38 ` Jesper Juhl
2004-07-12 0:56 ` Jesper Juhl
2004-07-12 3:20 ` Brian Gerst
2004-07-12 3:57 ` Brian Gerst
2004-07-12 11:01 ` Jesper Juhl
2004-07-12 12:38 ` Brian Gerst
2004-07-12 14:05 ` Matthias Andree
2004-07-12 15:59 ` Linus Torvalds
2004-07-12 21:50 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2004-07-06 18:38 Ray Lee
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=40EEB1B2.7000800@kolivas.org \
--to=kernel@kolivas.org \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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.