2007-05-16 11:55:30 |
DrCurl |
bug |
|
|
added bug |
2007-05-16 18:52:12 |
Brian Murray |
None: status |
Unconfirmed |
Needs Info |
|
2007-05-16 18:52:12 |
Brian Murray |
None: assignee |
|
brian-murray |
|
2007-05-16 18:52:12 |
Brian Murray |
None: statusexplanation |
|
Thanks for taking the time to report this bug and helping to make Ubuntu better. When you mention suspend are you referring to suspend to RAM or suspend to disk? If it is suspend to disk are certain that you have an active swap partition? You could check using the command 'free' and looking for the line starting with "Swap". Thanks in advance. |
|
2007-06-20 00:45:24 |
Brian Murray |
None: statusexplanation |
Thanks for taking the time to report this bug and helping to make Ubuntu better. When you mention suspend are you referring to suspend to RAM or suspend to disk? If it is suspend to disk are certain that you have an active swap partition? You could check using the command 'free' and looking for the line starting with "Swap". Thanks in advance. |
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments 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 '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! |
|
2007-06-25 19:11:17 |
DrCurl |
bug |
|
|
added attachment 'logs.zip' (logs.zip) |
2007-06-25 19:47:41 |
Brian Murray |
linux-source-2.6.20: status |
Incomplete |
Triaged |
|
2007-06-25 19:47:41 |
Brian Murray |
linux-source-2.6.20: importance |
Undecided |
Medium |
|
2007-06-25 19:47:41 |
Brian Murray |
linux-source-2.6.20: statusexplanation |
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments 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 '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! |
|
|
2007-06-25 19:47:41 |
Brian Murray |
linux-source-2.6.20: assignee |
brian-murray |
ubuntu-kernel-acpi |
|
2008-08-29 06:12:45 |
Leann Ogasawara |
bug |
|
|
added subscriber Leann Ogasawara |
2009-01-10 00:36:30 |
Leann Ogasawara |
linux: status |
Incomplete |
Won't Fix |
|
2009-01-10 00:36:30 |
Leann Ogasawara |
linux: statusexplanation |
|
|
|
2012-04-21 18:51:15 |
Curtis Hovey |
linux-source-2.6.20 (Ubuntu): assignee |
Registry Administrators (registry) |
|
|