linux-kernel - Re: The never ending BEEEEP/__smp_call_function

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] [day] [month] [year] [list]

Message-Id: <200804021445.19021.chunkeey@web.de>
Date:	Wed, 2 Apr 2008 14:45:18 +0200
From:	Chr <chunkeey@....de>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
	Andi Kleen <andi-suse@...stfloor.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7

On Tuesday 01 April 2008 23:16:15 Rafael J. Wysocki wrote:
> On Tuesday, 1 of April 2008, Chr wrote:
> > On Tuesday 01 April 2008 01:14:24 Rafael J. Wysocki wrote:
> > > On Tuesday, 1 of April 2008, Chr wrote:
> > >
> > > Have you posted the .config already?
> >
> > Done!
>
> Hmm.  Can you please choose one RTC infrastructure and maybe disable
> CONFIG_HPET_EMULATE_RTC?
well... another hang... but I noticed something while filling a new bugreport.

2.6.25-rc8 /arch/x86/Kconfig

config HPET_TIMER
        def_bool X86_64
        prompt "HPET Timer Support" if X86_32

[...]

config HPET_EMULATE_RTC
        def_bool y

[...]

Geee... there's no way to disable it on x86_64 without messing with the 
Kconfig. So I try to disable the other RTC framework... 
(since there's no sign of any of those RTC mods in the clocksource/timerlist.
I guess it'll be worthless)

Regards,	
	Chr.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/