| Summary: | xorg freeze onf xorg 1.6.1.901 with refer to intel drivers [sony vaio sr19xn and dell mini 9] | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Giovanni Pellerano <giovanni.pellerano> | ||||||
| Component: | Server/General | Assignee: | Keith Packard <keithp> | ||||||
| Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | critical | ||||||||
| Priority: | high | CC: | idr, ingmar, jbarnes, jcristau, keithp, maggu2810, mike.auty, remi | ||||||
| Version: | unspecified | ||||||||
| Hardware: | x86 (IA32) | ||||||||
| OS: | Linux (All) | ||||||||
| URL: | https://bugs.gentoo.org/show_bug.cgi?id=275852 | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Giovanni Pellerano
2009-06-29 11:10:04 UTC
Created attachment 27225 [details]
gentoo patchset 1.6.1.901-r5
Created attachment 27226 [details]
gentoo patchset 1.6.1.901-r4
So this sounds like an xserver regression. Could you figure out which patch in 1.6.1.901-r5 causes the regression? Thanks. sorry gordon at the moment i've problems to test it; i will do; please keep me updated of the informations or test you need end if any other fill a similar bug report. thanks (In reply to comment #3) > So this sounds like an xserver regression. Could you figure out which patch in > 1.6.1.901-r5 causes the regression? Thanks. > > For me it was the following patch: DRI2: Implement protocol for DRI2GetBuffersWithFormat This change implements the protocol for DRI2GetBuffersWithFormat, but the bulk of the differences are the changes to the extension / driver interface to make this function work. The old CreateBuffers and DeleteBuffers routines are replaced with CreateBuffer and DeleteBuffer (both singular). This allows drivers to allocate buffers for a drawable one at a time. As a result, 3D drivers can now allocate the (fake) front-buffer for a window only when it is needed. Since 3D drivers only ask for the front-buffer on demand, the real front-buffer is always created. This allows CopyRegion impelemenations of SwapBuffers to continue working. As with previous version of this code, if the client asks for the front-buffer for a window, we instead give it the fake front-buffer. Signed-off-by: Ian Romanick <ian.d.romanick@intel.com> Reviewed-by: Kristian Høgsberg <krh@redhat.com> Oh and it seems only KMS is affected, UMS works fine. Thanks (In reply to comment #3) > So this sounds like an xserver regression. Could you figure out which patch in > 1.6.1.901-r5 causes the regression? Thanks. > see http://lists.freedesktop.org/pipermail/xorg/2009-June/046267.html i think this is actually a driver bug. (In reply to comment #7) > see http://lists.freedesktop.org/pipermail/xorg/2009-June/046267.html i think > this is actually a driver bug. Confirming, we did some searching with a user whose X wouldn't freeze but segfault. Basically, [1] does not break the ABI like Julien said, but disables DRI2 on older drivers (2.7.1 in our case) or with drivers built with previous versions of the server. However, with DRI2 disabled, the driver tries to initialize DRI1 which for some reason also fails. Hell then breaks loose and the driver segfaults later on in drm_intel_bo_alloc_for_render (IIRC, the function is from memory, I need to look it up). Hope that helps [1] http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.6-branch&id=4fad615d689c61c6c3a000295a1fa755359737cb We can safely say this is obsolete now, as these machines no longer even have UMS/DRI1. |
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.