From: Pavel Machek <pavel@denx.de>
To: cip-dev@lists.cip-project.org, bot@kernelci.org,
Chris.Paterson2@renesas.com, alice.ferrazzi@miraclelinux.com
Subject: Re: [cip-dev] cip/linux-4.19.y-cip baseline: 121 runs, 1 regressions (v4.19.217-cip62) #kernelci
Date: Tue, 30 Nov 2021 09:41:37 +0100 [thread overview]
Message-ID: <20211130084137.GB2355@amd> (raw)
In-Reply-To: <61a58f0e.1c69fb81.ac5ac.8c21@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 2309 bytes --]
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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2021-11-30 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 2:40 cip/linux-4.19.y-cip baseline: 121 runs, 1 regressions (v4.19.217-cip62) #kernelci kernelci.org bot
2021-11-30 8:41 ` Pavel Machek [this message]
2021-12-02 12:22 ` [cip-dev] " Alice Ferrazzi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211130084137.GB2355@amd \
--to=pavel@denx.de \
--cc=Chris.Paterson2@renesas.com \
--cc=alice.ferrazzi@miraclelinux.com \
--cc=bot@kernelci.org \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox