Activity log for bug #1041315

Date Who What changed Old value New value Message
2012-08-24 17:48:37 James M. Leddy bug added bug
2012-08-24 18:00:08 Brad Figg linux (Ubuntu): status New Incomplete
2012-08-24 18:08:17 James M. Leddy description Issue Description ----------------- Garbage green lines (4-5 pixel lines) appear on top of some Lenovo laptops' screens, persist from boot splash screen to desktop running. Collected Data -------------- Attached are the kernel dmesg, Xorg.0.log and dump files by intel_reg_dumper for oneiric installation with kernel version 3.0.0-19.33 and 3.0.0-20.34, and for precise installation with kernel version 3.2.0-23.26. Observations ------------ 1. These laptops are pre-installed with Oneiric 2. This issue only happens on Oneiric with kernel version 3.0.0-20.34 and later ones 3. This issue does not happen on Oneiric with kernel version 3.0.0-19.33 and previous ones 4. This issue does not happen on Precise (12.04) with kernel version 3.2.0-23.36 5. This issue is caused by the upstream commit below: f47166d2 drm/i915: Sanitize BIOS debugging bits from PIPECONF The rationale and original bug description for the above commit can be found at https://bugs.freedesktop.org/show_bug.cgi?id=47271 6. This issue would be gone if the above commit is reverted on Oneiric kernel version 3.0.0-19.33 and later ones 7. There is one other commit below which fixed an issue of the above commit in later kernel version, BUT this commit was verified to have nothing to do with the issue here: a9dcf84b drm/i915: don't clobber the pipe param in sanitize_modesetting 8. This issue was reported to be related to BIOS version as well (supposedly) 9. There is a WARN_ON() oops on Oneiric with both kernel versions, but this is supposedly an unrelated seperate issue, as it happens in both cases, but presumably fixed in Precise. 10. By comparing the dump contents between two kernels running on Oneiric, the significant difference is the PIPEACONF register 11. By comparing the dump contents between oneiric and precise, there are many more registers with different values Summary ------- We are able to identify the guilty commit, and are able to provide a workaround by reverting the commit or by doing PIPECONF register change for non-relevant machines. However, we are not able to form a correct theory to explain exactly the above observations and to shape a correct patch to fix the root cause. Issue Description ----------------- Garbage green lines (4-5 pixel lines) appear on top of some Lenovo laptops' screens, persist from boot splash screen to desktop running. Collected Data -------------- Attached are the kernel dmesg, Xorg.0.log and dump files by intel_reg_dumper for oneiric installation with kernel version 3.0.0-19.33 and 3.0.0-20.34, and for precise installation with kernel version 3.2.0-23.26. Observations ------------ 2. This issue only happens on Oneiric with kernel version 3.0.0-20.34 and later ones 3. This issue does not happen on Oneiric with kernel version 3.0.0-19.33 and previous ones 4. This issue does not happen on Precise (12.04) with kernel version 3.2.0-23.36 5. This issue is caused by the upstream commit below:    f47166d2 drm/i915: Sanitize BIOS debugging bits from PIPECONF    The rationale and original bug description for the above commit can be    found at https://bugs.freedesktop.org/show_bug.cgi?id=47271 6. This issue would be gone if the above commit is reverted on Oneiric kernel    version 3.0.0-19.33 and later ones 7. There is one other commit below which fixed an issue of the above commit    in later kernel version, BUT this commit was verified to have nothing to    do with the issue here:    a9dcf84b drm/i915: don't clobber the pipe param in sanitize_modesetting 8. This issue was reported to be related to BIOS version as well (supposedly) 9. There is a WARN_ON() oops on Oneiric with both kernel versions, but this is    supposedly an unrelated seperate issue, as it happens in both cases, but    presumably fixed in Precise. 10. By comparing the dump contents between two kernels running on Oneiric, the     significant difference is the PIPEACONF register 11. By comparing the dump contents between oneiric and precise, there are many     more registers with different values Summary ------- We are able to identify the guilty commit, and are able to provide a workaround by reverting the commit or by doing PIPECONF register change for non-relevant machines. However, we are not able to form a correct theory to explain exactly the above observations and to shape a correct patch to fix the root cause.
2012-08-24 19:30:22 James M. Leddy bug added subscriber Canonical Hardware Enablement Team
2012-08-24 19:30:24 James M. Leddy tags blocks-hwcert-enablement
2012-08-27 15:17:16 Joseph Salisbury linux (Ubuntu): importance Undecided Medium
2012-08-27 15:18:30 Joseph Salisbury linux (Ubuntu): status Incomplete Triaged
2012-08-27 15:18:54 Joseph Salisbury tags blocks-hwcert-enablement blocks-hwcert-enablement oneiric
2012-08-29 18:52:37 James M. Leddy nominated for series Ubuntu Oneiric
2012-08-29 18:52:39 James M. Leddy nominated for series Ubuntu Precise
2012-09-07 12:50:02 James Ferguson description Issue Description ----------------- Garbage green lines (4-5 pixel lines) appear on top of some Lenovo laptops' screens, persist from boot splash screen to desktop running. Collected Data -------------- Attached are the kernel dmesg, Xorg.0.log and dump files by intel_reg_dumper for oneiric installation with kernel version 3.0.0-19.33 and 3.0.0-20.34, and for precise installation with kernel version 3.2.0-23.26. Observations ------------ 2. This issue only happens on Oneiric with kernel version 3.0.0-20.34 and later ones 3. This issue does not happen on Oneiric with kernel version 3.0.0-19.33 and previous ones 4. This issue does not happen on Precise (12.04) with kernel version 3.2.0-23.36 5. This issue is caused by the upstream commit below:    f47166d2 drm/i915: Sanitize BIOS debugging bits from PIPECONF    The rationale and original bug description for the above commit can be    found at https://bugs.freedesktop.org/show_bug.cgi?id=47271 6. This issue would be gone if the above commit is reverted on Oneiric kernel    version 3.0.0-19.33 and later ones 7. There is one other commit below which fixed an issue of the above commit    in later kernel version, BUT this commit was verified to have nothing to    do with the issue here:    a9dcf84b drm/i915: don't clobber the pipe param in sanitize_modesetting 8. This issue was reported to be related to BIOS version as well (supposedly) 9. There is a WARN_ON() oops on Oneiric with both kernel versions, but this is    supposedly an unrelated seperate issue, as it happens in both cases, but    presumably fixed in Precise. 10. By comparing the dump contents between two kernels running on Oneiric, the     significant difference is the PIPEACONF register 11. By comparing the dump contents between oneiric and precise, there are many     more registers with different values Summary ------- We are able to identify the guilty commit, and are able to provide a workaround by reverting the commit or by doing PIPECONF register change for non-relevant machines. However, we are not able to form a correct theory to explain exactly the above observations and to shape a correct patch to fix the root cause. Issue Description ----------------- Garbage green lines (4-5 pixel lines) appear on top of some Lenovo laptops' screens, persist from boot splash screen to desktop running. Collected Data -------------- Attached are the kernel dmesg, Xorg.0.log and dump files by intel_reg_dumper for oneiric installation with kernel version 3.0.0-19.33 and 3.0.0-20.34, and for precise installation with kernel version 3.2.0-23.26. Observations ------------ 2. This issue only happens on Oneiric with kernel version 3.0.0-20.34 and later ones 3. This issue does not happen on Oneiric with kernel version 3.0.0-19.33 and previous ones 4. This issue does not happen on Precise (12.04) with kernel version 3.2.0-23.36 5. This issue is caused by the upstream commit below:    f47166d2 drm/i915: Sanitize BIOS debugging bits from PIPECONF    The rationale and original bug description for the above commit can be    found at https://bugs.freedesktop.org/show_bug.cgi?id=47271 6. This issue would be gone if the above commit is reverted on Oneiric kernel    version 3.0.0-19.33 and later ones 7. There is one other commit below which fixed an issue of the above commit    in later kernel version, BUT this commit was verified to have nothing to    do with the issue here:    a9dcf84b drm/i915: don't clobber the pipe param in sanitize_modesetting 8. This issue was reported to be related to BIOS version as well (see comment #3) 9. There is a WARN_ON() oops on Oneiric with both kernel versions, but this is    supposedly an unrelated seperate issue, as it happens in both cases, but    presumably fixed in Precise. 10. By comparing the dump contents between two kernels running on Oneiric, the     significant difference is the PIPEACONF register 11. By comparing the dump contents between oneiric and precise, there are many     more registers with different values Summary ------- We are able to identify the guilty commit, and are able to provide a workaround by reverting the commit or by doing PIPECONF register change for non-relevant machines. However, we are not able to form a correct theory to explain exactly the above observations and to shape a correct patch to fix the root cause.
2012-10-18 03:49:27 Jamie Chang bug task added oem-priority
2012-10-18 03:50:12 Jamie Chang bug added subscriber OEM Priority Team
2012-10-18 03:50:32 Jamie Chang oem-priority: importance Undecided Critical
2012-10-19 17:12:20 Anthony Wong linux (Ubuntu): importance Medium Critical
2012-10-19 17:12:34 Anthony Wong linux (Ubuntu): assignee Timo Aaltonen (tjaalton)
2012-10-22 10:14:15 Timo Aaltonen bug task added linux (Ubuntu Oneiric)
2012-10-22 10:19:22 Timo Aaltonen linux (Ubuntu Oneiric): importance Undecided Critical
2012-10-22 10:19:22 Timo Aaltonen linux (Ubuntu Oneiric): status New In Progress
2012-10-22 10:19:32 Timo Aaltonen linux (Ubuntu Oneiric): assignee Timo Aaltonen (tjaalton)
2012-10-22 10:19:53 Timo Aaltonen linux (Ubuntu): status Triaged Fix Released
2012-10-22 10:19:53 Timo Aaltonen linux (Ubuntu): assignee Timo Aaltonen (tjaalton)
2012-10-22 11:13:53 Timo Aaltonen description Issue Description ----------------- Garbage green lines (4-5 pixel lines) appear on top of some Lenovo laptops' screens, persist from boot splash screen to desktop running. Collected Data -------------- Attached are the kernel dmesg, Xorg.0.log and dump files by intel_reg_dumper for oneiric installation with kernel version 3.0.0-19.33 and 3.0.0-20.34, and for precise installation with kernel version 3.2.0-23.26. Observations ------------ 2. This issue only happens on Oneiric with kernel version 3.0.0-20.34 and later ones 3. This issue does not happen on Oneiric with kernel version 3.0.0-19.33 and previous ones 4. This issue does not happen on Precise (12.04) with kernel version 3.2.0-23.36 5. This issue is caused by the upstream commit below:    f47166d2 drm/i915: Sanitize BIOS debugging bits from PIPECONF    The rationale and original bug description for the above commit can be    found at https://bugs.freedesktop.org/show_bug.cgi?id=47271 6. This issue would be gone if the above commit is reverted on Oneiric kernel    version 3.0.0-19.33 and later ones 7. There is one other commit below which fixed an issue of the above commit    in later kernel version, BUT this commit was verified to have nothing to    do with the issue here:    a9dcf84b drm/i915: don't clobber the pipe param in sanitize_modesetting 8. This issue was reported to be related to BIOS version as well (see comment #3) 9. There is a WARN_ON() oops on Oneiric with both kernel versions, but this is    supposedly an unrelated seperate issue, as it happens in both cases, but    presumably fixed in Precise. 10. By comparing the dump contents between two kernels running on Oneiric, the     significant difference is the PIPEACONF register 11. By comparing the dump contents between oneiric and precise, there are many     more registers with different values Summary ------- We are able to identify the guilty commit, and are able to provide a workaround by reverting the commit or by doing PIPECONF register change for non-relevant machines. However, we are not able to form a correct theory to explain exactly the above observations and to shape a correct patch to fix the root cause. SRU justification: Impact: Commit "628280f36e4fdbd drm/i915: Sanitize BIOS debugging bits from PIPECONF" got in the oneiric kernel via upstream, since it fixed a similar issue as here with an earlier version of the intel VBIOS. With a newer VBIOS however, the issue is back. Simply reverting the commit would likely mean breaking other setups. this is a critical bug for some our OEM's Fix: upstream patch 3bcf603f6d5d18b from 3.1 works around a bug in the CPT/PPT PCH chips, and it was bisected as the commit that fixes the bug in 3.1 and up. Testcase: boot a kernel that doesn't have 3bcf603f6d5d18b but has 628280f36e4fdbd on hw that has a "new enough" VBIOS. -- Issue Description ----------------- Garbage green lines (4-5 pixel lines) appear on top of some Lenovo laptops' screens, persist from boot splash screen to desktop running. Collected Data -------------- Attached are the kernel dmesg, Xorg.0.log and dump files by intel_reg_dumper for oneiric installation with kernel version 3.0.0-19.33 and 3.0.0-20.34, and for precise installation with kernel version 3.2.0-23.26. Observations ------------ 2. This issue only happens on Oneiric with kernel version 3.0.0-20.34 and later ones 3. This issue does not happen on Oneiric with kernel version 3.0.0-19.33 and previous ones 4. This issue does not happen on Precise (12.04) with kernel version 3.2.0-23.36 5. This issue is caused by the upstream commit below:    f47166d2 drm/i915: Sanitize BIOS debugging bits from PIPECONF    The rationale and original bug description for the above commit can be    found at https://bugs.freedesktop.org/show_bug.cgi?id=47271 6. This issue would be gone if the above commit is reverted on Oneiric kernel    version 3.0.0-19.33 and later ones 7. There is one other commit below which fixed an issue of the above commit    in later kernel version, BUT this commit was verified to have nothing to    do with the issue here:    a9dcf84b drm/i915: don't clobber the pipe param in sanitize_modesetting 8. This issue was reported to be related to BIOS version as well (see comment #3) 9. There is a WARN_ON() oops on Oneiric with both kernel versions, but this is    supposedly an unrelated seperate issue, as it happens in both cases, but    presumably fixed in Precise. 10. By comparing the dump contents between two kernels running on Oneiric, the     significant difference is the PIPEACONF register 11. By comparing the dump contents between oneiric and precise, there are many     more registers with different values Summary ------- We are able to identify the guilty commit, and are able to provide a workaround by reverting the commit or by doing PIPECONF register change for non-relevant machines. However, we are not able to form a correct theory to explain exactly the above observations and to shape a correct patch to fix the root cause.
2012-10-22 11:14:09 Timo Aaltonen bug watch added https://bugs.freedesktop.org/show_bug.cgi?id=56089
2012-10-22 11:14:09 Timo Aaltonen bug task added linux
2012-10-22 20:16:20 Tim Gardner linux (Ubuntu Oneiric): status In Progress Fix Committed
2012-10-22 22:04:04 James M. Leddy oem-priority: status New Invalid
2012-10-23 05:33:41 Bug Watch Updater linux: status Unknown Fix Released
2012-10-23 05:33:41 Bug Watch Updater linux: importance Unknown Medium
2012-11-16 20:00:35 James M. Leddy linux (Ubuntu Oneiric): status Fix Committed Fix Released
2012-11-16 20:00:53 James M. Leddy linux (Ubuntu Oneiric): status Fix Released Fix Committed
2012-11-19 13:41:37 Herton R. Krzesinski tags blocks-hwcert-enablement oneiric blocks-hwcert-enablement oneiric verification-done-oneiric
2012-11-28 22:53:09 Launchpad Janitor linux (Ubuntu Oneiric): status Fix Committed Fix Released
2012-11-28 22:53:09 Launchpad Janitor cve linked 2012-0957
2012-11-28 22:53:09 Launchpad Janitor cve linked 2012-4565
2013-05-07 17:21:21 Launchpad Janitor branch linked lp:ubuntu/lucid-security/linux-lts-backport-oneiric
2013-05-08 02:31:25 Launchpad Janitor branch linked lp:ubuntu/oneiric-security/linux-ti-omap4
2014-01-15 15:13:22 Launchpad Janitor branch linked lp:ubuntu/lucid-proposed/linux-lts-backport-oneiric
2014-01-15 21:39:30 Launchpad Janitor branch linked lp:ubuntu/lucid-updates/linux-lts-backport-oneiric