From: Frans Pop <elendil@planet.nl>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, john stultz <johnstul@us.ibm.com>
Subject: Re: [stable 2.6.24] WARNING: at kernel/time/clockevents.c
Date: Wed, 13 Feb 2008 09:47:10 +0100 [thread overview]
Message-ID: <200802130947.10781.elendil@planet.nl> (raw)
In-Reply-To: <alpine.LFD.1.00.0802130845380.12988@apollo.tec.linutronix.de>
On Wednesday 13 February 2008, Thomas Gleixner wrote:
> On Tue, 12 Feb 2008, Andrew Morton wrote:
> > On Sun, 10 Feb 2008 14:40:21 +0100 Frans Pop <elendil@planet.nl> wrote:
> > the hrtimer code is preparing an invalid ktime_t. Note that
> > clockevents_program_event() actually fails when this happens - I am
> > surprised that this is not causing observeable userspace problems.
> >
> > The WARN_ON_ONCE() means that you'll only see this warning once per
> > boot. But the actually error could be happening any number of times
> > without being reported.
> >
> > Looks pretty serious?
>
> Yes. It's the same problem, which got fixed with:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit
>;h=62f0f61e6673e67151a7c8c0f9a09c7ea43fe2b5
OK, so probably glibc performs a unit test during build that asks for a long
sleep. I guess that makes sense.
Thanks Thomas and Andrew.
next prev parent reply other threads:[~2008-02-13 8:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 13:40 [stable 2.6.24] WARNING: at kernel/time/clockevents.c Frans Pop
2008-02-10 14:20 ` Frans Pop
2008-02-13 7:07 ` Andrew Morton
2008-02-13 8:21 ` Thomas Gleixner
2008-02-13 8:47 ` Frans Pop [this message]
2008-02-13 9:32 ` Thomas Gleixner
2008-02-13 21:40 ` Frans Pop
2008-02-14 0:20 ` Thomas Gleixner
2008-02-14 11:30 ` Frans Pop
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=200802130947.10781.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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.