From: Chr <chunkeey@web.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [Bug #10369] The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7
Date: Wed, 9 Apr 2008 14:24:59 +0200 [thread overview]
Message-ID: <200804091424.59648.chunkeey@web.de> (raw)
In-Reply-To: <SvnMeM-aZi.A.x8E.s-_-HB@albercik>
On Wednesday 09 April 2008 01:02:09 Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.24. Please verify if it still should be listed.
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=10369
> Subject : The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7
> Submitter : Chr <chunkeey@web.de>
> Date : 2008-03-30 21:09 (10 days old)
> References : http://lkml.org/lkml/2008/3/30/87
> Handled-By : Thomas Gleixner <tglx@linutronix.de>
It's still there in 2.6.25-rc8-git7. The workarounds so far:
either disable chronyd (NTP-Daemon: my system clock
is a bit too fast: ~ -0.879 seconds) or "noapictimer" parameter.
Regards,
Chr.
next prev parent reply other threads:[~2008-04-09 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 23:02 [Bug #10369] The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7 Rafael J. Wysocki
2008-04-09 12:24 ` Chr [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-13 18:53 2.6.25-rc9: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-04-13 18:56 ` [Bug #10369] The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7 Rafael J. Wysocki
2008-04-13 20:02 ` Thomas Gleixner
2008-04-13 20:37 ` Chr
2008-04-14 12:51 ` Thomas Gleixner
2008-04-14 15:12 ` 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=200804091424.59648.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=linux-kernel@vger.kernel.org \
--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 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.