[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABXGCsP9vPxu=hN5CO5MPJ5QVNJURKsBbbeb-NLoq60=M=CN3Q@mail.gmail.com>
Date: Thu, 13 Feb 2025 20:27:24 +0500
From: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
To: Chuck Lever <chuck.lever@...cle.com>
Cc: brauner@...nel.org,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
Linux regressions mailing list <regressions@...ts.linux.dev>, linux-fsdevel@...r.kernel.org,
chromium-dev@...omium.org
Subject: Re: 6.14/regression/bisected - commit b9b588f22a0c somehow broke HW
acceleration in the Google Chrome
On Thu, Feb 13, 2025 at 7:18 PM Chuck Lever <chuck.lever@...cle.com> wrote:
> I need a simpler reproducer, please. "Chrome stopped working" doesn't
> give me anything actionable.
>
After applying commit b9b588f22a0c, the internal page chrome://gpu/ in
Google Chrome indicates that GPU acceleration is no longer functional.
I apologize, but as I am not a Google Chrome engineer, I have no idea
how to create more clean reproducer code.
I only noticed as a Web browser user that when I scrolled through
pages with a lot of images, Google Chrome got substantially sluggish.
Hopefully, someone from chromium-dev will read my message and help us.
--
Best Regards,
Mike Gavrilov.
Powered by blists - more mailing lists