Ubuntu
linux-source-2.6.17 package

no suspend2ram on edgy (ibook g4)

Bug #59848 reported by Keywan Tonekaboni
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I couldn't suspend to ram anymore. I had "no" problems on dapper. now I switched to edgy it's broken. /sys/power/state just contains standby. on 2.6.15-26 suspend is broken, too. It can mem, disk, standby, but disk never worked and mem go to sleep and immediately wake up. display didn't come back, but I was able to switch to a console and shutdown computer blind.

Package: linux-image-2.6.17-7-powerpc
Version: 2.6.17-7.20

-- System Information:
Debian Release: testing/unstable
  APT prefers edgy-updates
  APT policy: (990, 'edgy-updates'), (990, 'edgy-security'), (990, 'edgy-proposed'), (990, 'edgy-backports'), (990, 'edgy')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.15-26-powerpc
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.17-7-powerpc depends on:
ii coreutils [fileutils] 5.96-5ubuntu3 The GNU core utilities
ii initramfs-tools 0.69ubuntu11 tools for generating an initramfs
ii module-init-tools 3.2.2-3ubuntu3 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.17-7-powerpc recommends:
ii yaboot 1.3.13a-1ubuntu2 Yet Another Bootloader

-- debconf information:
  linux-image-2.6.17-7-powerpc/postinst/bootloader-error-2.6.17-7-powerpc:
  linux-image-2.6.17-7-powerpc/postinst/old-initrd-link-2.6.17-7-powerpc: true
  linux-image-2.6.17-7-powerpc/postinst/old-system-map-link-2.6.17-7-powerpc: true
  linux-image-2.6.17-7-powerpc/postinst/old-dir-initrd-link-2.6.17-7-powerpc: true
  linux-image-2.6.17-7-powerpc/postinst/depmod-error-initrd-2.6.17-7-powerpc: false
  linux-image-2.6.17-7-powerpc/preinst/abort-install-2.6.17-7-powerpc:
  linux-image-2.6.17-7-powerpc/preinst/bootloader-initrd-2.6.17-7-powerpc: true
  linux-image-2.6.17-7-powerpc/postinst/bootloader-test-error-2.6.17-7-powerpc:
  linux-image-2.6.17-7-powerpc/preinst/failed-to-move-modules-2.6.17-7-powerpc:
  linux-image-2.6.17-7-powerpc/postinst/kimage-is-a-directory:
  linux-image-2.6.17-7-powerpc/preinst/abort-overwrite-2.6.17-7-powerpc:
  linux-image-2.6.17-7-powerpc/prerm/removing-running-kernel-2.6.17-7-powerpc: true
  linux-image-2.6.17-7-powerpc/preinst/initrd-2.6.17-7-powerpc:
  linux-image-2.6.17-7-powerpc/prerm/would-invalidate-boot-loader-2.6.17-7-powerpc: true
  linux-image-2.6.17-7-powerpc/preinst/already-running-this-2.6.17-7-powerpc:
  linux-image-2.6.17-7-powerpc/postinst/create-kimage-link-2.6.17-7-powerpc: true
  linux-image-2.6.17-7-powerpc/preinst/elilo-initrd-2.6.17-7-powerpc: true
  linux-image-2.6.17-7-powerpc/postinst/depmod-error-2.6.17-7-powerpc: false
  linux-image-2.6.17-7-powerpc/preinst/lilo-initrd-2.6.17-7-powerpc: true
  linux-image-2.6.17-7-powerpc/preinst/overwriting-modules-2.6.17-7-powerpc: true
  linux-image-2.6.17-7-powerpc/preinst/lilo-has-ramdisk:

See original description
Keywan Tonekaboni (prometoys)
description: updated
Revision history for this message
Jonathan Hudson (jh+lpd) wrote :

Don't know if this is related or should be a separate report.

On my PPC, 2.6.17-10 suspends just fine, but locks the machine solid on resume. On Dapper, suspend resume worked fine.

The kernel prior to 2006-10-05 would mostly resume, albeit with screen corruption.

Revision history for this message
Jonathan Hudson (jh+lpd) wrote :

Here' some more stuff on the failure to resume. Sometimes the box is alive, but the display isn't:
[ 206.275809] radeonfb (0000:00:10.0): suspending to state: 2...
[ 206.276052] uninorth-agp: disabling AGP on device 0000:00:10.0
[ 206.276066] uninorth-agp: disabling AGP on bridge 0000:00:0b.0
[ 206.276078] radeonfb (0000:00:10.0): switching to D2 state...
[ 207.193713] radeonfb (0000:00:10.0): resuming from state: 2...
[ 207.193757] radeonfb (0000:00:10.0): switching to D0 state...
[ 207.930694] agpgart: Putting AGP V2 device at 0000:00:0b.0 into 1x mode
[ 207.930712] agpgart: Putting AGP V2 device at 0000:00:10.0 into 1x mode
[ 208.167654] PM: Writing back config space on device 0001:10:1a.0 at offset 1 (was 2100003, writing 2100007)
[ 208.881580] eth0: resuming
[ 208.946917] PHY ID: 2060e1, addr: 0
[ 210.986567] eth1: Airport waking up
[ 211.353770] hda: Enabling Ultra DMA 4
[ 211.813803] hdc: Enabling MultiWord DMA 2
[ 211.977564] PCI: Enabling device 0001:11:00.0 (0000 -> 0002)
[ 211.977580] ra0: got resume request
[ 211.977589] PM: Writing back config space on device 0001:11:00.0 at offset f (was 100, writing 13a)
[ 211.977614] PM: Writing back config space on device 0001:11:00.0 at offset 4 (was ffffe000, writing f3000000)
[ 211.977630] PM: Writing back config space on device 0001:11:00.0 at offset 1 (was 4100002, writing 4100006)
[ 212.523086] adb: starting probe task...
[ 212.778693] adb devices: [2]: 2 c4 [3]: 3 1 [7]: 7 1f
[ 212.785078] ADB keyboard at 2, handler 1
[ 212.800160] ADB mouse at 3, handler set to 4 (trackpad)
[ 212.859524] adb: finished probe task...
[ 222.104815] radeonfb: Idle Timeout !
[ 239.512540] radeonfb: Idle Timeout !
[ 242.323688] radeonfb: Idle Timeout !
[ 245.092957] radeonfb: Idle Timeout !
[ 247.812973] radeonfb: Idle Timeout !

Revision history for this message
Jonathan Hudson (jh+lpd) wrote :

The resume lock ups are fixed by adding /etc/power/{resume,suspend}.d/ scripts to switch from X to a console and back again. which was the previous working behaviour. It has nothing to do with the OPs bug.

Sorry for the noise.

Revision history for this message
Keywan Tonekaboni (prometoys) wrote :

Hi,

I just dont have suspend:

root@cassini:~# uname -r
2.6.17-10-powerpc
root@cassini:~# cat /sys/power/state
disk

I can't find a related change in the kernel config. is it somewhere deactivated?

Revision history for this message
Alessio Caiazza (nolith) wrote :

I can't suspend to ram too on my iBook G4 1GHz with edgy.
On Dapper I had any problem.

Revision history for this message
Matthias Jordan (matthiasjordan) wrote :

Can repro. On my G4 iBook it looks like this:
In GDM (i.e. without GNOME running) the iBook goes into Standby when the cover is closed. As soon as GNOME is running, closing the cover only locks the screen. There is no Standby and no suspend2ram in this case. cat /sys/power/state prints "disk" on my machine.
As Alessio reported: suspend was no problem on my machine with Dapper.

Revision history for this message
Matthias Jordan (matthiasjordan) wrote :

By a lucky coincidence I found out that uninstalling the hibernate package seems to resolve the problem. Keywan can reproduce this effect, too. Anybody else?

Revision history for this message
Alessio Caiazza (nolith) wrote : Re: [Bug 59848] Re: no suspend2ram on edgy (ibook g4)

I'm on KDE and just before logging in, if I clode the lid, the standby
led blink, the apple led switch off and just after a second it switch
on.
Open a lid and you can find a nice black screen.

I've tried with hibernate, wich was not installed on my machine, does
not work neither with nor without.

bye,
Alessio

2006/11/7, Matthias Jordan <email address hidden>:
> Can repro. On my G4 iBook it looks like this:
> In GDM (i.e. without GNOME running) the iBook goes into Standby when the cover is closed. As soon as GNOME is running, closing the cover only locks the screen. There is no Standby and no suspend2ram in this case. cat /sys/power/state prints "disk" on my machine.
> As Alessio reported: suspend was no problem on my machine with Dapper.
>
>

Revision history for this message
Alessio Caiazza (nolith) wrote :

Ok.
I made a fresh install of Ubuntu edgy.
Sleep has worked only first time.
After that I had same problem of Kubuntu.

Revision history for this message
Alessio Caiazza (nolith) wrote :

After 5 monts it's still unconfirmed?
Anyone has a workaround? I consider sleep a major feature.

Revision history for this message
Keywan Tonekaboni (prometoys) wrote :

On feisty suspend works great. i close this bug, even though suspend didn't work in gutsy, but I think in gutsy its another problem

Changed in linux-source-2.6.17:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.