On Tue, Sep 03, 2024 at 09:20:24AM -0000, Artur Frenszek-Iwicki wrote: > Hi all, > > I maintain the cpufetch package [0], which is a program that allows the > user to retrieve some info about the CPU of the machine - such as cache > size, frequency, sometimes also the manufacturer and model. > > A few weeks ago, the program had a new release and I updated the package. > However, the build failed on aarch64. After a little bit of debugging, > I was able to locate and patch the code responsible. > > After submitting the bug upstream [1], the developer asked if I was > able to provide some information regarding the machine where > I observed the crash. > > > what machine are we talking about in this case? Model? > > Also, what is the output of `cpufetch --verbose`? > > `cat /proc/device-tree/compatible`? > > Anything that could be indicating the model under `lspci -nn`? > > Looking at the build history in koji, my builds ran on: > - buildhw-a64-03.iad2.fedoraproject.org > - buildvm-a64-04.iad2.fedoraproject.org > - buildhw-a64-24.iad2.fedoraproject.org > - buildvm-a64-09.iad2.fedoraproject.org > - buildvm-a64-06.iad2.fedoraproject.org > > I'd be grateful if someone knowledgeable about infra could answer > the questions above. I don't know about the VMs, but information > about the two hardware builders could be very useful. If you have a link to the build, there is a hw_info.log file which contains some CPU info (but not the device tree). eg: https://koji.fedoraproject.org/koji/buildinfo?buildID=2531880 -> https://kojipkgs.fedoraproject.org//packages/cpufetch/1.06/1.fc40/data/logs/aarch64/hw_info.log (It looks like it possibly comes from 'lscpu', 'free' and 'df') Rich. > Thanks in advance, > A.FI. > > [0] https://src.fedoraproject.org/rpms/cpufetch > [1] https://github.com/Dr-Noob/cpufetch/issues/264 > -- > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
