Bug 467429 - Resume on radeon doesn't work with modeset in runlevel 3
Summary: Resume on radeon doesn't work with modeset in runlevel 3
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 10
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-17 13:06 UTC by Mads Kiilerich
Modified: 2018-04-11 09:23 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-03 14:19:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/var/log/messages from boot to runlevel 3 without nomodesetting where pm-suspend can't resume (56.33 KB, text/plain)
2008-10-20 15:49 UTC, Mads Kiilerich
no flags Details
Xorg.0.log from session without nomodeset which can't resume - but it probably isn't interestning when the same is seen without X ... (86.53 KB, text/plain)
2008-10-20 15:51 UTC, Mads Kiilerich
no flags Details

Description Mads Kiilerich 2008-10-17 13:06:03 UTC
Description of problem:

With nomodeset (and thus textual boot sequence) suspend/resume works fine.

Without nomodeset (and thus graphical boot sequence) then resume hangs.

01:00.1 Display controller: ATI Technologies Inc RV516 [Radeon X1300 Pro] (Secondary)
in Dell OptiPlex 745

Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.9.0-27.fc10.i386
kernel-2.6.27-13.fc10.i686

How reproducible:
100%

Comment 1 Matěj Cepl 2008-10-18 00:13:23 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config files (/etc/X11/xorg.conf) and X server log files (/var/log/Xorg.*.log), and /var/log/dmesg from both attempts to start Xorg (with and without nomodeset) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 Mads Kiilerich 2008-10-20 15:43:36 UTC
I tried booting to runlevel 3 (no X) but without nomodeset (and thus with graphical boot sequence) . After pm-suspend I couldn't resume.

So it isn't related to X and I reassign to kernel.

When booting to runlevel 5 it runs without xorg.conf.

Logs from running with nomodeset is attached to Bug 467430.

Comment 3 Mads Kiilerich 2008-10-20 15:49:47 UTC
Created attachment 320876 [details]
/var/log/messages from boot to runlevel 3 without nomodesetting where pm-suspend can't resume

Comment 4 Mads Kiilerich 2008-10-20 15:51:22 UTC
Created attachment 320877 [details]
Xorg.0.log from session without nomodeset which can't resume - but it probably isn't interestning when the same is seen without X ...

Comment 5 Mads Kiilerich 2008-10-23 12:13:01 UTC
Problem remains with
xorg-x11-drv-ati-6.9.0-29.fc10.i386
kernel-2.6.27.3-34.rc1.fc10.i686

Comment 6 Mads Kiilerich 2008-10-24 14:56:06 UTC
I changed the component to kernel, but can't change the assignment from X team to kernel team. 

Could someone please un/reassign.

Comment 7 Mads Kiilerich 2008-10-28 18:38:33 UTC
kernel-2.6.27.4-58.fc10.i686 contained some radeon fixes, but it did not fix this.

Comment 8 Mads Kiilerich 2008-10-31 18:06:28 UTC
FWIW, the same with kernel-2.6.27.4-69.fc10.i686

Comment 9 Mads Kiilerich 2008-11-04 20:59:47 UTC
- and rawhide with
kernel-2.6.27.4-73.fc10.i686
xorg-x11-drv-ati-6.9.0-41.fc10.i386

Comment 10 Mads Kiilerich 2008-11-10 22:58:06 UTC
and kernel-2.6.27.5-92.fc10.i686

Comment 11 Mads Kiilerich 2008-11-13 22:09:20 UTC
airlied: should be fixed with latest kernel/pm-utils
airlied: -104 kernel + pm-utils 1.2.2.1-2

Comment 12 Mads Kiilerich 2008-11-14 00:58:30 UTC
It did NOT work with
kernel-2.6.27.5-104.fc10.i686 (modeset)
xorg-x11-drv-ati-6.9.0-44.fc10.i386 (neither with or without)
pm-utils-1.2.2.1-2.fc10.i386

Can I debug more somehow?

Btw: the proper way to test from runlevel 3 - that is a plain "pm-suspend", right?

Comment 13 Jeff Layton 2008-11-14 01:56:23 UTC
Didn't work for me either:

kernel-2.6.27.5-104.fc10.i686
pm-utils-1.2.2.1-2.fc10.i386
xorg-x11-drv-ati-6.9.0-38.fc10.i386

...the behavior is pretty much:

"normal" boot -- without nomodeset:
-----------------------------------
suspend makes laptop go to sleep, but it will not resume
hibernate fails to ever power off the machine

with nomodeset:
---------------
suspend makes laptop go to sleep, but it will not resume
hibernate and wakeup works as expected

Comment 14 Mads Kiilerich 2008-11-15 00:06:49 UTC
Suspend AND resume works fine for me with nomodeset. So apparently it isn't exactly the same problem we have. 

(jlayton: Perhaps you should creater another issue with your system information and logs. Or you could wait and see if it gets solved with this issue.)

(I don't use hibernate and haven't tested it. Will do when suspend works.)

Comment 15 Jeff Layton 2008-11-15 11:00:00 UTC
Thanks Mads,

I've gone ahead and opened bug 471711 for the problems I'm seeing.

Comment 16 Bug Zapper 2008-11-26 03:57:17 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 17 Jan Martinek 2008-11-29 15:45:18 UTC
I confirm this issue with similar hardware

01:05.0 VGA compatible controller: ATI Technologies Inc RS690 [Radeon X1200 Series]

and kernel-2.6.27.7-130.fc10.x86_64.

With "nomodeset" (KMS disabled), suspend to ram (echo mem > /sys/power/state)
 works as well as resuming.

But if KMS is active, the computer suspends but resuming does not work (black screen, everything dead).

Comment 18 Lev Shamardin 2008-12-03 06:40:35 UTC
Can you please check if you have stuff like this in /var/log/messages after a failed resume?

Dec  2 12:25:35 lopeptoid kernel: Suspending console(s) (use no_console_suspend
to debug)
Dec  2 12:25:35 lopeptoid kernel: [drm:drm_bo_evict_mm] *ERROR* lru empty
Dec  2 12:25:35 lopeptoid kernel: [drm] Num pipes: 1
...
Dec  2 12:25:35 lopeptoid kernel: pci 0000:01:00.0: PCI INT A -> GSI 16 (level,
low) -> IRQ 16
Dec  2 12:25:35 lopeptoid kernel: [drm:radeon_resume] *ERROR* 
Dec  2 12:25:35 lopeptoid kernel: [drm] Loading R500 Microcode
Dec  2 12:25:35 lopeptoid kernel: [drm] Num pipes: 1
Dec  2 12:25:35 lopeptoid kernel: [drm] writeback test failed
Dec  2 12:25:35 lopeptoid kernel: [drm:drm_ttm_bind] *ERROR* Couldn't bind
backend.
Dec  2 12:25:35 lopeptoid kernel: executing set pll
Dec  2 12:25:35 lopeptoid kernel: executing set crtc timing
Dec  2 12:25:35 lopeptoid kernel: [drm] LVDS-8: set mode 1280x800 10
Dec  2 12:25:35 lopeptoid kernel: executing set LVDS encoder
Dec  2 12:25:35 lopeptoid kernel: Restarting tasks ... done.

Comment 19 Mads Kiilerich 2008-12-03 14:19:59 UTC
It seems to work fine with
kernel-2.6.27.7-130.fc10.i686 modeset
xorg-x11-drv-ati-6.9.0-60.fc10.i386
from updates-testing

Closing.


Note You need to log in before you can comment on or make changes to this bug.