Computer won't suspend

Bug #366182 reported by velis
2
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_signature:
Ubuntu 2.6.28-11.42-generic

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:d8ff:fea0:bf83 on eth1.
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(NETDEV_UP): eth0: link is not ready
 [ 32.264015] eth1: no IPv6 routers present
 [ 82.088040] Clocksource tsc unstable (delta = -251231017 ns)
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=5534c747-8dfd-41a1-a352-decf6928a9e3
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
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
ProcCmdLine: root=UUID=ef61b010-6e40-428b-abd2-b8c4986bf98f ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: linux

Revision history for this message
velis (jure-erznoznik-gmail) wrote :
Revision history for this message
velis (jure-erznoznik-gmail) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

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/KernelMainlineBuilds . 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.]

tags: added: kernel-suspend
tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
velis (jure-erznoznik-gmail) wrote :

Dear Jeremy. I no longer have the MB in question nor Ubuntu on the affected computer. Together with some other problems Ubuntu turned out as inappropriate for my usage scenarios.
Therefore I switched to another OS which had fewer issues.
I'm sorry, but I can't help with this issue any more.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.