From: Andrey N. <and...@ya...> - 2006-08-25 11:26:28
|
Hi, I just try to boot with kernel 2.6.16.2 which is built with essentially the same options as my 2.6.17.8 and the problem disappears. And it works even with i915 kernel driver distributed with kernel (i.e. I did not substitute it with the one from mesa cvs). So it seams to me like the problem has it roots in kernel module. But it just a guess. I am not familiar enough with this aspects to say for sure. Thank you, Andrey. --- Yuan Austin <yua...@gm...> wrote: > Hi, > > On 8/25/06, Andrey Nechypurenko <and...@ya...> wrote: > > Hi Folks, > > > > I am running Debian etch with 2.6.17.8 kernel on Fujitsu Siemens E8020D > > notebook. I just checked out the cvs version of Messa and drm using the > > following commands: > > > > git clone git://anongit.freedesktop.org/git/mesa/drm > > cvs -z3 -d:pserver:ano...@an...:/cvs/mesa co Mesa > > > > Then I run make linux-dri-x86 in Messa directory in order to build the > > i915_dri.so driver because the one distributed with this version of Debian > has > > a bug which prevents direct rendering from working. Everything went more or > > less well and I've got the new i915_dri.so and copy it to /usr/lib/dri > where > > the previous version was. > > > > Now glxinfo says that I have dirct rendering, but the new problem apears. > > Almost all openGL programs are crashing shortly after start with the > following > > message: > > > > Mesa: CPU vendor: GenuineIntel > > Mesa: CPU name: Intel(R) Pentium(R) M processor 1.73GHz > > Mesa: MMX cpu detected. > > Mesa: SSE cpu detected. > > Mesa: Not testing OS support for SSE, leaving enabled. > > lesson32: intel_ioctl.c:62: intelEmitIrqLocked: Assertion `((*(int > > *)intel->driHwLock) & ~0x40000000U) == (0x80000000U|intel->hHWContext)' > failed. > > Aborted > > > > Looks like there is a bug about locking... > When intelEmitIrqLocked is called, it assumes that it holds the lock, > but in intel_batchbuffer.c:intelCopyBuffer: > ............................... > intelWaitForFrameCompletion( intel ); > LOCK_HARDWARE( intel ); > ............................... > and intelWaitForFrameCompletion will call intelEmitIrqLocked. If > current application still holds the lock, there isn't this issue, but > if someone, e.g. X server steals the lock, the issue will occur. > > A workaroud is to swap the sequence of the two lines above:) > LOCK_HARDWARE( intel ); > intelWaitForFrameCompletion( intel ); > > --Ausitn > > > Could somebody please let me know whether it's me doing something wrong or > > it's a bug? > > > > Thank you, > > Andrey. > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com > > > > ------------------------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web services, security? > > Get stuff done quickly with pre-integrated technology to make your job > easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > > Mesa3d-users mailing list > > Mes...@li... > > https://lists.sourceforge.net/lists/listinfo/mesa3d-users > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |