Created attachment 138461 [details] The kernel config I'm using Suspecting a kernel memory leak involving radeon stuffs, I pulled down the kernel source, used "make localyesconfig" to automatically configure the kernel from my distro's configuration, did the typical procedure to make the kernel boot as per archlinux instructions and past experiance. During boot of the new kernel, a line saying the handoff from VESA VGA was handing off to radeondri for the framebuffer switchoff prints, CPU goes to 100% (from what I can tell -- fan speeds up and CPU kicks off heat) and does not progress. Even given a half hour, this doesn't change. I'm not sure how to proceed other than filing this report.
My distro kernel version is at 3.14.5
Can you attach the dmesg output from a sucessful load the driver? What GPU is this?
This is the R7 GPU on the A10-7850K
Created attachment 138971 [details] New kernel config that does boot I used localmodconfig for then, then added debug info -- my guess is something related to having the module built in vs. loaded. I ran into similar issues with my intel graphics a while back.
Created attachment 138981 [details] dmesg output I found where my kernel is leaking memory (USB audio related) but this hand off should still not have been an issue.
Did you build the necessary firmware into your kernel image when you built the driver into the kernel? I don't think this has anything to do with the handoff.
I'm not aware of anything involving firmware for building the modules separately or part of the main kernel. I follow the same build procedure for both.
You need to build the firmware into the kernel image if you build the driver into the kernel otherwise, the driver will not be able to fetch the firmware. What you may be seeing is the kernel firmware loading waiting for firmware to become available, but it never does since it's not actually in the kernel binary.
That looks to be it.