[Kernel-packages] [Bug 2022826] Re: Ethernet hangs
[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: Expired Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19
[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. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: 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 in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = True 11 │
[Kernel-packages] [Bug 2033944] Re: Thinkpad X1 Carbon sound is still tinny
** Description changed: This is not a new issue, and despite the fix reported in https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108 the - sound remains thin and lacking bass in Thinkpad Xi Carbon models up to + sound remains thin and lacking bass in Thinkpad X1 Carbon models up to and including the latest generations. Hoping that this will be dealt with eventually, but definitely not holding my breath. (I've had this issue on X1 Carbon Generation 7, 9, and now 11. Running Ubuntu 22.04.3 alsa-ucm-conf: - Installed: 1.2.6.3-1ubuntu1.7 - Candidate: 1.2.6.3-1ubuntu1.7 - Version table: - *** 1.2.6.3-1ubuntu1.7 500 - 500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages - 500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages - 100 /var/lib/dpkg/status - 1.2.6.3-1ubuntu1 500 - 500 http://jp.archive.ubuntu.com/ubuntu jammy/main amd64 Packages - 500 http://jp.archive.ubuntu.com/ubuntu jammy/main i386 Packages + Installed: 1.2.6.3-1ubuntu1.7 + Candidate: 1.2.6.3-1ubuntu1.7 + Version table: + *** 1.2.6.3-1ubuntu1.7 500 + 500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages + 500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages + 100 /var/lib/dpkg/status + 1.2.6.3-1ubuntu1 500 + 500 http://jp.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + 500 http://jp.archive.ubuntu.com/ubuntu jammy/main i386 Packages What I expect: Sound from all speakers including some bass What happens: Very thin, tinny sound, no bass. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2033944 Title: Thinkpad X1 Carbon sound is still tinny Status in alsa-ucm-conf package in Ubuntu: New Bug description: This is not a new issue, and despite the fix reported in https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108 the sound remains thin and lacking bass in Thinkpad X1 Carbon models up to and including the latest generations. Hoping that this will be dealt with eventually, but definitely not holding my breath. (I've had this issue on X1 Carbon Generation 7, 9, and now 11. Running Ubuntu 22.04.3 alsa-ucm-conf: Installed: 1.2.6.3-1ubuntu1.7 Candidate: 1.2.6.3-1ubuntu1.7 Version table: *** 1.2.6.3-1ubuntu1.7 500 500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.2.6.3-1ubuntu1 500 500 http://jp.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://jp.archive.ubuntu.com/ubuntu jammy/main i386 Packages What I expect: Sound from all speakers including some bass What happens: Very thin, tinny sound, no bass. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2033944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: 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 in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │
[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" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026658/+attachment/5697369/+files/thermaldLog_Adaptive_202309021949.zip -- 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 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: 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 in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 #
[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 thermald in Ubuntu. https://bugs.launchpad.net/bugs/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: In Progress Bug description: 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 in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │
[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 across the combination of CPU and GPU. None of these affect the power details variables or intel pstate values. For simplicity I'm using commands below that leave the GPU untouched. (the tool also lets you control the LEDs, and fan; those are irrelevant and fan doesn't work for me.) All of the below testing was done with that compiled build of thermald running in --adaptive mode. I have attached it. I doubt a single long and fiddly run makes for a great data source, please let me know if there is a specific combination of settings you would like me test. (its 3 megs, I have compressed it. exact command was `sudo ./thermald --no- daemon --adaptive --loglevel=debug`) (reminder: bug 1 is the 400mhz drop and lock, bug 2 is intel_pstate/no_turbo getting set to 1. bug 2 is way harder to trigger.) 1) razer-cli write power ac 4 3 0 Highest "boost" performance mode. CPU has much higher all core and multicore speeds, cpu package temp spikes to 100 nearly instantly even moderate load. I cannot trigger bug 1 (or bug 2) in this mode, `stress -c 1` pegs a core at 4.8ghz and it stays there. `stress -c 2` stays at values around ~4775MHz with periodic drops down to ~4450MHz but then jumps right back up after about 1 second. long_term_power either rock solid at 65 or very briefly drops down and then goes back up. 2) razer-cli write power ac 4 2 0 "High" performance mode. It looks like this one sets a cpu target temperature around 90 for all/multicore, frequencies are higher than normal, temperature does force frequencies down at least until the fan ramps up a bit. `stress -c 1` pegged a cpu core for less than a minute at 4.8, and then intel_pstate/max_perf_pct got set to 90 and cpu frequency dropped to 400MHz, and long_term_power dropped to 0.125. (e.g. bug 1). Swapping back to level 3 (Boost) mode did not resolve bug. Setting intel_pstate/max_perf_pct back to 100 does not resolve bug. Setting long_term_power back to 65 resolves bug. 3) razer-cli write power ac 4 1 0 "Medium" power mode. The behavior looks like a normal ~aggressive laptop performance behavior. `stress -c 1` pegs a cpu core at 4.8, temps spike, fan slowly spins up. CPU speed drops down to various levels (2.8ghz, 4.5ghz, 4.3ghz, 4.2ghz), temperatures drop from mid 90s to mid 80s or 70s for a bit, long_term_power drops to values in the 20-30s, but then resets back to 65 after a few seconds. I was able to trigger long_term_power down to 0.125 once by toggling stressing 1 vs 2 cpu cores, but it still reset up to 65 after a few seconds. Otherwise I was not able to trigger bug 1 or 2. (All and multicore CPU speeds are pretty close to normal, looks like it targets ~75 degrees) 4) razer-cli write power ac 4 0 0 "low" power mode. All and multicore CPU speeds are pretty close to normal, looks like it targets ~70 degrees, very close to "Medium". This behavior looks like a lower or fairly passive power mode on a laptop. Pegging a single core would get 4.8ghz for a while, adding a second would briefly get the normal behavior, but then the system would back down to 4.6, 4.5, 4.2, 3.9Ghz. Temperature would spike to 92-100 range only in the 4.7-4.8Ghz range (this is normal) and then would back off pretty quickly. long_term_power would drop to a value like 22 pretty quickly and stay there. If I was very quick with toggling between one and two pegged cores I could hit 16, but then the value would recover back up to the default 65 and reset the process. I was not able to trigger bug 1 at any point. 5) razer-cli write power ac 0 (this is a slightly different command than the others) "Balanced" mode (according to the docs this is the normal operating mode, I'm skeptical?) Seems to behave like a laptop that uses up its boost-range thermal headroom very quickly. All and multicore seem to target 70 degrees, normal-to-low cpu frequencies. I could only get 1 or 2 pegged cores to reach 4.8Ghz for a handful of seconds, then the max speed became about 4.6 but would hover in the 4.2-4.6 range for the rest of the test. If I let it sit idle for 30 seconds it would recover to allow for brief 4.8 spikes again. long_term_power would drop to ~30, and would sit there until load dropped, at which point it would recover to the default 65. Due to the inability to hit 4.8Ghz for long periods I was not able to trigger bug 1. -- 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 400Mhz on Alder Lake Status in linux package in Ubuntu: Incomplete Status in thermald
[Kernel-packages] [Bug 2027914] Re: missing nvidia kernel module for generic kernel (linux-objects-nvidia-535-6.2.0-25-generic)
Upgraded to linux-image-generic-hwe-22.04 on Ubuntu 22.04 with nvidia-driver-535 already installed and landed in the same situation. Attempts to re-install the nvidia driver fail to produce a working system, unable to use HWE in 22.04 due to this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2027914 Title: missing nvidia kernel module for generic kernel (linux-objects- nvidia-535-6.2.0-25-generic) Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: For latest generic kernel for Ubuntu 23.04 there in no package of kernel module. Present is for previous kernel: # aptitude search linux-objects-nvidia-535.*generic i A linux-objects-nvidia-535-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-open-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-open-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) There is no package for 6.2.0-25 kernel. So after upgrade to new kernel - gpu isn't working, as the module is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2027914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027848] Re: Soft-lockup caused by snd_hda_intel
Using Ubuntu 6.5.0-2.2 kernel as it is most likely to write the journal after a lockup, I turned on some audio debug and saw this: cold boot (all entries below have the same timestamp) jammy kernel: snd_sof_intel_hda:hda_codec_probe: sof-audio-pci-intel-tgl :00:1f.3: HDA codec #0 probed OK: response: 10ec0236 jammy kernel: snd_sof_intel_hda:request_codec_module: hdaudio ehdaudio0D0: loading codec module: hdaudio:v10EC0236r0012a01 jammy kernel: snd_sof_intel_hda:hda_codec_probe: sof-audio-pci-intel-tgl :00:1f.3: HDA codec #2 probed OK: response: 80862812 jammy kernel: snd_sof_intel_hda:request_codec_module: hdaudio ehdaudio0D2: loading codec module: hdaudio:v80862812r0010a01 warm boot jammy kernel: snd_sof_intel_hda:hda_codec_probe: sof-audio-pci-intel-tgl :00:1f.3: HDA codec #0 probed OK: response: fe05 jammy kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [kworker/2:1:92] So it seems the HDA codec probe should return a PCI ID and for some reason after a warm boot it does not. -- 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/2027848 Title: Soft-lockup caused by snd_hda_intel Status in linux package in Ubuntu: Confirmed Bug description: I report this bug the the 6.5rc1 kernel. Kernel before 6.5 hang even before there is any logging going on. The problem is gone when i blacklist snd_hda_core. jul 15 09:02:52 nick-HP-Laptop-15s-fq4xxx kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 78s! [kworker/1:1:90] jul 15 09:02:52 nick-HP-Laptop-15s-fq4xxx kernel: Modules linked in: snd_seq_dummy snd_hrtimer rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_> jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: hp_wmi snd_timer videodev input_leds spi_nor rapl cec sparse_keymap cfg80211 intel_cstate wmi_bmof serio_raw platform_profile videobuf2_common snd mei_> jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: CPU: 1 PID: 90 Comm: kworker/1:1 Tainted: G U WL 6.5.0-060500rc1-generic #202307092131 jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: Hardware name: HP HP Laptop 15s-fq4xxx/89BC, BIOS F.31 03/25/2023 jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: Workqueue: events azx_probe_work [snd_hda_intel] jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: RIP: 0010:_raw_spin_unlock_irq+0x15/0x50 jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: Code: cc cc 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 c6 07 00 0f 1f 00 fb 0f 1f 44 00 00 <65> ff 0d 5c 61 52 > jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: RSP: 0018:b450c05dbb30 EFLAGS: 0246 jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: RAX: 0007 RBX: 0007 RCX: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033967] [NEW] Laptop screen blinked, no tty works and 200 dmesg errors per second
Public bug reported: I was using my laptop and suddenly the screen blinked. After that, all I could do was to move the mouse, no interaction worked. Trying to change to a TTY would open the black screen but the text cursor wasn't blinking and nothing happened. I accessed the laptop via SSH and used: screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace To reload xfwm4. After that, the graphical interface started working again. However, no TTY is accessible and there are 200 dmesg errors per second. These are the errors that repeat endlessly: [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) And while I was writing this report, another problem happened: [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=2, emitted seq=6 [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process obs pid 38687 thread obs:cs0 pid 38694 [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin! [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 0x0100 != 0x [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.731204] [ cut here ] [44566.731205] WARNING: CPU: 15 PID: 29333 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk snd_rawmidi uvcvideo [44566.731465] snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq ath1 0k_pci [44566.731504] ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd r8169 video i2c_piix4 i2c_hid xhci_pci_renesas nvme_common realtek wmi hid [44566.731529] CPU: 15 PID: 29333 Comm: kworker/u32:1 Tainted: PW O 6.2.0-31-generic #31~22.04.1-Ubuntu [44566.731531] Hardware name: LENOVO 82MJ/LNVNB161216, BIOS H3CN36WW(V2.06) 09/30/2022 [44566.731533] Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched] [44566.731539] RIP: 0010:amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731702] Code: 31 f6 31 ff c3 cc cc cc cc 44 89 ea 4c 89 e6 4c 89 f7 e8 8f fc ff ff 5b 41 5c 41 5d 41 5e 5d 31 d2 31 f6 31 ff c3 cc cc cc cc <0f> 0b b8 ea ff ff ff eb c3 b8 ea ff ff ff eb bc b8 fe ff ff ff eb [44566.731704] RSP: 0018:b149228cfbf8 EFLAGS: 00010246 [44566.731705] RAX: RBX: 0001 RCX: [44566.731706] RDX: RSI: RDI: [44566.731707] RBP: b149228cfc18 R08: R09: [44566.731708]
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@Kur1977 @yash AFAIK version users with version 22.04 (born with kernel 5.x) are supposed to follow my approach on github version users with version >= 23.x (with kernel 6.x) are supposed to follow the https://github.com/Kvalme/uvc.git Strange thing, is that now 22.04 is using kernel 6.2, but still works with "old" approach... -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release:
[Kernel-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
Same problem on my father's laptop: stuck on reboot or shutdown with 6.2 kernel (tested with 6.2.0-26-generic and 6.2.0-31-generic). Model : ASUS TUF GAMMING F17 Graphic card : Nvidia GeForce RTX 2050 It uses the Nouveau driver. You'll find attached the output for the below command: journalctl -b -1 --since "1 hour ago" I cannot test the patched kernel at the moment. ** Attachment added: "output.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2031352/+attachment/5697283/+files/output.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2031352 Title: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Bug description: After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
Hi @giuliano69 I followed the steps from #19 for Fedora 38 (linux kernel 6.4). I got it working by just replacing the code part for `usb_device_id uvc_ids[]`, but after reboot it gets removed and I have to do insmod ./path_to_uvc/uvcvideo.ko -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 -
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
Does anyone have any idea how to make the Ubuntu or Ethernet interface automatically reboot on failure? -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm ulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246 [Mon Aug 7 12:39:19 2023] RAX: RBX: 997996868000 RCX: [Mon Aug 7 12:39:19 2023] RDX: RSI: RDI: [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08: R09: [Mon Aug 7 12:39:19 2023] R10: R11: R12: 9979968684c8 [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14: R15: [Mon Aug 7 12:39:19 2023] FS: () GS:997da930() knlGS: [Mon Aug 7 12:39:19 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000 CR3: 000329810004 CR4: 003726e0 [Mon Aug 7 12:39:19 2023] Call Trace: [Mon Aug 7 12:39:19 2023] [Mon Aug 7 12:39:19 2023] ? __pfx_dev_watchdog+0x10/0x10 [Mon Aug 7 12:39:19 2023] call_timer_fn+0x29/0x160 [Mon Aug 7 12:39:19 2023] ?
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
after around 68 hours without network problem it happened again there was some network issue on other devices at the moment where it resolved automatically but not on my ubuntu pc I tested the cable on other pc and it worked with no issue but I had to restart my pc I do not know if there is a way to restart just the part managing the network may be make a script restarting it if a problem detected sudo dmesg [0.00] Linux version 6.2.0-31-generic (buildd@lcy02-amd64-068) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~23.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #31-Ubuntu SMP PREEMPT_DYNAMIC Mon Aug 14 13:42:26 UTC 2023 (Ubuntu 6.2.0-31.31-generic 6.2.15) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=bad00fc3-af76-403c-a8f8-e4b840d16e23 ro quiet splash pcie_aspm=off vt.handoff=7 ... [243476.036212] audit: type=1400 audit(1693645893.352:387): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36eaf76d6640d9dc" pid=110650 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [243779.727985] [ cut here ] [243779.727991] NETDEV WATCHDOG: enp3s0 (r8169): transmit queue 0 timed out [243779.728000] WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [243779.728004] Modules linked in: snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables libcrc32c nfnetlink bridge stp llc nvidia_uvm(PO) binfmt_misc nls_iso8859_1 nvidia_drm(PO) nvidia_modeset(PO) snd_ctl_led snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof intel_rapl_msr snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core intel_rapl_common snd_soc_acpi_intel_match intel_tcc_cooling x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp nvidia(PO) soundwire_bus snd_soc_core snd_hda_codec_hdmi i915 snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel coretemp snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm_intel snd_hda_core snd_hwdep drm_buddy mei_pxp mei_hdcp snd_pcm kvm dell_wmi irqbypass [243779.728099] snd_seq_midi ttm snd_seq_midi_event crct10dif_pclmul drm_display_helper snd_rawmidi polyval_clmulni polyval_generic cec ghash_clmulni_intel dell_smbios snd_seq rc_core sha512_ssse3 aesni_intel drm_kms_helper ledtrig_audio dcdbas i2c_algo_bit crypto_simd snd_seq_device cryptd rapl dell_wmi_sysman intel_cstate cmdlinepart sparse_keymap firmware_attributes_class dell_wmi_descriptor snd_timer spi_nor mtd syscopyarea wmi_bmof ee1004 snd mei_me soundcore sysfillrect mei sysimgblt intel_pch_thermal input_leds acpi_pad mac_hid msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid r8169 nvme crc32_pclmul nvme_core realtek video spi_intel_pci intel_lpss_pci i2c_i801 ahci intel_lpss nvme_common spi_intel i2c_smbus libahci xhci_pci idma64 xhci_pci_renesas wmi pinctrl_cannonlake [243779.728207] CPU: 8 PID: 0 Comm: swapper/8 Tainted: P O 6.2.0-31-generic #31-Ubuntu [243779.728209] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.14.0 06/27/2023 [243779.728211] RIP: 0010:dev_watchdog+0x23a/0x250 [243779.728213] Code: 00 e9 2b ff ff ff 48 89 df c6 05 fb 9f 75 01 01 e8 8b 09 f8 ff 44 89 f1 48 89 de 48 c7 c7 60 37 67 b9 48 89 c2 e8 46 ff 28 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [243779.728215] RSP: 0018:ab5500324e38 EFLAGS: 00010246 [243779.728217] RAX: RBX: 9aacd3638000 RCX: [243779.728219] RDX: RSI: RDI: [243779.728220] RBP: ab5500324e68 R08: R09: [243779.728221] R10: R11: R12: 9aacd36384c8 [243779.728222] R13: 9aacd363841c R14: R15: [243779.728224] FS: () GS:9ab3dd40() knlGS: [243779.728225] CS: 0010 DS: ES: CR0: 80050033 [243779.728227] CR2: 0ad0fe594000 CR3: 00044c610006 CR4: 003706e0 [243779.728229] Call Trace: [243779.728230] [243779.728233] ? __pfx_dev_watchdog+0x10/0x10 [243779.728236] call_timer_fn+0x29/0x160 [243779.728239] ? __pfx_dev_watchdog+0x10/0x10 [243779.728240] __run_timers+0x259/0x310 [243779.728243] run_timer_softirq+0x1d/0x40 [243779.728245] __do_softirq+0xd6/0x346 [243779.728248] ? hrtimer_interrupt+0x11f/0x250 [243779.728251] __irq_exit_rcu+0xa2/0xd0 [243779.728254] irq_exit_rcu+0xe/0x20 [243779.728256] sysvec_apic_timer_interrupt+0x92/0xd0 [243779.728258] [243779.728259] [243779.728260]
[Kernel-packages] [Bug 2027848] Re: Soft-lockup caused by snd_hda_intel
I tested before rebooting by using the following commands: sudo rmmod snd_sof_pci_intel_tgl sudo rmmod snd_sof_intel_hda_common sudo rmmod snd_hda_intel sudo rmmod snd_intel_dspcfg sudo modprobe snd_intel_dspcfg dsp_driver=1 sudo modprobe snd_sof_intel_hda_common sudo modprobe snd_sof_pci_intel_tgl sudo modprobe snd_hda_intel After un-muting the output, a video played ok in vlc without any other changes. To persist the change I created a conf file in /etc/modprobe.d and ran sudo update-initramfs -k all -u. After a cold boot, a video played ok in vlc. After a warm boot, I saw lockups. This was using 5.15.0-82. -- 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/2027848 Title: Soft-lockup caused by snd_hda_intel Status in linux package in Ubuntu: Confirmed Bug description: I report this bug the the 6.5rc1 kernel. Kernel before 6.5 hang even before there is any logging going on. The problem is gone when i blacklist snd_hda_core. jul 15 09:02:52 nick-HP-Laptop-15s-fq4xxx kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 78s! [kworker/1:1:90] jul 15 09:02:52 nick-HP-Laptop-15s-fq4xxx kernel: Modules linked in: snd_seq_dummy snd_hrtimer rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_> jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: hp_wmi snd_timer videodev input_leds spi_nor rapl cec sparse_keymap cfg80211 intel_cstate wmi_bmof serio_raw platform_profile videobuf2_common snd mei_> jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: CPU: 1 PID: 90 Comm: kworker/1:1 Tainted: G U WL 6.5.0-060500rc1-generic #202307092131 jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: Hardware name: HP HP Laptop 15s-fq4xxx/89BC, BIOS F.31 03/25/2023 jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: Workqueue: events azx_probe_work [snd_hda_intel] jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: RIP: 0010:_raw_spin_unlock_irq+0x15/0x50 jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: Code: cc cc 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 c6 07 00 0f 1f 00 fb 0f 1f 44 00 00 <65> ff 0d 5c 61 52 > jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: RSP: 0018:b450c05dbb30 EFLAGS: 0246 jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: RAX: 0007 RBX: 0007 RCX: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
Got 0x4033 webcam to work. First of all install 6.3 kernel with Mainline Kernels software. than sudo apt-get install dwarves build-essential sudo cp /sys/kernel/btf/vmlinux /usr/lib/modules/`uname -r`/build/ git clone https://github.com/Kvalme/uvc.git cd ./uvc/ than change 4035 to 4033 in uvc_driver.c make sudo cp /lib/modules/$(uname -r)/kernel/drivers/media/usb/uvc/uvcvideo.ko{,.back} sudo cp uvcvideo.ko /lib/modules/$(uname -r)/kernel/drivers/media/usb/uvc/uvcvideo.ko sudo reboot Voila. Camera works -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@Giuliano Trying to start you script and got this error ((( home/serg/linux-hwe-6.2-6.2.0/drivers/media/usb/uvc/uvc_driver.c:254:39: error: ‘struct uvc_format’ has no member named ‘name’ 254 | strscpy(format->name, fmtdesc->name, | ^~ /home/serg/linux-hwe-6.2-6.2.0/drivers/media/usb/uvc/uvc_driver.c:255:46: error: ‘struct uvc_format’ has no member named ‘name’ 255 | sizeof(format->name)); | ^~ /home/serg/linux-hwe-6.2-6.2.0/drivers/media/usb/uvc/uvc_driver.c:260:40: error: ‘struct uvc_format’ has no member named ‘name’ 260 | snprintf(format->name, sizeof(format->name), "%pUl\n", |^~ /home/serg/linux-hwe-6.2-6.2.0/drivers/media/usb/uvc/uvc_driver.c:260:61: error: ‘struct uvc_format’ has no member named ‘name’ 260 | snprintf(format->name, sizeof(format->name), "%pUl\n", | ^~ /home/serg/linux-hwe-6.2-6.2.0/drivers/media/usb/uvc/uvc_driver.c:273:47: error: ‘struct uvc_format’ has no member named ‘name’ 273 | strscpy(format->name, "Greyscale 8-bit (Y8 )", | ^~ /home/serg/linux-hwe-6.2-6.2.0/drivers/media/usb/uvc/uvc_driver.c:274:54: error: ‘struct uvc_format’ has no member named ‘name’ 274 | sizeof(format->name)); -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
hi all and thanks for the help, after the last restart it is up for around 65 hours with no internet problems, I will not shut it down if any thing happen soon I will report it I run now kernel 6.2.0-31 and pcie_aspm=off hope it never let me down again I think there is some thing else happening with PCIe ASPM on my system now but it is working any way sudo dmesg | grep -i "PCIe ASPM" [0.052181] PCIe ASPM is disabled [0.182532] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it -- 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/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Bug description: hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm ulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246 [Mon Aug 7 12:39:19 2023] RAX: RBX: 997996868000 RCX: [Mon Aug 7 12:39:19 2023] RDX: RSI: RDI: [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08: R09: [Mon Aug 7 12:39:19 2023] R10: R11: R12: 9979968684c8 [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14: R15: [Mon Aug 7 12:39:19 2023] FS: ()