Broken suspend on 2.6.20-16.29
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Won't Fix
|
High
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Binary package hint: linux-source-2.6.20
I've got continous problems with suspend to both RAM and disk in feisty final on IBM T40 2374-MU7. I installed system as festy alpha 5 (last alpha) where both worked reliably. I upgraded to feisty final pretty late and a trouble begun. Some kernels since then sometime resume flawlessly (unfortunately I don't know, if apt has some packages history), but most times system just hangs in "black screen". I use now linux-image-
$ dmesg |grep -i 'magic\|hash'
[ 2.369427] PID hash table entries: 4096 (order: 12, 16384 bytes)
[ 2.371134] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 2.371824] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 2.493524] Mount-cache hash table entries: 512
[ 2.957476] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 2.957640] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 2.959229] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 2.960344] TCP: Hash tables configured (established 131072 bind 65536)
[ 3.668758] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 4.096020] Magic number: 0:798:917
[ 4.096023] hash matches drivers/
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
Changed in linux-source-2.6.22: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Thank you for your bug report.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http:// wiki.ubuntu. com/KernelTeamB ugPolicies. Thanks in advance!