Prev: [PATCH] freezer: only show the state of tasks refusing to freeze
Next: [kernel group] daily report 10/03/10
From: Pedro M. López on 10 Mar 2010 04:30 Kernel 2.6.33 [ 1.200658] ------------[ cut here ]------------ [ 1.200662] WARNING: at arch/x86/kernel/hpet.c:404 hpet_next_event+0x57/0x77() [ 1.200663] Hardware name: P55A-UD4 [ 1.200664] hpet: compare register read back failed. [ 1.200665] Modules linked in: [ 1.200666] Pid: 0, comm: swapper Not tainted 2.6.33-p1 #10 [ 1.200668] Call Trace: [ 1.200671] [<ffffffff8102c98f>] ? warn_slowpath_common+0x76/0x8c [ 1.200673] [<ffffffff8102c9f7>] ? warn_slowpath_fmt+0x40/0x45 [ 1.200676] [<ffffffff81026166>] ? find_busiest_group+0x341/0x7fe [ 1.200678] [<ffffffff81018eb1>] ? hpet_next_event+0x57/0x77 [ 1.200681] [<ffffffff81048d1e>] ? tick_dev_program_event+0x33/0x9e [ 1.200684] [<ffffffff81048836>] ? tick_broadcast_oneshot_control+0x9c/0xf5 [ 1.200686] [<ffffffff81048220>] ? tick_notify+0x1f9/0x34d [ 1.200688] [<ffffffff8104257a>] ? notifier_call_chain+0x2e/0x5b [ 1.200690] [<ffffffff81047c56>] ? clockevents_notify+0x31/0x139 [ 1.200693] [<ffffffff81175aa0>] ? acpi_idle_enter_simple+0x93/0x130 [ 1.200696] [<ffffffff811673c3>] ? acpi_write_bit_register+0x9e/0xab [ 1.200698] [<ffffffff8117585c>] ? acpi_idle_enter_bm+0xd3/0x284 [ 1.200701] [<ffffffff811f2705>] ? cpuidle_idle_call+0x89/0xc0 [ 1.200704] [<ffffffff81001256>] ? cpu_idle+0x9d/0xd7 [ 1.200707] ---[ end trace a4e806103d58b3e6 ]--- More info need??
From: john stultz on 10 Mar 2010 12:30
On Wed, Mar 10, 2010 at 1:01 AM, Pedro M. L�pez <pmlopez(a)multimensaje.es> wrote: > Kernel 2.6.33 > > [ � �1.200658] ------------[ cut here ]------------ > [ � �1.200662] WARNING: at arch/x86/kernel/hpet.c:404 hpet_next_event+0x57/0x77() > [ � �1.200663] Hardware name: P55A-UD4 > [ � �1.200664] hpet: compare register read back failed. > [ � �1.200665] Modules linked in: > [ � �1.200666] Pid: 0, comm: swapper Not tainted 2.6.33-p1 #10 > [ � �1.200668] Call Trace: > [ � �1.200671] �[<ffffffff8102c98f>] ? warn_slowpath_common+0x76/0x8c > [ � �1.200673] �[<ffffffff8102c9f7>] ? warn_slowpath_fmt+0x40/0x45 > [ � �1.200676] �[<ffffffff81026166>] ? find_busiest_group+0x341/0x7fe > [ � �1.200678] �[<ffffffff81018eb1>] ? hpet_next_event+0x57/0x77 > [ � �1.200681] �[<ffffffff81048d1e>] ? tick_dev_program_event+0x33/0x9e > [ � �1.200684] �[<ffffffff81048836>] ? > tick_broadcast_oneshot_control+0x9c/0xf5 > [ � �1.200686] �[<ffffffff81048220>] ? tick_notify+0x1f9/0x34d > [ � �1.200688] �[<ffffffff8104257a>] ? notifier_call_chain+0x2e/0x5b > [ � �1.200690] �[<ffffffff81047c56>] ? clockevents_notify+0x31/0x139 > [ � �1.200693] �[<ffffffff81175aa0>] ? acpi_idle_enter_simple+0x93/0x130 > [ � �1.200696] �[<ffffffff811673c3>] ? > acpi_write_bit_register+0x9e/0xab > [ � �1.200698] �[<ffffffff8117585c>] ? acpi_idle_enter_bm+0xd3/0x284 > [ � �1.200701] �[<ffffffff811f2705>] ? cpuidle_idle_call+0x89/0xc0 > [ � �1.200704] �[<ffffffff81001256>] ? cpu_idle+0x9d/0xd7 > [ � �1.200707] ---[ end trace a4e806103d58b3e6 ]--- > > More info need?? Known issue with that hardware:: http://bugzilla.kernel.org/show_bug.cgi?id=14996 There's a patch that quiets the warnings on its way to mainline. thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |