All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@lists.linux.dev>
Subject: Re: 5.15-dovetail or mainline regression?
Date: Sun, 03 Jul 2022 16:05:13 +0200	[thread overview]
Message-ID: <87wncuthpb.fsf@xenomai.org> (raw)
In-Reply-To: <ff6f30d3-ae56-3d13-efb8-6d51ca231ca5@siemens.com>


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

> On 21.06.22 08:47, Jan Kiszka wrote:
>> On 21.06.22 08:10, Jan Kiszka wrote:
>>> https://source.denx.de/Xenomai/xenomai-images/-/jobs/452968 (qemu-arm64) 
>>>
>>> 2022-06-20T23:57:39 [    0.337643] printk: console [ttyAMA0] enabled
>>> 2022-06-20T23:57:39 [    0.349807] Unable to handle kernel paging request at virtual address ffff80003675c000
>>> ...
>>> 2022-06-20T23:57:39 [    0.359334] Call trace:
>>> 2022-06-20T23:57:39 [    0.359508]  locked_inode_to_wb_and_lock_list+0x60/0x180
>>> 2022-06-20T23:57:39 [    0.359577]  __mark_inode_dirty+0x2e0/0x430
>>> 2022-06-20T23:57:39 [    0.359603]  simple_setattr+0x50/0x80
>>> 2022-06-20T23:57:39 [    0.359617]  notify_change+0x37c/0x3f0
>>> 2022-06-20T23:57:39 [    0.359636]  handle_create+0x1b0/0x21c
>>> 2022-06-20T23:57:39 [    0.359669]  devtmpfsd+0x80/0xd0
>>> 2022-06-20T23:57:39 [    0.359688]  kthread+0x150/0x160
>>> 2022-06-20T23:57:39 [    0.359707]  ret_from_fork+0x10/0x20
>>> 2022-06-20T23:57:39 [    0.360029] Code: 11000421 b90012a1 d538d081 8b010000 (c85f7c03) 
>>> 2022-06-20T23:57:39 [    0.369411] ---[ end trace 91ca49b5035e8050 ]---
>>>
>>> Hitting retry now to see if it sticks. The real arm64 target was stuck 
>>> in u-boot (tftp), so I cannot tell yet if it is only a side-effect of 
>>> emulation.
>>>
>> 
>> The issue with QEMU sticks:
>> https://source.denx.de/Xenomai/xenomai-images/-/jobs/453115
>> 
>> But now CI is failing in the infrastructure, so I can't retest on hikey.
>> 
>
> Mainline stable regression of
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bafbc134f5b0948aa1ca015a0dff70b02c0152b7
> (5.15.47), fixed by
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ca67881dcef04c5b586a3b122307b183babd62dc
> (5.15.49).
>
> Philippe, could you refresh v5.15.y-dovetail-rebase to consume this and
> fix our CI again?
>

Should be ok by now.

-- 
Philippe.

      reply	other threads:[~2022-07-03 14:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21  6:10 5.15-dovetail or mainline regression? Jan Kiszka
2022-06-21  6:47 ` Jan Kiszka
2022-06-21  7:19   ` Bezdeka, Florian
2022-06-21  7:25     ` Jan Kiszka
2022-06-29 16:56   ` Jan Kiszka
2022-07-03 14:05     ` Philippe Gerum [this message]

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=87wncuthpb.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@lists.linux.dev \
    /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.