-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Camera randomly disrupts i2c on other busses (RPI 3B+ & 4) #3893
Comments
It's going to be hard to get much interest here when you have a log full of undervoltage warnings - there's a good chance that the reason using the camera affects I2C is that using it draws more power. |
Thank you, I ran it again on RPI3B+ with a better power supply (no undervolt warnings) and updated the output in the first post.
|
Hello! I have the same issue, but with multiple I2C devices on multiple channels. In addition to the default channel 1, I enabled 3 additional I2C channels to read from and write to 4 devices simultaneously. After just a few seconds 3 channels stop working (while the (randomly) remaining one still runs) and timed-out errors appear in dmesg
My setup is Raspberry Pi 4 running Raspberry Pi OS Buster ( |
@chukhanhhoang Are you running the camera at the same time, or just the different I2C buses from the Pi4? All the I2C controllers share a common interrupt line (GIC 117 for Pi4, interrupt 21 on earlier boards), so there is a bit of cooperation required when they come to service them. The firmware (which generally controls the camera and /dev/i2c-0) doesn't use the interrupts, so shouldn't cause any effects. |
Thank you very much for your quick response! |
Curious as I'm not aware of any I2C changes between 5.10.17 and 5.10.46. |
Yes Linux 5.10.17-v7+ also created the same issues for me even without camera (on RPI3 B+). i2c timed out every second or so. rpi-update to 5.10.48-v7+ fixed it |
I have a raspberry pi4B with the following details lsb_release -a an 29 00:54:58 flsmidth-vision-flotation kernel: Modules linked in: 8021q garp stp llc brcmfmac brcmutil vc4 cfg80211 bcm2835_codec(C) snd_bcm2835(C) v4l2_mem2mem cec rfkill bcm2835_isp(C) bcm2835_v4l2(C) v3d bcm2835_mmal_vchiq(C) gpu_sched videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 drm_kms_helper videobuf2_common videodev mc drm i2c_bcm2835 raspberrypi_hwmon drm_panel_orientation_quirks vc_sm_cma(C) snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd syscopyarea sysfillrect sysimgblt fb_sys_fops backlight rpivid_mem uio_pdrv_genirq uio nvmem_rmem rpi_poe_power rpi_poe_fan i2c_dev ip_tables x_tables ipv6 This is the i2c error that I get. This error then randomly crashes the server.. the firmware is the latest as well.. I have just a pi camera connected to raspi |
Buster and the 5.10 kernel are no longer supported. Please test with a more recent kernel. |
Closing as previous reporters were reporting it solved. |
Recording from the camera (especially when using multiple splitter ports)
and sampling the I2C bus (1 or others on RPI4) simultaneously randomly throws:
errno 5 input output error or errno 110 connection timed out.
this happens on the RPI4 every minute or so, and on the RPI3B+ less frequently (sometimes once 1h or something).
See this thread for all the specific test condition etc:
https://www.raspberrypi.org/forums/viewtopic.php?f=44&t=287015&p=1738555#p1734925
I tested it on both Buster and Stretch with different firmware versions and kernels.
Changing anything in config.txt (e.g. core_freq, arm_freq, or gpu mem etc) did not solve the issue.
Last setup:
ON RPI3B+:
raspinfo:
EDIT: ran it again on RPI3B+ with better power supply to avoid under voltage, still same issue.
config.txt (current version but it tried multiple options see https://www.raspberrypi.org/forums/viewtopic.php?f=44&t=287015&p=1738555#p1734925)
RPI4:
raspinfo
config.txt
The text was updated successfully, but these errors were encountered: