Computer won't suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
HW configuration:
Asus A8N-SLI Deluxe
Athlon X2 3800+ @2GHz
2GB DDR 400 RAM
120 GB Seagate SATA disk
ATAPI DVD-RW
NVidia 6600 GT
Running Ubuntu 9.04 RC
uname -a:
Linux velis-linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux
cat /proc/version_
Ubuntu 2.6.28-
Clean install on 2GB swap (sda1) + 120GB XFS (sda2)
Computer won't enter suspend mode.
These are the last lines of syslog (suspect ipv6 has something to do with this):
Apr 24 17:52:39 velis-linux NetworkManager: <info> Sleeping...
Apr 24 17:52:39 velis-linux NetworkManager: <info> (eth1): now unmanaged
Apr 24 17:52:39 velis-linux NetworkManager: <info> (eth1): device state change: 8 -> 1
Apr 24 17:52:39 velis-linux NetworkManager: <info> (eth1): deactivating device (reason: 37).
Apr 24 17:52:39 velis-linux NetworkManager: <info> eth1: canceled DHCP transaction, dhcp client pid 2976
Apr 24 17:52:39 velis-linux NetworkManager: <WARN> check_one_route(): (eth1) error -34 returned from rtnl_route_del(): Sucess
Apr 24 17:52:39 velis-linux NetworkManager: <info> (eth1): cleaning up...
Apr 24 17:52:39 velis-linux NetworkManager: <info> (eth1): taking down device.
Apr 24 17:52:39 velis-linux avahi-daemon[2694]: Withdrawing address record for 192.168.254.145 on eth1.
Apr 24 17:52:39 velis-linux avahi-daemon[2694]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.254.145.
Apr 24 17:52:39 velis-linux NetworkManager: <info> (eth0): now unmanaged
Apr 24 17:52:39 velis-linux NetworkManager: <info> (eth0): device state change: 2 -> 1
Apr 24 17:52:39 velis-linux NetworkManager: <info> (eth0): cleaning up...
Apr 24 17:52:39 velis-linux NetworkManager: <info> (eth0): taking down device.
Apr 24 17:52:39 velis-linux NetworkManager: <info> (eth1): carrier now OFF (device state 1)
Apr 24 17:52:39 velis-linux kernel: [ 1040.608060] skge eth0: disabling interface
Apr 24 17:52:39 velis-linux avahi-daemon[2694]: Interface eth1.IPv4 no longer relevant for mDNS.
Apr 24 17:52:39 velis-linux avahi-daemon[2694]: Withdrawing address record for fe80::211:
Apr 24 17:53:47 velis-linux syslogd 1.5.0#5ubuntu3: restart.
Any further information required I will happily provide.
Thanks,
Jure
ProblemType: Bug
Architecture: i386
CurrentDmesg:
[ 21.841588] skge eth0: enabling interface
[ 21.844845] ADDRCONF(
[ 32.264015] eth1: no IPv6 routers present
[ 82.088040] Clocksource tsc unstable (delta = -251231017 ns)
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: root=UUID=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: linux
Changed in linux (Ubuntu): | |
status: | Incomplete → Invalid |
Hi velis,
This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you run the following command from a Terminal (Applications- >Accessories- >Terminal) . It will automatically gather and attach updated debug information to this report.
apport-collect -p linux 366182
Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. Please let us know your results.
Thanks in advance.
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]