From: Brian Gerst <bgerst@didntduck.org>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
Grzegorz Kulewski <kangur@polcom.net>,
Con Kolivas <kernel@kolivas.org>,
Matthias Andree <matthias.andree@gmx.de>
Subject: Re: post 2.6.7 BK change breaks Java?
Date: Sun, 11 Jul 2004 23:57:23 -0400 [thread overview]
Message-ID: <40F20C23.9050705@quark.didntduck.org> (raw)
In-Reply-To: <40F20372.9000205@quark.didntduck.org>
Brian Gerst wrote:
> Jesper Juhl wrote:
>
>> On Sun, 11 Jul 2004, Jesper Juhl wrote:
>>
>>
>>> On Sun, 11 Jul 2004, Grzegorz Kulewski wrote:
>>>
>>>
>>>> On Sun, 11 Jul 2004, Jesper Juhl wrote:
>>>>
>>>>
>>>>> On Fri, 9 Jul 2004, Jesper Juhl wrote:
>>>>>
>>>>>
>>>>>> On Fri, 9 Jul 2004, Con Kolivas wrote:
>>>>>>
>>>>>>
>>>>>>> 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_tabl
>>>>>>>
>>>>>>> es.patch
>>>>>>> http://ck.kolivas.org/patches/2.6/2.6.7/2.6.7-ck5/split-out/1105_CAN-200
>>>>>>>
>>>>>>> 4-0497.patch
>>>>>>> http://ck.kolivas.org/patches/2.6/2.6.7/2.6.7-ck5/split-out/1110_proc.pa
>>>>>>>
>>>>>>> tch
>>>>>>
>>>>>>
>>>>>> Thanks Con, I'll try playing with those tomorrow (got no time
>>>>>> tonight),
>>>>>> and report back.
>>>>>>
>>>>>
>>>>> Ok, got them all 3 backed out of 2.6.7-mm7 , but that doesn't change a
>>>>> thing. The JVM still dies when I try to run eclipse.
>>>>
>>>>
>>>> I can run Eclipse without any problems on 2.6.7-bk20-ck5 + few other
>>>> not
>>>> related patches. Maybe try using non -mm? Try 2.6.7-bk20 and then try
>>>> reverting some patches. Maybe there is some other problem in -mm that
>>>> gives similar results?
>>>>
>>>
>>> with plain 2.6.7-bk20 I see the issue, same with 2.6.7-mm7. Reverting
>>> http://linux.bkbits.net:8080/linux-2.6/cset@1.1743 from -mm7 fixes the
>>> issue. I'm currently building 2.6.7-bk20 minus that cset and I'll report
>>> back on the results of that in a few minutes.
>>>
>>
>> 2.6.7-bk20 minus the cset works.
>>
>> Testing with 2.6.8-rc1 and backing out one or both of the changes in the
>> cset I get these results :
>> 2.6.8-rc1 - vanilla -
>> breaks Java
>> 2.6.8-rc1-jju1 - both changes backed out - works
>> 2.6.8-rc1-jju2 - only first change (sys_rt_sigsuspend) applied - works
>> 2.6.8-rc1-jju3 - only second change (sys_sigaltstack) applied -
>> breaks Java
>>
>> --
>> Jesper Juhl <juhl-lkml@dif.dk>
>
>
> Looks like a GCC (gcc version 3.4.1 20040702 (Red Hat Linux 3.4.1-2))
> screwup:
>
> sys_sigaltstack:
> movl 4(%esp), %eax
> movl 8(%esp), %edx
> movl 56(%esp), %ecx
> jmp do_sigaltstack
>
> The offsets should be 4 more, to account for the return address on the
> stack.
Nevermind, I should have looked more carefully. The offsets are fine in
my example. What version of GCC are you using?
--
Brian Gerst
next prev parent reply other threads:[~2004-07-12 3:57 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
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 [this message]
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=40F20C23.9050705@quark.didntduck.org \
--to=bgerst@didntduck.org \
--cc=juhl-lkml@dif.dk \
--cc=kangur@polcom.net \
--cc=kernel@kolivas.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox