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

2011-11-28 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #8 from Rolf  2011-11-28 07:11:01 PST ---
On 28.11.2011 15:39, bugzilla-daemon at freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=43278
>
> --- Comment #7 from Alex Deucher  2011-11-28 06:39:03 PST 
> ---
> Install the debian firmware package.
>

What is the name of the package you mean?

The packages firmware-linux, firmware-linux-free and 
firmware-linux-nonfree are already installed.

The directory /lib/firmware/radeon exists and has the following contents:

-rw-r--r-- 1 root root 24096 Nov  2 14:45 BARTS_mc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 BARTS_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 BARTS_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 BTC_rlc.bin
-rw-r--r-- 1 root root 24096 Nov  2 14:45 CAICOS_mc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 CAICOS_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 CAICOS_pfp.bin
-rw-r--r-- 1 root root 24148 Nov  2 14:45 CAYMAN_mc.bin
-rw-r--r-- 1 root root  8704 Nov  2 14:45 CAYMAN_me.bin
-rw-r--r-- 1 root root  8704 Nov  2 14:45 CAYMAN_pfp.bin
-rw-r--r-- 1 root root  4096 Nov  2 14:45 CAYMAN_rlc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 CEDAR_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 CEDAR_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 CEDAR_rlc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 CYPRESS_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 CYPRESS_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 CYPRESS_rlc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 JUNIPER_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 JUNIPER_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 JUNIPER_rlc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 PALM_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 PALM_pfp.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 R100_cp.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 R200_cp.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 R300_cp.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 R420_cp.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 R520_cp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 R600_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 R600_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 R600_rlc.bin
-rw-r--r-- 1 root root  4096 Nov  2 14:45 R700_rlc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 REDWOOD_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 REDWOOD_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 REDWOOD_rlc.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 RS600_cp.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 RS690_cp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 RS780_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 RS780_pfp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 RV610_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 RV610_pfp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 RV620_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 RV620_pfp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 RV630_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 RV630_pfp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 RV635_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 RV635_pfp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 RV670_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 RV670_pfp.bin
-rw-r--r-- 1 root root  5440 Nov  2 14:45 RV710_me.bin
-rw-r--r-- 1 root root  3392 Nov  2 14:45 RV710_pfp.bin
-rw-r--r-- 1 root root  5440 Nov  2 14:45 RV730_me.bin
-rw-r--r-- 1 root root  3392 Nov  2 14:45 RV730_pfp.bin
-rw-r--r-- 1 root root  5440 Nov  2 14:45 RV770_me.bin
-rw-r--r-- 1 root root  3392 Nov  2 14:45 RV770_pfp.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 SUMO2_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 SUMO2_pfp.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 SUMO_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 SUMO_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 SUMO_rlc.bin
-rw-r--r-- 1 root root 24096 Nov  2 14:45 TURKS_mc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 TURKS_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 TURKS_pfp.bin

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


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

2011-11-28 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #7 from Alex Deucher  2011-11-28 06:39:03 PST 
---
Install the debian firmware package.

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


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

2011-11-28 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #6 from Rolf  2011-11-28 05:44:48 PST ---
On 28.11.2011 12:16, bugzilla-daemon at freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=43278
>
> --- Comment #5 from Jonathan Nieder  2011-11-28 
> 03:16:18 PST ---
> bugzilla-daemon at freedesktop.org wrote:
>
>> - hibernate test works very fine 3 times in follow
>> - after load of radeon module, system hangup on first hibernate test
> Great.
>
> Hopefully someone knowledgeable can step in to figure out why the
> radeon device is failing to hibernate.
>
> Aside from diving into the source and writing patches to confirm
> guesses about what's happening, the only trick I can think of is to
> try passing "drm.debug=0x6" and "no_console_suspend" as parameters on
> the kernel command line and hibernate to provoke the hang, capturing
> messages either using netconsole[1] or by taking a photograph of the
> screen if it stays up long enough.
>
> You mentioned before that suspend-to-RAM always works the first time
> you try it, and not the second.  Please attach full output from
> "dmesg" after booting and suspending successfully (to RAM or disk is
> not so important to me) with the radeon driver loaded and kernel
> parameter drm.debug=0x6 (and no_console_suspend if it happens to have
> been passed; it's not too relevant here).
>
> Thanks for your help and patience,
> Jonathan
>
> [1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt
>
Attached the dmesg output after successful first suspend to ram.
When the system hangs up there is no output on the screen - after some 
seconds the screen turns to power safe mode and the power led of the 
notebook does not start  to blink as normally in sleep mode but keeps on 
burning - and the system does not react any longer to mouse or keyboard 
action - and that's it - not output.
When trying the "drm.debug=0x6" and "no_console_suspend" parameters the 
system sometimes didn't hangup on hibernate test - the test worked 3 
times in follow without hangup.
And second suspend to disk with the two parameters did not really 
suspend - the power led continued to burn as described above - and the 
screen turned to power safe mode - but after a second or two the screen 
powered up again and showed the login screen of suspend mode.
But this could not be reproduced constantly - strange!

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


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

2011-11-28 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #5 from Jonathan Nieder  2011-11-28 03:16:18 
PST ---
bugzilla-daemon at freedesktop.org wrote:

> - hibernate test works very fine 3 times in follow
> - after load of radeon module, system hangup on first hibernate test

Great.

Hopefully someone knowledgeable can step in to figure out why the
radeon device is failing to hibernate.

Aside from diving into the source and writing patches to confirm
guesses about what's happening, the only trick I can think of is to
try passing "drm.debug=0x6" and "no_console_suspend" as parameters on
the kernel command line and hibernate to provoke the hang, capturing
messages either using netconsole[1] or by taking a photograph of the
screen if it stays up long enough.

You mentioned before that suspend-to-RAM always works the first time
you try it, and not the second.  Please attach full output from
"dmesg" after booting and suspending successfully (to RAM or disk is
not so important to me) with the radeon driver loaded and kernel
parameter drm.debug=0x6 (and no_console_suspend if it happens to have
been passed; it's not too relevant here).

Thanks for your help and patience,
Jonathan

[1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt

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


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

2011-11-28 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #4 from Rolf  2011-11-28 02:43:20 PST ---
On 28.11.2011 09:58, bugzilla-daemon at freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=43278
>
> --- Comment #3 from Jonathan Nieder  2011-11-28 
> 00:58:39 PST ---
> bugzilla-daemon at freedesktop.org wrote:
>
>> executing your proposition seems not to prevent the radeon
>> module from being loaded.
> Oh, right --- X loads the radeon module.  Could you choose "recovery
> mode" from the grub menu so X isn't started and try again?
>

So, in recovery mode everything behaves as you expected:

- radeon module is not loaded
- hibernate test works very fine 3 times in follow
- after load of radeon module, system hangup on first hibernate test

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


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

2011-11-28 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #3 from Jonathan Nieder  2011-11-28 00:58:39 
PST ---
bugzilla-daemon at freedesktop.org wrote:

> executing your proposition seems not to prevent the radeon 
> module from being loaded.

Oh, right --- X loads the radeon module.  Could you choose "recovery
mode" from the grub menu so X isn't started and try again?

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


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

2011-11-28 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #2 from Rolf  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  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.


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

2011-11-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #8 from Rolf  2011-11-28 07:11:01 PST ---
On 28.11.2011 15:39, bugzilla-dae...@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=43278
>
> --- Comment #7 from Alex Deucher  2011-11-28 06:39:03 PST ---
> Install the debian firmware package.
>

What is the name of the package you mean?

The packages firmware-linux, firmware-linux-free and 
firmware-linux-nonfree are already installed.

The directory /lib/firmware/radeon exists and has the following contents:

-rw-r--r-- 1 root root 24096 Nov  2 14:45 BARTS_mc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 BARTS_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 BARTS_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 BTC_rlc.bin
-rw-r--r-- 1 root root 24096 Nov  2 14:45 CAICOS_mc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 CAICOS_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 CAICOS_pfp.bin
-rw-r--r-- 1 root root 24148 Nov  2 14:45 CAYMAN_mc.bin
-rw-r--r-- 1 root root  8704 Nov  2 14:45 CAYMAN_me.bin
-rw-r--r-- 1 root root  8704 Nov  2 14:45 CAYMAN_pfp.bin
-rw-r--r-- 1 root root  4096 Nov  2 14:45 CAYMAN_rlc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 CEDAR_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 CEDAR_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 CEDAR_rlc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 CYPRESS_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 CYPRESS_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 CYPRESS_rlc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 JUNIPER_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 JUNIPER_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 JUNIPER_rlc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 PALM_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 PALM_pfp.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 R100_cp.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 R200_cp.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 R300_cp.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 R420_cp.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 R520_cp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 R600_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 R600_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 R600_rlc.bin
-rw-r--r-- 1 root root  4096 Nov  2 14:45 R700_rlc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 REDWOOD_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 REDWOOD_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 REDWOOD_rlc.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 RS600_cp.bin
-rw-r--r-- 1 root root  2048 Nov  2 14:45 RS690_cp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 RS780_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 RS780_pfp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 RV610_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 RV610_pfp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 RV620_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 RV620_pfp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 RV630_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 RV630_pfp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 RV635_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 RV635_pfp.bin
-rw-r--r-- 1 root root 21504 Nov  2 14:45 RV670_me.bin
-rw-r--r-- 1 root root  2304 Nov  2 14:45 RV670_pfp.bin
-rw-r--r-- 1 root root  5440 Nov  2 14:45 RV710_me.bin
-rw-r--r-- 1 root root  3392 Nov  2 14:45 RV710_pfp.bin
-rw-r--r-- 1 root root  5440 Nov  2 14:45 RV730_me.bin
-rw-r--r-- 1 root root  3392 Nov  2 14:45 RV730_pfp.bin
-rw-r--r-- 1 root root  5440 Nov  2 14:45 RV770_me.bin
-rw-r--r-- 1 root root  3392 Nov  2 14:45 RV770_pfp.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 SUMO2_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 SUMO2_pfp.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 SUMO_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 SUMO_pfp.bin
-rw-r--r-- 1 root root  3072 Nov  2 14:45 SUMO_rlc.bin
-rw-r--r-- 1 root root 24096 Nov  2 14:45 TURKS_mc.bin
-rw-r--r-- 1 root root  5504 Nov  2 14:45 TURKS_me.bin
-rw-r--r-- 1 root root  4480 Nov  2 14:45 TURKS_pfp.bin

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel


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

2011-11-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #7 from Alex Deucher  2011-11-28 06:39:03 PST ---
Install the debian firmware package.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel


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

2011-11-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #6 from Rolf  2011-11-28 05:44:48 PST ---
On 28.11.2011 12:16, bugzilla-dae...@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=43278
>
> --- Comment #5 from Jonathan Nieder  2011-11-28 03:16:18 
> PST ---
> bugzilla-dae...@freedesktop.org wrote:
>
>> - hibernate test works very fine 3 times in follow
>> - after load of radeon module, system hangup on first hibernate test
> Great.
>
> Hopefully someone knowledgeable can step in to figure out why the
> radeon device is failing to hibernate.
>
> Aside from diving into the source and writing patches to confirm
> guesses about what's happening, the only trick I can think of is to
> try passing "drm.debug=0x6" and "no_console_suspend" as parameters on
> the kernel command line and hibernate to provoke the hang, capturing
> messages either using netconsole[1] or by taking a photograph of the
> screen if it stays up long enough.
>
> You mentioned before that suspend-to-RAM always works the first time
> you try it, and not the second.  Please attach full output from
> "dmesg" after booting and suspending successfully (to RAM or disk is
> not so important to me) with the radeon driver loaded and kernel
> parameter drm.debug=0x6 (and no_console_suspend if it happens to have
> been passed; it's not too relevant here).
>
> Thanks for your help and patience,
> Jonathan
>
> [1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt
>
Attached the dmesg output after successful first suspend to ram.
When the system hangs up there is no output on the screen - after some 
seconds the screen turns to power safe mode and the power led of the 
notebook does not start  to blink as normally in sleep mode but keeps on 
burning - and the system does not react any longer to mouse or keyboard 
action - and that's it - not output.
When trying the "drm.debug=0x6" and "no_console_suspend" parameters the 
system sometimes didn't hangup on hibernate test - the test worked 3 
times in follow without hangup.
And second suspend to disk with the two parameters did not really 
suspend - the power led continued to burn as described above - and the 
screen turned to power safe mode - but after a second or two the screen 
powered up again and showed the login screen of suspend mode.
But this could not be reproduced constantly - strange!

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel


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

2011-11-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #5 from Jonathan Nieder  2011-11-28 03:16:18 
PST ---
bugzilla-dae...@freedesktop.org wrote:

> - hibernate test works very fine 3 times in follow
> - after load of radeon module, system hangup on first hibernate test

Great.

Hopefully someone knowledgeable can step in to figure out why the
radeon device is failing to hibernate.

Aside from diving into the source and writing patches to confirm
guesses about what's happening, the only trick I can think of is to
try passing "drm.debug=0x6" and "no_console_suspend" as parameters on
the kernel command line and hibernate to provoke the hang, capturing
messages either using netconsole[1] or by taking a photograph of the
screen if it stays up long enough.

You mentioned before that suspend-to-RAM always works the first time
you try it, and not the second.  Please attach full output from
"dmesg" after booting and suspending successfully (to RAM or disk is
not so important to me) with the radeon driver loaded and kernel
parameter drm.debug=0x6 (and no_console_suspend if it happens to have
been passed; it's not too relevant here).

Thanks for your help and patience,
Jonathan

[1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel


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

2011-11-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #4 from Rolf  2011-11-28 02:43:20 PST ---
On 28.11.2011 09:58, bugzilla-dae...@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=43278
>
> --- Comment #3 from Jonathan Nieder  2011-11-28 00:58:39 
> PST ---
> bugzilla-dae...@freedesktop.org wrote:
>
>> executing your proposition seems not to prevent the radeon
>> module from being loaded.
> Oh, right --- X loads the radeon module.  Could you choose "recovery
> mode" from the grub menu so X isn't started and try again?
>

So, in recovery mode everything behaves as you expected:

- radeon module is not loaded
- hibernate test works very fine 3 times in follow
- after load of radeon module, system hangup on first hibernate test

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel


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

2011-11-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #3 from Jonathan Nieder  2011-11-28 00:58:39 
PST ---
bugzilla-dae...@freedesktop.org wrote:

> executing your proposition seems not to prevent the radeon 
> module from being loaded.

Oh, right --- X loads the radeon module.  Could you choose "recovery
mode" from the grub menu so X isn't started and try again?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel


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

2011-11-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #2 from Rolf  2011-11-28 00:48:57 PST ---
On 27.11.2011 19:19, bugzilla-dae...@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=43278
>
> --- Comment #1 from Jonathan Nieder  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.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel


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

2011-11-27 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #1 from Jonathan Nieder  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.

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


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

2011-11-27 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=43278

--- Comment #1 from Jonathan Nieder  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.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel