Re: clockevents_program_event WARN_ON preventing boot.

From: Yinghai Lu
Date: Thu May 02 2013 - 16:54:23 EST


On Thu, May 2, 2013 at 12:58 PM, Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:

>
> The check should be:
>
> if (td->evtdev && tick_device_is_functional(td->evtdev))

still happens.

[ 3.457866] checking TSC synchronization [CPU#0 -> CPU#10]: passed.
[ 3.460806] SMP alternatives: lockdep: fixing up alternatives
[ 3.464282] ------------[ cut here ]------------
[ 3.464297] WARNING: at kernel/time/clockevents.c:209
clockevents_program_event+0x3b/0x100()
[ 3.464300] Modules linked in:
[ 3.464306] CPU: 10 PID: 0 Comm: swapper/10 Not tainted
3.9.0-yh-08066-g1252014-dirty #1537
[ 3.464308] Hardware name: Oracle Corporation unknown /
, BIOS 11016600 05/17/2011
[ 3.464327] 0000000000000009 ffff88203e203ed8 ffffffff82091022
ffff88203e203f18
[ 3.464343] ffffffff81088990 ffff88203e203f08 80000000003d08ff
80000000003d08ff
[ 3.464359] 000000000000000a ffff881027557fd8 0000000000000000
ffff88203e203f28
[ 3.464361] Call Trace:
[ 3.464379] <IRQ> [<ffffffff82091022>] dump_stack+0x19/0x1b
[ 3.464392] [<ffffffff81088990>] warn_slowpath_common+0x70/0xa0
[ 3.464395] [<ffffffff810889da>] warn_slowpath_null+0x1a/0x20
[ 3.464399] [<ffffffff810e312b>] clockevents_program_event+0x3b/0x100
[ 3.464403] [<ffffffff810e35ec>] tick_handle_periodic+0x4c/0x80
[ 3.464409] [<ffffffff820ae8cd>] smp_apic_timer_interrupt+0x8d/0xa3
[ 3.464418] [<ffffffff820adbef>] apic_timer_interrupt+0x6f/0x80
[ 3.464426] <EOI> [<ffffffff810527f7>] ? default_idle+0x57/0xd0
[ 3.464430] [<ffffffff810527f5>] ? default_idle+0x55/0xd0
[ 3.464434] [<ffffffff81053078>] arch_cpu_idle+0x18/0x20
[ 3.464438] [<ffffffff810dbec5>] cpu_startup_entry+0x165/0x210
[ 3.464446] [<ffffffff8207f3ad>] start_secondary+0x1df/0x1e6
[ 3.464469] ---[ end trace 89673eac7a3370c6 ]---
[ 3.717988] smpboot: Booting processor 11 APIC 0x26 ip 0x90000


>
>> a clue: If I disable CONFIG_SLUB_DEBUG, or even boot with slub_debug=- then it boots fine.
>
> Huch? That does not make any sense.

I don't have that CONFIG_SLUB_DEBUG in .config

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