linux-kernel - Re: A question about acpi_early_init(), and want to invoke acpi_early

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 14 Jul 2017 17:01:01 +0200
From:   Julian Wollrath <jwollrath@....de>
To:     Dou Liyang <douly.fnst@...fujitsu.com>
Cc:     "Rafael J. Wysocki" <rjw@...ysocki.net>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: A question about acpi_early_init(), and want to invoke
 acpi_early_init() earlier

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