[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3

2021-12-27 Thread Rick T 
I'm not sure what's needed to bisect the kernel?  What would I need to
do?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221

Title:
  CPU frequency stuck at minimum value..again Ubuntu 20.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3

2021-12-09 Thread Rick T 
The speed is limited on every boot now...I also notice my bios time
being reset to 2013...when unplugged from the wall (I'm going to open it
up, the cmos battery may have died.)

rt@sys76:~$ sudo grep . /sys/class/powercap/intel-rapl/intel-rapl\:0/*
[sudo] password for rt: 
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_max_power_uw:4700
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_name:long_term
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_power_limit_uw:4700
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_time_window_us:27983872
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_max_power_uw:0
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_name:short_term
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_power_limit_uw:5875
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_time_window_us:2440
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/device: Is a directory
/sys/class/powercap/intel-rapl/intel-rapl:0/enabled:0
/sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj:5242172615
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:0: Is a directory
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:1: Is a directory
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:2: Is a directory
/sys/class/powercap/intel-rapl/intel-rapl:0/max_energy_range_uj:262143328850
/sys/class/powercap/intel-rapl/intel-rapl:0/name:package-0
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/power: Is a directory
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/subsystem: Is a directory
rt@sys76:~$ 




rt@sys76:~$ 
rt@sys76:~$ 
rt@sys76:~$ 
rt@sys76:~$ 
rt@sys76:~$ 
rt@sys76:~$ sudo rdmsr -c -p0 0x64F

rdmsr: CPU 0 cannot read MSR 0x064f

rt@sys76:~$ sudo strace rdmsr 0x64F

execve("/usr/sbin/rdmsr", ["rdmsr", "0x64F"], 0x7ffe9486b188 /* 16 vars */) = 0
brk(NULL)   = 0x5633b869a000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffe398f8370) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=79034, ...}) = 0
mmap(NULL, 79034, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc1f8b19000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"..., 
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 
32, 848) = 32
pread64(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
 68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fc1f8b17000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 
32, 848) = 32
pread64(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
 68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fc1f8925000
mprotect(0x7fc1f894a000, 1847296, PROT_NONE) = 0
mmap(0x7fc1f894a000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7fc1f894a000
mmap(0x7fc1f8ac2000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x19d000) = 0x7fc1f8ac2000
mmap(0x7fc1f8b0d000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7fc1f8b0d000
mmap(0x7fc1f8b13000, 13528, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fc1f8b13000
close(3)= 0
arch_prctl(ARCH_SET_FS, 0x7fc1f8b18580) = 0
mprotect(0x7fc1f8b0d000, 12288, PROT_READ) = 0
mprotect(0x5633b7d85000, 4096, PROT_READ) = 0
mprotect(0x7fc1f8b5a000, 4096, PROT_READ) = 0
munmap(0x7fc1f8b19000, 79034)   = 0
openat(AT_FDCWD, "/dev/cpu/0/msr", O_RDONLY) = 3
pread64(3, 0x7ffe398f8288, 8, 1615) = -1 EIO (Input/output error)
write(2, "rdmsr: CPU 0 cannot read MSR 0x0"..., 40rdmsr: CPU 0 cannot read MSR 
0x064f
) = 40
exit_group(4)   = ?
+++ exited with 4 +++
rt@sys76:~$

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221

Title:
  CPU frequency stuck at minimum value..again Ubuntu 20.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3

2021-12-05 Thread Rick T 
@koba issue still occurs.


@Doug

rt@sys76:~$ sudo rdmsr -c -p0 0x1b2
0x3



rt@sys76:~$ sudo strace rdmsr 0x1b2


execve("/usr/sbin/rdmsr", ["rdmsr", "0x1b2"], 0x7fff4f90a298 /* 17 vars */) = 0
brk(NULL)   = 0x56510cc31000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffe42320b10) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=253505, ...}) = 0
mmap(NULL, 253505, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fec4390
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"..., 
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 
32, 848) = 32
pread64(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
 68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fec438fe000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 
32, 848) = 32
pread64(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
 68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fec4370c000
mprotect(0x7fec43731000, 1847296, PROT_NONE) = 0
mmap(0x7fec43731000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7fec43731000
mmap(0x7fec438a9000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x19d000) = 0x7fec438a9000
mmap(0x7fec438f4000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7fec438f4000
mmap(0x7fec438fa000, 13528, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fec438fa000
close(3)= 0
arch_prctl(ARCH_SET_FS, 0x7fec438ff580) = 0
mprotect(0x7fec438f4000, 12288, PROT_READ) = 0
mprotect(0x56510cbb5000, 4096, PROT_READ) = 0
mprotect(0x7fec4396b000, 4096, PROT_READ) = 0
munmap(0x7fec4390, 253505)  = 0
openat(AT_FDCWD, "/dev/cpu/0/msr", O_RDONLY) = 3
pread64(3, "\3\0\0\0\0\0\0\0", 8, 434)  = 8
close(3)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(0x88, 0), ...}) = 0
brk(NULL)   = 0x56510cc31000
brk(0x56510cc52000) = 0x56510cc52000
write(1, "3\n", 23
)  = 2
exit_group(0)   = ?
+++ exited with 0 +++
rt@sys76:~$

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221

Title:
  CPU frequency stuck at minimum value..again Ubuntu 20.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3

2021-12-05 Thread Rick T 
ok

rt@sys76:~$ sudo rdmsr -c -p0 0x19c
0x8839080c
rt@sys76:~$ sudo rdmsr -c -p0 0x1aa
0x40
rt@sys76:~$ sudo rdmsr -c -p0 0x1b1
0x8839080c
rt@sys76:~$ sudo rdmsr -c -p0 0x16f
rdmsr: CPU 0 cannot read MSR 0x016f
rt@sys76:~$ sudo rdmsr -c -p0 0x1fc
0x4005d


rt@sys76:~$ sudo strace rdmsr 0x19C
execve("/usr/sbin/rdmsr", ["rdmsr", "0x19C"], 0x7ffdaa2d1488 /* 17 vars */) = 0
brk(NULL)   = 0x55b45cb84000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffc77c46f80) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=253505, ...}) = 0
mmap(NULL, 253505, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f35e41bf000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"..., 
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 
32, 848) = 32
pread64(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
 68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f35e41bd000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 
32, 848) = 32
pread64(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
 68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f35e3fcb000
mprotect(0x7f35e3ff, 1847296, PROT_NONE) = 0
mmap(0x7f35e3ff, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7f35e3ff
mmap(0x7f35e4168000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x19d000) = 0x7f35e4168000
mmap(0x7f35e41b3000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f35e41b3000
mmap(0x7f35e41b9000, 13528, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f35e41b9000
close(3)= 0
arch_prctl(ARCH_SET_FS, 0x7f35e41be580) = 0
mprotect(0x7f35e41b3000, 12288, PROT_READ) = 0
mprotect(0x55b45c8b1000, 4096, PROT_READ) = 0
mprotect(0x7f35e422a000, 4096, PROT_READ) = 0
munmap(0x7f35e41bf000, 253505)  = 0
openat(AT_FDCWD, "/dev/cpu/0/msr", O_RDONLY) = 3
pread64(3, "\f\109\210\0\0\0\0", 8, 412) = 8
close(3)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(0x88, 0x3), ...}) = 0
brk(NULL)   = 0x55b45cb84000
brk(0x55b45cba5000) = 0x55b45cba5000
write(1, "8839080c\n", 98839080c
)   = 9
exit_group(0)   = ?
+++ exited with 0 +++


rt@sys76:~$ sudo strace rdmsr 0x1aa
execve("/usr/sbin/rdmsr", ["rdmsr", "0x1aa"], 0x7fffde650548 /* 17 vars */) = 0
brk(NULL)   = 0x555d67d9f000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd9bfd56d0) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=253505, ...}) = 0
mmap(NULL, 253505, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fd5f63ff000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"..., 
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 
32, 848) = 32
pread64(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
 68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fd5f63fd000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 
32, 848) = 32
pread64(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
 68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fd5f620b000
mprotect(0x7fd5f623, 1847296, PROT_NONE) = 0
mmap(0x7fd5f623, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7fd5f623
mmap(0x7fd5f63a8000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x19d000) = 0x7fd5f63a8000
mmap(0x7fd5f63f3000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0

[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3

2021-12-05 Thread Rick T 
Ok

One terminal was running 
rt@sys76:~$ taskset -c 2 yes > /dev/null


2nd terminal data:

rt@sys76:~$ grep . /sys/devices/system/cpu/intel_pstate/*

/sys/devices/system/cpu/intel_pstate/max_perf_pct:100
/sys/devices/system/cpu/intel_pstate/min_perf_pct:50
/sys/devices/system/cpu/intel_pstate/no_turbo:0
/sys/devices/system/cpu/intel_pstate/num_pstates:27
/sys/devices/system/cpu/intel_pstate/status:active
/sys/devices/system/cpu/intel_pstate/turbo_pct:38
rt@sys76:~$ 
rt@sys76:~$ 
rt@sys76:~$ 
rt@sys76:~$ 
rt@sys76:~$ 
rt@sys76:~$ 
rt@sys76:~$ grep . /sys/devices/system/cpu/cpu2/cpufreq/*

/sys/devices/system/cpu/cpu2/cpufreq/affected_cpus:2
/sys/devices/system/cpu/cpu2/cpufreq/cpuinfo_max_freq:340
/sys/devices/system/cpu/cpu2/cpufreq/cpuinfo_min_freq:80
/sys/devices/system/cpu/cpu2/cpufreq/cpuinfo_transition_latency:0
/sys/devices/system/cpu/cpu2/cpufreq/related_cpus:2
/sys/devices/system/cpu/cpu2/cpufreq/scaling_available_governors:performance 
powersave
/sys/devices/system/cpu/cpu2/cpufreq/scaling_cur_freq:798228
/sys/devices/system/cpu/cpu2/cpufreq/scaling_driver:intel_pstate
/sys/devices/system/cpu/cpu2/cpufreq/scaling_governor:powersave
/sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq:340
/sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq:80
/sys/devices/system/cpu/cpu2/cpufreq/scaling_setspeed:
rt@sys76:~$ 

rt@sys76:~$ sudo rdmsr --bitfield 15:8 -u -a 0x198
[sudo] password for rt: 
8
8
8
8
8
8
8
8
rt@sys76:~$ 
rt@sys76:~$ 
rt@sys76:~$ 
rt@sys76:~$ sudo rdmsr --bitfield 15:8 -u -a 0x199
17
17
34
17
17
34
17
17
rt@sys76:~$

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221

Title:
  CPU frequency stuck at minimum value..again Ubuntu 20.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3

2021-12-04 Thread Rick T 
Now after another reboot the speed is stuck at 800mhz again and doesn't
move


rt@sys76:~$ uname -r
5.15.5-76051505-generic
rt@sys76:~$ grep CONFIG_CPU_FREQ_DEFAULT /boot/config-5.15.5-76051505-generic
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y
rt@sys76:~$ 



rt@sys76:~$ sudo turbostat --Summary --quiet --show 
Busy%,Bzy_MHz,IRQ,PkgWatt,PkgTmp,RAMWatt,GFXWatt,CorWatt --interval 10
[sudo] password for rt: 
Busy%   Bzy_MHz IRQ PkgTmp  PkgWatt CorWatt GFXWatt
2.42800 555043  1.590.050.02
15.37   800 17228   44  2.990.420.17
19.79   800 25124   44  3.500.510.15
31.52   800 42876   46  5.060.880.44
9.73800 14967   46  2.610.250.15
3.60800 735846  1.660.070.04
4.63800 852946  1.870.100.04
3.29800 724346  1.680.070.03
7.49800 12913   47  2.290.190.07



rt@sys76:~$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpuf...@vger.kernel.org, please.
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: 4294.55 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
  The governor "performance" may decide which speed to use
  within this range.
  current CPU frequency is 798 MHz.
analyzing CPU 1:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 4294.55 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
  The governor "performance" may decide which speed to use
  within this range.
  current CPU frequency is 798 MHz.
analyzing CPU 2:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 4294.55 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
  The governor "performance" may decide which speed to use
  within this range.
  current CPU frequency is 798 MHz.
analyzing CPU 3:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 4294.55 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
  The governor "performance" may decide which speed to use
  within this range.
  current CPU frequency is 798 MHz.
analyzing CPU 4:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 4
  CPUs which need to have their frequency coordinated by software: 4
  maximum transition latency: 4294.55 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
  The governor "performance" may decide which speed to use
  within this range.
  current CPU frequency is 798 MHz.
analyzing CPU 5:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 5
  CPUs which need to have their frequency coordinated by software: 5
  maximum transition latency: 4294.55 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
  The governor "performance" may decide which speed to use
  within this range.
  current CPU frequency is 799 MHz.
analyzing CPU 6:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 6
  CPUs which need to have their frequency coordinated by software: 6
  maximum transition latency: 4294.55 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
  The governor "performance" may decide which speed to use
  within this range.
  current CPU frequency is 798 MHz.
analyzing CPU 7:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 7
  CPUs which need to have their frequency coordinated by software: 7
  maximum transition latency: 4

[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3

2021-12-03 Thread Rick T 
Yes I can get it to boot into active mode thanks to Doug, but after
several minutes the cpu drops to 798-800mhz and won't increase no matter
if I try and change it.  I did notice that the scaling_governor always
boots to powersave mode.  When I change it to performance after several
minutes the cpu drops to 798-800mhz again.

I did find a similar problem "Linux kernel 5.8 defaults to passive mode
for intel_pstate driver for cpu before skylake"  but it always boots to
the powersave governor and changing it doesn't fix the issue.

https://www.reddit.com/r/linux/comments/ihdozd/linux_kernel_58_defaults_to_passive_mode_for/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221

Title:
  CPU frequency stuck at minimum value..again Ubuntu 20.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3

2021-12-02 Thread Rick T 
Here's a list  I can't remember the last time it worked, if you do a
google search on "ubuntu cpu lowest freq"  seems to be a very common
problem but none of the fixes work for me.


I can't change the speed of my CPU's in my bios (a system76 linux machine).  
What do you want me to check in the bios?

Here's the kernel versions


rt@sys76:~$ uname --all
Linux sys76 5.15.5-76051505-generic 
#202111250933~1638201579~20.04~09f1aa7~dev-Ubuntu SMP Tue Nov 30 x86_64 x86_64 
x86_64 GNU/Linux
rt@sys76:~$ 



rt@sys76:~$ dpkg --list | grep linux-image

rc  linux-image-4.10.0-27-generic   
4.10.0-27.30~16.04.2  amd64Linux 
kernel image for version 4.10.0 on 64 bit x86 SMP
rc  linux-image-4.10.0-28-generic   
4.10.0-28.32~16.04.2  amd64Linux 
kernel image for version 4.10.0 on 64 bit x86 SMP
rc  linux-image-4.10.0-30-generic   
4.10.0-30.34~16.04.1  amd64Linux 
kernel image for version 4.10.0 on 64 bit x86 SMP
rc  linux-image-4.10.0-32-generic   
4.10.0-32.36~16.04.1  amd64Linux 
kernel image for version 4.10.0 on 64 bit x86 SMP
rc  linux-image-4.10.0-33-generic   
4.10.0-33.37~16.04.1  amd64Linux 
kernel image for version 4.10.0 on 64 bit x86 SMP
rc  linux-image-4.10.0-42-generic   
4.10.0-42.46~16.04.1  amd64Linux 
kernel image for version 4.10.0 on 64 bit x86 SMP
rc  linux-image-4.13.0-26-generic   
4.13.0-26.29~16.04.2  amd64Linux 
kernel image for version 4.13.0 on 64 bit x86 SMP
rc  linux-image-4.15.0-101-generic  4.15.0-101.102  
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-106-generic  4.15.0-106.107  
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-108-generic  4.15.0-108.109  
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-109-generic  4.15.0-109.110  
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-111-generic  4.15.0-111.112  
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-112-generic  4.15.0-112.113  
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-115-generic  4.15.0-115.116  
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-117-generic  4.15.0-117.118  
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-118-generic  4.15.0-118.119  
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-20-generic   4.15.0-20.21
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-22-generic   4.15.0-22.24
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-23-generic   4.15.0-23.25
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-24-generic   4.15.0-24.26
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-29-generic   4.15.0-29.31
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-30-generic   4.15.0-30.32
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-32-generic   4.15.0-32.35
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-33-generic   4.15.0-33.36
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-36-generic   4.15.0-36.39
  amd64Signed kernel image 
generic
rc  linux-image-4.15.0-38-generic   4.15.0-38.41
  amd6

[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3

2021-12-01 Thread Rick T 
ok...

rt@sys76:~$ sudo cpupower -c all frequency-info

[sudo] password for rt: 
analyzing CPU 0:
  driver: intel_cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 20.0 us
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: conservative ondemand userspace powersave 
performance schedutil
  current policy: frequency should be within 1.70 GHz and 3.40 GHz.
  The governor "ondemand" may decide which speed to use
  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 798 MHz (asserted by call to kernel)
  boost state support:
Supported: yes
Active: yes
analyzing CPU 1:
  driver: intel_cpufreq
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 20.0 us
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: conservative ondemand userspace powersave 
performance schedutil
  current policy: frequency should be within 1.70 GHz and 3.40 GHz.
  The governor "ondemand" may decide which speed to use
  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 798 MHz (asserted by call to kernel)
  boost state support:
Supported: yes
Active: yes
analyzing CPU 2:
  driver: intel_cpufreq
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 20.0 us
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: conservative ondemand userspace powersave 
performance schedutil
  current policy: frequency should be within 1.70 GHz and 3.40 GHz.
  The governor "ondemand" may decide which speed to use
  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 798 MHz (asserted by call to kernel)
  boost state support:
Supported: yes
Active: yes
analyzing CPU 3:
  driver: intel_cpufreq
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 20.0 us
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: conservative ondemand userspace powersave 
performance schedutil
  current policy: frequency should be within 1.70 GHz and 3.40 GHz.
  The governor "ondemand" may decide which speed to use
  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 798 MHz (asserted by call to kernel)
  boost state support:
Supported: yes
Active: yes
analyzing CPU 4:
  driver: intel_cpufreq
  CPUs which run at the same hardware frequency: 4
  CPUs which need to have their frequency coordinated by software: 4
  maximum transition latency: 20.0 us
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: conservative ondemand userspace powersave 
performance schedutil
  current policy: frequency should be within 1.70 GHz and 3.40 GHz.
  The governor "ondemand" may decide which speed to use
  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 798 MHz (asserted by call to kernel)
  boost state support:
Supported: yes
Active: yes
analyzing CPU 5:
  driver: intel_cpufreq
  CPUs which run at the same hardware frequency: 5
  CPUs which need to have their frequency coordinated by software: 5
  maximum transition latency: 20.0 us
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: conservative ondemand userspace powersave 
performance schedutil
  current policy: frequency should be within 1.70 GHz and 3.40 GHz.
  The governor "ondemand" may decide which speed to use
  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 798 MHz (asserted by call to kernel)
  boost state support:
Supported: yes
Active: yes
analyzing CPU 6:
  driver: intel_cpufreq
  CPUs which run at the same hardware frequency: 6
  CPUs which need to have their frequency coordinated by software: 6
  maximum transition latency: 20.0 us
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: conservative ondemand userspace powersave 
performance schedutil
  current policy: frequency should be within 1.70 GHz and 3.40 GHz.
  The governor "ondemand" may decide which speed to use
  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 798 MHz (asserted by call to kernel)
  boost state support:
Supported: yes
Active: yes
analyzing CPU 7:
  driver: intel_cpufreq
  CPUs which run at the same hardware frequency: 7
  CPUs which need to have their frequency coordinated by software: 7
  ma

[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3

2021-12-01 Thread Rick T 
rt@sys76:~$ sudo systemctl status thermald.service
● thermald.service - Thermal Daemon Service
 Loaded: loaded (/lib/systemd/system/thermald.service; enabled; v>
 Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago
Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enabl>
   Main PID: 1319 (code=exited, status=0/SUCCESS)

Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:s>
Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4
Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for>
Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for>
Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for>
Dec 01 09:39:24 sys76 thermald[1319]: Terminating ...
Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service...
Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request ..
Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded.
Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service.
lines 1-16/16 (END)...skipping...
● thermald.service - Thermal Daemon Service
 Loaded: loaded (/lib/systemd/system/thermald.service; enabled; ven>
 Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago
Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable >
   Main PID: 1319 (code=exited, status=0/SUCCESS)

Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:ste>
Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4
Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for r>
Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for r>
Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for r>
Dec 01 09:39:24 sys76 thermald[1319]: Terminating ...
Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service...
Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request ..
Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded.
Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service.
~
~
~
~
~
~
~
~
~
lines 1-16/16 (END)...skipping...
● thermald.service - Thermal Daemon Service
 Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor pre>
 Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago
Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable --adapt>
   Main PID: 1319 (code=exited, status=0/SUCCESS)

Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:stepping 0>
Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4
Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading >
Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading >
Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading >
Dec 01 09:39:24 sys76 thermald[1319]: Terminating ...
Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service...
Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request ..
Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded.
Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service.
~
~
~
~
~
~
~
~
~
~
lines 1-16/16 (END)...skipping...
● thermald.service - Thermal Daemon Service
 Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor 
preset>
 Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago
Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable 
--adaptive>
   Main PID: 1319 (code=exited, status=0/SUCCESS)

Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:stepping 
0x6:>
Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4
Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading 
raw>
Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading 
raw>
Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading 
raw>
Dec 01 09:39:24 sys76 thermald[1319]: Terminating ...
Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service...
Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request ..
Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded.
Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service.
~
~
~
~
~
~
~
~
~
~
~
lines 1-16/16 (END)...skipping...
● thermald.service - Thermal Daemon Service
● thermald.service - Thermal Daemon Service
● thermald.service - Thermal Daemon Service
● thermald.service - Thermal Daemon Service
● thermald.service - Thermal Daemon Service
● thermald.service - Thermal Daemon Service
● thermald.service - Thermal Daemon Service
 Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago
Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable 
--adaptive (code=exited, status=0/>
   Main PID: 1319 (code=exited, status=0/SUCCESS)

Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:mod

[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3

2021-09-27 Thread Rick T 
I'm not sure if this is the right package

** Package changed: ubuntu => thermald (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221

Title:
  CPU frequency stuck at minimum value..again Ubuntu 20.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945221] [NEW] CPU frequency stuck at minimum value..again Ubuntu 20.04.3

2021-09-27 Thread Rick T 
Public bug reported:


I would really like to find out why my cpu's keep reverting back to a cpu 
powersave mode after I get a kernel update then reboot.

I cleaned my laptops vent but this seems to happen whenever a new kernel
is updated and installed.

https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts-significant-
throttling-of-intel-i7-processor?noredirect=1#comment2345549_1366090


Description:Ubuntu 20.04.3 LTS
Release:20.04


Computer
Summary
Computer
Processor   Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Memory  16315MB (4407MB used)
Machine TypeLaptop
Operating SystemUbuntu 20.04.3 LTS
User Name   rt (rt)
Date/Time   Mon 30 Aug 2021 02:33:09 PM EDT
Display
Resolution  1920x1080 pixels
OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2)
X11 Vendor  The X.Org Foundation
Audio Devices
Audio Adapter   HDA-Intel - HDA Intel HDMI
Audio Adapter   HDA-Intel - HDA Intel PCH
Audio Adapter   USB-Audio - USB Audio Device
Input Devices
Power Button
Sleep Button
Lid Switch  
Power Button
AT Translated Set 2 keyboard
USB Audio Device
ETPS/2 Elantech Touchpad
Logitech Anywhere MX
Video Bus   
HDA Intel PCH Mic   
HDA Intel PCH Front Headphone   
HDA Intel HDMI HDMI/DP,pcm:3
HDA Intel HDMI HDMI/DP,pcm:7
HDA Intel HDMI HDMI/DP,pcm:8
HDA Intel HDMI HDMI/DP,pcm:9
HDA Intel HDMI HDMI/DP,pcm:10   
Printers (CUPS)
OfficeJet_Pro_6978  Default
SCSI Disks
TSSTcorp CDDVDW SN-208DB
ATA INTEL SSDMCEAC12
ATA ST1000LM014-1EJ1
Operating System
Version
Kernel  Linux 5.4.0-81-generic (x86_64)
Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021
C Library   GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31
DistributionUbuntu 20.04.3 LTS
Current Session
Computer Name   sys76
User Name   rt (rt)
Languageen_US.UTF-8 ()
Home Directory  /home/rt
Misc
Uptime  20 minutes
Load Average0.83, 1.37, 1.62
Available entropy in /dev/random3649 bits (healthy)


rt@sys76:~$ dpkg -l *freq* | grep ii
rt@sys76:~$ 


rt@sys76:~$ sudo turbostat --Summary --quiet --show 
Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6

Busy%   Bzy_MHz IRQ PkgTmp  PkgWatt GFXWatt
2.95800 334747  2.160.01
2.76800 306949  2.150.01
5.85800 512248  2.730.01
11.87   800 800847  3.410.04
8.23800 577847  2.860.05

rt@sys76:~$ 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:   60
Model name:  Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Stepping:3
CPU MHz: 798.103
CPU max MHz: 3400.
CPU min MHz: 800.
BogoMIPS:4788.65
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 Itlb multihit: KVM: Mitigation: Split huge pages
Vulnerability L1tf:  Mitigation; PTE Inversion; VMX conditional 
cache flushes, SMT vulne
 rable
Vulnerability Mds:   Mitigation; Clear CPU buffers; SMT 
vulnerable
Vulnerability Meltdown:  Mitigation; PTI
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitizatio
 n
Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB 
conditional, IBRS_FW, STIB
 P conditional, RSB filling
Vulnerability Srbds: Mitigation; Microcode
Vulnerability Tsx async abort:   Not affected
Flags:   fpu vme de pse tsc msr pae mce cx8 apic 
sep mtrr pge mca cmov pat p
 se36 clflush dts acpi mmx fxsr sse sse2 ss 
ht tm pbe syscall nx pdp
 e1gb rdtscp lm constant_tsc arch_perfmon 
pebs bts rep_good nopl xto
 pology nonstop_tsc cpuid aperfmperf pni 
pclmulqdq dtes64 monitor ds
 _cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

2020-10-08 Thread Rick T 
I switched display managers from lightdm to gdm and it fixed the issue

sudo systemctl status display-manager

sudo dpkg-reconfigure lightdm

systemctl status gdm.service

sudo apt install --reinstall ubuntu-session

reboot machine

Info about the issue:
https://bbs.archlinux.org/viewtopic.php?id=150017

https://askubuntu.com/questions/1245071/cant-lock-screen-with-shortcut-
on-ubuntu-20-04-gnome

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

2020-10-04 Thread Rick T 
I get false

rt@sys76:~$  gsettings get org.gnome.desktop.lockdown disable-lock-screen
false

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

2020-10-02 Thread Rick T 
Sure

The Keyboard Shortcuts for Lock Screen is set to Ctrl+Alt+L
Found in Settings -> Keyboard Shortcuts -> Lock screen -> Ctrl+Alt+L

1) I can't lock the screen using the (keybinding / shortcut) Ctrl+Alt+L 
https://i.imgur.com/VKiXvZV.png

2) I can lock the screen by clicking on the lock option but the screen doesn't 
go blank
https://i.imgur.com/JDHEs2Q.png

3) Here's something that looks interesting I found in the journalctlr file
Oct 02 19:18:52 sys76 gnome-shell[2577]: meta_window_raise: assertion 
'!window->override_redirect' failed
Oct 02 19:18:52 sys76 gnome-shell[2577]: meta_window_lower: assertion 
'!window->override_redirect' failed
Oct 02 19:18:56 sys76 gsd-media-keys[2742]: Couldn't lock screen: Cannot invoke 
method; proxy is for the well-known name org.gnome.ScreenSaver without an 
owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START 
flag

4) The full file is below


** Attachment added: "journalctl -b 0 > jour.txt  file requested"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+attachment/5416816/+files/jour.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

2020-10-02 Thread Rick T 
1. The specific steps or actions you took that caused you to encounter
the problem.

-I tried to set the screen to lock at a specific interval and it doesn't lock
Settings-> Privacy-> Screen Lock -> Automatic Screen Lock -> Enabled
Settings-> Privacy-> Screen Lock -> Automatic Screen Lock -> 30 seconds



-The screen doesn't go blank at all (option found under)
Settings-> Privacy-> Screen Lock -> Blank screen Delay -> 1 minute


2. The behavior you expected.
It should lock the screen and have the screen go blank but it doesn't

3. The behavior you actually encountered (in as much detail as possible).
Nothing happens the screen doesn't lock or goes blank.


Please also ensure that you include the release and flavour of Ubuntu that you 
are using.
I upgraded from 18.04 to 20.04.1 using the sotware updater GUI
rt@sys76:~$ uname -a
Linux sys76 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

About me including the file-manager being nemo I was just trying to
include everything I could think of to help out.

If you need anything else let me know.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

2020-10-02 Thread Rick T 
Should be: 
Settings-> Privacy-> Screen Lock -> Automatic Screen Lock Delay -> 30 seconds

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

2020-10-02 Thread Rick T 
The options for locking, blanking and shortcut keys are in the gnome-
control-center

** Package changed: ubuntu => gnome-control-center (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

2020-10-01 Thread Rick T 
rt@sys76:~$ uname -a
Linux sys76 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1898153/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898153] [NEW] I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

2020-10-01 Thread Rick T 
Public bug reported:

I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
blank at the set time.  I think this issue also effects the shortcuts
not working also.

I'm using nemo as my file manager I followed these instructions below

https://itsfoss.com/install-nemo-file-manager-ubuntu/

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1898153/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1673344] [NEW] Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely (intel 7260) even when I try to restart network manager

2017-03-16 Thread Rick T 
Public bug reported:

My wireless connection completely disappears and isn't recognized along
with my NIC card and doesn't come back until I reboot even if I restart
network manager.


I've attached the required files showing what my wifi information looks like 
connected and what it looks like when the problem occurs hopefully a fix or 
workaround can be found this happens several times a day.

Steps:

1) I boot up type in sudo iwconfig wlp3s0 power off (turn off power 
management)
 
2) 
$ iwconfig
enp4s0f2  no wireless extensions.

lono wireless extensions.

wlp3s0IEEE 802.11  ESSID:"2.4ghz"  
  Mode:Managed  Frequency:2.437 GHz  Access Point: 
E0:3F:29:93:3F:20   
  Bit Rate=144.4 Mb/s   Tx-Power=22 dBm   
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Power Management:off
  Link Quality=60/70  Signal level=-50 dBm  
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:55   Missed beacon:0

3) I loose wifi using 5ghz or 2.4ghz after a certain amount of time

4) sudo rmmod iwlmvm iwlwifi && sudo modprobe iwlmvm iwlwifi
5) sudo systemctl restart network-manager.service

I do a **iwconfig** and **I'm missing wlp3s0IEEE 802.11
ESSID:"2.4ghz"**

$ iwconfig
enp4s0f2  no wireless extensions.

lono wireless extensions.

I have to reboot to get my wifi back and for ubunutu to recognize my
wifi card back how can I prevent this.

$ uname -a
Linux sys76 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

$ dmesg | grep iwlwifi
876.891600] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
[  876.891602] iwlwifi :03:00.0: Scan failed! ret -5
[  877.909370] iwlwifi :03:00.0: Failed to wake NIC for hcmd
[  877.909397] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
[  877.909409] iwlwifi :03:00.0: Scan failed! ret -5
[  878.928277] iwlwifi :03:00.0: Failed to wake NIC for hcmd
[  878.928364] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
[  878.928366] iwlwifi :03:00.0: Scan failed! ret -5
[  879.947120] iwlwifi :03:00.0: Failed to wake NIC for hcmd
[  879.947170] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
[  879.947172] iwlwifi :03:00.0: Scan failed! ret -5


$ sudo lshw -C network
[sudo] password for rt: 
  *-network   
   description: Wireless interface
   product: Wireless 7260
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:03:00.0
   logical name: wlp3s0
   version: 73
   serial: 0c:8b:fd:2e:64:8e
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=4.8.0-41-generic firmware=17.352738.0 ip=192.168.1.8 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
   resources: irq:31 memory:f7d0-f7d01fff
  *-network
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0.2
   bus info: pci@:04:00.2
   logical name: enp4s0f2
   version: 0a
   serial: 00:90:f5:f9:d4:f8
   size: 10Mbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list 
ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8411-1_0.0.3 06/18/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
   resources: irq:27 ioport:e000(size=256) memory:f0004000-f0004fff 
memory:f000-f0003fff
$ 

ethtool -i wlp3s0 | grep driver
driver: iwlwifi


$ dmesg | grep iwlwifi


[3.183972] iwlwifi :03:00.0: loaded firmware version 17.352738.0 
op_mode iwlmvm
[3.214247] iwlwifi :03:00.0: Detected Intel(R) Dual Band Wireless AC 
7260, REV=0x144
[3.216284] iwlwifi :03:00.0: L1 Disabled - LTR Enabled
[3.216508] iwlwifi :03:00.0: L1 Disabled - LTR Enabled
[3.733932] iwlwifi :03:00.0 wlp3s0: renamed from wlan0
[4.369906] iwlwifi :03:00.0: L1 Disabled - LTR Enabled
[4.370133] iwlwifi :03:00.0: L1 Disabled - LTR Enabled
[4.590402] iwlwifi :03:00.0: L1 Disabled - LTR Enabled
[4.590625] iwlwifi :03:00.0: L1 Disabled - LTR Enabled
[ 2613.473520] iwlwifi 000

[Bug 196561] Re: can't print multiple pages in open office calc

2008-04-29 Thread Rick T 
Hi, I have ubuntu  hardy and I have the same problem. I can only print
one Cal sheet at a time. That is page 1 only. Page 2 wont even show in
the print preview. I have another older computer with dapper drake and I
dont have this problem.

Regards Rick T

-- 
can't print multiple pages in open office calc
https://bugs.launchpad.net/bugs/196561
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs