Bug 37157 - [bisected] KDE KWin crashes on start with delayed BO mapping
Summary: [bisected] KDE KWin crashes on start with delayed BO mapping
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-12 18:55 UTC by Jure Repinc
Modified: 2011-05-13 03:56 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
lspci (9.54 KB, text/plain)
2011-05-12 18:56 UTC, Jure Repinc
Details
Xorg.0.log (34.18 KB, text/plain)
2011-05-12 18:57 UTC, Jure Repinc
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jure Repinc 2011-05-12 18:55:27 UTC
After updating the mesa today KWin started to crash/segfault on start. I've bisected and the first commmit that causes the crash is:
5e15497452cf3e4d2fc76fdc6ed8113d0891b467
r600g: delay mapping until first map request. (v2)

This is with KDE KWin 4.6.3 and on a laptop with integrated ATI Mobility Radeon HD 5470.

Later I've also tried with glxgears, which appears to work fine if in window and crashes if started with -fullscreen option.
Comment 1 Jure Repinc 2011-05-12 18:56:24 UTC
Created attachment 46654 [details]
lspci
Comment 2 Jure Repinc 2011-05-12 18:57:04 UTC
Created attachment 46655 [details]
Xorg.0.log
Comment 3 Mathieu Belanger 2011-05-12 20:47:50 UTC
Same commit cause problem there.

Using EVE-Online game. The game crash between "login" and "characters selection" after I have updated to the latest git drivers.

Bisecting pointed out this commit as the problem!
Comment 4 Dave Airlie 2011-05-12 21:05:51 UTC
please re-test with master.

thanks for the bug report.
Comment 5 Jure Repinc 2011-05-13 03:56:39 UTC
Retested with master and it is fixed, so closiing as such. Thanks.


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.