All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Thomas Voegtle <tv@lio96.de>
Cc: linux-kernel@vger.kernel.org, Hyunwoo Kim <imv4bel@gmail.com>
Subject: Re: Sometimes DVB broken with commit 6769a0b7ee0c3b
Date: Mon, 5 Jun 2023 11:17:15 +0100	[thread overview]
Message-ID: <20230605111715.4c0ba2ed@sal.lan> (raw)
In-Reply-To: <da5382ad-09d6-20ac-0d53-611594b30861@lio96.de>

Em Tue, 30 May 2023 13:12:57 +0200 (CEST)
Thomas Voegtle <tv@lio96.de> escreveu:

> Hello,
> 
> 
> I have the problem that sometimes my DVB card does not initialize 
> properly booting Linux 6.4-rc4.
> This is not always, maybe in 3 out of 4 attempts.
> When this happens somehow you don't see anything special in dmesg, but the 
> card just doesn't work.

Can you paste the full dmesg?

> 
> Reverting this helps:
> commit 6769a0b7ee0c3b31e1b22c3fadff2bfb642de23f
> Author: Hyunwoo Kim <imv4bel@gmail.com>
> Date:   Thu Nov 17 04:59:22 2022 +0000
> 
>      media: dvb-core: Fix use-after-free on race condition at dvb_frontend

What do you mean by helps? Does it fix it every time, or it just
reduces the number of init problems?

Regards,
Mauro

  parent reply	other threads:[~2023-06-05 10:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 11:12 Sometimes DVB broken with commit 6769a0b7ee0c3b Thomas Voegtle
2023-05-31 13:31 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-06-05  9:38 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-05 10:37   ` Mauro Carvalho Chehab
2023-06-05 10:44     ` Thorsten Leemhuis
2023-06-05 18:00       ` Mauro Carvalho Chehab
2023-06-12 15:10         ` Linux regression tracking (Thorsten Leemhuis)
2023-06-14 22:20           ` Mauro Carvalho Chehab
2023-06-05 10:17 ` Mauro Carvalho Chehab [this message]
2023-06-05 13:10   ` Thomas Voegtle
2023-06-05 17:43     ` Mauro Carvalho Chehab

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=20230605111715.4c0ba2ed@sal.lan \
    --to=mchehab@kernel.org \
    --cc=imv4bel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tv@lio96.de \
    /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.