Hello I had found 3 months ago problem and is not solved in git yet: Some 3d applications are crashing when i915tex_dri.so is used I have debian unstable , lastest kernel, xorg, drm, mesa, drm/linux-core, linux-agp-compat from git (default branches) When I use option Legacy3D (i915_dri.so is used) games from wine and native opengl game Second Life are working fine , without Legacy3D (i915tex_dri.so is used) they are crashing , so its i915tex dri bug Second life only show : 2007-02-16T22:05:44Z WARNING: *** Caught signal 11 3dmark2001 when crashing show some backtrace : Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00000000). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:00000000 ESP:003263b0 EBP:0033ee1c EFLAGS:00010202( - 00 - -RI1) EAX:00e475d0 EBX:7e7d15bc ECX:00a6dec8 EDX:0033ee10 ESI:001cb948 EDI:00780d28 Stack dump: 0x003263b0: 0046527a 001cb948 00464b80 001cb948 0x003263c0: 001cb948 003264bc 00732308 00000000 0x003263d0: 00464a68 0033ee1c 004082cb 00000001 0x003263e0: 7e7a4e62 0033ee1c 7e7d15bc 0000007b 0x003263f0: 7e7a4c04 00000073 00000246 00000000 0x00326400: 00000000 00000000 00000000 00000000 Backtrace: =>1 0x00000000 (0x0033ee1c) 2 0x00406d49 in 3dmark2001se (+0x6d49) (0x0033f060) 3 0x5f4021e6 in mfc42 (+0x21e6) (0x0033f090) 4 0x5f402945 in mfc42 (+0x2945) (0x0033f0c0) 5 0x5f402ae5 in mfc42 (+0x2ae5) (0x0033f110) 6 0x5f401be1 in mfc42 (+0x1be1) (0x0033f190) 7 0x5f401aff in mfc42 (+0x1aff) (0x0033f1b0) 8 0x5f401a88 in mfc42 (+0x1a88) (0x0033f210) 9 0x5f401a10 in mfc42 (+0x1a10) (0x0033f22c) 10 0x5f4019cf in mfc42 (+0x19cf) (0x0033f258) 11 0x7ea75eea (0x0033f288) 12 0x7ea76280 (0x00000111) 13 0x00000000 (0x00000000) 0x00000000: addb %al,0x0(%eax) Modules: Module Address Debug info Name (29 modules) PE 340000-3af000 Deferred e2mfc PE 3b0000-3d1000 Deferred grphmfc PE 3e0000-3f8000 Deferred sndmfc PE 400000-84c000 Export 3dmark2001se PE 850000-870000 Deferred inetmfc PE 870000-880000 Deferred si2guimfc PE 9c0000-a45000 Deferred e2_d3d8_driver_mfc PE 10000000-10065000 Deferred rlmfc PE 5f400000-5f4f2000 Export mfc42 PE 780a0000-780b2000 Deferred msvcirt PE 780c0000-78121000 Deferred msvcp60 PE 7cc60000-7cc64000 Deferred d3d8 PE 7e3f0000-7e3f5000 Deferred setupapi PE 7e450000-7e453000 Deferred version PE 7e480000-7e484000 Deferred oleaut32 PE 7e520000-7e531000 Deferred comctl32 PE 7e5f0000-7e5f6000 Deferred shlwapi PE 7e650000-7e6b1000 Deferred shell32 PE 7e740000-7e744000 Deferred dsound PE 7e790000-7e794000 Deferred msvcrt PE 7e800000-7e848000 Deferred winmm PE 7e8c0000-7e8c3000 Deferred rpcrt4 PE 7e920000-7e924000 Deferred gdi32 PE 7e9c0000-7e9d1000 Deferred user32 PE 7eb00000-7eb03000 Deferred advapi32 PE 7eb50000-7eb54000 Deferred ole32 PE 7ed20000-7ed24000 Deferred ddraw PE 7edf0000-7ee54000 Deferred kernel32 PE 7ef80000-7ef83000 Deferred ntdll Threads: process tid prio (all id:s are in hex) 0000000a 0000000c 0 0000000b 0 00000008 (D) C:\Program Files\MadOnion.com\3DMark2001 SE\3DMark2001SE.exe 0000000f 0 00000009 0 <== I do not know how to debug , I will attach any informations what will be nessesery Mike
hmm I didnt update xorg and driver long time , and I was suprised today , 3dmark with wine was working , at least first test , with second when modes was changing everything crashed and goes to kde logging screen ... So i have to wait longer :D
oh,it using i915_dri.so , so it is like withLegacy3D ... and performance with wine the same , but nero (neuro evolving robots operatives) was speed up , but maybe due better vbo , maybe other things like mouse or network doing interupts and doing cpu to sleep and this could be reason slown too
So as for now I can run 3dmark in emulated screen (in window) , when is not emulating after first test when modes are changed 3dmark crashing (this wasn't before) , maybe 3dmark trying change mode to some what is not supported and that is why crashing ? (when was in emulated , window was changed to 0 width and haight when changing after test)
Mass version move, cvs -> git
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.