public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.31.4: WARNING: at arch/x86/kernel/hpet.c:390 hpet_next_event+0x70/0x80()
Date: Wed, 11 Nov 2009 14:50:16 -0500	[thread overview]
Message-ID: <20091111195016.GB22225@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0911080932590.4556@p34.internal.lan>

On Sun, Nov 08, 2009 at 09:35:33AM -0500, Justin Piszcz wrote:
 > Motherboard: Intel DP55KG
 > BIOS: 3878P (latest as of 11/08/09)
 > 
 > When CPUFREQ is compiled in the kernel:
 > 
 > [    3.377946]  [<ffffffff81043180>] ? hpet_next_event+0x70/0x80
 > [    3.377947]  [<ffffffff81043180>] ? hpet_next_event+0x70/0x80
 > [    3.377950]  [<ffffffff810564d4>] ? warn_slowpath_common+0x74/0xd0
 > [    3.377952]  [<ffffffff81043180>] ? hpet_next_event+0x70/0x80
 > [    3.377954]  [<ffffffff81076fd6>] ? tick_dev_program_event+0x36/0xb0
 > [    3.377956]  [<ffffffff810769b9>] ? tick_broadcast_oneshot_control+0x119/0x120
 > [    3.377957]  [<ffffffff8107617d>] ? tick_notify+0x22d/0x420
 > [    3.377960]  [<ffffffff8106f737>] ? notifier_call_chain+0x37/0x70
 > [    3.377961]  [<ffffffff81075a6b>] ? clockevents_notify+0x2b/0x90
 > [    3.377964]  [<ffffffff812438a8>] ? acpi_idle_enter_bm+0x15f/0x2d3
 > [    3.377966]  [<ffffffff8124373e>] ? acpi_idle_enter_c1+0xf1/0xfc
 > [    3.377969]  [<ffffffff812e84ea>] ? cpuidle_idle_call+0xba/0x120
 > [    3.377972]  [<ffffffff8102b830>] ? cpu_idle+0x60/0xa0
 > [    3.377975] ---[ end trace 222f8db6d7ba1b9b ]---
 
This also happens if cpufreq is a module ?
There's no cpufreq code in that trace, so I'm puzzled.

 > [    3.883303] cpufreq-core: trying to register driver acpi-cpufreq
 > [    3.883305] cpufreq-core: adding CPU 0
 > [    3.883348] cpufreq-core: initialization failed
 > [    3.883349] cpufreq-core: adding CPU 1
 > [    3.883390] cpufreq-core: initialization failed
 > [    3.883391] cpufreq-core: adding CPU 2
 > [    3.883432] cpufreq-core: initialization failed
 > [    3.883433] cpufreq-core: adding CPU 3
 > [    3.883473] cpufreq-core: initialization failed
 > [    3.883474] cpufreq-core: adding CPU 4
 > [    3.883515] cpufreq-core: initialization failed
 > [    3.883516] cpufreq-core: adding CPU 5
 > [    3.883556] cpufreq-core: initialization failed
 > [    3.883557] cpufreq-core: adding CPU 6
 > [    3.883598] cpufreq-core: initialization failed
 > [    3.883599] cpufreq-core: adding CPU 7
 > [    3.883639] cpufreq-core: initialization failed
 > [    3.883640] cpufreq-core: no CPU initialized for driver acpi-cpufreq

Does acpi-cpufreq work when built as a module ?
If it does, seeing the differences in output from booting with cpufreq.debug=7
might yield some clues.

	Dave


  reply	other threads:[~2009-11-11 19:50 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 [this message]
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
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=20091111195016.GB22225@redhat.com \
    --to=davej@redhat.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    /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