[Kernel-packages] [Bug 1919150] [NEW] My keybord does not work

Public bug reported: I am using UBUNTU 18. My keyboard and mouse do not work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-136-generic 4.15.0-136.140 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion:

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

@koba I've tried to install the vanilla kernel you linked, I'm installing with a `dpkg -i *.deb` command in a folder of the unpacked downloaded zip of that folder. I'm getting the following error (I've been having issues with the nvidia 535 driver, I don't know exactly what's going on here,

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

I posted an issue on the repo of that razer-cli tool, maybe they can help. (I apologize for my triple post above, but I think I know how they happened so...) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu.

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

** Attachment added: "thermaldLog_Adaptive_202309021949.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026658/+attachment/5697370/+files/thermaldLog_Adaptive_202309021949.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

previous post was too large to add an attachment? or something? here it is. 3MB text file, zipped to ~240k. ** Attachment added: "thermaldLog_Adaptive_202309021949.zip"

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

** Attachment added: "thermaldLog_Adaptive_202309021949.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026658/+attachment/5697371/+files/thermaldLog_Adaptive_202309021949.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

I have an interesting update: I went and compiled/installed this tool: https://github.com/phush0/razer-laptop-control-no-dkms @jadgardner: you will definitely want this, boost mode is at least +15% performance. Its a cli tool for poking the Razer hardware bits to set the different power modes

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

@koba Everything here has been 23.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

I have some ~different behavior, but I was still able to achieve bug 1. Initially I saw some intel_pstate/max_perf_pct getting set to 90, but it would recover quickly. long_term_power would fluctuate from very low values all the way up to the nominal 65. Previously when triggering the bug it

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

No its not new, its a 2022 model, 12 gen has been replaced by 13th gen. Its definitely a software issue introduced in a software update to either thermald or the layer in the kernel it interacts with directly. (There is the group that makes the Linux hardware drivers for Razer products - I think

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

> Maybe it's caused by thermald? See if `sudo systemctl stop thermald` can help. I will try this, I will also reinstall the package. I am waiting to see if using sane power parameters in my script for bug 1 fixes the bug 2 issue, but that means I need to leave it sitting for 12+ hours so my

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

Oops, thought I responded. I was running a different test so couldn't try this immediately. I figured I would do a an apt reinstall thermald first, aanndd that seems to hae fixe bug 1, bug 2 takes many hours to kick in so I will have to leave it on for a ~day to find out. Thank you, hopefully

[Kernel-packages] [Bug 2026658] [NEW] CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

Public bug reported: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

I disabled thermald, I think bug 1 may be resolved now, but bug 2 eventually occurred again overnight. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

I will grep that for you, here is the reference information just after boot when everything works. I have to wait for the bug to kick in (and woke up to blinking cursor in the upper left corner, funnn). reference: /sys/devices/system/cpu/intel_pstate/hwp_dynamic_boost:0

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

Interesting, a new ~intermediate situation of bug 1. Its not constraining that thermal envelope quite as much now. Thermald is running, I guess bug 1 is still present but lessened since I reinstalled it? Computer was not in use. When running `stress -c 1` it places the task on the correct ideal

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

Ok well this is interesting. It has been over 24 hours (uptime 1 day 15:48hrs) and bug 2 still hasn't triggered, "Degraded = no". I probably need this computer today, so I ran `stress -c 1` to try to force the high temperature power state after running the script to reset the power values, but

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

reference data point: the power values just after a reboot when thermald is not installed are: {'backup_rest': 65536, 'locked': False, 'long_term_enabled': True, 'long_term_power': 65.0, 'long_term_time': 56.0, 'short_term_enabled': True, 'short_term_power': 160.0, 'short_term_time':

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

So far I have not had either bug recur with thermald uninstalled, I'm satisfied that thermald was the culprit for bug one. Running `stress -c 2` (highest possible thermal load) doesn't trigger anything. The grep on this run is /sys/devices/system/cpu/intel_pstate/hwp_dynamic_boost:1

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

Nope, running stress -c 2 yields... long_term_power starts at 65, drops to ~10, then jumps around values like 37.625, 30.0, 31.0, 28.0, but then after a ~minute the power values look like this and clearly aren't recovering: {'backup_rest': 281474976776192, 'locked': False, 'long_term_enabled':

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

Not to distract too much, but I have also uncovered a separate, replicable performance bug that is quite bizarre. tl;dr, though reported clock speeds are consistently higher after running `cpupower frequency- set -g performance` I see very reliable on-the-order-of-40%-ish performance loss on a

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

I'm running day-to-day without thermald installed, so I will need to find time to do this. But yes I can. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

I have updates! - I set /sys/devices/system/cpu/intel_pstate/max_perf_pct to 100 and confirmed that it restore the 4.7/4.8 peak turbo frequencies. - I ran `stress -c 1`, cpu package temps went up to ~84 degrees C. No changes on the grep, no changes on the powerprofilesctl degraded state. - I ran

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

Received a response on github from the maintainer, https://github.com/Razer-Linux/razer-laptop-control-no- dkms/issues/37#issuecomment-1808340928 Relevant extract of that comment is: my opinion is uninstall thermald, as for Razer laptop it does nothing positive, same for tlp. Control on the

[Kernel-packages] [Bug 1283625] [NEW] bugs

Public bug reported: i cannot update ubuntu13.10, environment variable (such as export) not find,as well .thx ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic

[Kernel-packages] [Bug 1426973] [NEW] package linux-image-3.13.0-46-generic 3.13.0-46.76 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Public bug reported: upon statup recieved this error. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-46-generic 3.13.0-46.76 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6

[Kernel-packages] [Bug 1893858] [NEW] Touchpad not working

: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli1279 F pulseaudio /dev/snd/controlC1: eli1279 F pulseaudio

[Kernel-packages] [Bug 1918994] [NEW] general protection fault on Ubuntu 4.15.0-1103.114~16.04.1-azure 4.15.18

Public bug reported: Hello The following kernel tainted scenario have been observed in Azure VMs. This happened some weeks after the kernel was upgraded from 4.15.0-1098-azure to 4.15.0-1103-azure. Now, the VMs have been updated to kernel 1106 and the issue has not been observed. but want to

[Kernel-packages] [Bug 1324529] [NEW] Backlight not adjustable

Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu May 29

[Kernel-packages] [Bug 1324529] Re: Backlight not adjustable

3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13

[Kernel-packages] [Bug 1324529] UdevDb.txt

3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13

[Kernel-packages] [Bug 1324529] IwConfig.txt

3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13

[Kernel-packages] [Bug 1324529] UdevLog.txt

3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13

[Kernel-packages] [Bug 1324529] Re: Backlight not adjustable

PID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu May 29 08:43:12 2014 InstallationDate

[Kernel-packages] [Bug 1324529] CRDA.txt

-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13

[Kernel-packages] [Bug 1324529] PulseList.txt

: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm

[Kernel-packages] [Bug 1324529] ProcModules.txt

: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg

[Kernel-packages] [Bug 1324529] ProcEnviron.txt

: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg

[Kernel-packages] [Bug 1324529] HookError_source_linux_meta.txt

3.13.0-27.50 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error

[Kernel-packages] [Bug 1324529] ProcInterrupts.txt

ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c

[Kernel-packages] [Bug 1324529] Dependencies.txt

: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg

[Kernel-packages] [Bug 1324529] Lsusb.txt

-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13

[Kernel-packages] [Bug 1324529] ProcCpuinfo.txt

: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg

[Kernel-packages] [Bug 1324529] Lspci.txt

-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13

[Kernel-packages] [Bug 1324529] Re: Backlight not adjustable

ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command

[Kernel-packages] [Bug 1307064] Re: Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570

This might be related to bug 1324529. On my Lenovo T530, there is only thinkpad_screen in /sys/class/backlight. The fixes suggested here (the acpi_backlight=vendor and 80-backlight.conf) do not fix the issue for me and echoing numbers into /sys/class/backlight/thinkpad_screen/brightness does

[Kernel-packages] [Bug 1324529] Re: [Lenovo ThinkPad T530] Backlight not adjustable

: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg

[Kernel-packages] [Bug 1324529] Re: [Lenovo ThinkPad T530] Backlight not adjustable

3.13.0-27.50 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eli3150 F pulseaudio CurrentDmesg: Error

[Kernel-packages] [Bug 1796469] Re: aws s3 cp --recursive hangs on the last file on a large file transfer to instance

Not sure if it's related but I'll leave this here. We have a bunch of EC2 instances running Ubuntu 18.04 LTS and GitLab Runner, with the latter configured to execute build jobs inside Docker containers. Our EC2 instances are of the t2.medium, t2.xlarge and t3.medium sizes and run in the

[Kernel-packages] [Bug 1796469] Re: aws s3 cp --recursive hangs on the last file on a large file transfer to instance

Can also confirm that the 4.15.0-1025-aws kernel appears to have solved the timeout issues we were seeing with `git clone` processes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu.