> This is a very poor bug report because it does not list the hardware details of the machine.
yes, it's a discussion. When I get to know more details I'll file a bug report. For example is it really "libinput"?
> What is the output from "uname -a"?
[alsadi@laptop ~]$ uname -r
4.18.10-200.fc28.x86_64
[alsadi@laptop ~]$ uname -a
Linux laptop.local 4.18.10-200.fc28.x86_64 #1 SMP Wed Sep 26 09:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
4.18.10-200.fc28.x86_64
[alsadi@laptop ~]$ uname -a
Linux laptop.local 4.18.10-200.fc28.x86_64 #1 SMP Wed Sep 26 09:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> What is one section of "cat /proc/cpuinfo"?
it's 4-th gen i7-4710MQ CPU
processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz
stepping : 3
microcode : 0x25
cpu MHz : 1339.496
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 3
cpu cores : 4
apicid : 7
initial apicid : 7
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips : 4988.65
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz
stepping : 3
microcode : 0x25
cpu MHz : 1339.496
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 3
cpu cores : 4
apicid : 7
initial apicid : 7
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips : 4988.65
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
> How much RAM? (The first 5 lines of /proc/meminfo .)
I've 16GB of RAM and 8GB of swap on spin disks (no SSDs)
at the moment
$ head /proc/meminfo
MemTotal: 16299908 kB
MemFree: 8227004 kB
MemAvailable: 11423928 kB
Buffers: 287440 kB
Cached: 3541396 kB
MemTotal: 16299908 kB
MemFree: 8227004 kB
MemAvailable: 11423928 kB
Buffers: 287440 kB
Cached: 3541396 kB
but when the problem happens (tracker-miner is running all memory is used and swap is utilized)
> The initial cause is a hardware failure [intermittent], but the software is not robust enough to recover.
there should be a workaround, maybe rate limiting? a condition to drop such signals? what was the workaround before libinput?
On Thu, Oct 25, 2018 at 5:33 PM John Reiser <jreiser@xxxxxxxxxxxx> wrote:
On 10/25/18 11:27 UTC, Muayyad AlSadi wrote:
> There are some things that makes my machine to freeze [[snip]]
This is a very poor bug report because it does not list the hardware details
of the machine.
What is the output from "uname -a"? What is one section of "cat /proc/cpuinfo"?
How much RAM? (The first 5 lines of /proc/meminfo .)
For instance, the RaspberryPi model 2B is subject to hardware(+software) failures
of exactly the ilk mentioned: a USB-connected keyboard decides to send
"infinitely many" repetitions of the same character, as fast as it can.
The initial cause is a hardware failure [intermittent], but the software
is not robust enough to recover.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
