dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43278] System hangs after suspend to ram or disk cause radeon firmware cannot be loaded.
Date: Mon, 28 Nov 2011 08:48:57 +0000	[thread overview]
Message-ID: <bug-43278-502-4FENVF6frh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-43278-502@http.bugs.freedesktop.org/>

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

--- Comment #2 from Rolf <hubba@online.de> 2011-11-28 00:48:57 PST ---
On 27.11.2011 19:19, bugzilla-daemon@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=43278
>
> --- Comment #1 from Jonathan Nieder<jrnieder@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.

  parent reply	other threads:[~2011-11-28  8:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-27 17:45 [Bug 43278] New: System hangs after suspend to ram or disk cause radeon firmware cannot be loaded bugzilla-daemon
2011-11-27 18:19 ` [Bug 43278] " bugzilla-daemon
2011-11-28  8:48 ` bugzilla-daemon [this message]
2011-11-28  8:58 ` bugzilla-daemon
2011-11-28 10:43 ` bugzilla-daemon
2011-11-28 11:16 ` bugzilla-daemon
2011-11-28 13:44 ` bugzilla-daemon
2011-11-28 14:39 ` bugzilla-daemon
2011-11-28 15:11 ` bugzilla-daemon
2011-11-28 23:38 ` [Bug 43278] RS482: Hibernation reliably hangs, suspend-to-RAM unreliably hangs bugzilla-daemon
2011-11-29  7:39 ` bugzilla-daemon
2011-11-29  7:39 ` bugzilla-daemon
2012-03-20 18:47 ` bugzilla-daemon
2012-03-21 12:01 ` bugzilla-daemon
2012-03-21 17:49 ` bugzilla-daemon
2012-03-26  8:46 ` bugzilla-daemon
2013-04-08  8:46 ` bugzilla-daemon
2019-11-19  8:23 ` bugzilla-daemon

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=bug-43278-502-4FENVF6frh@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox