Suspend fails in Jaunty on Macbook 4,1

From syslog:

Mar 18 15:47:59 abstractmobile NetworkManager: <info> Sleeping...
Mar 18 15:47:59 abstractmobile NetworkManager: <info> (eth1): now unmanaged
Mar 18 15:47:59 abstractmobile NetworkManager: <info> (eth1): device state change: 2 -> 1
Mar 18 15:47:59 abstractmobile NetworkManager: <info> (eth1): cleaning up...
Mar 18 15:47:59 abstractmobile NetworkManager: <info> (eth1): taking down device.
Mar 18 15:47:59 abstractmobile NetworkManager: <info> (wlan0): now unmanaged
Mar 18 15:47:59 abstractmobile NetworkManager: <info> (wlan0): device state change: 8 -> 1
Mar 18 15:47:59 abstractmobile NetworkManager: <info> (wlan0): deactivating device (reason: 37).
Mar 18 15:47:59 abstractmobile kernel: [ 9534.177068] sky2 eth1: disabling interface
Mar 18 15:47:59 abstractmobile NetworkManager: <info> wlan0: canceled DHCP transaction, dhcp client pid 2589
Mar 18 15:47:59 abstractmobile NetworkManager: <WARN> check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess
Mar 18 15:47:59 abstractmobile NetworkManager: <info> (wlan0): cleaning up...
Mar 18 15:47:59 abstractmobile NetworkManager: <info> (wlan0): taking down device.
Mar 18 15:47:59 abstractmobile NetworkManager: <info> Waking up...
Mar 18 15:47:59 abstractmobile NetworkManager: <info> (eth1): now managed
Mar 18 15:47:59 abstractmobile NetworkManager: <info> (eth1): device state change: 1 -> 2
Mar 18 15:47:59 abstractmobile NetworkManager: <info> (eth1): bringing up device.

Not terribly helpful.

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please attach the resulting log file of: gnome-power-bugreport.sh &> gpm.log to the report? You might also want to take a look to the Debugging instructions located at https://wiki.ubuntu.com/DebuggingGNOMEPowerManager for submit any other logs related to your problem.Thanks in advance.

Okay, gnome-power-bugreport.sh does not exist anywhere on my machine, but I did find /usr/share/gnome-power-manager/gnome-power-bugreport

Attached is the output.

Here's the output of gnome-power-manager --verbose --no-daemon 2>&1 | tee gpm.debug.log.txt during a suspend sequence.

Bypassing GPM via dbus-send --system --print-reply --dest="org.freedesktop.Hal" /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0 was not successful.

ok thanks setting this to confirmed.

When I try to suspend with my T61 running Jaunty updated, I get the following in my pm-suspend.log:

Initial commandline parameters: --quirk-s3-bios
--quirk-s3-mode
Mon Mar 23 18:34:06 EDT 2009: Running hooks for suspend.
/usr/lib/pm-utils/sleep.d/000record suspend suspend: success.
/usr/lib/pm-utils/sleep.d/00auto-quirk suspend suspend: success.
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: Linux Mariner-T61 2.6.28-11
-generic #36-Ubuntu SMP Fri Mar 20 19:40:40 UTC 2009 i686 GNU/Linux
Module Size Used by
i915 65668 2
drm 96424 3 i915
ppdev 15492 0
bridge 56340 0
stp 10500 1 bridge
bnep 20224 2
tun 18820 1
input_polldev 11912 0
iptable_nat 13700 0
nf_nat 25876 1 iptable_nat
ipt_LOG 13700 2
xt_limit 10116 2
ipt_REJECT 11136 1
xt_tcpudp 11008 25
nf_conntrack_ipv4 21388 5 iptable_nat,nf_nat
nf_defrag_ipv4 9984 1 nf_conntrack_ipv4
xt_state 10112 2
iptable_filter 10752 1
ip_tables 19472 2 iptable_nat,iptable_filter
x_tables 23044 7 iptable_nat,ipt_LOG,xt_limit,ipt_REJECT,xt_tcpud
p,xt_state,ip_tables
binfmt_misc 16776 1
nf_conntrack_ftp 15652 0
nf_conntrack 72008 5 iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state,nf
_conntrack_ftp
lp 17156 0
parport 42220 2 ppdev,lp
joydev 18368 0
snd_hda_intel 435508 2
snd_pcm_oss 46336 0
snd_mixer_oss 22656 1 snd_pcm_oss
snd_pcm 82820 2 snd_hda_intel,snd_pcm_oss
arc4 9856 2
snd_seq_dummy 10756 0
snd_seq_oss 37760 0
snd_seq_midi 14336 0
ecb 10752 2
snd_rawmidi 29696 1 snd_seq_midi
snd_seq_midi_event 15104 2 snd_seq_oss,snd_seq_midi
pcmcia 44748 0
snd_seq 56880 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_m
idi_event
iwlagn 102660 0
snd_timer 29704 2 snd_pcm,snd_seq
snd_seq_device 14988 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmi
di,snd_seq
psmouse 61972 0
iwlcore 112128 1 iwlagn
lbm_cw_mac80211 224804 2 iwlagn,iwlcore
thinkpad_acpi 66432 0
yenta_socket 32396 1
rsrc_nonstatic 19328 1 yenta_socket
video 25360 0
intel_agp 34108 1
serio_raw 13316 0
pcspkr 10496 0
snd 62628 13 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm
,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
ricoh_mmc 11904 0
sdhci_pci 15232 0
sdhci 23940 1 sdhci_pci
led_class 12036 2 iwlcore,thinkpad_acpi
nvram 16396 1 thinkpad_acpi
pcmcia_core 43540 3 pcmcia,yenta_socket,rsrc_nonstatic
output 11008 1 video
iTCO_wdt 19108 0
iTCO...

I started poking around pm-suspend.log on my system and pulseaudio was not the cause of the problem. There was, however, a script left over from when I ran madwifi drivers that was causing a problem. Removing the script fixed suspend for me.

I found that if I killed PulseAudio, I could suspend. Something about how
the script works is not stopping PulseAudio properly...

Shannon

On Mon, Mar 23, 2009 at 8:22 PM, onyxrev <email address hidden> wrote:

> I started poking around pm-suspend.log on my system and pulseaudio was
> not the cause of the problem. There was, however, a script left over
> from when I ran madwifi drivers that was causing a problem. Removing
> the script fixed suspend for me.
>
> --
> Suspend fails in Jaunty on Macbook 4,1
> https://bugs.launchpad.net/bugs/344989
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “gnome-power-manager” source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: acpi-support
>
> Just upgraded my Macbook Intrepid install to Jaunty (as of March 18) via
> update-manager -d. Machine would suspend and resume fine in Intrepid but
> now does not appear to initiate suspend at all when requested from the menu.
>
> The sequence of events:
>
> I hit suspend, machine locks screen and dumps to screensaver but does not
> suspend. I wiggle the mouse or hit a key, unlock, and am back at my
> desktop. Network connections have disengaged and reengaged, so it got that
> far.
>
> Can't find anything useful in the logs but if someone would point me in the
> right direction I'll post whatever is requested.
>
> I hadn't yet uninstalled the Intrepid kernel and tried booting then
> suspending from that to no avail.
>

If I kill PulseAudio manually, I can suspend. However, upon resume, I get no Thinkpad key function for suspend/hibernate. I may try a fresh install of the current Jaunty to see if anything gets better...

@onyxrev: This bug report is being closed due to your last comment regarding this being fixed by removing an old madwifi script. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

@Mariner09: If your problem exists in Jaunty (or the development version of Karmic), I suggest opening a new bug report and following the directions at: https://wiki.ubuntu.com/DebuggingGNOMEPowerManager, since your problem and onyxrev's appear to be different.