[Bug 43278] System hangs after suspend to ram or disk cause radeon firmware cannot be loaded.

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Nov 28 00:48:57 PST 2011


https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #2 from Rolf <hubba at online.de> 2011-11-28 00:48:57 PST ---
On 27.11.2011 19:19, bugzilla-daemon at freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=43278
>
> --- Comment #1 from Jonathan Nieder<jrnieder at gmail.com>  2011-11-27 10:19:47 PST ---
> Hi Rolf,
>
> Actually there's one more test that it would be useful to try. Please try
> preventing the radeon driver from being loaded at boot time, like this:
>
>    echo 'blacklist radeon'>/etc/modprobe.d/rh-blacklist-radeon.conf
>    update-initramfs -u -k all
>    reboot
>
> Then try hibernating before and after loading the radeon module.
>
> If I am lucky, the "Failed to load firmware" messages will not show up in
> dmesg, but the second time you hibernate after loading the radeon module the
> hibernation will fail.
>
Hi Jonathan,

first I should mention that there already exist 2 files in 
/etc/modprobe.d concerning the radeon module and having the following 
contents:

fbdev-blacklist.conf:blacklist radeonfb
radeon-kms.conf:options radeon modeset=1

Second, executing your proposition seems not to prevent the radeon 
module from being loaded.
There is a certain difference in system behaviour that the login window 
of the graphical desktop manager kdm is not automatically opened but 
insteat a shell login prompt is given.
But after login as user root the lsmod command shows that radeon is 
loaded - maybe because other modules like ttm and drm are depending on it?
Unloading the module with "modprobe -r radeon" does not work and shows 
message "the module is in use" .
The dmesg output does not contain the firmware error message at this point.
Please let me know how to go on.

Thanks and regards
Rolf

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the dri-devel mailing list