linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)"  <regressions@leemhuis.info>
To: Chris McGimpsey-Jones <chrisjones.unixmen@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: Latest RC causing web browser crash
Date: Thu, 16 Feb 2023 12:10:28 +0100	[thread overview]
Message-ID: <e503afb9-df36-5b98-6b1b-e1ad3a9d13a7@leemhuis.info> (raw)
In-Reply-To: <ee9518a8-64ce-142d-ecfd-f560978352b0@leemhuis.info>

On 30.01.23 11:11, Linux kernel regression tracking (Thorsten Leemhuis)
wrote:
> On 28.01.23 02:14, Chris McGimpsey-Jones wrote:
>> Is anyone else with the latest RC having issues with Google Chrome
>> browser, causing it to crash after a couple of minutes?
> FWIW, this is unlikely to get any traction: nearly nobody reads the LKML
> anymore, hence it's unlikely that someone that can help will see it.

FWIW, I pointed to this problem in my weekly reports, but there was no
reaction. That sound like this is something rare which might only happen
on your machine.

Is the problem actually still occuring?

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

>> I reverted (temporarily) back to Linux 6.1.0 and it's fine.
>> Tested a couple of times, the issue can be reproduced.
> 
> Are there any crash dumps that might indicate what might cause the problem?
> 
>> I don't know of the relationship between the kernel and web browser
>> and it seems odd the kernel would cause this problem, but there's no
>> disputing it is the cause as I can reproduce the issue.
> 
> Well, things like this don't happen frequently, but they do happen.
> Without more data it's just very hard to get to the root of this issue,
> as it could be caused by all sorts of things (mm and drm are two most
> likely suspects, but it could be something totally different).
> 
> Could you try to bisect the issue? There are various pages on the net
> that explain how to do that.

  reply	other threads:[~2023-02-16 11:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28  1:14 Latest RC causing web browser crash Chris McGimpsey-Jones
2023-01-30 10:11 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-16 11:10   ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-02-22 15:45     ` Linux regression tracking #update (Thorsten Leemhuis)

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=e503afb9-df36-5b98-6b1b-e1ad3a9d13a7@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=chrisjones.unixmen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).