Graphic driver (radeon) screen problem in kernels released after 2019-06-09

[Radek]

I've got a problem with some kernel modules (probably radeon) which cause screen problems. It occurs only on internal laptop screen.
I found that problem is present in all kernels released after 2019-06-09 18:25. Last kernel which works corectly is v4.19.49 2019-06-09 10:04. v5.2-rc4 2019-06-09 18:25 has this bug and also v4.19.50 2019-06-11 13:06. So I think there are some changes in all kernel packages between hour 10:04 and 18:25 that day (2019-06-09) casue future problems.

This may be problem with radeon modules cause screen goes strange when console shows "fb: switching to radeondrmfb from VESA VGA" (I remove "quiet splash" from GRUB menu).

In this video I show described problem -> https://player.vimeo.com/video/382017028

I've tested those kernels:

*Works correctly:
v4.19/ 2018-10-22 23:50
v4.19.49/ 2019-06-09 10:04
v5.0.1/ 2019-03-10 08:30
v5.0.7/ 2019-04-05 22:40
v5.0.21/ 2019-06-04 08:28
v5.1.6/ 2019-05-31 15:32
v5.1.8/ 2019-06-09 09:29

*Not working correctly
v4.14.163/ 2020-01-09 12:29
v4.19.50/ 2019-06-11 13:06
v4.19.94/ 2020-01-09 12:42
v5.0.0-37/ 2019-11-14 12:06
v5.1.9/ 2019-06-11 12:29
v5.1.10/ 2019-06-15 11:30
v5.1.11/ 2019-06-17 19:36
v5.2-rc4/ 2019-06-09 18:25
v5.2-rc5/ 2019-06-16 20:26

Quick Hardware info:
* Compal FL90
* CPU: Intel Core 2 Duo T7500
* GPU: AMD Rv620
* System Description: Ubuntu 18.04.3 LTS x64 (xubuntu)
* Kernel (works OK): 5.1.8-050108-generic #201906090832 SMP Sun Jun 9 08:35:40 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: master 1305 F.... pulseaudio
 /dev/snd/controlC1: master 1305 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
MachineType: - N/A
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=e286c111-0a34-4f09-9d80-ebb947347f62 ro
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-37-generic N/A
 linux-backports-modules-5.0.0-37-generic N/A
 linux-firmware 1.173.14
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/18/2008
dmi.bios.vendor: COMPAL
dmi.bios.version: 1.18
dmi.board.name: IFL90
dmi.board.vendor: -
dmi.board.version: IFT00
dmi.chassis.asset.tag: -
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnCOMPAL:bvr1.18:bd06/18/2008:svn-:pnN/A:pvrN/A:rvn-:rnIFL90:rvrIFT00:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.family: Compal
dmi.product.name: N/A
dmi.product.sku: Compal
dmi.product.version: N/A
dmi.sys.vendor: -

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1859352/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Radek (radzixxx)]

add package |linux" because problem is in kernel modules (i think)

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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 1859352

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.

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Radek (radzixxx)]

apport information

[Kai-Heng Feng (kaihengfeng)]

Would it be possible for you to do a kernel bisection?

First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the working version you found)
$ git bisect bad $(the non-working version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If it still have the same issue,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the offending commit.

[Radek (radzixxx)]

From "-rc":
last works: v5.1-rc7
first not works: v5.2-rc1.

From non "-rc":
last works: v5.1.8
first not works: v5.1.9

I tried do bisection from your instruction, but I did it for a first time and got too many errors while $ make -j`nproc` deb-pkg so I gave up. Thank you for your help.

I'll stay with 5.1.8.

[Kai-Heng Feng (kaihengfeng)]

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

If this doesn't work then let's start bisection.