linux-kernel - Re: Kernel almost hangs when CONFIG_DRM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1314435638.2321.12.camel@thor.local>
Date:	Sat, 27 Aug 2011 11:00:38 +0200
From:	Michel Dänzer <michel@...nzer.net>
To:	Pavel Ivanov <paivanof@...il.com>
Cc:	dri-devel@...ts.freedesktop.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Kernel almost hangs when CONFIG_DRM_RADEON=y

On Sam, 2011-08-27 at 00:20 -0400, Pavel Ivanov wrote: 
> 
> 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

With CONFIG_DRM_RADEON=y, the microcode is needed before it can be
loaded from userspace, so it needs to be built into the kernel as well.


-- 
Earthling Michel Dänzer           |                   http://www.amd.com
Libre software enthusiast         |          Debian, X and DRI developer
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/