From: Al Stone <ahs3@redhat.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Valdis Kletnieks <valdis.kletnieks@vt.edu>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next 20180515 - ACPI disabled..
Date: Tue, 15 May 2018 15:49:15 -0600 [thread overview]
Message-ID: <664f2475-9718-d38e-7270-3426c94f86e8@redhat.com> (raw)
In-Reply-To: <CAHp75VdwDPumYBphE0BTE=ngsvGkWKuOr9QjBv4c+yw-1pKBWg@mail.gmail.com>
On 05/15/2018 03:23 PM, Andy Shevchenko wrote:
> +Cc: Rafael
>
> On Wed, May 16, 2018 at 12:18 AM, <valdis.kletnieks@vt.edu> wrote:
>> Seeing this at boot with linux-next 20180415. ACPI gets disabled, hilarity and hijinks
>> result - everything from a lot of stuff can't find an IRQ to the dual-core w/ HT CPU
>> coming up as just 1 core no HT. 20180430 works just fine...
>>
>> [ 0.000000] ACPI: Early table checksum verification disabled
>> [ 0.000000] ACPI: RSDP 0x00000000CB7F1000 000024 (v02 DELL )
>> [ 0.000000] ACPI: XSDT 0x00000000CB7F1088 000094 (v01 DELL CBX3 01072009 AMI 00010013)
>> [ 0.000000] ACPI: FACP 0x00000000CB7FB720 00010C (v05 DELL CBX3 01072009 AMI 00010013)
>> [ 0.000000] ACPI: DSDT 0x00000000CB7F11B0 00A56F (v02 DELL CBX3 00000021 INTL 20091112)
>> [ 0.000000] ACPI: FACS 0x00000000CCFED080 000040
>> [ 0.000000] ACPI: APIC 0x00000000CB7FB830 000072 (v03 DELL CBX3 01072009 AMI 00010013)
>> [ 0.000000] ACPI: FPDT 0x00000000CB7FB8A8 000044 (v01 DELL CBX3 01072009 AMI 00010013)
>> [ 0.000000] ACPI: TCPA 0x00000000CB7FB8F0 000032 (v02 APTIO4 NAPAASF 00000001 MSFT 01000013)
>> [ 0.000000] ACPI: MCFG 0x00000000CB7FB928 00003C (v01 DELL CBX3 01072009 MSFT 00000097)
>> [ 0.000000] ACPI: HPET 0x00000000CB7FB968 000038 (v01 DELL CBX3 01072009 AMI. 00000005)
>> [ 0.000000] ACPI: SSDT 0x00000000CB7FB9A0 000415 (v01 SataRe SataTabl 00001000 INTL 20091112)
>> [ 0.000000] ACPI: SSDT 0x00000000CB7FBDB8 0009B9 (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
>> [ 0.000000] ACPI: SSDT 0x00000000CB7FC778 000B22 (v01 PmRef CpuPm 00003000 INTL 20051117)
>> [ 0.000000] ACPI: DMAR 0x00000000CB7FD2A0 000080 (v01 INTEL SNB 00000001 INTL 00000001)
>> [ 0.000000] ACPI: ASF! 0x00000000CB7FD320 0000A5 (v32 INTEL HCG 00000001 TFSM 000F4240)
>> [ 0.000000] ACPI: SSDT 0x00000000CB7FD3C8 000579 (v01 AMITCG PROC 00000001 INTL 20051117)
>> [ 0.000000] ACPI: BGRT 0x00000000CB7FD948 000038 (v00 ?? 01072009 AMI 00010013)
>> [ 0.000000] ACPI: SSDT 0x00000000CB7FD980 00198A (v01 NvdRef NvdTabl 00001000 INTL 20091112)
>> [ 0.000000] ACPI: Local APIC address 0xfee00000
>> [ 0.000000] ACPI: [APIC:0x05] Invalid zero length
>> [ 0.000000] ACPI: Error parsing LAPIC address override entry
>> [ 0.000000] ACPI: Invalid BIOS MADT, disabling ACPI
>> [ 0.000000] tsc: Fast TSC calibration using PIT
>>
>> On next-20180430, the boot goes like this, and continues properly:
>>
>> [ 0.000000] ACPI: SSDT 0x00000000CB7FD980 00198A (v01 NvdRef NvdTabl 00001000 INTL 20091112)
>> [ 0.000000] ACPI: Local APIC address 0xfee00000
>> [ 0.000000] tsc: Fast TSC calibration using PIT
>>
>> Not seeing any commits to drivers/acpi/tables.c other than Al Stone's.
>>
>> This ringing any bells before I go bisecting?
>>
>
>
>
Not off-hand. Could you please send me a copy of /sys/firmware/acpi/tables/APIC
on this machine? The commit cd8c65a6442b that I wrote looks like it got pulled
in on 20180430, which if I'm understanding correctly, seems to have fixed the
problem. Did this work before 20180415? I assume it did.
What puzzles me is that this message:
ACPI: [APIC:0x05] Invalid zero length
should only have shown up if the MADT has a broken subtable, and I think that
bit of code has been that way for quite some time (git blame says somewhere
around 2012 when the test for this condition was put in).
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@redhat.com
-----------------------------------
next prev parent reply other threads:[~2018-05-15 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 21:18 valdis.kletnieks
2018-05-15 21:23 ` Andy Shevchenko
2018-05-15 21:49 ` Al Stone [this message]
2018-05-15 22:25 ` valdis.kletnieks
2018-05-15 22:40 ` Al Stone
2018-05-16 11:58 ` Rafael J. Wysocki
2018-05-17 22:01 ` valdis.kletnieks
2018-05-18 7:41 ` Rafael J. Wysocki
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=664f2475-9718-d38e-7270-3426c94f86e8@redhat.com \
--to=ahs3@redhat.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=valdis.kletnieks@vt.edu \
/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
all inboxes | Powered by JetHome®