public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Kay Sievers <kay@vrfy.org>
Subject: Re: Force enabled HPET at 0x%lx
Date: Sun, 19 Aug 2012 22:22:02 +0800	[thread overview]
Message-ID: <20120819142202.GA24014@localhost> (raw)
In-Reply-To: <20120819141824.GC251@x4>

On Sun, Aug 19, 2012 at 04:18:24PM +0200, Markus Trippelsdorf wrote:
> On 2012.08.19 at 22:02 +0800, Fengguang Wu wrote:
> > Hi,
> > 
> >         [   38.650387] PCI host bridge to bus 0000:00
> >         [   38.657920] pci_bus 0000:00: Force enabled HPET at 0x%lx
> >                                                                 ~~~
> > 
> > That "0x%lx" message should be emitted by one of the dev_printks in
> > arch/x86/kernel/quirks.c and I failed to see anything wrong with it:
> > 
> >                 dev_printk(KERN_DEBUG, &dev->dev, "Force enabled HPET at "
> >                         "0x%lx\n", force_hpet_address);
> > 
> > So why the value of "force_hpet_address" is not printed?
> > 
> >         [   38.657920] busn_res: [bus 00-ff] is inserted under domain [bus 00-ff]
> >         [   38.658480] pci_bus 0000:00: ^A0root bus resource [bus 00-ff]
> >         [   38.662411] pci_bus 0000:00: ^A0root bus resource [io  0x0000-0xffff]
> >         [   38.664639] pci_bus 0000:00: ^A0root bus resource [mem 0x00000000-0xffffffffff]
> >                                         ~~~
> > 
> > And that ^A0 character also looks strange..
> 
> http://lkml.org/lkml/2012/8/18/143
> 
> Fix:
> http://git.kernel.org/?p=linux/kernel/git/gregkh/driver-core.git;a=commitdiff;h=ebdc82899ec5ed35af1c79ed6a4eeda69dad9b90

Quick hand! Thanks!

Fengguang

      reply	other threads:[~2012-08-19 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-19 14:02 Force enabled HPET at 0x%lx Fengguang Wu
2012-08-19 14:18 ` Markus Trippelsdorf
2012-08-19 14:22   ` Fengguang Wu [this message]

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=20120819142202.GA24014@localhost \
    --to=fengguang.wu@intel.com \
    --cc=kay@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.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