public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Julian Wollrath <jwollrath@web.de>
To: Dou Liyang <douly.fnst@cn.fujitsu.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: A question about acpi_early_init(), and want to invoke acpi_early_init() earlier
Date: Fri, 14 Jul 2017 17:01:01 +0200	[thread overview]
Message-ID: <20170714170101.3edfaf46@saldaea> (raw)
In-Reply-To: <66904bb8-36ca-beb3-f19c-4796aae743df@cn.fujitsu.com>

Hi,

> > I reproduced it by the following command line:
> >     ...noapic acpi_sci=level...
> >
> > the original dmesg is:
> >
> > [    0.000000] tsc: Fast TSC calibration using PIT
> >
> > the broken dmesg is:
> >
> > [    0.001000] tsc: PIT calibration matches HPET. 1 loops
> >
> > Is it right? If it is wrong, please give the right process for
> > reproducing.
yes, this is right, see [1] for the original thread.

The earliest I could move the call of acpi_early_init() without
triggering the bug back than is shown in the patch at [2] but
unforunately I do not have access to the Thinkpad X121e I had back than
anymore, so I cannot help with regression testing.

Cheers,
Julian

[1] https://lkml.org/lkml/2014/3/10/123
[2] https://lkml.org/lkml/2014/3/11/424

-- 
 ()  ascii ribbon campaign - against html e-mail 
 /\                        - against proprietary attachments

  reply	other threads:[~2017-07-14 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 13:26 A question about acpi_early_init(), and want to invoke acpi_early_init() earlier Dou Liyang
2017-07-11 13:29 ` Dou Liyang
2017-07-13  5:53 ` Dou Liyang
2017-07-14 15:01   ` Julian Wollrath [this message]
2017-07-18  0:53     ` Dou Liyang

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=20170714170101.3edfaf46@saldaea \
    --to=jwollrath@web.de \
    --cc=douly.fnst@cn.fujitsu.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    /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