From: batouzo <batouzo@gmx.com>
To: dri-devel@lists.freedesktop.org
Subject: Re: [drm] [radeon] [3.1.4] slub memory corruption in drm_vblank_cleanup
Date: Wed, 14 Dec 2011 17:32:01 +0100 [thread overview]
Message-ID: <jcaj21$iej$1@dough.gmane.org> (raw)
In-Reply-To: <CADnq5_PFWTt4CJHo1vhGvv41jVAN5i8eaHEUfUAWMZA7kWWyew@mail.gmail.com>
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.
>> [ 62.347154] r600_cp: Failed to load firmware "radeon/CEDAR_pfp.bin"
>> [ 62.347189] [drm:evergreen_startup] *ERROR* Failed to load firmware!
>> [ 62.347222] radeon 0000:01:00.0: disabling GPU acceleration
next prev parent reply other threads:[~2011-12-14 16:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 21:26 [drm] [radeon] [3.1.4] slub memory corruption in drm_vblank_cleanup batouzo
2011-12-13 23:31 ` Jerome Glisse
2011-12-13 23:33 ` batouzo
2011-12-13 23:46 ` Jerome Glisse
2011-12-13 23:47 ` Jerome Glisse
2011-12-14 7:00 ` batouzo
2011-12-14 14:10 ` Alex Deucher
2011-12-14 16:32 ` batouzo [this message]
2011-12-14 16:40 ` Alex Deucher
2011-12-14 17:12 ` batouzo
2011-12-14 17:21 ` Alex Deucher
2011-12-14 17:27 ` batouzo
2011-12-14 17:40 ` Alex Deucher
2011-12-14 17:49 ` batouzo
2011-12-14 18:14 ` Alex Deucher
2011-12-14 16:18 ` Jerome Glisse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='jcaj21$iej$1@dough.gmane.org' \
--to=batouzo@gmx.com \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.