Oneiric kernel doesn't boot on Ivybridge.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Oneiric |
Fix Released
|
High
|
Robert Hooker |
Bug Description
== Oneiric SRU Justification ==
[Impact]
This wil affect all users of Ivybridge on Oneiric when it releases.
[Justification]
This patch fixes Ivy Bridge bringup on Oneiric after recent bios
updates where gpu frequency scaling was enabled. It does not affect
anything besides Ivy Bridge (covered by IS_GEN7, IS_GEN6 is sandybridge
generation) in the code and has no way to regress other systems.
Without this patch, i915 will fail to load like this
[drm:init_
[drm:init_
[drm:i915_
vesafb will then load, and X will use the vesa driver with all kinds
of corruption problems due to the partially initialized GPU. No public
bug has been filed because it is unreleased hardware but it has been
tested internally.
[Test Case]
Boot to X on an Ivy Bridge system, which is not possible without this
patch.
[Regression Potential]
None, this only affects generation 7 GPU's which are unreleased and
covered by IS_GEN7 in the patch. No new code is added, only the
enabling of already existing code used for Sandy Bridge on the newer
processors.
Related branches
tags: | added: kernel-bot-stop-nagging |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: |
added: bot-stop-nagging removed: kernel-bot-stop-nagging |
Changed in linux (Ubuntu Oneiric): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
Changed in linux (Ubuntu Oneiric): | |
assignee: | nobody → Robert Hooker (sarvatt) |
tags: | added: blocks-hwcert-enablement |
Changed in linux (Ubuntu Oneiric): | |
status: | Confirmed → Fix Committed |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 888154
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.