1) Yup, system not hangs up, but I feel the system response slower when it
happens. E.g. keyboard mouse not work for seconds. I can check if the
cpufreq be changed next time I get machine.

2) Not saw the over temperature by command sensors. Isn't it reported from
sysfs? If not, I can check it  next time I get machine.


Kai-Heng Feng <kai.heng.f...@canonical.com> 於 2019年7月24日 週三 下午4:11 寫道:

> Alex,
>
> 1) This warning should be harmless. Does it affect actual usage?
> 2) What's the temperature reports under thermal_zones sysfs?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1781924
>
> Title:
>   Kernel wrong temperature reporting
>
> Status in OEM Priority Project:
>   New
> Status in linux package in Ubuntu:
>   Expired
>
> Bug description:
>   I'm having some thermal trouble since I've started using kernel >4.0.x
>   with my new laptop. According to psensor and sensord, CPU temperature
>   jumps above the 90C, stays there for around 1second, and goes back to
>   50C. All transitions happen in around 100ms. I've cleaned and re-
>   applied thermal paste and checked the connections twice. More
>   interestingly, this doesn't happen when the CPU is under heavy-load,
>   but when it is waiting idly. Sometimes sensord reports the CPU temp
>   has gone over the critical threshold of the CPU and device shuts down
>   itself immediately.
>
>   There is also Windows 10 installed as a dual boot and didn't see this
>   problem on it when idle or under heavy load.
>
>   Dmesg output is full of following warnings;
>
>   [ 1282.296247] CPU0: Core temperature above threshold, cpu clock
> throttled (total events = 109)[ 1282.296267] CPU4: Core temperature above
> threshold, cpu clock throttled (total events = 109)
>   [ 1282.296269] CPU5: Package temperature above threshold, cpu clock
> throttled (total events = 220)
>   [ 1282.296269] CPU1: Package temperature above threshold, cpu clock
> throttled (total events = 220)
>   [ 1282.296271] CPU4: Package temperature above threshold, cpu clock
> throttled (total events = 220)
>   [ 1282.296272] CPU6: Package temperature above threshold, cpu clock
> throttled (total events = 220)
>   [ 1282.296273] CPU2: Package temperature above threshold, cpu clock
> throttled (total events = 220)
>   [ 1282.296274] CPU7: Package temperature above threshold, cpu clock
> throttled (total events = 220)
>   [ 1282.296275] CPU3: Package temperature above threshold, cpu clock
> throttled (total events = 220)
>   [ 1282.296281] CPU0: Package temperature above threshold, cpu clock
> throttled (total events = 220)
>   [ 1282.297226] CPU4: Core temperature/speed normal
>   [ 1282.297227] CPU5: Package temperature/speed normal
>   [ 1282.297228] CPU0: Core temperature/speed normal
>   [ 1282.297229] CPU1: Package temperature/speed normal
>   [ 1282.297229] CPU0: Package temperature/speed normal
>   [ 1282.297230] CPU4: Package temperature/speed normal
>   [ 1282.297233] CPU3: Package temperature/speed normal
>   [ 1282.297233] CPU7: Package temperature/speed normal
>   [ 1282.297269] CPU2: Package temperature/speed normal
>   [ 1282.297269] CPU6: Package temperature/speed normal
>
>   Because of wrong temperature reporting, kernel throttles the CPU and
>   reduces overall performance, which results in frustrating user
>   experience.
>
>   I've tried followings and find a temporary solution;
>    - intel_pstate enabled, turbo-boost enabled > problem exists
>    - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
>    - intel_pstate disabled, governor set to anythig other than powersave >
> problem exists
>    - intel_pstate disabled, governor set to powersave > problem frequency
> reduced
>
>   I'm suspicious about a kernel bug such as;
>   - https://bugzilla.redhat.com/show_bug.cgi?id=924570
>   - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   AudioDevicesInUse:
>    USER        PID ACCESS COMMAND
>    /dev/snd/pcmC0D7p:   burak      1547 F...m pulseaudio
>    /dev/snd/controlC0:  burak      1547 F.... pulseaudio
>   CurrentDesktop: X-Cinnamon
>   DistroRelease: Linux Mint 19
>   HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
>   Lsusb:
>    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>    Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp.
>    Bus 001 Device 003: ID 8087:0a2b Intel Corp.
>    Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
>    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: ASUSTeK COMPUTER INC. UX430UNR
>   NonfreeKernelModules: nvidia_modeset nvidia
>   Package: linux (not installed)
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic
> root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash
> intel_pstate=disable vt.handoff=1
>   ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
>   RelatedPackageVersions:
>    linux-restricted-modules-4.15.0-24-generic N/A
>    linux-backports-modules-4.15.0-24-generic  N/A
>    linux-firmware                             1.173.1
>   Tags:  tara
>   Uname: Linux 4.15.0-24-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 11/28/2017
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: UX430UNR.302
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: UX430UNR
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: 1.0
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK COMPUTER INC.
>   dmi.chassis.version: 1.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrUX430UNR.302:bd11/28/2017:svnASUSTeKCOMPUTERINC.:pnUX430UNR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UNR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>   dmi.product.family: UX
>   dmi.product.name: UX430UNR
>   dmi.product.version: 1.0
>   dmi.sys.vendor: ASUSTeK COMPUTER INC.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/oem-priority/+bug/1781924/+subscriptions
>


** Bug watch added: Red Hat Bugzilla #924570
   https://bugzilla.redhat.com/show_bug.cgi?id=924570

** Bug watch added: Red Hat Bugzilla #1317190
   https://bugzilla.redhat.com/show_bug.cgi?id=1317190

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781924

Title:
  Kernel wrong temperature reporting

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak      1547 F...m pulseaudio
   /dev/snd/controlC0:  burak      1547 F.... pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware                             1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UNR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UNR.302:bd11/28/2017:svnASUSTeKCOMPUTERINC.:pnUX430UNR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UNR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UNR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1781924/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to