kri
March 7, 2023, 8:14am
1
Hello
I’ve recently encountered another strange behavior with Manjaro: Every time when I disconnect my Thunderbolt Dock (Dell WD22TB4) and reconnect it, the displays wont turn on. When i manually power them, they stay black. However, Manjaro recognizes the monitors and expands my desktop as usual and the connected devices of the dock are also working normally.
The output of boltctl
and boltctl monitor
are also normal.
● Dell WD22TB4 Thunderbolt Dock
├─ type: peripheral
├─ name: WD22TB4 Thunderbolt Dock
├─ vendor: Dell
├─ uuid: c10...fff
├─ generation: USB4
├─ status: authorized
│ ├─ domain: ed9c...fff
│ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s
│ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s
│ └─ authflags: none
├─ authorized: Di 07 Mär 2023 07:48:42
├─ connected: Di 07 Mär 2023 07:48:41
└─ stored: Do 03 Nov 2022 07:33:58
├─ policy: iommu
└─ key: no
I have to reboot my system to get my monitors working again.
~$ inxi -b -a -G -J -x
System:
Host: alienware Kernel: 6.1.12-1-MANJARO arch: x86_64 bits: 64 compiler: gcc
v: 12.2.1 parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
root=UUID=97c37ae5-35c0-4fd3-80a4-a7ecaf3fad24 rw quiet
cryptdevice=UUID=83b3ecb5-0465-4d91-8c3a-f240695eb071:luks-83b3ecb5-0465-4d91-8c3a-f240695eb071
root=/dev/mapper/luks-83b3ecb5-0465-4d91-8c3a-f240695eb071 apparmor=1
security=apparmor
resume=/dev/mapper/luks-85d6d627-c623-4bfa-bb6d-a7892a5b4e83
udev.log_priority=3 ibt=off
Desktop: Cinnamon v: 5.6.7 tk: GTK v: 3.24.36 vt: 7 dm: LightDM v: 1.32.0
Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Laptop System: Alienware product: Alienware m15 R7 v: N/A
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Alienware model: 02R5KV v: A00 serial: <superuser required>
UEFI: Alienware v: 1.14.0 date: 12/09/2022
Battery:
ID-1: BAT0 charge: 59.6 Wh (97.2%) condition: 61.3/84.3 Wh (72.8%)
volts: 12.7 min: 11.4 model: BYD DELL M59JH1A type: Li-poly serial: 1220
status: charging
CPU:
Info: 14-core (6-mt/8-st) 12th Gen Intel Core i7-12700H [MST AMCP]
arch: Alder Lake speed (MHz): avg: 2205 min/max: 400/4600:4700:3500
Graphics:
Device-1: Intel Alder Lake-P Integrated Graphics vendor: Dell driver: i915
v: kernel arch: Gen-12.2 process: Intel 10nm built: 2021-22+ ports:
active: DP-3,DP-5,eDP-1 empty: DP-1,DP-2,DP-4 bus-ID: 00:02.0
chip-ID: 8086:46a6 class-ID: 0300
Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Dell
driver: nvidia v: 525.89.02 alternate: nouveau,nvidia_drm non-free: 525.xx+
status: current (as of 2023-02) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 1 speed: 2.5 GT/s
lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none
empty: HDMI-A-1,eDP-2 bus-ID: 01:00.0 chip-ID: 10de:2560 class-ID: 0300
Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
bus-ID: 3-5:2 chip-ID: 0c45:6a10 class-ID: 0e02
Device-4: Logitech BRIO Ultra HD Webcam type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 3-6.1.3.2.1:17 chip-ID: 046d:085e
class-ID: 0102 serial: 43FB6A01
Display: x11 server: X.Org v: 21.1.7 driver: X: loaded: modesetting,nvidia
dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 7040x1440 s-dpi: 96 s-size: 1863x381mm (73.35x15.00")
s-diag: 1902mm (74.86")
Monitor-1: not-matched mapped: DP-1-1 pos: left res: 2560x1440 hz: 75
dpi: 109 size: 597x336mm (23.5x13.23") diag: 685mm (26.97") modes: N/A
Monitor-2: not-matched mapped: DP-1-3 pos: primary,center res: 2560x1440
hz: 75 dpi: 109 size: 597x336mm (23.5x13.23") diag: 685mm (26.97")
modes: N/A
Monitor-3: eDP-1 pos: right model: LG Display 0x06e2 built: 2021
res: 1920x1080 hz: 165 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64")
diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.5 renderer: Mesa Intel Graphics (ADL GT2)
direct-render: Yes
Network:
Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:51f0 class-ID: 0280
Device-2: Realtek Killer E3000 2.5GbE vendor: Dell driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 3c:00.0
chip-ID: 10ec:3000 class-ID: 0200
Device-3: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152
bus-ID: 2-1.4.4:5 chip-ID: 0bda:8153 class-ID: 0000 serial: 1113000001
Drives:
Local Storage: total: 1.16 TiB used: 691.27 GiB (58.2%)
USB:
Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
Hub-2: 2-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 20 Gb/s
chip-ID: 1d6b:0003 class-ID: 0900
Hub-3: 2-1:2 info: Intel USB3.0 Hub ports: 4 rev: 3.2 speed: 10 Gb/s
chip-ID: 8087:0b40 class-ID: 0900
Hub-4: 2-1.4:3 info: Realtek Dell dock ports: 4 rev: 3.1 speed: 10 Gb/s
chip-ID: 0bda:0487 class-ID: 0900
Hub-5: 2-1.4.3:4 info: Realtek Dell dock ports: 4 rev: 3.1 speed: 5 Gb/s
chip-ID: 0bda:0413 class-ID: 0900
Device-1: 2-1.4.4:5 info: Realtek RTL8153 Gigabit Ethernet Adapter
type: Network driver: r8152 interfaces: 1 rev: 3.2 speed: 5 Gb/s
power: 112mA chip-ID: 0bda:8153 class-ID: 0000 serial: 1113000001
Hub-6: 3-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0
speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 3-5:2 info: Microdia Integrated_Webcam_HD type: Video
driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA
chip-ID: 0c45:6a10 class-ID: 0e02
Hub-7: 3-6:6 info: Fresco Logic USB2.0 Hub ports: 4 rev: 2.1
speed: 480 Mb/s chip-ID: 1d5c:5801 class-ID: 0900
Hub-8: 3-6.1:7 info: Realtek Dell dock ports: 5 rev: 2.1 speed: 480 Mb/s
chip-ID: 0bda:5487 class-ID: 0900
Hub-9: 3-6.1.3:8 info: Realtek Dell dock ports: 6 rev: 2.1 speed: 480 Mb/s
chip-ID: 0bda:5413 class-ID: 0900
Device-1: 3-6.1.3.1:10 info: Logitech Advanced Corded Mouse M500s
type: Mouse,HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0
speed: 12 Mb/s power: 300mA chip-ID: 046d:c093 class-ID: 0300
serial: 206F30475743
Hub-10: 3-6.1.3.2:16 info: VIA Labs USB2.0 Hub ports: 4 rev: 2.1
speed: 480 Mb/s chip-ID: 2109:2822 class-ID: 0900
Device-1: 3-6.1.3.2.1:17 info: Logitech BRIO Ultra HD Webcam
type: Video,Audio driver: snd-usb-audio,uvcvideo interfaces: 5 rev: 2.1
speed: 480 Mb/s power: 500mA chip-ID: 046d:085e class-ID: 0102
serial: 43FB6A01
Device-2: 3-6.1.3.2.2:18 info: GN Netcom Jabra EVOLVE Link MS
type: Audio,HID driver: jabra,snd-usb-audio,usbhid interfaces: 4 rev: 2.0
speed: 12 Mb/s power: 500mA chip-ID: 0b0e:0305 class-ID: 0300
serial: 000FD5839D2E0A
Device-3: 3-6.1.3.3:11 info: Logitech G910 Orion Spectrum Mechanical
Keyboard type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2
rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 046d:c335 class-ID: 0300
serial: 1670315E3931
Device-4: 3-6.1.3.5:12 info: Dell dock type: HID
driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 480 Mb/s
power: 100mA chip-ID: 413c:b06f class-ID: 0300
Device-5: 3-6.1.5:9 info: Dell dock type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 480 Mb/s power: 100mA chip-ID: 413c:b06e
class-ID: 0300
Device-6: 3-7:3 info: Alienware LED controller type: HID
driver: hid-generic,usbhid interfaces: 1 rev: 2.1 speed: 12 Mb/s
chip-ID: 187c:0550 class-ID: 0300 serial: 00.01
Device-7: 3-8:4 info: Darfon Keyboard type: Keyboard
driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s
power: 100mA chip-ID: 0d62:dabc class-ID: 0301
Device-8: 3-10:5 info: Intel AX201 Bluetooth type: Bluetooth driver: btusb
interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 8087:0026
class-ID: e001
Hub-11: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
chip-ID: 1d6b:0003 class-ID: 0900
Info:
Processes: 540 Uptime: 15m wakeups: 3 Memory: 62.49 GiB
used: 25.42 GiB (40.7%) Init: systemd v: 252 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
pkgs: 1721 libs: 377 tools: pamac,yay pm: flatpak pkgs: 0 Shell: Bash
v: 5.1.16 running-in: gnome-terminal inxi: 3.3.25
Any ideas?
Regards
Zesko
March 7, 2023, 9:02am
2
I also use my thunderbolt dock with my Thinkpad laptop to connect dual monitors.
I have no problem re-connecting the dock when using Intel iGPU only, no Nvidia.
Check journalctl --no-pager -p 3 -b -1 after failure of reconnecting and reboot.
Do other peripherals work like USB devices or ethernet on your docking station?
Try to run lspci -v
to enumerate the available devices.
kri
March 7, 2023, 1:34pm
4
Yes, the peripheral devices are working. If I had to guess, I would say its a problem with the GPU and Thunderbolt.
kri
March 16, 2023, 7:45am
5
So it happend again.
Yesterday tb3 worked just fine and today after connecting it a second time i had the same issue.
here is the journal log
Mär 16 08:32:05 alienware bluetoothd[1386]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mär 16 08:32:24 alienware kernel: ACPI Error: Thread 3911843840 cannot release Mutex [ECMX] acquired by thread 2718744960 (20220331/exmutex-378)
Mär 16 08:32:24 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:32:24 alienware kernel: ACPI Error: Thread 1758708096 cannot release Mutex [ECMX] acquired by thread 2718744960 (20220331/exmutex-378)
Mär 16 08:32:24 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:32:28 alienware cinnamon-screensaver-pam-helper[1827691]: pam_unix(cinnamon-screensaver:auth): conversation failed
Mär 16 08:32:28 alienware cinnamon-screensaver-pam-helper[1827691]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [kris]
Mär 16 08:33:04 alienware cinnamon-screensaver-pam-helper[1828592]: pam_unix(cinnamon-screensaver:auth): conversation failed
Mär 16 08:33:04 alienware cinnamon-screensaver-pam-helper[1828592]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [kris]
Mär 16 08:34:02 alienware kernel: pcieport 0000:04:00.0: Unable to change power state from D3hot to D0, device inaccessible
Mär 16 08:34:02 alienware kernel: pcieport 0000:05:04.0: Unable to change power state from D3hot to D0, device inaccessible
Mär 16 08:34:02 alienware kernel: pcieport 0000:05:03.0: Unable to change power state from D3hot to D0, device inaccessible
Mär 16 08:34:02 alienware kernel: pcieport 0000:05:02.0: Unable to change power state from D3hot to D0, device inaccessible
Mär 16 08:34:02 alienware kernel: pcieport 0000:05:01.0: Unable to change power state from D3hot to D0, device inaccessible
Mär 16 08:34:02 alienware kernel: pcieport 0000:05:00.0: Unable to change power state from D3hot to D0, device inaccessible
Mär 16 08:34:09 alienware kernel: ACPI Error: Thread 2228035776 cannot release Mutex [ECMX] acquired by thread 526369152 (20220331/exmutex-378)
Mär 16 08:34:09 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:34:12 alienware kernel: i915 0000:00:02.0: [drm] *ERROR* [ENCODER:244:DDI TC1/PHY TC1][DPRX] Failed to enable link training
Mär 16 08:34:13 alienware kernel: i915 0000:00:02.0: [drm] *ERROR* Step 2 of creating MST payload for 0000000076e0d6c9 failed: -5
Mär 16 08:34:21 alienware kernel: i915 0000:00:02.0: [drm] *ERROR* [ENCODER:244:DDI TC1/PHY TC1][DPRX] Failed to enable link training
Mär 16 08:34:23 alienware kernel: i915 0000:00:02.0: [drm] *ERROR* Step 2 of creating MST payload for 0000000076e0d6c9 failed: -5
Mär 16 08:34:23 alienware kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe C FIFO underrun: port,transcoder,
Mär 16 08:37:13 alienware kernel: pcieport 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible
Mär 16 08:37:13 alienware kernel: pcieport 0000:05:04.0: Unable to change power state from D3cold to D0, device inaccessible
Mär 16 08:37:13 alienware kernel: pcieport 0000:05:03.0: Unable to change power state from D3cold to D0, device inaccessible
Mär 16 08:37:13 alienware kernel: pcieport 0000:05:00.0: Unable to change power state from D3cold to D0, device inaccessible
Mär 16 08:37:13 alienware kernel: pcieport 0000:05:01.0: Unable to change power state from D3cold to D0, device inaccessible
Mär 16 08:37:13 alienware kernel: pcieport 0000:05:02.0: Unable to change power state from D3cold to D0, device inaccessible
Mär 16 08:37:21 alienware kernel: i915 0000:00:02.0: [drm] *ERROR* [ENCODER:244:DDI TC1/PHY TC1][DPRX] Failed to enable link training
Mär 16 08:37:23 alienware kernel: i915 0000:00:02.0: [drm] *ERROR* Step 2 of creating MST payload for 00000000c1b5c7f2 failed: -5
Mär 16 08:37:31 alienware kernel: i915 0000:00:02.0: [drm] *ERROR* [ENCODER:244:DDI TC1/PHY TC1][DPRX] Failed to enable link training
Mär 16 08:37:32 alienware kernel: i915 0000:00:02.0: [drm] *ERROR* Step 2 of creating MST payload for 00000000c1b5c7f2 failed: -5
Mär 16 08:37:32 alienware kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe C FIFO underrun: port,transcoder,
Mär 16 08:38:04 alienware systemd-coredump[1833750]: Failed to connect to coredump service: Connection refused
Mär 16 08:38:04 alienware systemd-coredump[1833794]: Failed to connect to coredump service: Connection refused
Mär 16 08:38:04 alienware systemd-coredump[1833844]: Failed to connect to coredump service: Connection refused
Mär 16 08:38:04 alienware systemd-coredump[1833971]: Failed to connect to coredump service: Connection refused
Mär 16 08:39:06 alienware kernel: ACPI Error: Thread 1730527616 cannot release Mutex [ECMX] acquired by thread 1093836992 (20220331/exmutex-378)
Mär 16 08:39:06 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:39:06 alienware kernel: ACPI Error: Thread 1730527616 cannot release Mutex [ECMX] acquired by thread 1093836992 (20220331/exmutex-378)
Mär 16 08:39:06 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:39:06 alienware kernel: ACPI Error: Thread 2193620992 cannot release Mutex [ECMX] acquired by thread 4044857536 (20220331/exmutex-378)
Mär 16 08:39:06 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:39:06 alienware kernel: ACPI Error: Thread 1480966528 cannot release Mutex [ECMX] acquired by thread 314638336 (20220331/exmutex-378)
Mär 16 08:39:06 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:39:06 alienware kernel: ACPI Error: Thread 4044857536 cannot release Mutex [ECMX] acquired by thread 1320943616 (20220331/exmutex-378)
Mär 16 08:39:06 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:39:06 alienware kernel: ACPI Error: Thread 1480966528 cannot release Mutex [ECMX] acquired by thread 3631415296 (20220331/exmutex-378)
Mär 16 08:39:06 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:39:07 alienware kernel: ACPI Error: Thread 1366868352 cannot release Mutex [ECMX] acquired by thread 2200510656 (20220331/exmutex-378)
Mär 16 08:39:07 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:39:07 alienware kernel: ACPI Error: Thread 4149248000 cannot release Mutex [ECMX] acquired by thread 2200510656 (20220331/exmutex-378)
Mär 16 08:39:07 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:39:07 alienware kernel: ACPI Error: Thread 1042596224 cannot release Mutex [ECMX] acquired by thread 2200510656 (20220331/exmutex-378)
Mär 16 08:39:07 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:39:07 alienware kernel: ACPI Error: Thread 4167073792 cannot release Mutex [ECMX] acquired by thread 2200510656 (20220331/exmutex-378)
Mär 16 08:39:07 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20220331/psparse-529)
Mär 16 08:39:08 alienware kernel: ACPI Error: Cannot release Mutex [ECMX], not acquired (20220331/exmutex-357)
Mär 16 08:39:08 alienware kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_MUTEX_NOT_ACQUIRED) (20220331/psparse-529)
Mär 16 08:39:35 alienware systemd-cryptsetup[1834780]: Device luks-83b3ecb5-0465-4d91-8c3a-f240695eb071 is still in use.
Mär 16 08:39:35 alienware systemd-cryptsetup[1834780]: Failed to deactivate: Device or resource busy
Mär 16 08:39:37 alienware kernel: watchdog: watchdog0: watchdog did not stop!
Zesko
March 16, 2023, 10:00am
6
That would look like the kernel’s issue.
Try to update the current kernel 6.1.19 or switch to Kernel 5.15
kri
March 17, 2023, 8:39am
7
I see… Well 5.15 doesn’t work properly on this machine either. I updated to 6.2.6.
Is there maybe a kernel flag that I can set to avoid this issue?
Zesko
March 17, 2023, 9:15am
8
Check BIOS and disable “Power On Lid Open” option.
Source: ACPI error
kri
March 17, 2023, 10:26am
9
Holy cow. that might actually be it. I activated that options a few weeks ago but didn’t recognize it as a potential cause. Hopefully that will fix it.
Thank you anyway!
system
Closed
March 22, 2023, 7:45am
10
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.