Emma Anholt

@babyimp have you tried since the i2c fixes?

It comes from the hardware specification. I would bet that something like HDMI audio or CEC would be the first things to break when running the HDMI pixel clock too...

Possibly infoframe packets, too. We'd need a hardware engineer to answer the question.

The Raspberry Pi panel's bridge apparently doesn't respond well to reads, so I've never used them. Looking at the code, the IRQ handler wakes up the transfer's completion on TXPKT1_DONE,...

I've also seen this periodically and don't have any good ideas yet.

@lategoodbye not sure how that cursor patch would help, since the backtrace here is from a general setcrtc.

[ 0.000000] cma: Reserved 476 MiB at 0x1f000000 This cause intermittent crashes with 3D. Delete the gpu_mem and cma lines from your config.txt, and use the defaults that vc4-kms-v3d sets...

OK, so we're looking at this: ``` [ 60.934] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB [ 60.934] (II) AIGLX: enabled GLX_ARB_fbconfig_float [ 60.934] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects [ 60.938]...

The open driver scans out pixels 1:1, and it has no way to see the contents of your config.txt Many TVs default to scaling from a subset of the screen,...

Can you attach your xrandr --verbose output? I'm curious what your CEA block reports.