LKML Archive on
help / color / mirror / Atom feed
From: "Rui Nuno Capela" <>
To: "Ingo Molnar" <>
Subject: Re: Two 2.6.20-rc5-rt2 issues
Date: Wed, 17 Jan 2007 00:45:13 -0000 (WET)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

On Tue, January 16, 2007 11:56, Ingo Molnar wrote:

> * Rui Nuno Capela <> wrote:
>> First one is about building for UP (CONFIG_SMP not set) on my old P4
>> laptop. As it seems, all my build attempts failed at the final link
>> stage, with undefined references to paravirt_enable. After disabling
>> CONFIG_PARAVIRT I get a similar failure, but this time for a couple
>> kvm* symbols. [...]
> ok, i think i have managed to fix both bugs. I have released -rt3,
> please re-check whether it works any better. If it still doesnt then
> please send me the exact .config that fails.

Building this already with -rt5, still gives:
  LD      arch/i386/boot/compressed/vmlinux
  OBJCOPY arch/i386/boot/vmlinux.bin
  BUILD   arch/i386/boot/bzImage
Root device is (3, 2)
Boot sector 512 bytes.
Setup is 7407 bytes.
System is 1427 kB
Kernel: arch/i386/boot/bzImage is ready  (#1)
WARNING: "profile_hits" [drivers/kvm/kvm-intel.ko] undefined!
WARNING: "profile_hits" [drivers/kvm/kvm-amd.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2

.config \x7fas .gz is attached.

>> Second one is already about running SMP, on a Dual Core2 T7200, for
>> which the build goes fine but run-time is haunted by a crippling BUG:
>> Call Trace:
>> [<c0102dad>] __switch_to+0xcc/0x176
>> [<c01185c8>] wake_up_process+0x19/0x1b
>> [<c01fe568>] acpi_ec_gpe_handler+0x1f/0x53
>> [<c01ec6c6>] acpi_ev_gpe_dispatch+0x64/0x163
>> [<c01eca06>] acpi_ev_gpe_detect+0x94/0xd7
> hm, this is a -rt specific thing that i hoped to have worked around but
> apparently not. The ACPI code uses a waitqueue in its idle routine
> (argh!) which cannot by done sanely on PREEMPT_RT. In -rt3 i've added
> a more conservative (but still ugly and incorrect) hack - could you try
> it, does -rt3 work any better?

Yes it does. No BUG has been spotted on -rt3, yet.

rncbc aka Rui Nuno Capela

[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 20296 bytes --]

  reply	other threads:[~2007-01-17  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2007-01-16 11:56 ` Ingo Molnar
2007-01-17  0:45   ` Rui Nuno Capela [this message]
2007-01-17  6:31     ` Ingo Molnar
2007-01-17  8:58       ` Rui Nuno Capela

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: Two 2.6.20-rc5-rt2 issues' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).