Bug 77471

Summary: VESA VGA to radeondri handoff results in boot hang
Product: Drivers Reporter: joshua.r.marshall.1991
Component: Video(DRI - non Intel)Assignee: drivers_video-dri
Status: RESOLVED INVALID    
Severity: normal CC: alexdeucher
Priority: P1    
Hardware: x86-64   
OS: Linux   
Kernel Version: 3.15-rc8 Subsystem:
Regression: No Bisected commit-id:
Attachments: The kernel config I'm using
New kernel config that does boot
dmesg output

Description joshua.r.marshall.1991 2014-06-07 22:19:26 UTC
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.
Comment 1 joshua.r.marshall.1991 2014-06-07 22:33:27 UTC
My distro kernel version is at 3.14.5
Comment 2 Alex Deucher 2014-06-10 14:56:17 UTC
Can you attach the dmesg output from a sucessful load the driver?  What GPU is this?
Comment 3 joshua.r.marshall.1991 2014-06-10 19:40:15 UTC
This is the R7 GPU on the A10-7850K
Comment 4 joshua.r.marshall.1991 2014-06-10 19:43:05 UTC
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.
Comment 5 joshua.r.marshall.1991 2014-06-10 19:44:31 UTC
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.
Comment 6 Alex Deucher 2014-06-10 19:47:39 UTC
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.
Comment 7 joshua.r.marshall.1991 2014-06-10 19:52:30 UTC
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.
Comment 8 Alex Deucher 2014-06-10 19:59:10 UTC
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.
Comment 9 joshua.r.marshall.1991 2014-06-10 20:04:06 UTC
That looks to be it.