nik/frigate
1
0
Fork 0
mirror of https://github.com/blakeblackshear/frigate.git synced 2026-10-18 07:29:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

Docs: warn about kernel Oops with v4l2m2m hwaccel on ASUS GT-BE19000AI

Browse Source 
Enabling the recommended h264_v4l2m2m hwaccel args on the GT-BE19000AI AI
board (SL1680, firmware kernel 5.15.140) triggers a LIST_POISON dereference
Oops in the vendor vpu driver during decoder teardown, requiring a reboot.
Observed and captured on real hardware. Also fixes a Synaptics typo.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Jonathan LoBue 2026-08-16 08:35:42 -07:00
parent 26f4642c26
commit 5664fe5c80
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/docs/configuration/hardware_acceleration_video.md
View File

@ -498,7 +498,7 @@ cameras:
## Synaptics
Hardware accelerated video de-/encoding is supported on Synpatics SL-series SoC.
Hardware accelerated video de-/encoding is supported on Synaptics SL-series SoC.
### Prerequisites
@ -532,3 +532,9 @@ output_args:
Make sure that your SoC supports hardware acceleration for your input stream and your input stream is h264 encoding. For example, if your camera streams with h264 encoding, your SoC must be able to de- and encode with it. If you are unsure whether your SoC meets the requirements, take a look at the datasheet.
:::
:::warning
On the ASUS GT-BE19000AI router AI board (SL1680, firmware kernel 5.15.140), enabling `-c:v h264_v4l2m2m` has been observed to trigger a kernel Oops in the vendor `vpu` driver when the decoder is closed, leaving the board in a state that requires a reboot. Until ASUS ships a firmware fix, leave `hwaccel_args` unset on this device and rely on software decoding.
:::