| 2006-03-28 08:39:24 |
Anders H |
bug |
|
|
added bug |
| 2006-04-28 04:42:23 |
Barry deFreese |
linux-source-2.6.15: status |
Unconfirmed |
Needs Info |
|
| 2006-04-28 04:42:23 |
Barry deFreese |
linux-source-2.6.15: statusexplanation |
|
Do you still have this problem with 2.6.15-20 ? Thank you. |
|
| 2007-06-13 16:52:45 |
Brian Murray |
linux-source-2.6.15: assignee |
|
brian-murray |
|
| 2007-06-13 16:52:45 |
Brian Murray |
linux-source-2.6.15: statusexplanation |
Do you still have this problem with 2.6.15-20 ? Thank you. |
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.
4. Please run the command 'sudo dmidecode > dmidecode.log' and attach the resulting file 'dmidecode.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-07-16 16:25:18 |
Brian Murray |
linux-source-2.6.15: status |
Incomplete |
Invalid |
|
| 2007-07-16 16:25:18 |
Brian Murray |
linux-source-2.6.15: 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.
4. Please run the command 'sudo dmidecode > dmidecode.log' and attach the resulting file 'dmidecode.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! |
We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future. |
|
| 2012-05-29 14:40:38 |
Curtis Hovey |
removed subscriber Registry Administrators |
|
|
|
