From: "Pavel Machek" <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Cc: Pavel Machek <pavel@denx.de>,
"kernel-build-reports@lists.linaro.org"
<kernel-build-reports@lists.linaro.org>,
"kernelci-results@groups.io" <kernelci-results@groups.io>
Subject: Re: [cip-dev] cip/linux-4.4.y-cip usb: 4 runs, 2 regressions (v4.4.243-cip51-21-g1d9a9094c010)
Date: Fri, 4 Dec 2020 18:48:10 +0100 [thread overview]
Message-ID: <20201204174810.GA8507@duo.ucw.cz> (raw)
In-Reply-To: <OSAPR01MB238504B0E42A849BF97CF39AB7F10@OSAPR01MB2385.jpnprd01.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 2553 bytes --]
Hi!
> > *** gpg4o | HINT: Error while checking message with detached signature
> > (PGP/MIME signature)!
> > Couldn't locate the original MIME source of the mail to verify the signature!
> > gpg4oh32.dll:: func_IV Init OK ***
> >
> > Hello, bot. Can you speak english?
>
> Beep boop.
>
> I've recently enabled these email reports. They come from KernelCI.org.
> I meant to say yesterday, but forgot :(
No problem :-).
> > > 2020-12-03 05:04:20.968000+00:00 [ 18.800704] Freezing remaining
> > freezable tasks ... (elapsed 0.001 seconds) done.
> > > 2020-12-03 05:04:20.972000+00:00 [ 18.809224] Suspending console(s)
> > (use no_console_suspend to debug)
> > > 2020-12-03 05:04:23.674000+00:00 [ 18.865290] hub 3-1:1.0: activate --> -
> > 113
> > > 2020-12-03 05:04:23.675000+00:00 [ 18.867538] PM: suspend of devices
> > complete after 51.550 msecs
> > > 2020-12-03 05:04:23.685000+00:00 [ 18.868293] PM: late suspend of
> > devices complete after 0.750 msecs
> > > ... (66 line(s) more)
> >
> >
> > I'm not sure where you see failure here, plus I find it hard to
> > believe that we have broken anything between
> > v4.4.243-cip51-10-gd7466739b72e9 and v4.4.243-cip51-21-g1d9a9094c010.
>
> Looking at the full test log [0] it looks like a comparison (before.txt with after-freeze.txt) has gone wrong. Presumably some corrupt data?
>
> 05:04:29.997473 + lava-test-case compare-freeze --shell diff -u before.txt after-f[ 27.830724] <LAVA_SIGNAL_STARTTC compare-freeze>
> 05:04:30.009142 reeze.txt
> 05:04:30.009390 --- before.txt[ 27.841181] <LAVA_SIGNAL_ENDTC compare-freeze>
> 05:04:30.009581 2019-02-14 10:12:01.895000001 +0000
> 05:04:30.020487 +++ after-freeze.txt 2019-[ 27.848337] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=compare-freeze RESULT=fail>
> 05:04:30.020750 02-14 10:12:11.459256544 +0000
> 05:04:30.032157 @@ -1,4 +1,5 @@
> 05:04:30.032446 0424:9514
> 05:04:30.032634 +0424:ec00
> 05:04:30.032840 04f2:b443
> 05:04:30.033020 1d6b:0002
> 05:04:30.033195 1d6b:0002
This looks like USB id's. (1d6b: is Linux foundation, common in USB
hubs). So I believe this tells us that someone plugged in device
0424:ec00 -- ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514
Fast Ethernet Adapter ... and I don't think we have a bug to solve
here.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5945): https://lists.cip-project.org/g/cip-dev/message/5945
Mute This Topic: https://lists.cip-project.org/mt/78682105/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-12-04 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 5:32 [cip-dev] cip/linux-4.4.y-cip usb: 4 runs, 2 regressions (v4.4.243-cip51-21-g1d9a9094c010) kernelci.org bot
2020-12-04 16:40 ` Pavel Machek
2020-12-04 17:17 ` Chris Paterson
2020-12-04 17:48 ` Pavel Machek [this message]
2020-12-07 9:02 ` Guillaume Tucker
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=20201204174810.GA8507@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@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;
as well as URLs for NNTP newsgroup(s).