-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CPU-X segfaults with vfio GPU #108
Comments
Hello, can you paste the |
Yes, the CPU-X dump above was obtained with |
Oh, the |
Okay, that worked! Here it is: Setting label names Calling libcpuid for retrieving static data Finding CPU technology Calling libcpuid for retrieving CPU MSR static values Calling dmidecode Finding devices Your GPU driver is unknown: ../../../../../../bus/pci/drivers/vfio-pci Identifying running system Calling libcpuid for retrieving dynamic data Calling libcpuid for retrieving CPU MSR dynamic values Calculating CPU usage Retrieving CPU temperature in fallback mode Calculating CPU multipliers Calling bandwidth Calling libprocps Retrieving GPU clocks Oops, something was wrong! CPU-X has received signal 11 (Segmentation fault) and has crashed. ========================= Backtrace ========================= CPU-X 3.2.4 (Aug 7 2019 13:33:03, Linux x86_64, GNU 9.1.0) # 1 /usr/lib/libc.so.6(+0x3a7e0) [0x7f23803b37e0] # 2 /usr/lib/libc.so.6(+0x160a78) [0x7f23804d9a78] # 3 cpu-x() [0x40d6b8] # 4 cpu-x() [0x40fabf] # 5 cpu-x() [0x40eae2] # 6 cpu-x(fill_labels+0x5e7) [0x410527] # 7 cpu-x(main+0x1824) [0x409864] # 8 /usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7f238039fee3] # 9 cpu-x(_start+0x2e) [0x409d3e] ======================== End Backtrace ======================= |
EDIT: Oops! I forgot to turn off the NVIDIA blacklist. Here's the trace with the NVIDIA driver working. I thought it might be useful for you if I provided a trace with vfio disabled. In this case the GT710 uses the nouveau driver and cpu-x works perfectly. Here's the good trace info: Setting label names Calling libcpuid for retrieving static data Finding CPU technology Calling libcpuid for retrieving CPU MSR static values Calling dmidecode Finding devices Identifying running system Calling libcpuid for retrieving dynamic data Calling libcpuid for retrieving CPU MSR dynamic values Calculating CPU usage Retrieving CPU temperature in fallback mode Calculating CPU multipliers Calling bandwidth Calling libprocps Retrieving GPU clocks Updating benchmark status Dumping data... >>>>>>>>>> CPU <<<<<<<<<< ***** Processor ***** Vendor: AMD Code Name: Ryzen 7 (Matisse) Package: AM4 Technology: 7 nm Voltage: 0.900 V Specification: AMD Ryzen 7 3700X 8-Core Processor Family: 0XF Ext. Family: 0X17 Model: 0X1 Ext. Model: 0X71 Temp.: 61.75°C Stepping: 0 Instructions: HT, MMX(+), SSE(1, 2, 3, 3S, 4.1, 4.2, 4A), AVX(1, 2), FMA(3), AES, CLMUL, RdRand, AMD-V, x86-64 ***** Clocks ***** Core Speed: 2103 MHz Multiplier: x21.1 (22-36) Bus Speed: 99.80 MHz Usage: 3.80 % ***** Cache ***** L1 Data: 8 x 32 kB, 8-way L1 Inst.: 8 x 32 kB, 8-way Level 2: 8 x 512 kB, 8-way Level 3: 32 MB, ***** * ***** Socket(s): 1 Core(s): 8 Thread(s): 16 >>>>>>>>>> Caches <<<<<<<<<< ***** L1 Cache ***** Size: 8 x 32 kB, 8-way associative, 64-bytes line size Speed: 124917.20 MB/s ***** L2 Cache ***** Size: 8 x 512 kB, 8-way associative, 64-bytes line size Speed: 127154.50 MB/s ***** L3 Cache ***** Size: 32 MB, associative, 64-bytes line size Speed: 73486.30 MB/s >>>>>>>>>> Motherboard <<<<<<<<<< ***** Motherboard ***** Manufacturer: ASUSTeK COMPUTER INC. Model: TUF GAMING X570-PLUS Revision: Rev X.0x ***** BIOS ***** Brand: American Megatrends Inc. Version: 1005 Date: 08/01/2019 ROM Size: 64 kB / 16 MB ***** Chipset ***** Vendor: Advanced Micro Devices, Inc. [AMD] Model: FCH LPC Bridge >>>>>>>>>> Memory <<<<<<<<<< ***** Bank 0 ***** Reference: Corsair CMK16GX4M2Z3200C16 , 8192 MB @ 2666 MHz (DIMM DDR4) ***** Bank 1 ***** Reference: - - - - - - - - - - - - - - - - - - - ***** Bank 2 ***** Reference: Corsair CMK16GX4M2Z3200C16 , 8192 MB @ 2666 MHz (DIMM DDR4) ***** Bank 3 ***** Reference: - - - - - - - - - - - - - - - - - - - >>>>>>>>>> System <<<<<<<<<< ***** Operating System ***** Kernel: Linux 5.3.0-rc8-mainline Distribution: Manjaro Linux Hostname: Entropod Uptime: 0 days, 0 hours, 1 minutes, 51 seconds Compiler: cc (GCC) 9.1.0 ***** Memory ***** Used: 1385 MB / 16304 MB Buffers: 439 MB / 16304 MB Cached: 1690 MB / 16304 MB Free: 12789 MB / 16304 MB Swap: 0 MB / 15624 MB >>>>>>>>>> Graphics <<<<<<<<<< ***** Card 0 ***** Vendor: AMD Model: Hawaii PRO [Radeon R9 290/390] Temperature: 43.00°C Usage: 0% GPU clock: 858 MHz Memory clock: 1500 MHz ***** Card 1 ***** Vendor: NVIDIA Model: GK208B [GeForce GT 710] Temperature: 37.00°C Usage: GPU clock: 405 MHz Memory clock: 810 MHz Freeing memory |
Ok, I understand the problem. I think d36e869 should solve this issue (as a workaround). Can you test with the |
Oh wow, fantastic! I just tested it and it works perfectly. It even reports that the NVIDIA GT710 exists, which is awesome. When I run it from the command line, and view the "Graphics" tab, there's a continuous info message stating "Your GPU driver is unknown: ../../../../../../bus/pci/drivers/vfio-pci", but this would help people who wonder why more detailed info isn't being displayed. Thank you very much for fixing the problem so quickly. Do you have a PayPal donation address? As I said I love this program and would be happy to donate to its development. I don't have a lot of money but have $20 in my budget that I donate to worthy Linux projects on a rotating basis like clockwork on the 3rd of every month. I know it's not much, and I give more when I can, but I found if I don't specifically set something aside I end up conveniently forgetting to give anything :) By the way, would it be possible to add more detailed DRAM timing info (RAS, CAS, etc.) to the program? If not do you know of any current programs that I could use? I've never found anything that outputs detailed information and always have to go into the BIOS/UEFI to see it, but then still have to wonder if it's being altered when running the OS. Once again, thank you very much for fixing this problem so quickly. |
Also, can you give me that
Ok, thanks for your feedback. It is improved in b551ecd.
No, I don't. It's very kind of you, but I can't accept donations. I appreciate that, but I don't actively maintain this software, so I prefer you spend your money for an other project.
It was a dream, but I am unable to do that, sorry. After some tests with |
Describe the bug/Expected behavior
I have a Radeon R9 390 GPU running with the mesa driver, and an Nvidia GT710 GPU I use for KVM passtrhough using the vfio driver. When I run cpu-x it crashes with the the following error output:
Additional information
CPU-X dump
The text was updated successfully, but these errors were encountered: