From: Chr <chunkeey@web.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Andi Kleen <andi-suse@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7
Date: Wed, 2 Apr 2008 14:45:18 +0200 [thread overview]
Message-ID: <200804021445.19021.chunkeey@web.de> (raw)
In-Reply-To: <200804012316.16371.rjw@sisk.pl>
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.
next prev parent reply other threads:[~2008-04-02 12:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 19:09 The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7 Chr
2008-03-30 19:25 ` Rafael J. Wysocki
2008-03-30 19:59 ` Thomas Gleixner
2008-03-30 20:18 ` Chr
2008-03-30 20:37 ` Thomas Gleixner
2008-03-30 21:09 ` Chr
2008-03-30 21:36 ` Thomas Gleixner
2008-03-30 22:19 ` Chr
2008-03-31 12:56 ` Adrian Bunk
2008-03-31 13:23 ` Chr
2008-03-31 22:01 ` Chr
2008-03-31 23:14 ` Rafael J. Wysocki
2008-03-31 23:30 ` Chr
2008-04-01 21:16 ` Rafael J. Wysocki
2008-04-01 22:27 ` Chr
2008-04-02 12:45 ` Chr [this message]
2008-04-01 16:27 ` Thomas Gleixner
2008-04-01 18:57 ` Chr
2008-04-01 22:29 ` Chr
2008-04-02 7:08 ` Thomas Gleixner
2008-04-02 9:34 ` Chr
2008-03-31 7:10 ` Andi Kleen
2008-03-31 12:51 ` Chr
-- strict thread matches above, loose matches on Subject: below --
2008-04-03 22:49 2.6.25-rc8-git2: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-04-03 23:22 ` The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7 Rafael J. Wysocki
2008-04-04 1:49 ` Chr
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=200804021445.19021.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=akpm@linux-foundation.org \
--cc=andi-suse@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.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