FS#41349 - [linux] 3.15.x kernel upgrade breaking xorg/xf86-video-ati

Attached to Project: Arch Linux
Opened by _ (shaffl) - Saturday, 26 July 2014, 13:25 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 27 August 2016, 12:10 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Hi,
upgrading to 3.15.5-2-ARCH kernel (x86_64 arch), video has stopped working properly on my laptop. I have AMD dual graphics:

lspci | grep VGA
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G]
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] (rev ff)

I'm using the latest version of xorg and xf86-video-ati.
Xorg exits before loading – any – desktop environment. I've never had problems before. If I retry to startx another time, it succesfully loads the environment, but the latter continuously freezes (every about 10 seconds). If I switch to a tty while the gui is running, I don't get these freezes (they affects gui only). The latest version of the lts kernel doesn't show such flaws. I've attached Xorg.0.log and dmesg output (catched immediately after xorg crash). Looking at dmesg, I've noticed a block of messages that keeps repeating, the one starting with “gaarb: device added”, which probably deals with the repeating gui locks I've mentioned. Also, I know that 3.14.6-1-ARCH neither shows such problems. Thanks for the help, I hope there's nothing wrong with the bug report.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 27 August 2016, 12:10 GMT
Reason for closing:  No response
Comment by _ (shaffl) - Saturday, 26 July 2014, 13:27 GMT
dmesg + Xorg.0.log
   Xorg.0.log (6.5 KiB)
   dmesg.log (128.6 KiB)
Comment by patrick (potomac) - Saturday, 26 July 2014, 16:30 GMT
you can try to disable dpm, to see if it's better, there is a kernel option :

"radeon.dpm=0" ( add it in the configuration of your bootloader, like grub or syslinux )

Comment by _ (shaffl) - Saturday, 26 July 2014, 17:13 GMT
@patrick (potomac): thanks for the reply. I tried with that kernel parameter, but it hasn't solved.
Comment by Sandeep (sandy8925) - Tuesday, 05 August 2014, 07:45 GMT
Can you please try radeon.runpm=0 ? This will disable runtime power management(automatically switching off dGPU) without disabling power management(dpm).

I had lockups too, and runtime power management was the cause. You may be facing the same problem. In my case, dmesg had error messages with the words "stuck executing xxxx", and some messages about GPU reset.
Comment by _ (shaffl) - Tuesday, 05 August 2014, 10:17 GMT
@Sandeep (sandy8925): your solution worked, thanks. Just one question: how does that parameter affect the GPU?
Comment by Tobias Powalowski (tpowa) - Wednesday, 13 August 2014, 07:42 GMT
Status on 3.16?
Comment by _ (shaffl) - Monday, 18 August 2014, 08:24 GMT
Same with 3.16
Comment by Andreas Radke (AndyRTR) - Thursday, 28 July 2016, 12:42 GMT
Is this still an issue?

Loading...