Re: Tiny fonts, was Re: system lock up, not sure if related to "your system is too slow"

[songbird]

David Wright wrote:
...
> For 1280x720, you could try 1920x1080, or 960x540, according
> to how large you want the characters. With a screen having
> a wide aspect ratio, you might try 1600x900, 800x450, and
> so on (ie native resolution ÷ small integer).

  thank you, i've already got that taken care of by the
what i wrote in the other message.  it wasn't enough to
just change the font, but rerunning the configure step
which copied the relevant files to /etc/ so
they were available during early boot stage.

  i've not had any more lock ups recently but i'm also
running a different kernel now so perhaps it was a bug in
there someplace that got squashed.  for that i would need
some kind of way to trace everything that is running and
put it in a log that persists, but not so much that it
plugs up my entire system.  i'm hoping it's just fixed and
gone, but ...


  songbird

Tiny fonts, was Re: system lock up, not sure if related to "your system is too slow"

[David Wright]

On Thu 10 Mar 2022 at 08:44:10 (-0500), songbird wrote:
> Jörg-Volker Peetz wrote:

> > Did you take a look into `dmesg -l err` and `Xorg.log` in this case?
> 
>   no, i didn't, too hard for me to see or sit to squint at the 
> screen to be able to read.  the login prompt and screen fonts
> are so small that i type it all in by memory and can usually 
> get it right.  i used to have it set up where all the terminal 
> fonts would come up with a big enough font that i'd not have 
> that problem, but i've not been dealing much with the raw 
> terminal screens enough to do it on this system yet.

The trick I use to workaround this problem is:

. When the grub screen appears, press "E" instead of Return,

. Look at the Grub script that appears (you don't need to be
  able to actually /read/ it).

. The bottom line is the initrd line, preceded by a comment line,
  The third line from the bottom is the kernel line.

. Press  enough times to reach the bottom (you can just see
  the cursor appear below the bottom line), then  twice, followed
  by . That puts the cursor at the end of the kernel line.

. Type  video=1280x720

. Type Ctrl-X to boot.

For 1280x720, you could try 1920x1080, or 960x540, according
to how large you want the characters. With a screen having
a wide aspect ratio, you might try 1600x900, 800x450, and
so on (ie native resolution ÷ small integer).

Cheers,
David.

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

[songbird]

Jörg-Volker Peetz wrote:
...
> Maybe this website can help with the console font size:
>
> https://www.linux.com/topic/desktop/how-change-your-linux-console-fonts/

  interesting...

  after trying various things out and getting various fonts installed
i found that simply changing /etc/default/console-setup did not make
the changes effective for the linux virtual terminals, but running:

# dpkg-reconfigure console-setup

would.  in nosing around i found comments about some things being
required made available in other locations so that they could be
used during early boot stage so it now makes sense as to why just
changing the file doesn't do everything you need.  (/etc/console-setup 
contains the files needed).


  songbird

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

[Jörg-Volker Peetz]

songbird wrote on 10/03/2022 14:44:

Jörg-Volker Peetz wrote:

songbird wrote:

...

i did install the dummy package and uninstalled the intel
but that did not leave me with a system that booted to the
desktop so i put it back.


Did you take a look into `dmesg -l err` and `Xorg.log` in this case?


   no, i didn't, too hard for me to see or sit to squint at the
screen to be able to read.  the login prompt and screen fonts
are so small that i type it all in by memory and can usually
get it right.  i used to have it set up where all the terminal
fonts would come up with a big enough font that i'd not have
that problem, but i've not been dealing much with the raw
terminal screens enough to do it on this system yet.


   songbird


Maybe this website can help with the console font size:

https://www.linux.com/topic/desktop/how-change-your-linux-console-fonts/

Regards,
Jörg.

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

[songbird]

Jörg-Volker Peetz wrote:
>songbird wrote:
... 
>>i did install the dummy package and uninstalled the intel
>> but that did not leave me with a system that booted to the
>> desktop so i put it back.
>> 
> Did you take a look into `dmesg -l err` and `Xorg.log` in this case?

  no, i didn't, too hard for me to see or sit to squint at the 
screen to be able to read.  the login prompt and screen fonts
are so small that i type it all in by memory and can usually 
get it right.  i used to have it set up where all the terminal 
fonts would come up with a big enough font that i'd not have 
that problem, but i've not been dealing much with the raw 
terminal screens enough to do it on this system yet.


  songbird

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

[Jörg-Volker Peetz]

songbird wrote on 08/03/2022 16:35:

Jörg-Volker Peetz wrote:

As far as I know, the xserver-xorg-video-intel is deprecated for modern Intel
CPUs. With an Intel Core i7 7700 the kernel `modesetting` works well here:

Something like

Section "Device"
Identifier  "Intel Graphics"
Driver  "modesetting"
EndSection

in `/etc/X11/xorg.conf.d/20-modesetting.conf` or `/etc/X11/xorg.conf`.

Keep just the `xserver-xorg-video-dummy` on the system for dependencies.
And for video acceleration the package `intel-media-va-driver`.


   i did install the dummy package and uninstalled the intel
but that did not leave me with a system that booted to the
desktop so i put it back.


   songbird


Did you take a look into `dmesg -l err` and `Xorg.log` in this case?

Regards,
Jörg.

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

[songbird]

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   019530748


> 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

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

[Vincent Lefevre]

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  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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

[songbird]

Jörg-Volker Peetz wrote:
> As far as I know, the xserver-xorg-video-intel is deprecated for modern Intel 
> CPUs. With an Intel Core i7 7700 the kernel `modesetting` works well here:
>
> Something like
>
> Section "Device"
>Identifier  "Intel Graphics"
>Driver  "modesetting"
> EndSection
>
> in `/etc/X11/xorg.conf.d/20-modesetting.conf` or `/etc/X11/xorg.conf`.
>
> Keep just the `xserver-xorg-video-dummy` on the system for dependencies.
> And for video acceleration the package `intel-media-va-driver`.

  i did install the dummy package and uninstalled the intel
but that did not leave me with a system that booted to the
desktop so i put it back.


  songbird

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

[songbird]

Greg Wooledge wrote:
...
> You shouldn't even need to create that xorg.conf.d snippet.  It should
> just work automatically.

   removing the xserver-xorg-video-intel package left me with a
command line only system.  so i had to reinstall that.


> You *will* however most likely need to install some non-free firmware
> packages, e.g. firmware-misc-nonfree .
>
> unicorn:~$ sudo dmesg | grep -i firmware
> [...]
> [   10.387158] i915 :00:02.0: firmware: direct-loading firmware 
> i915/kbl_dmc_ver1_04.bin
> [   10.387505] i915 :00:02.0: [drm] Finished loading DMC firmware 
> i915/kbl_dmc_ver1_04.bin (v1.4)
>
> unicorn:~$ dpkg -L firmware-misc-nonfree | grep i915/kbl_dmc_ver1_04.bin
> /lib/firmware/i915/kbl_dmc_ver1_04.bin
>
> (That's from my system, which is not necessarily the same model of Intel
> onboard graphics as the OP's, but all of the modern Intel graphics chipsets
> need non-free firmware for acceleration to work.)

  i didn't have firmware-misc-nonfree installed so now that is
so perhaps that will help.  thanks.


  songbird

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

[Greg Wooledge]

On Tue, Mar 08, 2022 at 10:07:19AM +0100, Jörg-Volker Peetz wrote:
> As far as I know, the xserver-xorg-video-intel is deprecated for modern
> Intel CPUs. With an Intel Core i7 7700 the kernel `modesetting` works well
> here:
> 
> Something like
> 
> Section "Device"
>   Identifier  "Intel Graphics"
>   Driver  "modesetting"
> EndSection
> 
> in `/etc/X11/xorg.conf.d/20-modesetting.conf` or `/etc/X11/xorg.conf`.
> 
> Keep just the `xserver-xorg-video-dummy` on the system for dependencies.
> And for video acceleration the package `intel-media-va-driver`.

You shouldn't even need to create that xorg.conf.d snippet.  It should
just work automatically.

You *will* however most likely need to install some non-free firmware
packages, e.g. firmware-misc-nonfree .

unicorn:~$ sudo dmesg | grep -i firmware
[...]
[   10.387158] i915 :00:02.0: firmware: direct-loading firmware 
i915/kbl_dmc_ver1_04.bin
[   10.387505] i915 :00:02.0: [drm] Finished loading DMC firmware 
i915/kbl_dmc_ver1_04.bin (v1.4)

unicorn:~$ dpkg -L firmware-misc-nonfree | grep i915/kbl_dmc_ver1_04.bin
/lib/firmware/i915/kbl_dmc_ver1_04.bin

(That's from my system, which is not necessarily the same model of Intel
onboard graphics as the OP's, but all of the modern Intel graphics chipsets
need non-free firmware for acceleration to work.)

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

[Jörg-Volker Peetz]

As far as I know, the xserver-xorg-video-intel is deprecated for modern Intel 
CPUs. With an Intel Core i7 7700 the kernel `modesetting` works well here:


Something like

Section "Device"
  Identifier  "Intel Graphics"
  Driver  "modesetting"
EndSection

in `/etc/X11/xorg.conf.d/20-modesetting.conf` or `/etc/X11/xorg.conf`.

Keep just the `xserver-xorg-video-dummy` on the system for dependencies.
And for video acceleration the package `intel-media-va-driver`.

Regards,
Jörg.

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

[songbird]

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

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

[songbird]

Johann Klammer wrote:
...
> xserver-xorg-video-intel
> update that one. if that doesn't help, 

  already at the most current version in unstable.  i can
reinstall it without any problem.  all done.


> try 
> xserver-xorg-video-fbdev

  same as above.


> and as alast try
> xserver-xorg-video-vesa

  same as above.


> (you may have to edit /etc/X11/xorg.conf and possibly mess with kernel 
> modesetting, initrd and bootime parameters to get an acceptable resolution)
> you'll lose all `acceleration' as usual.
> but it might run more stable.
> no internet or video but ok for text processing(mcedit/pico/nano/vim but not 
> openoffice)

  it hasn't been terribly unstable, just a once in a while hard
lock up.  i'd like to figure out which part is the problem and
not wonder which it might be.

  one reason i run testing is to find issues before they go into
stable.  unfortunately, i'm not as well versed in this sort of
debugging as i'd like to be so i get to learn some new things.  :)

  if i have to get source code and compile it locally with certain
flags for debugging or whatever that is ok with me just so long
as it gets me further along in figuring out what this specific
problem is and what chunk of code it is coming from.


  songbird

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

[Johann Klammer]

On 03/06/2022 09:10 PM, songbird wrote:
> Johann Klammer wrote:
> ...
>> Likely the xorg video driver.
>> Try installing the alternatives possible for your hardware.
>> avoid the closed source nvidias.
>> They've had the hard lock ups since about 2000.
>> nouveau and framebuffer ones will probably work.
> 
> 
>   hi, thanks for the hints, i just have the built in GPU for the CPU:
> 
> 
> # lscpu
> Architecture:x86_64
>   CPU op-mode(s):32-bit, 64-bit
>   Address sizes: 39 bits physical, 48 bits virtual
>   Byte Order:Little Endian
> CPU(s):  8
>   On-line CPU(s) list:   0-7
> Vendor ID:   GenuineIntel
>   BIOS Vendor ID:Intel(R) Corporation
>   Model name:Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
> BIOS Model name: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
> CPU family:  6
> Model:   158
> Thread(s) per core:  1
> Core(s) per socket:  8
> Socket(s):   1
> Stepping:13
> CPU max MHz: 4900.
> CPU min MHz: 800.
> BogoMIPS:7200.00
> Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
> mc
>  a cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
> ss 
>  ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc 
> art
>   arch_perfmon pebs bts rep_good nopl xtopology 
> nonstop_
>  tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor 
> ds_cp
>  l vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid 
> ss
>  e4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer 
> aes 
>  xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
> cpuid_f
>  ault invpcid_single ssbd ibrs ibpb stibp 
> ibrs_enhanced 
>  tpr_shadow vnmi flexpriority ept vpid ept_ad 
> fsgsbase t
>  sc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx 
> rdseed a
>  dx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 
> xsa
>  ves dtherm ida arat pln pts hwp hwp_notify 
> hwp_act_wind
>  ow hwp_epp md_clear flush_l1d arch_capabilities
> Virtualization features: 
>   Virtualization:VT-x
> Caches (sum of all): 
>   L1d:   256 KiB (8 instances)
>   L1i:   256 KiB (8 instances)
>   L2:2 MiB (8 instances)
>   L3:12 MiB (1 instance)
> NUMA:
>   NUMA node(s):  1
>   NUMA node0 CPU(s): 0-7
> 
> 
>   the following shows installed:
> 
> 
> # dpkg -l | grep video-intel
> 
> ii  xserver-xorg-video-intel 2:2.99.917+git20210115-1   
> amd64X.Org X server -- Intel i8xx, i9xx display driver
> 
> 
> # uname -a
> Linux rant 5.16.0-3-amd64 #1 SMP PREEMPT Debian 5.16.11-1 (2022-02-25) x86_64 
> GNU/Linux
> 
> 
> songbird
> 
xserver-xorg-video-intel
update that one. if that doesn't help, 
try 
xserver-xorg-video-fbdev
and as alast try
xserver-xorg-video-vesa
(you may have to edit /etc/X11/xorg.conf and possibly mess with kernel 
modesetting, initrd and bootime parameters to get an acceptable resolution)
you'll lose all `acceleration' as usual.
but it might run more stable.
no internet or video but ok for text processing(mcedit/pico/nano/vim but not 
openoffice)

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

[Vincent Lefevre]

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  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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

[songbird]

Johann Klammer wrote:
...
> Likely the xorg video driver.
> Try installing the alternatives possible for your hardware.
> avoid the closed source nvidias.
> They've had the hard lock ups since about 2000.
> nouveau and framebuffer ones will probably work.


  hi, thanks for the hints, i just have the built in GPU for the CPU:


# lscpu
Architecture:x86_64
  CPU op-mode(s):32-bit, 64-bit
  Address sizes: 39 bits physical, 48 bits virtual
  Byte Order:Little Endian
CPU(s):  8
  On-line CPU(s) list:   0-7
Vendor ID:   GenuineIntel
  BIOS Vendor ID:Intel(R) Corporation
  Model name:Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
BIOS Model name: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
CPU family:  6
Model:   158
Thread(s) per core:  1
Core(s) per socket:  8
Socket(s):   1
Stepping:13
CPU max MHz: 4900.
CPU min MHz: 800.
BogoMIPS:7200.00
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mc
 a cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss 
 ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art
  arch_perfmon pebs bts rep_good nopl xtopology nonstop_
 tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cp
 l vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid ss
 e4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes 
 xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_f
 ault invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced 
 tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase t
 sc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed a
 dx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsa
 ves dtherm ida arat pln pts hwp hwp_notify hwp_act_wind
 ow hwp_epp md_clear flush_l1d arch_capabilities
Virtualization features: 
  Virtualization:VT-x
Caches (sum of all): 
  L1d:   256 KiB (8 instances)
  L1i:   256 KiB (8 instances)
  L2:2 MiB (8 instances)
  L3:12 MiB (1 instance)
NUMA:
  NUMA node(s):  1
  NUMA node0 CPU(s): 0-7


  the following shows installed:


# dpkg -l | grep video-intel

ii  xserver-xorg-video-intel 2:2.99.917+git20210115-1   
amd64X.Org X server -- Intel i8xx, i9xx display driver


# uname -a
Linux rant 5.16.0-3-amd64 #1 SMP PREEMPT Debian 5.16.11-1 (2022-02-25) x86_64 
GNU/Linux


songbird

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

[Johann Klammer]

On 03/06/2022 01:20 PM, songbird wrote:
> 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
> 
Likely the xorg video driver.
Try installing the alternatives possible for your hardware.
avoid the closed source nvidias.
They've had the hard lock ups since about 2000.
nouveau and framebuffer ones will probably work.

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

[songbird]

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