| Summary: | Internal buffer too small to read \'/proc/cpuinfo\' | ||
|---|---|---|---|
| Product: | [Applications] ksysguard | Reporter: | Bill <billfleming11> |
| Component: | ksysguard | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | billfleming11 |
| Priority: | NOR | ||
| Version: | 5.16.4 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | Fixed with huge CPUINFOBUFSIZE number. | ||
*** This bug has been marked as a duplicate of bug 384515 *** |
Created attachment 121989 [details] Fixed with huge CPUINFOBUFSIZE number. SUMMARY Ksysguard cannot parse cpu info on CPUs with lots of cores. Cannot see pretty CPU Freq turbo graphs on Ryzen 9. STEPS TO REPRODUCE 1. Buy Ryzen 9 or Threadripper 12 core and above 2. Prevent your wallet from filing divorce papers. (optional) 3. Run Ksysguard 4. Check system log file for errors OBSERVED RESULT Internal buffer too small to read \'/proc/cpuinfo\' EXPECTED RESULT Should be able to see CPU Frequency and add to graph SOFTWARE/OS VERSIONS Linux/KDE Plasma: Latest version compiled on ARCH ADDITIONAL INFORMATION See ./ksysguard/ksysguardd/Linux/cpuinfo.c:43: CPUINFOBUFSIZE For my 3900X CPU it reads about 1504 char per CPU core when you read proc/cpuinfo. While this is fixed by setting a huge number for CPUINFOBUFSIZE I recommend that either you increase the array based on number of CPUs, or use a smaller buffer and re-use it for each CPU. Otherwise the huge size for CPUINFOBUFSIZE to accommodate new CPUs (128 threads) would be a pretty big silly number. After changing CPUINFOBUFSIZE and make install I can see the purdy graph attached. Next stop moar overclocking... Bill