Bug 209239

Summary:	General protection faults from 5.8.7 on when booting with Apple Magic Trackpad 2 connected
Product:	Drivers	Reporter:	eomanis
Component:	Input Devices	Assignee:	drivers_input-devices
Status:	NEW ---
Severity:	normal	CC:	felixhaedicke, jan.steffens, jose.exposito89, mike.osipov
Priority:	P1
Hardware:	x86-64
OS:	Linux
Kernel Version:	5.8.7	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	Kernel log (excerpt) from booting 5.8.7 with trackpad attached

Description eomanis 2020-09-11 13:50:10 UTC

Created attachment 292471 [details]
Kernel log (excerpt) from booting 5.8.7 with trackpad attached

Arch Linux, with linux-5.8.7-arch1-1 and linux-5.8.8-arch1-1, last known good kernel is linux-5.8.6-arch1-1

When booting the system while an Apple Magic Trackpad 2 is connected to USB, multiple general protection faults occur, which usually prevent the system from booting up to a usable state.

However, no kernel errors occur and everything seems to work properly when booting e.g. linux-5.8.8-arch1-1 without the trackpad and attaching it later. Suspend/resume while the trackpad is connected also seems to work.

The trackpad is connected via an external USB 2.0 hub.
Here some hopefully useful info, both obtained on 5.8.8 with the trackpad connected after bootup:

* Output of "lsusb"
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 048d:8297 Integrated Technology Express, Inc. IT8297 RGB LED Controller
Bus 001 Device 007: ID 046d:c328 Logitech, Inc. Corded Keyboard K280e
Bus 001 Device 005: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
Bus 001 Device 008: ID 054c:0268 Sony Corp. Batoh Device / PlayStation 3 Controller
Bus 001 Device 012: ID 05ac:0265 Apple, Inc. 
Bus 001 Device 006: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

* Output of "lsusb -t"
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
    |__ Port 6: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
    |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 1: Dev 12, If 0, Class=Human Interface Device, Driver=usbhid, 12M
                |__ Port 1: Dev 12, If 3, Class=Human Interface Device, Driver=usbhid, 12M
                |__ Port 1: Dev 12, If 1, Class=Human Interface Device, Driver=usbhid, 12M
                |__ Port 1: Dev 12, If 2, Class=Human Interface Device, Driver=usbhid, 12M
                |__ Port 2: Dev 8, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 3: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 3: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 4: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 4: Dev 7, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 4: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M

Also see the respective distribution-specific bug report [1].
I am attaching the same kernel log from that report here.

[1] https://bugs.archlinux.org/task/67860

Comment 1 Felix Hädicke 2020-11-24 21:38:44 UTC

Could you please check, if this is somehow related to bug 210241?

Does this patch make a difference?
https://patchwork.kernel.org/project/linux-input/patch/20201119082232.8774-1-felixhaedicke@web.de/raw

Comment 2 Jan Steffens 2021-02-10 18:38:21 UTC

(In reply to Felix Hädicke from comment #1)
> Could you please check, if this is somehow related to bug 210241?
> 
> Does this patch make a difference?
> https://patchwork.kernel.org/project/linux-input/patch/20201119082232.8774-1-
> felixhaedicke@web.de/raw

This patch is currently in the Arch Linux kernel (5.10 series). As it has been rejected upstream I will not carry it into the 5.11 series. If you still care about this issue, please get it fixes upstream.

Comment 3 José Expósito 2021-05-16 09:06:30 UTC

Hi Jan,

I'm experimenting similar issues, so I submitted a patch upstream:
https://lore.kernel.org/patchwork/patch/1423070/

I'd be really helpful if you could test the patch and confirm if it solved the issue also for your hardware and kernel.

Thanks a lot in advance,
Jose