On 3/3/25 10:20, Kenneth Crudup wrote:
Building now. Fingers crossed!
So far, so good- tried a variety of suspend/hibernate with/without
scenarios on none, one and two connected monitors, and I can't get any
resume OOPSes. Nice!
I did see one anomaly I haven't seen before, but I'm not sure if it's
related to this patch (or original commit, masked by the OOPS) or not.
For some reason after resuming from the 2nd or 3rd hibernation cycle my
Belkin Dock couldn't get authorized by boltd after I'd plugged it in
post-hibernation-resume. It was indeed authorized the first time
(post-hibernate) with the new code (was plugged in at the time of resume):
----
2025-03-03T10:39:34.405568-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] parent is 63ae8780-500c...
2025-03-03T10:39:34.406815-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] connected: connected
(/sys/devices/pci0000:00/0000:00:0d.2/domain0/0-0/0-1)
2025-03-03T10:39:34.406995-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] auto-auth: authmode:
enabled, policy: iommu, iommu: yes -> ok
2025-03-03T10:39:34.407094-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] auto-auth: security:
iommu+user mode, key: no -> ok
2025-03-03T10:39:34.407287-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] authorize: authorization
prepared for 'user' level
2025-03-03T10:39:34.408876-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] udev: device changed:
authorizing -> authorizing
2025-03-03T10:39:34.412223-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] udev: device changed:
authorizing -> authorizing
2025-03-03T10:39:34.417191-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] authorize: finished: ok
(status: authorized, flags: 0)
2025-03-03T10:39:34.417414-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] auto-auth: authorization
successful
2025-03-03T10:39:34.419207-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] udev: device changed:
authorized -> authorized
2025-03-03T10:47:42.252854-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] disconnected
(/sys/devices/pci0000:00/0000:00:0d.2/domain0/0-0/0-1)
----
But after that, it wouldn't get authorized again until I'd rebooted:
----
2025-03-03T10:47:42.252854-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] disconnected
(/sys/devices/pci0000:00/0000:00:0d.2/domain0/0-0/0-1)
2025-03-03T10:49:24.319123-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] parent is 63ae8780-500c...
2025-03-03T10:49:24.320239-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] connected: connected
(/sys/devices/pci0000:00/0000:00:0d.2/domain0/0-0/0-1)
2025-03-03T10:49:24.320320-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] auto-auth: authmode:
enabled, policy: iommu, iommu: yes -> ok
2025-03-03T10:49:24.320368-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] auto-auth: security:
iommu+user mode, key: no -> ok
2025-03-03T10:49:24.320449-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] authorize: authorization
prepared for 'user' level
2025-03-03T10:49:24.320539-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] udev: device changed:
authorizing -> authorizing
2025-03-03T10:49:24.321698-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] udev: device changed:
authorizing -> authorizing
2025-03-03T10:49:24.335697-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] authorize: finished: FAIL
(status: auth-error, flags: 0)
2025-03-03T10:49:24.335817-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] auto-auth: authorization
failed: kernel error: write error: Cannot allocate memory
2025-03-03T10:49:59.011121-08:00 xps-9320 boltd[1240]:
[c2010000-0072-Thunderbolt 3 Dock Core ] disconnected
(/sys/devices/pci0000:00/0000:00:0d.2/domain0/0-0/0-1)
----
Oh, and while I couldn't see any of the USB functions of the dock, the
DP tunnel was working, the external (cable-attached) monitor was on.
There were no kernel messages from the failure either (but I didn't have
TB dyndbg turned on).
Several attempts at reconnecting and a fully-disconnected power-cycle of
the dock gave the same error until I'd rebooted the laptop. What's
interesting is my CalDigit dock had no problem being recognized when I'd
plugged it in during these failures:
----
2025-03-03T11:03:33.383513-08:00 xps-9320 boltd[1240]:
[80a78780-00b3-TS4 ] parent is 833f8780-3179...
2025-03-03T11:03:33.385441-08:00 xps-9320 boltd[1240]:
[80a78780-00b3-TS4 ] connected: connected
(/sys/devices/pci0000:00/0000:00:0d.3/domain1/1-0/1-1)
2025-03-03T11:03:33.385585-08:00 xps-9320 boltd[1240]:
[80a78780-00b3-TS4 ] auto-auth: authmode:
enabled, policy: iommu, iommu: yes -> ok
2025-03-03T11:03:33.385635-08:00 xps-9320 boltd[1240]:
[80a78780-00b3-TS4 ] auto-auth: security:
iommu+user mode, key: no -> ok
2025-03-03T11:03:33.385733-08:00 xps-9320 boltd[1240]:
[80a78780-00b3-TS4 ] authorize: authorization
prepared for 'user' level
2025-03-03T11:03:33.387211-08:00 xps-9320 boltd[1240]:
[80a78780-00b3-TS4 ] udev: device changed:
authorizing -> authorizing
2025-03-03T11:03:33.389891-08:00 xps-9320 boltd[1240]:
[80a78780-00b3-TS4 ] udev: device changed:
authorizing -> authorizing
2025-03-03T11:03:34.395468-08:00 xps-9320 boltd[1240]:
[80a78780-00b3-TS4 ] authorize: finished: ok
(status: authorized, flags: 0)
2025-03-03T11:03:34.395641-08:00 xps-9320 boltd[1240]:
[80a78780-00b3-TS4 ] auto-auth: authorization
successful
2025-03-03T11:03:34.395943-08:00 xps-9320 boltd[1240]:
[80a78780-00b3-TS4 ] udev: device changed:
authorized -> authorized
----
I'll keep an eye out for it if it happens again, but at least it's not
crashing!
-Kenny
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
