All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Henning Schild <henning.schild@siemens.com>,
	Henning Schild via Xenomai <xenomai@xenomai.org>
Subject: Re: [I-PIPE] ipipe-core-4.19.165-cip41-arm64-09 released
Date: Thu, 25 Feb 2021 14:54:55 +0100	[thread overview]
Message-ID: <87zgzs6ymo.fsf@xenomai.org> (raw)
In-Reply-To: <a208dd97-7c5b-5944-5a8e-9752c6d235af@siemens.com>


Jan Kiszka <jan.kiszka@siemens.com> writes:

> On 24.02.21 12:35, Henning Schild via Xenomai wrote:
>> Am Wed, 24 Feb 2021 11:24:55 +0100
>> schrieb Henning Schild via Xenomai <xenomai@xenomai.org>:
>> 
>>> Am Wed, 10 Feb 2021 12:08:43 +0100
>>> schrieb Jan Kiszka via Xenomai <xenomai@xenomai.org>:
>>>
>>>> On 10.02.21 11:07, Bezdeka, Florian (T RDA IOT SES-DE) wrote:  
>>>>> On Wed, 2021-02-10 at 09:15 +0100, Jan Kiszka via Xenomai wrote:
>>>>>   
>>>>>> On 10.02.21 07:22, xenomai--- via Xenomai wrote:    
>>>>>>> Download URL:
>>>>>>> https://xenomai.org/downloads/ipipe/v4.x/arm64/ipipe-core-4.19.165-cip41-arm64-09.patch
>>>>>>>
>>>>>>> Repository: https://git.xenomai.org/ipipe-arm64
>>>>>>> Release tag: ipipe-core-4.19.165-cip41-arm64-09
>>>>>>>    
>>>>>>
>>>>>> Hmm, now we have the 5.4-arm64 issue also on 4.19:
>>>>>> https://gitlab.denx.de/Xenomai/xenomai-images/-/jobs/219984
>>>>>>    
>>>>>
>>>>> I don't know much about the things going on here, but found this
>>>>> line in the log. Maybe a starting point...
>>>>>
>>>>> 2021-02-10T07:51:47 setsched.c:120, assertion failed: stats.msw ==
>>>>> msw   
>>>>
>>>> Exactly, that is causing the overall failure. And it was first seen
>>>> with the newly added 5.4 kernel.  
>>>
>>> Seing the same on amd64 when testing on qemu, real HW is fine.
>>>
>>> Managed to bisect it down to 4.19.147-cip (good) 4.19.150-cip (bad)
>>>
>>> Which also means that ipipe-core-4.19.152-cip37-x86-15 is affected.
>>>
>>> https://gitlab.denx.de/Xenomai/xenomai-images/-/jobs/200646
>>> did not find it, so maybe our config differs
>
> Already compared yours against the one in xenomai-images? That would be
> useful.
>
>> 
>> Digging further i found 0f0b6099c45ff3e06d2487816cf1ff30d21835f6 likely
>> causing the problem.
>> 
>> ipipe-core-4.19.152-cip37-x86-15 <- bad
>> revert 2b294ac325c7ce3f36854b74d0d1d89dc1d1d8b8
>> revert 8579a0440381353e0a71dd6a4d4371be8457eac4 <- bad
>> revert 0f0b6099c45ff3e06d2487816cf1ff30d <- good
>> 
>> I think here Jan or Phillipe should take over.
>
> Thanks for bisecting, this is helpful!
>
> Philippe, any immediate idea why all that is failing now?

Something may be going wrong with MAP_SHARED mappings wrt commit_vma()
in Dovetail. I'm adding this to my debug queue.

-- 
Philippe.


  reply	other threads:[~2021-02-25 13:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10  6:22 [I-PIPE] ipipe-core-4.19.165-cip41-arm64-09 released xenomai
2021-02-10  8:15 ` Jan Kiszka
2021-02-10 10:07   ` florian.bezdeka
2021-02-10 11:08     ` Jan Kiszka
2021-02-10 12:41       ` Greg Gallagher
2021-02-10 14:58         ` Greg Gallagher
2021-02-10 15:00           ` Jan Kiszka
2021-02-11  5:04             ` Greg Gallagher
2021-02-24 10:24       ` Henning Schild
2021-02-24 11:35         ` Henning Schild
2021-02-24 12:46           ` Jan Kiszka
2021-02-25 13:54             ` Philippe Gerum [this message]
2021-02-25 13:57               ` Jan Kiszka
2021-02-25 14:18                 ` Philippe Gerum
2021-02-25 14:22                   ` Greg Gallagher
2021-03-01 16:15                   ` Jan Kiszka
2021-03-01 16:34                     ` Greg Gallagher
2021-03-01 16:37                       ` Jan Kiszka
2021-03-01 16:53                     ` Philippe Gerum
2021-03-05  9:32                       ` Jan Kiszka
2021-03-05  9:34                         ` Philippe Gerum
2021-03-05 10:54                           ` Jan Kiszka
2021-03-05 11:29                             ` Philippe Gerum
2021-03-05 11:36                               ` Jan Kiszka

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=87zgzs6ymo.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=henning.schild@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.