| 2008-08-27 01:54:35 |
Nelson Villoria |
bug |
|
|
added bug |
| 2008-08-27 01:54:35 |
Nelson Villoria |
bug |
|
|
added attachment 'bugreportusb.txt' (bugreportusb.txt) |
| 2008-08-29 07:58:07 |
James Collier |
None: status |
New |
Incomplete |
|
| 2008-08-29 07:58:07 |
James Collier |
None: bugtargetdisplayname |
Ubuntu |
linux (Ubuntu) |
|
| 2008-08-29 07:58:07 |
James Collier |
None: bugtargetname |
ubuntu |
linux (Ubuntu) |
|
| 2008-08-29 07:58:07 |
James Collier |
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-08-29 07:58:07 |
James Collier |
None: title |
Bug #261710 in Ubuntu: "Corsair Flash Voyager 8GB USB key causes device descriptor read/64, error -110 " |
Bug #261710 in linux (Ubuntu): "Corsair Flash Voyager 8GB USB key causes device descriptor read/64, error -110 " |
|
| 2008-09-13 18:46:28 |
jcasanov |
bug |
|
|
added attachment 'report.tar.gz' (report.tar.gz) |
| 2008-09-17 18:01:04 |
Jorge Castro |
bug |
|
|
assigned to linux |
| 2008-09-17 18:01:29 |
Jorge Castro |
linux: status |
Incomplete |
Confirmed |
|
| 2008-09-17 18:01:29 |
Jorge Castro |
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! |
|
|
| 2008-09-18 00:17:34 |
Bug Watch Updater |
linux: status |
Unknown |
Fix Released |
|
| 2008-09-18 23:39:12 |
Nelson Villoria |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
| 2008-09-18 23:39:12 |
Nelson Villoria |
bug |
|
|
added attachment 'lspci-vvnn,log' (lspci-vvnn,log) |
| 2009-05-23 20:19:04 |
Jordi Ferran |
removed subscriber Jordi Ferran |
|
|
|
| 2009-09-03 09:32:02 |
Allochtoon |
removed subscriber Allochtoon |
|
|
|
| 2011-02-03 17:22:21 |
Bug Watch Updater |
linux: importance |
Unknown |
Medium |
|
| 2012-08-04 03:32:39 |
penalvch |
tags |
|
dapper hardy needs-kernel-logs needs-upstream-testing |
|
| 2012-08-04 03:34:50 |
penalvch |
linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2012-08-04 03:34:50 |
penalvch |
linux (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2012-08-04 03:35:22 |
penalvch |
attachment removed |
report.tar.gz https://bugs.launchpad.net/ubuntu/+source/linux/+bug/261710/+attachment/350117/+files/report.tar.gz |
|
|
| 2019-10-03 09:21:54 |
Po-Hsu Lin |
linux (Ubuntu): status |
Incomplete |
Won't Fix |
|
