From: Pavel Machek <pavel@denx.de>
To: Chris Paterson <Chris.Paterson2@renesas.com>
Cc: Pavel Machek <pavel@denx.de>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"bot@kernelci.org" <bot@kernelci.org>,
"alice.ferrazzi@miraclelinux.com"
<alice.ferrazzi@miraclelinux.com>,
"kernelci@groups.io" <kernelci@groups.io>
Subject: Re: [cip-dev] cip/linux-4.19.y-cip baseline-nfs: 12 runs, 1 regressions (v4.19.217-cip62) #kernelci
Date: Wed, 1 Dec 2021 10:01:39 +0100 [thread overview]
Message-ID: <20211201090139.GA23274@amd> (raw)
In-Reply-To: <OSZPR01MB687760A42FAC36D478192D11B7679@OSZPR01MB6877.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2360 bytes --]
Hi!
> > Then we have:
> >
> > > cip/linux-4.19.y-cip baseline-nfs: 12 runs, 1 regressions (v4.19.217-cip62)
> >
> > Ok, so we may have an regression. That means it worked before and it
> > does not work now. I'd expect two versions "worked in v4.19.123-cip12,
> > now broken in v4.19.217-cip62", but we only have one.
> >
> > > Regressions Summary
> > > -------------------
> > >
> > > platform | arch | lab | compiler | defconfig | regressions
> > > -----------------+-------+---------------+----------+-----------+------------
> > > rk3399-gru-kevin | arm64 | lab-collabora | gcc-10 | defconfig | 1
>
> Did you not have a "details" link here? In my copy of the email (attached) it links to
> https://linux.kernelci.org/test/job/cip/branch/linux-4.19.y-cip/kernel/v4.19.217-cip62/plan/baseline-nfs/
>
> If you click on the platform in question it says: "New regression, last pass: v4.19.216-cip61", which also links to the relevant build job.
> I think it also says this in the email below the failed test case? (baseline-nfs.login)
>
I did not find the "New regression, last pass" summary, but clicking
on testcase path indeed gave me failing and passing dmesg.
Working test says:
07:05:59.319716 <4>[ 16.957513] cdn-dp fec00000.dp: Direct firmware
load for rockchip/dptx.bin failed with error -2
07:06:00.206271 <6>[ 17.844209] asix 7-1:1.0 enx48f8b3454d72: link
up, 100Mbps, full-duplex, lpa 0xC1E1
07:06:00.551556 IP-Config: no response after 2 secs - giving up
07:06:00.609271 IP-Config: enx48f8b3454d72 hardware address
48:f8:b3:45:4d:72 mtu 1500 DHCP
And after scrolling around it looks enx48f8b3454d72 is usb ethernet
card.
> This includes a link to the defconfig used, although perhaps you'd like to know more about the platform.
>
Yes, knowing more about platform would be nice (one question would be
"Is the ethernet removable?"). But in case like this I'd need someone
to do the tests for me (or to have enough access to do the tests
myself). First question would be "does v4.19.217 work with same
config"? Easist way to debug this is usually bisection....
Is that feasible?
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-12-01 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 2:40 cip/linux-4.19.y-cip baseline-nfs: 12 runs, 1 regressions (v4.19.217-cip62) #kernelci kernelci.org bot
2021-11-30 8:33 ` [cip-dev] " Pavel Machek
2021-11-30 10:22 ` Chris Paterson
2021-12-01 9:01 ` Pavel Machek [this message]
2021-12-01 9:11 ` Pavel Machek
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=20211201090139.GA23274@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 \
--cc=kernelci@groups.io \
/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