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 22:40:03 +0100 [thread overview]
Message-ID: <200802132240.04357.elendil@planet.nl> (raw)
In-Reply-To: <alpine.LFD.1.00.0802131004460.12988@apollo.tec.linutronix.de>
On Wednesday 13 February 2008, Thomas Gleixner wrote:
> can you please apply the following patch ? I really should have
> thought about that, when I fixed the above one.
I still get the bug with this patch. At least I'm now certain it happens
during glibc compilation and that I can reproduce it.
I applied your patch on top of 2.6.24.2 (applied with only minor offsets)
because I also saw the issue with that kernel and I don't yet completely
trust 2.6.25.
Here's the error from this run:
WARNING: at kernel/time/clockevents.c:82 clockevents_program_event()
Pid: 27638, comm: ld-linux.so.2 Not tainted 2.6.24.2-test1 #39
Call Trace:
[<ffffffff8024afaf>] ktime_get+0xc/0x41
[<ffffffff8024ea59>] clockevents_program_event+0x3b/0x94
[<ffffffff8024f8c8>] tick_program_event+0x31/0x4d
[<ffffffff8024a2fd>] hrtimer_reprogram+0x3b/0x51
[<ffffffff8024a478>] enqueue_hrtimer+0x66/0x102
[<ffffffff8024ad38>] hrtimer_start+0x102/0x125
[<ffffffff8819f403>] :ext3:__ext3_journal_stop+0x1f/0x3d
[<ffffffff803f8dcc>] rt_mutex_slowlock+0x90/0x53a
[<ffffffff802667e8>] find_lock_page+0x29/0x8d
[<ffffffff80277a78>] find_extend_vma+0x16/0x59
[<ffffffff802509b2>] get_futex_key+0x82/0x14e
[<ffffffff80251ac5>] futex_lock_pi+0x60f/0x90d
[<ffffffff8024a70d>] hrtimer_wakeup+0x0/0x21
[<ffffffff803f8dcc>] rt_mutex_slowlock+0x90/0x53a
[<ffffffff802527cb>] do_futex+0xa08/0xa3d
[<ffffffff803f9c59>] error_exit+0x0/0x51
[<ffffffff80252d48>] compat_sys_futex+0xf0/0x10e
[<ffffffff8020a6f1>] __switch_to+0x10e/0x27e
[<ffffffff80231889>] schedule_tail+0x23/0x60
[<ffffffff80223972>] ia32_sysret+0x0/0xa
Cheers,
FJP
next prev parent reply other threads:[~2008-02-13 22:00 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
2008-02-13 9:32 ` Thomas Gleixner
2008-02-13 21:40 ` Frans Pop [this message]
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=200802132240.04357.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.