June 16, 20242 yr Hi, I have recently updated a friends server from 6.9.2 to 6.12.10 and have started getting full system hangs, around once per day since. Yesterday I made many changes to the system as per this thread. Overnight, instead of totally hanging, the server survived (partially) and I only had one app that wasn't functioning correctly (Frigate due to the TPU drivers not being loaded). I've checked the logs and it looks like there are multiple OOM errors, unfortunately I just cannot read/understand them. I was hoping someone may be able to help interpret them? home43-diagnostics-20240616-1008.zip
June 16, 20242 yr Community Expert OOM issues appear to have been caused by ffmpge, so try stopping the container that uses it, and re-test.
June 16, 20242 yr Author 25 minutes ago, JorgeB said: OOM issues appear to have been caused by ffmpge, so try stopping the container that uses it, and re-test. Thanks for the reply @JorgeB, unfortunately that container/app is Frigate, which is my CCTV system and I can't turn it off.... Would you have any suggestions of what I can try that would allow me to keep it running? Below is the extra args I have for that: --shm-size=512mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 --restart unless-stopped --gpus=all --memory=8G I've got the media (saved files) going directly to the disk & not using fuse; /mnt/disk4/media/frigate
June 16, 20242 yr Community Expert 36 minutes ago, DrSpaldo said: target=/tmp/cache This is going to RAM so map that to a disk, too
June 16, 20242 yr Author 47 minutes ago, Michael_P said: This is going to RAM so map that to a disk, too Thanks for the reply @Michael_P. I think that’s 1 gig of RAM for the temp cache, I’m happy to use a gig on that to reduce the HDD wear. I’ve currently got 64 gigs with the system using 33%. So plenty free?
June 16, 20242 yr Community Expert 3 minutes ago, DrSpaldo said: So plenty free? Considering it was using ~12GB when it was killed, I'm going to say no
June 16, 20242 yr Author 2 minutes ago, Michael_P said: Considering it was using ~12GB when it was killed, I'm going to say no Interesting. If it were using 12 gigs, that’s way more than it should be. Currently it’s sitting at about 5 gigs on the docker page, earlier today it was closer to 4 gigs. Using 12 gigs though, should still have 30+ free in the system. So do you think regardless I should change that tmpfs map to a drive and not ram?
June 16, 20242 yr Community Expert Just now, DrSpaldo said: So do you think regardless I should change that tmpfs map to a drive and not ram? Worth testing for a period of time to verify. There's been a few other users of frigate here reporting the same OOM events
June 16, 20242 yr Author Yep, there are quite a few that I’ve searched for, most are slightly different and without any definitive answer unfortunately. I’m happy to give anything a go though, I can’t have the machine crashing every day. how exactly would I change that extra args to be on the drive instead of ram?
June 16, 20242 yr Community Expert Just now, DrSpaldo said: how exactly would I change that extra args to be on the drive instead of ram? Map it in the container settings like you would any other path
June 16, 20242 yr Author 1 minute ago, Michael_P said: Map it in the container settings like you would any other path Ah ok, so not in the extra args part. Thanks
June 17, 20242 yr Author Totally locked up / crashed again this morning. I physically pulled out the USB and just took the log from it. Couldn't connect via web/ssh or even ping the server this time. Prior to this, I increased the Frigate container ram limit to 16gb, increased the shm size from 512meg to 1gb. See attached log. I am currently running memtest86 to see if there are any ram issues. If that is fine, the next step is to remove the hardware acceleration from Frigate's config and then I will also try putting that tmpfs to disk. 2024-06-17 syslog.zip Edited June 17, 20242 yr by DrSpaldo Forgot to attach logs
June 17, 20242 yr Community Expert 6 hours ago, DrSpaldo said: I am currently running memtest86 to see if there are any ram issues OOMs aren't hardware related, it isn't hard to see what's causing it Jun 16 15:30:58 Home43 kernel: [ 474] 0 474 328006 34440 569344 0 0 frigate.logger Jun 16 15:30:58 Home43 kernel: [ 476] 0 476 553572 46644 995328 0 0 frigate.recordi Jun 16 15:30:58 Home43 kernel: [ 485] 0 485 562259 36658 782336 0 0 frigate.review_ Jun 16 15:30:58 Home43 kernel: [ 507] 0 507 3658 1320 65536 0 0 python3 Jun 16 15:30:58 Home43 kernel: [ 508] 0 508 483514 39732 696320 0 0 frigate.detecto Jun 16 15:30:58 Home43 kernel: [ 510] 0 510 1428766 53321 1404928 0 0 frigate.output Jun 16 15:30:58 Home43 kernel: [ 534] 0 534 31705 1753 155648 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 539] 0 539 31705 1753 163840 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 544] 0 544 31705 1752 167936 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 549] 0 549 31705 2157 167936 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 554] 0 554 31705 1249 167936 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 560] 0 560 31705 1704 163840 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 565] 0 565 31705 1672 163840 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 570] 0 570 31705 1753 163840 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 575] 0 575 31705 1753 167936 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 580] 0 580 31705 1734 163840 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 585] 0 585 31705 1753 167936 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 590] 0 590 31705 1752 163840 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 595] 0 595 46919 16988 315392 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 650] 0 650 629123 75729 1126400 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 654] 0 654 629247 75284 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 664] 0 664 629123 75770 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 674] 0 674 629123 75542 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 683] 0 683 629123 75769 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 691] 0 691 629123 75760 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 699] 0 699 629123 75771 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 707] 0 707 629247 75431 1110016 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 715] 0 715 629247 75410 1110016 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 723] 0 723 629247 75585 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 731] 0 731 629123 75891 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 739] 0 739 629251 76011 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 745] 0 745 612789 75694 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 748] 0 748 612789 75407 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 751] 0 751 2442947 70314 868352 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 754] 0 754 612789 75626 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 755] 0 755 2442911 70436 864256 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 760] 0 760 612789 75985 1040384 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 761] 0 761 32336 2488 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 762] 0 762 2442927 69623 872448 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 765] 0 765 32991 3603 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 768] 0 768 612789 75653 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 769] 0 769 32317 3406 180224 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 774] 0 774 612789 75632 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 775] 0 775 32339 2887 184320 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 779] 0 779 33047 3988 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 781] 0 781 33042 3370 200704 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 784] 0 784 32811 2929 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 785] 0 785 2442893 69050 856064 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 786] 0 786 612778 75650 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 791] 0 791 32824 2797 184320 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 794] 0 794 612789 75522 1040384 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 795] 0 795 2442932 70520 860160 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 799] 0 799 122241 9344 364544 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 803] 0 803 32748 3441 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 804] 0 804 612789 75369 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 805] 0 805 32979 3766 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 812] 0 812 36614 7777 217088 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 815] 0 815 32341 3390 192512 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 816] 0 816 612789 75666 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 818] 0 818 2442945 70476 864256 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 819] 0 819 33229 4339 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 824] 0 824 33508 4081 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 826] 0 826 612789 75662 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 829] 0 829 37108 7828 221184 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 830] 0 830 2442947 70669 860160 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 834] 0 834 32322 2207 176128 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 835] 0 835 32818 2935 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 841] 0 841 33018 3106 200704 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 842] 0 842 612814 75715 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 843] 0 843 2442931 70143 868352 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 848] 0 848 35767 6157 217088 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 849] 0 849 1383268 89979 1748992 0 0 frigate.audio_m Jun 16 15:30:58 Home43 kernel: [ 850] 0 850 2443013 70426 872448 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 851] 0 851 32338 2886 180224 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 859] 0 859 33307 3585 204800 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 860] 0 860 32339 2488 184320 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 861] 0 861 32865 3592 184320 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 870] 0 870 33007 3800 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 874] 0 874 33005 2985 200704 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 877] 0 877 32793 2813 180224 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 879] 0 879 33120 4010 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 885] 0 885 32771 3313 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 887] 0 887 32969 3445 192512 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 897] 0 897 32635 2277 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 906] 0 906 33060 4121 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 916] 0 916 33114 3730 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 932] 0 932 32850 3443 192512 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 933] 0 933 32809 3060 192512 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 942] 0 942 32801 2304 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 955] 0 955 33015 3475 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 964] 0 964 32887 2927 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 23297] 0 23297 2405543 36872 569344 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 23299] 0 23299 32316 2671 192512 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 5484] 0 5484 3624 1892 65536 0 0 python3 Jun 16 15:30:58 Home43 kernel: [ 8979] 0 8979 2405413 65540 827392 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 19516] 0 19516 3247086 879208 7319552 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 19518] 0 19518 32369 2330 180224 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 22768] 0 22768 33053 3515 200704 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 2587] 0 2587 622 217 40960 0 0 sleep Jun 16 15:30:58 Home43 kernel: [ 3744] 0 3744 622 216 40960 0 0 sleep And it looks like one of your containers is going up and down repeatedly which may be related to any memory limits you've set Jun 17 09:54:52 Home43 kernel: br-191c7978c3a3: port 5(veth11b8ae4) entered blocking state Jun 17 09:54:52 Home43 kernel: br-191c7978c3a3: port 5(veth11b8ae4) entered forwarding state Jun 17 09:54:57 Home43 kernel: veth0844f4a: renamed from eth0 Jun 17 09:54:57 Home43 kernel: br-191c7978c3a3: port 5(veth11b8ae4) entered disabled state Jun 17 09:54:57 Home43 kernel: br-191c7978c3a3: port 5(veth11b8ae4) entered disabled state Jun 17 09:54:57 Home43 kernel: device veth11b8ae4 left promiscuous mode Jun 17 09:54:57 Home43 kernel: br-191c7978c3a3: port 5(veth11b8ae4) entered disabled state Jun 17 09:55:28 Home43 kernel: device eth0 entered promiscuous mode Jun 17 09:55:39 Home43 kernel: device eth0 left promiscuous mode
June 17, 20242 yr Author Thanks for the reply @Michael_P. I wish all of that mean't as much to me as it did to you. I think that Frigate is the cause. Now I just have to work with them I guess to find out what is going on, hopefully someone over there may be able to help. So far, it seems it may be related to having nvidia hardware acceleration turned on. It isn't anywhere near as bad leaking/using ram without that turned on. Regarding your second part of the post, I have even less idea what that means. What is the container that keeps going up & down? Currently it is this that keeps repeating itself in the logs: Jun 17 19:59:11 Home43 kernel: eth0: renamed from veth356a5b4 Jun 17 19:59:11 Home43 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6ce0dbf: link becomes ready Jun 17 19:59:11 Home43 kernel: br-191c7978c3a3: port 5(veth6ce0dbf) entered blocking state Jun 17 19:59:11 Home43 kernel: br-191c7978c3a3: port 5(veth6ce0dbf) entered forwarding state Jun 17 19:59:16 Home43 kernel: br-191c7978c3a3: port 5(veth6ce0dbf) entered disabled state Jun 17 19:59:16 Home43 kernel: veth356a5b4: renamed from eth0 Jun 17 19:59:16 Home43 kernel: br-191c7978c3a3: port 5(veth6ce0dbf) entered disabled state Jun 17 19:59:16 Home43 kernel: device veth6ce0dbf left promiscuous mode Jun 17 19:59:16 Home43 kernel: br-191c7978c3a3: port 5(veth6ce0dbf) entered disabled state Jun 17 20:00:16 Home43 kernel: br-191c7978c3a3: port 5(veth70cdb5a) entered blocking state Jun 17 20:00:16 Home43 kernel: br-191c7978c3a3: port 5(veth70cdb5a) entered disabled state Jun 17 20:00:16 Home43 kernel: device veth70cdb5a entered promiscuous mode Jun 17 20:00:16 Home43 kernel: br-191c7978c3a3: port 5(veth70cdb5a) entered blocking state Jun 17 20:00:16 Home43 kernel: br-191c7978c3a3: port 5(veth70cdb5a) entered forwarding state Jun 17 20:00:16 Home43 kernel: br-191c7978c3a3: port 5(veth70cdb5a) entered disabled state Jun 17 20:00:17 Home43 kernel: eth0: renamed from vethdb7f9e1 Jun 17 20:00:17 Home43 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth70cdb5a: link becomes ready Jun 17 20:00:17 Home43 kernel: br-191c7978c3a3: port 5(veth70cdb5a) entered blocking state Jun 17 20:00:17 Home43 kernel: br-191c7978c3a3: port 5(veth70cdb5a) entered forwarding state Jun 17 20:00:21 Home43 kernel: vethdb7f9e1: renamed from eth0 Jun 17 20:00:21 Home43 kernel: br-191c7978c3a3: port 5(veth70cdb5a) entered disabled state Jun 17 20:00:21 Home43 kernel: br-191c7978c3a3: port 5(veth70cdb5a) entered disabled state Jun 17 20:00:21 Home43 kernel: device veth70cdb5a left promiscuous mode Jun 17 20:00:21 Home43 kernel: br-191c7978c3a3: port 5(veth70cdb5a) entered disabled state Edited June 17, 20242 yr by DrSpaldo add the syslog
June 17, 20242 yr Community Expert 11 minutes ago, DrSpaldo said: What is the container that keeps going up & down? Check on the containers page, look at the uptime - should be the one(s) with less than a minute uptime
June 18, 20242 yr Author Turns out that crashing container was a relic from one of my stacks. It was one that was no longer used but had not been removed from the system. However, it appears just a bonus in the logs, it wasn't related to the crashing. At this early stage, I have the most uptime so far, and main change I made was removing nvidia hardware acceleration from Frigate. I swapped back to qsv/vaapi instead and the ram is holding steady. When the nvidia hardware acceleration was enabled, the ram continued to grow and grow until it overloaded the system. Despite there being a docker ram limit, it just went beyond the limit and consumed all system resources. I should know in the next few days if that was the issue, but for now it looks that way....
June 18, 20242 yr Community Expert 23 minutes ago, DrSpaldo said: main change I made was removing nvidia hardware acceleration from Frigate There was a bunch of nvidia related errors in the log, too - maybe check with frigate's community to see if it's the issue Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:12 Home43 kernel: x86/PAT: frigate.detecto:4054 map pfn RAM range req uncached-minus for [mem 0x62a3b4000-0x62a3b7fff], got write-back
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.