| Priority | medium |
|---|---|
| Bug ID | 76490 |
| Assignee | dri-devel@lists.freedesktop.org |
| Summary | No output after radeon module is loaded (R9 270X) |
| Severity | normal |
| Classification | Unclassified |
| OS | All |
| Reporter | mail@geleia.net |
| Hardware | Other |
| Status | NEW |
| Version | unspecified |
| Component | DRM/Radeon |
| Product | DRI |
Created attachment 96217 [details]
kernel log
The screen goes black after the radeon module is loaded. The only way I can get
any output is to blacklist the radeon module, load it via modprobe and then
change the resolution with xrandr from another computer via ssh.
I seem to get some sort of lockup if I don't blacklist the module, because then
I get a black screen at startup and I cannot even ssh into the machine. I tried
to enable netconsole from the kernel command line but I can't get it to work
(do I have to compile it statically?).
I tried this with 3.14-rc6. For reference, I'm including the log output I get
after I load the radeon module.
This card is an MSI R9 270X Gaming 4G.
When it hangs (which always happen if I don't have X already started), I sometimes get a bunch vertical white and black stripes. dmesg doesn't show anything interesting, just [ 278.575937] fbcon: radeondrmfb (fb0) is primary device [ 278.590490] Console: switching to colour frame buffer device 240x67 [ 278.602467] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device [ 278.602531] radeon 0000:01:00.0: registered panic notifier [ 278.606539] [drm] Initialized radeon 2.37.0 20080528 for 0000:01:00.0 on minor 0
Does booting with radeon.runpm=0 on the kernel command line in grub also help?
Have you installed the latest mc ucode for pitcarin? http://people.freedesktop.org/~agd5f/radeon_ucode/PITCAIRN_mc2.bin make sure that is installed and available in your initrd if you are using one.
I installed it now, but still no luck. glopes ~ $ ls -l /lib/firmware/radeon/PITCAIRN_mc* -rw-r--r-- 1 root root 31100 Mai 13 18:58 /lib/firmware/radeon/PITCAIRN_mc2.bin -rw-r--r-- 1 root root 31076 Mar 23 02:02 /lib/firmware/radeon/PITCAIRN_mc.bin When I run with radeon.dpm=0, it seems to load the correct file: [ 0.630585] [drm] radeon: 4096M of VRAM memory ready [ 0.630586] [drm] radeon: 1024M of GTT memory ready. [ 0.630593] [drm] Loading PITCAIRN Microcode [ 0.630632] [drm] radeon/PITCAIRN_mc2.bin: 31100 bytes [ 0.630644] [drm] Internal thermal controller with fan control [ 0.630673] [drm] radeon: power management initialized I'm attaching the full log as well.
Created attachment 98989 [details]
kernel log with dpm=0 on 3.15-rc5
Oh and I made sure the initramfs had the module and the firmware. For reference the xz cpio image is here: https://s3-eu-west-1.amazonaws.com/artefacto-test/initramfs-linux-mainline.img
Created attachment 98997 [details] [review] disable some dpm features Does this patch help? If so, can you narrow down which setting(s) are the problematic one(s)?
I tried sprinkling si_dpm_ini() and si_dpm_enabled with printk and msleep statements, but while I can tell they're being executed (it takes much longer for the screen to become black due to the sleeps), I cannot see any log messages. The last lines I see are: [drm] radeon kernel modesetting enabled. fb: switching to radeondrmfb from EFI VGA
Created attachment 99000 [details]
kernel log dpm on plus disabling patch
By statically compiling netconsole and the nic driver and having radeon as
module, I was able to get a kernel log. This is full log, I get nothing after
this.
| What | Removed | Added |
|---|---|---|
| Summary | No output after radeon module is loaded (R9 270X) | Hang during boot when DPM is on (R9 270X) |
Still present in 3.16-rc2: https://gist.github.com/cataphract/29a7c132ef4c240e9330 (last message varies; in my other try it got a little further but the log started later as well)
| What | Removed | Added |
|---|---|---|
| CC | dex+fdobugzilla@dragonslave.de |
*** Bug 79773 has been marked as a duplicate of this bug. ***
Created attachment 101819 [details] [review] disable cg Does this patch help? You might also try in conjuction with attachment 98997 [details] [review].
Still nothing, both with 101819 and 101819 + 98997. Same behavior.
Can you try my drm-next-3.17-wip branch: http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.17-wip along with the updated ucode here: http://people.freedesktop.org/~agd5f/radeon_ucode/ucode.tar.gz
Nope. Only difference is took some extra 60 seconds when it couldn't find radeon/TAHITI_uvd.bin (which was not in your tarball). After I copied it from my distro's linux-firmware, I had quicker hangs. console output for both situations: https://gist.github.com/cataphract/4dac266bba4f9be44ea7
I can confirm: drm-next-3.17-wip + new ucode doesn't make any difference. Testscenario: * Built/Installed new kernel, copied new ucode into /lib/firmware * Built new initrd * reboot with "nomodeset" and gfxpayload=text into multi user runlevel * modprobe radeon drm=1 modeset=1 Monitor went black (but shows connected DVI), system is unresponsive.