FS#48578 - [linux] system freezes on loading radeon module

Attached to Project: Arch Linux
Opened by Raphael Dümig (einbisschen) - Monday, 14 March 2016, 11:34 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 28 March 2016, 12:35 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
system freezes when radeon module is loaded:
1. screen goes black
2. I can hear the harddrive spin down
3. no reaction on key presses like Ctrl+Alt+Del

Additional info:
kernel log obtained from netconsole is attached

$ lspci
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] (rev 81)

* package version(s)
linux 4.4.5-1

Steps to reproduce:
1. start system with radeon module blacklisted
2. stop graphical login manager
3. log into the console and manually load radeon module (# modprobe radeon)
   module_load_log.txt (5.7 KiB)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Monday, 28 March 2016, 12:35 GMT
Reason for closing:  Upstream
Comment by Raphael Dümig (einbisschen) - Monday, 14 March 2016, 11:44 GMT
I forgot to mention that I tested the fglrx driver and it worked.
Comment by Andreas Radke (AndyRTR) - Monday, 14 March 2016, 14:42 GMT
There's nothing wrong in the module loading logfile. Try to get an error logging from a remote system.
Comment by Raphael Dümig (einbisschen) - Monday, 14 March 2016, 14:56 GMT
This is the complete kernel log from the moment on, when I load the radeon module. I had to capture this from a remote system.
Kernel loglevel is set to debug.
Sorry, but I do not know how to provide more...
Comment by Andreas Radke (AndyRTR) - Monday, 14 March 2016, 15:16 GMT
Start your system to console mode. Login from a remote machine via ssh and watch dmesg/journalctl while you startx or load the failing module.
Comment by Raphael Dümig (einbisschen) - Monday, 14 March 2016, 15:43 GMT
This is the "journalctl -kf" output, again logged from a remote system using ssh this time.
It has been started some moments before loading the module radeon.
After the last log line the pipe breaks.
X is not running.

It gives the same output as netconsole, but the connection breaks earlier.

Is it neccessary to debug the kernel module with gdb, to get more information?
   journalctl.txt (6.4 KiB)
Comment by Andreas Radke (AndyRTR) - Monday, 14 March 2016, 16:03 GMT
This doesn't help. Maybe something is in your Xorg log.

What update has introduced this bug? A kernel od Xorg update? You may need to git bisect the breaking commit.
Comment by Raphael Dümig (einbisschen) - Monday, 14 March 2016, 16:18 GMT
I changed the graphics hardware of my system.
Before that I was working on a Radeon HD 2350 with the same driver without any problems.
Now I installed the R7 370.

I can only offer Xorg logs with VESA or fglrx as graphics driver, as the kernel seems to attempt loading the radeon module before starting X.
Comment by Raphael Dümig (einbisschen) - Monday, 14 March 2016, 16:23 GMT
output of lspci -vvs 01:00.0
   lspci.txt (3.4 KiB)
Comment by Andreas Radke (AndyRTR) - Monday, 14 March 2016, 16:30 GMT
Do you have the required linux-firmware pkg installed? Google says the gfx card should work well.
Comment by Raphael Dümig (einbisschen) - Monday, 14 March 2016, 16:36 GMT
linux-firmware 20160113.40e9ae8-1 is installed

the attached Xorg.0.log is the X server running with VESA
   Xorg.0.log (78.3 KiB)
Comment by Raphael Dümig (einbisschen) - Monday, 14 March 2016, 16:37 GMT
the attached Xorg.1.log is the X server running with fglrx
   Xorg.1.log (43.1 KiB)
Comment by Raphael Dümig (einbisschen) - Tuesday, 15 March 2016, 20:31 GMT
I tried compiling the vanilla sources of the 4.5 kernel.
The system also freezes with that kernel when the radeon module is loaded.
Comment by Andreas Radke (AndyRTR) - Tuesday, 15 March 2016, 21:00 GMT
This could be almost everything but sounds more like a hardware problem with you graphics card.
Comment by Raphael Dümig (einbisschen) - Wednesday, 16 March 2016, 07:05 GMT
In case of a hardware problem, would vesa and fglrx really work?
Comment by Raphael Dümig (einbisschen) - Saturday, 26 March 2016, 15:13 GMT
- does not work with Ubuntu 15.10
- the problem occurs as well with the graphics card plugged in other computers with different hardware and linux system
- works on windows
Comment by Raphael Dümig (einbisschen) - Saturday, 26 March 2016, 17:06 GMT
I reported this bug on the kernel bug tracker: https://bugzilla.kernel.org/show_bug.cgi?id=115291
Comment by Andreas Radke (AndyRTR) - Monday, 28 March 2016, 12:35 GMT
CC'ed to the upstream bug.

Loading...