From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Al Stone <al.stone@linaro.org>, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Hanjun Guo <hanjun.guo@linaro.org>,
kernel test robot <ying.huang@linux.intel.com>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0
Date: Sat, 10 Oct 2015 01:44:12 +0200 [thread overview]
Message-ID: <5618514C.3050806@intel.com> (raw)
In-Reply-To: <56184536.2020009@linaro.org>
On 10/10/2015 12:52 AM, Al Stone wrote:
> On 10/09/2015 03:02 PM, Rafael J. Wysocki wrote:
>> On Thursday, October 08, 2015 05:05:00 PM Al Stone wrote:
>>> On 10/08/2015 04:50 PM, Rafael J. Wysocki wrote:
>>>> On Thursday, October 08, 2015 02:32:15 PM Al Stone wrote:
>>>>> On 10/08/2015 02:41 PM, Rafael J. Wysocki wrote:
>>>>>> On Thursday, October 08, 2015 10:37:55 PM Rafael J. Wysocki wrote:
>>>>>>> On Thursday, October 08, 2015 10:36:40 AM Al Stone wrote:
>>>>>>>> On 10/08/2015 05:44 AM, Hanjun Guo wrote:
>>>>>>>>> On 10/08/2015 11:21 AM, kernel test robot wrote:
>>>>>>>>>> FYI, we noticed the below changes on
>>>>>>>>>>
>>>>>>>>>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>>>>>>>>>> commit 7494b07ebaae2117629024369365f7be7adc16c3 ("ACPI: add in a
>>>>>>>>>> bad_madt_entry() function to eventually replace the macro")
>>>>>>>>>>
>>>>>>>>>> [ 0.000000] ACPI: undefined MADT subtable type for FADT 4.0: 127 (length 12)
> [snip....]
>
>>> In the meantime, I'll poke the spec folks on the use of reserved subtable IDs
>>> in the MADT and see what the consensus is there. It may just be a matter of
>>> clarifying the language in the spec.
>> One additional question to ask is what checks have been present in the OSes
>> and what they do if they see a reserved MADT subtable ID. If they haven't been
>> doing anything so far, I'm afraid this particular train may be gone already.
> It may be gone. The silence so far is deafening :).
>
>>> It's also on my plate to really dig into an ACPI test suite and see about
>>> building something really robust for that -- this can be added as an example.
>>> I'll see if I have time to send in a patch for FWTS, too, which is pretty
>>> good about capturing such things.
>> Sounds good!
>>
>> Thanks,
>> Rafael
>>
> Let me know if I need to send the patch to fix the regression elsewhere; it
> dawned on me long after I sent it that this may not be the right place for it
> to go...
>
Please send it to linux-acpi@vger.kernel.org.
Thanks,
Rafael
prev parent reply other threads:[~2015-10-09 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871td6xcxc.fsf@yhuang-dev.intel.com>
2015-10-08 11:44 ` [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 Hanjun Guo
2015-10-08 16:36 ` Al Stone
2015-10-08 20:37 ` Rafael J. Wysocki
2015-10-08 20:41 ` Rafael J. Wysocki
2015-10-08 20:32 ` Al Stone
2015-10-08 22:50 ` Rafael J. Wysocki
2015-10-08 23:05 ` Al Stone
2015-10-09 21:02 ` Rafael J. Wysocki
2015-10-09 22:52 ` Al Stone
2015-10-09 23:44 ` Rafael J. Wysocki [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=5618514C.3050806@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=al.stone@linaro.org \
--cc=hanjun.guo@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=rjw@rjwysocki.net \
--cc=ying.huang@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).