Suspend stopped working on Dell Latitude C610 in recent Hardy update

Bug #250533 reported by Michael Losonsky
2
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Suspend used to work in Hardy Heron but after a recent update (
and I cannot remember which one), it stopped working. It will
suspend, but it will not resume. Need to force shutdown and
reboot. Same problem using suspend button, suspend on
close lid, or from log off menu. Hibernate works, and if I set
power manager to hibernate on close lid, this resumes without
a problem.

Kernel: 2.6.24-19-generic
Dell Latitude C610
Relevant segment from sys.log:
Jul 21 07:54:56 philosnb01 gnome-power-manager: (ml) Suspending computer. Reason: The suspend button has been pressed.

Jul 21 07:54:57 philosnb01 kernel: [ 129.469257] gnome-screensav[10531]: segfault at 00000200 eip b7f22bad esp bfb5ef10 error 4

Jul 21 07:54:59 philosnb01 NetworkManager: <info> Going to sleep.

Jul 21 07:54:59 philosnb01 kernel: [ 95.393346] eth1: New link status: Disconnected (0002)

Jul 21 07:54:59 philosnb01 kernel: [ 95.617728] hermes @ 0001e100: Timeout waiting for command 0x0002 completion.
Jul 21 07:54:59 philosnb01 kernel: [ 95.617971] eth1: Unable to disable port while reconfiguring card

Jul 21 07:54:59 philosnb01 kernel: [ 95.617976] eth1: Resetting instead...
Jul 21 07:54:59 philosnb01 dhclient: There is already a pid file /var/run/dhclient.eth1.pid with pid 6789
Jul 21 07:54:59 philosnb01 dhclient: killed old client process, removed PID file
Jul 21 07:54:59 philosnb01 kernel: [ 95.857406] hermes @ 0001e100: Timeout waiting for command 0x0021 completion.
Jul 21 07:54:59 philosnb01 kernel: [ 95.858419] eth1: orinoco_set_multicast_list() called when hw_unavailable
Jul 21 07:54:59 philosnb01 avahi-daemon[4877]: Interface eth1.IPv4 no longer relevant for mDNS.
Jul 21 07:54:59 philosnb01 avahi-daemon[4877]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.0.65.
Jul 21 07:54:59 philosnb01 avahi-daemon[4877]: Withdrawing address record for fe80::202:2dff:fe5d:6f7b on eth1.
Jul 21 07:54:59 philosnb01 avahi-daemon[4877]: Withdrawing address record for 192.168.0.65 on eth1.
Jul 21 07:55:00 philosnb01 dhclient: DHCPRELEASE on eth1 to 192.168.0.1 port 67
Jul 21 07:55:00 philosnb01 dhclient: send_packet: Network is unreachable
Jul 21 07:55:00 philosnb01 dhclient: send_packet: please consult README file regarding broadcast address.
Jul 21 07:55:00 philosnb01 NetworkManager: <debug> [1216648500.291833] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/net_00_06_5b_e2_18_36').
Jul 21 07:55:00 philosnb01 NetworkManager: <info> Deactivating device eth0.
Jul 21 08:00:03 philosnb01 syslogd 1.5.0#1ubuntu1: restart.

attached.

Revision history for this message
Michael Losonsky (michl) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Intrepid Ibex. 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 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
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gnome-power-manager:
status: Incomplete → Invalid
Revision history for this message
Michael Losonsky (michl) wrote :

Intrepid had problems with network cards -- I had to
a mess with one computer and didn't want to
risk it. So Ignored this. And in any case, why
should I try it in Intrepid when I want it to work
in LTS. Suspend still doesn;t work, but I just
don't use it. You just learn to live with the
bugs.

In general, I am ignoring bugs and bug reports because
I haven't found the process very satisfactory. There
are certain applications that are persistently buggy and
the basic treatment of them is denial and workarounds.
Examples are dial-up, sound recorder, and suspend/hibernate

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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