public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.31.4: WARNING: at arch/x86/kernel/hpet.c:390 hpet_next_event+0x70/0x80() [occurs when ACPI_PROCESSOR=y]
Date: Thu, 12 Nov 2009 15:49:43 -0800	[thread overview]
Message-ID: <1258069783.14894.10.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.0911121841420.5147@p34.internal.lan>

On Thu, 2009-11-12 at 18:45 -0500, Justin Piszcz wrote:
> 
> On Thu, 12 Nov 2009, john stultz wrote:
> 
> > Forgot to CC lkml, re-adding.
> >
> > On Thu, 2009-11-12 at 18:25 -0500, Justin Piszcz wrote:
> >> On Thu, 12 Nov 2009, john stultz wrote:
> >>> On Thu, Nov 12, 2009 at 8:33 AM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> >>>> On Thu, 12 Nov 2009, Justin Piszcz wrote:
> >>>>> On Wed, 11 Nov 2009, Justin Piszcz wrote:
> >>>>> Again, the problem:
> >>>>> [    3.318770] cpuidle: using governor ladder
> >>>>> [    3.321556] ------------[ cut here ]------------
> >>>>> [    3.321560] WARNING: at arch/x86/kernel/hpet.c:390
> >>>>> hpet_next_event+0x70/0x80()
> >>>>> [    3.321561] Hardware name:
> >>>>> [    3.321562] Modules linked in:
> >>>>> [    3.321564] Pid: 0, comm: swapper Not tainted 2.6.31.5 #17
> >>>>> [    3.321565] Call Trace:
> >>>>> [    3.321567]  [<ffffffff81042f00>] ? hpet_next_event+0x70/0x80
> >>>>> [    3.321568]  [<ffffffff81042f00>] ? hpet_next_event+0x70/0x80
> >>>>> [    3.321571]  [<ffffffff81056724>] ? warn_slowpath_common+0x74/0xd0
> >>>>> [    3.321573]  [<ffffffff81042f00>] ? hpet_next_event+0x70/0x80
> >>>>> [    3.321576]  [<ffffffff81077696>] ? tick_dev_program_event+0x36/0xb0
> >>>>> [    3.321578]  [<ffffffff81077079>] ?
> >>>>> tick_broadcast_oneshot_control+0x119/0x120
> >>>>> [    3.321579]  [<ffffffff8107683d>] ? tick_notify+0x22d/0x420
> >>>>> [    3.321581]  [<ffffffff8106fe37>] ? notifier_call_chain+0x37/0x70
> >>>>> [    3.321583]  [<ffffffff8107612b>] ? clockevents_notify+0x2b/0x90
> >>>>> [    3.321586]  [<ffffffff81244848>] ? acpi_idle_enter_bm+0x15f/0x2d3
> >>>>> [    3.321587]  [<ffffffff812446de>] ? acpi_idle_enter_c1+0xf1/0xfc
> >>>>> [    3.321590]  [<ffffffff812e6d7a>] ? cpuidle_idle_call+0xba/0x120
> >>>>> [    3.321593]  [<ffffffff8102b832>] ? cpu_idle+0x62/0xc0
> >>>>> [    3.321596] ---[ end trace cac202f11005305c ]---
> >>>>> [    3.553852] cpuidle: using governor menu
> >>>>
> >>>> Other user with this problem:
> >>>> http://lkml.org/lkml/2009/10/2/330 - Nobody responded to his report.
> >>>>
> >>>> This has been also been reported on other forums with no fix / conclusion on
> >>>> any type of fix or work-around.
> >>>
> >>> Looks like your hpet is busted, or maybe something is resetting the
> >>> hpet at exactly the wrong time.
> >>>
> >>> What does booting with the attached patch do?
> >>
> >> Unfortunately I cannot login fast enough to get a full dmesg:
> >
> > So if you comment out the printk I added, does it boot?
> I can login ok, its just a little slower with the message printing so quickly.

And just to be clear, without the patch it doesn't boot at all? 
Or is it fine, and you get just an annoying warning?

thanks
-john



  reply	other threads:[~2009-11-12 23:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08 14:35 2.6.31.4: WARNING: at arch/x86/kernel/hpet.c:390 hpet_next_event+0x70/0x80() Justin Piszcz
2009-11-11 19:50 ` Dave Jones
2009-11-11 21:32   ` 2.6.31.4: WARNING: at arch/x86/kernel/hpet.c:390 hpet_next_event+0x70/0x80() [occurs when ACPI_PROCESSOR=y] Justin Piszcz
2009-11-12 16:26     ` Justin Piszcz
2009-11-12 16:33       ` Justin Piszcz
2009-11-12 23:39         ` Justin Piszcz
     [not found]         ` <1f1b08da0911121513l32d47b4x8b9722ad3440ceb6@mail.gmail.com>
     [not found]           ` <alpine.DEB.2.00.0911121824290.2852@p34.internal.lan>
2009-11-12 23:40             ` john stultz
2009-11-12 23:45               ` Justin Piszcz
2009-11-12 23:49                 ` john stultz [this message]
2009-11-12 23:53                   ` Justin Piszcz
2009-11-12 23:53               ` Thomas Gleixner
2009-11-12 23:56                 ` Justin Piszcz
2009-11-13  0:18                   ` Pallipadi, Venkatesh
2009-11-13  0:20                     ` Justin Piszcz
2009-11-13  0:30                       ` Pallipadi, Venkatesh
2009-11-13  9:38                     ` Thomas Gleixner
2009-11-13 18:32                       ` Pallipadi, Venkatesh
2009-11-13 18:43                         ` Justin Piszcz
2009-11-14  1:12                           ` Pallipadi, Venkatesh
2009-11-14  8:48                             ` Justin Piszcz
2009-11-17 11:45                               ` Justin Piszcz
2009-11-17 21:37                                 ` Pallipadi, Venkatesh
2009-11-17 22:53                                   ` Justin Piszcz
2009-11-19 22:08                                     ` Pallipadi, Venkatesh
2009-11-19 23:12                                       ` Justin Piszcz

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=1258069783.14894.10.camel@localhost.localdomain \
    --to=johnstul@us.ibm.com \
    --cc=jpiszcz@lucidpixels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox