Bug #99675 “System incredibly slow after suspend, refuses to res...” : Bugs : gnome-power-manager package : Ubuntu

Revision history for this message

Dennis Dirdjaja (dcd-ditsch) wrote on 2007-05-20: Re: [Bug 99675] System incredibly slow after suspend, refuses to restart

#1

Download full text (13.9 KiB)

I attached syslog and kern.log when this occurs.

System information: ibook G4, Ubuntu Feisty 7.04 PPC with latest updates

If some more information is needed, please let me know.

May 14 23:28:16 localhost gnome-power-manager: (dennis) Rechner wird in Bereitschaft versetzt da Deckel wurde im Netzbetrieb geschlossen
May 14 23:28:16 localhost NetworkManager: <information>^IGoing to sleep.
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): ted AP.
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): Wireless event: cmd=0x8b06 len=8
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): Wireless event: cmd=0x8b19 len=8
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): Received 253 bytes of scan results (1 BSSes)
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): Scan results: 1
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): Selecting BSS from priority group 0
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): 0: 00:14:bf:a4:ef:e2 ssid='dlan' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): selected based on WPA IE
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Already associated with the selected AP.
May 14 23:28:16 localhost dhclient: receive_packet failed on eth1: Network is down
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Wireless event: cmd=0x8b06 len=8
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Wireless event: cmd=0x8b19 len=8
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Received 253 bytes of scan results (1 BSSes)
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Scan results: 1
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Selecting BSS from priority group 0
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): 0: 00:14:bf:a4:ef:e2 ssid='dlan' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): selected based on WPA IE
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Already associated with the selected AP.
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): CTRL-EVENT-TERMINATING - signal 15 received
May 14 23:28:16 localhost dhclient: There is already a p...

I attached syslog and kern.log when this occurs.

System information: ibook G4, Ubuntu Feisty 7.04 PPC with latest updates

If some more information is needed, please let me know.

May 14 23:28:16 localhost gnome-power-manager: (dennis) Rechner wird in Bereitschaft versetzt da Deckel wurde im Netzbetrieb geschlossen
May 14 23:28:16 localhost NetworkManager: <information>^IGoing to sleep. 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): ted AP. 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): Wireless event: cmd=0x8b06 len=8 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): Wireless event: cmd=0x8b19 len=8 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): Received 253 bytes of scan results (1 BSSes) 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): Scan results: 1 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): Selecting BSS from priority group 0 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710): 0: 00:14:bf:a4:ef:e2 ssid='dlan' wpa_ie_len=26 rsn_ie_len=0 caps=0x11 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(6710):    selected based on WPA IE 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Already associated with the selected AP. 
May 14 23:28:16 localhost dhclient: receive_packet failed on eth1: Network is down
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Wireless event: cmd=0x8b06 len=8 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Wireless event: cmd=0x8b19 len=8 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Received 253 bytes of scan results (1 BSSes) 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Scan results: 1 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Selecting BSS from priority group 0 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): 0: 00:14:bf:a4:ef:e2 ssid='dlan' wpa_ie_len=26 rsn_ie_len=0 caps=0x11 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1):    selected based on WPA IE 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): Already associated with the selected AP. 
May 14 23:28:16 localhost NetworkManager: <information>^Iwpa_supplicant(-1): CTRL-EVENT-TERMINATING - signal 15 received 
May 14 23:28:16 localhost dhclient: There is already a pid file /var/run/dhclient.eth1.pid with pid 6718
May 14 23:28:16 localhost dhclient: killed old client process, removed PID file
May 14 23:28:16 localhost avahi-daemon[4126]: Interface eth1.IPv4 no longer relevant for mDNS.
May 14 23:28:16 localhost avahi-daemon[4126]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.52.101.
May 14 23:28:16 localhost avahi-daemon[4126]: Withdrawing address record for fe80::20a:95ff:fef1:fbd6 on eth1.
May 14 23:28:16 localhost avahi-daemon[4126]: Withdrawing address record for 192.168.52.101 on eth1.
May 14 23:28:17 localhost dhclient: DHCPRELEASE on eth1 to 192.168.52.1 port 67
May 14 23:28:17 localhost dhclient: send_packet: Network is unreachable
May 14 23:28:17 localhost dhclient: send_packet: please consult README file regarding broadcast address.
May 14 23:28:18 localhost kernel: [ 8046.520658]  usbdev4.1_ep81: PM: suspend 0->2, parent 4-0:1.0 already 2
May 14 23:28:18 localhost kernel: [ 8046.520682] hub 4-0:1.0: PM: suspend 2->2, parent usb4 already 2
May 14 23:28:18 localhost kernel: [ 8046.520692]  usbdev4.1_ep00: PM: suspend 0->2, parent usb4 already 2
May 14 23:28:18 localhost kernel: [ 8046.520703]  usbdev3.1_ep81: PM: suspend 0->2, parent 3-0:1.0 already 2
May 14 23:28:18 localhost kernel: [ 8046.520713] hub 3-0:1.0: PM: suspend 2->2, parent usb3 already 2
May 14 23:28:18 localhost kernel: [ 8046.520723]  usbdev3.1_ep00: PM: suspend 0->2, parent usb3 already 2
May 14 23:28:18 localhost kernel: [ 8046.520750]  usbdev1.1_ep81: PM: suspend 0->2, parent 1-0:1.0 already 2
May 14 23:28:18 localhost kernel: [ 8046.520760] hub 1-0:1.0: PM: suspend 2->2, parent usb1 already 2
May 14 23:28:18 localhost kernel: [ 8046.520769]  usbdev1.1_ep00: PM: suspend 0->2, parent usb1 already 2
May 14 23:28:19 localhost kernel: [ 8047.756334] eth0: suspending, WakeOnLan disabled
May 14 23:28:19 localhost kernel: [ 8047.784887] ohci1394 does not fully support suspend and resume yet
May 14 23:28:19 localhost kernel: [ 8047.784909] ieee1394: hpsb_bus_reset called while bus reset already in progress
May 14 23:28:19 localhost kernel: [ 8047.868679] radeonfb (0000:00:10.0): suspending for event: 2...
May 14 23:28:23 localhost kernel: [ 8047.868974] uninorth-agp: disabling AGP on device 0000:00:10.0
May 14 23:28:23 localhost kernel: [ 8047.868994] uninorth-agp: disabling AGP on bridge 0000:00:0b.0
May 14 23:28:23 localhost kernel: [ 8048.362742] radeonfb (0000:00:10.0): resuming from state: 2...
May 14 23:28:23 localhost kernel: [ 8049.035467] agpgart: Putting AGP V2 device at 0000:00:0b.0 into 1x mode
May 14 23:28:23 localhost kernel: [ 8049.035488] agpgart: Putting AGP V2 device at 0000:00:10.0 into 1x mode
May 14 23:28:23 localhost kernel: [ 8049.284667] PCI: Enabling device 0001:10:12.0 (0000 -> 0002)
May 14 23:28:23 localhost kernel: [ 8049.284695] PM: Writing back config space on device 0001:10:12.0 at offset f (was 100, writing 134)
May 14 23:28:23 localhost kernel: [ 8049.284721] PM: Writing back config space on device 0001:10:12.0 at offset 4 (was 0, writing 80084000)
May 14 23:28:23 localhost kernel: [ 8049.284734] PM: Writing back config space on device 0001:10:12.0 at offset 3 (was 0, writing 1000)
May 14 23:28:23 localhost kernel: [ 8049.284749] PM: Writing back config space on device 0001:10:12.0 at offset 1 (was 100002, writing 100006)
May 14 23:28:23 localhost kernel: [ 8049.304651] PCI: Enabling device 0001:10:1b.0 (0000 -> 0002)
May 14 23:28:23 localhost kernel: [ 8049.320651] PCI: Enabling device 0001:10:1b.1 (0000 -> 0002)
May 14 23:28:23 localhost kernel: [ 8049.336653] PCI: Enabling device 0001:10:1b.2 (0000 -> 0002)
May 14 23:28:23 localhost kernel: [ 8049.336692] PM: Writing back config space on device 0001:10:1b.2 at offset 1 (was 2100006, writing 2100016)
May 14 23:28:23 localhost kernel: [ 8050.423485] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[40]  MMIO=[f5000000-f50007ff]  Max Packet=[2048]  IR/IT contexts=[8/8]
May 14 23:28:23 localhost kernel: [ 8050.427883] eth0: resuming
May 14 23:28:23 localhost kernel: [ 8050.492997] PHY ID: 4061e4, addr: 0
May 14 23:28:23 localhost kernel: [ 8051.516415] hda: Enabling Ultra DMA 5
May 14 23:28:23 localhost kernel: [ 8051.520629] hdc: Enabling MultiWord DMA 2
May 14 23:28:23 localhost kernel: [ 8051.521932]  usbdev3.1_ep00: PM: resume from 0, parent usb3 still 2
May 14 23:28:23 localhost kernel: [ 8051.522218]  usbdev3.1_ep81: PM: resume from 0, parent 3-0:1.0 still 2
May 14 23:28:23 localhost kernel: [ 8051.800306] Machine check in kernel mode.
May 14 23:28:23 localhost kernel: [ 8051.800327] Caused by (from SRR1=149030): Transfer error ack signal
May 14 23:28:23 localhost kernel: [ 8051.801671] Oops: Machine check, sig: 7 [#1]
May 14 23:28:23 localhost kernel: [ 8051.801687] 
May 14 23:28:23 localhost kernel: [ 8051.801691] Modules linked in: michael_mic arc4 ecb blkcipher ieee80211_crypt_tkip af_packet ipv6 binfmt_misc rfcomm l2cap bluetooth uinput ppdev lp parport radeon drm cpufreq_stats cpufreq_ondemand cpufreq_conservative cpufreq_userspace cpufreq_powersave therm_adt746x sbp2 scsi_mod apm_emu snd_powermac fuse snd_aoa_i2sbus snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_aoa_soundbus pmac_zilog serial_core bcm43xx ieee80211softmac ieee80211 ieee80211_crypt uninorth_agp agpgart evdev tsdev ext3 jbd mbcache usbhid hid ide_cd cdrom ide_disk sungem sungem_phy ohci1394 ieee1394 ehci_hcd ohci_hcd usbcore capability commoncap
May 14 23:28:23 localhost kernel: [ 8051.801850] NIP: C0016644 LR: EA456984 CTR: C001663C
May 14 23:28:23 localhost kernel: [ 8051.801861] REGS: e551bc60 TRAP: 0200   Not tainted  (2.6.20-15-powerpc)
May 14 23:28:23 localhost kernel: [ 8051.801869] MSR: 00149030 <EE,ME,IR,DR>  CR: 44004482  XER: 20000000
May 14 23:28:23 localhost kernel: [ 8051.801889] TASK = c1e0c680[8739] 'ifconfig' THREAD: e551a000
May 14 23:28:23 localhost kernel: [ 8051.801896] GPR00: 000000B4 E551BD10 C1E0C680 00006498 EA1BC120 C0350000 C03544D0 00000000 
May 14 23:28:23 localhost kernel: [ 8051.801916] GPR08: DC4BDE84 8DF8D026 177AC7EB C001663C 24004488 100189FC 100B0000 00000000 
May 14 23:28:23 localhost kernel: [ 8051.801937] GPR16: 100F96E8 100E0000 100B0000 100E0000 DC705EEC FFFFFC18 E6E32ED8 00000001 
May 14 23:28:23 localhost kernel: [ 8051.801958] GPR24: E6E32ED8 E6E32ED8 E551BD18 E6E32ED8 EA1B3000 E6E32D6C 00000148 00000000 
May 14 23:28:23 localhost kernel: [ 8051.801979] NIP [C0016644] ioread32+0x8/0x14
May 14 23:28:23 localhost kernel: [ 8051.802003] LR [EA456984] bcm43xx_wireless_core_init+0x1fc/0xe8c [bcm43xx]
May 14 23:28:23 localhost kernel: [ 8051.802059] Call Trace:
May 14 23:28:23 localhost kernel: [ 8051.802065] [E551BD10] [EA45737C] bcm43xx_wireless_core_init+0xbf4/0xe8c [bcm43xx] (unreliable)
May 14 23:28:23 localhost kernel: [ 8051.802091] [E551BD60] [EA458B0C] wireless_core_up+0x48/0x11c [bcm43xx]
May 14 23:28:23 localhost kernel: [ 8051.802115] [E551BD80] [EA458E44] bcm43xx_select_wireless_core+0x264/0x45c [bcm43xx]
May 14 23:28:23 localhost kernel: [ 8051.802139] [E551BDD0] [EA45917C] bcm43xx_init_board+0xa4/0x144 [bcm43xx]
May 14 23:28:23 localhost kernel: [ 8051.802163] [E551BDF0] [C01D98F4] dev_open+0x78/0xcc
May 14 23:28:23 localhost kernel: [ 8051.802178] [E551BE10] [C01D77EC] dev_change_flags+0x13c/0x168
May 14 23:28:23 localhost kernel: [ 8051.802203] [E551BE30] [C02260B0] devinet_ioctl+0x5bc/0x71c
May 14 23:28:23 localhost kernel: [ 8051.802227] [E551BEA0] [C0226768] inet_ioctl+0xb0/0xdc
May 14 23:28:23 localhost kernel: [ 8051.802241] [E551BEB0] [C01CB080] sock_ioctl+0xd8/0x278
May 14 23:28:23 localhost kernel: [ 8051.802254] [E551BED0] [C0097624] do_ioctl+0x38/0x84
May 14 23:28:23 localhost kernel: [ 8051.802273] [E551BEE0] [C00976F4] vfs_ioctl+0x84/0x3f4
May 14 23:28:23 localhost kernel: [ 8051.802286] [E551BF10] [C0097AF4] sys_ioctl+0x90/0xa0
May 14 23:28:23 localhost kernel: [ 8051.802299] [E551BF40] [C00134F0] ret_from_syscall+0x0/0x38
May 14 23:28:23 localhost kernel: [ 8051.802320] --- Exception: c01 at 0xff6f2a8
May 14 23:28:23 localhost kernel: [ 8051.802335]     LR = 0xff6f240
May 14 23:28:23 localhost kernel: [ 8051.802341] Instruction dump:
May 14 23:28:23 localhost kernel: [ 8051.802348] 0c030000 4c00012c 5463043e 4e800020 7c0004ac a0630000 0c030000 4c00012c 
May 14 23:28:23 localhost kernel: [ 8051.802368] 5463043e 4e800020 7c0004ac 7c601c2c <0c030000> 4c00012c 4e800020 7c0004ac 
May 15 08:09:40 localhost kernel: [ 8051.802390]  <6>agpgart: Putting AGP V2 device at 0000:00:0b.0 into 1x mode
May 15 08:09:40 localhost kernel: [ 8052.143322] agpgart: Putting AGP V2 device at 0000:00:10.0 into 1x mode
May 15 08:09:40 localhost kernel: [ 8052.143402] [drm] Loading R200 Microcode
May 15 08:09:40 localhost kernel: [ 8052.200447] adb: starting probe task...
May 15 08:09:40 localhost gnome-power-manager: (dennis) An unknown error occured code='32' quark='g-exec-error-quark'
May 15 08:09:40 localhost kernel: [ 8052.458245] adb devices: [2]: 2 c4 [3]: 3 1 [7]: 7 1f
May 15 08:09:40 localhost kernel: [ 8052.465897] ADB keyboard at 2, handler 1
May 15 08:09:40 localhost kernel: [ 8052.481214] ADB mouse at 3, handler set to 4 (trackpad)
May 15 08:09:40 localhost kernel: [ 8052.540222] adb: finished probe task...
May 15 08:09:41 localhost gnome-power-manager: (dennis) Rechner wird aufgeweckt
May 15 08:09:41 localhost gnome-power-manager: (dennis) suspend failed
May 15 08:09:41 localhost NetworkManager: <information>^IWaking up from sleep. 
May 15 08:09:41 localhost NetworkManager: <information>^IDeactivating device eth1. 
May 15 08:10:00 localhost dhcdbd: dhco_input_option: Value -1 cannot be converted to type L 
May 15 08:10:00 localhost dhcdbd: dhco_parse_option_settings: bad option setting: old_dhcp_lease_time = -1 
May 15 08:10:54 localhost gconfd (dennis-4685): Beenden
May 15 08:10:54 localhost gdm[4271]: Master wird angehalten...
May 15 08:10:56 localhost init: tty4 main process (3873) killed by TERM signal
May 15 08:10:56 localhost init: tty5 main process (3874) killed by TERM signal
May 15 08:10:56 localhost init: tty2 main process (3876) killed by TERM signal
May 15 08:10:56 localhost init: tty3 main process (3877) killed by TERM signal
May 15 08:10:56 localhost init: tty1 main process (3878) killed by TERM signal
May 15 08:10:56 localhost init: tty6 main process (3881) killed by TERM signal
May 15 08:11:02 localhost avahi-daemon[4126]: Got SIGTERM, quitting.
May 15 08:11:02 localhost NetworkManager: <WARNING>^I nm_signal_handler (): Caught signal 15, shutting down normally. 
May 15 08:12:02 localhost hcid[4473]: Got disconnected from the system message bus
May 15 08:12:02 localhost mouseemu[4424]: mouseemu: cleaning... 
May 15 08:12:07 localhost hcid[4473]: Can't connect to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
May 15 08:12:08 localhost exiting on signal 15

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2007-08-09:

#2

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Also the issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at [WWW] http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Changed in gnome-power-manager:
status:	New → Incomplete

Revision history for this message

Dennis Dirdjaja (dcd-ditsch) wrote on 2007-08-09:

#3

I switched to Gutsy a while ago and just retested it with the current development status. The iBook does not return from suspend completely, i.e. the display isn't powered on again (and it is a bit difficult to work without display). Also, there are no return messages in syslog so I can't tell what is failing.

Pedro Villavicencio (pedro) on 2007-09-03

Changed in gnome-power-manager:
status:	Incomplete → New

Revision history for this message

pmatthew (matteo-pillon-deactivatedaccount) wrote on 2007-10-08:

#4

I can confirm the bug with Gutsy... No resume after suspending the ibook.

Revision history for this message

Matthias Jordan (matthiasjordan) wrote on 2007-11-17:

#5

I, too, can confirm this bug on a 1,3 GHz G4 iBook with the Gutsy Gibbon inside. The machine goes to sleep (heartbeat LED pulses, backlight is off, everything comes to a halt) when closing the lid. When opening the lid, subsystems audibly restart but the screen remains powered on in a strange configuration (horizontal black and white stripes). Incidentally (or not) a friend of mine has the same problem on his machine.

Revision history for this message

Graham Dumas (graham-dumas) wrote on 2007-11-19:

#6

I'm also having the identical issue running Gutsy Gibbon on my G3 iBook: upon waking from sleep the system starts up, but the display looks like there's a problem with the logic board (horizontal stripes). Mine are green, black and white, but I'm sure the issue is the same. Sounds like this is a fairly widespread problem.

Revision history for this message

Basilio Kublik (sourcercito) wrote on 2008-02-21:

#7

Hi there
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you?, Can you try with latest Ubuntu release?, Can you please try with the live environment of the Desktop CD of the development release - Hardy Heron?

Thanks in advance.

Changed in gnome-power-manager:
assignee:	nobody → sourcercito
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

Dennis Dirdjaja (dcd-ditsch) wrote on 2008-02-21:

#8

I am running a Debian command line system on it at the moment but I can test it this weekend. Stay tuned...

Revision history for this message

zmoog (zmoog) wrote on 2008-02-22: Re: [Bug 99675] Re: System incredibly slow after suspend, refuses to restart

#9

On Thu, Feb 21, 2008 at 4:02 PM, Basilio Kublik <email address hidden> wrote:
> Hi there
> Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you?, Can you try with latest Ubuntu release?, Can you please try with the live environment of the Desktop CD of the development release - Hardy Heron?

Hi all,

this bug is still an issue, al least for me. I'm still using the
feisty fawn at the moment, because it's the most stable ubuntu I can
run..

I'll download the latest develompent release now and report the results here..

See you soon!

zmoog
--
Free Software, Free Society.
(and notav, plz)

Revision history for this message

Basilio Kublik (sourcercito) wrote on 2008-02-22:

#10

Thank you guys for the feedback, in the mean time you can take a look at https://wiki.ubuntu.com/DebuggingGNOMEPowerManager and follow the instructions to obtain the debugging information so you can include in this report as separated attachments.

Thanks again.

Revision history for this message

Dennis Dirdjaja (dcd-ditsch) wrote on 2008-02-23:

#11

gpm.txt Edit (2.4 KiB, text/plain)

No luck for me, Suspend does not appear as an option in the live session (daily live from 20080223), so I installed it. Suspend does still not appear. Information from the bugreport script attached.

I also tried to invoke the dbus-send thing (although it seems useless if suspend capatibility seems to be not recognized by gpm):

dennis@ibook:~$ dbus-send --system --print-reply --dest="org.freedesktop.Hal" /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0
method return sender=:1.5 -> dest=:1.224 reply_serial=2
int32 1
dennis@ibook:~$

If there is anything more to test/provide information, please let me know.

Basilio Kublik (sourcercito) on 2008-04-14

Changed in gnome-power-manager:
assignee:	sourcercito → nobody

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-08-22:

#12

Closing this report, Basilio asked for reproduction on Hardy or Intrepid no Feisty, feel free to re open it or report a new one if you can do it with either of those releases.

Changed in gnome-power-manager:
status:	Incomplete → Invalid

Revision history for this message

Dennis Dirdjaja (dcd-ditsch) wrote on 2008-08-22:

#13

Pedro, the latest debug log I attached was from a Hardy installation as can easily be seen in the first lines of the text file attached. But nevermind, as soon as there are working installation CDs for Intrepid, I will retest with Intrepid (again).

Revision history for this message

xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob) wrote on 2011-06-24:

#14

This bug seems to be back in latest Ubuntu updates.

Revision history for this message

Jason Smith (sddfdds) wrote on 2011-10-01:

#15

Im getting this in natty too, or something similar. Suspend/resume work fine and are fast, but after resuming, hard drive access speed is limited to ~4MB/s. USB hard drives plugged into the system are not affected though. It's not quite unusable, but extremely frustrating when doing anything with the hard drive.

Ubuntu
gnome-power-manager package

System incredibly slow after suspend, refuses to restart

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntugnome-power-manager package

System incredibly slow after suspend, refuses to restart

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
gnome-power-manager package