linux-kernel - Re: Two 2.6.20-rc5-rt2 issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <47345.192.168.1.8.1168994713.squirrel@www.rncbc.org>
Date:	Wed, 17 Jan 2007 00:45:13 -0000 (WET)
From:	"Rui Nuno Capela" <rncbc@...bc.org>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Two 2.6.20-rc5-rt2 issues

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

> * Rui Nuno Capela <rncbc@...bc.org> 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 as .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.

Cheers.
-- 
rncbc aka Rui Nuno Capela
rncbc@...bc.org
Download attachment "config.gz" of type "application/x-gzip" (20296 bytes)