[Support]: N150 computer restarts bacause of frigate & openvino #20912
Replies: 7 comments 14 replies
-
|
Many users are running with the OpenVINO detector, so this is not likely to be a Frigate bug. We'll need to see Frigate logs and host logs in order to be able to help further. |
Beta Was this translation helpful? Give feedback.
-
|
Frigate logs. The error messages about crashing ffmpeg were 15-17 minutes before the restart, so probably unrelated: Host logs. Nothing preceding the reboot. Then normal booting logs follow. |
Beta Was this translation helpful? Give feedback.
-
|
Right, there's not much to go on here, unfortunately. Many users run the N150 without issue, and this isn't anything we can reproduce. Without more info I'm not sure what can be done. |
Beta Was this translation helpful? Give feedback.
-
|
Something is wrong with frigate. How is it possible that openvino running detections on GPU consumes 0% of it, and then suddenly starts using 50+%? And exactly then restarts happen. 
Nothing changes in cameras' settings or the landscape they look at. |
Beta Was this translation helpful? Give feedback.
-
|
This is due to a known bug in Intel's GPU stats, so when the computer restarts the stats show correctly. It is not actually using 0% of the GPU during that time |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, but if you look closely, the GPU stats go >0% right before the restart. Then the restart happens. It does not look as a coincidence, as it happens every time the unexpected restart happens. |
Beta Was this translation helpful? Give feedback.
-
|
There are a large number of users running YOLOv9 with Intel iGPU without any problems, there is no reason to think this has anything to do with Frigate and is not a machine specific issue. You haven't really provided anything other than anecdotal timing information. What would help figure out what is going on is information like journalct, dmesg, etc. |
Beta Was this translation helpful? Give feedback.
-
|
There are large number of users running beta softwares and doing fine. It still does not mean that the soft is production ready for every use case. I appreciate you stand for software you contribute to, but let's face reality.
Regarding troubleshooting: there is no journalct in HAOS. Dmesg output attached. In the meantime I think I will give a try to Scrypted - it seems to also have people detections and probably is more mature product. |
Beta Was this translation helpful? Give feedback.
-
That just points to running the GPU causes this, it does not mean something is wrong with Frigate itself. We have seen plenty of reports over the years of running OpenVINO to cause computers to restart. Oftentimes things like BIOS settings, kernel updates, etc fixed the issue after seeing in dmesg that it was a host problem. It was not something wrong with Frigate itself. Feel free to use something else, it makes no difference to me, just trying to make it clear how these things are working under the hood, because you seem to be making some incorrect assumptions |
Beta Was this translation helpful? Give feedback.
-
|
Indeed, many people complain over the Internet on openvino causing restarts while running on Intel GPUs. But openvino is not "my" package - it comes with Frigate. For me it means it is Frigate issue. Just to explain my POV. Nevertheless it does not bring us any closer to a solution. I give up for now until I discover anything new (then I will share for community benefit). Happy to hear anyone who had similar issue and got it resolved. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, running HA OS you don't have much control, you're subject to whatever kernel and drivers are installed in that image. |
Beta Was this translation helpful? Give feedback.
-
|
It really seems like there’s some kind of pattern with 12th-gen iGPUs and instability in Frigate, or possibly OpenVINO itself, or even Intel Driver itself. I opened a discussion about this before and eventually accepted that it might be a hardware-specific quirk. I also found a few similar issues on Reddit, especially from users with N150-based mini PCs, showing the same kind of random crashes when running Frigate. Hard to say what the root cause is because it could be a mix of factors. For what it’s worth, I ran multiple stress tests on Windows (CPU/GPU) and the machine was completely stable there. The issues only appear when running Frigate OpenVINO. |
Beta Was this translation helpful? Give feedback.
-
|
The Linux driver stack is different to windows, so those directly aren't really comparable N150 is also a bit of a different case because it is newer and requires a newer kernel, different from 12th Gen in general which I know @hawkeye217 runs without issues |
Beta Was this translation helpful? Give feedback.
-
|
Correct. My 12th gen iGPU is an i7-12650H and there are no issues at all with OpenVINO on a stock Debian 12 install. |
Beta Was this translation helpful? Give feedback.
-
|
I made several stress tests on Ubuntu without any issues, yet probably also not the same drivers/kernel as the ones in HA OS. |
Beta Was this translation helpful? Give feedback.
-
|
It's difficult to see how Frigate is supposed to prevent bugs in an Intel-developed library on an Intel CPU. You could just as likely blame the Linux kernel or cheaper hardware that's not designed to run high-utilisation workloads for extended periods of time. I don't have an N150 (using an i5-10500t) but I did find OpenVINO crashed sporadically when I tried it with a pile of 4k cameras. For me, disabling Intel turboboost seemed to resolve it, and had the pleasant side-effect of reducing temps and power consumption. Might be worth a go (assuming it applies to the N150 family)...
|
Beta Was this translation helpful? Give feedback.
-
|
Well, Frigate could stop recommending hardware/software setup known for causing issues with no clear root cause and solution
Even better, Frigate could thoroughly test and then "certify" hardware and OS version to run it in. I purchased hardware recommended in docs, installed it according to docs, paid for Frigate+. Now all I have are the issues. Luckily I have decided to have physical NVR and not to go all in Frigate. My "cheaper hardware" runs Valley benchmark utilizing 100% GPU plus some math calculations consuming all 4 CPU cores for 30+ minutes not even sweating (~72°C on chip). Anyway, thank for the hint about turbo. I was playing with C-states in BIOS with no impact. Need to check if there are any settings for boost related staff there. |
Beta Was this translation helpful? Give feedback.
-
No it isn't? the only links there are for the N100, 1220P, and 125H. At least for me, we have had some reports in the past of the link in Amazon changing to a different product but that is why there is a warning on that page |
Beta Was this translation helpful? Give feedback.
-
|
hi, root@pve: check this ( german ) maybe it´s helpful. best regards |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
I am running HA OS 16.3 with Frigate (Full Access) add-on in 0.16.2 version on Intel N150 mini PC (GMKtec G3 Plus).
I recently switched from Coral TPU to Openvino GPU detections. Since then I observe random computer restarts - sometimes multiple times a day, sometimes once every few days. It is definitely Frigate and openvino related, as if I switch to Coral the problem never happens again. I also performed heavy stress tests on GPU (and even CPU) and the machine does not reboots so it is likely not a hardware issue.
I can see that the restarts happens each time when GPU usage increases:
I have 4 720p streams and my config is pretty straightforward.
I cannot find anything useful in the logs but I might be looking in a wrong place. Any advices?
Steps to reproduce
As described above
Version
0.16.2-4d58206
In which browser(s) are you experiencing the issue with?
No response
Frigate config file
docker-compose file or Docker CLI command
n/aRelevant Frigate log output
Relevant go2rtc log output
Operating system
Home Assistant OS
Install method
Home Assistant Add-on
Network connection
Wired
Camera make and model
hikvision
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions