From: Pavel Skripkin <paskripkin@gmail.com>
To: "Maximilian Böhm" <maximilian.boehm@elbmurf.de>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>
Cc: hverkuil-cisco@xs4all.nl, sashal@kernel.org,
linux-media@vger.kernel.org, Brad Love <brad@nextdimension.cc>
Subject: Re: Kernel hangs after DVB patch from July 2021 with Hauppauge WinTV dualHD
Date: Tue, 4 Jan 2022 20:31:16 +0300 [thread overview]
Message-ID: <12440c22-9f69-740d-bcfd-3b6bf0e4dcc1@gmail.com> (raw)
In-Reply-To: <5c891c4a-7a02-18b7-c4c1-8429fcd3366f@elbmurf.de>
On 1/4/22 20:22, Maximilian Böhm wrote:
> Hey Pavel,
>
> did you have time to look into this issue further?
>
Hi Maximilian,
I did give it a try, but looking at the code didn't give any results :(
It's a bit hard to debug without reproducer or real hw piece
With regards,
Pavel Skripkin
next prev parent reply other threads:[~2022-01-04 17:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 1:09 Kernel hangs after DVB patch from July 2021 with Hauppauge WinTV dualHD Maximilian Böhm
2021-12-18 9:15 ` Mauro Carvalho Chehab
2021-12-18 14:23 ` Pavel Skripkin
2021-12-18 22:50 ` Maximilian Böhm
2021-12-20 14:39 ` Pavel Skripkin
2022-01-04 17:22 ` Maximilian Böhm
2022-01-04 17:31 ` Pavel Skripkin [this message]
2022-01-04 17:58 ` Maximilian Böhm
2022-01-06 11:54 ` Pavel Skripkin
2022-01-06 11:57 ` Pavel Skripkin
2022-01-20 19:29 ` Maximilian Böhm
2022-01-20 19:37 ` [PATCH] Revert "media: em28xx: add missing em28xx_close_extension" Pavel Skripkin
2022-01-21 18:30 ` Maximilian Böhm
2022-01-20 19:42 ` Kernel hangs after DVB patch from July 2021 with Hauppauge WinTV dualHD Pavel Skripkin
2022-02-17 11:14 ` Hans Verkuil
2022-02-18 0:16 ` Maximilian Böhm
2022-02-18 7:58 ` Hans Verkuil
2021-12-18 20:33 ` Robert Schlabbach
2021-12-18 20:51 ` Pavel Skripkin
2021-12-18 23:19 ` Maximilian Böhm
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=12440c22-9f69-740d-bcfd-3b6bf0e4dcc1@gmail.com \
--to=paskripkin@gmail.com \
--cc=brad@nextdimension.cc \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=maximilian.boehm@elbmurf.de \
--cc=mchehab+huawei@kernel.org \
--cc=sashal@kernel.org \
/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