From: "Michel Dänzer" <michel@daenzer.net>
To: Pavel Ivanov <paivanof@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel almost hangs when CONFIG_DRM_RADEON=y
Date: Sat, 27 Aug 2011 11:00:38 +0200 [thread overview]
Message-ID: <1314435638.2321.12.camel@thor.local> (raw)
In-Reply-To: <CAG1a4rs53RwkSxBvRQ5MrUbm7KEnpuEjw2fhSnT_1vqVPQrqgA@mail.gmail.com>
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
next prev parent reply other threads:[~2011-08-27 9:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 4:20 Kernel almost hangs when CONFIG_DRM_RADEON=y Pavel Ivanov
2011-08-27 9:00 ` Michel Dänzer [this message]
2011-08-27 22:50 ` Pavel Ivanov
2011-08-28 5:36 ` Borislav Petkov
2011-08-28 21:47 ` Pavel Ivanov
2011-08-29 5:49 ` Borislav Petkov
2011-08-29 6:04 ` Michel Dänzer
2011-08-29 13:20 ` Peter Zijlstra
2011-08-29 13:38 ` Borislav Petkov
2011-08-29 13:43 ` Dave Airlie
2011-08-29 13:48 ` Alex Deucher
2011-08-29 14:16 ` Borislav Petkov
2011-08-29 15:47 ` David Airlie
2011-08-29 15:55 ` Borislav Petkov
2011-08-29 16:10 ` Arnaud Lacombe
2011-08-29 17:17 ` Borislav Petkov
2011-08-29 17:38 ` Michel Dänzer
2011-08-29 17:50 ` Peter Zijlstra
2011-08-29 18:09 ` Peter Zijlstra
2011-08-29 18:16 ` Peter Zijlstra
2011-08-29 21:14 ` Borislav Petkov
2011-08-30 2:08 ` Henrique de Moraes Holschuh
2011-08-30 7:17 ` Borislav Petkov
2011-08-30 14:44 ` Henrique de Moraes Holschuh
2011-08-30 8:37 ` Peter Zijlstra
2011-08-30 14:55 ` Henrique de Moraes Holschuh
2011-08-29 16:28 ` Kyle Moffett
2011-08-29 17:21 ` Borislav Petkov
2011-08-29 17:51 ` Peter Zijlstra
2011-08-27 23:03 ` Kyle Moffett
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=1314435638.2321.12.camel@thor.local \
--to=michel@daenzer.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paivanof@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox