linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 6.10-rc1
Date: Thu, 13 Jun 2024 13:09:26 +0200	[thread overview]
Message-ID: <ZmrTZozoi0t/tuva@duo.ucw.cz> (raw)
In-Reply-To: <CAHk-=wjQv_CSPzhjOMoOjGO3FmuHe5hzm6Ds69zZSFPa4PeuCA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]

Hi!

> Ok, the merge window is over, and 6.10-rc1 is tagged and pushed out.
> 
> This seems to be a regular-sized release, maybe even slightly on the
> smaller side. All the stats look fairly normal, but "normal" obviously
> means "much too big to post the shortlog", so below is - as always -
> just my "merge log" that gives an overview of who I've merged from
> with just the barest of descriptions.
> 
> We don't have any new filesystems, and the xfs online repair work
> means that the bcachefs fixes aren't even the biggest filesystem
> change any more. But all of that is dwarfed by all the usual driver
> updates (and, as is tradition, GPU drivers are in a massive lead, with
> networking a distant second and everything else is relatively small).
> 
> But we do have all the usual architecture updates, core cleanups and
> fixes, tooling and documentation updates.
> 
> Please - let the testing commence,

I tried ~6.10-rc1 for a week or so, and it something was very wrong with
the performance, likely to do with graphics. Thinkpad X220.

It looked like GPU is working way harder than usual, leading to
machine overheating and thermal throttling, making machine _really_
unusable.

I went back to 6.9, and things seem better. At least "have to buy new
machine" feeling is gone.

Unfortunately, these GPU perfromance issues are not exactly to
confirm/debug. Hints would be welcome.

Best								Pvel

-- 
People of Russia, stop Putin before his war on Ukraine escalates.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2024-06-13 11:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-26 22:31 Linux 6.10-rc1 Linus Torvalds
2024-05-27  7:50 ` Build regressions/improvements in v6.10-rc1 Geert Uytterhoeven
2024-05-27  8:21   ` Geert Uytterhoeven
2024-05-30 16:48 ` Linux 6.10-rc1 Guenter Roeck
2024-06-13 11:09 ` Pavel Machek [this message]
2024-06-13 16:17   ` Linus Torvalds
2024-06-14  9:02     ` Pavel Machek
2024-06-14 16:21       ` Linus Torvalds
2024-06-14 17:04         ` Linus Torvalds
2024-06-14 20:13           ` Pavel Machek
2024-06-14 20:24           ` Pavel Machek
2024-06-17  9:27           ` Pavel Machek
2024-06-19 10:43             ` Pavel Machek
2024-06-19 15:52               ` Linus Torvalds
2024-07-08 12:03                 ` Pavel Machek
2024-06-19 16:52               ` Gerhard Stoiber

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=ZmrTZozoi0t/tuva@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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).