| 2008-10-20 00:09:50 |
anagor |
bug |
|
|
added bug |
| 2008-10-20 00:09:50 |
anagor |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
| 2008-10-22 23:35:26 |
Leann Ogasawara |
linux: status |
New |
Incomplete |
|
| 2008-10-22 23:35:26 |
Leann Ogasawara |
linux: statusexplanation |
|
Hi anagor,
Which specific 2.6.27-6 kernel version was working and which specific 2.6.27-7 kernel this began failing. For example was it working in say 2.6.27-6.9 and began failing with say 2.6.27-7.10 ? You can find this specific version by doing 'cat /proc/version_signature' . That can at least help narrow down where a patch may have been introduced that causes this regression. The changelog can be seen at:
https://edge.launchpad.net/ubuntu/+source/linux/
It's likely the best solution would be to do a git bisect to narrow down the offending patch. Would you be comfortable doing a git bisect - http://www.kernel.org/doc/local/git-quick.html#bisect . I've previously tried to outline performing a git bisect on an Ubuntu kernel in another bug report - https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/273266/comments/6 so that may help. Let me know if you have any questions. Thanks. |
|
| 2008-10-23 22:29:38 |
Leann Ogasawara |
bug |
|
|
added attachment 'linux-image-2.6.27-7-generic_2.6.27-7.14_i386.deb' (linux-image-2.6.27-7-generic_2.6.27-7.14_i386.deb) |
| 2008-10-24 18:31:02 |
Leann Ogasawara |
bug |
|
|
added attachment '286169.patch' (286169.patch) |
| 2008-10-27 18:00:19 |
Leann Ogasawara |
linux: status |
Incomplete |
Triaged |
|
| 2008-10-27 18:00:19 |
Leann Ogasawara |
linux: assignee |
|
ubuntu-kernel-team |
|
| 2008-10-27 18:00:19 |
Leann Ogasawara |
linux: importance |
Undecided |
High |
|
| 2008-10-27 18:00:19 |
Leann Ogasawara |
linux: statusexplanation |
Hi anagor,
Which specific 2.6.27-6 kernel version was working and which specific 2.6.27-7 kernel this began failing. For example was it working in say 2.6.27-6.9 and began failing with say 2.6.27-7.10 ? You can find this specific version by doing 'cat /proc/version_signature' . That can at least help narrow down where a patch may have been introduced that causes this regression. The changelog can be seen at:
https://edge.launchpad.net/ubuntu/+source/linux/
It's likely the best solution would be to do a git bisect to narrow down the offending patch. Would you be comfortable doing a git bisect - http://www.kernel.org/doc/local/git-quick.html#bisect . I've previously tried to outline performing a git bisect on an Ubuntu kernel in another bug report - https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/273266/comments/6 so that may help. Let me know if you have any questions. Thanks. |
Thanks anagor. So the patch in question was actually cherrypicked form the upstream kernel. But I'll notify the kernel team of the regression it introduced. However, I'm curious if you'd be willing to test the upstream vanilla kernel as well to verify if this issue exists upstream as well and if reverting the patch resolves the issue. Information on how to build the upstream kernel from git can be found at https://wiki.ubuntu.com/KernelTeam/GitKernelBuild . Thanks. |
|
| 2008-10-28 12:45:41 |
anagor |
bug |
|
|
added attachment 'dmesg.log' (dmesg for vanilla 2.6.28-rc2 kernel.) |
| 2008-10-29 05:08:29 |
Leann Ogasawara |
linux: statusexplanation |
Thanks anagor. So the patch in question was actually cherrypicked form the upstream kernel. But I'll notify the kernel team of the regression it introduced. However, I'm curious if you'd be willing to test the upstream vanilla kernel as well to verify if this issue exists upstream as well and if reverting the patch resolves the issue. Information on how to build the upstream kernel from git can be found at https://wiki.ubuntu.com/KernelTeam/GitKernelBuild . Thanks. |
|
|
| 2008-10-29 05:08:29 |
Leann Ogasawara |
linux: milestone |
|
intrepid-updates |
|
| 2008-10-30 16:57:32 |
Leann Ogasawara |
bug |
|
|
assigned to linux |
| 2008-10-30 22:11:13 |
Bug Watch Updater |
linux: status |
Unknown |
In Progress |
|
| 2008-11-12 18:55:49 |
Bug Watch Updater |
linux: status |
In Progress |
Fix Released |
|
| 2008-11-26 08:50:37 |
Andy Whitcroft |
linux: status |
Triaged |
Fix Committed |
|
| 2008-11-26 08:50:37 |
Andy Whitcroft |
linux: assignee |
ubuntu-kernel-team |
apw |
|
| 2008-11-26 08:50:37 |
Andy Whitcroft |
linux: statusexplanation |
|
@anagor -- thanks for the heads up. I have read through the upstream bug, good work there with those guys to find and fix this one. I have checked our 2.6.27-10.20 release and it does indeed contain the upstream fix from upstream. That came through as part of the 2.6.27.7 stable updates.
Moving this Fix Committed as this is in -proposed. |
|
| 2009-04-21 19:08:30 |
Leann Ogasawara |
linux (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2011-02-04 10:26:58 |
Bug Watch Updater |
linux: importance |
Unknown |
Medium |
|
