analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or is not supported.
hardware limits: 800 MHz - 3.80 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 3.80 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 842 MHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
lspcu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 39 bits physical, 48 bits virtual
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 158
Model name: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Stepping: 9
CPU MHz: 900.046
CPU max MHz: 3800,0000
CPU min MHz: 800,0000
BogoMIPS: 5618.00
Virtualization: VT-x
L1d cache: 128 KiB
L1i cache: 128 KiB
L2 cache: 1 MiB
L3 cache: 6 MiB
NUMA node0 CPU(s): 0-7
Vulnerability L1tf: Mitigation; PTE Inversion; VMX vulnerable
Vulnerability Mds: Vulnerable; SMT vulnerable
Vulnerability Meltdown: Vulnerable
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1: Vulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers
Vulnerability Spectre v2: Vulnerable, IBPB: disabled, STIBP: disabled
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
Wow this is a complete game changer. I changed the governor to performance and now my machine is faster than yours (because mitigations are off I guess).
My clean build is now down to sth like 50 seconds instead of 12 minutes.
I don't get it: Why is a scheduler set as default that completely cripples the system?
Is it a driver bug? I tested this on the latest precision with a i9-9880H and there the performance is not so severely crippled with the default scheduler also being powersafe.
I have run the test, because I was curious myself. My results are very different from yours. Hardware-wise I exchanged the stock ram with some bigger-sized alternative. I have installed the latest `intel-ucode` version `20190918-1`.
sysbench 1.0.17 (using system LuaJIT 2.0.5)
Running the test with following options:
Number of threads: 1
Initializing random number generator from current time
Prime numbers limit: 10000
Initializing worker threads...
Threads started!
CPU speed:
events per second: 1216.36
General statistics:
total time: 10.0007s
total number of events: 12166
Latency (ms):
min: 0.76
avg: 0.82
max: 3.39
95th percentile: 0.97
sum: 9997.54
Threads fairness:
events (avg/stddev): 12166.0000/0.00
execution time (avg/stddev): 9.9975/0.00
sysbench 1.0.17 (using system LuaJIT 2.0.5)
Running the test with following options:
Number of threads: 1
Initializing random number generator from current time
Running memory speed test with the following options:
block size: 1KiB
total size: 102400MiB
operation: write
scope: global
Initializing worker threads...
Threads started!
Total operations: 57739501 (5773109.84 per second)
56386.23 MiB transferred (5637.80 MiB/sec)
General statistics:
total time: 10.0000s
total number of events: 57739501
Latency (ms):
min: 0.00
avg: 0.00
max: 2.53
95th percentile: 0.00
sum: 4868.59
Threads fairness:
events (avg/stddev): 57739501.0000/0.00
execution time (avg/stddev): 4.8686/0.00
sysbench 1.0.17 (using system LuaJIT 2.0.5)
Running the test with following options:
Number of threads: 1
Initializing random number generator from current time
Initializing worker threads...
Threads started!
General statistics:
total time: 10.0003s
total number of events: 18322
Latency (ms):
min: 0.49
avg: 0.55
max: 3.15
95th percentile: 0.65
sum: 9996.92
Threads fairness:
events (avg/stddev): 18322.0000/0.00
execution time (avg/stddev): 9.9969/0.00
sysbench 1.0.17 (using system LuaJIT 2.0.5)
Running the test with following options:
Number of threads: 1
Initializing random number generator from current time
Initializing worker threads...
Threads started!
General statistics:
total time: 0.1593s
total number of events: 1
Latency (ms):
min: 159.29
avg: 159.29
max: 159.29
95th percentile: 158.63
sum: 159.29
Threads fairness:
events (avg/stddev): 1.0000/0.00
execution time (avg/stddev): 0.1593/0.00
Could you post the output of… (pkg `cpupower` needs to be installed)
# cpupower frequency-info
my results are
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or is not supported.
hardware limits: 800 MHz - 3.80 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 3.80 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.76 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Specifically the cpufreq governor `performance` is not set automatically, but may give better results. I use the systemd service `cpupower.service` to set it after startup.
Also my `lscpu` output:
# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 39 bits physical, 48 bits virtual
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 158
Model name: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Stepping: 9
CPU MHz: 3546.318
CPU max MHz: 3800,0000
CPU min MHz: 800,0000
BogoMIPS: 5602.18
Virtualization: VT-x
L1d cache: 128 KiB
L1i cache: 128 KiB
L2 cache: 1 MiB
L3 cache: 6 MiB
NUMA node0 CPU(s): 0-7
Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cach
e flushes, SMT vulnerable
Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Meltdown: Mitigation; PTI
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled v
ia prctl and seccomp
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user
pointer sanitization
Vulnerability Spectre v2: Mitigation; Full generic retpoline, IBPB condit
ional, IBRS_FW, STIBP conditional, RSB filling
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtr
r pge mca cmov pat pse36 clflush dts acpi mmx f
xsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rd
tscp lm constant_tsc art arch_perfmon pebs bts
rep_good nopl xtopology nonstop_tsc cpuid aperf
mperf pni pclmulqdq dtes64 monitor ds_cpl vmx e
st tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_
1 sse4_2 x2apic movbe popcnt tsc_deadline_timer
aes xsave avx f16c rdrand lahf_lm abm 3dnowpre
fetch cpuid_fault epb invpcid_single pti ssbd i
brs ibpb stibp tpr_shadow vnmi flexpriority ept
vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep
bmi2 erms invpcid mpx rdseed adx smap clflusho
pt intel_pt xsaveopt xsavec xgetbv1 xsaves dthe
rm ida arat pln pts hwp hwp_notify hwp_act_wind
ow hwp_epp md_clear flush_l1d
I did a sysbench benchmark. You can easily install it from pacman:
pacman -Syu sysbench
The benchmark takes like 1 minute and the command I ran is:
sysbench cpu run > benchmark.txt && sysbench memory run >> benchmark.txt && sysbench threads run >> benchmark.txt && sysbench mutex run >> benchmark.txt
I'd like to compare it with other users before reporting this on dell. This is the output on my machine:
sysbench 1.0.17 (using system LuaJIT 2.0.5)
Running the test with following options:
Number of threads: 1
Initializing random number generator from current time
Prime numbers limit: 10000
Initializing worker threads...
Threads started!
CPU speed:
events per second: 275.04
General statistics:
total time: 10.0002s
total number of events: 2752
Latency (ms):
min: 3.62
avg: 3.63
max: 4.52
95th percentile: 3.62
sum: 9997.95
Threads fairness:
events (avg/stddev): 2752.0000/0.00
execution time (avg/stddev): 9.9979/0.00
sysbench 1.0.17 (using system LuaJIT 2.0.5)
Running the test with following options:
Number of threads: 1
Initializing random number generator from current time
Running memory speed test with the following options:
block size: 1KiB
total size: 102400MiB
operation: write
scope: global
Initializing worker threads...
Threads started!
Total operations: 13911028 (1390288.31 per second)
13584.99 MiB transferred (1357.70 MiB/sec)
General statistics:
total time: 10.0001s
total number of events: 13911028
Latency (ms):
min: 0.00
avg: 0.00
max: 0.04
95th percentile: 0.00
sum: 4945.02
Threads fairness:
events (avg/stddev): 13911028.0000/0.00
execution time (avg/stddev): 4.9450/0.00
sysbench 1.0.17 (using system LuaJIT 2.0.5)
Running the test with following options:
Number of threads: 1
Initializing random number generator from current time
Initializing worker threads...
Threads started!
General statistics:
total time: 10.0006s
total number of events: 10394
Latency (ms):
min: 0.95
avg: 0.96
max: 1.05
95th percentile: 0.97
sum: 9994.66
Threads fairness:
events (avg/stddev): 10394.0000/0.00
execution time (avg/stddev): 9.9947/0.00
sysbench 1.0.17 (using system LuaJIT 2.0.5)
Running the test with following options:
Number of threads: 1
Initializing random number generator from current time
Initializing worker threads...
Threads started!
General statistics:
total time: 0.6361s
total number of events: 1
Latency (ms):
min: 635.93
avg: 635.93
max: 635.93
95th percentile: 634.66
sum: 635.93
Threads fairness:
events (avg/stddev): 1.0000/0.00
execution time (avg/stddev): 0.6359/0.00
Can someone please run the same command and share the output?
]]>Yes, the problem may come from the hardware. I am trying to see if I could improve the situation only playing with software, in order to avoid the hassle of calling the warranty service and risking to have my laptop replaced by one that is performs even worse or has coil whine (silly?). And because the laptop is still under warrantee, I cannot (I think) open it to add thermal pads or tape inside, but I will do it as soon as the warrantee ends if the problem is not solved at this point.
Edit: typo
]]>I am using an XPS 13 9560 with Arch and I have overheating problems, so I tried to play with thermald.
(When I stress the CPU it goes over 90 degrees and I have to kill processes in order to get a 'normal' temperature.)
However thermald's documentation is not complete and I did not figure out satisfying parameters so far.
To those who obtained satisfying thermald settings (with the XPS 13), would you mind sharing your config files (thermal-conf.xml and thermal-cpu-cdev-order.xml, in /etc/thermald/)?
I would also be interested to know the configuration files of those who are using the pre-installed ubuntu setup (if any on this forum ), as it might be optimized for the hardware.
What I found so far includes:
* https://smackerelofopinion.blogspot.com … -file.html
* https://bbs.archlinux.org/viewtopic.php?id=236887
* https://github.com/intel/thermal_daemon/issues/42
(but it is not satisfying / not XPS13 specific)
Currently I am not even sure what I have, but I do know that sometimes my laptop screen goes off, and won't come back on again. I have to ssh to it and reboot to gain access to the screen again so I definitely need something that works.
]]>From what I can tell, the following line is presented every time display fails to turn on:
[drm:intel_dp_start_link_train [i915]] *ERROR* [CONNECTOR:71:eDP-1] Link Training failed at link rate = 540000, lane count = 4
Using the power button to suspend/wake can bring the display online. (On GDM and after logging in)
GNOME display settings then also claims the refresh rate is at 120Hz
Does anybody know if this is issue known/reported upstream somewhere? I'd like to report it to thee intel-gfx tracker but I'm not sure I understand what's wrong enough for a meaningful bug report.
]]>I had a boot option i915.enable_psr=1 which I had added long ago for some problem I don't remember. Removing that option fixed the blank screen problem.
For anyone else out there where this doesn't work...
I didn't have the i915.enable_psr option specified on my boot commandline. Nonetheless, I had to add it and explicitly set i915.enable_psr=0. When I had a look in the module info the default is "-1" which is the "chipset default". It's entirely possible that I have set enable_psr=1 at some point in the past and I wonder if it persisted in the hardware in some manner? (Otherwise, it's possible different hardware has ended up with different defaults. EDIT - it's also possible that you all set the value to zero rather than deleting the option so my situation hasn't presented it self.)
In any event, thanks bulletmark, you saved me some time looking...
]]>Was hoping to get some assistance here as I am perplexed on how to go about resolving it.
XPS15 9570 w TB16
4.18.9-arch1-1-ARCH
Once in a while, when plugging a USB device into the dock the xHCI host controller dies. Seems to happen when there is heavier activity on the USBs connected to the dock IE: USB audio, USB serial adapter, Raspberry PI connected. I've spent hours googling this issue and have found a bug report on the redhat forums which describes my issue exactly https://bugzilla.redhat.com/show_bug.cgi?id=1600126 on which I have also posted. Monitors (DP & HDMI on dock) continue to work despite all the USBs dying. Power cycling the dock does not always fix it and sometimes results in the monitors ceasing to work while the USBs recover. The only reliable fix is to unplug TB from PC and power and also reboot the PC.
Has anyone experienced this issue here before? Any suggestions on further troubleshooting? BIOS is up to date according to fwupdmgr.
dmesg output:
[10727.087651] xhci_hcd 0000:0a:00.0: xHCI host not responding to stop endpoint command.
[10727.202880] xhci_hcd 0000:0a:00.0: Host halt failed, -110
[10727.202881] xhci_hcd 0000:0a:00.0: xHCI host controller not responding, assume dead
[10727.202889] usb 3-1.1: cannot submit urb (err = -108)
[10727.202961] r8152 4-1.2:1.0 ens4u1u2: Tx status -108
[10727.202966] r8152 4-1.2:1.0 ens4u1u2: Tx status -108
[10727.202972] r8152 4-1.2:1.0 ens4u1u2: Tx status -108
[10727.202978] r8152 4-1.2:1.0 ens4u1u2: Tx status -108
[10727.203009] xhci_hcd 0000:0a:00.0: HC died; cleaning up
[10727.203016] xhci_hcd 0000:0a:00.0: Timeout waiting for reset device command
[10727.203041] ftdi_sio ttyUSB0: failed to get modem status: -110
[10727.203082] usb 3-1.1: cannot submit urb 0, error -19: no device
[10727.203459] usb 3-1: USB disconnect, device number 2
[10727.203461] usb 3-1.1: USB disconnect, device number 16
[10727.203496] usb 4-1: USB disconnect, device number 2
[10727.203497] usb 4-1.2: USB disconnect, device number 3
[10727.204063] usb 3-1.3: USB disconnect, device number 3
[10727.204165] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[10727.204178] ftdi_sio 3-1.3:1.0: device disconnected
[10727.204295] usb 3-1.5: USB disconnect, device number 5
[10727.204746] usb 3-1.7: USB disconnect, device number 6
[10727.614377] usb 3-1.7.3: device not accepting address 17, error -108
[10727.614465] usb 3-1.7-port3: couldn't allocate usb_device
[10727.614487] usb 3-1.7.4: USB disconnect, device number 8
I had a boot option i915.enable_psr=1 which I had added long ago for some problem I don't remember. Removing that option fixed the blank screen problem.
Thank you so much for the hint. Had the same problem.
]]>Yep this fixed it for me too! To clarify, how did you end up figuring out it was this parameter? Just your testing with the screen suspending and the fact everything was still active in the background (despite not displaying)?
No great insight. Since I knew it was just a screen blanking problem and since the problem was not widely reported across the forums/reddit I figured it was quite specific to my notebook type or configuration so I looked at my boot settings and that one seemed relevant.
]]>gnunn wrote:Anyone have an issue with the laptop screen not displaying on X or Wayland after upgrading to kernel 4.18.8?
I have a Dell XPS 13 9343 and after the 4.18.8 update it would boot to a black screen. I could press the suspend button twice and it would display normally. I noticed I could actually start apps from the keyboard etc while the screen was blank and they would appear after the suspend confirming it was only a screen blanking issue.
I had a boot option i915.enable_psr=1 which I had added long ago for some problem I don't remember. Removing that option fixed the blank screen problem.
Yep this fixed it for me too! To clarify, how did you end up figuring out it was this parameter? Just your testing with the screen suspending and the fact everything was still active in the background (despite not displaying)?
]]>gnunn wrote:Anyone have an issue with the laptop screen not displaying on X or Wayland after upgrading to kernel 4.18.8?
I have a Dell XPS 13 9343 and after the 4.18.8 update it would boot to a black screen. I could press the suspend button twice and it would display normally. I noticed I could actually start apps from the keyboard etc while the screen was blank and they would appear after the suspend confirming it was only a screen blanking issue.
I had a boot option i915.enable_psr=1 which I had added long ago for some problem I don't remember. Removing that option fixed the blank screen problem.
Thank you so much, I had the same parameter and removing it fixed the issue.
]]>