Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1243730
| From | Al Stone <al.stone@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 |
| Date | 2015-10-10 01:00 +0200 |
| Message-ID | <qhONQ-7Be-5@gated-at.bofh.it> (permalink) |
| References | <qhhRU-2oG-37@gated-at.bofh.it> <qhrRf-8pC-15@gated-at.bofh.it> <qhstX-WT-11@gated-at.bofh.it> <qhMCm-4yA-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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...
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Linaro Enterprise Group
al.stone@linaro.org
-----------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 Hanjun Guo <hanjun.guo@linaro.org> - 2015-10-08 13:50 +0200
Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 Al Stone <al.stone@linaro.org> - 2015-10-08 18:40 +0200
Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2015-10-08 22:10 +0200
Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2015-10-08 22:20 +0200
Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 Al Stone <al.stone@linaro.org> - 2015-10-08 22:40 +0200
Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2015-10-09 00:30 +0200
Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 Al Stone <al.stone@linaro.org> - 2015-10-09 01:10 +0200
Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2015-10-09 22:40 +0200
Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 Al Stone <al.stone@linaro.org> - 2015-10-10 01:00 +0200
Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 "Rafael J. Wysocki" <rafael.j.wysocki@intel.com> - 2015-10-10 01:50 +0200
csiph-web