All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: adeos-main <adeos-main@gna.org>
Subject: [Adeos-main] Re: tracer broken on 2.6.20-i386
Date: Sat, 10 Feb 2007 14:20:32 +0100	[thread overview]
Message-ID: <45CDC6A0.1020407@domain.hid> (raw)
In-Reply-To: <45CDC5AE.5010903@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

Jan Kiszka wrote:
> Jan Kiszka wrote:
> 
>> Philippe,
>>
>> have you had to adopt any tracer-related code while switching to 2.6.20?
>> The same .config that worked fine for 2.6.19 doesn't boot here on
>> 2.6.20. The kernel hangs during or after decompression. Disabling the
>> tracer resolves this.
>>   
> 
> I had a look at latest -rt and found some new change (which turned out
> to be a hack). Playing with it, I understood its motivation (avoid
> instrumentation of the decompressor). Here comes a cleaner variant for
> 2.6.20 (all archs). Tracer boots fine again. :)
          ^^^^^^^^^
Strike that, I lost the overview for a while. It remains an i386 issue.

> 
> Jan
> 
> 
> Index: linux-2.6.20/arch/i386/boot/compressed/Makefile
> ===================================================================
> --- linux-2.6.20.orig/arch/i386/boot/compressed/Makefile
> +++ linux-2.6.20/arch/i386/boot/compressed/Makefile
> @@ -9,6 +9,7 @@ targets		:= vmlinux vmlinux.bin vmlinux.
>  EXTRA_AFLAGS	:= -traditional
>  
>  LDFLAGS_vmlinux := -T
> +CFLAGS := $(subst -pg,,$(CFLAGS))
>  CFLAGS_misc.o += -fPIC
>  hostprogs-y	:= relocs
>  
> 
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]

  reply	other threads:[~2007-02-10 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-10 11:20 [Adeos-main] tracer broken on 2.6.20-i386 Jan Kiszka
2007-02-10 13:16 ` [Adeos-main] " Jan Kiszka
2007-02-10 13:20   ` Jan Kiszka [this message]
2007-02-11 22:42     ` Philippe Gerum
2007-02-12  0:28       ` Jan Kiszka
2007-02-16 13:27         ` Philippe Gerum

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=45CDC6A0.1020407@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=rpm@xenomai.org \
    /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.