From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: valdis.kletnieks@vt.edu
Cc: ahs3@redhat.com, Andy Shevchenko <andy.shevchenko@gmail.com>,
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: Wed, 16 May 2018 13:58:04 +0200 [thread overview]
Message-ID: <2369798.f7cP5IOQk6@aspire.rjw.lan> (raw)
In-Reply-To: <58438.1526423130@turing-police.cc.vt.edu>
On Wednesday, May 16, 2018 12:25:30 AM CEST valdis.kletnieks@vt.edu wrote:
> On Tue, 15 May 2018 15:49:15 -0600, Al Stone said:
>
> > Not off-hand. Could you please send me a copy of /sys/firmware/acpi/tables/APIC
>
> cat /sys/firmware/acpi/tables/APIC | od -x
> 0000000 5041 4349 0072 0000 3903 4544 4c4c 2020
> 0000020 4243 3358 2020 0020 2009 0107 4d41 2049
> 0000040 0013 0001 0000 fee0 0001 0000 0800 0001
> 0000060 0001 0000 0800 0202 0001 0000 0800 0103
> 0000100 0001 0000 0800 0304 0001 0000 0c01 0002
> 0000120 0000 fec0 0000 0000 0a02 0000 0002 0000
> 0000140 0000 0a02 0900 0009 0000 000d 0604 05ff
> 0000160 0100
> 0000162
>
> > 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.
>
> 0430 is what I'm running right ow, and it works. Everything before that too.
> It fell over sometime between 0430 and 0515,
>
> > 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).
There was one commit that I had to drop.
Please try linux-next tomorrow and let me know if it works for you.
next prev parent reply other threads:[~2018-05-16 11:58 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
2018-05-15 22:25 ` valdis.kletnieks
2018-05-15 22:40 ` Al Stone
2018-05-16 11:58 ` Rafael J. Wysocki [this message]
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=2369798.f7cP5IOQk6@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=ahs3@redhat.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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®