[Bug 1207900] New: Thinkpad P16 Gen 1 freezes when put into Dockingstation
https://bugzilla.suse.com/show_bug.cgi?id=1207900 Bug ID: 1207900 Summary: Thinkpad P16 Gen 1 freezes when put into Dockingstation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: mvetter@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 864712 --> https://bugzilla.suse.com/attachment.cgi?id=864712&action=edit dmesg in dockingstation Thinkpad P16 Gen 1 with TW 20230131 freezes whenever I put it in the docking station while it is running. If I boot it while in the docking station, then everything is fine. Undocking it while it is running is fine as well. I will attach dmesg output inside docking station and without. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c1 --- Comment #1 from Michael Vetter <mvetter@suse.com> --- Created attachment 864713 --> https://bugzilla.suse.com/attachment.cgi?id=864713&action=edit dmesg without docking station -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 Michael Vetter <mvetter@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel Assignee|screening-team-bugs@suse.de |kernel-bugs@opensuse.org -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c2 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com --- Comment #2 from Takashi Iwai <tiwai@suse.com> --- What docking station is it, more specifically? If you have another dock model, could you test it to see whether the same problem happens, too? The splat from PCI AER could be suppressed via pci=noaer boot option. But it might be worth to try to turn off ASPM at first by giving pcie_aspm=off boot option. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c3 --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- Oh, and another important question: is this a regression by the recent updates? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c4 --- Comment #4 from Michael Vetter <mvetter@suse.com> ---
What docking station is it, more specifically?
It is the "Thinkpad Thunderbolt 4 workstation dock". Sorry I should have mentioned that :)
If you have another dock model, could you test it to see whether the same problem happens, too?
It is the only one I have.
is this a regression by the recent updates?
No. (I got this new work laptop/docking station recently so can't say for sure) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c5 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvetter@suse.com Flags| |needinfo?(mvetter@suse.com) --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- Then could you check a few old kernels to see whether it's a recent regression or not? Some kernel packages are found in my OBS repo like OBS home:tiwai:kernel:6.0, home:tiwai:kernel:5.19, ... Note that those are unofficial builds, hence you'd need to turn off Secure Boot (if enabled on BIOS). Also, please give the hwinfo output. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 Michael Vetter <mvetter@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mvetter@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c7 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mvetter@suse.com) --- Comment #7 from Takashi Iwai <tiwai@suse.com> --- So, did you try the boot options I mentioned in comment 2? Also, tests with the older kernels? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 Petr Vorel <petr.vorel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |petr.vorel@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c11 --- Comment #11 from Michael Vetter <mvetter@suse.com> --- With kernel 6.2.1-1-default and TW snapshot 20230308 my system doesn't freeze anymore. However it seems to fail to detect the external monitor correctly once I plug in the docking station. Keyboard and mouse work fine. Only notebook monitor is working. When I go to "Displays" in the GNOME settings I can see "unknown device" (or similar) for the external monitor. But not the name as I usually see it. And also I can't active it. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c12 --- Comment #12 from Michael Vetter <mvetter@suse.com> --- I updated today, and with kernel 6.2.2 this notebook doesn't boot at all anymore. A light on the caps lock key is blinking. I booted the previous btrfs snapshot now. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c13 --- Comment #13 from Michael Vetter <mvetter@suse.com> --- (In reply to Takashi Iwai from comment #5)
Then could you check a few old kernels to see whether it's a recent regression or not? Some kernel packages are found in my OBS repo like OBS home:tiwai:kernel:6.0, home:tiwai:kernel:5.19, ...
What's the proper way to do this? I assume: 1) Edit /etc/zypp/zypp.conf like: `multiversion.kernels = latest,latest-1,6.2.1-1-default,running` since 6.2.1 is the only Kernel that works more or less for me and I should keep a working one. 2) `zypper ar -f obs://home:tiwai:kernel:6.0 kernel6`, `zypper dup --from kernel6` to get the kernel-default (etc) packages from there? 3) reboot and select that kernel -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c14 --- Comment #14 from Takashi Iwai <tiwai@suse.com> --- /etc/zypp/zypp.conf should be with simply a few more entries like: multiversion.kernels = latest,latest-1,latest-2,latest-3,running It's for allowing to install more kernel packages than default (= 2). Then just download kernel-default.rpm from the OBS download URL, e.g. http://download.opensuse.org/repositories/home:/tiwai:/kernel:/6.0/standard/... And install it directly with zypper install --oldpackage option, e.g. % zypper in --oldpackage kernel-default-6.0.12-1.1.ga6c4f4e.x86_64.rpm Boot with that kernel and retest. If the test is done and the kernel is no longer needed, uninstall it % zypper rm kernel-default-6.0.12-1.1.ga6c4f4e -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c15 Michael Vetter <mvetter@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mvetter@suse.com) | --- Comment #15 from Michael Vetter <mvetter@suse.com> --- Thanks for the explanation. 6.0.12-1.1.ga6c4f4e: does not boot at all. I see `16.604928][T1003] spi-nor spi0.0: unrecognized JEDEC id bytes: 3c f0 30 09 6f 00` 5.19.12-1.1.g95fa5b8: does not boot at all. All I see after a while is a blinking cursor. I also updated to 6.2.4-1.1 now and with this I have the same behaviour like with 6.2.1-1, meaning it boots and I can use the laptop. However when I disconnect from docking station and then reconnect it doesn't detect the external monitor anymore. Any more information I can provide that would be helpful? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c16 --- Comment #16 from Takashi Iwai <tiwai@suse.com> --- You have disabled Secure Boot, right? Otherwise the unofficial kernels won't boot. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c17 --- Comment #17 from Michael Vetter <mvetter@suse.com> --- Yes I have. I also enabled it at first to see the difference. But all reported tests were with disabled secure boot (I also left it disabled for now). And the boot process started but didn't finish (that's what I meant with doesn't boot). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c18 --- Comment #18 from Takashi Iwai <tiwai@suse.com> --- And, if you boot with pcie_aspm=off, does the boot still hang? If I understand correctly, the original issue has been addressed with 6.2.1 kernel? Then the tests with older kernels are rather redundant... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c19 --- Comment #19 from Michael Vetter <mvetter@suse.com> ---
And, if you boot with pcie_aspm=off, does the boot still hang?
I did not test the old kernels with this. Should I now?
If I understand correctly, the original issue has been addressed with 6.2.1 kernel? Then the tests with older kernels are rather redundant... That's right. The freezing stops with 6.2.1. 6.2.2 doesn't boot at all. And 6.2.4 is fine like 6.2.1.
But I still can't work "normally". Every time I plug my laptop out of the docking station that will mean that I have to reboot the machine when I want to plug it in again. Since it will not recognize the external monitor otherwise. Every time the laptop goes go suspend, it will not detect the external monitor as well. And it even looks like it this will also happen if it just blanks the screen. By default after 5 min GNOME blanks the screen. And sometimes I had problems that after I return to the computer I had to force reboot. So yes the freezing doesn't happen anymore. But still its quite unusable. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c20 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #20 from Takashi Iwai <tiwai@suse.com> --- The AMDGPU problem is a completely different issue and we shouldn't mix in a single bug report. Please open another bug report, and let's close this one as fixed. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207900 Petr Vorel <petr.vorel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1209441 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com