New: BUG: kernel NULL pointer dereference, address: 0000000000000000

https://bugzilla.kernel.org/show_bug.cgi?id=216422

            Bug ID: 216422
           Summary: BUG: kernel NULL pointer dereference, address:
                    0000000000000000
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.18.0-rc1-1-00059-g87d0e2f41b8c
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: USB
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Created attachment 301686
--> https://bugzilla.kernel.org/attachment.cgi?id=301686&action=edit
dmesg with NULL pointer dereferences.

Hi,

Several users including me are experiencing an issue with Thinkpads becoming completely unresponsive after several hours. This seems to happen more often shortly after the system has been idle for some time.
The issue only occurs when the Thinkpad is already connected to a USB C docking station before booting.

dmesg shows regular
"BUG: kernel NULL pointer dereference, address: 0000000000000000" that do not cause a crash however.
These only show up, when the systemd upower.service is running.

In the attached dmesg.txt, I booted with upower.service disabled and started it manually which immediately lead to the NULL pointer dereference (but no crash).

We bisected and found the offending commit in
https://bbs.archlinux.org/viewtopic.php?id=279027

Please see the attached bisect-log.txt .

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=216422

--- Comment #1 from Jan ([email protected]) --- Created attachment 301687
--> https://bugzilla.kernel.org/attachment.cgi?id=301687&action=edit
bisect log

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=216422

Eric Haynes ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #2 from Eric Haynes ([email protected]) ---
I am also experiencing this. I'm not sure if modern docking stations are more than just a USB C hub, but in case it matters, I have an external monitor and a keyboard connected via USB C but do not own a docking station.

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=216422

The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected],
                   |                            |[email protected]

--- Comment #3 from The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) --- Thx for the bisect. That commits is known to cause some trouble. See this
thread:
https://lore.kernel.org/all/[email protected]/

A fix for that problem is heading towards mainline currently:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=5f73aa2cf8bef4a39baa1591c3144ede4788826e

Might be worth giving it a shot.

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=216422

Artem S. Tashkinov ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #4 from Artem S. Tashkinov ([email protected]) --- Is this still an issue in 6.7.9 or 6.8?

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.