[Letux-kernel] [PATCH 0/8] Get sound playback working on the Pandora again

H. Nikolaus Schaller hns at goldelico.com
Thu Feb 3 16:52:04 CET 2022


Hi,
sorry for not working on this issue... I have not forgotten but there are
too many other important things ahead.

But I have a minor observation in addition to this:

> Am 10.01.2022 um 21:33 schrieb H. Nikolaus Schaller <hns at goldelico.com>:
> 
> PS: one more observation - I can sometimes trigger it by pure
> kernel/processor activity. But not systematically.
> root at letux:~# 
> root at letux:~# ./high-load    
> 100% load stress test for 1 cores running loop
> Mon Jan 10 20:32:26 UTC 2022 51° 3853mV 600MHz
> Mon Jan 10 20:32:26 UTC 2022 51° 3859mV 600MHz
> Mon Jan 10 20:32:28 UTC 2022 52° 3853mV 600MHz
> [  747.156127] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
> [  747.168548] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
> [  747.438201] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
> [  747.529113] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
> Mon Jan 10 20:32:29 UTC 2022 54° 3853mV 600MHz
> Mon Jan 10 20:32:32 UTC 2022 54° 3853mV 600MHz
> [  750.409240] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
> [  750.499999] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
> Mon Jan 10 20:32:33 UTC 2022 54° 3847mV 600MHz
> [  753.147277] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
> [  753.168212] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
> [  753.177795] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
> [  753.187408] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
> Mon Jan 10 20:32:35 UTC 2022 54° 3847mV 600MHz
> [  753.448516] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
> [  753.538452] omap_i2c 48060000.i2c: timeout waiting on XUDF bit
> ^Ckill 3692
> 
> root at letux:~#

running

	timeout 30s /root/high-load >/dev/null; dmesg | fgrep -q XUDF && echo "bad" || echo good

quite reliably triggers and reports the XUDF issue. But only if I run full letux-5.4.

Not, if I just add some minor tweaks to upstream v5.4 (which then has no display and
no hubs of course).

Well, there are a lot of no-yet upstreamed patches in between, e.g. for display
or the nubs itself. So it could be expected that the bug is not visible with v5.4.

On the other hand it is also not visible on v5.1 or full letux-5.1.

So I think it may be an upstream change that only manifests itself on a full
letux kernel.

Maybe I have to set up a more complete letux patch set on top of bisecting
upstream between v5.1 and v5.4. That is additionally challenging to get
something that merges and compiles well in all intermediate steps...

BR,
Nikolaus



More information about the Letux-kernel mailing list