From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling
Date: Thu, 20 Dec 2012 14:45:39 +0100 [thread overview]
Message-ID: <20121220134539.GA224@x4> (raw)
In-Reply-To: <CADnq5_Mkye_3fN1J=1Udw3mPH+nzn-n7yAjDjzUPX5x=XEGiZg@mail.gmail.com>
On 2012.12.20 at 08:30 -0500, Alex Deucher wrote:
> On Wed, Dec 19, 2012 at 9:33 AM, Markus Trippelsdorf
> <markus@trippelsdorf.de> wrote:
> > On 2012.12.19 at 15:18 +0100, Maarten Lankhorst wrote:
> >> Fix regression introduced by 85b144f860176
> >
> > Thanks. This fixes the kernel BUG, but now I get this errors in my
> > Xorg.log:
> >
> > [ 23.092] [mi] Increasing EQ size to 512 to prevent dropped events.
> > (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
> > (EE)
> > (EE) Backtrace:
> > (EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x584f1d]
> > (EE) 1: /usr/bin/X (mieqEnqueue+0x21b) [0x56615b]
> > (EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x44a792]
> > (EE) 3: /usr/bin/X (xf86PostButtonEvent+0xd5) [0x4829b5]
> > (EE) 4: /usr/lib64/xorg/modules/input/mouse_drv.so (0x7ff8f2501000+0x6b70) [0x7ff8f2507b70]
> > (EE) 5: /usr/lib64/xorg/modules/input/mouse_drv.so (0x7ff8f2501000+0x73a0) [0x7ff8f25083a0]
> > (EE) 6: /usr/lib64/xorg/modules/input/mouse_drv.so (0x7ff8f2501000+0x428c) [0x7ff8f250528c]
> > (EE) 7: /usr/bin/X (0x400000+0x71cd8) [0x471cd8]
> > (EE) 8: /usr/bin/X (0x400000+0x9a2ab) [0x49a2ab]
> > (EE) 9: /lib/libpthread.so.0 (0x7ff8f1edc000+0xf260) [0x7ff8f1eeb260]
> > (EE) 10: /lib/libc.so.6 (ioctl+0x7) [0x7ff8f19bd127]
> > (EE) 11: /usr/lib/libdrm.so.2 (drmIoctl+0x34) [0x7ff8f246a634]
> > (EE) 12: /usr/lib/libdrm.so.2 (drmCommandWriteRead+0x1f) [0x7ff8f246cbdf]
> > (EE) 13: /usr/lib/libdrm_radeon.so.1 (0x7ff8f250e000+0x27bf) [0x7ff8f25107bf]
> > (EE) 14: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7ff8f154f000+0x407ec) [0x7ff8f158f7ec]
> > (EE) 15: /usr/bin/X (_CallCallbacks+0x34) [0x438894]
> > (EE) 16: /usr/bin/X (FlushAllOutput+0x2c) [0x5880ec]
> > (EE) 17: /usr/bin/X (0x400000+0x33aa1) [0x433aa1]
> > (EE) 18: /usr/bin/X (0x400000+0x230cd) [0x4230cd]
> > (EE) 19: /lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff8f19088b5]
> > (EE) 20: /usr/bin/X (0x400000+0x22c09) [0x422c09]
> > (EE)
> > (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
> > (EE) [mi] mieq is *NOT* the cause. It is a victim.
> > (EE) [mi] EQ overflow continuing. 100 events have been dropped.
> > (EE)
> > (EE) Backtrace:
> > (EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x584f1d]
> > (EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44a792]
> > (EE) 2: /usr/bin/X (xf86PostButtonEvent+0xd5) [0x4829b5]
> > (EE) 3: /usr/lib64/xorg/modules/input/mouse_drv.so (0x7ff8f2501000+0x6b70) [0x7ff8f2507b70]
> > (EE) 4: /usr/lib64/xorg/modules/input/mouse_drv.so (0x7ff8f2501000+0x73a0) [0x7ff8f25083a0]
> > (EE) 5: /usr/lib64/xorg/modules/input/mouse_drv.so (0x7ff8f2501000+0x428c) [0x7ff8f250528c]
> > (EE) 6: /usr/bin/X (0x400000+0x71cd8) [0x471cd8]
> > (EE) 7: /usr/bin/X (0x400000+0x9a2ab) [0x49a2ab]
> > (EE) 8: /lib/libpthread.so.0 (0x7ff8f1edc000+0xf260) [0x7ff8f1eeb260]
> > (EE) 9: /lib/libc.so.6 (ioctl+0x7) [0x7ff8f19bd127]
> > (EE) 10: /usr/lib/libdrm.so.2 (drmIoctl+0x34) [0x7ff8f246a634]
> > (EE) 11: /usr/lib/libdrm.so.2 (drmCommandWriteRead+0x1f) [0x7ff8f246cbdf]
> > (EE) 12: /usr/lib/libdrm_radeon.so.1 (0x7ff8f250e000+0x27bf) [0x7ff8f25107bf]
> > (EE) 13: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7ff8f154f000+0x407ec) [0x7ff8f158f7ec]
> > (EE) 14: /usr/bin/X (_CallCallbacks+0x34) [0x438894]
> > (EE) 15: /usr/bin/X (FlushAllOutput+0x2c) [0x5880ec]
> > (EE) 16: /usr/bin/X (0x400000+0x33aa1) [0x433aa1]
> > (EE) 17: /usr/bin/X (0x400000+0x230cd) [0x4230cd]
> > (EE) 18: /lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff8f19088b5]
> > (EE) 19: /usr/bin/X (0x400000+0x22c09) [0x422c09]
> > (EE)
> > (EE) [mi] EQ overflow continuing. 200 events have been dropped.
> >
> > And the pictures get distorted on the test-webpage. See attached screenshot.
> >
>
> Anything in your kernel log that corresponds to the errors in your xorg log?
No. But I've found out that the errors in the xorg log are unrelated to
the image corruption.
I use one of those Logitech mice with this "hyper" fast scrolling
feature. And I guess the Xorg mouse driver just can't keep up with the
fast input. So it's just a harmless warning that can be ignored, I
guess.
--
Markus
next prev parent reply other threads:[~2012-12-20 13:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 14:18 [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling Maarten Lankhorst
2012-12-19 14:33 ` Markus Trippelsdorf
2012-12-20 13:30 ` Alex Deucher
2012-12-20 13:45 ` Markus Trippelsdorf [this message]
2012-12-20 13:58 ` Markus Trippelsdorf
2013-01-05 10:41 ` Markus Trippelsdorf
2013-01-15 14:43 ` Michel Dänzer
2013-01-15 15:23 ` Markus Trippelsdorf
2013-01-15 15:26 ` Michel Dänzer
2013-01-15 16:32 ` Markus Trippelsdorf
2013-01-15 17:03 ` Markus Trippelsdorf
2013-01-16 22:36 ` Alex Deucher
2013-01-16 23:10 ` Markus Trippelsdorf
2013-01-17 0:18 ` Jerome Glisse
2013-01-17 8:46 ` Markus Trippelsdorf
2013-01-17 15:44 ` Jerome Glisse
2013-01-17 16:10 ` Markus Trippelsdorf
2013-01-17 17:55 ` Jerome Glisse
2013-01-17 18:07 ` Markus Trippelsdorf
2013-01-17 18:28 ` Jerome Glisse
2013-01-17 18:57 ` Markus Trippelsdorf
2012-12-19 14:41 ` Paul Menzel
2012-12-19 14:47 ` Alex Deucher
2012-12-19 14:54 ` Markus Trippelsdorf
2012-12-19 16:03 ` Markus Trippelsdorf
2012-12-19 17:21 ` Maarten Lankhorst
2012-12-19 18:40 ` Paul Menzel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121220134539.GA224@x4 \
--to=markus@trippelsdorf.de \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).