[CFT] drm updates

[Paul B. Mahol]

On 8/29/08, Paul B. Mahol <onemda at gmail.com> wrote:
> On 8/29/08, Robert Noland <rnoland at freebsd.org> wrote:
>> On Fri, 2008-08-29 at 12:54 +0200, Paul B. Mahol wrote:
>>> On 8/28/08, Robert Noland <rnoland at freebsd.org> wrote:
>>> > On Thu, 2008-08-28 at 20:45 +0200, Paul B. Mahol wrote:
>>> >> On 8/28/08, Robert Noland <rnoland at freebsd.org> wrote:
>>> >> > On Thu, 2008-08-28 at 19:07 +0200, Paul B. Mahol wrote:
>>> >> >> On 8/27/08, Robert Noland <rnoland at freebsd.org> wrote:
>>> >> >> > On Wed, 2008-08-27 at 12:07 +0200, Paul B. Mahol wrote:
>>> >> >> >> On 8/26/08, Robert Noland <rnoland at freebsd.org> wrote:
>>> >> >> >> > On Tue, 2008-08-26 at 17:51 +0200, Paul B. Mahol wrote:
>>> >> >> >> >> Here is more kernel debug info (after updating libdrm and
>>> >> >> >> >> testing
>>> >> >> >> >> with
>>> >> >> >> >> glxgears)
>>> >> >> >> >
>>> >> >> >> > I don't think that the two issues are related, but try this
>>> >> >> >> > patch...
>>> >> >> >> > It
>>> >> >> >> > should at least, resolve the issue below.
>>> >> >> >> >
>>> >> >> >> > robert.
>>> >> >> >>
>>> >> >> >> Issue bellow is fixed, previous problem still exist.
>>> >> >> >>
>>> >> >> >> textdump of panic when unloading drm attached.
>>> >> >> >
>>> >> >> > Ok, The locking semantics are a nightmare... Give this a try, it
>>> >> >> > should
>>> >> >> > correct both the previous issue as well as this one.
>>> >> >> >
>>> >> >> > robert.
>>> >> >> >
>>> >> >>
>>> >> >> Panic fixed, now only Xorg crashing when using glxgears (,...)
>>> >> >> remains
>>> >> >> ;)
>>> >> >
>>> >> > Ok, what hardware are you using again?  Can you manually load drm
>>> >> > modules and set hw.dri.0.debug=1 and send me the debug output?
>>> >> >
>>> >> > robert.
>>> >>
>>> >> Hardware: "Mobile 945GM/GU Express Integrated Graphics Controller"
>>> >> Debug ouptut attached.
>>> >
>>> > Alright, try this...  I was pointed at this from another thread, but
>>> > your trace confirms why it doesn't work, at least with your driver.
>>> >
>>> > robert.
>>> >
>>>
>>> Nothing improved with that patch, still crash with glxgears, and lock
>>> with stellarium.
>>
>> ok, I don't understand why I'm not seeing any of this on my 965gm...  If
>> you want to send me another debug trace, I'll see if I can tell what is
>> going on now... Also, please send me a copy of your xorg.conf.
>
> Well, actually it is:
>
> agp0: <Intel 82945GM (945GM GMCH) SVGA controller> on vgapci0
> agp0: detected 7932k stolen memory
> agp0: aperture size is 256M
> drm0: <Intel i945GM> on vgapci0
>
>>
>>> How to make sure that this is really drm problem and not i915, Xorg,
>>> mesa-ports that need recompiling?
>>
>> If you are using current ports tree, then nothing should need rebuilding
>> that I can think of.  I have been using git libdrm and xf86-video-intel
>> driver, but what is in ports now should be fine I think.  The updated
>> libdrm should only be required to get the new vblank code to allow it to
>> disable vblank interrupts.
>>
>> There is a bug which prevents vblanks irqs from being disabled after a
>> vt switch, but it shouldn't have a real impact on functionality.
>>
>> robert.
>>
>>
>

Ooops, there is still (with newest HEAD) panic when unloading agp module,
textdump with backtrack and alltrace attached.