> If it's really crashing, you should see a backtrace at the end of > /var/log/Xorg.0.log (please send this backtrace then). If it's a > freeze/hang of the machine instead of a crash, it's harder to debug...
Sorry, no backtrace. The whole machine freezes. >> I can't reproduce this with upstream git, pulled BEFORE the 2.2.1-1 >> release, but it was reproducable with the 2.2.0.90-3 debian package. >> My git pull took place between those two upstream releases. > > Did you pull from xf86-video-intel-2.2-branch or from the master branch? > 2.2.0.90 and 2.2.1 come from the former, by default you get the latter. I pulled from master. Are they really so much different? To be exact, I pulled from master first some time after middle of December and upgraded multiple times, but this bug never occured. >> The main difference between my git pulls and the debian package is >> probably that I always compile with -O0, while the debian package is >> compiled with -O2 AFAIK. > > It would be very nice to check whether -O0 is actually involved and > to locate which commit introduced/fixed the problem (with git-bisect > or so). Yes, but that would require the bug to be always reproducable. Currently, it's only sometimes reproducable. Willi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
