b3rs3rk Posted May 3, 2020 Author Share Posted May 3, 2020 (edited) On 4/28/2020 at 10:00 PM, nisbne said: hi all, as others have mention, my syslog is getting flooded with these error messages, any idea on a fix? i have disable the plugin for now, please let me know if i can supply any other info to assist Apr 29 11:44:52 Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Apr 29 11:44:52 Tower kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs I cannot reproduce the errors. Regrettably, even if I could reproduce them I'm not sure my code is in any way capable of fixing them. I'm only running a utility that comes with the Unraid-Nvidia build. In turn, they are only including a utility that comes with the NVIDIA driver. If it were compiled code that I authored it would be a different story. But I'm only receiving the output of that command to populate the widget data. The impact from running my code should be minimal to say the least. Uninstall my plugin and from the UnRAID console run: watch -n 2 nvidia-smi -q -x If you are still getting the errors in syslog, it begs the question how my code can be at fault. Edited May 3, 2020 by b3rs3rk Quote Link to comment
b3rs3rk Posted May 3, 2020 Author Share Posted May 3, 2020 On 4/27/2020 at 2:48 PM, JesterEE said: Enhancement Request: Can a monitor be added for the PCI Rx and Tx bus speeds reported in the nvidia-smi -q -x command? Is has been reported in the logs here as: <nvidia_smi_log> <gpu id="00000000:0A:00.0"> <pci> <tx_util>320000 KB/s</tx_util> <rx_util>3686000 KB/s</rx_util> </pci> </gpu> </nvidia_smi_log> Thanks! -JesterEE I will look at adding this when I'm finished doing the Intel integration. Shouldn't be difficult and now that individual statistics are selectable users can feel free to disable it if they don't want to display it. Quote Link to comment
Max Posted May 5, 2020 Share Posted May 5, 2020 On 3/15/2020 at 3:56 PM, SuberSeb said: I fixed that. For some reason plugin don't detect my GPU. I just pressed "Default" button and all works. i was experiencing empty stats issue and this fixed it for me. even though it was detecting both my gpu's but as soon as i started my vm it used to stop posting stats for my second gpu which is being used by plex. luckily this fixed it for me. Quote Link to comment
Max Posted May 5, 2020 Share Posted May 5, 2020 22 minutes ago, Max said: i was experiencing empty stats issue and this fixed it for me. even though it was detecting both my gpu's but as soon as i started my vm it used to stop posting stats for my second gpu which is being used by plex. luckily this fixed it for me. looks like i spoke too soon it looks like everytime i run my vm it stop posting gpu stats and it only working once i click on default. but then when vm is shutdown it switch to gpu 0 which was being used by vm cause i clicked on default. so it looks like it will keep posting if i dont maually select gpu 1, here it will keep posting and switch to gpu 1 whenever i run my vm and then switch back to gpu 0 when vm is no longer running but i mainly wanna see stats for gpu 1 as this the gpu that is being used by plex and gpu 0 is for my vm's but this way i wont be able to see stats for gpu1 when vms are not running i will only be able to see stats for it when vm are running and if i do maually select gpu 1 in gpu stats plugin settings then it will stop posting as soons vm start to run and then start posting once again when vm is shutdown. a really weird glitch i guess if am not the only one with this issue. Quote Link to comment
JamesAdams Posted May 7, 2020 Share Posted May 7, 2020 Hello, I would like to know if anyone else still has the problem with the gtx 1050 or we do not see the energy consumption. for the power draw i have "N/A/75W" Is there a solution to fix this? Thanks. Quote Link to comment
Urbanpixels Posted May 8, 2020 Share Posted May 8, 2020 (edited) Hi Guys, I love this plugin but im getting some weird log issues. It's spamming my log every 2 seconds or so, any ideas? i have to disable it to view anything else in my log. May 8 09:20:46 Urbanpixels kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs May 8 09:20:49 Urbanpixels kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] May 8 09:20:49 Urbanpixels kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs May 8 09:20:52 Urbanpixels kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] May 8 09:20:52 Urbanpixels kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs May 8 09:20:54 Urbanpixels kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] May 8 09:20:54 Urbanpixels kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs Edit - Could be something else as i get the errors in the log when uninstalled and running the command above. Edited May 8, 2020 by Urbanpixels Quote Link to comment
b3rs3rk Posted May 8, 2020 Author Share Posted May 8, 2020 Hello, I would like to know if anyone else still has the problem with the gtx 1050 or we do not see the energy consumption. for the power draw i have "N/A/75W" Is there a solution to fix this? Thanks.You can disable that statistic to prevent displaying it but that’s about it. Either the hardware or the driver doesn’t support the polling of the power draw. It stands to reason that buying cheaper cards can mean lesser monitoring features. Quote Link to comment
b3rs3rk Posted May 8, 2020 Author Share Posted May 8, 2020 4 hours ago, Urbanpixels said: Hi Guys, I love this plugin but im getting some weird log issues. It's spamming my log every 2 seconds or so, any ideas? i have to disable it to view anything else in my log. May 8 09:20:46 Urbanpixels kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs May 8 09:20:49 Urbanpixels kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] May 8 09:20:49 Urbanpixels kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs May 8 09:20:52 Urbanpixels kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] May 8 09:20:52 Urbanpixels kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs May 8 09:20:54 Urbanpixels kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] May 8 09:20:54 Urbanpixels kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs Edit - Could be something else as i get the errors in the log when uninstalled and running the command above. What CPU do you have in your system? Quote Link to comment
b3rs3rk Posted May 8, 2020 Author Share Posted May 8, 2020 On 5/5/2020 at 11:07 AM, Max said: looks like i spoke too soon it looks like everytime i run my vm it stop posting gpu stats and it only working once i click on default. but then when vm is shutdown it switch to gpu 0 which was being used by vm cause i clicked on default. so it looks like it will keep posting if i dont maually select gpu 1, here it will keep posting and switch to gpu 1 whenever i run my vm and then switch back to gpu 0 when vm is no longer running but i mainly wanna see stats for gpu 1 as this the gpu that is being used by plex and gpu 0 is for my vm's but this way i wont be able to see stats for gpu1 when vms are not running i will only be able to see stats for it when vm are running and if i do maually select gpu 1 in gpu stats plugin settings then it will stop posting as soons vm start to run and then start posting once again when vm is shutdown. a really weird glitch i guess if am not the only one with this issue. I'm happy to help as this seems like a bug, but I'm afraid I don't understand your post. Quote Link to comment
Max Posted May 8, 2020 Share Posted May 8, 2020 5 hours ago, b3rs3rk said: I'm happy to help as this seems like a bug, but I'm afraid I don't understand your post. yeah i had felling that it was getting a little confusing. okay i try my best to explain it. you see here i have to nvidia GPU's, 0 is gtx 1070 ti which im using for my vm and 1 is gtx 750 for plex hardware transcoding. (i only want to see the stats for gpu 1 i.e. gtx 750) https://imgur.com/a/mGddMgH Now if i select gpu 1 i.e. gtx 750 from the dropdown list of unit ID for dashboard option it will keep posting stats until vm starts, the moment i start the vm all info on dashboard page will go blank and it will only resume posting when i shutdown my vm. Now if i click on this default button (while vm is still running) on gpu stats's page it will shows stats for gpu 1 i.e. gtx 750 but now when i shutdown my vm it will switch back to gpu 0 i.e. gtx 1070 ti cause under unit id for option it has switched back to gpu 0 cause we selected default option earlier, so cause 0 should be default it is now set gpu 0 i.e.e gtx 1070 ti. https://imgur.com/a/YzY4YmW so as long as its set to gpu 0 it will keep posting stats, now ofcourse it wil switch between gpu's whenever vm starts or stops but now atleast its always posting gpu stats. So basically its like this if its set it to gpu 0 it will always show gpu stats, it won't go blank but if i set it to gpu 1 it wont shows stats when the vm's are running. 1 Quote Link to comment
b3rs3rk Posted May 8, 2020 Author Share Posted May 8, 2020 yeah i had felling that it was getting a little confusing. okay i try my best to explain it. you see here i have to nvidia GPU's, 0 is gtx 1070 ti which im using for my vm and 1 is gtx 750 for plex hardware transcoding. (i only want to see the stats for gpu 1 i.e. gtx 750) https://imgur.com/a/mGddMgH Now if i select gpu 1 i.e. gtx 750 from the dropdown list of unit ID for dashboard option it will keep posting stats until vm starts, the moment i start the vm all info on dashboard page will go blank and it will only resume posting when i shutdown my vm. Now if i click on this default button (while vm is still running) on gpu stats's page it will shows stats for gpu 1 i.e. gtx 750 but now when i shutdown my vm it will switch back to gpu 0 i.e. gtx 1070 ti cause under unit id for option it has switched back to gpu 0 cause we selected default option earlier, so cause 0 should be default it is now set gpu 0 i.e.e gtx 1070 ti. https://imgur.com/a/YzY4YmW so as long as its set to gpu 0 it will keep posting stats, now ofcourse it wil switch between gpu's whenever vm starts or stops but now atleast its always posting gpu stats. So basically its like this if its set it to gpu 0 it will always show gpu stats, it won't go blank but if i set it to gpu 1 it wont shows stats when the vm's are running.Okay, I’m on it now. Try starting your VM and then pasting me the result of: nvidia-smi -L Then shutdown the VM and run that command again and paste me this second result. My guess is when you pass the GPU through nvidia-smi can no longer see it. Then GPUID 1 becomes zero. Quote Link to comment
Max Posted May 8, 2020 Share Posted May 8, 2020 12 minutes ago, b3rs3rk said: Okay, I’m on it now. Try starting your VM and then pasting me the result of: nvidia-smi -L Then shutdown the VM and run that command again and paste me this second result. My guess is when you pass the GPU through nvidia-smi can no longer see it. Then GPUID 1 becomes zero. yup you are right, this is with vm is running. root@Unraid:~# nvidia-smi -L GPU 0: GeForce GTX 750 (UUID: GPU-4daa28f9-2851-49be-7240-d485e0fa6aad) no gtx 1070ti. root@Unraid:~# nvidia-smi -L GPU 0: GeForce GTX 1070 Ti (UUID: GPU-b3281921-cd4e-952e-a85c-853c365a663b) GPU 1: GeForce GTX 750 (UUID: GPU-4daa28f9-2851-49be-7240-d485e0fa6aad) and this here when vm is shut nvidia-smi can see both my gou again. i see, so this why gpu stats goes blank when i select gpu 1 and start my vm cause now there is no gpu 1 .😅 Quote Link to comment
b3rs3rk Posted May 8, 2020 Author Share Posted May 8, 2020 (edited) On 5/8/2020 at 5:32 PM, Max said: yup you are right, this is with vm is running. root@Unraid:~# nvidia-smi -LGPU 0: GeForce GTX 750 (UUID: GPU-4daa28f9-2851-49be-7240-d485e0fa6aad) no gtx 1070ti. root@Unraid:~# nvidia-smi -LGPU 0: GeForce GTX 1070 Ti (UUID: GPU-b3281921-cd4e-952e-a85c-853c365a663b)GPU 1: GeForce GTX 750 (UUID: GPU-4daa28f9-2851-49be-7240-d485e0fa6aad) and this here when vm is shut nvidia-smi can see both my gou again. i see, so this why gpu stats goes blank when i select gpu 1 and start my vm cause now there is no gpu 1 . Cool. Let me think on the best way to handle this in code. EDIT: Okay, so I'm going to change the GPU identifier when the nvidia-smi statistics command is run to use the GPU guid instead of the ID number. GUID should never change and I probably should have used that in the first place. Hindsight is 20/20 and all. Probably going to cause a little pain for updaters since the old GPUID will be invalid. Edited May 10, 2020 by b3rs3rk Quote Link to comment
Urbanpixels Posted May 9, 2020 Share Posted May 9, 2020 19 hours ago, b3rs3rk said: What CPU do you have in your system? I have a ryzen 2700x with a Nvidia Quadro P400. Quote Link to comment
b3rs3rk Posted May 10, 2020 Author Share Posted May 10, 2020 On 5/9/2020 at 4:55 AM, Urbanpixels said: I have a ryzen 2700x with a Nvidia Quadro P400. Well nevermind then. I saw some old mailing list traffic about Haswell/Ivy Bridge systems having improper MCH mappings that cause issues like yours. But something else may be causing it. Quote Link to comment
xavc1201 Posted May 10, 2020 Share Posted May 10, 2020 My GPU data is not showing in the dashboard, how can i solve this? Information to Include when asking for Support: ---------------------------------------------------------------------------------------------------------------------------------- 1) the result of 'nvidia-smi -q -x -i 0' from the UnRAID console ---------------------------------------------------------------------------------------------------------------------------------- root@UnRaid:~# nvidia-smi -q -x -i 0 <?xml version="1.0" ?> <!DOCTYPE nvidia_smi_log SYSTEM "nvsmi_device_v10.dtd"> <nvidia_smi_log> <timestamp>Sun May 10 14:10:07 2020</timestamp> <driver_version>440.59</driver_version> <cuda_version>10.2</cuda_version> <attached_gpus>1</attached_gpus> <gpu id="00000000:20:00.0"> <product_name>GeForce GT 730</product_name> <product_brand>GeForce</product_brand> <display_mode>N/A</display_mode> <display_active>N/A</display_active> <persistence_mode>Disabled</persistence_mode> <accounting_mode>N/A</accounting_mode> <accounting_mode_buffer_size>N/A</accounting_mode_buffer_size> <driver_model> <current_dm>N/A</current_dm> <pending_dm>N/A</pending_dm> </driver_model> <serial>N/A</serial> <uuid>GPU-XXX9-b02c-1c4ca42113c8</uuid> <minor_number>0</minor_number> <vbios_version>80.28.78.00.0D</vbios_version> <multigpu_board>N/A</multigpu_board> <board_id>N/A</board_id> <gpu_part_number>N/A</gpu_part_number> <inforom_version> <img_version>N/A</img_version> <oem_object>N/A</oem_object> <ecc_object>N/A</ecc_object> <pwr_object>N/A</pwr_object> </inforom_version> <gpu_operation_mode> <current_gom>N/A</current_gom> <pending_gom>N/A</pending_gom> </gpu_operation_mode> <gpu_virtualization_mode> <virtualization_mode>N/A</virtualization_mode> <host_vgpu_mode>N/A</host_vgpu_mode> </gpu_virtualization_mode> <ibmnpu> <relaxed_ordering_mode>N/A</relaxed_ordering_mode> </ibmnpu> <pci> <pci_bus>20</pci_bus> <pci_device>00</pci_device> <pci_domain>0000</pci_domain> <pci_device_id>128710DE</pci_device_id> <pci_bus_id>00000000:20:00.0</pci_bus_id> <pci_sub_system_id>00000000</pci_sub_system_id> <pci_gpu_link_info> <pcie_gen> <max_link_gen>N/A</max_link_gen> <current_link_gen>N/A</current_link_gen> </pcie_gen> <link_widths> <max_link_width>N/A</max_link_width> <current_link_width>N/A</current_link_width> </link_widths> </pci_gpu_link_info> <pci_bridge_chip> <bridge_chip_type>N/A</bridge_chip_type> <bridge_chip_fw>N/A</bridge_chip_fw> </pci_bridge_chip> <replay_counter>0</replay_counter> <replay_rollover_counter>0</replay_rollover_counter> <tx_util>N/A</tx_util> <rx_util>N/A</rx_util> </pci> <fan_speed>30 %</fan_speed> <performance_state>P0</performance_state> <clocks_throttle_reasons>N/A</clocks_throttle_reasons> <fb_memory_usage> <total>2001 MiB</total> <used>0 MiB</used> <free>2001 MiB</free> </fb_memory_usage> <bar1_memory_usage> <total>N/A</total> <used>N/A</used> <free>N/A</free> </bar1_memory_usage> <compute_mode>Default</compute_mode> <utilization> <gpu_util>N/A</gpu_util> <memory_util>N/A</memory_util> <encoder_util>N/A</encoder_util> <decoder_util>N/A</decoder_util> </utilization> <encoder_stats> <session_count>N/A</session_count> <average_fps>N/A</average_fps> <average_latency>N/A</average_latency> </encoder_stats> <fbc_stats> <session_count>N/A</session_count> <average_fps>N/A</average_fps> <average_latency>N/A</average_latency> </fbc_stats> <ecc_mode> <current_ecc>N/A</current_ecc> <pending_ecc>N/A</pending_ecc> </ecc_mode> <ecc_errors> <volatile> <single_bit> <device_memory>N/A</device_memory> <register_file>N/A</register_file> <l1_cache>N/A</l1_cache> <l2_cache>N/A</l2_cache> <texture_memory>N/A</texture_memory> <texture_shm>N/A</texture_shm> <cbu>N/A</cbu> <total>N/A</total> </single_bit> <double_bit> <device_memory>N/A</device_memory> <register_file>N/A</register_file> <l1_cache>N/A</l1_cache> <l2_cache>N/A</l2_cache> <texture_memory>N/A</texture_memory> <texture_shm>N/A</texture_shm> <cbu>N/A</cbu> <total>N/A</total> </double_bit> </volatile> <aggregate> <single_bit> <device_memory>N/A</device_memory> <register_file>N/A</register_file> <l1_cache>N/A</l1_cache> <l2_cache>N/A</l2_cache> <texture_memory>N/A</texture_memory> <texture_shm>N/A</texture_shm> <cbu>N/A</cbu> <total>N/A</total> </single_bit> <double_bit> <device_memory>N/A</device_memory> <register_file>N/A</register_file> <l1_cache>N/A</l1_cache> <l2_cache>N/A</l2_cache> <texture_memory>N/A</texture_memory> <texture_shm>N/A</texture_shm> <cbu>N/A</cbu> <total>N/A</total> </double_bit> </aggregate> </ecc_errors> <retired_pages> <multiple_single_bit_retirement> <retired_count>N/A</retired_count> <retired_pagelist>N/A</retired_pagelist> </multiple_single_bit_retirement> <double_bit_retirement> <retired_count>N/A</retired_count> <retired_pagelist>N/A</retired_pagelist> </double_bit_retirement> <pending_blacklist>N/A</pending_blacklist> <pending_retirement>N/A</pending_retirement> </retired_pages> <temperature> <gpu_temp>44 C</gpu_temp> <gpu_temp_max_threshold>N/A</gpu_temp_max_threshold> <gpu_temp_slow_threshold>N/A</gpu_temp_slow_threshold> <gpu_temp_max_gpu_threshold>N/A</gpu_temp_max_gpu_threshold> <memory_temp>N/A</memory_temp> <gpu_temp_max_mem_threshold>N/A</gpu_temp_max_mem_threshold> </temperature> <power_readings> <power_state>P0</power_state> <power_management>N/A</power_management> <power_draw>N/A</power_draw> <power_limit>N/A</power_limit> <default_power_limit>N/A</default_power_limit> <enforced_power_limit>N/A</enforced_power_limit> <min_power_limit>N/A</min_power_limit> <max_power_limit>N/A</max_power_limit> </power_readings> <clocks> <graphics_clock>N/A</graphics_clock> <sm_clock>N/A</sm_clock> <mem_clock>N/A</mem_clock> <video_clock>N/A</video_clock> </clocks> <applications_clocks> <graphics_clock>901 MHz</graphics_clock> <mem_clock>800 MHz</mem_clock> </applications_clocks> <default_applications_clocks> <graphics_clock>901 MHz</graphics_clock> <mem_clock>800 MHz</mem_clock> </default_applications_clocks> <max_clocks> <graphics_clock>N/A</graphics_clock> <sm_clock>N/A</sm_clock> <mem_clock>N/A</mem_clock> <video_clock>N/A</video_clock> </max_clocks> <max_customer_boost_clocks> <graphics_clock>N/A</graphics_clock> </max_customer_boost_clocks> <clock_policy> <auto_boost>N/A</auto_boost> <auto_boost_default>N/A</auto_boost_default> </clock_policy> <supported_clocks> <supported_mem_clock> <value>800 MHz</value> <supported_graphics_clock>901 MHz</supported_graphics_clock> <supported_graphics_clock>888 MHz</supported_graphics_clock> <supported_graphics_clock>875 MHz</supported_graphics_clock> <supported_graphics_clock>862 MHz</supported_graphics_clock> <supported_graphics_clock>849 MHz</supported_graphics_clock> <supported_graphics_clock>836 MHz</supported_graphics_clock> <supported_graphics_clock>823 MHz</supported_graphics_clock> <supported_graphics_clock>810 MHz</supported_graphics_clock> <supported_graphics_clock>797 MHz</supported_graphics_clock> <supported_graphics_clock>784 MHz</supported_graphics_clock> <supported_graphics_clock>771 MHz</supported_graphics_clock> <supported_graphics_clock>758 MHz</supported_graphics_clock> <supported_graphics_clock>745 MHz</supported_graphics_clock> <supported_graphics_clock>732 MHz</supported_graphics_clock> <supported_graphics_clock>719 MHz</supported_graphics_clock> <supported_graphics_clock>705 MHz</supported_graphics_clock> <supported_graphics_clock>692 MHz</supported_graphics_clock> <supported_graphics_clock>679 MHz</supported_graphics_clock> <supported_graphics_clock>666 MHz</supported_graphics_clock> <supported_graphics_clock>653 MHz</supported_graphics_clock> </supported_mem_clock> <supported_mem_clock> <value>405 MHz</value> <supported_graphics_clock>405 MHz</supported_graphics_clock> <supported_graphics_clock>402 MHz</supported_graphics_clock> <supported_graphics_clock>400 MHz</supported_graphics_clock> <supported_graphics_clock>398 MHz</supported_graphics_clock> <supported_graphics_clock>396 MHz</supported_graphics_clock> <supported_graphics_clock>394 MHz</supported_graphics_clock> <supported_graphics_clock>392 MHz</supported_graphics_clock> <supported_graphics_clock>390 MHz</supported_graphics_clock> <supported_graphics_clock>388 MHz</supported_graphics_clock> <supported_graphics_clock>386 MHz</supported_graphics_clock> <supported_graphics_clock>384 MHz</supported_graphics_clock> <supported_graphics_clock>382 MHz</supported_graphics_clock> <supported_graphics_clock>380 MHz</supported_graphics_clock> <supported_graphics_clock>378 MHz</supported_graphics_clock> <supported_graphics_clock>376 MHz</supported_graphics_clock> <supported_graphics_clock>374 MHz</supported_graphics_clock> <supported_graphics_clock>372 MHz</supported_graphics_clock> <supported_graphics_clock>370 MHz</supported_graphics_clock> <supported_graphics_clock>368 MHz</supported_graphics_clock> <supported_graphics_clock>366 MHz</supported_graphics_clock> <supported_graphics_clock>364 MHz</supported_graphics_clock> <supported_graphics_clock>361 MHz</supported_graphics_clock> <supported_graphics_clock>359 MHz</supported_graphics_clock> <supported_graphics_clock>357 MHz</supported_graphics_clock> <supported_graphics_clock>355 MHz</supported_graphics_clock> <supported_graphics_clock>353 MHz</supported_graphics_clock> <supported_graphics_clock>351 MHz</supported_graphics_clock> <supported_graphics_clock>349 MHz</supported_graphics_clock> <supported_graphics_clock>347 MHz</supported_graphics_clock> <supported_graphics_clock>345 MHz</supported_graphics_clock> <supported_graphics_clock>343 MHz</supported_graphics_clock> <supported_graphics_clock>341 MHz</supported_graphics_clock> <supported_graphics_clock>339 MHz</supported_graphics_clock> <supported_graphics_clock>337 MHz</supported_graphics_clock> <supported_graphics_clock>335 MHz</supported_graphics_clock> <supported_graphics_clock>333 MHz</supported_graphics_clock> <supported_graphics_clock>331 MHz</supported_graphics_clock> <supported_graphics_clock>329 MHz</supported_graphics_clock> <supported_graphics_clock>327 MHz</supported_graphics_clock> <supported_graphics_clock>325 MHz</supported_graphics_clock> <supported_graphics_clock>323 MHz</supported_graphics_clock> <supported_graphics_clock>321 MHz</supported_graphics_clock> <supported_graphics_clock>318 MHz</supported_graphics_clock> <supported_graphics_clock>316 MHz</supported_graphics_clock> <supported_graphics_clock>314 MHz</supported_graphics_clock> <supported_graphics_clock>312 MHz</supported_graphics_clock> <supported_graphics_clock>310 MHz</supported_graphics_clock> <supported_graphics_clock>308 MHz</supported_graphics_clock> <supported_graphics_clock>306 MHz</supported_graphics_clock> <supported_graphics_clock>304 MHz</supported_graphics_clock> <supported_graphics_clock>302 MHz</supported_graphics_clock> <supported_graphics_clock>300 MHz</supported_graphics_clock> <supported_graphics_clock>298 MHz</supported_graphics_clock> <supported_graphics_clock>296 MHz</supported_graphics_clock> <supported_graphics_clock>294 MHz</supported_graphics_clock> <supported_graphics_clock>292 MHz</supported_graphics_clock> <supported_graphics_clock>290 MHz</supported_graphics_clock> <supported_graphics_clock>288 MHz</supported_graphics_clock> <supported_graphics_clock>286 MHz</supported_graphics_clock> <supported_graphics_clock>284 MHz</supported_graphics_clock> <supported_graphics_clock>282 MHz</supported_graphics_clock> <supported_graphics_clock>280 MHz</supported_graphics_clock> <supported_graphics_clock>278 MHz</supported_graphics_clock> <supported_graphics_clock>275 MHz</supported_graphics_clock> <supported_graphics_clock>273 MHz</supported_graphics_clock> <supported_graphics_clock>271 MHz</supported_graphics_clock> <supported_graphics_clock>269 MHz</supported_graphics_clock> <supported_graphics_clock>267 MHz</supported_graphics_clock> <supported_graphics_clock>265 MHz</supported_graphics_clock> <supported_graphics_clock>263 MHz</supported_graphics_clock> <supported_graphics_clock>261 MHz</supported_graphics_clock> <supported_graphics_clock>259 MHz</supported_graphics_clock> <supported_graphics_clock>257 MHz</supported_graphics_clock> <supported_graphics_clock>255 MHz</supported_graphics_clock> <supported_graphics_clock>253 MHz</supported_graphics_clock> <supported_graphics_clock>251 MHz</supported_graphics_clock> <supported_graphics_clock>249 MHz</supported_graphics_clock> <supported_graphics_clock>247 MHz</supported_graphics_clock> <supported_graphics_clock>245 MHz</supported_graphics_clock> <supported_graphics_clock>243 MHz</supported_graphics_clock> <supported_graphics_clock>241 MHz</supported_graphics_clock> <supported_graphics_clock>239 MHz</supported_graphics_clock> <supported_graphics_clock>237 MHz</supported_graphics_clock> <supported_graphics_clock>235 MHz</supported_graphics_clock> <supported_graphics_clock>232 MHz</supported_graphics_clock> <supported_graphics_clock>230 MHz</supported_graphics_clock> <supported_graphics_clock>228 MHz</supported_graphics_clock> <supported_graphics_clock>226 MHz</supported_graphics_clock> <supported_graphics_clock>224 MHz</supported_graphics_clock> <supported_graphics_clock>222 MHz</supported_graphics_clock> <supported_graphics_clock>220 MHz</supported_graphics_clock> <supported_graphics_clock>218 MHz</supported_graphics_clock> <supported_graphics_clock>216 MHz</supported_graphics_clock> <supported_graphics_clock>214 MHz</supported_graphics_clock> <supported_graphics_clock>212 MHz</supported_graphics_clock> <supported_graphics_clock>210 MHz</supported_graphics_clock> <supported_graphics_clock>208 MHz</supported_graphics_clock> <supported_graphics_clock>206 MHz</supported_graphics_clock> <supported_graphics_clock>204 MHz</supported_graphics_clock> <supported_graphics_clock>202 MHz</supported_graphics_clock> <supported_graphics_clock>200 MHz</supported_graphics_clock> <supported_graphics_clock>198 MHz</supported_graphics_clock> <supported_graphics_clock>196 MHz</supported_graphics_clock> <supported_graphics_clock>194 MHz</supported_graphics_clock> <supported_graphics_clock>192 MHz</supported_graphics_clock> <supported_graphics_clock>189 MHz</supported_graphics_clock> <supported_graphics_clock>187 MHz</supported_graphics_clock> <supported_graphics_clock>185 MHz</supported_graphics_clock> <supported_graphics_clock>183 MHz</supported_graphics_clock> <supported_graphics_clock>181 MHz</supported_graphics_clock> <supported_graphics_clock>179 MHz</supported_graphics_clock> <supported_graphics_clock>177 MHz</supported_graphics_clock> <supported_graphics_clock>175 MHz</supported_graphics_clock> <supported_graphics_clock>173 MHz</supported_graphics_clock> <supported_graphics_clock>171 MHz</supported_graphics_clock> <supported_graphics_clock>169 MHz</supported_graphics_clock> <supported_graphics_clock>167 MHz</supported_graphics_clock> <supported_graphics_clock>165 MHz</supported_graphics_clock> <supported_graphics_clock>163 MHz</supported_graphics_clock> <supported_graphics_clock>161 MHz</supported_graphics_clock> <supported_graphics_clock>159 MHz</supported_graphics_clock> <supported_graphics_clock>157 MHz</supported_graphics_clock> <supported_graphics_clock>155 MHz</supported_graphics_clock> <supported_graphics_clock>153 MHz</supported_graphics_clock> <supported_graphics_clock>151 MHz</supported_graphics_clock> <supported_graphics_clock>149 MHz</supported_graphics_clock> <supported_graphics_clock>146 MHz</supported_graphics_clock> <supported_graphics_clock>144 MHz</supported_graphics_clock> <supported_graphics_clock>142 MHz</supported_graphics_clock> <supported_graphics_clock>140 MHz</supported_graphics_clock> <supported_graphics_clock>138 MHz</supported_graphics_clock> <supported_graphics_clock>136 MHz</supported_graphics_clock> </supported_mem_clock> </supported_clocks> <processes>N/A</processes> <accounted_processes>N/A</accounted_processes> </gpu> </nvidia_smi_log> ---------------------------------------------------------------------------------------------------------------------------------- 2) the result of 'cd /usr/local/emhttp/plugins/gpustat/ && php ./gpustatus.php' ---------------------------------------------------------------------------------------------------------------------------------- {"vendor":"NVIDIA","name":"GeForce GT 730","clock":"N\/A","memclock":"N\/A","util":"N\/A","memutil":"N\/A","encutil":"N\/A","decutil":"N\/A","temp":"44C","tempmax":"N\/A","fan":"30%","perfstate":"P0","throttled":"No","thrtlrsn":"","power":"N\/A","powermax":"N\/A","sessions":0}root@UnRaid:/usr/local/emhttp/plugins/gpustat# ---------------------------------------------------------------------------------------------------------------------------------- 3) a screenshot of the dashboard plugin. / and a screenshot form my main dashboard ---------------------------------------------------------------------------------------------------------------------------------- https://drive.google.com/open?id=16RvJLvCoo4o_EsGgBBmmqlYlinWoWXBw https://drive.google.com/open?id=16Sn16l-VC10jwnhp0vQq9t1_FBwQWCRj Quote Link to comment
Unixsystem Posted May 13, 2020 Share Posted May 13, 2020 (edited) I too am also getting spammed with: May 13 09:44:28 Tank kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs May 13 09:44:31 Tank kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] but, I tried to uncheck some of the polling options to see if a particular one maybe causing it, but no matter how many I uncheck or which ones, it automatically goes back to all of them being checked. UPDATE: Ok I figured it out, it has to do with power states and this query waking up the display. Setting nvidia-smi --persistence-mode=1 will fix the issue, to keep the gpu initialized. I noticed when looking at the state, it was always in a P0, state with persistent mode on, it allowed it to drop to P8. (This is for a quadro p2000, btw) Edited May 21, 2020 by Unixsystem 1 Quote Link to comment
Can0n Posted May 23, 2020 Share Posted May 23, 2020 (edited) Hello @b3rs3rk I was wondering if you plan in implenting Intel Integated GPU for the I3/5/7/9 etc. I use a docker called Intel GPOU tools for now but to have this on the dashboard would be awesome I'm currently using Intel Quick Sync for both unraid servers (i5 8600K and i7 7700K) running two Plex servers and would be nice at a glance to see the health and stats I would be interested in a beta test if you need guinea pigs Edited May 23, 2020 by Can0nfan grammer Quote Link to comment
b3rs3rk Posted June 3, 2020 Author Share Posted June 3, 2020 On 5/23/2020 at 3:22 AM, Can0nfan said: Hello @b3rs3rk I was wondering if you plan in implenting Intel Integated GPU for the I3/5/7/9 etc. I use a docker called Intel GPOU tools for now but to have this on the dashboard would be awesome I'm currently using Intel Quick Sync for both unraid servers (i5 8600K and i7 7700K) running two Plex servers and would be nice at a glance to see the health and stats I would be interested in a beta test if you need guinea pigs It's mostly developed how I think it should work, but I have no way to test any of it. I'm trying to get remote access to a friend's UnRAID with an iGPU so that I can test pushing the code to it and see how the Intel stuff functions. I'm not a professional developer, so diagnosing this stuff based on user reporting isn't my forte. Just kind of hard to do. Quote Link to comment
sp3cialk Posted June 17, 2020 Share Posted June 17, 2020 On 5/8/2020 at 4:25 AM, Urbanpixels said: Hi Guys, I love this plugin but im getting some weird log issues. It's spamming my log every 2 seconds or so, any ideas? i have to disable it to view anything else in my log. May 8 09:20:46 Urbanpixels kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs May 8 09:20:49 Urbanpixels kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] May 8 09:20:49 Urbanpixels kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs May 8 09:20:52 Urbanpixels kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] May 8 09:20:52 Urbanpixels kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs May 8 09:20:54 Urbanpixels kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] May 8 09:20:54 Urbanpixels kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs Edit - Could be something else as i get the errors in the log when uninstalled and running the command above. Getting this same issue. I've resorted to uninstalling the plugin as it just seems to fill my log up with these. As soon as I remove the plug-in my log pretty much sits at like 1-4% depending on last reboot. 13 days as of now and no erroneous logs like above. CPU - Ryzen 3700x GPU - Quadro P2000 Any suggestions, really like this plug-in but don't want spam in my logs Quote Link to comment
b3rs3rk Posted July 2, 2020 Author Share Posted July 2, 2020 (edited) On 6/17/2020 at 1:52 AM, sp3cialk said: Getting this same issue. I've resorted to uninstalling the plugin as it just seems to fill my log up with these. As soon as I remove the plug-in my log pretty much sits at like 1-4% depending on last reboot. 13 days as of now and no erroneous logs like above. CPU - Ryzen 3700x GPU - Quadro P2000 Any suggestions, really like this plug-in but don't want spam in my logs My suggestion is to update your BIOS, change to Legacy boot if currently UEFI (if possible), or switch the physical slot your GPU is in and see if the problem goes away. The issue is your build parameters, not my plugin. The only other option would be to figure out a way to squelch that log. Maybe a combination of using this script and creating a custom .conf file to remove the offending log messages. If anyone wants to try it, create a file (02-barmappingblock.conf) in /etc/rsyslog.d/ that contains: :msg,contains,"mapping multiple BARs" stop :msg,contains,"which spans more than PCI Bus" stop Then do a: /etc/rc.d/rc.rsyslogd restart > /dev/null If it works, then copy that .conf file to the location the script suggestions, and then add it to your startup scripts when UnRAID boots. It's not a 'fix' per se, but a kernel/driver issue can't be fixed by myself or the linuxserver folks. Edited July 2, 2020 by b3rs3rk Add command 1 Quote Link to comment
tlmmy Posted July 12, 2020 Share Posted July 12, 2020 Hi, does anyone know how to change the refresh timing on the widget? Mine works but the stats doesn't change until I refresh my browser. Or do I need to do something else to clear cache? Thank you in advance! Quote Link to comment
BradJ Posted July 13, 2020 Share Posted July 13, 2020 Due to the constant spamming of the logs I also had to uninstall this plugin. Otherwise I loved this plugin. What a shame. Tower kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff] Quote Link to comment
b3rs3rk Posted July 13, 2020 Author Share Posted July 13, 2020 Due to the constant spamming of the logs I also had to uninstall this plugin. Otherwise I loved this plugin. What a shame. Tower kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff] Two posts up I show a potential way to squelch those logs. Did you attempt it? Quote Link to comment
b3rs3rk Posted July 13, 2020 Author Share Posted July 13, 2020 Hi, does anyone know how to change the refresh timing on the widget? Mine works but the stats doesn't change until I refresh my browser. Or do I need to do something else to clear cache? Thank you in advance!I would have to add it. It is currently hard coded in the page JavaScript. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.