Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: "Maíra Canal" <mcanal@igalia.com>,
	"Florian Fainelli" <florian.fainelli@broadcom.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Arnd Bergmann" <arnd@arndb.de>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	bcm-kernel-feedback-list@broadcom.com,
	kernel-list@raspberrypi.com, linux-staging@lists.linux.dev
Subject: Re: [PATCH 4/5] staging: vchiq_arm: Create keep-alive thread during probe
Date: Fri, 27 Jun 2025 17:18:35 +0200	[thread overview]
Message-ID: <232c4fbd-5c5c-4211-831b-2b6d8c757f2d@gmx.net> (raw)
In-Reply-To: <1db32ad6-b699-4a28-abc2-56f8efae38df@igalia.com>

Hi Maíra,

[drop bouncing address from Umang and Ojaswin]

Am 26.06.25 um 22:30 schrieb Maíra Canal:
> Hi Stefan,
>
> On 26/06/25 17:14, Stefan Wahren wrote:
>> Hi Maíra,
>>
>> [add Arnd]
>>
>> Am 26.06.25 um 20:22 schrieb Maíra Canal:
>>> Hi Stefan,
>>>
>>> On 09/03/25 09:50, Stefan Wahren wrote:
>>>> Creating the keep-alive thread in vchiq_platform_init_state have
>>>> the following advantages:
>>>> - abort driver probe if kthread_create fails (more consistent 
>>>> behavior)
>>>> - make resource release process easier
>>>>
>>>> Since vchiq_keepalive_thread_func is defined below
>>>> vchiq_platform_init_state, the latter must be moved.
>>>>
>>>> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
>>>> ---
>>>>   .../interface/vchiq_arm/vchiq_arm.c           | 69 
>>>> +++++++++----------
>>>>   1 file changed, 34 insertions(+), 35 deletions(-)
>>>>
>>>
>>> After this patch landed on 6.12 stable, I started to observe the
>>> following warning in Mesa CI [1]:
>> Is this also reproducible with 6.15.x or mainline ?
>
> I was able to reproduce it with 6.16.0-rc2 [2].
Thanks, does these hangs occur without any Mesa test / are these test 
steps necessary to trigger the issue?

Is this reproducible with a real Raspberry Pi 3 (Plus)?

Do you use arm64/defconfig or a special kernel configuration?

Could you please provide kernel logs from boot until the first hang warning?

Best regards
>
> [2] https://gitlab.freedesktop.org/mairacanal/mesa/-/jobs/79092300
>
> Best Regards,
> - Maíra


  reply	other threads:[~2025-06-27 15:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-09 12:50 [PATCH 0/5] staging: vchiq_arm: Fix & improve resource handling Stefan Wahren
2025-03-09 12:50 ` [PATCH 1/5] staging: vchiq_arm: Register debugfs after cdev Stefan Wahren
2025-03-09 12:50 ` [PATCH 2/5] staging: vchiq_arm: Fix possible NPR of keep-alive thread Stefan Wahren
2025-03-09 12:50 ` [PATCH 3/5] staging: vchiq_arm: Stop kthreads if vchiq cdev register fails Stefan Wahren
2025-03-09 12:50 ` [PATCH 4/5] staging: vchiq_arm: Create keep-alive thread during probe Stefan Wahren
2025-06-26 18:22   ` Maíra Canal
2025-06-26 20:14     ` Stefan Wahren
2025-06-26 20:30       ` Maíra Canal
2025-06-27 15:18         ` Stefan Wahren [this message]
2025-06-27 22:28           ` Maíra Canal
2025-06-28 22:34             ` Stefan Wahren
2025-08-24 18:37               ` MichaIng
2025-08-24 19:58                 ` Stefan Wahren
2025-08-24 20:14                   ` MichaIng
2025-03-09 12:50 ` [PATCH 5/5] staging: vchiq_arm: Improve initial VCHIQ connect Stefan Wahren

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=232c4fbd-5c5c-4211-831b-2b6d8c757f2d@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=dan.carpenter@linaro.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-list@raspberrypi.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mcanal@igalia.com \
    /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