dmesg shows i2c and spidev errors on bookworm 2023-12-11

Open
#5,858 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, linux
Domain
embedded-iot, operating-systems

Research direction

Start with the reported kernel logs and the Raspberry Pi 5 system details, focusing on the i2c_designware and spidev timeout messages. Reproduce the issue on the stated kernel and determine whether the I2C and SPI failures share a cause; done means identifying a reproducible cause and a verified kernel or configuration fix.

Written by the indexing model from the issue text.

Description

Describe the bug
[36179.397186] i2c_designware 1f00074000.i2c: timeout waiting for bus ready
[36179.417868] i2c_designware 1f00074000.i2c: timeout waiting for bus ready
[36179.438707] i2c_designware 1f00074000.i2c: timeout waiting for bus ready
[36179.458975] i2c_designware 1f00074000.i2c: timeout waiting for bus ready
[36179.480084] i2c_designware 1f00074000.i2c: timeout waiting for bus ready
[36179.500519] i2c_designware 1f00074000.i2c: timeout waiting for bus ready
[36179.520695] i2c_designware 1f00074000.i2c: timeout waiting for bus ready
[36179.540765] i2c_designware 1f00074000.i2c: timeout waiting for bus ready
[36179.561087] i2c_designware 1f00074000.i2c: timeout waiting for bus ready
[36179.581862] i2c_designware 1f00074000.i2c: timeout waiting for bus ready
[36179.784769] spidev spi0.0: SPI transfer timed out
[36179.784782] spi_master spi0: failed to transfer one message from queue
[36179.988772] spidev spi0.0: SPI transfer timed out
[36179.988783] spi_master spi0: failed to transfer one message from queue
[36180.192775] spidev spi0.1: SPI transfer timed out
[36180.192787] spi_master spi0: failed to transfer one message from queue
[36180.396781] spidev spi0.1: SPI transfer timed out
[36180.396797] spi_master spi0: failed to transfer one message from queue
[36180.417872] i2c_designware 1f00074000.i2c: timeout waiting for bus ready
[36180.438976] i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Steps to reproduce the behaviour

Was simply running and started happening after some time on raspberry pi5 rev 1

Device (s)

Other

System
user@lysmarine:~ $ cat /etc/rpi-issue
Raspberry Pi reference 2023-12-11
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 2acf7afcba7d11500313a7b93bb55a2aae20b2d6, stage2
user@lysmarine:~ $ vcgencmd version
2024/01/05 15:57:40
Copyright (c) 2012 Broadcom
version 30cc5f37 (release) (embedded)
user@lysmarine:~ $ uname -a
Linux lysmarine 6.1.0-rpi7-rpi-2712 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux
Logs
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:37 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Jan 17 15:43:38 lysmarine kernel: spidev spi0.0: SPI transfer timed out
Jan 17 15:43:38 lysmarine kernel: spi_master spi0: failed to transfer one message from queue
Jan 17 15:43:38 lysmarine kernel: spidev spi0.0: SPI transfer timed out
Jan 17 15:43:38 lysmarine kernel: spi_master spi0: failed to transfer one message from queue
Jan 17 15:43:38 lysmarine kernel: spidev spi0.1: SPI transfer timed out
Jan 17 15:43:38 lysmarine kernel: spi_master spi0: failed to transfer one message from queue
Jan 17 15:43:38 lysmarine kernel: spidev spi0.1: SPI transfer timed out
Jan 17 15:43:38 lysmarine kernel: spi_master spi0: failed to transfer one message from queue
Jan 17 15:43:38 lysmarine kernel: i2c_designware 1f00074000.i2c: timeout waiting for bus ready
Additional context

No response

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.