Bug 211895 - dell_wmi_sysman causes unbootable system
Summary: dell_wmi_sysman causes unbootable system
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Platform_x86 (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-22 13:26 UTC by Borislav Gerassimov
Modified: 2021-03-01 15:15 UTC (History)
2 users (show)

See Also:
Kernel Version: 5.11
Tree: Mainline
Regression: No


Attachments
journalctl from the failed boot (174.88 KB, text/plain)
2021-02-22 13:26 UTC, Borislav Gerassimov
Details
journalctl from the failed boot - DELL E5470 (131.85 KB, text/plain)
2021-02-26 09:16 UTC, Petr Špaček
Details
journalctl from 5.11.2 + the patch by Mario (135.79 KB, text/plain)
2021-03-01 12:12 UTC, Borislav Gerassimov
Details

Description Borislav Gerassimov 2021-02-22 13:26:42 UTC
Created attachment 295399 [details]
journalctl from the failed boot

The affected system is a Dell Latitude E5570 running ArchLinux with latest firmware/UEFI/etc. The system boots to a general protection fault screen (see https://bugs.archlinux.org/task/69702 - there is an attached screenshot in the first comment).
I've also just tested with linux-next from 20210222 - the problem persists. Blacklisting 'dell_wmi_sysman' is the only solution for reaching a working system.

Tell me if I can be of any help.
Comment 1 Petr Špaček 2021-02-26 09:16:46 UTC
Created attachment 295461 [details]
journalctl from the failed boot - DELL E5470
Comment 2 Petr Špaček 2021-02-26 09:18:10 UTC
Panic reproduced also on Dell Latitude E5470/0MT53G, BIOS 1.23.3 08/04/2020 with kernel 5.11.1.

First log lines about WMI are:
wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method not found
acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)

and then boot goes on for a second. Several processes cause stack traces to be printed, pointing all over the place. Blacklisting the module workarounds the problem.
Comment 3 Mario Limonciello 2021-02-26 18:57:47 UTC
So if it's 5.11.1 as well as linux-next then you have https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/dell-wmi-sysman?h=linux-5.11.y&id=215164bfb7144c5890dd8021ff06e486939862d4 already applied then.

> 5570/5470?  

These are quite old right - like they came out in 2015/2016 time frame.

I would expect they don't support this interface, but they should have bailed more gracefully too.

Can you please test https://lkml.org/lkml/2021/2/18/748
It needs to be re-spun from maintainer feedback, but I think it will fix the issue for you.  If it works for you, i'll respin it soon and you can test the new one as well hopefully.
Comment 4 Borislav Gerassimov 2021-03-01 12:12:55 UTC
Created attachment 295547 [details]
journalctl from 5.11.2 + the patch by Mario
Comment 5 Borislav Gerassimov 2021-03-01 15:15:51 UTC
There is no change in the behavior with the above patch.

Note You need to log in before you can comment on or make changes to this bug.