Activity log for bug #112132

Date Who What changed Old value New value Message
2007-05-03 17:12:47 Serious Sven bug added bug
2007-05-14 21:13:24 Brian Murray None: status Unconfirmed Needs Info
2007-05-14 21:13:24 Brian Murray None: assignee brian-murray
2007-05-14 21:13:24 Brian Murray None: 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 the following additional information as attachments, 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-06-04 17:40:43 outlaw686 bug added attachment 'logs.zip' (logs.zip)
2007-06-11 20:14:30 Brian Murray linux-source-2.6.20: status Needs Info Confirmed
2007-06-11 20:14:30 Brian Murray linux-source-2.6.20: importance Undecided Medium
2007-06-11 20:14:30 Brian Murray linux-source-2.6.20: 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 the following additional information as attachments, 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-06-11 20:14:30 Brian Murray linux-source-2.6.20: assignee brian-murray ubuntu-kernel-team
2007-10-19 23:20:31 Ned bug added attachment 'NED_dmesg_out.txt' (DMESG output corresponding to Ned's post)
2007-11-23 15:24:26 Rob Miracle bug added attachment 'lspci-vvnn.log' (lspci-vvnn.log)
2007-11-23 15:26:28 Rob Miracle bug added attachment 'dmesg.log' (dmesg.log)
2007-11-26 09:36:19 Oleksij Rempel bug assigned to linux
2007-11-26 09:50:17 Bug Watch Updater linux: status Unknown In Progress
2007-12-06 09:45:56 Bug Watch Updater linux: status In Progress Fix Released
2008-08-29 05:31:55 Leann Ogasawara bug added subscriber Leann Ogasawara
2008-09-18 18:16:32 Leann Ogasawara linux: status Incomplete Fix Released
2008-09-18 18:16:32 Leann Ogasawara linux: statusexplanation Setting this to "Fix Released" based on the decision to stick with the 2.6.27 kernel for Intrepid - https://lists.ubuntu.com/archives/kernel-team/2008-September/003107.html
2011-02-03 16:00:03 Bug Watch Updater linux: importance Unknown Medium