Xorg EQ overflowing

[Renato Caldas]

On Fri, Nov 6, 2009 at 1:18 AM, Adam Williamson <awilliam at redhat.com> wrote:
> On Thu, 2009-11-05 at 15:18 -0800, David L wrote:
>> After recent rawhide updates, I'm having Xorg problems:
>>
>> [mi] EQ overflowing. The server is probably stuck in an infinite loop.
>>
>> On this hardware:
>>  http://www.smolts.org/client/show/pub_8aaac744-2cff-40c2-aeed-743e9495e525
>>
>> Backtrace:
>> 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e585c]
>> 1: /usr/bin/Xorg (mieqEnqueue+0x1b7) [0x80e5187]
>> 2: /usr/bin/Xorg (xf86PostMotionEventP+0xd4) [0x80bf8a4]
>> 3: /usr/lib/xorg/modules/input/evdev_drv.so (0xd14000+0x3172) [0xd17172]
>> 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xd14000+0x3466) [0xd17466]
>> 5: /usr/bin/Xorg (0x8048000+0x6a1f0) [0x80b21f0]
>> 6: /usr/bin/Xorg (0x8048000+0x11dd04) [0x8165d04]
>> 7: (vdso) (__kernel_sigreturn+0x0) [0xbaf400]
>> 8: (vdso) (__kernel_vsyscall+0x10) [0xbaf424]
>> 9: /lib/libc.so.6 (ioctl+0x19) [0x80ee39]
>> 10: /usr/lib/libdrm.so.2 (drmIoctl+0x2e) [0x46888e]
>> 11: /usr/lib/libdrm.so.2 (drmCommandWrite+0x3c) [0x468c1c]
>> 12: /usr/lib/libdrm_nouveau.so.1 (0xabb000+0x2bea) [0xabdbea]
>> 13: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map_range+0xf8) [0xabde38]
>> 14: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map+0x34) [0xabdf04]
>> 15: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x27d000+0x9573) [0x286573]
>> 16: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x27d000+0xa81d) [0x28781d]
>> 17: /usr/lib/xorg/modules/libexa.so (0x521000+0x75ca) [0x5285ca]
>> 18: /usr/bin/Xorg (0x8048000+0x15cc80) [0x81a4c80]
>> 19: /usr/bin/Xorg (0x8048000+0xcd926) [0x8115926]
>> 20: /usr/bin/Xorg (0x8048000+0xc9c94) [0x8111c94]
>> 21: /usr/bin/Xorg (0x8048000+0x261f7) [0x806e1f7]
>> 22: /usr/bin/Xorg (0x8048000+0x1a8c5) [0x80628c5]
>> 23: /lib/libc.so.6 (__libc_start_main+0xe6) [0x753bb6]
>> 24: /usr/bin/Xorg (0x8048000+0x1a4b1) [0x80624b1]
>>
>>
>> I changed to an older kernel and used nomodeset and the problem
>> went away (I think... not sure I really have statistical significance, but
>> it failed 3x with the newer kernel with kms and worked once without
>> it).
>>
>> Anybody else seeing this?

I am seeing this too.

> Please try the latest shiny - today's Rawhide, plus:
>
> http://koji.fedoraproject.org/koji/buildinfo?buildID=140035
>
> and:
>
> http://koji.fedoraproject.org/koji/buildinfo?buildID=139823
>
> and possibly:
>
> http://koji.fedoraproject.org/koji/buildinfo?buildID=139811
>
> (that one might be in today's rawhide already, not sure)
>
> hopefully it goes away with those.

It seems to have gone away.

Cheers,
  Renato

> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
> http://www.happyassassin.net
>
> --
> fedora-test-list mailing list
> fedora-test-list at redhat.com
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-test-list
>