linux-kernel - Re: [PATCH] media: venus: Synchronize probe() between venus

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 27 Oct 2021 19:36:56 -0700
From:   John Stultz <john.stultz@...aro.org>
To:     Tadeusz Struk <tadeusz.struk@...aro.org>
Cc:     Stanimir Varbanov <stanimir.varbanov@...aro.org>,
        Andy Gross <agross@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Lee Jones <lee.jones@...aro.org>,
        Amit Pundir <amit.pundir@...aro.org>,
        linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] media: venus: Synchronize probe() between venus_core and enc/dec

On Wed, Oct 27, 2021 at 5:19 PM Tadeusz Struk <tadeusz.struk@...aro.org> wrote:
>
> Hi John,
> On 10/27/21 17:01, John Stultz wrote:
> >    Thanks so much for sending this out, I definitely would like to see
> > these crashes sorted!
> >
> > Unfortunately this patch causes some odd behavior when I use it with a
> > modular config.  The display does not start up and trying to reboot
> > the board ends up with it hanging instead of rebooting.
> >
> > And booting with this patch in my non-modular config, it just seems to
> > get stuck during bootup (I suspect waiting on firmware that's not yet
> > mounted?).
> >
>
> Thanks for trying the patch. With this patch I was able to boot android13
> running 5.15.0-rc4-mainlineon on my Dragonboard 845c with the default
> config common/build.config.db845c. Without it it was crashing.

Hrm.. For my module enabled build I'm using the current
android-mainline as well w/ AOSP.

Still seeing some odd behavior, but I'm trying to isolate what change
in your patch is causing it (as it's not obvious).

thanks
-john