Hi Artur, > 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`? I'm not sure why any of that matters TBH, not all arm machines for example are device tree capable so the cat above will fail. I rand cpufetch across 8 machines and it only returned those bits on 3 of them and on one it didn't even return the third field which was a standard off the shelf arm core. > 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. I suspect upstream needs to generalise the way they deal with some of the pieces, happy to assist with comments upstream. -- _______________________________________________ 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
