mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: "jackson.lee" <jackson.lee@chipsnmedia.com>,
	"mchehab@kernel.org"	 <mchehab@kernel.org>,
	"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
	 "bob.beckett@collabora.com"	 <bob.beckett@collabora.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	 "linux-kernel@vger.kernel.org"	 <linux-kernel@vger.kernel.org>,
	"lafley.kim" <lafley.kim@chipsnmedia.com>,
	 "b-brnich@ti.com"	 <b-brnich@ti.com>,
	"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
	Nas Chung	 <nas.chung@chipsnmedia.com>
Subject: Re: [PATCH v3 0/4] Performance improvement of decoder
Date: Tue, 09 Sep 2025 17:33:34 -0400	[thread overview]
Message-ID: <48540d8ee22cf747d2dd591a7869baf1cba6719e.camel@collabora.com> (raw)
In-Reply-To: <SLXP216MB114806E1937625CA3760CA3EED0FA@SLXP216MB1148.KORP216.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]

Le mardi 09 septembre 2025 à 06:16 +0000, jackson.lee a écrit :
> > I tried and reproduce your results. I've used an ISOMP4 file, nothing big,
> > 720p 10min video. After 30s of seeking back and forth I've got a deadlock,
> > with the following kernel log:
> > 
> > vdec 4210000.video-codec: wave5_vpu_firmware_command_queue_error_check:
> > still running: 0x1000
> > 
> > I don't know if its worse then before, but the bug is severe enough to be
> > concern. To reproduce easily, I pick a longer video, seek forward close to
> > the end, and then seek back (gst-play so smaller steps back) very quickly
> > till it reaches position 0, and repeat.
> > 
> > This happened without resolution change happening concurrent to seeks,
> > just a flat, single resolution video. Once I do the same test with an
> > agressive DRC in place, I hit kernel crash. I will share in private email
> > the DRC H.264 sample I'm using, and how to make it bigger so its manually
> > seekable.
> > 
> 
> I tried to reproduce this problem, but I am seeing a different phenomenon.
> Can you let me know your Gstreamer version you are using ?

GStreamer 1.26.5. I retested today and did not reproduce the crash this time,
but did get the "still running" message and stall (recoverable though). You have
to try really hard, it might be worth automating a tests, so it can be more
agressive.

Nicolas

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-09-09 21:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23  0:21 Jackson.lee
2025-06-23  0:21 ` [PATCH v3 1/4] media: chips-media: wave5: Fix SError of kernel panic when closed Jackson.lee
2025-08-29 18:03   ` Nicolas Dufresne
2025-06-23  0:21 ` [PATCH v3 2/4] media: chips-media: wave5: Fix Null reference while testing fluster Jackson.lee
2025-08-29 18:13   ` Nicolas Dufresne
2025-09-09  3:43     ` jackson.lee
2025-06-23  0:21 ` [PATCH v3 3/4] media: chips-media: wave5: Add WARN_ON to check if dec_output_info is NULL Jackson.lee
2025-08-29 18:15   ` Nicolas Dufresne
2025-09-09  3:45     ` jackson.lee
2025-06-23  0:21 ` [PATCH v3 4/4] media: chips-media: wave5: Improve performance of decoder Jackson.lee
2025-08-29 18:01   ` Nicolas Dufresne
2025-09-09  1:42     ` jackson.lee
2025-09-16 11:21   ` Markus Elfring
2025-07-07  0:37 ` [PATCH v3 0/4] Performance improvement " jackson.lee
2025-08-12  7:51   ` jackson.lee
2025-08-29 15:40 ` Nicolas Dufresne
2025-09-09  6:16   ` jackson.lee
2025-09-09 21:33     ` Nicolas Dufresne [this message]
2025-09-10  6:59       ` jackson.lee
2025-09-10 12:56         ` Nicolas Dufresne
2025-09-11  2:04           ` jackson.lee
2025-09-11 12:23             ` Nicolas Dufresne
2025-09-11  4:40           ` jackson.lee
2025-09-15  7:33           ` jackson.lee
2025-09-15 20:14             ` Nicolas Dufresne
2025-09-16  0:40               ` jackson.lee

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=48540d8ee22cf747d2dd591a7869baf1cba6719e.camel@collabora.com \
    --to=nicolas.dufresne@collabora.com \
    --cc=b-brnich@ti.com \
    --cc=bob.beckett@collabora.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=hverkuil@xs4all.nl \
    --cc=jackson.lee@chipsnmedia.com \
    --cc=lafley.kim@chipsnmedia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nas.chung@chipsnmedia.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

all inboxes | Powered by JetHome®