[radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state

Bug #1969815 reported by Daniel LaSalle
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned
marco (Ubuntu)
New
Undecided
Unassigned
xorg-server (Ubuntu)
New
Undecided
Unassigned

Bug Description

I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end-user experience)

For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken.

The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated.

Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left.

That behavior held true for all TTYs.

Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK.

Solution was: unplug one of the two monitor and automagically jammy's login screen popped up.

If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re-back again at the jammy login having lost the current session that I had.

Both of my screens are the same model and both use HDMI.

I have attached my ~/.config/monitors.xml
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: dd 3464333 F.... pulseaudio
 /dev/snd/controlC0: dd 3464333 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
DistroRelease: Ubuntu 22.04
HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb
InstallationDate: Installed on 2020-08-29 (613 days ago)
InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
 lo no wireless extensions.

 enp7s0 no wireless extensions.

 tun0 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: xorg-server
PackageArchitecture: amd64
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-25-generic N/A
 linux-backports-modules-5.15.0-25-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
RfKill:

Tags: jammy
Uname: Linux 5.15.0-25-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/02/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5809
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Daniel LaSalle (daniellasalle) wrote :
description: updated
summary: - 22.04-machine rendered totally useless because of dual-screen (post-
- install)
+ 22.04-machine rendered totally useless because of (portrait(?)) dual-
+ screen (post-install)
Revision history for this message
Daniel LaSalle (daniellasalle) wrote : Re: 22.04-machine rendered totally useless because of (portrait(?)) dual-screen (post-install)

Here's a final update from my end: using that single monitor when I go under "Displays" and then change my monitor's rotation to either right or left I will kill my TTY7 session and bring me back at login

no longer affects: ubuntu-mate
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: Dual screens started blinking from blank to another type of blank for =<1 second each state

Thanks for the bug report. Please run:

  lspci -k > lspci.txt
  journal -b0 > journal.txt

and attach the resulting text files here.

summary: - 22.04-machine rendered totally useless because of (portrait(?)) dual-
- screen (post-install)
+ Dual screens started blinking from blank to another type of blank for
+ =<1 second each state
Changed in marco (Ubuntu):
status: New → Incomplete
Changed in xorg-server (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel LaSalle (daniellasalle) wrote :

$ lspci -k > lspci.txt
$ journal -b0 > journal.txt
zsh: command not found: journal
$ which journal
journal not found
$ sudo apt install journal -y
[sudo] password for dd:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package journal
$

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sorry, I made a typo. Please run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

tags: added: radeon
summary: - Dual screens started blinking from blank to another type of blank for
- =<1 second each state
+ [radeon] Dual screens started blinking from blank to another type of
+ blank for =<1 second each state
Revision history for this message
Daniel LaSalle (daniellasalle) wrote :
Changed in marco (Ubuntu):
status: Incomplete → New
Changed in xorg-server (Ubuntu):
status: Incomplete → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I wonder if this is another DRM regression that started in kernel 5.14.21 ...

Please try some older kernels from:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

Revision history for this message
Daniel LaSalle (daniellasalle) wrote :

What I'll tell you is this has been working fine since AT LEAST 18.04-LTS and just with 22.04 it broke.

In terms of deploying a new kernel, since this a production machine, I can't do anything that I want.

Would there be an easy way to do so? such as via apt, reboot, select new kernel or is manual/compiling work in order here?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

There is no compilation necessary. Using the above link you just download the package set for a given version and install the set as one:

  sudo dpkg -i *.deb

But certainly don't do that if it's a production machine and you have an acceptable workaround.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1969815

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel LaSalle (daniellasalle) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Daniel LaSalle (daniellasalle) wrote : CRDA.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : Dependencies.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : Lspci.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : Lspci-vt.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : Lsusb.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : Lsusb-t.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : Lsusb-v.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : PaInfo.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : ProcEnviron.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : ProcModules.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : PulseList.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : UdevDb.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : WifiSyslog.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote : acpidump.txt

apport information

Revision history for this message
Daniel LaSalle (daniellasalle) wrote :

FYI:

$ apport-collect 1969815
dpkg-query: no packages found matching linux
$

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I'm suddenly reminded of bug 1971146. Please try adding kernel parameter:

  intel_iommu=off

to /etc/default/grub (in GRUB_CMDLINE_LINUX_DEFAULT) and then run:

  sudo update-grub

and reboot.

Revision history for this message
Daniel LaSalle (daniellasalle) wrote :

Thanks for that, will try it. However my box is AMD therefore 1. no onboard video and 2. no Intel.

Back to your request of installing an older kernel: I might have found a maintenance window.

Given that I did, would you like for me to try any one? I understand you mentioned to install any of them but if we would have *1* shot, would we have any preference in terms of tag? Of course, I would need to stick to v5.something and possibly v5.1x.?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If you can only afford to try one kernel then please make it drm-tip:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2022-05-08/amd64/

That will tell us if the bug already has a fix upstream. Although you won't get automatic updates for that kernel so may want to uninstall the packages after you've finished testing them.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.