vbetool should not be called on -intel when KMS is in use
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
acpi-support (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
pm-utils (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: acpi-support
jbarnes reports that vbetool can cause weird register resets on certain Intel graphics chipsets.
<jbarnes> bryce: more evidence of vbetool fail
bryce: running it will cause interrupts to break on some machines, leading to rendering hangs
<jbarnes> bryce: fdo bug 20896
<ubottu> Freedesktop bug 20896 in DRM/Intel "[GM965 KMS] X does not draw untill mouse is moved. Probably IRQ problems" [Major,New] http://
<bryce> ah yes, acpi-support calls vbetool
./resume.
./resume.
./suspend.
<jbarnes> I don't think all vbioses do it
also it mainly affects kms apparently
due to the ordering of irq enable
<jbarnes> symptoms would have been "all rendering stops"
mouse movement or some other interrupt source may have allowed it to continue
but that's config dependent I think
So it sounds like the calls to vbetool ought to be conditionalized such that they are not used if KMS is enabled and the system has an -intel graphics card.
Setting to High importance with milestone since this is a KMS-related issue, which should probably be investigated for Karmic.