All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Amit Daniel Kachhap <amit.kachhap@gmail.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Goran <goran.brkuljan@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Power Management <linux-pm@vger.kernel.org>
Subject: Re: Fwd: XPS 17 9730 runs significantly warmer on Kernel 6.5-rc3 compared to Kernel 6.4.3
Date: Fri, 28 Jul 2023 08:31:12 +0700	[thread overview]
Message-ID: <ZMMaYLcc5G4KSVyf@debian.me> (raw)
In-Reply-To: <4aaf1d3d-2ab7-2d3a-f597-a1741bf699d6@gmail.com>

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

On Thu, Jul 27, 2023 at 09:25:19PM +0700, Bagas Sanjaya wrote:
> Hi,
> 
> I notice a regression report on Bugzilla [1]. Quoting from it:
> 
> > On my new XPS 17 9730 laptop, I recently installed the Kernel 6.5-rc3. I noticed, however, that during its operation, the laptop was getting significantly warmer than before. I did some analysis using the 'stress' tool to measure and compare the difference in CPU temperatures between Kernel 6.4.3 and Kernel 6.5-rc3. Here are my results:
> > 
> > OS: Ubuntu 23.10
> > CPU: i7-13700H
> > 
> > kernel 6.4.3:
> >                                                                                                                                                                                         
> > Initial CPU temperature:
> > coretemp-isa-0000
> > Core 0:        +47.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 4:        +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 8:        +46.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 12:       +46.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 16:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 20:       +44.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 24:       +44.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 25:       +44.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 26:       +44.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 27:       +44.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 28:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 29:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 30:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 31:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Stressing CPU for 30 seconds...
> > stress: info: [4858] dispatching hogs: 14 cpu, 0 io, 0 vm, 0 hdd
> > stress: info: [4858] successful run completed in 30s
> > CPU temperature immediately after stress test:
> > coretemp-isa-0000
> > Core 0:        +67.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 4:        +76.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 8:        +69.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 12:       +77.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 16:       +69.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 20:       +76.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 24:       +68.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 25:       +68.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 26:       +68.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 27:       +68.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 28:       +71.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 29:       +71.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 30:       +71.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 31:       +71.0°C  (high = +100.0°C, crit = +100.0°C)
> > Test ended at: Tue Jul 25 01:10:16 PM CEST 2023
> > 
> > 
> > kernel 6.5-rc-3:
> > 
> > Initial CPU temperature:
> > coretemp-isa-0000
> > Core 0:        +46.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 4:        +46.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 8:        +46.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 12:       +46.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 16:       +44.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 20:       +44.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 24:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 25:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 26:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 27:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 28:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 29:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 30:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 31:       +45.0°C  (high = +100.0°C, crit = +100.0°C)
> > Stressing CPU for 30 seconds...
> > stress: info: [11146] dispatching hogs: 14 cpu, 0 io, 0 vm, 0 hdd
> > stress: info: [11146] successful run completed in 30s
> > CPU temperature immediately after stress test:
> > coretemp-isa-0000
> > Core 0:        +84.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 4:        +97.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 8:        +87.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 12:      +100.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 16:       +86.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 20:       +99.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 24:       +83.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 25:       +83.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 26:       +83.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 27:       +83.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 28:       +89.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 29:       +89.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 30:       +89.0°C  (high = +100.0°C, crit = +100.0°C)
> > Core 31:       +89.0°C  (high = +100.0°C, crit = +100.0°C)
> > Test ended at: Tue Jul 25 01:05:42 PM CEST 2023
> > 
> > I tested few times with different setup and CPU temp on 6.5-rc3 is always higher especially when stressing with fewer cores.
> 
> See Bugzilla for the full thread.
> 
> Goran: On Tuesday, I asked you to perform bisection. Any update on it?
> 
> Anyway, I'm adding this regression to regzbot:
> 
> #regzbot introduced: v6.4..v6.5-rc3 https://bugzilla.kernel.org/show_bug.cgi?id=217703
> #regzbot title: significant temperature increase on XPS 17 9730
> 
> Thanks.
> 
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217703
> 

Oops, I accidentally duped this. My email client was stuck sending it
(but got delivered anyway), thus:

#regzbot dup-of: https://lore.kernel.org/regressions/107f05b8-0104-501c-130c-4f89f3f8a628@gmail.com/

-- 
An old man doll... just what I always wanted! - Clara

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

  reply	other threads:[~2023-07-28  1:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 14:25 Fwd: XPS 17 9730 runs significantly warmer on Kernel 6.5-rc3 compared to Kernel 6.4.3 Bagas Sanjaya
2023-07-28  1:31 ` Bagas Sanjaya [this message]
2023-07-28  7:00   ` Bagas Sanjaya
  -- strict thread matches above, loose matches on Subject: below --
2023-07-27 14:24 Bagas Sanjaya
2023-07-28 13:42 ` Thorsten Leemhuis
     [not found]   ` <CANhdOJEq-+KaMv=TX7E4ggf7rm456ibha2W_+Y5m1580ngCw_A@mail.gmail.com>
2023-07-28 19:43     ` 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=ZMMaYLcc5G4KSVyf@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=amit.kachhap@gmail.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=goran.brkuljan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.