Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #245993 > unrolled thread

system lock up, not sure if related to "your system is too slow"

Back to article view | Back to linux.debian.user

Contents

  system lock up, not sure if related to "your system is too slow" songbird <songbird@anthive.com> - 2022-03-06 13:20 +0100
    Re: system lock up, not sure if related to "your system is too slow" Vincent Lefevre <vincent@vinc17.net> - 2022-03-07 18:10 +0100
      Re: system lock up, not sure if related to "your system is too slow" songbird <songbird@anthive.com> - 2022-03-08 03:20 +0100
        Re: system lock up, not sure if related to "your system is too slow" Vincent Lefevre <vincent@vinc17.net> - 2022-03-09 11:20 +0100
          Re: system lock up, not sure if related to "your system is too slow" songbird <songbird@anthive.com> - 2022-03-09 14:20 +0100

#245993 — system lock up, not sure if related to "your system is too slow"

ok, i've finally had my computer lock up again while i've
set up the core dumps and i was hoping that i'd get an
actual core dump file to help narrow things down to a
specific programs, but no luck with that at all.

system is running Debian Testing, updates applied each
morning. desktop is MATE.

the only messages i can find are in the Xorg.old log and
they look like:

=====
[  2341.978] (EE) event4  - Logitech K840 Mechanical Corded Keyboard: client bug: event processing lagging behind by 27ms, your system is too slow
=====

the symptoms are that as i am typing the keyboard completely
stops responding and the mouse too, the system is then hung.
nothing updates or changes.  the clock, network, etc.  all 
stuck.

when i search for this kind of problem on the internet i come
up with:

https://itectec.com/ubuntu/ubuntu-why-am-i-getting-event-processing-lagging-behind-msg-in-ubuntu-20-10/

which says ignore it

while the following two give me the hope that it is some
kind of bug that might get fixed.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968093

https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues/46

i'm not sure i can help at all with debugging this further, but
since others might be seeing this message and wondering what is
going on i'll post this anyways.


  songbird

[toc] | [next] | [standalone]

#246022

On 2022-03-06 07:12:10 -0500, songbird wrote:
> when i search for this kind of problem on the internet i come
> up with:
> 
> https://itectec.com/ubuntu/ubuntu-why-am-i-getting-event-processing-lagging-behind-msg-in-ubuntu-20-10/
> 
> which says ignore it
> 
> while the following two give me the hope that it is some
> kind of bug that might get fixed.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968093
> 
> https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues/46

My opinion is that the behavior is normal and that the bug is the
message itself, i.e. libinput misdetects a potential issue. No-one
knows the cause yet, possibly a buggy timestamp. AFAIK, users
(including me) who see this message haven't notice any slowness
issue.

Well, only if you get something like more than 100ms, perhaps you
need to worry. But even 100ms, that's a fraction of second, thus
not related to a lock up.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [next] | [standalone]

#246037

Vincent Lefevre wrote:
> On 2022-03-06 07:12:10 -0500, songbird wrote:
>> when i search for this kind of problem on the internet i come
>> up with:
>> 
>> https://itectec.com/ubuntu/ubuntu-why-am-i-getting-event-processing-lagging-behind-msg-in-ubuntu-20-10/
>> 
>> which says ignore it
>> 
>> while the following two give me the hope that it is some
>> kind of bug that might get fixed.
>> 
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968093
>> 
>> https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues/46
>
> My opinion is that the behavior is normal and that the bug is the
> message itself, i.e. libinput misdetects a potential issue. No-one
> knows the cause yet, possibly a buggy timestamp. AFAIK, users
> (including me) who see this message haven't notice any slowness
> issue.
>
> Well, only if you get something like more than 100ms, perhaps you
> need to worry. But even 100ms, that's a fraction of second, thus
> not related to a lock up.

  thanks for the reply,  :)

  ok, any ideas how to get a crash instead of a lockup so i can
figure out where the problem might be?

  right now it locks solid and i can't get a core file at all.
all my log files are not giving me any clues either the Xorg
one is the only one that's telling me anything relating to
what is happening (some kind of IO issue).

  it happens when i'm typing, not at other times.  it might
only be typing in the browser (firefox).  i'm not sure if the
issue is the keyboard driver, the USB subsystems or xorg stuff
or the browser and i'm not sure how to get it isolated.  any
tips would be greatly appreciated.  :)

  all my drives are SSD and they seem to not be having trouble
recovering from the lockups when i restart the machine but it
would be nice to have some more detailed logs of what is going
on and those would need to be sync'd to make sure i'm catching
them completely, but that's better than the nothing i'm coming
up with now for figuring this out.  :)


  songbird

[toc] | [prev] | [next] | [standalone]

#246110

On 2022-03-07 20:55:52 -0500, songbird wrote:
>   right now it locks solid and i can't get a core file at all.
> all my log files are not giving me any clues either the Xorg
> one is the only one that's telling me anything relating to
> what is happening (some kind of IO issue).
> 
>   it happens when i'm typing, not at other times.  it might
> only be typing in the browser (firefox).  i'm not sure if the
> issue is the keyboard driver, the USB subsystems or xorg stuff
> or the browser and i'm not sure how to get it isolated.  any
> tips would be greatly appreciated.  :)

First, you need to make sure that the lockup isn't due to memory usage
(if you have swap). You can limit the memory used by a process, e.g.
firefox with "ulimit -v ..." before executing firefox in a wrapper.

Other than that, firefox shouldn't be able to lock up the whole system
(even though the issue would be visible only with firefox, the actual
issue would be somewhere else, probably a kernel or hardware bug).

You can install atop and use it with a small interval to detect
a potential abnormal increase of resource usage before the lockup
occurs.

>   all my drives are SSD and they seem to not be having trouble
> recovering from the lockups when i restart the machine but it
> would be nice to have some more detailed logs of what is going
> on and those would need to be sync'd to make sure i'm catching
> them completely, but that's better than the nothing i'm coming
> up with now for figuring this out.  :)

I fear for such kind of issues, the logs will not tell you more.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [next] | [standalone]

#246118

Vincent Lefevre wrote:
> On 2022-03-07 20:55:52 -0500, songbird wrote:
>>   right now it locks solid and i can't get a core file at all.
>> all my log files are not giving me any clues either the Xorg
>> one is the only one that's telling me anything relating to
>> what is happening (some kind of IO issue).
>> 
>>   it happens when i'm typing, not at other times.  it might
>> only be typing in the browser (firefox).  i'm not sure if the
>> issue is the keyboard driver, the USB subsystems or xorg stuff
>> or the browser and i'm not sure how to get it isolated.  any
>> tips would be greatly appreciated.  :)
>
> First, you need to make sure that the lockup isn't due to memory usage
> (if you have swap). You can limit the memory used by a process, e.g.
> firefox with "ulimit -v ..." before executing firefox in a wrapper.

  thanks,

  i'm barely using this machine most of the time, the few times i
use swap space are when i'm editing a large picture or something
like that.  it hasn't locked up at all during those kinds of
tasks.

$ free

  Mem:         8003140     1349040     4420980      480208     2233120     5904008
Swap:       19530748           0    19530748


> Other than that, firefox shouldn't be able to lock up the whole system
> (even though the issue would be visible only with firefox, the actual
> issue would be somewhere else, probably a kernel or hardware bug).

  yes, i think so too, someplace in the USB, keyboard or IO 
processes for such devices.


> You can install atop and use it with a small interval to detect
> a potential abnormal increase of resource usage before the lockup
> occurs.

  i'll take a look at that.

  at the moment i see a new version of firefox is being downloaded
so that will get installed within a few minutes.


>>   all my drives are SSD and they seem to not be having trouble
>> recovering from the lockups when i restart the machine but it
>> would be nice to have some more detailed logs of what is going
>> on and those would need to be sync'd to make sure i'm catching
>> them completely, but that's better than the nothing i'm coming
>> up with now for figuring this out.  :)
>
> I fear for such kind of issues, the logs will not tell you more.

  :(

  we'll see what can be done.  thanks again.  :)


  songbird

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web