From: Daniel Scally <djrscally@gmail.com>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: mchehab+huawei@kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: Kernel oops bisected to media: videobuf2: move cache_hints handling to allocators
Date: Thu, 2 Dec 2021 11:20:59 +0000 [thread overview]
Message-ID: <8dc4414d-af47-d92f-e255-ccc07fc96b42@gmail.com> (raw)
In-Reply-To: <d4be3ea9-5d41-0a19-c03c-4037d01d1b6a@xs4all.nl>
Hello
On 02/12/2021 11:15, Hans Verkuil wrote:
> Daniel: ping!
>
> On 20/11/2021 04:26, Sergey Senozhatsky wrote:
>> Hello,
>>
>> On (21/11/19 22:41), Daniel Scally wrote:
>>> Hi all
>>>
>>> I've been experiencing an oops trying to run libcamera's qcam util
>>> (which starts streaming on a camera sensor - the ov8865), which I
>>> bisected down to the patch cde513fd9b35: "media: videobuf2: move
>>> cache_hints handling to allocators"
>> Can you please check if you have these two patches in your tree:
>>
>> https://lore.kernel.org/lkml/20210928034634.333785-1-senozhatsky@chromium.org/raw
>> https://lore.kernel.org/all/20211101145355.533704-1-hdegoede@redhat.com/raw
>>
>> If not then please apply, this should fix the problems you're seeing.
>>
> I really like to know if the cause is indeed that you are missing two patches.
I'm sorry, I missed this. I'll check it asap and let you know.
>
> Regards,
>
> Hans
next prev parent reply other threads:[~2021-12-02 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 22:41 Kernel oops bisected to media: videobuf2: move cache_hints handling to allocators Daniel Scally
2021-11-20 3:26 ` Sergey Senozhatsky
2021-12-02 11:15 ` Hans Verkuil
2021-12-02 11:20 ` Daniel Scally [this message]
2021-12-07 21:41 ` Daniel Scally
2021-12-08 9:27 ` Hans Verkuil
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=8dc4414d-af47-d92f-e255-ccc07fc96b42@gmail.com \
--to=djrscally@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=senozhatsky@chromium.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 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.