Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: MichaIng <micha@dietpi.com>
Cc: arnd@arndb.de, bcm-kernel-feedback-list@broadcom.com,
	dan.carpenter@linaro.org, florian.fainelli@broadcom.com,
	gregkh@linuxfoundation.org, kernel-list@raspberrypi.com,
	kieran.bingham@ideasonboard.com,
	laurent.pinchart@ideasonboard.com,
	linux-arm-kernel@lists.infradead.org,
	linux-staging@lists.linux.dev, mcanal@igalia.com
Subject: Re: [PATCH 4/5] staging: vchiq_arm: Create keep-alive thread during probe
Date: Sun, 24 Aug 2025 21:58:07 +0200	[thread overview]
Message-ID: <8e51d9c4-512a-4b98-8ef7-e08a259cbf07@gmx.net> (raw)
In-Reply-To: <dafff4b4-f022-453e-935f-6d79c4c57292@dietpi.com>

Hi Micha,

Am 24.08.25 um 20:37 schrieb MichaIng:
> > Okay, after disabling all VCHIQ users including VCHIQ_CDEV and 
> enabling DETECT_HUNG_TASK, i was able to reproduce it.
>
> > I will try to fix that.
>
> Hi Stefan,
>
> is there any progress in this regards, or a way we can help? Would it 
> make sense to share the issue to the RPi Ltd. downstream repository?
> https://github.com/raspberrypi/linux
this issue has been fixed in mainline/stable by reverting the commit in 
July. So downstream should have received the fix, too.

Best regards
>
> We ship images with downstream RPi Ltd. kernel packages, but with 
> non-GUI/server setups and low memory usage in mind, we 
> disable/blacklist camera and GPU related kernel modules by default, 
> and reduce the dedicated GPU memory to the minimal 16 MiB, so that our 
> users report as well these errors every few minutes on their main 
> console, until GUI, video codec, or camera features are enabled.
>
> I am thinking about letting one kernel module load by default which 
> releases the hanging task. But the majority of systems are headless, 
> and really don't require any of those. Reducing the console log level 
> or muting hung task timeout messages would be another workaround, but 
> that could mute important messages as well.
>
> Just in case someone else is in the same situation: I found the VC CMA 
> driver "vc_sm_cma" module to be the lightest way of releasing the 
> waiting task. Other than the camera/video modules, it does not pull in 
> a large stack of dependency modules. With less than 32 MiB GPU memory 
> (where the cut-down firmware is used automatically), it fails to 
> initialise, but releases the vchiq-keep thread regardless. Its size is 
> also tiny compared to the Broadcom camera/video drivers.
>



  reply	other threads:[~2025-08-24 20:01 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
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 [this message]
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=8e51d9c4-512a-4b98-8ef7-e08a259cbf07@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 \
    --cc=micha@dietpi.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