Re: kernelci test results

[Sebastian Andrzej Siewior <bigeasy@linutronix.de>]

On 2026-09-04 08:15:12 [+0300], Denys Fedoryshchenko wrote:
> Hi Sebastian, Alan
Hi,

> The system currently creates a short log extract only when a build or
> boot test is marked as failed. This job completed successfully,
> including the boot and cyclictest, so the log was stored but not
> automatically analyzed for an extract.
> The kernel warning is present in the full log and our analyzer can
> recognize it, but it was missed because the overall job passed. This
> is a limitation in the current reporting flow.
> We initially chose to create log extracts only for failed builds or
> boot tests because successful boots often contain harmless or known
> warnings, such as spurious IRQ messages. Reporting every warning as an
> issue could create substantial noise that kernel developers may not
> find actionable.
> We could review this policy and maintain an ignore list for known,
> non-actionable messages. That would let us highlight new or unexpected
> warnings without creating unnecessary noise for kernel developers.

Okay. So this might look okay since the tests pass. With my kernel
developer hat on, I have to say that there should be warnings of any
kind. Looking at log from
	https://dashboard.kernelci.org/test/maestro%3A6aa88a0d20239ade9037b72f

reminds that I poked at the first error "Event mtu3_gadget_ep_set_halt
has double dereference" but it is still there so I need to poke again.
There there is
|Unable to handle kernel NULL pointer dereference at virtual address 0000000000000019
which is definitely not normal.
Someone with hardware should look at this. I will try to forward it,
maybe it goes away :)

Even the "spurious IRQ messages" is a sign of bad driver/ hardware setup
and shouldn't be ignored.

Sebastian