linux-kernel - Re: [4.5-rc regression] drm radeon Tahiti

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] [day] [month] [year] [list]

Message-ID: <56C5F9B2.7060508@gmail.com>
Date:	Thu, 18 Feb 2016 12:04:50 -0500
From:	Woody Suwalski <terraluna977@...il.com>
To:	"Deucher, Alexander" <Alexander.Deucher@....com>,
	LKML <linux-kernel@...r.kernel.org>
Cc:	"Koenig, Christian" <Christian.Koenig@....com>
Subject: Re: [4.5-rc regression] drm radeon Tahiti_vce fails to load

Deucher, Alexander wrote:
>> -----Original Message-----
>> From: Woody Suwalski [mailto:terraluna977@...il.com]
>> Sent: Thursday, February 18, 2016 7:53 AM
>> To: LKML
>> Cc: Deucher, Alexander; Koenig, Christian
>> Subject: [4.5-rc regression] drm radeon Tahiti_vce fails to load
>>
>> Alex, the 4.5-rc 32-bit kernels seem to have a problem initializing VCE.
>> The drm.debug boot option does not show more info as to what the problem
>> is.
>> On 4.4 (tested with 4.4.1 and 4.4.2) kernels it is loading OK.
>>
>> I have confirmed the regression on 4.5-rc2 and 4.5-rc4 kernels.
> [    1.051686] radeon 0000:01:00.0: Requesting firmware: radeon/TAHITI_vce.bin
> [    1.051856] radeon 0000:01:00.0: Direct firmware load for radeon/TAHITI_vce.bin failed with error -2
> [    1.051858] radeon 0000:01:00.0: radeon_vce: Can't load firmware "radeon/TAHITI_vce.bin"
>
>
> You did not include the vce firmware image in your kernel image.  Please make sure to include the firmware image in your kernel image if you are building it in or if you are using an initrd, please make sure the firmware image is in your initrd.
>
> Alex
>
You are right - somehow the TAHITI_vce.bin got omitted from the kernel's 
.config.
The Radeon included firmware line is now close to 3400 long, and 
growing... Will there be a better way to manage these firmware blobs (a 
rhetorical question)...

Thanks, Woody