| 2008-11-12 13:52:32 |
y-man |
bug |
|
|
added bug |
| 2008-11-12 17:19:14 |
Ian Weisser |
None: status |
New |
Incomplete |
|
| 2008-11-12 17:19:14 |
Ian Weisser |
None: bugtargetdisplayname |
Ubuntu |
linux (Ubuntu) |
|
| 2008-11-12 17:19:14 |
Ian Weisser |
None: bugtargetname |
ubuntu |
linux (Ubuntu) |
|
| 2008-11-12 17:19:14 |
Ian Weisser |
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-11-12 17:19:14 |
Ian Weisser |
None: title |
Bug #297192 in Ubuntu: "Intrepid: disk drive order changes every boot" |
Bug #297192 in linux (Ubuntu): "Intrepid: disk drive order changes every boot" |
|
| 2008-11-14 12:30:41 |
y-man |
bug |
|
|
added attachment 'logs.tar.gz' (logs.tar.gz) |
| 2008-11-14 17:34:32 |
Ian Weisser |
linux: status |
Incomplete |
New |
|
| 2008-11-14 17:34:32 |
Ian Weisser |
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-11-20 23:23:07 |
y-man |
bug |
|
|
added attachment 'logs_PATA_sda.tar.gz' (Logs from a session where PATA is sda, SATA is sdb) |
| 2009-09-02 22:43:39 |
kernel-janitor |
tags |
|
needs-kernel-logs |
|
| 2009-09-02 22:43:43 |
kernel-janitor |
tags |
needs-kernel-logs |
needs-kernel-logs needs-upstream-testing |
|
| 2009-09-02 22:43:44 |
kernel-janitor |
tags |
needs-kernel-logs needs-upstream-testing |
kj-triage needs-kernel-logs needs-upstream-testing |
|
| 2009-09-02 22:43:49 |
kernel-janitor |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2010-03-13 21:07:59 |
Jeremy Foshee |
tags |
kj-triage needs-kernel-logs needs-upstream-testing |
kj-expired kj-triage needs-kernel-logs needs-upstream-testing |
|
| 2010-03-13 21:08:04 |
Jeremy Foshee |
linux (Ubuntu): status |
Incomplete |
Invalid |
|
