| 2007-04-05 10:11:39 |
Bogdan Butnaru |
bug |
|
|
added bug |
| 2007-04-05 10:16:44 |
Bogdan Butnaru |
bug |
|
|
added attachment 'syslog' (syslog during network failure) |
| 2007-04-05 23:38:32 |
Brian Murray |
network-manager: status |
Unconfirmed |
Needs Info |
|
| 2007-04-05 23:38:32 |
Brian Murray |
network-manager: assignee |
|
brian-murray |
|
| 2007-04-05 23:38:32 |
Brian Murray |
network-manager: statusexplanation |
|
Thanks for taking the time to report this bug and helping to make Ubuntu better. This seems to be a kernel bug but unfortunately we can't fix it, because your description doesn't yet have enough information.
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 '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-04-06 07:23:42 |
Bogdan Butnaru |
bug |
|
|
added attachment 'dmesg.log' (outpt of "sudo dmesg") |
| 2007-04-06 07:25:40 |
Bogdan Butnaru |
bug |
|
|
added attachment 'lspci-vvnn.log' (outpt of "sudo lspci -vvnn") |
| 2007-04-06 15:06:42 |
Brian Murray |
linux-source-2.6.20: status |
Needs Info |
Confirmed |
|
| 2007-04-06 15:06:42 |
Brian Murray |
linux-source-2.6.20: assignee |
brian-murray |
ubuntu-kernel-team |
|
| 2007-04-06 15:06:42 |
Brian Murray |
linux-source-2.6.20: statusexplanation |
Thanks for taking the time to report this bug and helping to make Ubuntu better. This seems to be a kernel bug but unfortunately we can't fix it, because your description doesn't yet have enough information.
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 '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-04-19 17:58:23 |
Brian Murray |
linux-source-2.6.20: status |
Confirmed |
Fix Released |
|
| 2007-04-19 17:58:23 |
Brian Murray |
linux-source-2.6.20: assignee |
ubuntu-kernel-team |
brian-murray |
|
| 2007-04-19 17:58:23 |
Brian Murray |
linux-source-2.6.20: statusexplanation |
|
This bug report is being closed due to your last comment regarding this being fixed with an update. Thanks again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find. |
|
