-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Running libcamera-hello leads to Division by zero in kernel #4714
Comments
@naushir looks like |
@davidplowman have you seen this before? Not something I've encountered. I can't really see how q_data->fmt->depth would be zero in this case either. |
@oniongarlic is this easily reproducible? Could you add the following to the end of
and provide a kernel log after the failure please? |
I'm observing something similar on Pi Zero W when trying to use an OV5647 module:
That's the kernel log with |
I think #4732 might fix this div by 0. Fairly obvious bug when you look at it, so I am somewhat surprised we have not seen it happen more. |
I can confirm this has been fixed for me. (Raspberry Pi Zero W) |
@oniongarlic can you close issue if this is fixed for you? |
Describe the bug
Running libcamera-hello on a Model B with Camera V1 leads to Division by zero in kernel oops.
To reproduce
Run libcamera-hello
Expected behaviour
No Division by zero in kernel
Actual behaviour
[ 95.199368] Division by zero in kernel.
System
Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:
Which model of Raspberry Pi? Vintage Model B
Which OS and version (
cat /etc/rpi-issue
)? 11Which firmware version (
vcgencmd version
)?Oct 29 2021 10:49:08
Copyright (c) 2012 Broadcom
version b8a114e5a9877e91ca8f26d1a5ce904b2ad3cf13 (clean) (release) (start)
Which kernel version (
uname -a
)?Linux pifhdcamera 5.10.63+ # 1459 Wed Oct 6 16:40:27 BST 2021 armv6l GNU/Linux
Logs
Additional context
1080p forced in config.txt, otherwise defaults
The text was updated successfully, but these errors were encountered: