MIME-Version: 1.0
References: <20230316094129.846802350@linuxfoundation.org> <ZBQ/rhv9nP+i8Pyc@debian>
 <ZBRjTid0Hc4V7bwB@kroah.com>
In-Reply-To: <ZBRjTid0Hc4V7bwB@kroah.com>
From:   Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Date:   Fri, 17 Mar 2023 13:21:03 +0000
Message-ID: <CADVatmOU9nJQDo7OGDNGppU8eci98yqsJzxYLjT=NPXqv8BbDg@mail.gmail.com>
Subject: Re: [PATCH 4.19 00/27] 4.19.278-rc3 review
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc:     stable@vger.kernel.org, patches@lists.linux.dev,
        linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
        akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
        patches@kernelci.org, lkft-triage@lists.linaro.org, pavel@denx.de,
        jonathanh@nvidia.com, f.fainelli@gmail.com, srw@sladewatkins.net,
        rwarsow@gmx.de
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hi Greg,

On Fri, 17 Mar 2023 at 12:55, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Fri, Mar 17, 2023 at 10:23:42AM +0000, Sudip Mukherjee wrote:
> > Hi Greg,
> >
> > On Thu, Mar 16, 2023 at 10:42:14AM +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.19.278 release.
> > > There are 27 patches in this series, all will be posted as a response
> > > to this one.  If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by Sat, 18 Mar 2023 09:41:20 +0000.
> > > Anything received after that time might be too late.
> >
> > Build test (gcc version 11.3.1 20230311):
> > mips: 63 configs -> no  failure
> > arm: 115 configs -> no failure
> > arm64: 2 configs -> no failure
> > x86_64: 4 configs -> no failure
> > alpha allmodconfig -> no failure
> > powerpc allmodconfig -> no failure
> > riscv allmodconfig -> no failure
> > s390 allmodconfig -> no failure
> > xtensa allmodconfig -> no failure
> >
> > Boot test:
> > x86_64: Booted on qemu. No regression. [1]
> >
> > Boot Regression on test laptop:
> > Only black screen but ssh worked, so from the dmesg it seems i915 failed.
>
> Can you bisect this?

There was no need to bisect. Only one i915 related commit was there
and reverting that has fixed it for me.

9a0789a26289 ("drm/i915: Don't use BAR mappings for ring buffers with LLC")
commit 85636167e3206c3fbd52254fc432991cc4e90194 upstream.


-- 
Regards
Sudip