| 2008-12-13 22:24:04 |
Stubbs |
bug |
|
|
added bug |
| 2008-12-14 13:05:44 |
goto |
None: status |
New |
Incomplete |
|
| 2008-12-14 13:05:44 |
goto |
None: statusexplanation |
|
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.
Please include the following additional information, if you have not already done so (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" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo 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 https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance! |
|
| 2008-12-14 19:02:02 |
Stubbs |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci-vvnn.log) |
| 2008-12-14 19:02:28 |
Stubbs |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
| 2008-12-14 19:02:59 |
Stubbs |
bug |
|
|
added attachment 'uname -a result' (uname -a result) |
| 2008-12-15 17:24:14 |
goto |
None: status |
Incomplete |
New |
|
| 2008-12-15 17:24:14 |
goto |
None: statusexplanation |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.
Please include the following additional information, if you have not already done so (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" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo 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 https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance! |
|
|
| 2008-12-15 17:25:17 |
goto |
None: assignee |
|
ubuntu-kernel-team |
|
| 2008-12-15 17:25:17 |
goto |
None: bugtargetdisplayname |
Ubuntu |
linux (Ubuntu) |
|
| 2008-12-15 17:25:17 |
goto |
None: bugtargetname |
ubuntu |
linux (Ubuntu) |
|
| 2008-12-15 17:25:17 |
goto |
None: title |
Bug #307780 in Ubuntu: "Suspend/Hibernate Not Working" |
Bug #307780 in linux (Ubuntu): "Suspend/Hibernate Not Working" |
|
| 2009-02-16 06:53:47 |
Leann Ogasawara |
linux: status |
New |
Incomplete |
|
| 2009-02-16 06:53:47 |
Leann Ogasawara |
linux: statusexplanation |
|
Hi Stubbs,
Care to test and confirm if this issue remains with the most recent pre-release of Jaunty 9.04 (currently Alpha4) - http://cdimage.ubuntu.com/releases/jaunty/ . It contains a newer 2.6.28 based kernel. You should be able to test suspend via a LiveCD. Please let us know your results. Thanks. |
|
| 2009-07-07 23:12:37 |
Jeremy Foshee |
linux (Ubuntu): status |
Incomplete |
Invalid |
|
| 2011-10-05 22:17:06 |
Jeremy Foshee |
removed subscriber Jeremy Foshee |
|
|
|
