| 2008-09-07 01:17:05 |
dmoyne |
bug |
|
|
added bug |
| 2008-09-07 20:32:10 |
Jean-Baptiste Lallement |
None: status |
New |
Incomplete |
|
| 2008-09-07 20:32:10 |
Jean-Baptiste Lallement |
None: bugtargetdisplayname |
Ubuntu |
linux (Ubuntu) |
|
| 2008-09-07 20:32:10 |
Jean-Baptiste Lallement |
None: bugtargetname |
ubuntu |
linux (Ubuntu) |
|
| 2008-09-07 20:32:10 |
Jean-Baptiste Lallement |
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-09-07 20:32:10 |
Jean-Baptiste Lallement |
None: title |
Bug #267306 in Ubuntu: "ATA error messages reported in syslog" |
Bug #267306 in linux (Ubuntu): "ATA error messages reported in syslog" |
|
| 2008-09-08 08:48:10 |
dmoyne |
bug |
|
|
added attachment 'dmesg.log' (file dmesg.log) |
| 2008-09-08 08:51:00 |
dmoyne |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci-vvnn.log) |
| 2008-09-09 15:38:30 |
dmoyne |
bug |
|
|
added attachment 'dmesg.log' (log just after booting+opening konsole to run dmesg > ~/tmp/dmesg.log) |
| 2008-09-10 17:47:19 |
Jean-Baptiste Lallement |
linux: status |
Incomplete |
Invalid |
|
| 2008-09-10 17:47:19 |
Jean-Baptiste Lallement |
linux: 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! |
Thanks for the update. I'm closing this report due to your last comment regarding this being caused by a faulty hardware.
Don't hesitate to submit any new bug. |
|
