Summary: | [G965 non-GEM] systray in KDE 4 completely broken | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | walch.martin | ||||||||||
Component: | Driver/intel | Assignee: | Eric Anholt <eric> | ||||||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||
Severity: | major | ||||||||||||
Priority: | high | Keywords: | regression | ||||||||||
Version: | unspecified | ||||||||||||
Hardware: | x86-64 (AMD64) | ||||||||||||
OS: | Linux (All) | ||||||||||||
URL: | http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=6c0ca1676bf60529dd331cc739abdf68fa9e918d | ||||||||||||
Whiteboard: | |||||||||||||
i915 platform: | i915 features: | ||||||||||||
Bug Depends on: | |||||||||||||
Bug Blocks: | 20276 | ||||||||||||
Attachments: |
|
Description
walch.martin
2009-03-07 12:25:55 UTC
Created attachment 23643 [details]
dmesg
Created attachment 23644 [details]
/var/log/Xorg.0.log
Created attachment 23645 [details]
/etc/X11/xorg.conf
Thanks for the bisect. So it's caused by: author Eric Anholt <eric@anholt.net> 2009-01-21 23:52:02 (GMT) committer Eric Anholt <eric@anholt.net> 2009-01-27 22:33:43 (GMT) commit 6c0ca1676bf60529dd331cc739abdf68fa9e918d (patch) Don't forget the new state bos in check_aperture. They're tiny so it shouldn't have been a problem, but play it safe. This is another <5% loss on top of the previously reported value, bringing the whole series to about 8%. Might check with: commit fb6e00f40f713a87c760fc7603159ed11ea9b0d5 Author: Eric Anholt <eric@anholt.net> Date: Mon Mar 9 20:06:30 2009 -0700 Fix XV with non-GEM kernels by allocating a larger fake bufmgr. After syncing to git master, it's working fine. :) (I do not set the bug to resolved/fixed, because I do not know your policies for doing that) The policy is, if it's fixed upstream, go ahead and mark it fixed :) Thanks for testing. I'm pretty sure it was that commit. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.