System shuts down abruptly without warning

$ inxi --admin --verbosity=7 --filter --no-host --width
System:
  Kernel: 6.6.8-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=74458dbb-feb8-4898-8716-c7bc82302328 rw amd_iommu=on iommu=pt
    quiet
    cryptdevice=UUID=22c33ed5-bf14-4137-947e-ea101ee86678:luks-22c33ed5-bf14-4137-947e-ea101ee86678
    root=/dev/mapper/luks-22c33ed5-bf14-4137-947e-ea101ee86678
    udev.log_priority=3
  Desktop: i3 v: 4.23 info: i3bar vt: 7 dm: LightDM v: 1.32.0
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: TUXEDO product: TUXEDO Book XUX7 Gen11 v: N/A
    serial: <superuser required> Chassis: Notebook type: 10
    serial: <superuser required>
  Mobo: TUXEDO model: X170SM serial: <superuser required> UEFI: INSYDE
    v: 1.07.03RTR1 date: 07/03/2020
Battery:
  ID-1: BAT0 charge: 92.1 Wh (100.0%) condition: 92.1/96.5 Wh (95.5%)
    volts: 16.3 min: 14.4 model: Notebook BAT type: Li-ion serial: <filter>
    status: full
Memory:
  System RAM: total: 128 GiB available: 125.57 GiB used: 7.45 GiB (5.9%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i9-10900K bits: 64 type: MT MCP arch: Comet Lake
    gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
    model-id: 0xA5 (165) stepping: 5 microcode: 0xF8
  Topology: cpus: 1x cores: 10 tpc: 2 threads: 20 smt: enabled cache:
    L1: 640 KiB desc: d-10x32 KiB; i-10x32 KiB L2: 2.5 MiB desc: 10x256 KiB
    L3: 20 MiB desc: 1x20 MiB
  Speed (MHz): avg: 3573 high: 5300 min/max: 800/5300 scaling:
    driver: intel_pstate governor: powersave cores: 1: 1387 2: 1406 3: 3769
    4: 5300 5: 4901 6: 5300 7: 5300 8: 1272 9: 1090 10: 5300 11: 5300 12: 5300
    13: 1387 14: 4874 15: 5300 16: 5300 17: 5300 18: 1958 19: 802 20: 930
    bogomips: 148040
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs
    ibrs_enhanced ida intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor
    movbe mpx msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid pclmulqdq
    pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdrand rdseed
    rdtscp rep_good sdbg sep sgx sgx_lc smap smep smx ss ssbd sse sse2 sse4_1
    sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust
    tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt
    xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional,
    RSB filling, PBRSB-eIBRS: SW sequence
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU104BM [GeForce RTX 2080 SUPER Mobile / Max-Q]
    vendor: CLEVO/KAPOK driver: nvidia v: 545.29.06 alternate: nouveau,nvidia_drm
    non-free: 545.xx+ status: current (as of 2023-11; EOL~2026-12-xx)
    arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie:
    gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
    bus-ID: 01:00.0 chip-ID: 10de:1ed3 class-ID: 0300
  Device-2: Chicony USB2.0 Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:5 chip-ID: 04f2:b685
    class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.10 compositor: Compton driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 256 s-size: 254x140mm (10.00x5.51")
    s-diag: 290mm (11.42")
  Monitor-1: Unknown-1 mapped: DP-2 res: 2560x1440 hz: 60 dpi: 171
    size: 381x214mm (15x8.43") modes: 3840x2160
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.
Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: CLEVO/KAPOK driver: snd_hda_intel
    v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:06c8 class-ID: 0403
  Device-2: NVIDIA TU104 HD Audio vendor: CLEVO/KAPOK driver: snd_hda_intel
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s bus-ID: 01:00.1 chip-ID: 10de:10f8 class-ID: 0403
  API: ALSA v: k6.6.8-2-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: active 3: pipewire-alsa
    type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 44:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp68s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: ipv6leakintrf0 state: unknown speed: N/A duplex: N/A mac: <filter>
  IP v6: <filter> type: noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-2: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
  IP v6: <filter> virtual: stable-privacy proto kernel_ll scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:10 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: N/A
Logical:
  Message: No logical block device data found.
  Device-1: luks-22c33ed5-bf14-4137-947e-ea101ee86678 maj-min: 254:0
    type: LUKS dm: dm-0 size: 232.59 GiB
  Components:
  p-1: nvme2n1p2 maj-min: 259:2 size: 232.59 GiB
  Device-2: drive2 maj-min: 254:1 type: LUKS dm: dm-1 size: 1.82 TiB
  Components:
  p-1: nvme0n1 maj-min: 259:3 size: 1.82 TiB
  Device-3: drive3 maj-min: 254:2 type: LUKS dm: dm-2 size: 1.82 TiB
  Components:
  p-1: nvme1n1 maj-min: 259:4 size: 1.82 TiB
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 3.88 TiB used: 1.16 TiB (29.8%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Samsung
    model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 70.8 C
  ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Samsung
    model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 69.8 C
  ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 1B2QGXA7 temp: 65.8 C
    scheme: GPT
  ID-4: /dev/sda maj-min: 8:0 vendor: Kingston model: DataTraveler 3.0
    size: 14.44 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.0
    spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: PMAP scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 232.59 GiB size: 227.88 GiB (97.98%)
    used: 114.68 GiB (50.3%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-22c33ed5-bf14-4137-947e-ea101ee86678 label: N/A
    uuid: 74458dbb-feb8-4898-8716-c7bc82302328
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 480 KiB (0.2%) fs: vfat dev: /dev/nvme2n1p1 maj-min: 259:1 label: N/A
    uuid: 1F06-F175
  ID-3: /media/drive2 raw-size: 1.82 TiB size: 1.79 TiB (98.37%)
    used: 850.86 GiB (46.4%) fs: ext4 dev: /dev/dm-1 maj-min: 254:1
    mapped: drive2 label: N/A uuid: N/A
  ID-4: /media/drive3 raw-size: 1.82 TiB size: 1.79 TiB (98.37%)
    used: 218.72 GiB (11.9%) fs: ext4 dev: /dev/dm-2 maj-min: 254:2
    mapped: drive3 label: N/A uuid: N/A
  ID-5: /media/nas raw-size: N/A size: 12.21 TiB used: 6.59 TiB (54.0%)
    fs: cifs dev: /dev/fro
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 1.6 MiB fs: iso9660
  ID-2: /dev/sda2 maj-min: 8:2 size: 4 MiB fs: vfat label: MEMTEST-ESP
    uuid: C4EB-B66B
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-4:2 info: Realtek RTS5411 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
    class-ID: 0900
  Device-1: 1-4.1:4 info: Holtek Keyboard type: keyboard,mouse
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s (183 KiB/s)
    lanes: 1 mode: 1.0 power: 100mA chip-ID: 04d9:0169 class-ID: 0301
  Device-2: 1-4.2:6 info: Logitech G PRO Gaming Mouse type: mouse,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 300mA chip-ID: 046d:c08c class-ID: 0300
    serial: <filter>
  Device-3: 1-4.3:11 info: Canon PIXMA MG2500 Series type: printer
    driver: usblp interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 2mA chip-ID: 04a9:176d class-ID: 0701 serial: <filter>
  Device-4: 1-5:3 info: Integrated Express ITE Device(829x) type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 048d:8910 class-ID: 0300
  Device-5: 1-8:5 info: Chicony USB2.0 Camera type: video driver: uvcvideo
    interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 500mA chip-ID: 04f2:b685 class-ID: 0e02
  Device-6: 1-9:7 info: Integrated Express IT8297 RGB LED Controller
    type: keyboard driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 048d:8297 class-ID: 0301
  Device-7: 1-10:8 info: Synaptics type: <vendor specific> driver: N/A
    interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 06cb:00a8 class-ID: ff00 serial: <filter>
  Device-8: 1-14:10 info: Intel AX200 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0029 class-ID: e001
  Hub-3: 2-0:1 info: super-speed hub ports: 10 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 2-1:3 info: Kingston DataTraveler 100 G3/G4/SE9 G2/50 Kyson
    type: mass storage driver: usb-storage interfaces: 1 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 504mA
    chip-ID: 0951:1666 class-ID: 0806 serial: <filter>
  Hub-4: 2-4:2 info: Realtek Hub ports: 4 rev: 3.1
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0411
    class-ID: 0900
  Hub-5: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-6: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-7: 5-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-8: 6-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-9: 7-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-10: 8-0:1 info: super-speed hub ports: 1 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 68.0 C pch: 97.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 427 Uptime: 5h 32m wakeups: 0 Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
  Packages: pm: pacman pkgs: 1457 libs: 390 tools: pamac,yay Shell: Bash
  v: 5.2.21 running-in: urxvtd inxi: 3.3.31

You don’t seem to have a swap partition defined. That can possibly contribute to random shutdowns. In this instance, it’s unlikely, considering you have 128GB of RAM.

Once again, I think this points to hardware, rather than Manjaro. It might be best to have a local computer repair shop look at it.

1 Like

All your drive temperatures are rather in the higher range of what is being acceptable.

2 Likes

You might consider re-evaluating whatever cooling you have. Perhaps use more chassis fans better positioned to cool the drives. Overheating will cause shutdowns randomly, depending on how hard you’re cooking the computer at any given time.

Playing intensive games (for example) can drive temperatures to the point that the CPU can no longer cope; and the system shuts down. If it’s a particularly good computer, shutdown will be triggered before damage can occur.

1 Like

@Wollie @soundofthunder

All your drive temperatures are rather in the higher range of what is being acceptable.

Good point. I have now put the notebook on a stand, to lift it off the table. I guess it will help some.

You might consider re-evaluating whatever cooling you have. Perhaps use more chassis fans better positioned to cool the drives.

It is not easy to do much with the internal fans, as it is a notebook. But it unfortunately gets quite hot. I hope the stand will help.

I think this points to hardware, rather than Manjaro. It might be best to have a local computer repair shop look at it.

Yes, you might be right. Luckily the system is still under warranty, so I will contact support. I will report back here with the findings.

I appreciate all inputs!

Yes, a momentary lapse of reason (thinking it a desktop) :). Possibly the internal fans could be replaced (again, by your local repairer), or at least cleaned thoroughly, if you can’t reach them yourself.

I dare say it will. Blocking the air intake is one of the more common reasons for laptop overheating (running it flat on a table, the floor, a bed, or on a cushion).

The stand you describe can certainly help in most cases. Be sure to let us know the outcome. Cheers.

1 Like

Yes, you are right. After having put the computer on a stand instead of directly on the table, the drive temperatures seems to have dropped around 20 degrees, from around 70 to 50 C. I should have done that before!

  ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: Samsung
    model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 53.9 C
  ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Samsung
    model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 50.9 C
  ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 1B2QGXA7 temp: 47.9 C
    scheme: GPT

When I have more info I will report back to HQ :smiley:

1 Like

This is a powerful Clevo gaming laptop sold with a linux os option, (Tuxedo and Schenker are 2 of their German brands) and they are getting hot quickly and need regular clean-outs. On the plus side they offer very easy access and allow opening the case without losing warranty.

Those laptops have decent support and get a fair amount of ec/bios updates (always do ec first) when they are new, so check for updates on the Tuxedo site. You do not need windows to upgrade them.
Once you’re up-to-date check your bios for any performance options and try if any changes there might help your issue. Warning: Unfortunately there are problems with Comet Lake U CPUs and Undervolting. It may happen that the system “freezes” with activated Undervolting.

3 Likes

Thank you for the info, @6x12! Tuxedo support have asked my to update the Samsung SSD Firmware, to see if that helps. So far I have been unable to create a bootable USB drive, as the Samsung iso seems a bit problematic. However, I shall try another USB drive, to see if that makes any difference.

The temperatures also is a lot healthier after I put the notebook on a stand. I will check if I can easily clean the fans on the inside (from the outside things look clean), to make sure the air flows even better. And, I have ordered an external fan that I will try to use to see if it helps keeping the system even a tad cooler.

$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +62.0°C  (high = +82.0°C, crit = +100.0°C)
Core 0:        +55.0°C  (high = +82.0°C, crit = +100.0°C)
Core 1:        +56.0°C  (high = +82.0°C, crit = +100.0°C)
Core 2:        +55.0°C  (high = +82.0°C, crit = +100.0°C)
Core 3:        +54.0°C  (high = +82.0°C, crit = +100.0°C)
Core 4:        +55.0°C  (high = +82.0°C, crit = +100.0°C)
Core 5:        +62.0°C  (high = +82.0°C, crit = +100.0°C)
Core 6:        +55.0°C  (high = +82.0°C, crit = +100.0°C)
Core 7:        +55.0°C  (high = +82.0°C, crit = +100.0°C)
Core 8:        +56.0°C  (high = +82.0°C, crit = +100.0°C)
Core 9:        +55.0°C  (high = +82.0°C, crit = +100.0°C)

pch_cometlake-virtual-0
Adapter: Virtual device
temp1:        +86.0°C  

nvme-pci-0700
Adapter: PCI adapter
Composite:    +52.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +52.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +47.9°C  (low  = -273.1°C, high = +65261.8°C)

BAT0-acpi-0
Adapter: ACPI interface
in0:          16.27 V  
curr1:         0.00 A  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +56.0°C  

nvme-pci-0600
Adapter: PCI adapter
Composite:    +55.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +55.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +47.9°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-4300
Adapter: PCI adapter
Composite:    +49.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +49.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +50.9°C  (low  = -273.1°C, high = +65261.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +57.0°C  

These temperatures appear to be perfectly OK. :+1:

1 Like

Hi again @mzuniga

I’d strongly recommend using a Ventoy USB. It might be easier to create the USB in Windows; following directions from the Ventoy site.

The beauty of a Ventoy USB, is that all that’s needed to boot an ISO file is to copy it to a folder on the Ventoy USB. When you boot the Ventoy USB, any ISOs are automatically listed in the Ventoy menu, and can be booted directly.

I recommend at least an 8GB USB; preferably 16GB or greater, to give you ample space to store several ISOs of your choice.

Copy the appropriate Samsung ISO to the Ventoy USB, and you should be able to boot that directly from the Ventoy menu as well.

I hope this helps. Cheers.

1 Like
pch_cometlake-virtual-0
temp1:        +86.0°C

Platform controller hub temps can be a little high but considering your processor cores are in the mid fifties, that temp looks excessive. Since you’re already in contact with Tuxedo’s support I’d definitely mention that. Other things to consider:

  • Are you running any ultra-low latency/high encoding rate audio defaults for pipewire/pulse? If so, bring them back to defaults.
  • Try powertop (maybe with powertop-auto-tune from the aur) to try to get those readings down.
  • Again, check bios settings for anything related to pci bus speed, intel chipset speed/power, cpu/ram overclocking/undervolting etc.
1 Like

This package appears to be abandoned.

This is more promising, I would check for Intel Turbo Boost Technology, usually is enabled by default. If there is an option to disable it in your firmware it’s worth to verify the effect on temperatures / system performance.

@soundofthunder

Thank you. Ventoy was a great recommendation! That is such an easy way to deal with ISO files. The Samsung one started without issues in the grub2 mode. Unfortunately, the update tool did not recognise any supported SSDs. I will check with Tuxedo support again to hear if they have any ideas.

@6x12 @Wollie

I will mention this high temperature to support as well. Thanks! And, I have not done any changes to the default audio settings for pipewire/pulse.

I went digging around in the BIOS, and found a setting for Intel Turbo Boost Technology that I have now disabled.


The system just did another of its unannounced reboots. When I turned it back on, after about 10 minutes, I once more ran sensors. The temperatures had increased a lot since last time I checked. pch_cometlake-virtual-0 read +95.0°C.

$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +66.0°C  (high = +82.0°C, crit = +100.0°C)
Core 0:        +60.0°C  (high = +82.0°C, crit = +100.0°C)
Core 1:        +64.0°C  (high = +82.0°C, crit = +100.0°C)
Core 2:        +61.0°C  (high = +82.0°C, crit = +100.0°C)
Core 3:        +62.0°C  (high = +82.0°C, crit = +100.0°C)
Core 4:        +61.0°C  (high = +82.0°C, crit = +100.0°C)
Core 5:        +66.0°C  (high = +82.0°C, crit = +100.0°C)
Core 6:        +64.0°C  (high = +82.0°C, crit = +100.0°C)
Core 7:        +63.0°C  (high = +82.0°C, crit = +100.0°C)
Core 8:        +61.0°C  (high = +82.0°C, crit = +100.0°C)
Core 9:        +62.0°C  (high = +82.0°C, crit = +100.0°C)

pch_cometlake-virtual-0
Adapter: Virtual device
temp1:        +95.0°C  

nvme-pci-0700
Adapter: PCI adapter
Composite:    +67.8°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +67.8°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +71.8°C  (low  = -273.1°C, high = +65261.8°C)

BAT0-acpi-0
Adapter: ACPI interface
in0:          16.27 V  
curr1:         0.00 A  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +70.0°C  

nvme-pci-4300
Adapter: PCI adapter
Composite:    +63.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +63.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +65.8°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-0600
Adapter: PCI adapter
Composite:    +69.8°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +69.8°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +61.9°C  (low  = -273.1°C, high = +65261.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +65.0°C  

Five minutes later I re-ran sensors. Then I got the following reading, that does not look good:

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +97.0°C  

Now, the system has been running for 40 minutes, and the temperatures are back at 50-60, except for pch_cometlake-virtual-0 which reads 85°C (despite having disabled “Intel Turbo Boost Technology”). When I search for “pch_cometlake-virtual-0” it looks like there are more having a problem with high temperatures.

I will hear what Tuxedo support say about these findings as well.


I have now created a cron job, to log the temperatures. This way I can check what the temperatures read before next shutdown.

*/5 * * * * date >> /home/qqq/log/sensors.txt && sensors >> /home/qqq/log/sensors.txt

Yes, the Intel homepage is dead but it’s still in the official repos. I mentioned that especially since I found this (slightly enthusiastic) reference to a fix: “Powertop is fantastic! From 82 to 58 degrees in just half a minute!”.

@mzuniga I’d dig deeper in those “Advanced chipset control” features, try disabling some or one-by-one, maybe in conjunction with installing a power-managing software. There are other power-managing and cpu frequency scaling packages that can handle those features in case you have to disable them in bios.

I used an older 3-drive Clevo gaming laptop for audio recording and I had issues with heat/fan noise in the past, at one stage removed the msata drive and the wifi card to get to grips with it. Got best results by removing tlp and installing auto-cpufreq.

1 Like

I appreciate your inputs, @6x12. Thank you.

Digging around I realised that my system was locked in a high performance mode. That explains why also I have had a lot of issues with annoying fan noise, and the high temperatures. I tried out the Tuxedo Control Center. Several features are missing on Manjaro, but I can alter the profile / power mode through that tool.

This was the previous active profile:

Now, I am trying out a predefined mode named “Cool and breezy”:

The notebook has been running, doing different tasks, for five hours, and the temperature now looks like this:

$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +44.0°C  (high = +82.0°C, crit = +100.0°C)
Core 0:        +42.0°C  (high = +82.0°C, crit = +100.0°C)
Core 1:        +43.0°C  (high = +82.0°C, crit = +100.0°C)
Core 2:        +42.0°C  (high = +82.0°C, crit = +100.0°C)
Core 3:        +43.0°C  (high = +82.0°C, crit = +100.0°C)
Core 4:        +43.0°C  (high = +82.0°C, crit = +100.0°C)
Core 5:        +43.0°C  (high = +82.0°C, crit = +100.0°C)
Core 6:        +42.0°C  (high = +82.0°C, crit = +100.0°C)
Core 7:        +43.0°C  (high = +82.0°C, crit = +100.0°C)
Core 8:        +43.0°C  (high = +82.0°C, crit = +100.0°C)
Core 9:        +42.0°C  (high = +82.0°C, crit = +100.0°C)

pch_cometlake-virtual-0
Adapter: Virtual device
temp1:        +65.0°C  

nvme-pci-4300
Adapter: PCI adapter
Composite:    +49.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +49.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +49.9°C  (low  = -273.1°C, high = +65261.8°C)

BAT0-acpi-0
Adapter: ACPI interface
in0:          16.27 V  
curr1:         0.00 A  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +55.0°C  

nvme-pci-0700
Adapter: PCI adapter
Composite:    +51.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +51.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +46.9°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-0600
Adapter: PCI adapter
Composite:    +55.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +55.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +46.9°C  (low  = -273.1°C, high = +65261.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +45.0°C  

I will test this profile for a few days, to see if the system still shuts down on its own. If it does not help I will keep checking out the BIOS options, and look at powertop.

3 Likes

Just wanted to leave an update. After I changed the power mode to “Cool and breezy”, the temperatures have stayed low. And, the system has been running for more than eight days straight without rebooting or any other issues (things are just a lot slower, and more silent, than what I am used to). So, this seems to point to overheating as the culprit in this issue.

Tuxedo support still asks me to upgrade the firmware of the main SSD, the Samsung 980 Pro, as the firmware I am running is said to be known for causing reboot issues. Unfortunately, the Samsung tool doesn’t recognise my drive, so I have not been able to upgrade. Maybe the Samsung tool gets confused when there is more than one drive present. I will try to disconnect the two extra SSDs and only leave the main one when I boot into the Samsung firmware tool. Hopefully that will help.

$ neofetch 
██████████████████  ████████   poq@tuxwarrior 
██████████████████  ████████   -------------- 
██████████████████  ████████   OS: Manjaro Linux x86_64 
██████████████████  ████████   Host: TUXEDO Book XUX7 Gen11 
████████            ████████   Kernel: 6.6.8-2-MANJARO 
████████  ████████  ████████   Uptime: 8 days, 9 hours, 57 mins 
████████  ████████  ████████   Packages: 1457 (pacman) 
████████  ████████  ████████   Shell: bash 5.2.21 
████████  ████████  ████████   Resolution: 3840x2160 
████████  ████████  ████████   WM: i3 
████████  ████████  ████████   Theme: Sweet-Dark-v40 [GTK2/3] 
████████  ████████  ████████   Icons: candy-icons [GTK2/3] 
████████  ████████  ████████   Terminal: urxvt 
████████  ████████  ████████   Terminal Font: NotoSansMono-Light 
                               CPU: Intel i9-10900K (20) @ 1.850GHz 
                               GPU: NVIDIA GeForce RTX 2080 SUPER Mobile / Max-Q 
                               Memory: 16949MiB / 128580MiB 
$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +49.0°C  (high = +82.0°C, crit = +100.0°C)
Core 0:        +47.0°C  (high = +82.0°C, crit = +100.0°C)
Core 1:        +49.0°C  (high = +82.0°C, crit = +100.0°C)
Core 2:        +46.0°C  (high = +82.0°C, crit = +100.0°C)
Core 3:        +47.0°C  (high = +82.0°C, crit = +100.0°C)
Core 4:        +47.0°C  (high = +82.0°C, crit = +100.0°C)
Core 5:        +47.0°C  (high = +82.0°C, crit = +100.0°C)
Core 6:        +46.0°C  (high = +82.0°C, crit = +100.0°C)
Core 7:        +47.0°C  (high = +82.0°C, crit = +100.0°C)
Core 8:        +48.0°C  (high = +82.0°C, crit = +100.0°C)
Core 9:        +47.0°C  (high = +82.0°C, crit = +100.0°C)

pch_cometlake-virtual-0
Adapter: Virtual device
temp1:        +69.0°C  

nvme-pci-4300
Adapter: PCI adapter
Composite:    +51.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +51.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +51.9°C  (low  = -273.1°C, high = +65261.8°C)

BAT0-acpi-0
Adapter: ACPI interface
in0:          16.16 V  
curr1:         0.00 A  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +59.0°C  

nvme-pci-0700
Adapter: PCI adapter
Composite:    +54.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +54.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +48.9°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-0600
Adapter: PCI adapter
Composite:    +58.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +58.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +48.9°C  (low  = -273.1°C, high = +65261.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +49.0°C  

Indeed, it was always the most likely.

A slower system to get used to, maybe, but you will get used to it over time. Slow is better than crashing; at least this allows a level of confidence in the machine you haven’t had for a while. Perhaps you can rename the profile to “Slow and Breezy”. :slight_smile:

Regarding the Samsung 980 Pro;

The firmware might go some way toward allowing you to regain some of that performance loss; if what Tuxedo Support tells you, is accurate.

It is also possible that only the range of drives specific to the firmware will be detected (a guess). Make sure you have the exact firmware for your drive. There is an ISO on the Samsung site listed under Samsung Storage Firmware – NVMe SSD-980 PRO Series Firmware – ISO 5B2QGXA7 | 27MB that appears to be the one. Is this the same as you downloaded previously?

Related:- I found this article at Toms’Hardware Samsung Issues Fix for Dying 980 Pro SSDs, which is disconcerting in itself.

However, it also states:

It should be noted that 980 Pro SSDs running the 4B2QGXA7 or 5B2QGXA7 firmware are not affected by this issue.

So, the 5B2QGXA7 previously linked seems to be the correct one, if it isn’t already applied.

Samsung also recommends that it be installed using Samsung Magician Software; only Windows, macOS and Android versions are mentioned. Here is the Installation Guide (for Windows).

Of course, these are not much use without Windows or macOS.

It might be possible to use the Samsung tool via a Windows PE boot disk; such as the Hiren’s BootCD PE (Preinstallation Environment). However, this is likely outside the scope of the Manjaro forum.

As overheating is now recognised at the culprit, it’s probably time to mark this thread as solved. Check the tick under whichever post you feel initially led you to this conclusion.

I’m glad we could help. Cheers.

1 Like

He he. A great idea! Yes, it is far better having a system that works and is stable, than one frequently shutting down.

That is the one I tried!

I definitively need to get that firmware updated. Thanks for the Hiren’s BootCD PE tip. I hope I will manage to upgrade, one way or another, before my SSD shuts down.

I will do so.

Thanks for amazing help, from you and other members of this forum.

Cheers!

2 Likes

This topic was automatically closed 3 hours after the last reply. New replies are no longer allowed.