From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <cip-dev@lists.cip-project.org>, <pavel@denx.de>
Cc: <jan.kiszka@siemens.com>, <SZ.Lin@moxa.com>,
<ben.hutchings@codethink.co.uk>, <Chris.Paterson2@renesas.com>
Subject: Re: [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15
Date: Tue, 6 Oct 2020 23:43:00 +0000 [thread overview]
Message-ID: <OSBPR01MB2983148027370F1B4D02B0B6920D0@OSBPR01MB2983.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <163B547D5FFC3079.30511@lists.cip-project.org>
[-- Attachment #1: Type: text/plain, Size: 3653 bytes --]
Hi,
FYI:
https://patchwork.ozlabs.org/project/netdev/patch/20200922072931.2148-1-geert+renesas@glider.be/
Best regards,
Nobuhiro
> -----Original Message-----
> From: cip-dev@lists.cip-project.org [mailto:cip-dev@lists.cip-project.org] On Behalf Of Nobuhiro Iwamatsu
> Sent: Tuesday, October 6, 2020 3:49 PM
> To: cip-dev@lists.cip-project.org; pavel@denx.de
> Cc: jan.kiszka@siemens.com; SZ.Lin@moxa.com; ben.hutchings@codethink.co.uk; Chris.Paterson2@renesas.com
> Subject: Re: [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15
>
> Hi,
>
> This issue seems to occur randomly.
>
> # cip+rt kernel
> NG: https://lava.ciplatform.org/scheduler/job/57129
> https://lava.ciplatform.org/scheduler/job/57842
> OK: https://lava.ciplatform.org/scheduler/job/57851
> https://lava.ciplatform.org/scheduler/job/57841
>
> # 4.19.148+cip kernel
> NG: https://lava.ciplatform.org/scheduler/job/58836
> OK: https://lava.ciplatform.org/scheduler/job/58837
>
>
> We may need to confirm these relationships with CIP kernel patches.
>
> Best regards,
> Nobuhiro
>
> > -----Original Message-----
> > From: cip-dev@lists.cip-project.org [mailto:cip-dev@lists.cip-project.org] On Behalf Of Pavel Machek
> > Sent: Monday, October 5, 2020 6:39 AM
> > To: Chris Paterson <Chris.Paterson2@renesas.com>
> > Cc: Pavel Machek <pavel@denx.de>; jan.kiszka@siemens.com; cip-dev@lists.cip-project.org; SZ.Lin@moxa.com;
> > ben.hutchings@codethink.co.uk
> > Subject: Re: [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15
> >
> > Hi!
> >
> > > > New realtime trees should be available at kernel.org.
> > > >
> > > > Trees are available at
> > > >
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-
> > > > cip.git/log/?h=linux-4.19.y-cip-rt
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-
> > > > cip.git/log/?h=linux-4.19.y-cip-rt-rebase
> > > >
> > > > And their content should be identical.
> > >
> > > Thank you for the release.
> > >
> > > >
> > > > This patch merges 4.19.148-stable into -cip-rt (because that's what
> > > > recent -rt is based on, and older -rt tree is too old). Unfortunately,
> > > > that brings regression with ethernet on Renesas Arm64 targets, which
> > > > will prevent boot, and fail tests etc.
> > > >
> > > > Kernel that should work ok on Renesas Arm64 machines can be obtained
> > > > by reverting fb3a780e7a76cf8efb055f8322ec039923cee41f "ravb: Fixed to
> > > > be able to unload modules" on top of -cip-rt release.
> > >
> > > So we're releasing a Kernel that we know doesn't boot on one of CIP's reference platforms?
> > > Or did you already revert the above patch as part of your release?
> >
> > Yes, I did that, as the changelog explains. Sorry.
> >
> > I had to select from few bad options: 4.19.147-rt release is not
> > available and previous release is too old. So -cip-rt is based on
> > 4.19.148-rt, and it brings in the bad commit.
> >
> > I thought about reverting it for release, but all I'd get would be
> > rejects, as it really needs to be solved in -cip, not -cip-rt.
> >
> > Proper solution is likely updating 4.19-cip to 4.19.148, first. Then
> > figuring out what is the clean way to solve the problem, and then
> > creating new -rt release. But that will likely take more than few
> > days, and it will end up with different release number.
> >
> > I can create new -cip-rt release when that is done.
> >
> > Best regards,
> > Pavel
> > --
> > DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5501): https://lists.cip-project.org/g/cip-dev/message/5501
Mute This Topic: https://lists.cip-project.org/mt/77295090/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-10-06 23:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 9:06 [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15 Pavel Machek
2020-10-04 20:29 ` Chris Paterson
2020-10-04 21:39 ` Pavel Machek
2020-10-06 6:49 ` Nobuhiro Iwamatsu
[not found] ` <163B547D5FFC3079.30511@lists.cip-project.org>
2020-10-06 23:43 ` Nobuhiro Iwamatsu [this message]
2020-10-07 20:11 ` Pavel Machek
2020-10-08 5:32 ` Nobuhiro Iwamatsu
2020-10-08 5:45 ` Nobuhiro Iwamatsu
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=OSBPR01MB2983148027370F1B4D02B0B6920D0@OSBPR01MB2983.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=Chris.Paterson2@renesas.com \
--cc=SZ.Lin@moxa.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=pavel@denx.de \
/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).