Incomplete stable drm/ast backport - screen freeze on boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Mantic |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
When connected to a remote machine via the BMC KVM functionality,
I am experiencing screen freezes when attempting to install mantic
(lunar is fine). Upstream master is also fine. Bisecting the ubuntu
kernel branch, I found:
```
git bisect start
# status: waiting for both good and bad commits
# bad: [0eec6d2a63d86a
git bisect bad 0eec6d2a63d86ac
# status: waiting for good commit(s), bad commit known
# good: [9ee3c53fe0c7d8
git bisect good 9ee3c53fe0c7d82
# good: [c344403b4a5fd6
git bisect good c344403b4a5fd6a
# good: [890166a2bf6fde
git bisect good 890166a2bf6fde5
# bad: [80b1a5a85758d1
git bisect bad 80b1a5a85758d11
# bad: [33252ba0195ad9
git bisect bad 33252ba0195ad94
# good: [81ab44acfe7947
git bisect good 81ab44acfe79470
# good: [119b834594e515
git bisect good 119b834594e5151
# good: [f46694216f1d5e
git bisect good f46694216f1d5ed
# bad: [f30e95bc205987
git bisect bad f30e95bc205987f
# bad: [88895f3d6635eb
git bisect bad 88895f3d6635ebf
# bad: [4b85b2ba439fc8
git bisect bad 4b85b2ba439fc85
# bad: [916ae609a033cb
git bisect bad 916ae609a033cbb
# first bad commit: [916ae609a033cb
```
Which led to test the upstream 6.5 stable branch and found the issue
present there as well. I have submitted a report upstream, copied below,
but I was hoping to get a quick resolution in Ubuntu as well, since
it appears that the BMC KVM is currently unusable on any machines that
have mantic installed, which is a bit of a precarious situation, since
the BMC KVM is intended as recovery tool.
Upstream report (https:/
```
The BMC on the machine in question is an ASpeed AST2600.
A quick bisect shows the problematic commit to be 2fb9667
("drm/ast: report connection status on Display Port.").
This is commit f81bb0ac upstream.
I believe the problem is that the previous commit in the series
e329cb5 ("drm/ast: Add BMC virtual connector")
was not backported to the stable branch.
As a consequence, it appears that the more accurate DP state detection
is causing the kernel to believe that no display is connected,
even when the BMC's virtual display is in fact in use.
A cherry-pick of e329cb5 onto the stable branch resolves the issue.
```
Changed in linux (Ubuntu): | |
status: | New → Invalid |
Just in case anybody else runs into this, an effective workaround is to set `modprobe. blacklist= ast` on the kernel command line.