[Kernel-packages] [Bug 2019968] Re: Add missing feature bits in EPYC-Milan model
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Mantic) Status: Incomplete => Confirmed -- 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/2019968 Title: Add missing feature bits in EPYC-Milan model Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Jammy: Confirmed Status in qemu source package in Jammy: New Status in linux source package in Kinetic: Won't Fix Status in qemu source package in Kinetic: Won't Fix Status in linux source package in Lunar: Confirmed Status in qemu source package in Lunar: New Status in linux source package in Mantic: Confirmed Status in qemu source package in Mantic: New Bug description: [Impact] Add the following feature bits for EPYC-Milan model and bump the version. vaes: Vector VAES(ENC|DEC), VAES(ENC|DEC)LAST instruction support vpclmulqdq : Vector VPCLMULQDQ instruction support stibp-always-on : Single Thread Indirect Branch Prediction Mode has enhanced performance and may be left Always on amd-psfd: Predictive Store Forward Disable no-nested-data-bp : Processor ignores nested data breakpoints lfence-always-serializing : LFENCE instruction is always serializing null-sel-clr-base : Null Selector Clears Base. When this bit is set, a null segment load clears the segment base [Test Plan] * First of all we'll (and have in advance) run general regression tests * Qemu shall show to be aware of the new types # qemu-system-x86_64 -cpu ? | grep EPYC-Milan x86 EPYC-Milan (alias configured by machine type) x86 EPYC-Milan-v1 AMD EPYC-Milan Processor x86 EPYC-Milan-v2 AMD EPYC-Milan Processor [Where problems could occur] * There are two areas to look at a) compat behavior on old systems - e.g. libvirt would now detect IBRS on such AMD chips and one might wonder about the change. E.g. compatibility would exist between old-code/new-code/old->new code; but any action (e.g. suspend resume) from new to old code might run into trouble (not supported that way but worth to mention for awareness) b) Migrations between systems - this should be covered by chip versioning but still is worth to mention. Versioning will recognize a formerly started system as v1 and continue to handle it that way. Only new started guests would become v2 and behave the new and improved way. [Other Info] * n/a --- https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg02082.html https://github.com/qemu/qemu/commit/27f03be6f59d04bd5673ba1e1628b2b490f9a9ff.patch This patch depends on the definitions that were added as part of the EPYC-Milan patch: amd-psfd, stibp-always-on: * https://github.com/qemu/qemu/commit/bb039a230e6a7920d71d21fa9afee2653a678c48.patch Add feature bits for CPUID_Fn8021_EAX: * https://github.com/qemu/qemu/commit/b70eec312b185197d639bff689007727e596afd1.patch Kernel patches: https://lkml.kernel.org/lkml/20230124163319.2277355-1-kim.phill...@amd.com/ kvm: Add support for CPUID_8021_EAX * https://github.com/torvalds/linux/commit/8415a74852d7c24795007ee9862d25feb519007c.patch kvm: Add the NO_NESTED_DATA_BP feature * https://github.com/torvalds/linux/commit/a9dc9ec5a1fafc3d2fe7a7b594eefaeaccf89a6b.patch kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf * https://github.com/torvalds/linux/commit/84168ae786f8a15a7eb0f79d34f20b8d261ce2f5.patch kvm: Add the Null Selector Clears Base feature * https://github.com/torvalds/linux/commit/5b909d4ae59aedc711b7a432da021be0e82c95a0.patch kvm: Add the SMM_CTL MSR not present feature https://github.com/torvalds/linux/commit/faabfcb194a8d0686396e3fff6a5b42911f65191.patch And probably this one as well: KVM: Add common feature flag for AMD's PSFD https://github.com/torvalds/linux/commit/3d8f61bf8bcd69bcd397276d53aa18f7ca8347f9.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019968/+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 2019971] Re: Add EPYC-Genoa model
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Mantic) Status: Incomplete => Confirmed -- 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/2019971 Title: Add EPYC-Genoa model Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Triaged Status in linux source package in Jammy: Confirmed Status in qemu source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in qemu source package in Kinetic: Won't Fix Status in linux source package in Lunar: Confirmed Status in qemu source package in Lunar: Triaged Status in linux source package in Mantic: Confirmed Status in qemu source package in Mantic: Triaged Bug description: [Impact] * To avoid bugs with newer Hardware and to allow users/admins to control the KVM guests correctly we usually try to backport major CPU- detect/control features back to at least the last LTS (currently jammy) In SRU Terms this is under the second entry in https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases * In this particular case it is about Support for EPYC Genoa chips https://en.wikipedia.org/wiki/Epyc#Fourth_generation_Epyc_(Genoa) [Test Plan] * First of all we'll (and have in advance) run general regression tests * Second you'd want to run this with host-model and host-passthrough on Rome / Milan chips to ensure no case is now falling in to a totally dysfunctional state * Qemu shall show to be aware of the new types # qemu-system-x86_64 -cpu ? | grep EPYC-Genoa x86 EPYC-Genoa (alias configured by machine type) x86 EPYC-Genoa-v1 AMD EPYC-Genoa Processor * Finally migrations between old->new should be checked to work fine. [Where problems could occur] * This kind of "add the new type" usually only s a problem in backward- migratebility which isn't supported anyway. Never the less the areas to look out for is behavior on various AMD EPYC chips. To ensure that old chips won't change in a breaking way (they might detect new features now, but not more) and that new Milan chips are now all detected properly. [Other Info] * This is not the first time new AMD chips need to add their definitions, for example bug 1921880 was similar QEMU added a separate model for EPYC-Genoa in https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg02087.html On the qemu side most bits are already present as far back as jammy. The only things missing are the vnmi and auto-ibrs flag. The lfence-always-serializing, amd-psfd, no-nested-data-bp, null-sel-clr-base are part of the Milan-v2 patch set https://github.com/qemu/qemu/commit/62a798d4bc2c3e767d94670776c77a7df274d7c5.patch https://github.com/qemu/qemu/commit/166b1741884dd4fd7090b753cd7333868457a29b.patch Kernel auto-ibrs et al: https://lkml.kernel.org/lkml/20230124163319.2277355-1-kim.phill...@amd.com/ kvm: Add support for CPUID_8021_EAX * https://github.com/torvalds/linux/commit/8415a74852d7c24795007ee9862d25feb519007c.patch kvm: Add the NO_NESTED_DATA_BP feature * https://github.com/torvalds/linux/commit/a9dc9ec5a1fafc3d2fe7a7b594eefaeaccf89a6b.patch kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf * https://github.com/torvalds/linux/commit/84168ae786f8a15a7eb0f79d34f20b8d261ce2f5.patch kvm: Add the Null Selector Clears Base feature * https://github.com/torvalds/linux/commit/5b909d4ae59aedc711b7a432da021be0e82c95a0.patch kvm: Add the SMM_CTL MSR not present feature https://github.com/torvalds/linux/commit/faabfcb194a8d0686396e3fff6a5b42911f65191.patch x86/cpu: Support AMD Automatic IBRS https://github.com/torvalds/linux/commit/e7862eda309ecfccc36bb5558d937ed3ace07f3f.patch KVM: Add common feature flag for AMD's PSFD https://github.com/torvalds/linux/commit/3d8f61bf8bcd69bcd397276d53aa18f7ca8347f9.patch Add support for virtual NMIs https://github.com/torvalds/linux/commit/4a5fd419952e49ef870e9259d815718062871cc1.patch Please consider adding/backporting these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019971/+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 2019971] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2019971 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux (Ubuntu Lunar) Status: New => Incomplete -- 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/2019971 Title: Add EPYC-Genoa model Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Triaged Status in linux source package in Jammy: Confirmed Status in qemu source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in qemu source package in Kinetic: Won't Fix Status in linux source package in Lunar: Confirmed Status in qemu source package in Lunar: Triaged Status in linux source package in Mantic: Confirmed Status in qemu source package in Mantic: Triaged Bug description: [Impact] * To avoid bugs with newer Hardware and to allow users/admins to control the KVM guests correctly we usually try to backport major CPU- detect/control features back to at least the last LTS (currently jammy) In SRU Terms this is under the second entry in https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases * In this particular case it is about Support for EPYC Genoa chips https://en.wikipedia.org/wiki/Epyc#Fourth_generation_Epyc_(Genoa) [Test Plan] * First of all we'll (and have in advance) run general regression tests * Second you'd want to run this with host-model and host-passthrough on Rome / Milan chips to ensure no case is now falling in to a totally dysfunctional state * Qemu shall show to be aware of the new types # qemu-system-x86_64 -cpu ? | grep EPYC-Genoa x86 EPYC-Genoa (alias configured by machine type) x86 EPYC-Genoa-v1 AMD EPYC-Genoa Processor * Finally migrations between old->new should be checked to work fine. [Where problems could occur] * This kind of "add the new type" usually only s a problem in backward- migratebility which isn't supported anyway. Never the less the areas to look out for is behavior on various AMD EPYC chips. To ensure that old chips won't change in a breaking way (they might detect new features now, but not more) and that new Milan chips are now all detected properly. [Other Info] * This is not the first time new AMD chips need to add their definitions, for example bug 1921880 was similar QEMU added a separate model for EPYC-Genoa in https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg02087.html On the qemu side most bits are already present as far back as jammy. The only things missing are the vnmi and auto-ibrs flag. The lfence-always-serializing, amd-psfd, no-nested-data-bp, null-sel-clr-base are part of the Milan-v2 patch set https://github.com/qemu/qemu/commit/62a798d4bc2c3e767d94670776c77a7df274d7c5.patch https://github.com/qemu/qemu/commit/166b1741884dd4fd7090b753cd7333868457a29b.patch Kernel auto-ibrs et al: https://lkml.kernel.org/lkml/20230124163319.2277355-1-kim.phill...@amd.com/ kvm: Add support for CPUID_8021_EAX * https://github.com/torvalds/linux/commit/8415a74852d7c24795007ee9862d25feb519007c.patch kvm: Add the NO_NESTED_DATA_BP feature * https://github.com/torvalds/linux/commit/a9dc9ec5a1fafc3d2fe7a7b594eefaeaccf89a6b.patch kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf * https://github.com/torvalds/linux/commit/84168ae786f8a15a7eb0f79d34f20b8d261ce2f5.patch kvm: Add the Null Selector Clears Base feature * https://github.com/torvalds/linux/commit/5b909d4ae59aedc711b7a432da021be0e82c95a0.patch kvm: Add the SMM_CTL MSR not present feature https://github.com/torvalds/linux/commit/faabfcb194a8d0686396e3fff6a5b42911f65191.patch x86/cpu: Support AMD Automatic IBRS https://github.com/torvalds/linux/commit/e7862eda309ecfccc36bb5558d937ed3ace07f3f.patch KVM: Add common feature flag for AMD's PSFD https://github.com/torvalds/linux/commit/3d8f61bf8bcd69bcd397276d53aa18f7ca8347f9.patch Add support for virtual NMIs https://github.com/torvalds/linux/commit/4a5fd419952e49ef870e9259d815718062871cc1.patch Please consider adding/backporting these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019971/+subscriptions -- Mailing
[Kernel-packages] [Bug 2019968] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2019968 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux (Ubuntu Lunar) Status: New => Incomplete -- 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/2019968 Title: Add missing feature bits in EPYC-Milan model Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in qemu source package in Jammy: New Status in linux source package in Kinetic: Won't Fix Status in qemu source package in Kinetic: Won't Fix Status in linux source package in Lunar: Incomplete Status in qemu source package in Lunar: New Status in linux source package in Mantic: Incomplete Status in qemu source package in Mantic: New Bug description: [Impact] Add the following feature bits for EPYC-Milan model and bump the version. vaes: Vector VAES(ENC|DEC), VAES(ENC|DEC)LAST instruction support vpclmulqdq : Vector VPCLMULQDQ instruction support stibp-always-on : Single Thread Indirect Branch Prediction Mode has enhanced performance and may be left Always on amd-psfd: Predictive Store Forward Disable no-nested-data-bp : Processor ignores nested data breakpoints lfence-always-serializing : LFENCE instruction is always serializing null-sel-clr-base : Null Selector Clears Base. When this bit is set, a null segment load clears the segment base [Test Plan] * First of all we'll (and have in advance) run general regression tests * Qemu shall show to be aware of the new types # qemu-system-x86_64 -cpu ? | grep EPYC-Milan x86 EPYC-Milan (alias configured by machine type) x86 EPYC-Milan-v1 AMD EPYC-Milan Processor x86 EPYC-Milan-v2 AMD EPYC-Milan Processor [Where problems could occur] * There are two areas to look at a) compat behavior on old systems - e.g. libvirt would now detect IBRS on such AMD chips and one might wonder about the change. E.g. compatibility would exist between old-code/new-code/old->new code; but any action (e.g. suspend resume) from new to old code might run into trouble (not supported that way but worth to mention for awareness) b) Migrations between systems - this should be covered by chip versioning but still is worth to mention. Versioning will recognize a formerly started system as v1 and continue to handle it that way. Only new started guests would become v2 and behave the new and improved way. [Other Info] * n/a --- https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg02082.html https://github.com/qemu/qemu/commit/27f03be6f59d04bd5673ba1e1628b2b490f9a9ff.patch This patch depends on the definitions that were added as part of the EPYC-Milan patch: amd-psfd, stibp-always-on: * https://github.com/qemu/qemu/commit/bb039a230e6a7920d71d21fa9afee2653a678c48.patch Add feature bits for CPUID_Fn8021_EAX: * https://github.com/qemu/qemu/commit/b70eec312b185197d639bff689007727e596afd1.patch Kernel patches: https://lkml.kernel.org/lkml/20230124163319.2277355-1-kim.phill...@amd.com/ kvm: Add support for CPUID_8021_EAX * https://github.com/torvalds/linux/commit/8415a74852d7c24795007ee9862d25feb519007c.patch kvm: Add the NO_NESTED_DATA_BP feature * https://github.com/torvalds/linux/commit/a9dc9ec5a1fafc3d2fe7a7b594eefaeaccf89a6b.patch kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf * https://github.com/torvalds/linux/commit/84168ae786f8a15a7eb0f79d34f20b8d261ce2f5.patch kvm: Add the Null Selector Clears Base feature * https://github.com/torvalds/linux/commit/5b909d4ae59aedc711b7a432da021be0e82c95a0.patch kvm: Add the SMM_CTL MSR not present feature https://github.com/torvalds/linux/commit/faabfcb194a8d0686396e3fff6a5b42911f65191.patch And probably this one as well: KVM: Add common feature flag for AMD's PSFD https://github.com/torvalds/linux/commit/3d8f61bf8bcd69bcd397276d53aa18f7ca8347f9.patch To manage notifications about this bug go to:
[Kernel-packages] [Bug 2033944] [NEW] Thinkpad X1 Carbon sound is still tinny
Public bug reported: 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 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. ** Affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New -- 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 Xi 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 2025585] Re: Nvidia 530 kernel driver monitor resolution problem
[Expired for nvidia-graphics-drivers-530 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-530 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-530 in Ubuntu. https://bugs.launchpad.net/bugs/2025585 Title: Nvidia 530 kernel driver monitor resolution problem Status in nvidia-graphics-drivers-530 package in Ubuntu: Expired Bug description: I have managed to install the drivers and nvidia-smi shows output but it does NOT detect my external monitor which used to work with previous version of the driver. Sometimes it is detected by the resolution too small https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-530/+bug/2023946 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2025585/+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 2019968] Re: Add missing feature bits in EPYC-Milan model
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => New ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => New ** Changed in: linux (Ubuntu Mantic) Status: Incomplete => New ** Changed in: qemu (Ubuntu Kinetic) Status: New => Won't Fix -- 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/2019968 Title: Add missing feature bits in EPYC-Milan model Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: New Status in linux source package in Jammy: New Status in qemu source package in Jammy: New Status in linux source package in Kinetic: Won't Fix Status in qemu source package in Kinetic: Won't Fix Status in linux source package in Lunar: New Status in qemu source package in Lunar: New Status in linux source package in Mantic: New Status in qemu source package in Mantic: New Bug description: [Impact] Add the following feature bits for EPYC-Milan model and bump the version. vaes: Vector VAES(ENC|DEC), VAES(ENC|DEC)LAST instruction support vpclmulqdq : Vector VPCLMULQDQ instruction support stibp-always-on : Single Thread Indirect Branch Prediction Mode has enhanced performance and may be left Always on amd-psfd: Predictive Store Forward Disable no-nested-data-bp : Processor ignores nested data breakpoints lfence-always-serializing : LFENCE instruction is always serializing null-sel-clr-base : Null Selector Clears Base. When this bit is set, a null segment load clears the segment base [Test Plan] * First of all we'll (and have in advance) run general regression tests * Qemu shall show to be aware of the new types # qemu-system-x86_64 -cpu ? | grep EPYC-Milan x86 EPYC-Milan (alias configured by machine type) x86 EPYC-Milan-v1 AMD EPYC-Milan Processor x86 EPYC-Milan-v2 AMD EPYC-Milan Processor [Where problems could occur] * There are two areas to look at a) compat behavior on old systems - e.g. libvirt would now detect IBRS on such AMD chips and one might wonder about the change. E.g. compatibility would exist between old-code/new-code/old->new code; but any action (e.g. suspend resume) from new to old code might run into trouble (not supported that way but worth to mention for awareness) b) Migrations between systems - this should be covered by chip versioning but still is worth to mention. Versioning will recognize a formerly started system as v1 and continue to handle it that way. Only new started guests would become v2 and behave the new and improved way. [Other Info] * n/a --- https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg02082.html https://github.com/qemu/qemu/commit/27f03be6f59d04bd5673ba1e1628b2b490f9a9ff.patch This patch depends on the definitions that were added as part of the EPYC-Milan patch: amd-psfd, stibp-always-on: * https://github.com/qemu/qemu/commit/bb039a230e6a7920d71d21fa9afee2653a678c48.patch Add feature bits for CPUID_Fn8021_EAX: * https://github.com/qemu/qemu/commit/b70eec312b185197d639bff689007727e596afd1.patch Kernel patches: https://lkml.kernel.org/lkml/20230124163319.2277355-1-kim.phill...@amd.com/ kvm: Add support for CPUID_8021_EAX * https://github.com/torvalds/linux/commit/8415a74852d7c24795007ee9862d25feb519007c.patch kvm: Add the NO_NESTED_DATA_BP feature * https://github.com/torvalds/linux/commit/a9dc9ec5a1fafc3d2fe7a7b594eefaeaccf89a6b.patch kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf * https://github.com/torvalds/linux/commit/84168ae786f8a15a7eb0f79d34f20b8d261ce2f5.patch kvm: Add the Null Selector Clears Base feature * https://github.com/torvalds/linux/commit/5b909d4ae59aedc711b7a432da021be0e82c95a0.patch kvm: Add the SMM_CTL MSR not present feature https://github.com/torvalds/linux/commit/faabfcb194a8d0686396e3fff6a5b42911f65191.patch And probably this one as well: KVM: Add common feature flag for AMD's PSFD https://github.com/torvalds/linux/commit/3d8f61bf8bcd69bcd397276d53aa18f7ca8347f9.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019968/+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 2019971] Re: Add EPYC-Genoa model
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => New ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => New ** Changed in: linux (Ubuntu Mantic) Status: Incomplete => New ** Changed in: qemu (Ubuntu Kinetic) Status: Triaged => Won't Fix ** Changed in: qemu (Ubuntu Kinetic) Assignee: Sergio Durigan Junior (sergiodj) => (unassigned) -- 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/2019971 Title: Add EPYC-Genoa model Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Triaged Status in linux source package in Jammy: New Status in qemu source package in Jammy: Triaged Status in linux source package in Kinetic: Won't Fix Status in qemu source package in Kinetic: Won't Fix Status in linux source package in Lunar: New Status in qemu source package in Lunar: Triaged Status in linux source package in Mantic: New Status in qemu source package in Mantic: Triaged Bug description: [Impact] * To avoid bugs with newer Hardware and to allow users/admins to control the KVM guests correctly we usually try to backport major CPU- detect/control features back to at least the last LTS (currently jammy) In SRU Terms this is under the second entry in https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases * In this particular case it is about Support for EPYC Genoa chips https://en.wikipedia.org/wiki/Epyc#Fourth_generation_Epyc_(Genoa) [Test Plan] * First of all we'll (and have in advance) run general regression tests * Second you'd want to run this with host-model and host-passthrough on Rome / Milan chips to ensure no case is now falling in to a totally dysfunctional state * Qemu shall show to be aware of the new types # qemu-system-x86_64 -cpu ? | grep EPYC-Genoa x86 EPYC-Genoa (alias configured by machine type) x86 EPYC-Genoa-v1 AMD EPYC-Genoa Processor * Finally migrations between old->new should be checked to work fine. [Where problems could occur] * This kind of "add the new type" usually only s a problem in backward- migratebility which isn't supported anyway. Never the less the areas to look out for is behavior on various AMD EPYC chips. To ensure that old chips won't change in a breaking way (they might detect new features now, but not more) and that new Milan chips are now all detected properly. [Other Info] * This is not the first time new AMD chips need to add their definitions, for example bug 1921880 was similar QEMU added a separate model for EPYC-Genoa in https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg02087.html On the qemu side most bits are already present as far back as jammy. The only things missing are the vnmi and auto-ibrs flag. The lfence-always-serializing, amd-psfd, no-nested-data-bp, null-sel-clr-base are part of the Milan-v2 patch set https://github.com/qemu/qemu/commit/62a798d4bc2c3e767d94670776c77a7df274d7c5.patch https://github.com/qemu/qemu/commit/166b1741884dd4fd7090b753cd7333868457a29b.patch Kernel auto-ibrs et al: https://lkml.kernel.org/lkml/20230124163319.2277355-1-kim.phill...@amd.com/ kvm: Add support for CPUID_8021_EAX * https://github.com/torvalds/linux/commit/8415a74852d7c24795007ee9862d25feb519007c.patch kvm: Add the NO_NESTED_DATA_BP feature * https://github.com/torvalds/linux/commit/a9dc9ec5a1fafc3d2fe7a7b594eefaeaccf89a6b.patch kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf * https://github.com/torvalds/linux/commit/84168ae786f8a15a7eb0f79d34f20b8d261ce2f5.patch kvm: Add the Null Selector Clears Base feature * https://github.com/torvalds/linux/commit/5b909d4ae59aedc711b7a432da021be0e82c95a0.patch kvm: Add the SMM_CTL MSR not present feature https://github.com/torvalds/linux/commit/faabfcb194a8d0686396e3fff6a5b42911f65191.patch x86/cpu: Support AMD Automatic IBRS https://github.com/torvalds/linux/commit/e7862eda309ecfccc36bb5558d937ed3ace07f3f.patch KVM: Add common feature flag for AMD's PSFD https://github.com/torvalds/linux/commit/3d8f61bf8bcd69bcd397276d53aa18f7ca8347f9.patch Add support for virtual NMIs https://github.com/torvalds/linux/commit/4a5fd419952e49ef870e9259d815718062871cc1.patch Please consider adding/backporting these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019971/+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 there. Kernel 6.2.0-31.31 I did sudo apt-get install build-essential git clone https://github.com/Kvalme/uvc.git cd ./uvc/ git checkout 5ea688c make It makes well after that I did sudo rmmod uvcvideo sudo insmod ./uvcvideo.ko But webcam still not working -- 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
[Kernel-packages] [Bug 2026863] Re: zfs-linux SRU build support against hwe kernels
we literary need this for oem kernel in the jammy archive -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2026863 Title: zfs-linux SRU build support against hwe kernels Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: Incomplete Bug description: [ Impact ] * hwe kernels keep on changing * jammy zfs-linux 2.1.5 upstream releases + cherry-picks is quite old, thus a jump to 2.1.12 or 2.2 has potential to break userspace * Instead cherry-pick patches that continue to enable building zfs-dkms against hwe kernels, if one desires to use dkms from the archive, rather than prebuilt modules that all of Ubuntu kernels ship. * the cherry-picks area gainst config/* code (autoconf/m4) and kernel code (module/ & include/), without any changes to userspace tooling or fixes. [ Test Plan ] * verify zfs-dkms module builds from source against v5.15, v5.19, v6.2, v6.3 kernels on jammy * verify existing zsys installs continue to work * verify kernel team zfs tests-suites continue to work with v5.15 kernel [ Where problems could occur ] * majority of diff is in config macros to detect different compatible kernel APIs and ABIs and use an appropriate one. there are changes to uidmap handling for v6.3 kernels, however it is mostly ignored by userspace without intruducing new feature. LXD will need to be double checked, as it may assume this driver version seems to accept uidmap mount options - which it then ignores. * Note this is still at feature parity with Lunar's upload 2.1.9-2ubuntu1.1, despite having partial kernel driver only build compat with v6.3 - as v6.3 kernels are not expected to land in lunar, and will not land in jammy until after mantic release. Mantic already has much newer 2.2.x series zfs-linux. [ Other Info ] * This is similar to previous zfs-linux SRUs we have performed in the past. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2026863/+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 2033931] Re: Lunar update: upstream stable patchset 2023-09-01
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ upstream stable patchset 2023-09-01
+ from git://git.kernel.org/
-upstream stable patchset 2023-09-01
-from git://git.kernel.org/
+ x86/head/64: Switch to KERNEL_CS as soon as new GDT is installed
+ test_firmware: Use kstrtobool() instead of strtobool()
+ cgroup: bpf: use cgroup_lock()/cgroup_unlock() wrappers
+ cgroup: always put cset in cgroup_css_set_put_fork
+ cgroup: fix missing cpus_read_{lock,unlock}() in cgroup_transfer_tasks()
+ qcom: llcc/edac: Fix the base address used for accessing LLCC banks
+ EDAC/qcom: Get rid of hardcoded register offsets
+ ksmbd: validate smb request protocol id
+ of: overlay: Fix missing of_node_put() in error case of
init_overlay_changeset()
+ power: supply: ab8500: Fix external_power_changed race
+ power: supply: sc27xx: Fix external_power_changed race
+ power: supply: bq27xxx: Use mod_delayed_work() instead of cancel() +
schedule()
+ ARM: dts: vexpress: add missing cache properties
+ tools: gpio: fix debounce_period_us output of lsgpio
+ selftests: gpio: gpio-sim: Fix BUG: test FAILED due to recent change
+ power: supply: Ratelimit no data debug output
+ PCI/DPC: Quirk PIO log size for Intel Ice Lake Root Ports
+ platform/x86: asus-wmi: Ignore WMI events with codes 0x7B, 0xC0
+ regulator: Fix error checking for debugfs_create_dir
+ irqchip/gic-v3: Disable pseudo NMIs on Mediatek devices w/ firmware issues
+ irqchip/meson-gpio: Mark OF related data as maybe unused
+ power: supply: Fix logic checking if system is running from battery
+ drm: panel-orientation-quirks: Change Air's quirk to support Air Plus
+ btrfs: scrub: try harder to mark RAID56 block groups read-only
+ btrfs: handle memory allocation failure in btrfs_csum_one_bio
+ ASoC: soc-pcm: test if a BE can be prepared
+ ASoC: Intel: avs: Account for UID of ACPI device
+ ASoC: Intel: avs: Add missing checks on FE startup
+ parisc: Improve cache flushing for PCXL in arch_sync_dma_for_cpu()
+ parisc: Flush gatt writes and adjust gatt mask in parisc_agp_mask_memory()
+ MIPS: unhide PATA_PLATFORM
+ MIPS: Restore Au1300 support
+ MIPS: Alchemy: fix dbdma2
+ mips: Move initrd_start check after initrd address sanitisation.
+ ASoC: cs35l41: Fix default regmap values for some registers
+ ASoC: dwc: move DMA init to snd_soc_dai_driver probe()
+ xen/blkfront: Only check REQ_FUA for writes
+ drm:amd:amdgpu: Fix missing buffer object unlock in failure path
+ io_uring: unlock sqd->lock before sq thread release CPU
+ NVMe: Add MAXIO 1602 to bogus nid list.
+ irqchip/gic: Correctly validate OF quirk descriptors
+ wifi: cfg80211: fix locking in regulatory disconnect
+ wifi: cfg80211: fix double lock bug in reg_wdev_chan_valid()
+ epoll: ep_autoremove_wake_function should use list_del_init_careful
+ ocfs2: fix use-after-free when unmounting read-only filesystem
+ ocfs2: check new file size on fallocate call
+ zswap: do not shrink if cgroup may not zswap
+ nios2: dts: Fix tse_mac "max-frame-size" property
+ nilfs2: fix incomplete buffer cleanup in nilfs_btnode_abort_change_key()
+ nilfs2: fix possible out-of-bounds segment allocation in resize ioctl
+ nilfs2: reject devices with insufficient block count
+ LoongArch: Fix perf event id calculation
+ io_uring/net: save msghdr->msg_control for retries
+ kexec: support purgatories with .text.hot sections
+ x86/purgatory: remove PGO flags
+ riscv/purgatory: remove PGO flags
+ powerpc/purgatory: remove PGO flags
+ btrfs: do not ASSERT() on duplicated global roots
+ btrfs: fix iomap_begin length for nocow writes
+ btrfs: can_nocow_file_extent should pass down args->strict from callers
+ ALSA: usb-audio: Fix broken resume due to UAC3 power state
+ ALSA: usb-audio: Add quirk flag for HEM devices to enable native DSD playback
+ dm thin metadata: check fail_io before using data_sm
+ dm thin: fix issue_discard to pass GFP_NOIO to __blkdev_issue_discard
+ net: ethernet: stmicro: stmmac: fix possible memory leak in __stmmac_open
+ nouveau: fix client work fence deletion race
+ RDMA/uverbs: Restrict usage of privileged
[Kernel-packages] [Bug 2026863] Proposed package upload rejected
An upload of zfs-linux to jammy-proposed has been rejected from the upload queue for the following reason: "no response from uploader to incomplete bug status for >1m". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2026863 Title: zfs-linux SRU build support against hwe kernels Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: Incomplete Bug description: [ Impact ] * hwe kernels keep on changing * jammy zfs-linux 2.1.5 upstream releases + cherry-picks is quite old, thus a jump to 2.1.12 or 2.2 has potential to break userspace * Instead cherry-pick patches that continue to enable building zfs-dkms against hwe kernels, if one desires to use dkms from the archive, rather than prebuilt modules that all of Ubuntu kernels ship. * the cherry-picks area gainst config/* code (autoconf/m4) and kernel code (module/ & include/), without any changes to userspace tooling or fixes. [ Test Plan ] * verify zfs-dkms module builds from source against v5.15, v5.19, v6.2, v6.3 kernels on jammy * verify existing zsys installs continue to work * verify kernel team zfs tests-suites continue to work with v5.15 kernel [ Where problems could occur ] * majority of diff is in config macros to detect different compatible kernel APIs and ABIs and use an appropriate one. there are changes to uidmap handling for v6.3 kernels, however it is mostly ignored by userspace without intruducing new feature. LXD will need to be double checked, as it may assume this driver version seems to accept uidmap mount options - which it then ignores. * Note this is still at feature parity with Lunar's upload 2.1.9-2ubuntu1.1, despite having partial kernel driver only build compat with v6.3 - as v6.3 kernels are not expected to land in lunar, and will not land in jammy until after mantic release. Mantic already has much newer 2.2.x series zfs-linux. [ Other Info ] * This is similar to previous zfs-linux SRUs we have performed in the past. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2026863/+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 2032338] Re: HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)
on the recent 6.2.0-31 all seems fine -- 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/2032338 Title: HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060) Status in linux-firmware package in Ubuntu: New Bug description: $ apt show linux-firmware Package: linux-firmware Version: 20220329.git681281e4-0ubuntu3.17 Priority: optional Section: misc Origin: Ubuntu Maintainer: Ubuntu Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 999 MB Provides: atmel-firmware Recommends: firmware-sof-signed Conflicts: atmel-firmware Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), linux-firmware-snapdragon (<= 1.2-0ubuntu1) Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-restricted-common Download-Size: 254 MB APT-Manual-Installed: yes APT-Sources: http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages Description: Firmware for Linux kernel drivers This package provides firmware used by Linux kernel drivers. N: There are 2 additional records. Please use the '-a' switch to see them. # update-initramfs -u update-initramfs: Generating /boot/initrd.img-6.2.0-26-generic cryptsetup: WARNING: swap: couldn't determine device type, assuming default (plain). cryptsetup: WARNING: Resume target swap uses a key file W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga102/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/NET_img.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/gr/NET_img.bin for module nouveau W: Possible missing firmware
[Kernel-packages] [Bug 2033931] [NEW] Lunar update: upstream stable patchset 2023-09-01
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-09-01 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Lunar) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/2033931 Title: Lunar update: upstream stable patchset 2023-09-01 Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-09-01 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033931/+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 2024935] Re: cpu 2.7x slower on ubuntu server 23.04 riscv64 Nezha/Sipeed images compared to 22.10 on mangopi mq-pro
*** This bug is a duplicate of bug 2021364 ***
https://bugs.launchpad.net/bugs/2021364
Hey, sorry for not noticing before. You're right this was a bug and
should be fixed in the 6.2 kernel in Lunar. It will also be backported
to Jammy soon.
** This bug has been marked a duplicate of bug 2021364
Linux 6.2 fails to reboot with current u-boot-nezha
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-allwinner in Ubuntu.
https://bugs.launchpad.net/bugs/2024935
Title:
cpu 2.7x slower on ubuntu server 23.04 riscv64 Nezha/Sipeed images
compared to 22.10 on mangopi mq-pro
Status in linux-allwinner package in Ubuntu:
New
Bug description:
I think I found a bug/regression with the ubuntu server 23.04 riscv64
Nezha/Sipeed kernels.
Somehow, the CPU speed on my mangopi mq pro seems to have decreased by 2.7x
compared to the 22.10 image.
The allwinner D1 should run at 1Ghz, and execute a single add per cycle.
On 22.10 I was able to confirm that executing `1024*1024*1024` add
instructions took roughly a second, but on 23.04 it took 2.7 seconds (both
fresh installs, with the same code [1]).
There were no resource hungry background processes running, when I
checked top.
I also binary patched the opensbi image afterward, to disable mcountinhibit
for `rdcycle`, and confirmed that even the hardware cycle counter was slower
than 1Ghz. [2]
One second had 410398820 cycles instead of something closer to the expected
1073741824.
On suggestion from the #ubuntu webchat, I also tested adding
`mitigations=off` to the linux cmd options, but that didn't change
anything.
[1]
// test.c
#include
#include
int main(void)
{
for (int i = 0; i < 10; ++i) {
clock_t beg = clock();
extern void foo(void);
foo();
printf("%f\n", (clock() - beg) * 1.0/CLOCKS_PER_SEC);
}
}
// test.S
.text
.global foo
foo:
li t0, (1024*1024*1024/(8*32))
1:
.rept 32
add a1, a1, a0
add a2, a2, a1
add a3, a3, a2
add a4, a4, a3
add a5, a5, a4
add a6, a6, a5
add a7, a7, a6
add a0, a0, a7
.endr
addit0, t0, -1
bnezt0, 1b
ret
$ gcc -Ofast -march=rv64gc test.* && ./a.out
[2] https://github.com/camel-cdr/rvv-d1/#extra-enable-rdcycle
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-5.19.0-1009-allwinner 5.19.0-1009.9
ProcVersionSignature: User Name 5.19.0-1009.9-allwinner 5.19.17
Uname: Linux 5.19.0-1009-allwinner riscv64
ApportVersion: 2.26.1-0ubuntu2
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20230415.2
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Fri Jun 23 20:10:14 2023
ProcCpuinfoMinimal:
processor: 0
hart : 0
isa : rv64imafdc
mmu : sv39
uarch: thead,c906
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=st-256color
XDG_RUNTIME_DIR=
SourcePackage: linux-allwinner
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2024935/+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 1987413] Re: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT
Meanwhile many HWE kernels were published and the current HWE kernel is 6.2.0-31.31~22.04.1. Can you test with this kernel? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux-hwe-5.15 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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
@Giuliano Once again it works, you are awesome, thanks a lot. Kind regards Samer Attrah -- 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 - Board Asset Tag dmi.board.name: Ignis_ADH dmi.board.vendor: ADL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer
[Kernel-packages] [Bug 2033923] Re: latest xububtu jammy daily isos fail to install on asus, lenovo & msi
the zfs dependency in question is systemd-udev-settle. Sep 1 17:49:20 xubuntu udevadm[1064]: systemd-udev-settle.service is deprecated. Please fix zfs-load-module.service, zfs-import-cache.service not to pull it in. (heh) Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: start operation timed out. Terminating. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: State 'stop-sigterm' timed out. Killing. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Killing process 1064 (udevadm) with signal SIGKILL. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Processes still around after SIGKILL. Ignoring. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: State 'final-sigterm' timed out. Killing. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Killing process 1064 (udevadm) with signal SIGKILL. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Processes still around after final SIGKILL. Entering failed mode. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Failed with result 'timeout'. Opening tasks on systemd and zfsutils-linux, since these packages need to fight it out wrt the "deprecation". And opening a task on the kernel, because a udevadm process that doesn't die with SIGKILL means it's hung in the kernel. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-cdimage Status: New => Invalid ** Summary changed: - latest xububtu jammy daily isos fail to install on asus, lenovo & msi + latest xubuntu jammy daily isos fail to install on asus, lenovo & msi -- 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/2033923 Title: latest xubuntu jammy daily isos fail to install on asus, lenovo & msi Status in Ubuntu CD Images: Invalid Status in linux-hwe-6.2 package in Ubuntu: New Status in systemd package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: Hi, I downloaded the latest xubuntu jammy images 20230901 (and previous ones, verified them) On a Mac all went well with a fresh install, however on a Lenovo, Asus, MSI the installer fails... udev startup job hangs and is restarted several times with 3 minutes increments I get several different errors: Dependency failed for Install ZFS kernel module Dependency failed for Import ZFS,... Failing start job without limit! Load Kernel Module efi_pstore Thank you for sorting this out Kind regards Otto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2033923/+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
@Samer Problem 1: /bin/sh: 1: pahole: not found solution to problem 1: you need to install sudo apt install dwarves (dwarves will also install pahole) Problem 2: [Makefile:1943: modules] Error 2 Solution (possibile) to problem2 : DELETE (please DO delete !) - all the files inux-hwe-6.2_6.2.0-* - AS WELL AS the DIRECTORY linux-hwe-6.2-6.2.0 the first time you run make, it (the make program) changes some makefile inside the dirtree so that the configuration is not “vanilla” as we need 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/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
[Kernel-packages] [Bug 2032963] Re: NBS clean up in focal-proposed for wrong variant
$ rmadison -s focal-proposed linux-ibm-lts-20.04 linux-ibm-lts-20.04 | 5.4.0.1056.85 | focal-proposed | amd64 $ It looks like the last request is superseded: ** Changed in: linux-meta-ibm-5.15 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-ibm-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2032963 Title: NBS clean up in focal-proposed for wrong variant Status in linux-meta-ibm-5.15 package in Ubuntu: Fix Released Bug description: # apt-cache policy linux-ibm-lts-20.04 linux-ibm-lts-20.04: Installed: (none) Candidate: 5.15.0.1035.38~20.04.6 Version table: 5.15.0.1035.38~20.04.6 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 5.4.0.1053.79 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages -lts-20.04 variant was incorrectly added on the linux-meta-ibm-5.15 when it was supposed to be added on linux-meta-ibm package only. this package did not go out of proposed, but we require NBS cleanup removal to roll back linux-ibm-lts-20.04 to 5.4.0. the errours package was already dropped in the 20.04.7 upload of linux-meta-ibm-5.15 which has otherwise migrated. Dear archive admins please drop this binary package: $ ./remove-package -A ubuntu -s focal-proposed -a amd64 --binary -m "NBS cleanup of incorrect variant, which will be moved back to src:linux-meta-ibm" linux-ibm-lts-20.04 -e 5.15.0.1035.38~20.04.6 Removing packages from focal-proposed: linux-ibm-lts-20.04 5.15.0.1035.38~20.04.6 in focal amd64 Comment: NBS cleanup of incorrect variant, which will be moved back to src:linux-meta-ibm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-ibm-5.15/+bug/2032963/+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 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
Same bug. https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe-6.2/+bug/2030673 Set "pcie_aspm=off", updated Grub, rebooted. $ sudo dmesg | grep -i "PCIe ASPM" [0.042017] PCIe ASPM is disabled I will watch. -- 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
[Kernel-packages] [Bug 2030673] Re: Linux 6.2.0-26-generic, network crashes intermittently.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031537 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2030673 Title: Linux 6.2.0-26-generic, network crashes intermittently. Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: After updating the kernel to version 6.2, the network drops once a day. Description: Ubuntu 22.04.3 LTS Release: 22.04 Linux MyHomeAssistant 6.2.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux авг 07 12:32:25 MyHomeAssistant kernel: [ cut here ] авг 07 12:32:25 MyHomeAssistant kernel: NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out авг 07 12:32:25 MyHomeAssistant kernel: WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x21f/0x230 авг 07 12:32:25 MyHomeAssistant kernel: Modules linked in: ntfs3 rfcomm tls xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc snd_hda_codec_hdmi cmac algif_hash algif_skcipher af_alg bnep overlay snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation binfmt_misc soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus nls_iso8859_1 snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel x86_pkg_temp_thermal mei_pxp mei_hdcp intel_rapl_msr snd_intel_dspcfg intel_powerclamp snd_intel_sdw_acpi i915 snd_hda_codec kvm_intel snd_usb_audio iwlmvm snd_hda_core snd_usbmidi_lib kvm mc snd_hwdep drm_buddy btusb mac80211 snd_pcm irqbypass ttm snd_seq_midi btrtl snd_seq_midi_event libarc4 btbcm авг 07 12:32:25 MyHomeAssistant kernel: crct10dif_pclmul snd_rawmidi drm_display_helper btintel polyval_generic snd_seq ghash_clmulni_intel cec sha512_ssse3 rc_core iwlwifi snd_seq_device aesni_intel btmtk processor_thermal_device_pci_legacy snd_timer drm_kms_helper processor_thermal_device crypto_simd processor_thermal_rfim snd i2c_algo_bit cryptd processor_thermal_mbox syscopyarea joydev input_leds bluetooth intel_cstate cdc_acm sysfillrect processor_thermal_rapl cmdlinepart sysimgblt cfg80211 spi_nor soundcore ecdh_generic intel_rapl_common 8250_dw mei_me ee1004 wmi_bmof ecc mtd int340x_thermal_zone intel_soc_dts_iosf mei acpi_pad mac_hid acpi_tad sch_fq_codel coretemp msr parport_pc ppdev lp parport ramoops pstore_blk drm reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 hid_generic usbhid uas hid usb_storage spi_pxa2xx_platform dw_dmac dw_dmac_core crc32_pclmul spi_intel_pci i2c_i801 xhci_pci ahci r8169 spi_intel i2c_smbus intel_lpss_pci intel_lpss realtek libahci idma64 xhci_pci_renesas video авг 07 12:32:25 MyHomeAssistant kernel: wmi pinctrl_jasperlake авг 07 12:32:25 MyHomeAssistant kernel: CPU: 3 PID: 0 Comm: swapper/3 Not tainted 6.2.0-26-generic #26~22.04.1-Ubuntu авг 07 12:32:25 MyHomeAssistant kernel: Hardware name: AZW U59/U59, BIOS JTKT001 05/05/2022 авг 07 12:32:25 MyHomeAssistant kernel: RIP: 0010:dev_watchdog+0x21f/0x230 авг 07 12:32:25 MyHomeAssistant kernel: Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 f5 a9 78 01 01 e8 c6 ff f7 ff 44 89 f1 4c 89 e6 48 c7 c7 08 30 c4 a7 48 89 c2 e8 31 0b 2c ff <0f> 0b e9 22 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 авг 07 12:32:25 MyHomeAssistant kernel: RSP: 0018:99cf001dce70 EFLAGS: 00010246 авг 07 12:32:25 MyHomeAssistant kernel: RAX: RBX: 8e93816704c8 RCX: авг 07 12:32:25 MyHomeAssistant kernel: RDX: RSI: RDI: авг 07 12:32:25 MyHomeAssistant kernel: RBP: 99cf001dce98 R08: R09: авг 07 12:32:25 MyHomeAssistant kernel: R10: R11: R12: 8e938167 авг 07 12:32:25 MyHomeAssistant kernel: R13: 8e938167041c R14: R15: авг 07 12:32:25 MyHomeAssistant kernel: FS: () GS:8e96f018() knlGS: авг 07 12:32:25 MyHomeAssistant kernel: CS: 0010 DS: ES: CR0: 80050033 авг 07 12:32:25 MyHomeAssistant kernel: CR2: 564d214f12cc CR3: 0002c601 CR4: 00350ee0 авг 07 12:32:25 MyHomeAssistant kernel: Call Trace: авг 07 12:32:25 MyHomeAssistant kernel: авг 07 12:32:25 MyHomeAssistant kernel: ? __pfx_dev_watchdog+0x10/0x10 авг 07 12:32:25 MyHomeAssistant kernel: call_timer_fn+0x29/0x160 авг 07 12:32:25 MyHomeAssistant kernel: ? __pfx_dev_watchdog+0x10/0x10 авг 07 12:32:25 MyHomeAssistant kernel: __run_timers.part.0+0x1fb/0x2b0
[Kernel-packages] [Bug 2031969] Re: Ubuntu 23.04: Suspend & Power off
** This bug is no longer a duplicate of bug 2031352 Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen -- 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/2031969 Title: Ubuntu 23.04: Suspend & Power off Status in linux package in Ubuntu: Confirmed Bug description: Since update to version 23.04 I am facing several problems related to system suspend and shutdown on a HP Envy 15 notebook (2016). The system refuses to wake up from standby mode, especially if it has run for a longer time. Screen is black, no response to keyboard or trackpad actions, Power button led is on. The only way out of here is a long press on power button. Another problem with this and I think it's kind of related. If you want to shut down the computer after a long runtime, the machine won't power off. In the logs you can see the steps for shutting down the OS but in the end the machine stays powered on. The power led is on, screen is black, no response to keyboard or trackpad actions. System has to be powered off by a long press on the power button. Ubuntu 6.2.0-27.28-generic 6.2.15 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom2051 F wireplumber /dev/snd/seq:tom2037 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 19 16:01:07 2023 InstallationDate: Installed on 2018-07-01 (1875 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias: dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY Notebook dmi.product.sku: Z6J78EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969/+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 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
I've builtt a test kernel with the above patch: https://kernel.ubuntu.com/~juergh/lp2031352/ Can someone give it a try, please? Note that the kernel is not signed so you need to disable SecureBoot to be able to boot it. Install linux- image-unsigned, linux-modules and maybe linux-modules-extra. -- 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 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Lunar) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Lunar) ** No longer affects: linux-hwe-6.2 (Ubuntu Lunar) ** Changed in: linux (Ubuntu Lunar) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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 2033386] Re: 6.2.0-31 SMB1 NAS won't mount
Hi Alex. It appears older NTLM support was dropped in Linux Kernel, so SMB version 1.0 does not work for cifs mount. SMB version 2.0 still works though. See https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c cifs: remove support for NTLM and weaker authentication algorithms for SMB1. This removes the dependency to DES. Signed-off-by: Ronnie Sahlberg Signed-off-by: Steve French See comment from jwunder in bug report 2031246: "I've managed to get an updated level of code on the Buffalo NAS and with that and 'cifs credentials=XXX,vers=2.0,iocharset=utf8,dir_mode=0777,file_mode=077,sec=ntlmssp 0 in fstab am able to now access my disks." -- 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/2033386 Title: 6.2.0-31 SMB1 NAS won't mount Status in linux package in Ubuntu: Confirmed Bug description: I can't connect to my old NAS SMB vers=1.0 using cifs via fstab, everything works in kernel 6.2.0-26 and I have to roll back. mount.cifs(8) -22 invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033386/+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 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
Without digging too deep, maybe this: https://lore.kernel.org/lkml/cacavsv6-aj4ehg7pnuwgsncn0cyro8gwd3nr8pu32a-wxso...@mail.gmail.com/T/ -- 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-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 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-hwe-6.2/+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 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen (nouveau driver crash)
** Summary changed: - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen + Ubuntu 22.04.3 LTS stuck on power-off/reboot screen (nouveau driver crash) ** Summary changed: - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen (nouveau driver crash) + Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen -- 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-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 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-hwe-6.2/+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 2033267] Re: Nouveau driver crash with 6.2
*** This bug is a duplicate of bug 2031352 *** https://bugs.launchpad.net/bugs/2031352 See bug 2031352 for more kernel traces. ** This bug has been marked a duplicate of bug 2031352 Ubuntu 22.04.3 LTS stuck on power-off/reboot screen -- 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/2033267 Title: Nouveau driver crash with 6.2 Status in linux package in Ubuntu: Confirmed Bug description: Since 7th of august 2023 after upgrading my system (apt update; apt upgrade) I cannot shutdown my HP Zbook Studio G9 laptop. It hangs forever. The suspend mode is also not working anymore since then, apparently it goes in suspend mode but I can't resume it. The workaround is to hard power it down by pressing 10 seconds on the power button. It works fine until the 7th of august where I update it. Note that we are several people using the same hardware and almost the same installation (using ansible to manage the installation) that have the exact same issue. Here are my HW infos: HW Model: HP HP ZBook Studio 16 inch G9 Mobile Workstation PC Processor: 12th Gen Intel® Core™ i7-12800H × 20 Graphics: Mesa Intel® Graphics (ADL GT2) OS: Ubuntu 22.04.3 LTS 64bits GNOME version: 42.9 Windows System: x11 Description: Ubuntu 22.04.3 LTS Release: 22.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ltshb 3644 F pulseaudio /dev/snd/controlC0: ltshb 3644 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-06 (82 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP ZBook Studio 16 inch G9 Mobile Workstation PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-26-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: jammy Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/21/2023 dmi.bios.release: 5.20 dmi.bios.vendor: HP dmi.bios.version: U99 Ver. 01.05.20 dmi.board.name: 89C3 dmi.board.vendor: HP dmi.board.version: KBC Version 10.5E.50 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 16.94 dmi.modalias: dmi:bvnHP:bvrU99Ver.01.05.20:bd02/21/2023:br5.20:efr16.94:svnHP:pnHPZBookStudio16inchG9MobileWorkstationPC:pvr:rvnHP:rn89C3:rvrKBCVersion10.5E.50:cvnHP:ct10:cvr:sku4Z8Q4AV: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Studio 16 inch G9 Mobile Workstation PC dmi.product.sku: 4Z8Q4AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033267/+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 2033267] Re: Suspend and shutdown not working on HP Zbook Studio G9
*** This bug is a duplicate of bug 2031352 *** https://bugs.launchpad.net/bugs/2031352 août 28 06:24:20 ltshb-zbook kernel: CR2: ffd6 CR3: 00010528e000 CR4: 00750ee0 août 28 06:24:20 ltshb-zbook kernel: CS: 0010 DS: ES: CR0: 80050033 août 28 06:24:20 ltshb-zbook kernel: FS: 7f07bccca8c0() GS:8b5f777c() knlGS: août 28 06:24:20 ltshb-zbook kernel: R13: R14: 8b5825fefcb0 R15: 8b5825fefc08 août 28 06:24:20 ltshb-zbook kernel: R10: R11: R12: 8b5825fefcc8 août 28 06:24:20 ltshb-zbook kernel: RBP: aa4e00f0f618 R08: 8b5825fefcb0 R09: août 28 06:24:20 ltshb-zbook kernel: RDX: 8b5825fefcd8 RSI: 8b5825fefcc8 RDI: 8b5825fefc00 août 28 06:24:20 ltshb-zbook kernel: RAX: RBX: 8b5825fefcb0 RCX: août 28 06:24:20 ltshb-zbook kernel: RSP: 0018:aa4e00f0f5b8 EFLAGS: 00010246 août 28 06:24:20 ltshb-zbook kernel: Code: Unable to access opcode bytes at 0xffd6. août 28 06:24:20 ltshb-zbook kernel: RIP: 0010:0x0 août 28 06:24:20 ltshb-zbook kernel: ---[ end trace ]--- août 28 06:24:20 ltshb-zbook kernel: CR2: août 28 06:24:20 ltshb-zbook kernel: Modules linked in: nouveau(+) i915(+) mxm_wmi drm_buddy drm_ttm_helper i2c_algo_bit ttm drm_display_helper cec crct10dif_pclmul rc_core crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel drm_kms_helper hid_generic sha512_ssse3 aesni_intel syscopyarea spi_pxa2xx_platform sysfillrect sysimgblt dw_dmac dw_dmac_core rtsx_pci_sdmmc crypto_simd nvme cryptd drm thunderbolt ucsi_acpi intel_lpss_pci intel_ish_ipc(+) i2c_i801 nvme_core spi_intel_pci rtsx_pci xhci_pci typec_ucsi intel_lpss spi_intel i2c_smbus intel_ishtp idma64 xhci_pci_renesas typec nvme_common i2c_hid_acpi i2c_hid hid video wmi pinctrl_tigerlake août 28 06:24:20 ltshb-zbook kernel: août 28 06:24:20 ltshb-zbook kernel: R13: 55e2d968be20 R14: 55e2d968c2e0 R15: 55e2d968dc30 août 28 06:24:20 ltshb-zbook kernel: R10: 0013 R11: 0246 R12: 7f07bd559441 août 28 06:24:20 ltshb-zbook kernel: RBP: 0002 R08: R09: 0002 août 28 06:24:20 ltshb-zbook kernel: RDX: RSI: 7f07bd559441 RDI: 0013 août 28 06:24:20 ltshb-zbook kernel: RAX: ffda RBX: 55e2d968c320 RCX: 7f07bd3c2a3d août 28 06:24:20 ltshb-zbook kernel: RSP: 002b:7ffcf95bb808 EFLAGS: 0246 ORIG_RAX: 0139 août 28 06:24:20 ltshb-zbook kernel: Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 août 28 06:24:20 ltshb-zbook kernel: RIP: 0033:0x7f07bd3c2a3d août 28 06:24:20 ltshb-zbook kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc août 28 06:24:20 ltshb-zbook kernel: ? do_syscall_64+0x69/0x90 août 28 06:24:20 ltshb-zbook kernel: ? do_syscall_64+0x69/0x90 août 28 06:24:20 ltshb-zbook kernel: ? syscall_exit_to_user_mode+0x2a/0x50 août 28 06:24:20 ltshb-zbook kernel: ? exit_to_user_mode_prepare+0x3b/0xd0 août 28 06:24:20 ltshb-zbook kernel: ? syscall_exit_to_user_mode+0x2a/0x50 août 28 06:24:20 ltshb-zbook kernel: ? ksys_mmap_pgoff+0x123/0x270 août 28 06:24:20 ltshb-zbook kernel: ? vm_mmap_pgoff+0x102/0x180 août 28 06:24:20 ltshb-zbook kernel: do_syscall_64+0x59/0x90 août 28 06:24:20 ltshb-zbook kernel: __x64_sys_finit_module+0x18/0x30 août 28 06:24:20 ltshb-zbook kernel: ? __do_sys_finit_module+0xcc/0x150 août 28 06:24:20 ltshb-zbook kernel: __do_sys_finit_module+0xcc/0x150 août 28 06:24:20 ltshb-zbook kernel: ? kernel_read_file+0x25c/0x2b0 août 28 06:24:20 ltshb-zbook kernel: load_module+0xb96/0xd60 août 28 06:24:20 ltshb-zbook kernel: do_init_module+0x52/0x240 août 28 06:24:20 ltshb-zbook kernel: ? kmalloc_trace+0x2a/0xb0 août 28 06:24:20 ltshb-zbook kernel: do_one_initcall+0x46/0x240 août 28 06:24:20 ltshb-zbook kernel: nouveau_drm_init+0x177/0xff0 [nouveau] août 28 06:24:20 ltshb-zbook kernel: __pci_register_driver+0x68/0x80 août 28 06:24:20 ltshb-zbook kernel: ? __pfx_init_module+0x10/0x10 [nouveau] août 28 06:24:20 ltshb-zbook kernel: driver_register+0x83/0x160 août 28 06:24:20 ltshb-zbook kernel: bus_add_driver+0x152/0x250 août 28 06:24:20 ltshb-zbook kernel: driver_attach+0x1e/0x30 août 28 06:24:20 ltshb-zbook kernel: bus_for_each_dev+0x80/0xe0 août 28 06:24:20 ltshb-zbook kernel: ? __pfx___driver_attach+0x10/0x10 août 28 06:24:20 ltshb-zbook kernel: __driver_attach+0x10f/0x220 août 28 06:24:20 ltshb-zbook kernel: driver_probe_device+0x23/0xd0 août 28 06:24:20 ltshb-zbook kernel: __driver_probe_device+0x8a/0x1a0 août 28 06:24:20 ltshb-zbook kernel: really_probe+0x1ea/0x450 août 28 06:24:20 ltshb-zbook
[Kernel-packages] [Bug 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
-- 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-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 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-hwe-6.2/+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 2033732] Re: SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Confirmed -- 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/2033732 Title: SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31) Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: I was running Ubuntu 22.04.3 on kernel version 5.15.0-82-generic, and I installed package linux-generic-hwe-22.04 in order to upgrade to kernel version 6.2.0-31. That upgrade broke the SMB version 1 protocol. I know that it is an old, deprecated protocol, but I still have to access some legacy systems and devices in a local network. This breakage has been discussed on the Internet. It is a Linux kernel regression. This is the commit that fixes it. It is a very small change: 2f6f19c7aaad "cifs: fix regression in very old smb1 mounts" https://github.com/torvalds/linux/commit/2f6f19c7aaad5005dc75298a413eb0243c5d312d I am no Linux kernel expert. Could you please backport that fix to the kernel versions that linux-generic-hwe-22.04 installs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2033732/+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 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
@steffel et al. I believe there are two different problems here. 1) A generic reboot/suspend/halt issue. When powering off or suspending, the machine doesn't fully turn off. The fan is still spinning and it can only be revived by pulling the plug. This is what this bug is about. 2) A similarly looking problem but caused (?) by a nouveau issue as seen in comment #18. I think this is a different issues. Please open a new ticket for that. -- 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: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen 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 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-hwe-6.2/+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
@Giuliano thanks so much for your effort. but, I deleted the old linux-generic-5.*** directory from my home directory, and now I only have linux-hwe-6.2-6.2.0 also, run the command sudo cp /sys/kernel/btf/vmlinux /usr/lib/modules/$(uname -r)/build/ before running the script. and it still gives the same error, you can find it in the file attached with a few different lines. Kind regards Samer Attrah ** Attachment added: "output.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000947/+attachment/5697228/+files/output.txt -- 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
[Kernel-packages] [Bug 1853306] Re: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part
--- Comment From boris.m...@de.ibm.com 2023-09-01 10:31 EDT--- As this has been released to jammy -updates, we can close the bug. Thanks everyone for all your work. ==> Changing the status to "CLOSED" ** Tags removed: verification-needed-jammy-linux-azure -- 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/1853306 Title: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [ Impact ] * Currently the PCI passthrough implementation for s390x is based on intercepting PCI I/O instructions, which leads to a reduced I/O performance compared to the execution of PCI instructions directly in LPAR. * Hence users may face I/O bottlenecks when using PCI devices in passthrough mode based on the current implementation. * For avoiding this and to improve performance, the interpretive execution of the PCI store and PCI load instructions get enabled. * A further improvement is achieved by enabling the Adapter-Event-Notification Interpretation (AENI). * Since LTS releases are the main focus for stable and long running KVM workloads, it is highly desired to get this backported to the jammy kernel (and because the next LTS is still some time away). [ Test Plan ] * Hardware used: z14 or greater LPAR, PCI-attached devices (RoCE VFs, ISM devices, NVMe drive) * Setup: Both the kernel and QEMU features are needed for the feature to function (an upstream QEMU can be used to verify the kernel early), and the facility is only avaialble on z14 or newer. When any of those pieces is missing, the interpretation facility will not be used. When both the kernel and QEMU features are included in their respective packages, and running in an LPAR on a z14 or newer machine, this feature will be enabled automatically. Existing supported devices should behave as before with no changes required by an end-user (e.g. no changes to libvirt domain definitions) -- but will now make use of the interpretation facility. Additionally, ISM devices will now be eligible for vfio-pci passthrough (where before QEMU would exit on error if attempting to provide an ISM device for vfio-pci passthrough, preventing the guest from starting) * Testing will include the following scenarios, repeated each for RoCE, ISM and NVMe: 1) Testing of basic device passthrough (create a VM with a vfio-pci device as part of the libvirt domain definition, passing through a RoCE VF, an ISM device, or an NVMe drive. Verify that the device is available in the guest and functioning) 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device, virsh detach-device to remove the device from the running guest, verify the device is removed from the guest, then virsh attach-device to hotplug the device to the guest again, verify the device functions in the guest) 3) Host power off testing: Power off the device from the host, verify that the device is unplugged from the guest as part of the poweroff 4) Guest power off testing: Power off the device from within the guest, verify that the device is unusuable in the guest, power the device back on within the guest and verify that the device is once again usable. 5) Guest reboot testing: (create a VM with a vfio-pci device, verify the device is in working condition, reboot the guest, verify that the device is still usable after reboot) Testing will include the following scenarios specifically for ISM devices: 1) Testing of SMC-D v1 fallback: Using 2 ISM devices on the same VCHID that share a PNETID, create 2 guests and pass one ISM device via vfio-pci device to each guest. Establish TCP connectivity between the 2 guests using the libvirt default network, and then use smc_run (https://manpages.ubuntu.com/manpages/jammy/man8/smc_run.8.html) to run an iperf workload between the 2 guests (will include both short workloads and longer-running workloads). Verify that SMC-D transfer was used between the guests instead of TCP via 'smcd stats' (https://manpages.ubuntu.com/manpages/jammy/man8/smcd.8.html) 2) Testing of SMC-D v2: Same as above, but using 2 ISM devices on the same VCHID that have no PNETID specified Testing will include the following scenarios specifically for RoCE devices: 1) Ping testing: Using 2 RoCE VFs that share a common network,
[Kernel-packages] [Bug 2029917] Re: [Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
Seen on b/aws-5.4 with version 5.4.0-1109 during cycle 2023.08.07.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2029917
Title:
[Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers
triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on
AWS cloud c3.xlarge
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Bionic:
Confirmed
Status in linux-aws source package in Focal:
Confirmed
Bug description:
Issue found with 5.4.0-1107.115~18.04.1 Bionic AWS and 5.4.0-1107.115
Focal AWS kernel, on c3.xlarge instance only.
There is no output from the test itself (looks like it has crashed):
START ubuntu_ltp_controllers.cpuset_hotplug
ubuntu_ltp_controllers.cpuset_hotplug timestamp=1689920544timeout=4500
localtime=Jul 21 06:22:24
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_controllers.cpuset_hotplug',
'ubuntu_ltp_controllers.cpuset_hotplug')
Waiting for pid 925631 for 4500 seconds
System python is too old, crash handling disabled
(nothing after this point)
But from the console log you will see a kernel BUG and kernel panic:
[ 3451.829941] kernel BUG at
/build/linux-aws-5.4-I38rpz/linux-aws-5.4-5.4.0/arch/x86/xen/spinlock.c:62!
[ 3451.833383] invalid opcode: [#1] SMP PTI
[ 3451.835146] CPU: 1 PID: 14 Comm: cpuhp/1 Tainted: G C
5.4.0-1107-aws #115~18.04.1-Ubuntu
[ 3451.838679] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006
[ 3451.840965] RIP: 0010:dummy_handler+0x4/0x10
[ 3451.842675] Code: 8b 75 e4 74 d6 44 89 e7 e8 39 89 61 00 eb d6 44 89 e7 e8
af ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66
2e 0f 1f 84 00 00 00 00 00 80 3d 69 d0 9f 01 00 75 02 f3
[ 3451.849042] RSP: :b54bee38 EFLAGS: 00010046
[ 3451.851021] RAX: 92c2e3d0 RBX: 003b RCX:
[ 3451.853509] RDX: 00400e00 RSI: RDI:
003b
[ 3451.855996] RBP: b54bee38 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.858435] R10: R11: 94664da8 R12:
[ 3451.860896] R13: R14: R15:
8a9de6583200
[ 3451.863313] FS: () GS:8a9de804()
knlGS:
[ 3451.899246] CS: 0010 DS: ES: CR0: 80050033
[ 3451.901338] CR2: CR3: 2040a001 CR4:
001606e0
[ 3451.903757] DR0: DR1: DR2:
[ 3451.906184] DR3: DR6: fffe0ff0 DR7:
0400
[ 3451.908623] Call Trace:
[ 3451.909869]
[ 3451.911014] __handle_irq_event_percpu+0x44/0x1a0
[ 3451.912818] handle_irq_event_percpu+0x32/0x80
[ 3451.914578] handle_percpu_irq+0x3d/0x60
[ 3451.916198] generic_handle_irq+0x28/0x40
[ 3451.917834] handle_irq_for_port+0x8f/0xe0
[ 3451.919493] evtchn_2l_handle_events+0x157/0x270
[ 3451.921298] __xen_evtchn_do_upcall+0x76/0xe0
[ 3451.923046] xen_evtchn_do_upcall+0x2b/0x40
[ 3451.924742] xen_hvm_callback_vector+0xf/0x20
[ 3451.926484]
[ 3451.927632] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20
[ 3451.929674] Code: e8 a0 3d 64 ff 4c 29 e0 4c 39 f0 76 cf 80 0b 08 eb 8a 90
90 90 0f 1f 44 00 00 55 48 89 e5 e8 d6 ad 66 ff 66 90 48 89 f7 57 9d <0f> 1f 44
00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07
[ 3451.935996] RSP: :b54b000fbcf8 EFLAGS: 0246 ORIG_RAX:
ff0c
[ 3451.939023] RAX: 0001 RBX: 8a9de6583200 RCX:
0002cc00
[ 3451.941475] RDX: 0001 RSI: 0246 RDI:
0246
[ 3451.943948] RBP: b54b000fbcf8 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.946382] R10: R11: 0246 R12:
003b
[ 3451.948849] R13: R14: 8a9d8e75c600 R15:
8a9d8e75c6a4
[ 3451.951297] __setup_irq+0x456/0x760
[ 3451.952850] ? kmem_cache_alloc_trace+0x170/0x230
[ 3451.954661] request_threaded_irq+0xfb/0x160
[ 3451.956376] bind_ipi_to_irqhandler+0xba/0x1c0
[ 3451.958113] ? xen_qlock_wait+0x90/0x90
[ 3451.959723] ? snr_uncore_mmio_init+0x20/0x20
[ 3451.961445] xen_init_lock_cpu+0x78/0xd0
[ 3451.963057] ? snr_uncore_mmio_init+0x20/0x20
[ 3451.964810] xen_cpu_up_online+0xe/0x20
[ 3451.966415] cpuhp_invoke_callback+0x8a/0x580
[ 3451.968144] cpuhp_thread_fun+0xb8/0x120
[ 3451.969760] smpboot_thread_fn+0xfc/0x170
[ 3451.971400] kthread+0x121/0x140
[ 3451.972855] ? sort_range+0x30/0x30
[ 3451.974378] ? kthread_park+0x90/0x90
[ 3451.975929] ret_from_fork+0x35/0x40
[ 3451.977454] Modules linked in: exfat(C) ufs qnx4
[Kernel-packages] [Bug 2031093] Re: libgnutls report "trap invalid opcode" when trying to install packages over https
** Tags removed: verification-needed-focal-linux ** Tags added: verification-done-focal-linux -- 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/2031093 Title: libgnutls report "trap invalid opcode" when trying to install packages over https Status in ubuntu-kernel-tests: New Status in gnutls28 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in gnutls28 source package in Focal: Confirmed Status in linux source package in Focal: Fix Released Status in gnutls28 source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Released Status in gnutls28 source package in Lunar: Confirmed Status in linux source package in Lunar: Fix Released Bug description: [Impact] When booting linux with Gather Data Sampling mitigations without updated microcode on an affected CPU, AVX will be disabled. This will cause programs connecting to https using gnutls on Jammy to break, including apt and git. [Test case] git clone https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] Works fine with the mitigation disabled by default. [Potential regressions] Users booting on affected parts without microcode updates will be subject to Gather Data Sampling attacks (which can be done by local untrusted attackers), which may leak confidential data, including keys. - When trying to install linux-libc-dev on Oracle BM.Standard2.52 (seems to be the only affected instance) with Jammy 5.15.0-81-generic, it will get interrupted with: E: Method https has died unexpectedly! E: Sub-process https received signal 4. $ sudo apt install linux-libc-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-libc-dev 0 upgraded, 1 newly installed, 0 to remove and 54 not upgraded. Need to get 1353 kB of archives. After this operation, 6943 kB of additional disk space will be used. E: Method https has died unexpectedly! E: Sub-process https received signal 4. From dmesg you will see: [ 1078.750067] traps: https[4572] trap invalid opcode ip:7f3c1e6316be sp:7ffea26b61c0 error:0 in libgnutls.so.30.31.0[7f3c1e50f000+129000] Also, git clone is not working as well. $ git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] libgnutls30 version:3.7.3-4ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031093/+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 2029917] Re: [Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-aws (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2029917
Title:
[Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers
triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on
AWS cloud c3.xlarge
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Bionic:
Confirmed
Status in linux-aws source package in Focal:
Confirmed
Bug description:
Issue found with 5.4.0-1107.115~18.04.1 Bionic AWS and 5.4.0-1107.115
Focal AWS kernel, on c3.xlarge instance only.
There is no output from the test itself (looks like it has crashed):
START ubuntu_ltp_controllers.cpuset_hotplug
ubuntu_ltp_controllers.cpuset_hotplug timestamp=1689920544timeout=4500
localtime=Jul 21 06:22:24
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_controllers.cpuset_hotplug',
'ubuntu_ltp_controllers.cpuset_hotplug')
Waiting for pid 925631 for 4500 seconds
System python is too old, crash handling disabled
(nothing after this point)
But from the console log you will see a kernel BUG and kernel panic:
[ 3451.829941] kernel BUG at
/build/linux-aws-5.4-I38rpz/linux-aws-5.4-5.4.0/arch/x86/xen/spinlock.c:62!
[ 3451.833383] invalid opcode: [#1] SMP PTI
[ 3451.835146] CPU: 1 PID: 14 Comm: cpuhp/1 Tainted: G C
5.4.0-1107-aws #115~18.04.1-Ubuntu
[ 3451.838679] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006
[ 3451.840965] RIP: 0010:dummy_handler+0x4/0x10
[ 3451.842675] Code: 8b 75 e4 74 d6 44 89 e7 e8 39 89 61 00 eb d6 44 89 e7 e8
af ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66
2e 0f 1f 84 00 00 00 00 00 80 3d 69 d0 9f 01 00 75 02 f3
[ 3451.849042] RSP: :b54bee38 EFLAGS: 00010046
[ 3451.851021] RAX: 92c2e3d0 RBX: 003b RCX:
[ 3451.853509] RDX: 00400e00 RSI: RDI:
003b
[ 3451.855996] RBP: b54bee38 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.858435] R10: R11: 94664da8 R12:
[ 3451.860896] R13: R14: R15:
8a9de6583200
[ 3451.863313] FS: () GS:8a9de804()
knlGS:
[ 3451.899246] CS: 0010 DS: ES: CR0: 80050033
[ 3451.901338] CR2: CR3: 2040a001 CR4:
001606e0
[ 3451.903757] DR0: DR1: DR2:
[ 3451.906184] DR3: DR6: fffe0ff0 DR7:
0400
[ 3451.908623] Call Trace:
[ 3451.909869]
[ 3451.911014] __handle_irq_event_percpu+0x44/0x1a0
[ 3451.912818] handle_irq_event_percpu+0x32/0x80
[ 3451.914578] handle_percpu_irq+0x3d/0x60
[ 3451.916198] generic_handle_irq+0x28/0x40
[ 3451.917834] handle_irq_for_port+0x8f/0xe0
[ 3451.919493] evtchn_2l_handle_events+0x157/0x270
[ 3451.921298] __xen_evtchn_do_upcall+0x76/0xe0
[ 3451.923046] xen_evtchn_do_upcall+0x2b/0x40
[ 3451.924742] xen_hvm_callback_vector+0xf/0x20
[ 3451.926484]
[ 3451.927632] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20
[ 3451.929674] Code: e8 a0 3d 64 ff 4c 29 e0 4c 39 f0 76 cf 80 0b 08 eb 8a 90
90 90 0f 1f 44 00 00 55 48 89 e5 e8 d6 ad 66 ff 66 90 48 89 f7 57 9d <0f> 1f 44
00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07
[ 3451.935996] RSP: :b54b000fbcf8 EFLAGS: 0246 ORIG_RAX:
ff0c
[ 3451.939023] RAX: 0001 RBX: 8a9de6583200 RCX:
0002cc00
[ 3451.941475] RDX: 0001 RSI: 0246 RDI:
0246
[ 3451.943948] RBP: b54b000fbcf8 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.946382] R10: R11: 0246 R12:
003b
[ 3451.948849] R13: R14: 8a9d8e75c600 R15:
8a9d8e75c6a4
[ 3451.951297] __setup_irq+0x456/0x760
[ 3451.952850] ? kmem_cache_alloc_trace+0x170/0x230
[ 3451.954661] request_threaded_irq+0xfb/0x160
[ 3451.956376] bind_ipi_to_irqhandler+0xba/0x1c0
[ 3451.958113] ? xen_qlock_wait+0x90/0x90
[ 3451.959723] ? snr_uncore_mmio_init+0x20/0x20
[ 3451.961445] xen_init_lock_cpu+0x78/0xd0
[ 3451.963057] ? snr_uncore_mmio_init+0x20/0x20
[ 3451.964810] xen_cpu_up_online+0xe/0x20
[ 3451.966415] cpuhp_invoke_callback+0x8a/0x580
[ 3451.968144] cpuhp_thread_fun+0xb8/0x120
[ 3451.969760] smpboot_thread_fn+0xfc/0x170
[ 3451.971400] kthread+0x121/0x140
[ 3451.972855] ? sort_range+0x30/0x30
[ 3451.974378] ? kthread_park+0x90/0x90
[ 3451.975929]
[Kernel-packages] [Bug 2029917] Re: [Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-aws (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2029917
Title:
[Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers
triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on
AWS cloud c3.xlarge
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Bionic:
Confirmed
Status in linux-aws source package in Focal:
Confirmed
Bug description:
Issue found with 5.4.0-1107.115~18.04.1 Bionic AWS and 5.4.0-1107.115
Focal AWS kernel, on c3.xlarge instance only.
There is no output from the test itself (looks like it has crashed):
START ubuntu_ltp_controllers.cpuset_hotplug
ubuntu_ltp_controllers.cpuset_hotplug timestamp=1689920544timeout=4500
localtime=Jul 21 06:22:24
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_controllers.cpuset_hotplug',
'ubuntu_ltp_controllers.cpuset_hotplug')
Waiting for pid 925631 for 4500 seconds
System python is too old, crash handling disabled
(nothing after this point)
But from the console log you will see a kernel BUG and kernel panic:
[ 3451.829941] kernel BUG at
/build/linux-aws-5.4-I38rpz/linux-aws-5.4-5.4.0/arch/x86/xen/spinlock.c:62!
[ 3451.833383] invalid opcode: [#1] SMP PTI
[ 3451.835146] CPU: 1 PID: 14 Comm: cpuhp/1 Tainted: G C
5.4.0-1107-aws #115~18.04.1-Ubuntu
[ 3451.838679] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006
[ 3451.840965] RIP: 0010:dummy_handler+0x4/0x10
[ 3451.842675] Code: 8b 75 e4 74 d6 44 89 e7 e8 39 89 61 00 eb d6 44 89 e7 e8
af ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66
2e 0f 1f 84 00 00 00 00 00 80 3d 69 d0 9f 01 00 75 02 f3
[ 3451.849042] RSP: :b54bee38 EFLAGS: 00010046
[ 3451.851021] RAX: 92c2e3d0 RBX: 003b RCX:
[ 3451.853509] RDX: 00400e00 RSI: RDI:
003b
[ 3451.855996] RBP: b54bee38 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.858435] R10: R11: 94664da8 R12:
[ 3451.860896] R13: R14: R15:
8a9de6583200
[ 3451.863313] FS: () GS:8a9de804()
knlGS:
[ 3451.899246] CS: 0010 DS: ES: CR0: 80050033
[ 3451.901338] CR2: CR3: 2040a001 CR4:
001606e0
[ 3451.903757] DR0: DR1: DR2:
[ 3451.906184] DR3: DR6: fffe0ff0 DR7:
0400
[ 3451.908623] Call Trace:
[ 3451.909869]
[ 3451.911014] __handle_irq_event_percpu+0x44/0x1a0
[ 3451.912818] handle_irq_event_percpu+0x32/0x80
[ 3451.914578] handle_percpu_irq+0x3d/0x60
[ 3451.916198] generic_handle_irq+0x28/0x40
[ 3451.917834] handle_irq_for_port+0x8f/0xe0
[ 3451.919493] evtchn_2l_handle_events+0x157/0x270
[ 3451.921298] __xen_evtchn_do_upcall+0x76/0xe0
[ 3451.923046] xen_evtchn_do_upcall+0x2b/0x40
[ 3451.924742] xen_hvm_callback_vector+0xf/0x20
[ 3451.926484]
[ 3451.927632] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20
[ 3451.929674] Code: e8 a0 3d 64 ff 4c 29 e0 4c 39 f0 76 cf 80 0b 08 eb 8a 90
90 90 0f 1f 44 00 00 55 48 89 e5 e8 d6 ad 66 ff 66 90 48 89 f7 57 9d <0f> 1f 44
00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07
[ 3451.935996] RSP: :b54b000fbcf8 EFLAGS: 0246 ORIG_RAX:
ff0c
[ 3451.939023] RAX: 0001 RBX: 8a9de6583200 RCX:
0002cc00
[ 3451.941475] RDX: 0001 RSI: 0246 RDI:
0246
[ 3451.943948] RBP: b54b000fbcf8 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.946382] R10: R11: 0246 R12:
003b
[ 3451.948849] R13: R14: 8a9d8e75c600 R15:
8a9d8e75c6a4
[ 3451.951297] __setup_irq+0x456/0x760
[ 3451.952850] ? kmem_cache_alloc_trace+0x170/0x230
[ 3451.954661] request_threaded_irq+0xfb/0x160
[ 3451.956376] bind_ipi_to_irqhandler+0xba/0x1c0
[ 3451.958113] ? xen_qlock_wait+0x90/0x90
[ 3451.959723] ? snr_uncore_mmio_init+0x20/0x20
[ 3451.961445] xen_init_lock_cpu+0x78/0xd0
[ 3451.963057] ? snr_uncore_mmio_init+0x20/0x20
[ 3451.964810] xen_cpu_up_online+0xe/0x20
[ 3451.966415] cpuhp_invoke_callback+0x8a/0x580
[ 3451.968144] cpuhp_thread_fun+0xb8/0x120
[ 3451.969760] smpboot_thread_fn+0xfc/0x170
[ 3451.971400] kthread+0x121/0x140
[ 3451.972855] ? sort_range+0x30/0x30
[ 3451.974378] ? kthread_park+0x90/0x90
[ 3451.975929]
[Kernel-packages] [Bug 2033386] Re: 6.2.0-31 SMB1 NAS won't mount
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/2033386 Title: 6.2.0-31 SMB1 NAS won't mount Status in linux package in Ubuntu: Confirmed Bug description: I can't connect to my old NAS SMB vers=1.0 using cifs via fstab, everything works in kernel 6.2.0-26 and I have to roll back. mount.cifs(8) -22 invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033386/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
This bug was fixed in the package nvidia-graphics-drivers-390 - 390.157-0ubuntu8 --- nvidia-graphics-drivers-390 (390.157-0ubuntu8) mantic; urgency=medium * debian/dkms_nvidia.conf, debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_6.5-garbage-collect-all-references-to-get_user.patch, debian/dkms_nvidia/patches/buildfix_kernel_6.5-handle-get_user_pages-vmas-argument-remova.patch: - Support linux 6.5 ABI (LP: #2028165). -- Paolo Pisati Wed, 19 Jul 2023 13:06:56 + ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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
UPDATE 2 It seems that to solve the BTF problem, we can copy the current version of vmlinux, in the appropriate directory: sudo cp /sys/kernel/btf/vmlinux /usr/lib/modules/$(uname -r)/build/ THEN Compiling the driver, the claim about BTF is no more raised -- 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
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@raj @Samer the cd error is due to the fact that you have many linux-*** directory in your home directory. This prevent the change of dir and the problems follows. The linx directory name changed from linux-generic-5.*** to linux-hwe-6.*** BUT there are more problem When deleted the old linux-* dirs, and restart compile script, it shows that new kernel version lack the vmlinux.gz file. Skipping BTF generation for /home/giuliano/linux-hwe-6.2-6.2.0/drivers/media/usb/uvc/uvcvideo.ko due to unavailability of vmlinux The problem prevent the compiling of the driver. There are some complain on the new 6.2 kernel (even kernel panic). @Jeremy (wa113y3s) May you help us in understanding how to change the compiling process, due to the main version kernel change ? -- 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:
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
UPDATE even without the BPF Type Format (BTF), the compiling process of uvcvideo.ko DOES work The problem with Type format seems not to prevent the new driver to became working (teste right now) -- 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 - Board Asset Tag dmi.board.name: Ignis_ADH
[Kernel-packages] [Bug 2032176] Re: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1
Right, fix-committed means it is applied to git and will be included in the 2023.09.04 SRU cycle. The fix for 5.15 is to change the default of tdp_mmu to off (like you did for testing). Changing the deployments like you did would be the work-around in the mean-time. The parent Ubuntu state refers to current development (Mantic right now). This should be fixed. This would leave Lunar (6.2). That should at least contain improvements to leave this enabled by default. And I read Thadeu's comment as he was not able to reproduce with 6.2 (to me it sounded like without changing the value there, but it is a bit ambigous). -- 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/2032176 Title: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: Impact: We had reports of VM setups which would show intermediate crashes and after that locking up completely. This could be reproduced with large memory setups. The problem seems to be that fixes to performance regressions caused more problems in 5.15 kernels and the full fixes are too intrusive to be backported. Fix: The following patch was recently sent to the upstream stable mailing list and looks to be making its way into linux-5.15.y. This changes the default value of kvm.tdp_mmu to off (if anyone is willing to take the risks, this can be changed back in config). Regression potential: VM hosts with many large memory tennants might see a performance impact which the TDP MMU approach tried to solve. If those did not see other problems they might turn this on again. Testcase: Large openstack instance (64GB memory, AMD CPU (using SVM)) with a large second level guest (32GB memory). Repeatedly starting and stopping the 2nd level guest. --- original description --- The crash occurred on a juju machine, and the juju agent was lost. The juju machine is on an openstack instance provision by juju. The openstack console log indicts the it is related to spin_lock and KVM MMU: [418200.348830] ? _raw_spin_lock+0x22/0x30 [418200.349588] _raw_write_lock+0x20/0x30 [418200.350196] kvm_tdp_mmu_map+0x2b1/0x490 [kvm] [418200.351014] kvm_mmu_notifier_invalidate_range_start+0x1ad/0x300 [kvm] [418200.351796] direct_page_fault+0x206/0x310 [kvm] [418200.352667] __mmu_notifier_invalidate_range_start+0x91/0x1b0 [418200.353624] kvm_tdp_page_fault+0x72/0x90 [kvm] [418200.354496] try_to_migrate_one+0x691/0x730 [418200.355436] kvm_mmu_page_fault+0x73/0x1c0 [kvm] openstack console log: https://pastebin.canonical.com/p/spmH8r3crQ/ syslog: https://pastebin.canonical.com/p/wFPsFD8G9n/ The syslog was rotated after the crash occurred, so the syslog at the time of the initial crash was lost. Other juju machine with 5.15.0.79.76 kernel seems to have the same issues. We previously have a similar issue with 5.15.0-73. The juju machine crashed with raw_spin_lock and kvm mmu in the logs as well: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Aug 21 08:59:46 2023 Ec2AMI: ami-0c61 Ec2AMIManifest: FIXME Ec2AvailabilityZone: availability-zone-1 Ec2InstanceType: builder-cpu4-ram72-disk20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 23 03:23 seq crw-rw 1 root audio 116, 33 Aug 23 03:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) DistroRelease: Ubuntu 22.04 Ec2AMI: ami-0fbb Ec2AMIManifest: FIXME Ec2AvailabilityZone: availability-zone-2
[Kernel-packages] [Bug 2021572] Re: dGPU cannot resume because system firmware stuck in IPCS method
** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2021572 Title: dGPU cannot resume because system firmware stuck in IPCS method Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When a dGPU on a laptop is in PCIe D3cold and TBT port is connected to a monitor via a cable, unplugging the cable will make the dGPU unable to resume to D0. [Fix] There's a part of system firmware, IOM, need the driver to disconnect all TBT/Type-C phy to let dGPU function normally. [Test] With the fix applied, the dGPU continues to work after replugging video cable many times. [Where problems could occur] The fix is composed of several overhaul, so it's likely to regression i915 GFX driver. To limit the impact, only target OEM kernel for now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021572/+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 2033869] [NEW] linux-intel-iotg package - bump to 6.5 kernel version - linux-intel-iotg-b
Public bug reported: linux-intel-iotg package - bump to 6.5 kernel version - linux-intel- iotg-b ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2033869 Title: linux-intel-iotg package - bump to 6.5 kernel version - linux-intel- iotg-b Status in linux-intel-iotg package in Ubuntu: New Bug description: linux-intel-iotg package - bump to 6.5 kernel version - linux-intel- iotg-b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2033869/+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 2033654] Re: amdgpu: Fixes for S0i3 resume on Phoenix
** Changed in: linux (Ubuntu Lunar) Status: Triaged => Fix Committed -- 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/2033654 Title: amdgpu: Fixes for S0i3 resume on Phoenix Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Hard hangs in some cases on resume from suspend on AMD Phoenix [Fix] pick three commits from v6.5-rc7 (also in 6.1.47): 730d44e1fa306a2 drm/amd/pm: skip the RLC stop when S0i3 suspend for SMU v13.0.4/11 f1740b1ab2703b2 drm/amdgpu: skip fence GFX interrupts disable/enable for S0ix a7b7d9e8aee4f71 drm/amd: flush any delayed gfxoff on suspend entry [Test Case] Check the updated kernel on a failing system, and test resume from suspend. [Where problems could occur] These are cherry-picks from upstream stable, and limited to Phoenix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033654/+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 2033868] [NEW] linux-intel-iotg package - bump to 6.1 kernel version - linux-intel-iotg-a
Public bug reported: linux-intel-iotg package - bump to 6.1 kernel version - linux-intel- iotg-a ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2033868 Title: linux-intel-iotg package - bump to 6.1 kernel version - linux-intel- iotg-a Status in linux-intel-iotg package in Ubuntu: New Bug description: linux-intel-iotg package - bump to 6.1 kernel version - linux-intel- iotg-a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2033868/+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 1959593] Re: tcm_loop requires '-extras' for EKS optimised AMIs
this is included in all available EKS images (and in general in Ubuntu images on AWS). Feel free to reopen if you still encounter this problem. ** Changed in: cloud-images Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1959593 Title: tcm_loop requires '-extras' for EKS optimised AMIs Status in cloud-images: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux-aws source package in Impish: Fix Released Status in linux-aws source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Hello, It seems that although the Azure kernel distribution includes the `tcm_loop` module by default, the EKS-optimised image's default kernel doesn't, instead including the module in the `linux-kernel- extras-$(uname -r)` package. `tcm_loop` is an incredibly useful package for any storage fabric software packages - eg. Ceph, Rook or Ondat. It would be very helpful to have it embedded into the default kernel distribution in order to reduce friction on installing 'storage fabric' type topologies. The Ubuntu on EKS images are all listed in https://cloud- images.ubuntu.com/docs/aws/eks/ - I'd be happy to provide any information necessary to help shave off this extra bit of work required to setup such images. [Fix] Add tcm_loop.ko to the inclusion list [Test Case] Check that linux-modules includes tcp_loop.ko [Where things could go wrong] Moving tcm_loop.ko from linux-modules-extra could impact proprietary methods. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1959593/+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 1908099] Re: nvidia-dkms-390 fails to build on unstable / 5.10
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Won't Fix ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Hirsute) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1908099 Title: nvidia-dkms-390 fails to build on unstable / 5.10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 source package in Hirsute: Won't Fix Bug description: [Impact] nvidia-graphics-drivers-390 fails to build against linux 5.10: ERROR (dkms apport): kernel package linux-headers-5.10.0-6-generic is not supported Error! Bad return status for module build on kernel: 5.10.0-6-generic (x86_64) Consult /var/lib/dkms/nvidia/390.138/build/make.log for more information. dpkg: error processing package nvidia-dkms-390 (--configure): installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.10.0-6-generic Errors were encountered while processing: nvidia-dkms-390 E: Sub-process /usr/bin/dpkg returned an error code (1) [Test case] sudo apt install nvidia-dkms-390 [Fix] Fix build errors adding the proper #ifdef to support the new 5.10 includes, function prototypes and data structs. [Regression potential] All the new code is conditional (#ifdef) and it's applied only with 5.10, so there is no risk to break the other kernels (5.8). Moreover, it's worth considering that hirsute should move soon to 5.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+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 2032704] Re: Fix panel brightness issues on HP laptops
** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2032704 Title: Fix panel brightness issues on HP laptops Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Brightness can't be changed or can only be changed once on some modern HP laptops. [Fix] BIOS folks identified the issue where the ACPI _PS0 method isn't called for the panel device. On Windows the method is being invoked. This is due to missing _PSC, but since Windows is the de facto spec, we have to perform the same to make the device functional. [Test] Once the fix is applied, the brightness can be changed smoothly. [Where problems could occur] According to BIOS folks, Windows also invokes _PS3 for sleep and shutdown, we need to tackle that in the future. Right now not calling _PS3 has no ill-effect, per BIOS folks. X-HWE-Bug: Bug #2032704 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032704/+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 2032767] Re: Fix ACPI TAD on some Intel based systems
** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2032767 Title: Fix ACPI TAD on some Intel based systems Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] ACPI TAD doesn't really work on several systems. When accessing TAD interface via sysfs, like setting/getting realtime, it also causes errors: [ 478.255453] ACPI Error: No handler for Region [RTCM] (a8d2dd39) [SystemCMOS] (20230331/evregion-130) [ 478.255458] ACPI Error: Region SystemCMOS (ID=5) has no handler (20230331/exfldio-261) [ 478.255461] Initialized Local Variables for Method [_GRT]: [ 478.255461] Local1: f182542cInteger [ 478.255464] No Arguments are initialized for method [_GRT] [ 478.255465] ACPI Error: Aborting method \_SB.AWAC._GRT due to previous error (AE_NOT_EXIST) (20230331/psparse-529) [Fix] Let the driver to install a handler for its SystemCMOS region. The spec on whether certain devices can use SystemCMOS or not is quite vague, so follow the de facto implementation, Windows :) [Test] Once the patch is applied, setting and getting realtime through TAD sysfs work, and there's no more error in dmesg. [Where problems could occur] Now ACPI TAD driver also depends on ACPI RTC driver, so the memory usage will go up slightly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032767/+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 2022361] Re: Please enable Renesas RZ platform serial installer
Hi Roxana
Thanks for the Fix committed.
Please update when the change will be "Fix Released"?
Best Regards
John
--
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/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Regression potential]
Statically building an additional driver in the kernel can make the
kernel image bigger, potentially causing boot issues in small (arm64 /
armhf) platforms.
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+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 2033122] Re: Request backport of xen timekeeping performance improvements
** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Krister Johansen (kmjohansen) ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => Krister Johansen (kmjohansen) -- 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/2033122 Title: Request backport of xen timekeeping performance improvements Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: Users, especially those on EC2, are encouraged to select tsc as their default clocksource. However, this requires manual tuning of the operating system. Kvm can determine if it safe to use the tsc, and will default to that instead of its pvclock when appropriate. This requests a backport of patch does the same for Xen instances. If appropriate, it's fine if this is applied to only the linux-aws branches. Not all Xen EC2 instances advertise explicit nomigrate support, however, on those that do we'll select tsc by default. On the subset of hosts where this is advertised, users will safely default to the more performant clocksource. [Impact] Xen instances default to the xen clocksource which has been documented to be slower. This is required for instances where the tsc is not safe to use, or the guest is subject to migration. On some platforms the performance impact can be high, and users are encouraged to select the tsc when appropriate. Instead of leaving up to users to figure this out by reading a variety of different documents, pick the fast clocksource when it can be determined to be safe to do so. [Backport] Clean cherry pick. No conflicts applying to 5.15 or 6.2. [Test] Booted EC2 xen instances with and without this patch and validated that on those that properly advertised the required criteria via cpuid, that the clocksource defaulted to tsc instead of xen. [Potential Regression] Potential is low, since only absurd configurations could lead to a problem. If this is considered risky, it can be applied to only linux-aws where the documented guidance is for users to enable tsc as the clocksource on Xen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033122/+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 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Committed -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+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 2033025] Re: Fix numerous AER related issues
** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033452] Re: Enable D3cold at s2idle for Intel DG2 GPU
** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033452 Title: Enable D3cold at s2idle for Intel DG2 GPU Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The system wakes up during s2idle with Intel DG2 GPU. It causes high power consumption during suspend. [Fix] Enable D3cold at s2idle. [Test] Tested on hardware, the system sleeps as long as expected, the power consumption is lower. [Where problems could occur] It may break i915 driver. It's a fix of regression in v6.1, no need for jammy and already in 6.5. SRU for lunar and oem-6.1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033452/+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 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+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 2019868] Re: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Magali Lemes do Sacramento (magalilemes) -- 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/2019868 Title: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. The results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: tls # TAP version 13 # 1..179 # # Starting 179 tests from 6 test cases. # # RUN global.non_established ... # #OK global.non_established # ok 1 global.non_established # # RUN global.keysizes ... # #OK global.keysizes # ok 2 global.keysizes # # RUN tls_basic.base_base ... # #OK tls_basic.base_base # ok 3 tls_basic.base_base # # RUN tls.12_gcm.sendfile ... # #OK tls.12_gcm.sendfile # ok 4 tls.12_gcm.sendfile # # RUN tls.12_gcm.send_then_sendfile ... # #OK tls.12_gcm.send_then_sendfile # ok 5 tls.12_gcm.send_then_sendfile # # RUN tls.12_gcm.recv_max ... # #OK tls.12_gcm.recv_max # ok 6 tls.12_gcm.recv_max # # RUN tls.12_gcm.recv_small ... # #OK tls.12_gcm.recv_small # ok 7 tls.12_gcm.recv_small # # RUN tls.12_gcm.msg_more ... # #OK tls.12_gcm.msg_more # ok 8 tls.12_gcm.msg_more # # RUN tls.12_gcm.msg_more_unsent ... # #OK tls.12_gcm.msg_more_unsent # ok 9 tls.12_gcm.msg_more_unsent # # RUN tls.12_gcm.sendmsg_single ... # #OK tls.12_gcm.sendmsg_single # ok 10 tls.12_gcm.sendmsg_single # # RUN tls.12_gcm.sendmsg_fragmented ... # #OK tls.12_gcm.sendmsg_fragmented # ok 11 tls.12_gcm.sendmsg_fragmented # # RUN tls.12_gcm.sendmsg_large ... # #OK tls.12_gcm.sendmsg_large # ok 12 tls.12_gcm.sendmsg_large # # RUN tls.12_gcm.sendmsg_multiple ... # #OK tls.12_gcm.sendmsg_multiple # ok 13 tls.12_gcm.sendmsg_multiple # # RUN tls.12_gcm.sendmsg_multiple_stress ... # #OK tls.12_gcm.sendmsg_multiple_stress # ok 14 tls.12_gcm.sendmsg_multiple_stress # # RUN tls.12_gcm.splice_from_pipe ... # #OK tls.12_gcm.splice_from_pipe # ok 15 tls.12_gcm.splice_from_pipe # # RUN tls.12_gcm.splice_from_pipe2 ... # #OK tls.12_gcm.splice_from_pipe2 # ok 16 tls.12_gcm.splice_from_pipe2 # # RUN tls.12_gcm.send_and_splice ... # #OK tls.12_gcm.send_and_splice # ok 17 tls.12_gcm.send_and_splice # # RUN tls.12_gcm.splice_to_pipe ... # #OK tls.12_gcm.splice_to_pipe # ok 18 tls.12_gcm.splice_to_pipe # # RUN tls.12_gcm.recvmsg_single ... # #OK tls.12_gcm.recvmsg_single # ok 19 tls.12_gcm.recvmsg_single # # RUN tls.12_gcm.recvmsg_single_max ... # #OK tls.12_gcm.recvmsg_single_max # ok 20 tls.12_gcm.recvmsg_single_max # # RUN tls.12_gcm.recvmsg_multiple ... # #OK tls.12_gcm.recvmsg_multiple # ok 21 tls.12_gcm.recvmsg_multiple # # RUN tls.12_gcm.single_send_multiple_recv ... # #OK tls.12_gcm.single_send_multiple_recv # ok 22 tls.12_gcm.single_send_multiple_recv # # RUN tls.12_gcm.multiple_send_single_recv ... # #OK tls.12_gcm.multiple_send_single_recv # ok 23 tls.12_gcm.multiple_send_single_recv # # RUN tls.12_gcm.single_send_multiple_recv_non_align ... # #OK tls.12_gcm.single_send_multiple_recv_non_align # ok 24 tls.12_gcm.single_send_multiple_recv_non_align # # RUN tls.12_gcm.recv_partial ... # #OK tls.12_gcm.recv_partial # ok 25 tls.12_gcm.recv_partial # # RUN tls.12_gcm.recv_nonblock ... # #OK
[Kernel-packages] [Bug 2019000] Re: Use new annotations model
The conversion on focal:linux-lowlatency-hwe-5.15 was done and I had verified that generated configs before and after did match. ** Tags removed: verification-needed-focal-linux-lowlatency-hwe-5.15 ** Tags added: verification-done-focal-linux-lowlatency-hwe-5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2019000 Title: Use new annotations model Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux source package in Focal: Triaged Status in linux-gcp source package in Focal: New Status in linux source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux source package in Kinetic: Confirmed Status in linux-gcp source package in Kinetic: Invalid Bug description: [Impact] Starting with lunar we have introduced a new way to manage kernel configs, unifying the duplicated information defined in the annotations file + config chunks into an annotations-only model. [Test case] A kernel build can be considered a valid test case, in particular the specific command that is used to update the .config's for all the supported architectures and flavours: $ fakeroot debian/rules updateconfigs [Fix] Import the required changes in debian/ from lunar (with the required adjustments) to support the annotations-only model also in all the previous releases. [Regression potential] We may experience regressions during the updateconfigs step, especially with derivatives. Moreover, derivatives that want to transition to the new annotations model require to adjust the header in the annotations file as following (make sure to define the corresponding architectures and flavours): # FORMAT: 4 # ARCH: amd64 arm64 armhf ppc64el s390x # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae ppc64el-generic s390x-generic After adjusting the header a special command is provided to transition to the new annotations-only model: $ fakeroot debian/rules migrateconfigs This command should automatically import the old configs into the new annotations file. A kernel with this change applied can still support the old annotations+configs model, the transition to the new model is not mandatory. Basically without using `fakeroot debian/rules migrateconfigs` the updateconfigs step will continue to use the old model and the old scripts (that is the safest approach to avoid potential unexpected .config changes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+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 2019880] Re: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Roxana Nicolescu (roxanan) ** Changed in: linux (Ubuntu Jammy) Assignee: Roxana Nicolescu (roxanan) => Magali Lemes do Sacramento (magalilemes) ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- 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/2019880 Title: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. Results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: vrf-xfrm-tests.sh # # No qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # netem qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # Tests passed: 6 # Tests failed: 8 not ok 1 selftests: net: vrf-xfrm-tests.sh # exit=1 make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2019880/+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 2022361] Re: Please enable Renesas RZ platform serial installer
** Changed in: linux (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Lunar)
Status: New => Fix Committed
--
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/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Regression potential]
Statically building an additional driver in the kernel can make the
kernel image bigger, potentially causing boot issues in small (arm64 /
armhf) platforms.
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+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 2033756] [NEW] Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U system freeze more than once a day
Public bug reported: Hello, Having this computer for about 6 month now. Tried Ubuntu 20.04, 23.04, now I'm back with 22.04 and many kernel versions. I can't found a stable configuration. Very often, once a day in average, the system hangs and I have to hard reboot it. I have plenty of kernel logs but most of the time they are not relevant because the last message may be hours old. I added a question at lenovo forum, the logs can be found there but if they help I can upload them here too. Url of the post on lenovo site: https://forums.lenovo.com/t5/Ubuntu/System-freeze-with-Ubuntu-22-04-to-23-04-on-P14s-gen3-AMD-version/m-p/5227346?page=4#6089001 I have some technical knowledge, so I can do some tests if that can help solving this issue. Note: currently attached dmeg contains a OoPs, I'm no sure but I feel like this message is an early sign of future freeze. Hence the bug report. Many thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-82-generic 5.15.0-82.91 ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 Uname: Linux 5.15.0-82-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jf 2338 F pulseaudio /dev/snd/pcmC1D0p: jf 2338 F...m pulseaudio /dev/snd/controlC0: jf 2338 F pulseaudio /dev/snd/controlC2: jf 2338 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 10:34:36 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2023-06-02 (90 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 MachineType: LENOVO 21J5CTO1WW ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-82-generic root=UUID=ad3cccf2-3072-4b29-84f0-ed7b41dd4de6 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-82-generic N/A linux-backports-modules-5.15.0-82-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-08-12 (19 days ago) dmi.bios.date: 03/21/2023 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET65W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21J5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR23ET65W(1.35):bd03/21/2023:br1.35:efr1.28:svnLENOVO:pn21J5CTO1WW:pvrThinkPadP14sGen3:rvnLENOVO:rn21J5CTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21J5_BU_Think_FM_ThinkPadP14sGen3: dmi.product.family: ThinkPad P14s Gen 3 dmi.product.name: 21J5CTO1WW dmi.product.sku: LENOVO_MT_21J5_BU_Think_FM_ThinkPad P14s Gen 3 dmi.product.version: ThinkPad P14s Gen 3 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: Hello, Having this computer for about 6 month now. Tried Ubuntu 20.04, 23.04, now I'm back with 22.04 and many kernel versions. + I can't found a stable configuration. Very often, once a day in average, the system hangs and I have to hard reboot it. I have plenty of kernel logs but most of the time they are not relevant because the last message may be hours old. + I added a question at lenovo forum, the logs can be found there but if they help I can upload them here too. - I have some technical knowledge, so I can do some tests if that can help solving this issue. + Url of the post on lenovo site: https://forums.lenovo.com/t5/Ubuntu/System-freeze-with-Ubuntu-22-04-to-23-04-on-P14s-gen3-AMD-version/m-p/5227346?page=4#6089001 + + I have some technical knowledge, so I can do some tests if that can help + solving this issue. Note: currently attached dmeg contains a OoPs, I'm no sure but I feel like this message is an early sign of future freeze. Hence the bug report. Many thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-82-generic 5.15.0-82.91 ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 Uname: Linux 5.15.0-82-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: jf 2338 F pulseaudio - /dev/snd/pcmC1D0p: jf 2338 F...m pulseaudio - /dev/snd/controlC0: jf 2338
[Kernel-packages] [Bug 2033756] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/2033756 Title: Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U system freeze more than once a day Status in linux package in Ubuntu: Confirmed Bug description: Hello, Having this computer for about 6 month now. Tried Ubuntu 20.04, 23.04, now I'm back with 22.04 and many kernel versions. I can't found a stable configuration. Very often, once a day in average, the system hangs and I have to hard reboot it. I have plenty of kernel logs but most of the time they are not relevant because the last message may be hours old. I added a question at lenovo forum, the logs can be found there but if they help I can upload them here too. Url of the post on lenovo site: https://forums.lenovo.com/t5/Ubuntu/System-freeze-with-Ubuntu-22-04-to-23-04-on-P14s-gen3-AMD-version/m-p/5227346?page=4#6089001 I have some technical knowledge, so I can do some tests if that can help solving this issue. Note: currently attached dmeg contains a OoPs, I'm no sure but I feel like this message is an early sign of future freeze. Hence the bug report. Many thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-82-generic 5.15.0-82.91 ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 Uname: Linux 5.15.0-82-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jf 2338 F pulseaudio /dev/snd/pcmC1D0p: jf 2338 F...m pulseaudio /dev/snd/controlC0: jf 2338 F pulseaudio /dev/snd/controlC2: jf 2338 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 10:34:36 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2023-06-02 (90 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 MachineType: LENOVO 21J5CTO1WW ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-82-generic root=UUID=ad3cccf2-3072-4b29-84f0-ed7b41dd4de6 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-82-generic N/A linux-backports-modules-5.15.0-82-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-08-12 (19 days ago) dmi.bios.date: 03/21/2023 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET65W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21J5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR23ET65W(1.35):bd03/21/2023:br1.35:efr1.28:svnLENOVO:pn21J5CTO1WW:pvrThinkPadP14sGen3:rvnLENOVO:rn21J5CTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21J5_BU_Think_FM_ThinkPadP14sGen3: dmi.product.family: ThinkPad P14s Gen 3 dmi.product.name: 21J5CTO1WW dmi.product.sku: LENOVO_MT_21J5_BU_Think_FM_ThinkPad P14s Gen 3 dmi.product.version: ThinkPad P14s Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033756/+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 2032164] Re: A general-proteciton exception during guest migration to unsupported PKRU machine
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/2032164 Title: A general-proteciton exception during guest migration to unsupported PKRU machine Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] When a host that supports PKRU initiates a guest that lacks PKRU support, the flag is enabled on the guest's fpstate. This information is then passed to userspace through the vcpu ioctl KVM_GET_XSAVE. However, a problem arises when the user opts to migrate the mentioned guest to another machine that does not support PKRU. In this scenario, the new host attempts to restore the guest's fpu registers. Nevertheless, due to the absence of PKRU support on the new host, a general-protection exception takes place, leading to a guest crash. [Fix] The problem is resolved by the following upstream commit: ad856280ddea x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 Additionally, a subsequent fix tackles the migration problem stemming from the earlier commit: a1020a25e697 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES [Test Plan] 1. Set up two machines: one with PKRU support and the other without. 2. Initiate a guest that lacks PKRU support on the machine with PKRU support. 3. Utilize libvirt to migrate the aforementioned guest to a different machine that lacks PKRU support. 4. The error emerges on the destination machine: KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=86cf7970 EBX= ECX=0001 EDX=005b0036 ESI=0087 EDI=0087 EBP=87c03e38 ESP=87c03e18 EIP=86cf7d5e EFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2023-07-09T03:03:14.911750Z qemu-system-x86_64: terminating on signal 15 from pid 4134 (/usr/sbin/libvirtd) 2023-07-09 03:03:15.312+: shutting down, reason=destroyed [Where problems could occur] The introduced commits will impact the guest migration process, potentially leading to failures and preventing the guest from operating successfully on the migration destination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032164/+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 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms
** Also affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.5 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-oem-6.5 (Ubuntu Mantic)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2008882
Title:
Remove all other acpi_video backlight interface on Dell AIO platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux-oem-6.5 source package in Lunar:
Invalid
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
There are acpi_video* sysfs backlight interface in the system which are not
working.
For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
The new way to do this is to collect all the quirk and auto detection method
in video_detect.c
I added an audo detection for the Dell AIO platoform to the driver which
should do the same thing as the old way.
[Test]
Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+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 2028217] Re: MTL: Add support for Meteor Lake
Verified ~~~ thermald[6941]: 32 CPUID levels; family:model:stepping 0x6:aa:2 (6:170:2) thermald[6941]: NO RAPL sysfs present thermald[6941]: 32 CPUID levels; family:model:stepping 0x6:aa:2 (6:170:2) thermald[6941]: sensor id 11 : No temp sysfs for reading raw temp thermald[6941]: sensor id 11 : No temp sysfs for reading raw temp thermald[6941]: sensor id 11 : No temp sysfs for reading raw temp thermald[6941]: Config file /etc/thermald/thermal-conf.xml does not exist thermald[6941]: Config file /etc/thermald/thermal-conf.xml does not exist thermald[6941]: Config file /etc/thermald/thermal-conf.xml does not exist thermald[6941]: Polling mode is enabled: 4 $ uname -a Linux ubuntu 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ~~~ ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy ** Tags removed: verification-needed ** Tags added: verification-done -- 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/2028217 Title: MTL: Add support for Meteor Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: Fix Committed Status in thermald source package in Kinetic: Won't Fix Status in thermald source package in Lunar: Won't Fix Status in thermald source package in Mantic: Fix Released Bug description: [Impact] * Support thermald on Meteor Lake CPU. [Test Plan] * Use a machine with a Meteor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change adds support for Meteor Lake in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2028217/+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 2033744] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/2033744 Title: Failed to resume from suspend in linux kernel 6.2.0.31 Status in linux package in Ubuntu: Confirmed Bug description: If system suspended, system can't resume and screen can't display anything, but my computer hardware still running. In some case, screen can show GDM but it content is freeze and can't do anything. I boot to older kernel because this issue This is my system info : $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 $ inxi -Fzxxx System: Kernel: 6.2.0-27-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME v: 44.3 tk: GTK v: 3.24.37 wm: gnome-shell dm: GDM3 v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: LENOVO product: 20KEA062UK v: ThinkPad X280 serial: Chassis: type: 10 serial: Mobo: LENOVO model: 20KEA062UK v: SDK0J40697 WIN serial: UEFI: LENOVO v: N20ET64P (1.49 ) date: 11/21/2022 Battery: ID-1: BAT0 charge: 34.8 Wh (81.3%) condition: 42.8/48.0 Wh (89.2%) volts: 12.2 min: 11.5 model: SMP 01AV471 type: Li-poly serial: status: discharging cycles: 455 CPU: Info: quad core model: Intel Core i5-8350U bits: 64 type: MT MCP smt: enabled arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB Speed (MHz): avg: 1844 high: 2265 min/max: 400/3600 cores: 1: 2265 2: 2092 3: 1900 4: 899 5: 1900 6: 1900 7: 1900 8: 1900 bogomips: 30399 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5917 class-ID: 0300 Device-2: Acer SunplusIT Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:3 chip-ID: 5986:2113 class-ID: 0e02 Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.8 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: 0 Monitor-1: eDP-1 model: AU Optronics 0x106c res: 1366x768 dpi: 126 size: 276x155mm (10.87x6.1") diag: 317mm (12.5") modes: 1366x768 API: OpenGL v: 4.6 Mesa 23.0.4-0ubuntu1~23.04.1 renderer: Mesa Intel UHD Graphics 620 (KBL GT2) direct-render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403 Sound API: ALSA v: k6.2.0-27-generic running: yes Sound Server-1: PulseAudio v: 16.1 running: no Sound Server-2: PipeWire v: 0.3.65 running: yes Network: Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d7 class-ID: 0200 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 3b:00.0 chip-ID: 8086:24fd class-ID: 0280 IF: wlp59s0 state: up mac: IF-ID-1: virbr0 state: down mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:2 chip-ID: 8087:0a2b class-ID: e001 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: no address: Drives: Local Storage: total: 238.47 GiB used: 163.05 GiB (68.4%) ID-1: /dev/sda model: M.2 SATA SSD 256GB size: 238.47 GiB speed: 6.0 Gb/s type: SSD serial: rev: 1C0 scheme: GPT Partition: ID-1: / size: 238 GiB used: 163.04 GiB (68.5%) fs: btrfs dev: /dev/sda2 ID-2: /boot/efi size: 486 MiB used: 13.3 MiB (2.7%) fs: vfat dev: /dev/sda1 ID-3: /home size: 238 GiB used: 163.04 GiB (68.5%) fs: btrfs dev: /dev/sda2 Swap: ID-1: swap-1 type: zram size: 7.5 GiB used: 4 MiB (0.1%) priority: 100 dev: /dev/zram0 Sensors: System Temperatures: cpu: 52.0 C mobo: N/A Fan Speeds (RPM): fan-1: 0 Info: Processes: 312 Uptime: 1h 1m wakeups: 7 Memory: 7.5 GiB used: 3.36 GiB (44.9%) Init: systemd v: 252 target: graphical (5) default: graphical Compilers: gcc: 12.3.0 alt: 12 clang: 15.0.7 Packages: 2439 pm: dpkg pkgs: 2398 pm: flatpak pkgs: 30 pm: snap pkgs: 11 Shell: Zsh v: 5.9 running-in: gnome-terminal inxi: 3.3.25 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-generic 6.2.0.31.29 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anifyuli 1986 F wireplumber
[Kernel-packages] [Bug 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
A few of my colleagues are also affected with 6.2. This is really a bad situation. As workaround we stepped back to linux-oem-22.04c (6.1) which works without problems. [1.545289] VGA switcheroo: detected Optimus DSM method \_SB_.PC00.PEG1.PEGP handle [1.545290] nouveau: detected PR support, will not use DSM [1.545320] nouveau :01:00.0: enabling device (0006 -> 0007) [1.545649] nouveau :01:00.0: NVIDIA GA107 (b77000a1) [1.567694] ACPI Error: Cannot release Mutex [ECMX], not acquired (20221020/exmutex-357) [1.567699] fbcon: Taking over console [1.567703] No Local Variables are initialized for Method [_Q66] [1.567704] No Arguments are initialized for method [_Q66] [1.567705] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_MUTEX_NOT_ACQUIRED) (20221020/psparse-529) [1.629655] usb 3-3: New USB device found, idVendor=0c45, idProduct=6720, bcdDevice=82.68 [1.629660] usb 3-3: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [1.629661] usb 3-3: Product: Integrated_Webcam_HD [1.629662] usb 3-3: Manufacturer: CN0V976R8LG001C1A5ANA01 [1.655115] nouveau :01:00.0: bios: version 94.07.3b.00.e4 [1.655549] nouveau :01:00.0: acr: firmware unavailable [1.655693] nouveau :01:00.0: gr: firmware unavailable [1.655706] nouveau :01:00.0: sec2: firmware unavailable [1.655798] nouveau :01:00.0: fb: 4096 MiB GDDR6 [1.659174] nouveau :01:00.0: fb: VPR locked, but no scrubber binary! [1.661968] BUG: kernel NULL pointer dereference, address: [1.661970] #PF: supervisor instruction fetch in kernel mode [1.661972] #PF: error_code(0x0010) - not-present page [1.661973] PGD 0 P4D 0 [1.661975] Oops: 0010 [#1] PREEMPT SMP NOPTI [1.661977] CPU: 14 PID: 233 Comm: systemd-udevd Not tainted 6.2.0-26-generic #26~22.04.1-Ubuntu [1.661980] Hardware name: Dell Inc. Precision 7560/0186RY, BIOS 1.20.0 02/10/2023 [1.661981] RIP: 0010:0x0 [1.661984] Code: Unable to access opcode bytes at 0xffd6. [1.661985] RSP: 0018:aaf340e0b628 EFLAGS: 00010246 [1.661986] RAX: RBX: 906ce208dcb0 RCX: [1.661988] RDX: 906ce208dcd8 RSI: 906ce208dcc8 RDI: 906ce208dc00 [1.661989] RBP: aaf340e0b688 R08: 906ce208dcb0 R09: [1.661990] R10: R11: R12: 906ce208dcc8 [1.661991] R13: R14: 906ce208dcb0 R15: 906ce208dc08 [1.661992] FS: 7f2e66a658c0() GS:90742ff8() knlGS: [1.661994] CS: 0010 DS: ES: CR0: 80050033 [1.661995] CR2: ffd6 CR3: 0001015d4006 CR4: 00770ee0 [1.661997] PKRU: 5554 [1.661999] Call Trace: [1.662000] [1.662001] nvkm_acr_oneinit+0x502/0x710 [nouveau] [1.662057] nvkm_subdev_oneinit_+0x4d/0x120 [nouveau] [1.662103] nvkm_subdev_init_+0x3e/0x150 [nouveau] [1.662145] nvkm_subdev_init+0x55/0x80 [nouveau] [1.662186] nvkm_device_init+0x17b/0x300 [nouveau] [1.662259] nvkm_udevice_init+0x50/0x60 [nouveau] [1.662322] nvkm_object_init+0x40/0x210 [nouveau] [1.662363] nvkm_ioctl_new+0x196/0x2c0 [nouveau] [1.662403] ? __pfx_nvkm_client_child_new+0x10/0x10 [nouveau] [1.662442] ? __pfx_nvkm_udevice_new+0x10/0x10 [nouveau] [1.662504] nvkm_ioctl+0x12e/0x290 [nouveau] [1.662543] nvkm_client_ioctl+0xe/0x20 [nouveau] [1.662614] nvif_object_ctor+0x136/0x1a0 [nouveau] [1.662652] nvif_device_ctor+0x24/0x90 [nouveau] [1.662690] nouveau_cli_init+0x161/0x5e0 [nouveau] [1.662757] nouveau_drm_device_init+0x67/0x310 [nouveau] [1.662821] nouveau_drm_probe+0x131/0x280 [nouveau] [1.662882] local_pci_probe+0x48/0xb0 [1.662886] pci_call_probe+0x55/0x190 [1.662888] pci_device_probe+0x84/0x120 [1.662890] really_probe+0x1ea/0x450 [1.662893] __driver_probe_device+0x8a/0x1a0 [1.662895] driver_probe_device+0x23/0xd0 [1.662897] __driver_attach+0x10f/0x220 [1.662899] ? __pfx___driver_attach+0x10/0x10 [1.662901] bus_for_each_dev+0x80/0xe0 [1.662903] driver_attach+0x1e/0x30 [1.662905] bus_add_driver+0x152/0x250 [1.662907] driver_register+0x83/0x160 [1.662909] ? __pfx_init_module+0x10/0x10 [nouveau] [1.662949] __pci_register_driver+0x68/0x80 [1.662950] nouveau_drm_init+0x177/0xff0 [nouveau] [1.662988] do_one_initcall+0x46/0x240 [1.662991] ? kmalloc_trace+0x2a/0xb0 [1.662994] do_init_module+0x52/0x240 [1.662997] load_module+0xb96/0xd60 [1.662999] ? kernel_read_file+0x25c/0x2b0 [1.663002] __do_sys_finit_module+0xcc/0x150 [1.663004] ? __do_sys_finit_module+0xcc/0x150 [1.663006] __x64_sys_finit_module+0x18/0x30 [1.663008] do_syscall_64+0x59/0x90 [1.663012] ? ksys_mmap_pgoff+0x123/0x270 [1.663014] ?
[Kernel-packages] [Bug 2033732] Re: SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31)
** Package changed: ubuntu => linux-hwe-6.2 (Ubuntu) ** Tags added: jammy -- 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/2033732 Title: SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31) Status in linux-hwe-6.2 package in Ubuntu: New Bug description: I was running Ubuntu 22.04.3 on kernel version 5.15.0-82-generic, and I installed package linux-generic-hwe-22.04 in order to upgrade to kernel version 6.2.0-31. That upgrade broke the SMB version 1 protocol. I know that it is an old, deprecated protocol, but I still have to access some legacy systems and devices in a local network. This breakage has been discussed on the Internet. It is a Linux kernel regression. This is the commit that fixes it. It is a very small change: 2f6f19c7aaad "cifs: fix regression in very old smb1 mounts" https://github.com/torvalds/linux/commit/2f6f19c7aaad5005dc75298a413eb0243c5d312d I am no Linux kernel expert. Could you please backport that fix to the kernel versions that linux-generic-hwe-22.04 installs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2033732/+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 2033744] [NEW] Failed to resume from suspend in linux kernel 6.2.0.31
Public bug reported: If system suspended, system can't resume and screen can't display anything, but my computer hardware still running. In some case, screen can show GDM but it content is freeze and can't do anything. I boot to older kernel because this issue This is my system info : $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 $ inxi -Fzxxx System: Kernel: 6.2.0-27-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME v: 44.3 tk: GTK v: 3.24.37 wm: gnome-shell dm: GDM3 v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: LENOVO product: 20KEA062UK v: ThinkPad X280 serial: Chassis: type: 10 serial: Mobo: LENOVO model: 20KEA062UK v: SDK0J40697 WIN serial: UEFI: LENOVO v: N20ET64P (1.49 ) date: 11/21/2022 Battery: ID-1: BAT0 charge: 34.8 Wh (81.3%) condition: 42.8/48.0 Wh (89.2%) volts: 12.2 min: 11.5 model: SMP 01AV471 type: Li-poly serial: status: discharging cycles: 455 CPU: Info: quad core model: Intel Core i5-8350U bits: 64 type: MT MCP smt: enabled arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB Speed (MHz): avg: 1844 high: 2265 min/max: 400/3600 cores: 1: 2265 2: 2092 3: 1900 4: 899 5: 1900 6: 1900 7: 1900 8: 1900 bogomips: 30399 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5917 class-ID: 0300 Device-2: Acer SunplusIT Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:3 chip-ID: 5986:2113 class-ID: 0e02 Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.8 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: 0 Monitor-1: eDP-1 model: AU Optronics 0x106c res: 1366x768 dpi: 126 size: 276x155mm (10.87x6.1") diag: 317mm (12.5") modes: 1366x768 API: OpenGL v: 4.6 Mesa 23.0.4-0ubuntu1~23.04.1 renderer: Mesa Intel UHD Graphics 620 (KBL GT2) direct-render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403 Sound API: ALSA v: k6.2.0-27-generic running: yes Sound Server-1: PulseAudio v: 16.1 running: no Sound Server-2: PipeWire v: 0.3.65 running: yes Network: Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d7 class-ID: 0200 IF: enp0s31f6 state: down mac: Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 3b:00.0 chip-ID: 8086:24fd class-ID: 0280 IF: wlp59s0 state: up mac: IF-ID-1: virbr0 state: down mac: Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:2 chip-ID: 8087:0a2b class-ID: e001 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: no address: Drives: Local Storage: total: 238.47 GiB used: 163.05 GiB (68.4%) ID-1: /dev/sda model: M.2 SATA SSD 256GB size: 238.47 GiB speed: 6.0 Gb/s type: SSD serial: rev: 1C0 scheme: GPT Partition: ID-1: / size: 238 GiB used: 163.04 GiB (68.5%) fs: btrfs dev: /dev/sda2 ID-2: /boot/efi size: 486 MiB used: 13.3 MiB (2.7%) fs: vfat dev: /dev/sda1 ID-3: /home size: 238 GiB used: 163.04 GiB (68.5%) fs: btrfs dev: /dev/sda2 Swap: ID-1: swap-1 type: zram size: 7.5 GiB used: 4 MiB (0.1%) priority: 100 dev: /dev/zram0 Sensors: System Temperatures: cpu: 52.0 C mobo: N/A Fan Speeds (RPM): fan-1: 0 Info: Processes: 312 Uptime: 1h 1m wakeups: 7 Memory: 7.5 GiB used: 3.36 GiB (44.9%) Init: systemd v: 252 target: graphical (5) default: graphical Compilers: gcc: 12.3.0 alt: 12 clang: 15.0.7 Packages: 2439 pm: dpkg pkgs: 2398 pm: flatpak pkgs: 30 pm: snap pkgs: 11 Shell: Zsh v: 5.9 running-in: gnome-terminal inxi: 3.3.25 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-generic 6.2.0.31.29 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anifyuli 1986 F wireplumber /dev/snd/seq:anifyuli 1982 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 14:14:08 2023 InstallationDate: Installed on 2023-08-08 (23 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 20KEA062UK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-27-generic root=UUID=b4ead3e8-7e4c-4d1e-bd37-81b8e5bce6a2 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
[Kernel-packages] [Bug 2033732] [NEW] SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31)
You have been subscribed to a public bug: I was running Ubuntu 22.04.3 on kernel version 5.15.0-82-generic, and I installed package linux-generic-hwe-22.04 in order to upgrade to kernel version 6.2.0-31. That upgrade broke the SMB version 1 protocol. I know that it is an old, deprecated protocol, but I still have to access some legacy systems and devices in a local network. This breakage has been discussed on the Internet. It is a Linux kernel regression. This is the commit that fixes it. It is a very small change: 2f6f19c7aaad "cifs: fix regression in very old smb1 mounts" https://github.com/torvalds/linux/commit/2f6f19c7aaad5005dc75298a413eb0243c5d312d I am no Linux kernel expert. Could you please backport that fix to the kernel versions that linux-generic-hwe-22.04 installs? ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New -- SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31) https://bugs.launchpad.net/bugs/2033732 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. -- 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
@Giuliano Hello, I am also having the same error as @Marcos and @raj, so please help. Kind regards Samer Attrah -- 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 - Board Asset Tag dmi.board.name: Ignis_ADH dmi.board.vendor: ADL dmi.board.version: V1.06 dmi.chassis.type: 10
[Kernel-packages] [Bug 2033271] Re: Fujitsu keyboard not working after updates
Another user in the Ask Ubuntu thread reports, that the problem may be related to a false switch to tablet mode. I confirm the output of my device of "cat /sys/class/dmi/id/chassis_type" is "10". In addition: The E5410 is not a tablet nor a convertible, so it should not switch to tablet mode. -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2029917] Re: [Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
This issue can be reproduced with X-aws-hwe (4.15.0-1160-aws), passed with X-aws-hwe 4.15.0-1158-aws I was unable to find X-aws-hwe 4.15.0-1159 to test. [ 1121.855862] kernel BUG at /build/linux-aws-hwe-dFjJIX/linux-aws-hwe-4.15.0/arch/x86/xen/spinlock.c:69! [ 1121.857747] invalid opcode: [#1] SMP PTI [ 1121.858746] Modules linked in: sb_edac i2c_piix4 intel_rapl_perf serio_raw nfsd auth_rpcgss nfs_acl lockd grace sunrpc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc cirrus ttm drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt fb_sys_fops aes_x86_64 crypto_simd glue_helper drm cryptd i2c_core ixgbevf pata_acpi [ 1121.868747] CPU: 1 PID: 13 Comm: cpuhp/1 Not tainted 4.15.0-1160-aws #173~16.04.1-Ubuntu [ 1121.870378] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006 [ 1121.871665] RIP: 0010:dummy_handler+0x4/0x10 [ 1121.872535] RSP: :92f327a43e38 EFLAGS: 00010046 [ 1121.873589] RAX: a6e2ac40 RBX: 92f320d8ee80 RCX: [ 1121.875039] RDX: 00400e00 RSI: RDI: 003b [ 1121.876472] RBP: 92f327a43e38 R08: 92f32161e400 R09: 92f327002480 [ 1121.877908] R10: R11: 0040 R12: 003b [ 1121.879346] R13: R14: R15: [ 1121.880781] FS: () GS:92f327a4() knlGS: [ 1121.882404] CS: 0010 DS: ES: CR0: 80050033 [ 1121.883574] CR2: CR3: 0001bf00a001 CR4: 001606e0 [ 1121.885023] DR0: DR1: DR2: [ 1121.886472] DR3: DR6: fffe0ff0 DR7: 0400 [ 1121.887918] Call Trace: [ 1121.888436] [ 1121.71] __handle_irq_event_percpu+0x84/0x1a0 [ 1121.889836] handle_irq_event_percpu+0x32/0x80 [ 1121.890756] handle_percpu_irq+0x3d/0x60 [ 1121.891571] generic_handle_irq+0x28/0x40 [ 1121.892399] handle_irq_for_port+0x82/0xf0 [ 1121.893246] evtchn_2l_handle_events+0x1a7/0x270 [ 1121.894200] __xen_evtchn_do_upcall+0x76/0xe0 [ 1121.895111] xen_evtchn_do_upcall+0x2b/0x50 [ 1121.895974] xen_hvm_callback_vector+0x90/0xa0 [ 1121.896887] [ 1121.897339] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20 [ 1121.898482] RSP: :a2abc0d37d08 EFLAGS: 0246 ORIG_RAX: ff0c [ 1121.900019] RAX: 0001 RBX: 92f32161e400 RCX: 0002cc00 [ 1121.901461] RDX: 0001 RSI: 0246 RDI: 0246 [ 1121.902912] RBP: a2abc0d37d08 R08: 92f32161e470 R09: 92f327002480 [ 1121.904363] R10: 92f32161e4a4 R11: 0246 R12: [ 1121.905816] R13: 92f320d8ee80 R14: 003b R15: 92f32161e560 [ 1121.907274] __setup_irq+0x449/0x740 [ 1121.908018] request_threaded_irq+0x101/0x1b0 [ 1121.908913] bind_ipi_to_irqhandler+0xcc/0x1f0 [ 1121.909829] ? xen_qlock_wait+0x80/0x80 [ 1121.910629] xen_init_lock_cpu+0x97/0xf0 [ 1121.912626] ? skx_uncore_pci_init+0x40/0x40 [ 1121.914659] xen_cpu_up_online+0xe/0x20 [ 1121.916587] cpuhp_invoke_callback+0xb2/0x5c0 [ 1121.918585] ? schedule+0x36/0x80 [ 1121.920338] cpuhp_thread_fun+0xce/0x160 [ 1121.922184] smpboot_thread_fn+0x11a/0x170 [ 1121.924015] kthread+0x105/0x140 [ 1121.925643] ? sort_range+0x30/0x30 [ 1121.927300] ? kthread_bind+0x40/0x40 [ 1121.928922] ret_from_fork+0x35/0x40 [ 1121.930527] Code: 5e 5d c3 44 89 ef e8 1c 04 57 00 84 c0 74 de 44 89 ef e8 b0 df 56 00 eb de 44 89 ef e8 36 04 57 00 eb d4 0f 1f 40 00 55 48 89 e5 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 80 3d f9 e6 1f 01 00 55 48 [ 1121.936061] RIP: dummy_handler+0x4/0x10 RSP: 92f327a43e38 [ 1121.938150] ---[ end trace 7f404ac02d38ea24 ]--- [ 1121.939992] Kernel panic - not syncing: Fatal exception in interrupt [ 1121.942253] Kernel Offset: 0x25e0 from 0x8100 (relocation range: 0x8000-0xbfff) ** Changed in: linux-aws (Ubuntu) Status: New => Invalid ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2029917 Title: [Potential Regression] cpuset_hotplug in ubuntu_ltp_controllers triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Status in linux-aws source package in Focal: New Bug description: Issue found with 5.4.0-1107.115~18.04.1 Bionic AWS and 5.4.0-1107.115 Focal AWS kernel, on
[Kernel-packages] [Bug 2033735] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2033735 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/2033735 Title: [mantic] New 6.5.0.2 kernel + Intel GPU = no HDMI Status in linux package in Ubuntu: Incomplete Bug description: Hi, Legion laptop with Nvidia. - Nouveau : no hdmi - Nvidia 535 dynamic graphics : no HDMI (screen not detected) - Nvidia 535 discrete graphics : HDMI is detected So I suppose this bug to be linked to Intel GPU. All was ok with previous 6.3 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033735/+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 2033271] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696978/+files/WifiSyslog.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696979/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696968/+files/Lsusb-t.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696977/+files/UdevDb.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696976/+files/RfKill.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696969/+files/Lsusb-v.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696967/+files/Lsusb.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696973/+files/ProcInterrupts.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696974/+files/ProcModules.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696970/+files/PaInfo.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696975/+files/PulseList.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696972/+files/ProcCpuinfoMinimal.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696971/+files/ProcCpuinfo.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696966/+files/Lspci-vt.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696964/+files/IwConfig.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696965/+files/Lspci.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033271] Re: Fujitsu keyboard not working after updates
apport information ** Tags added: apport-collected ** Description changed: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: cysec 1698 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-04-21 (497 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 + RelatedPackageVersions: + linux-restricted-modules-6.2.0-31-generic N/A + linux-backports-modules-6.2.0-31-generic N/A + linux-firmware20220329.git681281e4-0ubuntu3.18 + Tags: wayland-session jammy + Uname: Linux 6.2.0-31-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: 06/30/2023 + dmi.bios.release: 2.30 + dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED + dmi.bios.version: Version 2.30 + dmi.board.name: FJNB2D6 + dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED + dmi.board.version: A2 + dmi.chassis.type: 10 + dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED + dmi.chassis.version: LIFEBOOK E5410 + dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: + dmi.product.family: LIFEBOOK-FTS + dmi.product.name: LIFEBOOK E5410 + dmi.product.sku: SK01 + dmi.product.version: 10601736746 + dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696962/+files/AlsaInfo.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Kernel-packages] [Bug 2033271] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2033271/+attachment/5696963/+files/CurrentDmesg.txt -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2033735] [NEW] [mantic] New 6.5.0.2 kernel + Intel GPU = no HDMI
Public bug reported: Hi, Legion laptop with Nvidia. - Nouveau : no hdmi - Nvidia 535 dynamic graphics : no HDMI (screen not detected) - Nvidia 535 discrete graphics : HDMI is detected So I suppose this bug to be linked to Intel GPU. All was ok with previous 6.3 kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2033735 Title: [mantic] New 6.5.0.2 kernel + Intel GPU = no HDMI Status in linux package in Ubuntu: New Bug description: Hi, Legion laptop with Nvidia. - Nouveau : no hdmi - Nvidia 535 dynamic graphics : no HDMI (screen not detected) - Nvidia 535 discrete graphics : HDMI is detected So I suppose this bug to be linked to Intel GPU. All was ok with previous 6.3 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033735/+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
The legacy flag only works when you also set a model, for me the model dell-headset-multi works. You have to shutdown the system completely after setting these options. When you have done that you should be able to reboot without locking up. The logs will still contain errors though. -- 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
