radeon driver hangs : nothing else that static effect on display

[magowiz]

Hi,
since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard due to drop support of fglrx driver (that was working) and due to radeon opensource driver not working with my VGA.

Mine video card:
$ lspci -nn | grep VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]

$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04

I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0c: magowiz 4930 F...m pulseaudio
 /dev/snd/pcmC0D0p: magowiz 4930 F...m pulseaudio
 /dev/snd/controlC0: magowiz 4930 F.... pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=472405e9-ecbe-44ee-9931-9eedcc0a759a
InstallationDate: Installed on 2012-01-03 (1615 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=acd61f09-2fc9-4a54-bf0b-23f0a297d2e4 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
RfKill:

Tags: xenial
Uname: Linux 4.4.0-22-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-04-26 (40 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
_MarkForUpload: True
dmi.bios.date: 12/09/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1003
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F1A55-M LE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd12/09/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A55-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Does this issue go away if you boot the prior kernel version?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety

[magowiz (magowiz)]

Hi Joseph
with previous kernel (4.4.0-21-generic ) I have the same issue.
So I tried like you suggested to use a mainline build, using these 3 deb packages from link you posted :
linux-headers-4.6.0-040600_4.6.0-040600.201605151930_all.deb
linux-headers-4.6.0-040600-generic_4.6.0-040600.201605151930_amd64.deb
linux-image-4.6.0-040600-generic_4.6.0-040600.201605151930_amd64.deb

Also with 4.6.x mainline kernel I can confirm the same behavior as reported initially.

[magowiz (magowiz)]

In the meanwhile this bug gets fixed, is there a way I can use graphical environment without using radeon driver? A sort of failsafe/default Xorg graphical mode, otherwise a way to install fglrx which it worked until 16.04 ?

Please provide me this information if it is possible, also a link or two are welcome, keep in mind that since 16.04, on that pc, I can only use text mode (console) interface.

Thank you

[magowiz (magowiz)]

Today I noticed that if I restart X environment using : sudo service lightdm restart, the static effect goes away and I can log in and use graphical environment.

Obviously I have to perform lightdm restart on each boot, because on boot, every time, I get the issue. I don't know if this information is useful for bug report, please tell me if you need further information about that, like logs or something else.

[penalvch (penalvch)]

magowiz, please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1581799

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[magowiz (magowiz)]

apport information

[magowiz (magowiz)]

apport information

[magowiz (magowiz)]

apport information

[magowiz (magowiz)]

apport information

[magowiz (magowiz)]

apport information

[magowiz (magowiz)]

apport information

[magowiz (magowiz)]

apport information

[magowiz (magowiz)]

apport information

[magowiz (magowiz)]

apport information

[magowiz (magowiz)]

apport information

[magowiz (magowiz)]

apport information

[magowiz (magowiz)]

apport information

[magowiz (magowiz)]

apport information

[penalvch (penalvch)]

magowiz, to clarify your Bug Description, were you able to use the radeon driver (not fglrx) in 15.10 without this issue?

[magowiz (magowiz)]

I don't know : I clearly remember that from a version (or more) before I wasn't able to launch graphical environment without fglrx driver, so since then I always used fglrx, it was another issue I think, since the screen remained black and not with static effect, that I see for the first time into 16.04.
Anyway, do you think that booting with Ubuntu 15.10 installation media can provide you the information you are asking me? If so, let me know and I'll report you back.

[penalvch (penalvch)]

magowiz, it wouldn't hurt to have a test of 15.10 with the radeon driver to see if this is a regression.

[magowiz (magowiz)]

Hi Christopher,
I tried like I said with the ubuntu 15.10 amd64 iso , the results of the tests are almost the same of installed 16.04 :

while installed 16.04 goes static once , then after some seconds it blanks the screen and returns the static effect (then no moves from then)
the live 15.10 goes static once, then after a while goes blank and then static twice, after that it disables the screen (my monitor says "no signal") for 2-3 seconds, and finally it goes static for the third time and no moves since then.

I don't think it's a regression but something like : it has the defect in 15.10, it still has the defect on 16.04.

[magowiz (magowiz)]

Hi Christopher,
thank you for the detailed information and support, I dind't think it could be a bios issue.
Like you said I updated my MB BIOS firmware to 1069 (last available for my MB) , the situation changed a bit : instead of static effect, the screen remains blank.

I really don't know if you can consider this the same problem or another one, anyway I'll provide you the information you asked and , for now, not mark this bug as confirmed since it could be also another issue, different from initial one, I'll wait for your approval to mark this as confirmed.

Here it is the commands output :
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
1609
01/07/2014

At your disposal if you need further information.

[penalvch (penalvch)]

magowiz, could you please test the latest mainline kernel (4.7-rc2) and advise to the results?

[magowiz (magowiz)]

Hi Christopher,
I tried latest mainline kernel : the static issue is back.

I installed theese packages :
linux-headers-4.7.0-040700rc2_4.7.0-040700rc2.201606100641_all.deb
linux-headers-4.7.0-040700rc2-generic_4.7.0-040700rc2.201606100641_amd64.deb
linux-image-4.7.0-040700rc2-generic_4.7.0-040700rc2.201606100641_amd64.deb

and reboot , the uname -a says :
Linux liano 4.7.0-040700rc2-generic #201606100641 SMP Fri Jun 10 10:44:14 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Tell me if you need further information or tests and I'll report you back.

[penalvch (penalvch)]

magowiz, could you please provide the missing information from https://wiki.ubuntu.com/X/Troubleshooting/Freeze ?

[magowiz (magowiz)]

Christopher, do you mean /var/log/Xorg.0.log since dmesg.log was already attached or is it better to provide a new dmesg.log ?
And then the regdumps . Am I right?

[penalvch (penalvch)]

magowiz, while the missing information wouldn't include dmesg.log since it's already attached, it wouldn't hurt to provide the dmesg log that is at the same time stamp as the other logs.

[magowiz (magowiz)]

Christopher,
I attached the files needed in case of freeze, like you said, I hope I didn't forget anything, in that case and if you need further logs or information, please let me know and I will provide it.

[penalvch (penalvch)]

magowiz, could you please test the latest http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/ following https://wiki.ubuntu.com/Kernel/MainlineBuilds and advise to the results?

[magowiz (magowiz)]

Christopher, I tried drm-next latest kernel but static effect issue still occurs.
I downloaded from this url : http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/current/
and installed these packages :

linux-headers-4.7.0-996_4.7.0-996.201606092201_all.deb
linux-headers-4.7.0-996-generic_4.7.0-996.201606092201_amd64.deb
linux-image-4.7.0-996-generic_4.7.0-996.201606092201_amd64.deb

$uname -a
Linux liano 4.7.0-996-generic #201606092201 SMP Fri Jun 10 02:03:53 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[magowiz (magowiz)]

So... no way I can solve? Has this bug been reported to upstream yet?

[penalvch (penalvch)]

magowiz, apologies for this getting away from me.

In order to keep this relevant to upstream, and in turn report upstream, one would need to continue to test the latest mainline kernel (now 4.8-rc3) as they are released.

Could you please advise to this?

[magowiz (magowiz)]

Hi Christopher,
I tried latest rc from 4.8 mainline series : 4.8-rc5 ,
using these packages :
linux-headers-4.8.0-040800rc5_4.8.0-040800rc5.201609041832_all.deb
linux-headers-4.8.0-040800rc5-generic_4.8.0-040800rc5.201609041832_amd64.deb
linux-image-4.8.0-040800rc5-generic_4.8.0-040800rc5.201609041832_amd64.deb
from this url :
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc5/

uname -a says I'm running that kernel :
Linux liano 4.8.0-040800rc5-generic #201609041832 SMP Sun Sep 4 22:34:01 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

But I still get the same issue I reported initially.

Can we report it upstream ?
Any chances we get back proprietary fglrx driver support on next Ubuntu release ( 16.10 ) ? With that driver at least mine APU was working for graphical purposes.

Best regards,
magowiz

[penalvch (penalvch)]

magowiz, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Alex Deucher, and Christian König CC dri-devel)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your help.

[magowiz (magowiz)]

Hi Christopher,
I prepared the text I should write reporting upstream and following the instruction "kernel.org format information" but I didn't understand how and where I should send this message :

The document you posted points to : https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Driver/Radeon for radeon issues

The preceding mail section points to http://vger.kernel.org/vger-lists.html but I don't see any dri-devel or any name of person you mention .

I'm confused, please tell me what I have to do.

If I should write an email please provide me email addresses or a link where they are listed , otherwise If I should compile a bug report in https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Driver/Radeon just tell me the Assignee and cc persons.

[magowiz (magowiz)]

bump

[magowiz (magowiz)]

I'm still facing the same issue in ubuntu 17.10, tried mainline kernels.
Is there a way to install fglrx driver ? That is the only one it worked in these years .
Otherwise please help me to report this bug upstream, since it is present also on mainline kernels (standard and drm-next ones) providing me the right references.
As you can imagine, mine interest is to solve the problem, it doesn't matter if with driver A, B or C, the fact is that since reported, I wasn't able to have display environment working. Obviously if mine bug report is properly done upstream, with as much information I can provide, and give possibility to other linux users to have it resolved, it is better.

[Kai-Heng Feng (kaihengfeng)]

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/radeon

[magowiz (magowiz)]

Ok, thank you for the information, do I need to report here upstream bug reference after I created bug report?

[Kai-Heng Feng (kaihengfeng)]

> On 4 Jan 2018, at 4:08 AM, magowiz <email address hidden> wrote:
>
> Ok, thank you for the information, do I need to report here upstream bug
> reference after I created bug report?

Yes, that would be really helpful, thanks!

>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1581799
>
> Title:
> radeon driver hangs : nothing else that static effect on display
>
> Status in linux package in Ubuntu:
> Triaged
>
> Bug description:
> Hi,
> since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard due to drop support of fglrx driver (that was working) and due to radeon opensource driver not working with my VGA.
>
> Mine video card:
> $ lspci -nn | grep VGA
> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]
>
> $ lsb_release -rd
> Description: Ubuntu 16.04 LTS
> Release: 16.04
>
> I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .
> ---
> ApportVersion: 2.20.1-0ubuntu2.1
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/pcmC0D0c: magowiz 4930 F...m pulseaudio
> /dev/snd/pcmC0D0p: magowiz 4930 F...m pulseaudio
> /dev/snd/controlC0: magowiz 4930 F.... pulseaudio
> DistroRelease: Ubuntu 16.04
> HibernationDevice: RESUME=UUID=472405e9-ecbe-44ee-9931-9eedcc0a759a
> InstallationDate: Installed on 2012-01-03 (1615 days ago)
> InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
> IwConfig:
> eth0 no wireless extensions.
>
> lo no wireless extensions.
> MachineType: System manufacturer System Product Name
> Package: linux (not installed)
> ProcFB: 0 radeondrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=acd61f09-2fc9-4a54-bf0b-23f0a297d2e4 ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
> RelatedPackageVersions:
> linux-restricted-modules-4.4.0-22-generic N/A
> linux-backports-modules-4.4.0-22-generic N/A
> linux-firmware 1.157
> RfKill:
>
> Tags: xenial
> Uname: Linux 4.4.0-22-generic x86_64
> UpgradeStatus: Upgraded to xenial on 2016-04-26 (40 days ago)
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
> _MarkForUpload: True
> dmi.bios.date: 12/09/2011
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 1003
> dmi.board.asset.tag: To be filled by O.E.M.
> dmi.board.name: F1A55-M LE
> dmi.board.vendor: ASUSTeK COMPUTER INC.
> dmi.board.version: Rev X.0x
> dmi.chassis.asset.tag: Asset-1234567890
> dmi.chassis.type: 3
> dmi.chassis.vendor: Chassis Manufacture
> dmi.chassis.version: Chassis Version
> dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd12/09/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A55-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
> dmi.product.name: System Product Name
> dmi.product.version: System Version
> dmi.sys.vendor: System manufacturer
>
> To manage notifications about this bug go to:
> https://bugs...

[magowiz (magowiz)]

upstream bug : https://bugs.freedesktop.org/show_bug.cgi?id=104497