[drm] [radeon] [3.1.4] slub memory corruption in drm_vblank_cleanup

batouzo batouzo at gmx.com
Wed Dec 14 09:27:11 PST 2011


On 12/14/2011 06:21 PM, Alex Deucher wrote:
> On Wed, Dec 14, 2011 at 12:12 PM, batouzo <batouzo at gmx.com> wrote:
>> On 12/14/2011 05:40 PM, Alex Deucher wrote:
>>> On Wed, Dec 14, 2011 at 11:32 AM, batouzo <batouzo at gmx.com> wrote:
>>>> On 12/14/2011 03:10 PM, Alex Deucher wrote:
>>>>
>>>>>> Though, the 60 second delay may influence the rarity of hitting BUG (it
>>>>>> was the case with netconsole's 60sec wait).
>>>>>> Should I just remove loading of this firmware?
>>>>>>
>>>>> Make sure the ucode is available in your initrd or kernel image or
>>>>> filesystem depending on how you are loading the driver.  The driver
>>>>> has much more limited functionality without the ucode (no acceleration
>>>>> support, no interrupt support).  You may not hit the bug at all due to
>>>>> the reduced functionality.
>>>>
>>>> Actually, where is that file? Can't find CEDAR_pfp.bin or even any
>>>> "*CEDAR*" in entire filesystem where I build the kernel.
>>>>
>>>> Also I tried CONFIG_FIRMWARE_IN_KERNEL=y
>>>> but it didn't helped, hm.
>>>>
>>>
>>> You need to grab them from here:
>>> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git
>>
>> Ok I see.
>>
>> Is there a pubkey signed version of that available, or what is the
>> safe-download procedure (as with kernl.org .tar's + .sign for kernels)?
>>
> 
> You can download/compare with my tree:
> http://people.freedesktop.org/~agd5f/radeon_ucode/
> 
> Alex
> 
> 
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel

Thanks.

Is this firmware a closed source binary blob?
Or open source, only uploaded to the card on init?

Who develops it / where to get the source code, and how to build that
file from sources?

This means that entire firmeware of GFX card is flashed on bootup?
Btw this is a form of virus protection you could say (or anyway such
firmware is volatile and lost on reboot?)



More information about the dri-devel mailing list