Skip to contentSkip to conversation

v4.19.148-cip35-rt15

cip-dev Pavel Machek 3 participants 8 messages Oct 4, 2020 – Oct 8, 2020 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

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.

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.

Best regards,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5495): https://lists.cip-project.org/g/cip-dev/message/5495
Mute This Topic: https://lists.cip-project.org/mt/77295090/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#1 lore raw

Hello Pavel,

Quoted 11 lines

From: Pavel Machek <[email protected]>
Sent: 04 October 2020 10:07

*** gpg4o | The signature of this email could not be verified because the following public key is missing. Click here to search and import the key 30E7F06A95DBFAF2 ***

Hi!

New realtime trees should be available at kernel.org.

Quoted 8 lines

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.

Quoted 9 lines

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?

Thanks, Chris

Quoted 8 lines

Best regards,
                                                                 Pavel

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5497): https://lists.cip-project.org/g/cip-dev/message/5497
Mute This Topic: https://lists.cip-project.org/mt/77295090/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#2 lore raw

Hi!

Quoted 19 lines
Quoted 10 lines

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.

Quoted 6 lines

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.

Quoted 6 lines
Quoted 3 lines

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

Signature · 2 lines
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5498): https://lists.cip-project.org/g/cip-dev/message/5498
Mute This Topic: https://lists.cip-project.org/mt/77295090/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#3 lore raw

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

Quoted 50 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Pavel Machek
Sent: Monday, October 5, 2020 6:39 AM
To: Chris Paterson <[email protected]>
Cc: Pavel Machek <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15

Hi!

Quoted 19 lines
Quoted 10 lines

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.

Quoted 6 lines

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.

Quoted 6 lines
Quoted 3 lines

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.

Quoted 7 lines

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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5499): https://lists.cip-project.org/g/cip-dev/message/5499
Mute This Topic: https://lists.cip-project.org/mt/77295090/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#5 lore raw
In reply to a message not in the archive

Hi,

FYI:
https://patchwork.ozlabs.org/project/netdev/patch/[email protected]/

Best regards,
Nobuhiro

Quoted 22 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Nobuhiro Iwamatsu
Sent: Tuesday, October 6, 2020 3:49 PM
To: [email protected]; [email protected]
Cc: [email protected]; [email protected]; [email protected]; [email protected]
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

Quoted 62 lines

We may need to confirm these relationships with CIP kernel patches.

Best regards,
Nobuhiro

Quoted 57 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Pavel Machek
Sent: Monday, October 5, 2020 6:39 AM
To: Chris Paterson <[email protected]>
Cc: Pavel Machek <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15

Hi!

Quoted 19 lines
Quoted 10 lines

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.

Quoted 6 lines

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.

Quoted 6 lines
Quoted 3 lines

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

-=-=-=-=-=-=-=-=-=-=-=-
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: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#6 lore raw

Hi!

Quoted 3 lines

FYI:
https://patchwork.ozlabs.org/project/netdev/patch/[email protected]/

Yes, and the revert is now queued to 4.19-stable, too.

So.. what do we want to do here?

We can merge 4.19.151 to -cip when it is released, and I can then release new -cip-rt that works on renesas boards...

Best regards,
Pavel

Signature · 2 lines
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5503): https://lists.cip-project.org/g/cip-dev/message/5503
Mute This Topic: https://lists.cip-project.org/mt/77295090/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#7 lore raw

Hi Pavel,

Quoted 14 lines

-----Original Message-----
From: Pavel Machek [mailto:[email protected]]
Sent: Thursday, October 8, 2020 5:11 AM
To: iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT) <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15

Hi!

Quoted 3 lines

FYI:
https://patchwork.ozlabs.org/project/netdev/patch/[email protected]/

Quoted 6 lines

Yes, and the revert is now queued to 4.19-stable, too.

So.. what do we want to do here?

We can merge 4.19.151 to -cip when it is released, and I can then release new -cip-rt that works on renesas boards...

Yes, I think so.
Perhaps 4.19.151 will be released this weekend. And this week is the release week of the CIP kernel. And I think we can use it to release the cip-rt tree.

Quoted 3 lines

Best regards,
Pavel

Best regards,
Nobuhiro

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5506): https://lists.cip-project.org/g/cip-dev/message/5506
Mute This Topic: https://lists.cip-project.org/mt/77295090/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#8 lore raw

Hi,

Quoted 26 lines

-----Original Message-----
From: iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT)
Sent: Thursday, October 8, 2020 2:32 PM
To: Pavel Machek <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: RE: [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15

Hi Pavel,

Quoted 16 lines

-----Original Message-----
From: Pavel Machek [mailto:[email protected]]
Sent: Thursday, October 8, 2020 5:11 AM
To: iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT) <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15

Hi!

Quoted 3 lines

FYI:
https://patchwork.ozlabs.org/project/netdev/patch/[email protected]/

Yes, and the revert is now queued to 4.19-stable, too.

Quoted 7 lines
Quoted 4 lines

So.. what do we want to do here?

We can merge 4.19.151 to -cip when it is released, and I can then release new -cip-rt that works on renesas boards...

Yes, I think so.
Perhaps 4.19.151 will be released this weekend. And this week is the release week of the CIP kernel.

Sorry, this may be wrong.
If 151 isn't released this weekend, I'll cherry pick this commit, and release new CIP kernel.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-4.19.y&id=1fa5848fae409511eda2c6ee4f8ad9e42a0cb3c1

Quoted 2 lines

And I think we can use it to release the cip-rt tree.

Best regards,
Nobuhiro

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5507): https://lists.cip-project.org/g/cip-dev/message/5507
Mute This Topic: https://lists.cip-project.org/mt/77295090/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-