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-next>] [day] [month] [year] [list]
Date:	Sat, 27 Aug 2011 00:20:51 -0400
From:	Pavel Ivanov <paivanof@...il.com>
To:	David Airlie <airlied@...ux.ie>, dri-devel@...ts.freedesktop.org
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Kernel almost hangs when CONFIG_DRM_RADEON=y

Hi,

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


Is this a bug?


I'm seeing this on 3.1-rc3. Full dmesgs for both boots are attached.


Pavel

Download attachment "dmesg.module" of type "application/octet-stream" (81378 bytes)

Download attachment "dmesg.built-in" of type "application/octet-stream" (81503 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ