Hi!

> platform | arch | lab           | compiler | defconfig           | regressions
> ---------+------+---------------+----------+---------------------+------------
> panda    | arm  | lab-collabora | gcc-10   | omap2plus_defconfig | 1          
> 
>   Details:     https://kernelci.org/test/plan/id/61a587a0ab3b0079bd18f6d7
> 
>   Results:     5 PASS, 1 FAIL, 0 SKIP
>   Full config: omap2plus_defconfig
>   Compiler:    gcc-10 (arm-linux-gnueabihf-gcc (Debian 10.2.1-6) 10.2.1 20210110)
>   Plain log:   https://storage.kernelci.org//cip/linux-4.19.y-cip/v4.19.217-cip62/arm/omap2plus_defconfig/gcc-10/lab-collabora/baseline-panda.txt
>   HTML log:
> https://storage.kernelci.org//cip/linux-4.19.y-cip/v4.19.217-cip62/arm/omap2plus_defconfig/gcc-10/lab-collabora/baseline-panda.html

So this has enough information to tell me that we have a kernel
problem there, good:

02:08:17.792502  <6>[   18.847320] omap-mailbox 4a0f4000.mailbox: omap
mailbox rev 0x400
02:08:17.800596  <0>[   18.857543] BUG: spinlock bad magic on CPU#0,
udevd/110
02:08:17.808843  <6>[   18.857788] emif 4c000000.emif: emif_probe:
device configured with addr = (ptrval) and IRQ26
02:08:17.818753  <0>[   18.863311]  lock: emif_lock+0x0/0xffffecfc
[emif], .magic: dead4ead, .owner: <none>/-1, .owner_cpu: -1
02:08:17.825277  <4>[   18.877502] CPU: 0 PID: 110 Comm: udevd Not
tainted 4.19.217-cip62 #1
02:08:17.831655  <4>[   18.888275] Hardware name: Generic OMAP4
(Flattened Device Tree)
02:08:17.839660  <4>[   18.894195] [<c01123bc>] (unwind_backtrace)
from [<c010cc28>] (show_stack+0x10/0x14)
02:08:17.847570  <4>[   18.900482] [<c010cc28>] (show_stack) from
[<c0949dd4>] (dump_stack+0xe0/0x114)
02:08:17.855211  <4>[   18.905761] [<c0949dd4>] (dump_stack) from
[<c01a9168>] (do_raw_spin_lock+0xbc/0x124)

Unfortunately, not enough information to debug the problem, I'm
afraid. Questions to start debugging this would be:

a) is the problem deterministic?

b) is the problem present in v4.19.217 ?

c) what were the last -stable and -cip kernels that worked?

d) what device/module is causing the BUG?

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany