[PATCH] mieq: Provide better adaptability and diagnostics during mieq overflow

Peter Hutterer peter.hutterer at who-t.net
Sun Oct 16 17:44:05 PDT 2011

On Sun, Oct 16, 2011 at 01:57:27PM -0700, Jeremy Huddleston wrote:
> On Oct 16, 2011, at 1:47 PM, Jeremy Huddleston wrote:
> >> I'm not sure we need to be even this verbose; just a single warning when
> >> the queue is blocked and another one when it starts working again should
> >> be sufficient. I fear flooding the disk with errors if this happens
> >> because your cat falls asleep on the keyboard while watching dancing
> >> mice on the screen.
> > 
> > That's why we shut up after DROP_BACKTRACE_MAX reports.  What about lowering DROP_BACKTRACE_MAX to 5 rather than 20?
> Also, if your cat falls asleep on the keyboard, the system either can keep
> up with the generated events (no logging before or after this patch) or it
> fills up the queue and we have dropped events.  

I thought X kills kittens anyway. This is a nonissue.

More information about the xorg-devel mailing list