Hi, I observe very strange behavior dependent on value of CONFIG_DRM_RADEON parameter. When it's set to m everything works very good, no problem. When I set it to y I see kernel hang during boot. Or I should better say it "almost hangs" because during last boot attempt I accidentally waited a little bit longer and saw that after more than a minute waiting system continued to boot. Dmesg after "hang" shows these messages:
[ 8.542639] [drm] Loading CEDAR Microcode [ 69.161605] r600_cp: Failed to load firmware "radeon/CEDAR_pfp.bin" [ 69.161670] [drm:evergreen_startup] *ERROR* Failed to load firmware! While during normal boot [ 9.898870] [drm] Loading CEDAR Microcode [ 9.908425] radeon 0000:05:00.0: WB enabled Is this a bug? I'm seeing this on 3.1-rc3. Full dmesgs for both boots are attached. Pavel -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesg.module Type: application/octet-stream Size: 81377 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20110827/4c4e0b9b/attachment-0002.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesg.built-in Type: application/octet-stream Size: 81502 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20110827/4c4e0b9b/attachment-0003.obj>
