System crash possibly due to edid errors

Open
#7,199 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
linux

Research direction

Start by reproducing the Trixie failure with the Raspberry Pi 400, HDMI splitter, and Decimator arrangement described in the issue. Review the boot/firmware/config.txt setting and vc4-kms-v3d behavior, then collect the missing logs to determine whether the system is crashing. Done means identifying the EDID-related failure and establishing a kernel fix or a confirmed configuration cause.

Written by the indexing model from the issue text.

Description

Describe the bug

I plug an RPi 400 (single 720p HDMI-0 output) into a 1x4 hdmi splitter with the goal of duplicating the computer output on two or more monitors.

It works under both Bookworm (latest updates) and Trixie (latest updates) - both under labwc - either from boot up or adding monitors after system stabilized.

Steps to reproduce the behaviour

If I replace one of the monitors with a Decimator on the HDMI splitter, it works under Bookworm (either from boot up or after stabilized) however computer fails to boot under Trixie-or if already booted and stabilized the os appears to crash.

All attempts to add HDMI entries into the boot/firmware/config.txt are apparently ignored and commenting out #dtoverlay=vc4-kms-v3d prevented the system from booting.

In this configuration when Trixie booting- computer shows the rainbow image on decimator and other monitors on power up, but then no signal after.

However, if i connect the computer directly to the Decimator and then run its HDMI output to the HDMI splitter all monitors work under Trixie.

Device (s)

Raspberry Pi 400

System

Raspberry Pi Bookworm and Trixie, latest updates.

Logs

No response

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.