[Kernel-packages] [Bug 1940730] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1: bcmwl kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1940730 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: Sorry. I have got no idea what is this bug is about. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-27-generic Date: Sat Aug 21 13:22:34 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu7~20.04.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-08-20 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 6.30.223.271+bdcom-0ubuntu7~20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1940730/+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 1930188] Re: Acer Aspire 5 sound driver issues
Hello, regarding the latest SRU Justification for alsa-ucm-conf Isn't it normal to have separate microphone volume and mic boost. Currently I have mic volume on 100% and mic boost on 20db gain. It's just like windows where microphone volume and mic boost is separate. We just don't have UI for it need to change using alsamixer. With latest ubuntu official kernel mic boost has 4 levels just like windows now 0db, 10db, 20db, 30db. Anything above 20db causes too much noise. So, if mic volume and boost was to be tied so that both changes it would be difficult to achieve what I am using right now. Maybe would be better to provide a UI to change mic boost independently. Just a suggestion, let me know if I got the change wrong. Thanks. -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
** Description changed: + SRU Justification for alsa-ucm-conf: + + [Impact] + On the machines with the sof audio driver, users could adjust the input + volume from UI, but this only adjusts the "Capture Volume", the "Mic + Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture + Volume" to max, the recorded volume is still very low. + + [Fix] + Backport a upstream patch, the patch adds the "Mic Boost" into the + ucm + + [Test] + plug a headset, make sure the headset-mic is the active input device, + adjust the input volume to %20, open a terminal and run alsamixer, + check the "Capture Volume" and "Mic Boost" value, then adjust the + input volume to 80%, check those values and we could see both values + are changed. + + [Where problems could occur] + This patch could make the parse of input volume control fail, then + the input volume can't be changed anymore when users adjust the + volume from UI. But this possibility is very low, I tested this patch + on many lenovo and dell machines with sof audio driver, all worked + well. + + + SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. - The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. -- You received this bug notification because you are a member of Kernel
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This is the debdiff of alsa-ucm-conf for focal. thx. ** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu0.11.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5525078/+files/alsa-ucm-conf_1.2.2-1ubuntu0.11.debdiff -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+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 1930188] Re: Acer Aspire 5 sound driver issues
This is the debdiff of alsa-ucm-conf for hirsute. thx. ** Patch added: "alsa-ucm-conf_1.2.4-2ubuntu1.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5525077/+files/alsa-ucm-conf_1.2.4-2ubuntu1.4.debdiff -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+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 1930188] Re: Acer Aspire 5 sound driver issues
This is the debdiff of alsa-ucm-conf for impish. thx. ** Changed in: linux (Ubuntu Impish) Status: Incomplete => Fix Released ** Patch added: "alsa-ucm-conf_1.2.4-2ubuntu5.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5525076/+files/alsa-ucm-conf_1.2.4-2ubuntu5.debdiff -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1930188] 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 1930188 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 ** Tags added: groovy -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one.
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
** No longer affects: alsa-ucm-conf (Ubuntu) ** Also affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Package changed: alsa-ucm-conf (Ubuntu) => linux (Ubuntu) -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+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 1930188] Re: Acer Aspire 5 sound driver issues
** Changed in: pulseaudio (Ubuntu) Status: New => In Progress ** Also affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** No longer affects: alsa-ucm-conf (Ubuntu) ** No longer affects: alsa-ucm-conf (Ubuntu Focal) ** No longer affects: alsa-ucm-conf (Ubuntu Hirsute) ** Also affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** No longer affects: alsa-ucm-conf (Ubuntu) ** Also 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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1943469] Re: sleep mode
Thanks for the bug report. The first thing to try is to unplug your peripherals (before sleeping) to see if it is any of them waking the machine up. ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943469 Title: sleep mode Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: computer "wakes up" from sleep mode after 1 second no matter if i wait the given time for it to sleep, or if i put it to sleep with terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 13 18:56:14 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [1043:16a0] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce 810M] [1043:137e] InstallationDate: Installed on 2021-07-30 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:b721 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541NC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=264f931b-e96b-44e9-a13d-bf5c3236a567 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541NC.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541NC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541NC.307:bd06/19/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX541NC:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX541NC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X541NC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943469/+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 1943469] [NEW] sleep mode
You have been subscribed to a public bug: computer "wakes up" from sleep mode after 1 second no matter if i wait the given time for it to sleep, or if i put it to sleep with terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 13 18:56:14 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [1043:16a0] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce 810M] [1043:137e] InstallationDate: Installed on 2021-07-30 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:b721 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541NC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=264f931b-e96b-44e9-a13d-bf5c3236a567 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541NC.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541NC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541NC.307:bd06/19/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX541NC:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX541NC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X541NC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal ubuntu -- sleep mode https://bugs.launchpad.net/bugs/1943469 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 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 1939966] Re: Random system stops
We should get some hints from the system log usually... Each time the crash happens please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. -- 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/1939966 Title: Random system stops Status in linux package in Ubuntu: Incomplete Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync
** Tags removed: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30 [921588.559081] ? kmem_cache_alloc+0x38e/0x440 [921588.559084] ? ext4_init_io_end+0x1f/0x50 [921588.559088] ext4_io_submit+0x4d/0x60 [921588.559091] ext4_writepages+0x2c6/0xcd0 [921588.559094] ? __schedule+0x454/0x8a0 [921588.559097] ? hrtimer_start_range_ns+0x1aa/0x2f0 [921588.559100] ? timerqueue_del+0x24/0x50
[Kernel-packages] [Bug 1940485] Re: thermald often limits CPU frequency while on AC
I've run that debugging script. Unfortunately, Launchpad currently OOPSes when I try to attach the output to the bug. I'll keep trying every now and then. The throttling did not occur during that test, and doesn't seem to have occurred while running the build of thermald from git, but this does not necessarily mean the bug doesn't still occur. I'll continue running the build of thermald from git. Should I catch it in the bug-state, I'll re-collect the output of that script. -- 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/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: Incomplete Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+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 1942935] 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 1942935 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 ** Tags added: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062]
[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync
** Also 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-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30 [921588.559081] ? kmem_cache_alloc+0x38e/0x440 [921588.559084] ? ext4_init_io_end+0x1f/0x50 [921588.559088] ext4_io_submit+0x4d/0x60 [921588.559091] ext4_writepages+0x2c6/0xcd0 [921588.559094] ? __schedule+0x454/0x8a0 [921588.559097] ? hrtimer_start_range_ns+0x1aa/0x2f0
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gkeop/5.4.0.1024.27)
All autopkgtests for the newly accepted linux-meta-gkeop (5.4.0.1024.27) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gkeop [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1939349] Re: frequent hangs with latest hirsute kernel (nvidia graphics)
The system has now been running stably for 6 days, which is an order of magnitude better than what I was experiencing since filing this bug report. I will at some point flip the firmware setting back to see how it behaves. Are there any other tests I should try? -- 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/1939349 Title: frequent hangs with latest hirsute kernel (nvidia graphics) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to the latest kernel, I am experiencing frequent kernel hangs. The system does not respond to Alt+SysRq, and I have to power it off. In some cases the hang happens before X has even been launched at boot. When it hangs, the fan spins up to full speed. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vorlon10452 F pulseaudio /dev/snd/controlC0: vorlon10452 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 9 14:15:58 2021 InstallationDate: Installed on 2019-12-23 (594 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_di672m@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_di672m ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2019 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET40W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN2OET40W(1.27):bd10/17/2019:br1.27:efr1.19:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vorlon 8854 F pulseaudio /dev/snd/controlC0: vorlon 8854 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2019-12-23 (600 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_di672m@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_di672m ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 Tags: hirsute Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild src sudo _MarkForUpload: True dmi.bios.date: 04/28/2021 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET52W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN2OET52W(1.39):bd04/28/2021:br1.39:efr1.22:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync
Here is Donald Buczek's reproducer script. I setup an Ubuntu 20.04 VM with latest linux-image-generic and was able to reproduce it within maybe 10 or 15 minutes. Exactly the same issue. Filesystem layout built as follows: # assemble raid devices mdadm --create /dev/md0 --level=1 --raid-devices=2 --spare-devices=1 /dev/sda2 /dev/sdb2 /dev/sdc2 mdadm --create /dev/md1 --level=5 --raid-devices=5 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 /dev/sde3 # create PVs, VGs, LVs pvcreate /dev/md1 vgcreate vg1 /dev/md1 lvcreate --name root --extents 100%FREE vg1 # create filesystems mkfs.ext4 /dev/md0 mkfs.ext4 /dev/vg1/root ** Attachment added: "mdhang.sh" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1942935/+attachment/5525050/+files/mdhang.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456]
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.4/5.4.0.1053.39)
All autopkgtests for the newly accepted linux-meta-gcp-5.4 (5.4.0.1053.39) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.51 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1786013] Autopkgtest regression report (linux-meta-gke/5.4.0.1053.63)
All autopkgtests for the newly accepted linux-meta-gke (5.4.0.1053.63) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gke [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1939966] Re: Random system stops
It's gotten to the point where this happens at least once a day. I'm lost for answers. -- 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/1939966 Title: Random system stops Status in linux package in Ubuntu: Incomplete Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939966/+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 1939966] Re: Random system stops
I recorded a video (using my phone) of what the computer looks like once the crash has happened: https://www.youtube.com/watch?v=36kg68mfrds -- 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/1939966 Title: Random system stops Status in linux package in Ubuntu: Incomplete Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke-5.4/5.4.0.1053.56~18.04.18)
All autopkgtests for the newly accepted linux-meta-gke-5.4 (5.4.0.1053.56~18.04.18) for bionic have finished running. The following regressions have been reported in tests triggered by the package: kpatch/0.5.0-0ubuntu1.1 (amd64) systemd/unknown (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gke-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1937078] Re: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Hi, Tim. I'm dropping the 5.4 backport from focal/linux-azure in the
current cycle because this commit is causing the boot to hang:
http://10.246.72.46:8080/view/all/job/focal-linux-azure-azure-
amd64-5.4.0-Standard_A2_v2-ubuntu_boot/4/console
I managed to reproduce the problem manually and reverting the commit
solved the problem.
** Changed in: linux-azure (Ubuntu Focal)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1937078
Title:
Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Status in linux-azure package in Ubuntu:
Incomplete
Status in linux-azure source package in Focal:
In Progress
Status in linux-azure source package in Hirsute:
Fix Committed
Bug description:
SRU Justification
[Impact]
Customers have degraded network performance on Hyper-V/Azure
This is a request to pick up a patch from the upstream, the patch
fixes an issue with Ubuntu as a hyper-v and Azure guest. This patch
need to get picked up for 20.04, 18.04. The link to the upstream patch
follows:
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-
fixes=7c9ff3d61b253715dcf968a6307af148c9b2
Description of issue and solution:
The vmbus module uses a rotational algorithm to assign target CPUs to
a device's channels. Depending on the timing of different device's channel
offers, different channels of a device may be assigned to the same CPU.
For example on a VM with 2 CPUs, if NIC A and B's channels are offered
in the following order, NIC A will have both channels on CPU0, and
NIC B will have both channels on CPU1 -- see below. This kind of
assignment causes RSS load that is spreading across different channels
to end up on the same CPU.
Timing of channel offers:
NIC A channel 0
NIC B channel 0
NIC A channel 1
NIC B channel 1
VMBUS ID 14: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {cab064cd-1f31-47d5-a8b4-9d57e320cccd}
Sysfs path: /sys/bus/vmbus/devices/cab064cd-1f31-47d5-a8b4-9d57e320cccd
Rel_ID=14, target_cpu=0
Rel_ID=17, target_cpu=0
VMBUS ID 16: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {244225ca-743e-4020-a17d-d7baa13d6cea}
Sysfs path: /sys/bus/vmbus/devices/244225ca-743e-4020-a17d-d7baa13d6cea
Rel_ID=16, target_cpu=1
Rel_ID=18, target_cpu=1
Update the vmbus CPU assignment algorithm to avoid duplicate CPU
assignments within a device.
The new algorithm iterates num_online_cpus + 1 times.
The existing rotational algorithm to find "next NUMA & CPU" is still here.
But if the resulting CPU is already used by the same device, it will try
the next CPU.
In the last iteration, it assigns the channel to the next available CPU
like the existing algorithm. This is not normally expected, because
during device probe, we limit the number of channels of a device to
be <= number of online CPUs.
[Test Plan]
This could be tough to test as the patch fixes a race condition.
[Where problems could occur]
Network performance issues could persist.
[Other Info]
SF:#00315347
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937078/+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 1786013] Autopkgtest regression report (linux-meta-gkeop-5.4/5.4.0.1024.25~18.04.25)
All autopkgtests for the newly accepted linux-meta-gkeop-5.4 (5.4.0.1024.25~18.04.25) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gkeop-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1938645] Re: Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol
Thanks for the feedback. Closing as requested. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1938645 Title: Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol Status in linux package in Ubuntu: Invalid Bug description: I use package Rhythembox as my MP3 player software. I also use Rhythebox to transfer audio to my Sony WalkMan MP3 player. Since moving to Xubuntu 20.04.2, it has gotten much harder to successfully transfer mp3 audio to the Sony WalkMan MP3 player. I checked in syslog... I see some errors I believe are related: Aug 1 10:39:54 jaakob kernel: [ 8079.675644] mtp[10045]: segfault at 8a ip 7f2754d6f623 sp 7f274cbb2f20 error 4 in libglib-2.0.so.0.6400.6[7f2754d1b000+84000] Aug 1 10:39:54 jaakob kernel: [ 8079.675648] Code: 0f 1f 80 00 00 00 00 48 c1 e8 04 4c 8b 3b 8d 48 ff 48 89 c5 49 89 ce 49 c1 e6 04 4d 01 f7 4d 8b 27 4d 85 e4 0f 84 cd 00 00 00 <49> 8b 44 24 08 48 85 c0 74 43 48 8b 10 49 89 54 24 08 49 89 c4 49 Aug 1 10:40:13 jaakob kernel: [ 8098.630114] usb 1-11.2: USB disconnect, device number 6 Aug 1 10:41:34 jaakob kernel: [ 8179.600470] usb 1-5: new high-speed USB device number 8 using xhci_hcd Aug 1 10:41:34 jaakob kernel: [ 8179.749115] usb 1-5: New USB device found, idVendor=054c, idProduct=0385, bcdDevice= 0.01 Aug 1 10:41:34 jaakob kernel: [ 8179.749121] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Aug 1 10:41:34 jaakob kernel: [ 8179.749124] usb 1-5: Product: WALKMAN Aug 1 10:41:34 jaakob kernel: [ 8179.749127] usb 1-5: Manufacturer: Sony Aug 1 10:41:34 jaakob kernel: [ 8179.749130] usb 1-5: SerialNumber: 10FA1355316092 Aug 1 10:41:34 jaakob kernel: [ 8179.750689] usb-storage 1-5:1.0: USB Mass Storage device detected Aug 1 10:41:34 jaakob kernel: [ 8179.751175] scsi host14: usb-storage 1-5:1.0 Aug 1 10:41:35 jaakob kernel: [ 8180.761332] scsi 14:0:0:0: Direct-Access SONY WALKMAN 1.00 PQ: 0 ANSI: 4 Aug 1 10:41:35 jaakob kernel: [ 8180.761875] sd 14:0:0:0: Attached scsi generic sg3 type 0 Aug 1 10:41:35 jaakob kernel: [ 8180.762889] sd 14:0:0:0: [sdb] 1917952 2048-byte logical blocks: (3.93 GB/3.66 GiB) Aug 1 10:41:35 jaakob kernel: [ 8180.763062] sd 14:0:0:0: [sdb] Write Protect is off Aug 1 10:41:35 jaakob kernel: [ 8180.763066] sd 14:0:0:0: [sdb] Mode Sense: 3e 00 00 00 Aug 1 10:41:35 jaakob kernel: [ 8180.763200] sd 14:0:0:0: [sdb] No Caching mode page found Aug 1 10:41:35 jaakob kernel: [ 8180.763206] sd 14:0:0:0: [sdb] Assuming drive cache: write through Aug 1 10:41:36 jaakob kernel: [ 8180.809779] sdb: sdb1 Aug 1 10:41:36 jaakob kernel: [ 8180.811198] sd 14:0:0:0: [sdb] Attached SCSI removable disk Aug 1 10:41:36 jaakob Thunar[7060]: Working directory "/home/mdlueck/[Invalid UTF-8]" does not exist. It won't be used when spawning "exo-open".Working directory "/home/mdlueck/[Invalid UTF-8]" does not exist. It won't be used when spawning "exo-open". Aug 1 10:41:36 jaakob Thunar[10184]: thunar-volman: Unknown block device type "disk". Aug 1 10:41:42 jaakob kernel: [ 8186.793656] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Aug 1 10:41:42 jaakob systemd[1]: Created slice system-clean\x2dmount\x2dpoint.slice. Aug 1 10:41:42 jaakob systemd[1]: Finished Clean the /media/mdlueck/WALKMAN mount point. Aug 1 10:41:42 jaakob udisksd[813]: Mounted /dev/sdb1 at /media/mdlueck/WALKMAN on behalf of uid 1000 Aug 1 10:41:42 jaakob dbus-daemon[1546]: [session uid=1000 pid=1546] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.83' (uid=1000 pid=7060 comm="/usr/bin/Thunar --daemon " label="unconfined") Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer atril-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer gnome-thumbnail-font --size %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob dbus-daemon[1546]: [session uid=1000 pid=1546] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1' Aug 1 10:43:07 jaakob kernel: [ 8272.638815] blk_update_request: I/O error, dev sdb, sector 32 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Aug 1 10:43:07 jaakob kernel: [ 8272.638818] Buffer I/O error on dev sdb1, logical block 1, lost async page write Aug 1 10:43:07 jaakob kernel: [ 8272.638822] blk_update_request: I/O error, dev sdb,
[Kernel-packages] [Bug 1943484] Re: Focal update: v5.4.141 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** 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: + v5.4.141 upstream stable release + from git://git.kernel.org/ -v5.4.141 upstream stable release -from git://git.kernel.org/ + KVM: SVM: Fix off-by-one indexing when nullifying last used SEV VMCB + tee: Correct inappropriate usage of TEE_SHM_DMA_BUF flag + media: v4l2-mem2mem: always consider OUTPUT queue during poll + tracing: Reject string operand in the histogram expression + usb: dwc3: Stop active transfers before halting the controller + usb: dwc3: gadget: Allow runtime suspend if UDC unbinded + usb: dwc3: gadget: Restart DWC3 gadget when enabling pullup + usb: dwc3: gadget: Prevent EP queuing while stopping transfers + usb: dwc3: gadget: Clear DEP flags after stop transfers in ep disable + usb: dwc3: gadget: Disable gadget IRQ during pullup disable + usb: dwc3: gadget: Avoid runtime resume if disabling pullup + KVM: X86: MMU: Use the correct inherited permissions to get shadow page + USB:ehci:fix Kunpeng920 ehci hardware problem + ALSA: hda: Add quirk for ASUS Flow x13 + ppp: Fix generating ppp unit id when ifname is not specified + ovl: prevent private clone if bind mount is not allowed + btrfs: make qgroup_free_reserved_data take btrfs_inode + btrfs: make btrfs_qgroup_reserve_data take btrfs_inode + btrfs: qgroup: allow to unreserve range without releasing other ranges + btrfs: qgroup: try to flush qgroup space when we get -EDQUOT + btrfs: transaction: Cleanup unused TRANS_STATE_BLOCKED + btrfs: qgroup: remove ASYNC_COMMIT mechanism in favor of reserve retry-after-EDQUOT + btrfs: fix lockdep splat when enabling and disabling qgroups + net: xilinx_emaclite: Do not print real IOMEM pointer + btrfs: qgroup: don't commit transaction when we already hold the handle + btrfs: export and rename qgroup_reserve_meta + btrfs: don't flush from btrfs_delayed_inode_reserve_metadata + Linux 5.4.141 + UBUNTU: upstream stable to v5.4.141 -- 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/1943484 Title: Focal update: v5.4.141 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: 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: v5.4.141 upstream stable release from git://git.kernel.org/ KVM: SVM: Fix off-by-one indexing when nullifying last used SEV VMCB tee: Correct inappropriate usage of TEE_SHM_DMA_BUF flag media: v4l2-mem2mem: always consider OUTPUT queue during poll tracing: Reject string operand in the histogram expression usb: dwc3: Stop active transfers before halting the controller usb: dwc3: gadget: Allow runtime suspend if UDC unbinded usb: dwc3: gadget: Restart DWC3 gadget when enabling pullup usb: dwc3: gadget: Prevent EP queuing while stopping transfers usb: dwc3: gadget: Clear DEP flags after stop transfers in ep disable usb: dwc3: gadget: Disable gadget IRQ during pullup disable usb: dwc3: gadget: Avoid runtime resume if disabling pullup KVM: X86: MMU: Use the correct inherited permissions to get shadow page USB:ehci:fix Kunpeng920 ehci hardware problem ALSA: hda: Add quirk for ASUS Flow x13 ppp: Fix generating ppp unit id when ifname is not specified ovl: prevent private clone if bind mount is not allowed btrfs: make
[Kernel-packages] [Bug 1943484] [NEW] Focal update: v5.4.141 upstream stable release
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: v5.4.141 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) 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/1943484 Title: Focal update: v5.4.141 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New 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: v5.4.141 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943484/+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 1943104] Re: Kubuntu 21.04 Mainline Kernels Fail To Boot Using Nvidia 470.63.01
This is happening because the mainline kernels started getting built with CONFIG_UBSAN=y. Apparently, turning this on at build time inserts code at various points that helps identify undefined behaviour, and even though the runtime reporter is not on, the inserted code breaks the nvidia driver. If you build your own kernel without the option, things work fine. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed ** Summary changed: - Kubuntu 21.04 Mainline Kernels Fail To Boot Using Nvidia 470.63.01 + Recent Mainline Kernels with CONFIG_UBSAN=y Fail To Boot Using Nvidia 470.63.01 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1943104 Title: Recent Mainline Kernels with CONFIG_UBSAN=y Fail To Boot Using Nvidia 470.63.01 Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: Kubuntu 21.04 Nvidia 470.63.01 Installing mainline kernel using UKUU from https://kernel.ubuntu.com/~kernel-ppa/mainline/ All mainline kernels installed since upgrading to Nvidia 470.63.01 failing to boot though compile is without error. Splash screen blinks then is stuck at the point in the photo below. https://gyazo.com/a4aff411c1deb7bd1613e5740123dd5b Tried with the following kernels 5.13.13 5.14.0 5.14.1 5.14.2 Last good kernel was 5.14-rc7 which was compiled with previous Nvidia version 470.57.x Purge and reinstall makes zero difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1943104/+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 1786013] Autopkgtest regression report (linux-meta-snapdragon/4.15.0.1113.116)
All autopkgtests for the newly accepted linux-meta-snapdragon (4.15.0.1113.116) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-snapdragon [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1928352] Re: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 (In
** Summary changed: - package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 + package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 (Input/Output error) ** Summary changed: - package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 (Input/Output error) + package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 (Input/output error) -- 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/1928352 Title: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 (Input/output error) Status in linux package in Ubuntu: Confirmed Status in shim-signed package in Ubuntu: Confirmed Bug description: The installer crashed at the very end with a warning that my computer might fail to boot. It booted alright but after logging in I get a pop-up to signal that shim-signed has failed to install. Something to do with my system (EFI) running in insecure mode? ProblemType: Package DistroRelease: Ubuntu 21.04 Package: shim-signed 1.47+15.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootEFIContents: BOOTX64.CSV grub.cfg grubx64.efi mmx64.efi shimx64.efi CasperMD5CheckResult: pass Date: Thu May 13 16:54:46 2021 EFITables: mei 13 17:05:50 Selena kernel: efi: EFI v2.10 by American Megatrends mei 13 17:05:50 Selena kernel: efi: ACPI=0xba80b000 ACPI 2.0=0xba80b000 SMBIOS=0xf04c0 MOKvar=0xae8a2000 mei 13 17:05:50 Selena kernel: secureboot: Secure boot disabled mei 13 17:05:50 Selena kernel: secureboot: Secure boot disabled ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-05-13 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SecureBoot: 6 0 0 0 0 SourcePackage: shim-signed Title: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928352/+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 1943464] Re: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference
** Summary changed: - Reassign I/O Path of Mojave Port 1 before Port 2 causes NULL dereference + Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference ** Description changed: - After reassign RoCE CX5 Mojawe Card Pchid to another LPAR dmesg show + After reassign RoCE ConnectX-5 Card Pchid to another LPAR dmesg show under Ubuntu the following Error message Ubuntu 20.04.01 with updates oot@t35lp02:~# uname -a Linux t35lp02.lnxne.boe 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 17:41:33 UTC 2021 s390x s390x s390x GNU/Linux root@t35lp02:~# DMESG Output - - 761.778422] mlx5_core 0018:00:00.1: poll_health:715:(pid 0): Fatal error 1 detected + 761.778422] mlx5_core 0018:00:00.1: poll_health:715:(pid 0): Fatal error 1 detected [ 761.778432] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[0] 0x [ 761.778435] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[1] 0x [ 761.778437] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[2] 0x [ 761.778439] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[3] 0x [ 761.778442] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[4] 0x [ 761.778444] mlx5_core 0018:00:00.1: print_health_info:384:(pid 0): assert_exit_ptr 0x [ 761.778447] mlx5_core 0018:00:00.1: print_health_info:386:(pid 0): assert_callra 0x [ 761.778451] mlx5_core 0018:00:00.1: print_health_info:389:(pid 0): fw_ver 65535.65535.65535 [ 761.778454] mlx5_core 0018:00:00.1: print_health_info:390:(pid 0): hw_id 0x [ 761.778456] mlx5_core 0018:00:00.1: print_health_info:391:(pid 0): irisc_index 255 [ 761.778460] mlx5_core 0018:00:00.1: print_health_info:392:(pid 0): synd 0xff: unrecognized error [ 761.778462] mlx5_core 0018:00:00.1: print_health_info:394:(pid 0): ext_synd 0x [ 761.778465] mlx5_core 0018:00:00.1: print_health_info:396:(pid 0): raw fw_ver 0x [ 761.778467] mlx5_core 0018:00:00.1: mlx5_trigger_health_work:696:(pid 0): new health works are not permitted at this stage [ 763.179016] mlx5_core 0018:00:00.1: E-Switch: cleanup [ 768.348431] mlx5_core 0018:00:00.1: mlx5_reclaim_startup_pages:562:(pid 123): FW did not return all pages. giving up... [ 768.348433] [ cut here ] [ 768.348434] FW pages counter is 43318 after reclaiming all pages [ 768.348562] WARNING: CPU: 0 PID: 123 at drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c:567 mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core] [ 768.348563] Modules linked in: s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time mlx5_ib ib_uverbs ib_core pkey qeth_l2 zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 mlx5_core sha256_s390 sha1_s390 sha_common tls mlxfw ptp pps_core zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 768.348586] CPU: 0 PID: 123 Comm: kmcheck Tainted: GW 5.4.0-80-generic #90-Ubuntu [ 768.348586] Hardware name: IBM 8561 T01 703 (LPAR) [ 768.348587] Krnl PSW : 0704c0018000 03ff808d33ac (mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core]) [ 768.348607]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 768.348608] Krnl GPRS: 0004 0006 0034 0007 [ 768.348608]0007 fcb4fa00 007b 03e00458fafc [ 768.348609]b7d406f0 4d849c00 b7d00120 0001b6c0 [ 768.348610]f4cb1100 03e00458fe70 03ff808d33a8 03e00458fa50 [ 768.348615] Krnl Code: 03ff808d339c: c0241043larl %r2,03ff80955422 - 03ff808d33a2: c0e570c7brasl %r14,03ff808c1530 - #03ff808d33a8: a7f40001brc 15,03ff808d33aa - >03ff808d33ac: e330a5f04012lt %r3,263664(%r10) - 03ff808d33b2: a784ffd7brc 8,03ff808d3360 - 03ff808d33b6: b9140033lgfr %r3,%r3 - 03ff808d33ba: c024104elarl %r2,03ff80955456 - 03ff808d33c0: c0e570b8brasl %r14,03ff808c1530 + 03ff808d33a2: c0e570c7brasl %r14,03ff808c1530 + #03ff808d33a8: a7f40001brc
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
@tuxinvader @k3dar7 many thanks for the replies. Yes, I installed packages from mainline. Sorry, I thought this bug report is for mainline packages. Now I did see your PPA through AskUbuntu thread but is it just for "Focal" or from your PPA, I can install kernels in Hirsute too? -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
Sorry for the wait, I took a few days off. This kernel worked well. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5525012/+files/journalctl.log -- 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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected Status in linux package in Ubuntu: Confirmed Bug description: Hello, My laptop run well with last 5.4 linux kernel even if I connect my thunderbolt dock. When trying to boot with 5.11.0-25 or 5.11.0-27 (hwe) kernel with dock and 2 monitors connected, the kernel panic after 3 or 4 seconds. Without the dock, he work fine. After a lot of try, I was able to boot sometime on 5.11 with the dock, but randomly and only if I only connect 1 extra monitor (I usually use two). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jmaillar 1988 F pulseaudio /dev/snd/controlC1: jmaillar 1988 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 EcryptfsInUse: Yes HibernationDevice: RESUME=none MachineType: Dell Inc. Precision 7530 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=b21fab6e-02fe-4295-a308-9da15f339a36 ro ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-27-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-20 (483 days ago) UserGroups: adm audio cdrom dip disk input kismet kvm libvirt libvirtd lpadmin lxd netdev plugdev sambashare sudo systemd-network users vboxusers video wireshark _MarkForUpload: True dmi.bios.date: 05/25/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.1 dmi.board.name: 0425K7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.1:bd05/25/2021:br1.16:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn0425K7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7530 dmi.product.sku: 0831 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: 2015-11-27T14:42:56.796345 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+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 1942952] Re: Kernel Call Trace on Secure Boot
I downgraded to 20.04 LTS and 5.8 kernel. So far, it seems more reliable than the 5.11 kernel. The watchdog_thresh is default 10. -- 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/1942952 Title: Kernel Call Trace on Secure Boot Status in linux package in Ubuntu: Incomplete Bug description: Could the call traces in dmesg be related to UEFI secure boot? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 948 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Sep 7 21:05:54 2021 InstallationDate: Installed on 2021-09-06 (1 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M |__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic root=/dev/mapper/vgkubuntu-root ro ipv6.disable=1 elevator=deadline splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 15.63 dmi.bios.vendor: Insyde dmi.bios.version: F.63 dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 76.32 dmi.modalias: dmi:bvnInsyde:bvrF.63:bd03/25/2021:br15.63:efr76.32:svnHP:pn:pvr:sku:rvnHP:rn84B6:rvrKBCVersion76.32:cvnHP:ct10:cvrChassisVersion: dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942952/+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 1942935] Re: kernel io hangs during mdcheck/resync
The patch hasn't made it into mainline from what I have seen, it looks like it died back in March waiting for feedback from additional kernel developers. From what I have gathered this is a deadlock scenario directly caused by pausing the resync while the system is under heavy write activity. Donald Buczek provided a reproducer which is a shell script that generates a lot of write activity and pauses/resumes the raid scrubbing. And he also provided a workaround to get the stuck system running without reboot: echo active > /sys/block/md1/md/array_state I haven't tried the patch or any of this, I pretty much eliminated the trigger which is mdcheck_start & mdcheck_continue and went back to the 18.04 LTS way of scrubbing arrays (which is basically don't pause/interrupt it once it starts). I ran through a checkarray yesterday to 100%, no problems. Meanwhile since upgrading to 20.04 LTS it has hung almost every single time through 5.4, 5.8, and 5.11 kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032]
[Kernel-packages] [Bug 1943160] Re: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.
This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu2
---
nvidia-settings (470.57.01-0ubuntu2) impish; urgency=medium
* debian/patches/17_do_not_read_config_on_power_saving_mode.patch:
- Do not read config on Power Saving mode. (LP: #1943160).
-- Shengyao Xue Fri, 10 Sep 2021 00:42:38
+0800
** Changed in: nvidia-settings (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1943160
Title:
[SRU] It will take about 90+ seconds to open the 'Nvidia settings' app
when 'Power Saving mode' running.
Status in OEM Priority Project:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-settings source package in Focal:
In Progress
Bug description:
[Impact]
On some I+N configs, It will take about 90+ seconds to open the 'Nvidia
settings' window when 'Power Saving mode' running.
[Fix]
do not read config file if Nvidia driver did not loaded:
change nvidia-settings/src/nvidia-settings.c
if (!op->no_load) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, , );
to
if (!op->no_load && systems.n != 0) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, , );
[Test]
1. Install Ubuntu image.
2. Boot and login the system.
3. Open 'Nvidia Settings' app
4. Select the prime is 'Power saving' mode
5. Reboot system and login
6. Open 'Nvidia Settings' app
7. Verify the result
[Where problems will occur]
the "systems.n" gets from
NvCtrlConnectToSystem(op->ctrl_display, );
If there is a possibility that systems.n is zero and we still need to read
nvidia config file, then it will be a problem. I tried and cannot find a
situation like that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943160/+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 1938645] Re: Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol
The solution to this issue was documented in my #3 comment. The misleading error messages coming from Linux were indicating that it was time to fresh reformat the MP3 player and start over. Once done, no issues. This defect report may be close. Thank you. -- 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/1938645 Title: Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol Status in linux package in Ubuntu: Incomplete Bug description: I use package Rhythembox as my MP3 player software. I also use Rhythebox to transfer audio to my Sony WalkMan MP3 player. Since moving to Xubuntu 20.04.2, it has gotten much harder to successfully transfer mp3 audio to the Sony WalkMan MP3 player. I checked in syslog... I see some errors I believe are related: Aug 1 10:39:54 jaakob kernel: [ 8079.675644] mtp[10045]: segfault at 8a ip 7f2754d6f623 sp 7f274cbb2f20 error 4 in libglib-2.0.so.0.6400.6[7f2754d1b000+84000] Aug 1 10:39:54 jaakob kernel: [ 8079.675648] Code: 0f 1f 80 00 00 00 00 48 c1 e8 04 4c 8b 3b 8d 48 ff 48 89 c5 49 89 ce 49 c1 e6 04 4d 01 f7 4d 8b 27 4d 85 e4 0f 84 cd 00 00 00 <49> 8b 44 24 08 48 85 c0 74 43 48 8b 10 49 89 54 24 08 49 89 c4 49 Aug 1 10:40:13 jaakob kernel: [ 8098.630114] usb 1-11.2: USB disconnect, device number 6 Aug 1 10:41:34 jaakob kernel: [ 8179.600470] usb 1-5: new high-speed USB device number 8 using xhci_hcd Aug 1 10:41:34 jaakob kernel: [ 8179.749115] usb 1-5: New USB device found, idVendor=054c, idProduct=0385, bcdDevice= 0.01 Aug 1 10:41:34 jaakob kernel: [ 8179.749121] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Aug 1 10:41:34 jaakob kernel: [ 8179.749124] usb 1-5: Product: WALKMAN Aug 1 10:41:34 jaakob kernel: [ 8179.749127] usb 1-5: Manufacturer: Sony Aug 1 10:41:34 jaakob kernel: [ 8179.749130] usb 1-5: SerialNumber: 10FA1355316092 Aug 1 10:41:34 jaakob kernel: [ 8179.750689] usb-storage 1-5:1.0: USB Mass Storage device detected Aug 1 10:41:34 jaakob kernel: [ 8179.751175] scsi host14: usb-storage 1-5:1.0 Aug 1 10:41:35 jaakob kernel: [ 8180.761332] scsi 14:0:0:0: Direct-Access SONY WALKMAN 1.00 PQ: 0 ANSI: 4 Aug 1 10:41:35 jaakob kernel: [ 8180.761875] sd 14:0:0:0: Attached scsi generic sg3 type 0 Aug 1 10:41:35 jaakob kernel: [ 8180.762889] sd 14:0:0:0: [sdb] 1917952 2048-byte logical blocks: (3.93 GB/3.66 GiB) Aug 1 10:41:35 jaakob kernel: [ 8180.763062] sd 14:0:0:0: [sdb] Write Protect is off Aug 1 10:41:35 jaakob kernel: [ 8180.763066] sd 14:0:0:0: [sdb] Mode Sense: 3e 00 00 00 Aug 1 10:41:35 jaakob kernel: [ 8180.763200] sd 14:0:0:0: [sdb] No Caching mode page found Aug 1 10:41:35 jaakob kernel: [ 8180.763206] sd 14:0:0:0: [sdb] Assuming drive cache: write through Aug 1 10:41:36 jaakob kernel: [ 8180.809779] sdb: sdb1 Aug 1 10:41:36 jaakob kernel: [ 8180.811198] sd 14:0:0:0: [sdb] Attached SCSI removable disk Aug 1 10:41:36 jaakob Thunar[7060]: Working directory "/home/mdlueck/[Invalid UTF-8]" does not exist. It won't be used when spawning "exo-open".Working directory "/home/mdlueck/[Invalid UTF-8]" does not exist. It won't be used when spawning "exo-open". Aug 1 10:41:36 jaakob Thunar[10184]: thunar-volman: Unknown block device type "disk". Aug 1 10:41:42 jaakob kernel: [ 8186.793656] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Aug 1 10:41:42 jaakob systemd[1]: Created slice system-clean\x2dmount\x2dpoint.slice. Aug 1 10:41:42 jaakob systemd[1]: Finished Clean the /media/mdlueck/WALKMAN mount point. Aug 1 10:41:42 jaakob udisksd[813]: Mounted /dev/sdb1 at /media/mdlueck/WALKMAN on behalf of uid 1000 Aug 1 10:41:42 jaakob dbus-daemon[1546]: [session uid=1000 pid=1546] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.83' (uid=1000 pid=7060 comm="/usr/bin/Thunar --daemon " label="unconfined") Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer atril-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer gnome-thumbnail-font --size %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob dbus-daemon[1546]: [session uid=1000 pid=1546] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1' Aug 1 10:43:07 jaakob kernel: [ 8272.638815] blk_update_request: I/O error, dev sdb, sector 32 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Aug 1 10:43:07 jaakob kernel: [ 8272.638818] Buffer I/O
[Kernel-packages] [Bug 1942633] Re: Can not boot impish in Cavium ThunderX
For the CRB1S systems, the following is the firmware string that matters, and it shows that phanpy is running the latest (and very likely final) version: BIOS Date: 06/14/2018 14:42:48 Ver: 0ACGA022 Note that this is also reproducible on our Gigabyte R120 systems which use acpi=force by default, which suggests this is not a device tree problem. I can reproduce with upstream v5.13, and I've a bisect between that and v5.11 in progress. -- 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/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Confirmed Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+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 1943464] Re: Reassign I/O Path of Mojave Port 1 before Port 2 causes NULL dereference
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-z-systems Importance: Undecided => Low -- 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/1943464 Title: Reassign I/O Path of Mojave Port 1 before Port 2 causes NULL dereference Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: After reassign RoCE CX5 Mojawe Card Pchid to another LPAR dmesg show under Ubuntu the following Error message Ubuntu 20.04.01 with updates oot@t35lp02:~# uname -a Linux t35lp02.lnxne.boe 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 17:41:33 UTC 2021 s390x s390x s390x GNU/Linux root@t35lp02:~# DMESG Output 761.778422] mlx5_core 0018:00:00.1: poll_health:715:(pid 0): Fatal error 1 detected [ 761.778432] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[0] 0x [ 761.778435] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[1] 0x [ 761.778437] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[2] 0x [ 761.778439] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[3] 0x [ 761.778442] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[4] 0x [ 761.778444] mlx5_core 0018:00:00.1: print_health_info:384:(pid 0): assert_exit_ptr 0x [ 761.778447] mlx5_core 0018:00:00.1: print_health_info:386:(pid 0): assert_callra 0x [ 761.778451] mlx5_core 0018:00:00.1: print_health_info:389:(pid 0): fw_ver 65535.65535.65535 [ 761.778454] mlx5_core 0018:00:00.1: print_health_info:390:(pid 0): hw_id 0x [ 761.778456] mlx5_core 0018:00:00.1: print_health_info:391:(pid 0): irisc_index 255 [ 761.778460] mlx5_core 0018:00:00.1: print_health_info:392:(pid 0): synd 0xff: unrecognized error [ 761.778462] mlx5_core 0018:00:00.1: print_health_info:394:(pid 0): ext_synd 0x [ 761.778465] mlx5_core 0018:00:00.1: print_health_info:396:(pid 0): raw fw_ver 0x [ 761.778467] mlx5_core 0018:00:00.1: mlx5_trigger_health_work:696:(pid 0): new health works are not permitted at this stage [ 763.179016] mlx5_core 0018:00:00.1: E-Switch: cleanup [ 768.348431] mlx5_core 0018:00:00.1: mlx5_reclaim_startup_pages:562:(pid 123): FW did not return all pages. giving up... [ 768.348433] [ cut here ] [ 768.348434] FW pages counter is 43318 after reclaiming all pages [ 768.348562] WARNING: CPU: 0 PID: 123 at drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c:567 mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core] [ 768.348563] Modules linked in: s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time mlx5_ib ib_uverbs ib_core pkey qeth_l2 zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 mlx5_core sha256_s390 sha1_s390 sha_common tls mlxfw ptp pps_core zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 768.348586] CPU: 0 PID: 123 Comm: kmcheck Tainted: GW 5.4.0-80-generic #90-Ubuntu [ 768.348586] Hardware name: IBM 8561 T01 703 (LPAR) [ 768.348587] Krnl PSW : 0704c0018000 03ff808d33ac (mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core]) [ 768.348607]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 768.348608] Krnl GPRS: 0004 0006 0034 0007 [ 768.348608]0007 fcb4fa00 007b 03e00458fafc [ 768.348609]b7d406f0 4d849c00 b7d00120 0001b6c0 [ 768.348610]f4cb1100 03e00458fe70 03ff808d33a8 03e00458fa50 [ 768.348615] Krnl Code: 03ff808d339c: c0241043larl %r2,03ff80955422 03ff808d33a2: c0e570c7brasl %r14,03ff808c1530 #03ff808d33a8: a7f40001brc 15,03ff808d33aa >03ff808d33ac: e330a5f04012lt %r3,263664(%r10) 03ff808d33b2: a784ffd7brc 8,03ff808d3360 03ff808d33b6: b9140033lgfr %r3,%r3 03ff808d33ba: c024104elarl
[Kernel-packages] [Bug 1943421] Re: Error while enabling somerville driver: package linux-oem-5.13-headers-5.13.0-1010 (not installed) failed to install/upgrade: unable to open "/usr/src/linux-oem-5.1
Closing, as I discovered that the root cause was interference from my antivirus (Sophos). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1943421 Title: Error while enabling somerville driver: package linux- oem-5.13-headers-5.13.0-1010 (not installed) failed to install/upgrade: unable to open "/usr/src/linux- oem-5.13-headers-5.13.0-1010/sound/soc/jz4740/Kconfig.dpkg-new" Status in linux-oem-5.13 package in Ubuntu: Invalid Bug description: I'm trying to install Ubuntu 20.04.3 on a brand new Dell 7520, which is equipped with: * 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz × 8 * Intel Iris XE GPU (reported as Mesa Intel® Xe Graphics (TGL GT2)) Since on my first try I was getting a lot of SEGFAULTS, I repeated the installation without enabling 3rd party drivers, and all went smoothly, apart from the fan pushing a lot. This morning I tried to enable the drivers from the Ubuntu dedicated windows, and it started raining errors on me, like the one reported in the title. It seems that the kernel (5.13 OEM or HWE) and or the Intel (somerville) drivers are acting crazy. I can say that the freezes occur on two different laptop of the same kind, just after a fresh install and when using stuff like a browser, that leverages a bit the GPU. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-oem-5.13-headers-5.13.0-1010 (not installed) ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46 Uname: Linux 5.10.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 13 09:55:18 2021 ErrorMessage: impossibile aprire "/usr/src/linux-oem-5.13-headers-5.13.0-1010/sound/soc/jz4740/Kconfig.dpkg-new": Operazione non permessa InstallationDate: Installed on 2021-07-21 (53 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-oem-5.13 Title: package linux-oem-5.13-headers-5.13.0-1010 (not installed) failed to install/upgrade: impossibile aprire "/usr/src/linux-oem-5.13-headers-5.13.0-1010/sound/soc/jz4740/Kconfig.dpkg-new": Operazione non permessa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1943421/+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 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
@jagsdesai both #81 #57 still work with 5.14.3, installed yesterday on Xubuntu 20.04 ;-) -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1943464] [NEW] Reassign I/O Path of Mojave Port 1 before Port 2 causes NULL dereference
Public bug reported: After reassign RoCE CX5 Mojawe Card Pchid to another LPAR dmesg show under Ubuntu the following Error message Ubuntu 20.04.01 with updates oot@t35lp02:~# uname -a Linux t35lp02.lnxne.boe 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 17:41:33 UTC 2021 s390x s390x s390x GNU/Linux root@t35lp02:~# DMESG Output 761.778422] mlx5_core 0018:00:00.1: poll_health:715:(pid 0): Fatal error 1 detected [ 761.778432] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[0] 0x [ 761.778435] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[1] 0x [ 761.778437] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[2] 0x [ 761.778439] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[3] 0x [ 761.778442] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[4] 0x [ 761.778444] mlx5_core 0018:00:00.1: print_health_info:384:(pid 0): assert_exit_ptr 0x [ 761.778447] mlx5_core 0018:00:00.1: print_health_info:386:(pid 0): assert_callra 0x [ 761.778451] mlx5_core 0018:00:00.1: print_health_info:389:(pid 0): fw_ver 65535.65535.65535 [ 761.778454] mlx5_core 0018:00:00.1: print_health_info:390:(pid 0): hw_id 0x [ 761.778456] mlx5_core 0018:00:00.1: print_health_info:391:(pid 0): irisc_index 255 [ 761.778460] mlx5_core 0018:00:00.1: print_health_info:392:(pid 0): synd 0xff: unrecognized error [ 761.778462] mlx5_core 0018:00:00.1: print_health_info:394:(pid 0): ext_synd 0x [ 761.778465] mlx5_core 0018:00:00.1: print_health_info:396:(pid 0): raw fw_ver 0x [ 761.778467] mlx5_core 0018:00:00.1: mlx5_trigger_health_work:696:(pid 0): new health works are not permitted at this stage [ 763.179016] mlx5_core 0018:00:00.1: E-Switch: cleanup [ 768.348431] mlx5_core 0018:00:00.1: mlx5_reclaim_startup_pages:562:(pid 123): FW did not return all pages. giving up... [ 768.348433] [ cut here ] [ 768.348434] FW pages counter is 43318 after reclaiming all pages [ 768.348562] WARNING: CPU: 0 PID: 123 at drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c:567 mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core] [ 768.348563] Modules linked in: s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time mlx5_ib ib_uverbs ib_core pkey qeth_l2 zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 mlx5_core sha256_s390 sha1_s390 sha_common tls mlxfw ptp pps_core zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 768.348586] CPU: 0 PID: 123 Comm: kmcheck Tainted: GW 5.4.0-80-generic #90-Ubuntu [ 768.348586] Hardware name: IBM 8561 T01 703 (LPAR) [ 768.348587] Krnl PSW : 0704c0018000 03ff808d33ac (mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core]) [ 768.348607]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 768.348608] Krnl GPRS: 0004 0006 0034 0007 [ 768.348608]0007 fcb4fa00 007b 03e00458fafc [ 768.348609]b7d406f0 4d849c00 b7d00120 0001b6c0 [ 768.348610]f4cb1100 03e00458fe70 03ff808d33a8 03e00458fa50 [ 768.348615] Krnl Code: 03ff808d339c: c0241043larl %r2,03ff80955422 03ff808d33a2: c0e570c7brasl %r14,03ff808c1530 #03ff808d33a8: a7f40001brc 15,03ff808d33aa >03ff808d33ac: e330a5f04012lt %r3,263664(%r10) 03ff808d33b2: a784ffd7brc 8,03ff808d3360 03ff808d33b6: b9140033lgfr%r3,%r3 03ff808d33ba: c024104elarl %r2,03ff80955456 03ff808d33c0: c0e570b8brasl %r14,03ff808c1530 [ 768.348622] Call Trace: [ 768.348641] ([<03ff808d33a8>] mlx5_reclaim_startup_pages+0x128/0x1c0 [mlx5_core]) [ 768.348661] [<03ff808c8e14>] mlx5_function_teardown+0x44/0xa0 [mlx5_core] [ 768.348680] [<03ff808c95b0>] mlx5_unload_one+0x80/0x160 [mlx5_core] [ 768.348699] [<03ff808c9720>] remove_one+0x50/0xd0 [mlx5_core] [ 768.348702] [<4d2704c0>] pci_device_remove+0x40/0xa0 [ 768.348706] [<4d2f724e>] device_release_driver_internal+0xee/0x1c0 [ 768.348707] [<4d267054>] pci_stop_bus_device+0x94/0xc0 [ 768.348708] [<4d267210>]
[Kernel-packages] [Bug 1943464] [NEW] Reassign I/O Path of Mojave Port 1 before Port 2 causes NULL dereference
You have been subscribed to a public bug: After reassign RoCE CX5 Mojawe Card Pchid to another LPAR dmesg show under Ubuntu the following Error message Ubuntu 20.04.01 with updates oot@t35lp02:~# uname -a Linux t35lp02.lnxne.boe 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 17:41:33 UTC 2021 s390x s390x s390x GNU/Linux root@t35lp02:~# DMESG Output 761.778422] mlx5_core 0018:00:00.1: poll_health:715:(pid 0): Fatal error 1 detected [ 761.778432] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[0] 0x [ 761.778435] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[1] 0x [ 761.778437] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[2] 0x [ 761.778439] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[3] 0x [ 761.778442] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[4] 0x [ 761.778444] mlx5_core 0018:00:00.1: print_health_info:384:(pid 0): assert_exit_ptr 0x [ 761.778447] mlx5_core 0018:00:00.1: print_health_info:386:(pid 0): assert_callra 0x [ 761.778451] mlx5_core 0018:00:00.1: print_health_info:389:(pid 0): fw_ver 65535.65535.65535 [ 761.778454] mlx5_core 0018:00:00.1: print_health_info:390:(pid 0): hw_id 0x [ 761.778456] mlx5_core 0018:00:00.1: print_health_info:391:(pid 0): irisc_index 255 [ 761.778460] mlx5_core 0018:00:00.1: print_health_info:392:(pid 0): synd 0xff: unrecognized error [ 761.778462] mlx5_core 0018:00:00.1: print_health_info:394:(pid 0): ext_synd 0x [ 761.778465] mlx5_core 0018:00:00.1: print_health_info:396:(pid 0): raw fw_ver 0x [ 761.778467] mlx5_core 0018:00:00.1: mlx5_trigger_health_work:696:(pid 0): new health works are not permitted at this stage [ 763.179016] mlx5_core 0018:00:00.1: E-Switch: cleanup [ 768.348431] mlx5_core 0018:00:00.1: mlx5_reclaim_startup_pages:562:(pid 123): FW did not return all pages. giving up... [ 768.348433] [ cut here ] [ 768.348434] FW pages counter is 43318 after reclaiming all pages [ 768.348562] WARNING: CPU: 0 PID: 123 at drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c:567 mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core] [ 768.348563] Modules linked in: s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time mlx5_ib ib_uverbs ib_core pkey qeth_l2 zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 mlx5_core sha256_s390 sha1_s390 sha_common tls mlxfw ptp pps_core zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 768.348586] CPU: 0 PID: 123 Comm: kmcheck Tainted: GW 5.4.0-80-generic #90-Ubuntu [ 768.348586] Hardware name: IBM 8561 T01 703 (LPAR) [ 768.348587] Krnl PSW : 0704c0018000 03ff808d33ac (mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core]) [ 768.348607]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 768.348608] Krnl GPRS: 0004 0006 0034 0007 [ 768.348608]0007 fcb4fa00 007b 03e00458fafc [ 768.348609]b7d406f0 4d849c00 b7d00120 0001b6c0 [ 768.348610]f4cb1100 03e00458fe70 03ff808d33a8 03e00458fa50 [ 768.348615] Krnl Code: 03ff808d339c: c0241043larl %r2,03ff80955422 03ff808d33a2: c0e570c7brasl %r14,03ff808c1530 #03ff808d33a8: a7f40001brc 15,03ff808d33aa >03ff808d33ac: e330a5f04012lt %r3,263664(%r10) 03ff808d33b2: a784ffd7brc 8,03ff808d3360 03ff808d33b6: b9140033lgfr%r3,%r3 03ff808d33ba: c024104elarl %r2,03ff80955456 03ff808d33c0: c0e570b8brasl %r14,03ff808c1530 [ 768.348622] Call Trace: [ 768.348641] ([<03ff808d33a8>] mlx5_reclaim_startup_pages+0x128/0x1c0 [mlx5_core]) [ 768.348661] [<03ff808c8e14>] mlx5_function_teardown+0x44/0xa0 [mlx5_core] [ 768.348680] [<03ff808c95b0>] mlx5_unload_one+0x80/0x160 [mlx5_core] [ 768.348699] [<03ff808c9720>] remove_one+0x50/0xd0 [mlx5_core] [ 768.348702] [<4d2704c0>] pci_device_remove+0x40/0xa0 [ 768.348706] [<4d2f724e>] device_release_driver_internal+0xee/0x1c0 [ 768.348707] [<4d267054>] pci_stop_bus_device+0x94/0xc0 [ 768.348708] [<4d267210>]
[Kernel-packages] [Bug 1943287] 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 1943287 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 ** Tags added: hirsute -- 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/1943287 Title: Can't start qemu on linux-5.14.2-051402-lowlatency Status in linux package in Ubuntu: Incomplete Bug description: After installing kernel package linux-image- unsigned-5.14.2-051402-lowlatency from https://kernel.ubuntu.com/~kernel-ppa/mainline/ starting libvirtd, and thus qemu, results in 2 stack traces. Then libvirtd stops. Rolling back to 5.11.0-34-lowlatency fixes the problem. sep 10 17:07:37 kernel: invalid opcode: [#3] PREEMPT SMP NOPTI sep 10 17:07:37 kernel: CPU: 8 PID: 21670 Comm: daemon-init Tainted: G D W 5.14.2-051402-lowlatency #202109080331 sep 10 17:07:37 kernel: Hardware name: Supermicro C9X299-PG300F/C9X299-PG300F, BIOS 2.1 06/16/2020 sep 10 17:07:37 kernel: RIP: 0010:vmx_create_vcpu+0x6a7/0x6f0 [kvm_intel] sep 10 17:07:37 kernel: Code: 89 e7 48 8d 75 cc ba 04 00 00 00 e8 c3 58 fb d1 85 c0 74 d7 4c 89 ff 4c 89 f3 41 bd f2 ff ff ff e8 fe d9 5f d2 e9 0b fd ff ff <0f> 0b 4c 89 ff 45 89 e5 e8 ec d9 5f d2 45 85 e4 0f 84 34 fb ff ff sep 10 17:07:37 kernel: RSP: 0018:b976caa0fc78 EFLAGS: 00010202 sep 10 17:07:37 kernel: RAX: 9fce6af99db0 RBX: 9fce6af98000 RCX: 0007 sep 10 17:07:37 kernel: RDX: 0006 RSI: 0001 RDI: 0122 sep 10 17:07:37 kernel: RBP: b976caa0fcb8 R08: R09: 9fce6afa1080 sep 10 17:07:37 kernel: R10: 0293 R11: 9fdd3fc33588 R12: 0007 sep 10 17:07:37 kernel: R13: fff4 R14: 9fce6af98000 R15: sep 10 17:07:37 kernel: FS: 7f75e8b79640() GS:9fdd3fc0() knlGS: sep 10 17:07:37 kernel: CS: 0010 DS: ES: CR0: 80050033 sep 10 17:07:37 kernel: CR2: 7f75f8dc2800 CR3: 000314c88005 CR4: 003726e0 sep 10 17:07:37 kernel: DR0: DR1: DR2: sep 10 17:07:37 kernel: DR3: DR6: fffe0ff0 DR7: 0400 sep 10 17:07:37 kernel: Call Trace: sep 10 17:07:37 kernel: kvm_arch_vcpu_create+0x288/0x390 [kvm] sep 10 17:07:37 kernel: kvm_vm_ioctl_create_vcpu+0x188/0x420 [kvm] sep 10 17:07:37 kernel: ? obj_cgroup_uncharge_pages+0x69/0xe0 sep 10 17:07:37 kernel: kvm_vm_ioctl+0x546/0x7b0 [kvm] sep 10 17:07:37 kernel: ? kvm_uevent_notify_change.part.0+0x17b/0x210 [kvm] sep 10 17:07:37 kernel: ? kfree+0x22a/0x3e0 sep 10 17:07:37 kernel: ? __fget_files+0x74/0xa0 sep 10 17:07:37 kernel: __x64_sys_ioctl+0x8e/0xc0 sep 10 17:07:37 kernel: do_syscall_64+0x59/0xc0 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 sep 10 17:07:37 kernel: ? syscall_exit_to_user_mode+0x27/0x50 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 sep 10 17:07:37 kernel: ? syscall_exit_to_user_mode+0x27/0x50 sep 10 17:07:37 kernel: ? __x64_sys_close+0x11/0x40 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 sep 10 17:07:37 kernel: ? syscall_exit_to_user_mode+0x27/0x50 sep 10 17:07:37 kernel: ? __x64_sys_read+0x19/0x20 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? asm_sysvec_apic_timer_interrupt+0xa/0x20 sep 10 17:07:37 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae sep 10 17:07:37 kernel: RIP: 0033:0x7f75f895aecb sep 10 17:07:37 kernel: Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6d 1f 0d 00 f7 d8 64 89 01 48 sep 10 17:07:37 kernel: RSP: 002b:7f75e8b78498 EFLAGS: 0246 ORIG_RAX: 0010 sep 10 17:07:37 kernel: RAX: ffda RBX: 7f75b02d1260 RCX: 7f75f895aecb sep 10 17:07:37 kernel: RDX: RSI: ae41 RDI: 0022 sep 10 17:07:37 kernel: RBP: 7f75e8b78510 R08: R09: sep 10 17:07:37 kernel: R10: R11: 0246 R12: sep 10
[Kernel-packages] [Bug 1943287] Re: Can't start qemu on linux-5.14.2-051402-lowlatency
** Package changed: ubuntu => linux (Ubuntu) -- 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/1943287 Title: Can't start qemu on linux-5.14.2-051402-lowlatency Status in linux package in Ubuntu: New Bug description: After installing kernel package linux-image- unsigned-5.14.2-051402-lowlatency from https://kernel.ubuntu.com/~kernel-ppa/mainline/ starting libvirtd, and thus qemu, results in 2 stack traces. Then libvirtd stops. Rolling back to 5.11.0-34-lowlatency fixes the problem. sep 10 17:07:37 kernel: invalid opcode: [#3] PREEMPT SMP NOPTI sep 10 17:07:37 kernel: CPU: 8 PID: 21670 Comm: daemon-init Tainted: G D W 5.14.2-051402-lowlatency #202109080331 sep 10 17:07:37 kernel: Hardware name: Supermicro C9X299-PG300F/C9X299-PG300F, BIOS 2.1 06/16/2020 sep 10 17:07:37 kernel: RIP: 0010:vmx_create_vcpu+0x6a7/0x6f0 [kvm_intel] sep 10 17:07:37 kernel: Code: 89 e7 48 8d 75 cc ba 04 00 00 00 e8 c3 58 fb d1 85 c0 74 d7 4c 89 ff 4c 89 f3 41 bd f2 ff ff ff e8 fe d9 5f d2 e9 0b fd ff ff <0f> 0b 4c 89 ff 45 89 e5 e8 ec d9 5f d2 45 85 e4 0f 84 34 fb ff ff sep 10 17:07:37 kernel: RSP: 0018:b976caa0fc78 EFLAGS: 00010202 sep 10 17:07:37 kernel: RAX: 9fce6af99db0 RBX: 9fce6af98000 RCX: 0007 sep 10 17:07:37 kernel: RDX: 0006 RSI: 0001 RDI: 0122 sep 10 17:07:37 kernel: RBP: b976caa0fcb8 R08: R09: 9fce6afa1080 sep 10 17:07:37 kernel: R10: 0293 R11: 9fdd3fc33588 R12: 0007 sep 10 17:07:37 kernel: R13: fff4 R14: 9fce6af98000 R15: sep 10 17:07:37 kernel: FS: 7f75e8b79640() GS:9fdd3fc0() knlGS: sep 10 17:07:37 kernel: CS: 0010 DS: ES: CR0: 80050033 sep 10 17:07:37 kernel: CR2: 7f75f8dc2800 CR3: 000314c88005 CR4: 003726e0 sep 10 17:07:37 kernel: DR0: DR1: DR2: sep 10 17:07:37 kernel: DR3: DR6: fffe0ff0 DR7: 0400 sep 10 17:07:37 kernel: Call Trace: sep 10 17:07:37 kernel: kvm_arch_vcpu_create+0x288/0x390 [kvm] sep 10 17:07:37 kernel: kvm_vm_ioctl_create_vcpu+0x188/0x420 [kvm] sep 10 17:07:37 kernel: ? obj_cgroup_uncharge_pages+0x69/0xe0 sep 10 17:07:37 kernel: kvm_vm_ioctl+0x546/0x7b0 [kvm] sep 10 17:07:37 kernel: ? kvm_uevent_notify_change.part.0+0x17b/0x210 [kvm] sep 10 17:07:37 kernel: ? kfree+0x22a/0x3e0 sep 10 17:07:37 kernel: ? __fget_files+0x74/0xa0 sep 10 17:07:37 kernel: __x64_sys_ioctl+0x8e/0xc0 sep 10 17:07:37 kernel: do_syscall_64+0x59/0xc0 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 sep 10 17:07:37 kernel: ? syscall_exit_to_user_mode+0x27/0x50 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 sep 10 17:07:37 kernel: ? syscall_exit_to_user_mode+0x27/0x50 sep 10 17:07:37 kernel: ? __x64_sys_close+0x11/0x40 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 sep 10 17:07:37 kernel: ? syscall_exit_to_user_mode+0x27/0x50 sep 10 17:07:37 kernel: ? __x64_sys_read+0x19/0x20 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? asm_sysvec_apic_timer_interrupt+0xa/0x20 sep 10 17:07:37 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae sep 10 17:07:37 kernel: RIP: 0033:0x7f75f895aecb sep 10 17:07:37 kernel: Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6d 1f 0d 00 f7 d8 64 89 01 48 sep 10 17:07:37 kernel: RSP: 002b:7f75e8b78498 EFLAGS: 0246 ORIG_RAX: 0010 sep 10 17:07:37 kernel: RAX: ffda RBX: 7f75b02d1260 RCX: 7f75f895aecb sep 10 17:07:37 kernel: RDX: RSI: ae41 RDI: 0022 sep 10 17:07:37 kernel: RBP: 7f75e8b78510 R08: R09: sep 10 17:07:37 kernel: R10: R11: 0246 R12: sep 10 17:07:37 kernel: R13: 7f75b02ddd18 R14: R15: 7f75b02ddd10 sep 10 17:07:37 kernel: Modules linked in: cpuid snd_seq_dummy snd_hrtimer ip6t_REJECT nf_reject_ipv6 xt_CHECKSUM xt_tcpudp ipt_REJECT nf_reject_ipv4 xt_set ip_set_hash_ip ip_set bridge stp llc xt_MASQUERADE xt_conntrack nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink zstd lz4 lz4_compress zram netconsole macvlan binfmt_misc dm_crypt nls_iso8859_1 intel_rapl_msr intel_rapl_common isst_if_common nfit x86_pkg_temp_thermal intel_powerclamp
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159
Lenovo Legion 5 15IMH05
$ uname -rv
5.11.0-34-generic #36~20.04.1-Ubuntu SMP Fri Aug 27 08:06:32 UTC 2021
NVIDIA Driver Version: 470.63.01
Had the same issue for some time, until I've "fixed it" recently. The
problem appeared out of nowhere after some update. Booting with attached
external monitor no matter if attached to HDMI or to DP over USB-C
resulted in total freeze during Ubuntu splash screen (for me worse then
BSoD from the rival product, couse no feedback what's going on...).
The problem seems to be connected with Nvidia proprietary drivers. From
what I remember it didn't occur when the nouveau drivers were installed.
Also it only affected the "hybrid graphics" mode (the "dynamic graphics"
setting in the UEFI). The "discrete graphics" mode has another issue
(brightness control does not work).
What finally has fixed it for me was the purge of all nvidia packages
and the driver reinstallation.
$ sudo apt-get remove --purge '^nvidia-.*'
$ su
# for FILE in $(dpkg-divert --list | grep nvidia-470 | awk '{print $3}'); do
dpkg-divert --remove $FILE; done
# exit
$ sudo apt-get install -f
$ sudo apt-get autoremove
$ sudo apt-get clean
After that reboot the system and install a proprietary Nvidia driver.
I hope this helps somebody.
--
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/1874194
Title:
Ubuntu 20.04 HDMI connected, no boot
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have installed Ubuntu 20.04 (using the image created on 20 april) on
my Dell XPS15 9560. This laptop has a Intel / nVidia combo.
The problem i am facing is that when i have an external monitor
connected to the laptop through the HDMI connector of the laptop,
Ubuntu does not boot and hangs on the splash screen. I have not found
any way to get logging on any kind.
Before i was running Ubuntu 18.04 and did not have any problems with
the monitor and HDMI cable. After boot is finished (without monitor
connected) inserting the HDMI cable works fine and i can use the
monitor and laptop screen without any problem.
I have installed the preferred nVida proprietary driver. Also it does
not matter if booting with nVidia selected or Intel selected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1943287] [NEW] Can't start qemu on linux-5.14.2-051402-lowlatency
You have been subscribed to a public bug: After installing kernel package linux-image- unsigned-5.14.2-051402-lowlatency from https://kernel.ubuntu.com/~kernel-ppa/mainline/ starting libvirtd, and thus qemu, results in 2 stack traces. Then libvirtd stops. Rolling back to 5.11.0-34-lowlatency fixes the problem. sep 10 17:07:37 kernel: invalid opcode: [#3] PREEMPT SMP NOPTI sep 10 17:07:37 kernel: CPU: 8 PID: 21670 Comm: daemon-init Tainted: G D W 5.14.2-051402-lowlatency #202109080331 sep 10 17:07:37 kernel: Hardware name: Supermicro C9X299-PG300F/C9X299-PG300F, BIOS 2.1 06/16/2020 sep 10 17:07:37 kernel: RIP: 0010:vmx_create_vcpu+0x6a7/0x6f0 [kvm_intel] sep 10 17:07:37 kernel: Code: 89 e7 48 8d 75 cc ba 04 00 00 00 e8 c3 58 fb d1 85 c0 74 d7 4c 89 ff 4c 89 f3 41 bd f2 ff ff ff e8 fe d9 5f d2 e9 0b fd ff ff <0f> 0b 4c 89 ff 45 89 e5 e8 ec d9 5f d2 45 85 e4 0f 84 34 fb ff ff sep 10 17:07:37 kernel: RSP: 0018:b976caa0fc78 EFLAGS: 00010202 sep 10 17:07:37 kernel: RAX: 9fce6af99db0 RBX: 9fce6af98000 RCX: 0007 sep 10 17:07:37 kernel: RDX: 0006 RSI: 0001 RDI: 0122 sep 10 17:07:37 kernel: RBP: b976caa0fcb8 R08: R09: 9fce6afa1080 sep 10 17:07:37 kernel: R10: 0293 R11: 9fdd3fc33588 R12: 0007 sep 10 17:07:37 kernel: R13: fff4 R14: 9fce6af98000 R15: sep 10 17:07:37 kernel: FS: 7f75e8b79640() GS:9fdd3fc0() knlGS: sep 10 17:07:37 kernel: CS: 0010 DS: ES: CR0: 80050033 sep 10 17:07:37 kernel: CR2: 7f75f8dc2800 CR3: 000314c88005 CR4: 003726e0 sep 10 17:07:37 kernel: DR0: DR1: DR2: sep 10 17:07:37 kernel: DR3: DR6: fffe0ff0 DR7: 0400 sep 10 17:07:37 kernel: Call Trace: sep 10 17:07:37 kernel: kvm_arch_vcpu_create+0x288/0x390 [kvm] sep 10 17:07:37 kernel: kvm_vm_ioctl_create_vcpu+0x188/0x420 [kvm] sep 10 17:07:37 kernel: ? obj_cgroup_uncharge_pages+0x69/0xe0 sep 10 17:07:37 kernel: kvm_vm_ioctl+0x546/0x7b0 [kvm] sep 10 17:07:37 kernel: ? kvm_uevent_notify_change.part.0+0x17b/0x210 [kvm] sep 10 17:07:37 kernel: ? kfree+0x22a/0x3e0 sep 10 17:07:37 kernel: ? __fget_files+0x74/0xa0 sep 10 17:07:37 kernel: __x64_sys_ioctl+0x8e/0xc0 sep 10 17:07:37 kernel: do_syscall_64+0x59/0xc0 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 sep 10 17:07:37 kernel: ? syscall_exit_to_user_mode+0x27/0x50 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 sep 10 17:07:37 kernel: ? syscall_exit_to_user_mode+0x27/0x50 sep 10 17:07:37 kernel: ? __x64_sys_close+0x11/0x40 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 sep 10 17:07:37 kernel: ? syscall_exit_to_user_mode+0x27/0x50 sep 10 17:07:37 kernel: ? __x64_sys_read+0x19/0x20 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? asm_sysvec_apic_timer_interrupt+0xa/0x20 sep 10 17:07:37 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae sep 10 17:07:37 kernel: RIP: 0033:0x7f75f895aecb sep 10 17:07:37 kernel: Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6d 1f 0d 00 f7 d8 64 89 01 48 sep 10 17:07:37 kernel: RSP: 002b:7f75e8b78498 EFLAGS: 0246 ORIG_RAX: 0010 sep 10 17:07:37 kernel: RAX: ffda RBX: 7f75b02d1260 RCX: 7f75f895aecb sep 10 17:07:37 kernel: RDX: RSI: ae41 RDI: 0022 sep 10 17:07:37 kernel: RBP: 7f75e8b78510 R08: R09: sep 10 17:07:37 kernel: R10: R11: 0246 R12: sep 10 17:07:37 kernel: R13: 7f75b02ddd18 R14: R15: 7f75b02ddd10 sep 10 17:07:37 kernel: Modules linked in: cpuid snd_seq_dummy snd_hrtimer ip6t_REJECT nf_reject_ipv6 xt_CHECKSUM xt_tcpudp ipt_REJECT nf_reject_ipv4 xt_set ip_set_hash_ip ip_set bridge stp llc xt_MASQUERADE xt_conntrack nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink zstd lz4 lz4_compress zram netconsole macvlan binfmt_misc dm_crypt nls_iso8859_1 intel_rapl_msr intel_rapl_common isst_if_common nfit x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio rapl intel_cstate snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_usb_audio snd_hda_codec snd_seq_midi snd_usbmidi_lib snd_hda_core snd_seq_midi_event mc snd_hwdep snd_rawmidi efi_pstore snd_pcm snd_seq xpad snd_seq_device ff_memless snd_timer snd soundcore input_leds joydev mei_me mei ioatdma mac_hid acpi_tad
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
Hi @jagsdesai I think you're using the package from mainline. I publish a PPA for 20.04 LTS, and version 5.14.3 has just finished building on launchpad this morning, so any package you installed yesterday was nothing to do with me ;-) Here's my dependencies $ dpkg -I linux-headers-5.14.3-051403-generic_5.14.3-051403.202109130749_amd64.deb ... Depends: linux-headers-5.14.3-051403, libc6 (>= 2.22), libelf1 (>= 0.142), libssl1.1 (>= 1.1.0), zlib1g (>= 1:1.2.3.3) -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1942935] Re: kernel io hangs during mdcheck/resync
One of the systems was using package linux-generic and in practice Linux pedabackup 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/version_signature Ubuntu 5.4.0-80.90-generic 5.4.124 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30 [921588.559081] ? kmem_cache_alloc+0x38e/0x440 [921588.559084] ? ext4_init_io_end+0x1f/0x50 [921588.559088] ext4_io_submit+0x4d/0x60 [921588.559091]
[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30 [921588.559081] ? kmem_cache_alloc+0x38e/0x440 [921588.559084] ? ext4_init_io_end+0x1f/0x50 [921588.559088] ext4_io_submit+0x4d/0x60 [921588.559091] ext4_writepages+0x2c6/0xcd0 [921588.559094] ? __schedule+0x454/0x8a0 [921588.559097] ?
[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync
I think I've seen this issue once per two different systems so I think this is software issue. Does anybody know if patch in comment #6 is going to be included in Ubuntu 20.04 LTS? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30 [921588.559081] ? kmem_cache_alloc+0x38e/0x440 [921588.559084] ? ext4_init_io_end+0x1f/0x50 [921588.559088] ext4_io_submit+0x4d/0x60 [921588.559091] ext4_writepages+0x2c6/0xcd0 [921588.559094] ? __schedule+0x454/0x8a0
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
@tuxinvader While trying to install Kernel 5.14.3 (Sep 12, 2021) on Ubuntu MATE 21.04, I ran into similar issue but for libc6 2.34. Error: dpkg: dependency problems prevent configuration of linux- headers-5.14.3-051403-generic: linux-headers-5.14.3-051403-generic depends on libc6 (>= 2.34); however: version of libc6:amd64 on system is 2.33-0ubuntu5. -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1937078] Re: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Validated by Microsoft on test kernels. Tagging as verification done.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1937078
Title:
Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Status in linux-azure package in Ubuntu:
Incomplete
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure source package in Hirsute:
Fix Committed
Bug description:
SRU Justification
[Impact]
Customers have degraded network performance on Hyper-V/Azure
This is a request to pick up a patch from the upstream, the patch
fixes an issue with Ubuntu as a hyper-v and Azure guest. This patch
need to get picked up for 20.04, 18.04. The link to the upstream patch
follows:
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-
fixes=7c9ff3d61b253715dcf968a6307af148c9b2
Description of issue and solution:
The vmbus module uses a rotational algorithm to assign target CPUs to
a device's channels. Depending on the timing of different device's channel
offers, different channels of a device may be assigned to the same CPU.
For example on a VM with 2 CPUs, if NIC A and B's channels are offered
in the following order, NIC A will have both channels on CPU0, and
NIC B will have both channels on CPU1 -- see below. This kind of
assignment causes RSS load that is spreading across different channels
to end up on the same CPU.
Timing of channel offers:
NIC A channel 0
NIC B channel 0
NIC A channel 1
NIC B channel 1
VMBUS ID 14: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {cab064cd-1f31-47d5-a8b4-9d57e320cccd}
Sysfs path: /sys/bus/vmbus/devices/cab064cd-1f31-47d5-a8b4-9d57e320cccd
Rel_ID=14, target_cpu=0
Rel_ID=17, target_cpu=0
VMBUS ID 16: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {244225ca-743e-4020-a17d-d7baa13d6cea}
Sysfs path: /sys/bus/vmbus/devices/244225ca-743e-4020-a17d-d7baa13d6cea
Rel_ID=16, target_cpu=1
Rel_ID=18, target_cpu=1
Update the vmbus CPU assignment algorithm to avoid duplicate CPU
assignments within a device.
The new algorithm iterates num_online_cpus + 1 times.
The existing rotational algorithm to find "next NUMA & CPU" is still here.
But if the resulting CPU is already used by the same device, it will try
the next CPU.
In the last iteration, it assigns the channel to the next available CPU
like the existing algorithm. This is not normally expected, because
during device probe, we limit the number of channels of a device to
be <= number of online CPUs.
[Test Plan]
This could be tough to test as the patch fixes a race condition.
[Where problems could occur]
Network performance issues could persist.
[Other Info]
SF:#00315347
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937078/+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 1943160] Re: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.
** Also affects: nvidia-settings (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: nvidia-settings (Ubuntu Focal)
Status: New => In Progress
** Changed in: nvidia-settings (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: nvidia-settings (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-settings (Ubuntu Focal)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1943160
Title:
[SRU] It will take about 90+ seconds to open the 'Nvidia settings' app
when 'Power Saving mode' running.
Status in OEM Priority Project:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in nvidia-settings source package in Focal:
In Progress
Bug description:
[Impact]
On some I+N configs, It will take about 90+ seconds to open the 'Nvidia
settings' window when 'Power Saving mode' running.
[Fix]
do not read config file if Nvidia driver did not loaded:
change nvidia-settings/src/nvidia-settings.c
if (!op->no_load) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, , );
to
if (!op->no_load && systems.n != 0) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, , );
[Test]
1. Install Ubuntu image.
2. Boot and login the system.
3. Open 'Nvidia Settings' app
4. Select the prime is 'Power saving' mode
5. Reboot system and login
6. Open 'Nvidia Settings' app
7. Verify the result
[Where problems will occur]
the "systems.n" gets from
NvCtrlConnectToSystem(op->ctrl_display, );
If there is a possibility that systems.n is zero and we still need to read
nvidia config file, then it will be a problem. I tried and cannot find a
situation like that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943160/+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 1942633] Re: Can not boot impish in Cavium ThunderX
Feel free to bisect, i'm checking our SAUCE patches/configs. BTW: Firmware Version: 2017-10-12 12:34:31 it's the last FW version available, isn't it? I'm wondering about the device tree. -- 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/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Confirmed Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+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 1942999] Re: [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942999 Title: [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: New Status in linux source package in Impish: In Progress Bug description: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942999/+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 1943421] Re: Error while enabling somerville driver: package linux-oem-5.13-headers-5.13.0-1010 (not installed) failed to install/upgrade: unable to open "/usr/src/linux-oem-5.1
** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1943421 Title: Error while enabling somerville driver: package linux- oem-5.13-headers-5.13.0-1010 (not installed) failed to install/upgrade: unable to open "/usr/src/linux- oem-5.13-headers-5.13.0-1010/sound/soc/jz4740/Kconfig.dpkg-new" Status in linux-oem-5.13 package in Ubuntu: Invalid Bug description: I'm trying to install Ubuntu 20.04.3 on a brand new Dell 7520, which is equipped with: * 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz × 8 * Intel Iris XE GPU (reported as Mesa Intel® Xe Graphics (TGL GT2)) Since on my first try I was getting a lot of SEGFAULTS, I repeated the installation without enabling 3rd party drivers, and all went smoothly, apart from the fan pushing a lot. This morning I tried to enable the drivers from the Ubuntu dedicated windows, and it started raining errors on me, like the one reported in the title. It seems that the kernel (5.13 OEM or HWE) and or the Intel (somerville) drivers are acting crazy. I can say that the freezes occur on two different laptop of the same kind, just after a fresh install and when using stuff like a browser, that leverages a bit the GPU. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-oem-5.13-headers-5.13.0-1010 (not installed) ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46 Uname: Linux 5.10.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 13 09:55:18 2021 ErrorMessage: impossibile aprire "/usr/src/linux-oem-5.13-headers-5.13.0-1010/sound/soc/jz4740/Kconfig.dpkg-new": Operazione non permessa InstallationDate: Installed on 2021-07-21 (53 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-oem-5.13 Title: package linux-oem-5.13-headers-5.13.0-1010 (not installed) failed to install/upgrade: impossibile aprire "/usr/src/linux-oem-5.13-headers-5.13.0-1010/sound/soc/jz4740/Kconfig.dpkg-new": Operazione non permessa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1943421/+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 1943430] [NEW] Restarted computer, touchpad stopped working.
Public bug reported: Was using the computer quickly to join a zoom call like normal. Didn't install anything or modify any files. Shut off the computer only to start it up again and have the touchpad not working. Using Thinkpad T470S. Worth mentioning that the trackpoint (red button on keyboard) has not been working ever since install. Trackpad buttons (the three above the touchpad) do not work either, but they have worked once after intense googling, but do not work either right now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 13 10:46:59 2021 InstallationDate: Installed on 2021-08-28 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Drivers" https://bugs.launchpad.net/bugs/1943430/+attachment/5524927/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943430 Title: Restarted computer, touchpad stopped working. Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Was using the computer quickly to join a zoom call like normal. Didn't install anything or modify any files. Shut off the computer only to start it up again and have the touchpad not working. Using Thinkpad T470S. Worth mentioning that the trackpoint (red button on keyboard) has not been working ever since install. Trackpad buttons (the three above the touchpad) do not work either, but they have worked once after intense googling, but do not work either right now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 13 10:46:59 2021 InstallationDate: Installed on 2021-08-28 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943430/+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 1938697] Re: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic
Hi Chris, Apologises emailed my update rather than posting it via the webui. Yes it that version worked. Regards, James -- 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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes
[Kernel-packages] [Bug 1943425] 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/1943425 Title: Touchpad is not working and detected Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 5.4.0-84.94-generic 5.4.133 Description: Ubuntu 20.04.3 LTS Release: 20.04 xinput -list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech Wireless Receiver Mouseid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] xinput shows no touchpad Touchpad is not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: reveur 3039 F pulseaudio /dev/snd/controlC0: reveur 3039 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Sep 13 13:46:42 2021 HibernationDevice: RESUME=UUID=0d592d53-b697-445e-a05f-df427587848e MachineType: Dell Inc. Inspiron 3558 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=5276c553-95fa-4b9f-aa57-08c119bd464c ro i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop RelatedPackageVersions: linux-restricted-modules-5.4.0-84-generic N/A linux-backports-modules-5.4.0-84-generic N/A linux-firmware1.187.16 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0G1TDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd12/15/2015:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.product.sku: 06B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943425/+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 1943425] [NEW] Touchpad is not working and detected
Public bug reported: Ubuntu 5.4.0-84.94-generic 5.4.133 Description:Ubuntu 20.04.3 LTS Release:20.04 xinput -list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech Wireless Receiver Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=12 [slave keyboard (3)] ↳ Dell WMI hotkeys id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] xinput shows no touchpad Touchpad is not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: reveur 3039 F pulseaudio /dev/snd/controlC0: reveur 3039 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Sep 13 13:46:42 2021 HibernationDevice: RESUME=UUID=0d592d53-b697-445e-a05f-df427587848e MachineType: Dell Inc. Inspiron 3558 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=5276c553-95fa-4b9f-aa57-08c119bd464c ro i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop RelatedPackageVersions: linux-restricted-modules-5.4.0-84-generic N/A linux-backports-modules-5.4.0-84-generic N/A linux-firmware1.187.16 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0G1TDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd12/15/2015:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.product.sku: 06B0 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- 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/1943425 Title: Touchpad is not working and detected Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 5.4.0-84.94-generic 5.4.133 Description: Ubuntu 20.04.3 LTS Release: 20.04 xinput -list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech Wireless Receiver Mouseid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] xinput shows no touchpad Touchpad is not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: reveur 3039 F pulseaudio /dev/snd/controlC0: reveur 3039 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Sep 13 13:46:42 2021 HibernationDevice:
[Kernel-packages] [Bug 1938689] Re: [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1938689 Title: [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Incomplete Bug description: SRU justification: [Impact] System hang after unplug thunderbolt dock with Intel igc lan. [Fix] igc driver continue reading and writing MMIO address after PCI device is unplugged. This cause system page fault, and system hang. Add safe check and prevent reading and writing the MMIO. The patch is in maintainer's tree, but not merged to Linus's tree. Due to the schedule, send SRU as SAUCE patch. [Test] Verified on hardware, after unplug the thunderbolt cable, system work fine. [Where problems could occur] It may break the igc driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1938689/+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 1921345] Re: Support MIPI camera through Intel IPU6
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- 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/1921345 Title: Support MIPI camera through Intel IPU6 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Won't Fix Bug description: [SRU Justification] [Impact] There are new platforms with MIPI camera based on Intel IPU6(Imaging Processing Unit version 6) currently unsupported in Ubuntu. [Fix] Intel IPU6 can be enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc This patchset took kernel patches from intel/ipu6-drivers. [Test Case] With kernel/firmware properly installed, the hardware should be ready for further development: $ dmesg | grep ipu intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 There should be nearly 24 video4linux devices created under /dev. [Where problems could occur] MIPI camera through Intel IPU6 takes also firmware blobs loaded in runtime from user space, addtional softwares are also required to fully enable it for oridinary use. The exposed video devices are hidden from general users and a relay daemon+v4l2loopback is used to enable use from existing applications. >From kernel's point of view, there is still a known issue that it takes root priviledge to access these devices. [Other Info] So far Intel has no plan to commit this driver to upstream yet, so it's only nominated for oem-5.10. It will only be nominated to generic kernels when the plan/requirements have changed. The original driver Kconfig would disable VIDEO_IPU3_CIO2, but that's reverted to avoid unnecessary changes to existing users. == original bug description == The Intel imaging processing unit version 6, found in Intel SoCs and used for capturing images and video from a camera sensor is enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc With all components properly installed, the hardware should be ready for further development: intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu:
[Kernel-packages] [Bug 1928047] Re: AX201 BT will cause system could not enter S0i3
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1928047 Title: AX201 BT will cause system could not enter S0i3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Bug description: [Impact] Platforms with AX201 BT fail to pass the power consumption tests [Fix] Intel provides us the patch to fix it. https://patchwork.kernel.org/project/intel-gfx/patch/20210325120947.11950-1-anshuman.gu...@intel.com/ Wa_14010685332 sequence toggles a SDE chicken bit on and then off as the final step when disabling interrupts in preparation for runtime suspend. And this sequence also fixes the issues that dispcnlunit1_cp_xosc_clkreq clock keeps to be active on TGL-H during s2idle. v2. 8b46cc6577f4 drm/i915: Tweaked Wa_14010685332 for all PCHs [Test] Verified on the Dell machines with AX201 BT on them. [Where problems may occur] This patch extend the s0ix fix from gen8 and gen11 to CNP, ICP, JSP, MCC, TGP, and ADP PCHs, and also move the Wa_14010685332 sequence from reset functions to suspend/resume functions. It won't affect old chips as there is a if statement to check the pch type, and new chips require this sequence to work well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1928047/+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 1936708] Re: Wobbly graphics on built-in display since linux-image-5.11.0-22-generic
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1936708 Title: Wobbly graphics on built-in display since linux- image-5.11.0-22-generic Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Wobbly graphics after a kernel update. [Fix] Older panels may require more bandwidth then advertised, so we need to use max params for them. [Test] Multiple users tested with positive result. [Where problems could occur] This patch reverts to the old behavior, which is to use max parameters, for older panels. If there's any new panel reports with older DP version, this might change the behavior on it. == Original Bug Report == Lenovo laptop with Intel + Nvidia graphics. Since booting from linux-image-5.11.0-22-generic, the built-in display is unusable, with wobbling horizontal stripes from the disk decryption prompt onwards: https://www.youtube.com/watch?v=LyRTuPzCe2I HDMI output works fine. If I boot from linux-image-5.11.0-18-generic instead, all is well. If I use Recovery mode with linux-image-5.11.0-22-generic and continue bootup, it's usable but there's no HDMI output. I think others may be having this issue too: https://askubuntu.com/questions/1351188/weird-graphical-glitches-appears-only-on-integrated-display-on-any-ubuntu-base# ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1598 F pulseaudio /dev/snd/controlC0: alex 1598 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 17 09:50:31 2021 InstallationDate: Installed on 2021-01-03 (194 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 80DU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-22 (55 days ago) dmi.bios.date: 08/18/2014 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y70-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y70-70 Touch dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:br1.49:efr1.49:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 80DU dmi.product.sku: LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch dmi.product.version: Lenovo Y70-70 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936708/+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 1937056] Re: Touchpad not working with ASUS TUF F15
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1937056 Title: Touchpad not working with ASUS TUF F15 Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Touchpad and touchscreen don't work on TGL-H laptops. [Fix] Update GPIO mapping so the values can match between Linux and BIOS. [Test] After applying the patch, both touchpad and touchscreen can work correctly. [Where problems could occur] If somehow any of the new pin value is incorrect, it can break devices that require Intel GPIO to work. == Original Bug Report == I am using Kubuntu 21.04 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices. Laptop model: ASUS TUF F15 FX506HM_FX566HM. Manufacturer of the Touchpad: Probably ELAN1203 When the symptom first appeared: From beginning Output of lsb_release -rd Description:Ubuntu 21.04 Release:21.04 Using kernel version 5.13.6. Also tried 5.11, 5.12.8, 5.12.15, 5.13.1, 5.13.2, 5.13.4, 5.13.5, 5.14-rc2, 5.14-rc3 Output of xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Asus Wireless Radio Control id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Asus WMI hotkeys id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] Output of lspci :00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05) :00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05) :00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) :00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05) :00:06.0 System peripheral: Intel Corporation Device 09ab :00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05) :00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05) :00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01) :00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05) :00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05) :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller :00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) :00:14.2 RAM
[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown
@kaihengfeng Sorry for delay reply. Yes mine laptop is based on AMD Ryzen 5 3500U with integrated Vega 8. (HP Laptop 15s-eq0035nw) -- 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/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1937978] Re: New device IDs for Intel ADL-M
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1937978 Title: New device IDs for Intel ADL-M Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] Some ADL IDs are added after v5.13, need to backport them to OEM-5.13 kernel. [Fix] 9fb3cad02517 mfd: intel-lpss: Add Intel Alder Lake-M PCI IDs 854955ae96db mtd: spi-nor: intel-spi: Add support for Intel Alder Lake-M SPI serial flash a59c7b6c6ff6 platform/x86: intel-hid: add Alder Lake ACPI device ID [Test] Don't have h/w yet, so not tested. [Where problems could occur] Only adding new IDs, won't impact old platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937978/+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 1937252] Re: e1000e: add handshake with the Intel CSME to support S0ix
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1937252 Title: e1000e: add handshake with the Intel CSME to support S0ix Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] These improves power consumption on some e1000e platforms. [Fix] 3 fixes in thread https://www.spinics.net/lists/netdev/msg755279.html (now in netdev/net-next.git). [Test Case] These fixes solves two issues that the first one is the power consumption would be lower to 1.651W from 2.032W when device enters sleep state. The second is I219 may now enter ultra lower power mode after resumed from s2idle. [Where problems could occur] While these fixes are still not in mainline but net-next, expecting some more stability fix when necessary. == original bug description == Intel is doing some improvement for the Corp ME + S0ix support. Currently, this patch series have been landed in nextdev, net-next tree. e1000e: Additional PHY power saving in S0ix https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3ad3e28cb203309fb29022dea41cd65df0583632 e1000e: Add polling mechanism to indicate CSME DPG exit https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=ef407b86d3cc7ab7ad37658c1c7a094cb8f3b6b4 e1000e: Add handshake with the CSME to support S0ix https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3e55d231716ea361b1520b801c6778c4c48de102 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937252/+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 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disable ASPM L1.2
* CVE-2021-3609
- can: bcm: delay release of struct bcm_op after synchronize_rcu()
- can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after
RCU is done
-- Timo Aaltonen Tue, 07 Sep 2021
11:49:54 +0300
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load capability
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
in v5.11 fails firmware loading without IRAM recovery feature. However,
the latest firmware from
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
doesn't support IRAM, it follows new official ath10k firmwares may no
longer be loadable for kernel newer than v5.11.
[Fix]
A fix is proposed to
http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that
turns the lack/failure of IRAM recovery support a warning instead.
[Test Case]
With this fix, kernel gives errors about the IRAM supportness, but
proceeds to remaining procedures as before.
ath10k_pci :04:00.0: No hardware memory
ath10k_pci :04:00.0: failed to copy target iram contents: -12
ath10k_pci :07:00.0: No hardware memory
ath10k_pci :07:00.0: failed to copy target iram contents: -12
[Where problems could occur]
So the IRAM recovery feature may or may not be supported in the
officially released firmware, and people meet problems when using
non-IRAM supported firmware may still have a fallback to use older, but
IRAM recovery supported ones.
== original bug report ==
Hello, I use Ubuntu 20.04.2 LTS.
The kernel was recently updated to 5.11
5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Since then the ath10k_core driver for my QCA9984 card is broken and
only loads ~3 firmware versions from the 3.9.0.2 branch
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
The firmware versions 70 / 86 / 91 are functional (but these firmware
versions are already 2 years old)
Responsible for this is the defective patch "ath10k: add target IRAM
recovery feature support"
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8
If I understand the patch correctly then the driver tries to load
firmware with the feature "iram recovery" into the memory of the host
(for recvovery purposes).
If this fails, the firmware is discarded and the network controller
remains unusable.
Of course, this is not a desirable behavior for optional firmware
features.
dmesg:
[3.074952] ath: loading out-of-tree module taints kernel.
[3.090522] ath: module verification failed: signature and/or required key
missing - tainting kernel
[3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
[Kernel-packages] [Bug 1939539] Re: Fix Intel IPU6 camera sensor HM11b1 brightness
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939539 Title: Fix Intel IPU6 camera sensor HM11b1 brightness Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Incomplete Bug description: Intel has released fix for HM11B1 sensor on IPU6 platform for its brightness problem in https://github.com/intel/ipu6-drivers/commit/eca28d1aa048216dc034b134e65e1b47602ee4a6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1832 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-mewtwo+X82 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Latitude 9420 Package: linux-oem-5.13 (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1010-oem root=UUID=090b1bdb-5d69-4cb9-a704-e1fffed1e366 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-1010.11-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-1010-oem N/A linux-backports-modules-5.13.0-1010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal Uname: Linux 5.13.0-1010-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/25/2021 dmi.bios.release: 89.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.5.23 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.5.23:bd01/25/2021:br89.5:svnDellInc.:pnLatitude9420:pvr:sku0A32:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 9420 dmi.product.sku: 0A32 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1939539/+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 1940204] Re: AMDGPU: Fix System hang after resume from suspend
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1940204 Title: AMDGPU: Fix System hang after resume from suspend Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] With AMD-GPU and don't use it as a display output, After multiple Suspend, system would hang. [Fix] Disable BACO for polaris12 series. BACO allow the graphics cards on Linux to support S4 / hibernation support. [Test Case] 1. Must plug AMD GPU and don't use it as display output 2. Plug DP/HDMI on iGPU. 3. Suspend machine. 4. check if system hangs. [Where problems could occur] Disable BACO would cause higher power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940204/+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 1939541] Re: ALSA: hda/cs8409: Add support for dolphin
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939541 Title: ALSA: hda/cs8409: Add support for dolphin Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Dolphin devices have CS8409 HDA Bridge connected to two CS42L42 codecs. Codec 1 supports Headphone and Headset Mic. Codec 2 supports Line Out. [Fix] In order to support multiple CS42L42 codecs connected to a CS8409 HDA Bridge, a changeset of 27 patches is proposed to https://patchwork.kernel.org/project/alsa-devel/cover/20210811185654.6837-1-vita...@opensource.cirrus.com/ (now in linux-next), as well as two additional patches in https://lore.kernel.org/lkml/20210812183433.6330-1-vita...@opensource.cirrus.com/ that fixes pop sounds at insertion of earphone jack and reboot. The second patch of the latter changeset is on hold because of another fix series that deprecates the reboot_notify callback of HD-audio by forcibly doing runtime-suspend at shutdown. A Ubuntu sauced patch is also added to enable the now stand alone module snd-hda-codec-cs8409. [Test Case] Test on oem dolphin platform, as well as previous cs8409 platforms with one single codec. [Where problems could occur] While this is the first platform we have multiple codecs connected to a CS8409 HDA bridge, we may still have further stability or acoustic quality issues as we had for previous cirrus platforms. [Other Info] This also fixes default sample rate problem that was previously fixed by a oem-only package oem-fix-audio-cirrus-default-sample-rate. == original bug report == Dolphin devices have CS8409 HDA Bridge connected to two CS42L42 codecs. Codec 1 supports Headphone and Headset Mic. Codec 2 supports Line Out. Features: - Front and Read Jacks appear as separate jacks; Removal or connection of on jack should not affect the connection of the other. - Front Jack only shows up on jack detection. - Rear Jack is Phantom Jack. - Separate Volume Controls for each Jack To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939541/+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 1939473] Re: mute/micmute LEDs no function on HP ProBook 650 G8
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu) Status: Invalid => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939473 Title: mute/micmute LEDs no function on HP ProBook 650 G8 Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Fix Committed Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook 650 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1939473/+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 1941696] Re: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941696 Title: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] 1. On Troy JSL platform, add AC9560 2. Enter Settings -> Bluetooth menu 3. Default Bluetooth option is ON, try to toggle the BT option to OFF 4. Into suspend mode(S3) and resume the system 5. Enter BT settings and try to turn on BT, 6. BT function cannot enabled until reboot. [Fix] Turn off the msft ext only for AC9560. Maintainer thought Intel should take care this and reject this workaround. https://marc.info/?l=linux-bluetooth=162938546804458=2 Intel is working on this issue and sru the workaround for the schedule. [Test] Verified with the bellow steps 10 times. 1. On Troy JSL and add AC9560 2. Turn off BT 3. suspend the machine 10 times. 4. turn on BT and works well. [Regression Potential] Medium, it's a workaround to turn off the MSFT ext only for ac9560. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941696/+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 1940610] Re: Fix mic noise on HP ProBook 445 G8
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1940610 Title: Fix mic noise on HP ProBook 445 G8 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] There's mic noise on HP ProBook 445 G8. [Fix] Limit mic boost to make the audio capture crystal clear. [Test] $ arecord -f dat test $ aplay test With the fix, the mic noise is gone. [Where problems could occur] If someone would like to let others hear the noise in Zoom, this will deprive of their pleasure. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940610/+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 1942830] Re: Fix sluggish r8169 by disaling ASPM L1.2
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16 --- linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861) * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830) - SAUCE: r8169: Disable ASPM L1.2 * CVE-2021-3609 - can: bcm: delay release of struct bcm_op after synchronize_rcu() - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU is done -- Timo Aaltonen Tue, 07 Sep 2021 11:49:54 +0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942830 Title: Fix sluggish r8169 by disaling ASPM L1.2 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: [Impact] Realtek r8169 has abysmal network speed. [Fix] Disable ASPM L1.2 because the device takes a long time to exit from L1.2. [Test] Use `iperf` to test network speed. When ASPM L1.2 gets disabled, TX and RX and reach ~700Mbps and ~900Mbps respectively. [Where problems could occur] Disabling ASPM L1.2 can slightly increase power consumption. The CPU package C-State seems to be unaffected so the increase is rather minor. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942830/+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 1943421] [NEW] Error while enabling somerville driver: package linux-oem-5.13-headers-5.13.0-1010 (not installed) failed to install/upgrade: unable to open "/usr/src/linux-oem-5
Public bug reported: I'm trying to install Ubuntu 20.04.3 on a brand new Dell 7520, which is equipped with: * 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz × 8 * Intel Iris XE GPU (reported as Mesa Intel® Xe Graphics (TGL GT2)) Since on my first try I was getting a lot of SEGFAULTS, I repeated the installation without enabling 3rd party drivers, and all went smoothly, apart from the fan pushing a lot. This morning I tried to enable the drivers from the Ubuntu dedicated windows, and it started raining errors on me, like the one reported in the title. It seems that the kernel (5.13 OEM or HWE) and or the Intel (somerville) drivers are acting crazy. I can say that the freezes occur on two different laptop of the same kind, just after a fresh install and when using stuff like a browser, that leverages a bit the GPU. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-oem-5.13-headers-5.13.0-1010 (not installed) ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46 Uname: Linux 5.10.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 13 09:55:18 2021 ErrorMessage: impossibile aprire "/usr/src/linux-oem-5.13-headers-5.13.0-1010/sound/soc/jz4740/Kconfig.dpkg-new": Operazione non permessa InstallationDate: Installed on 2021-07-21 (53 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-oem-5.13 Title: package linux-oem-5.13-headers-5.13.0-1010 (not installed) failed to install/upgrade: impossibile aprire "/usr/src/linux-oem-5.13-headers-5.13.0-1010/sound/soc/jz4740/Kconfig.dpkg-new": Operazione non permessa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1943421 Title: Error while enabling somerville driver: package linux- oem-5.13-headers-5.13.0-1010 (not installed) failed to install/upgrade: unable to open "/usr/src/linux- oem-5.13-headers-5.13.0-1010/sound/soc/jz4740/Kconfig.dpkg-new" Status in linux-oem-5.13 package in Ubuntu: New Bug description: I'm trying to install Ubuntu 20.04.3 on a brand new Dell 7520, which is equipped with: * 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz × 8 * Intel Iris XE GPU (reported as Mesa Intel® Xe Graphics (TGL GT2)) Since on my first try I was getting a lot of SEGFAULTS, I repeated the installation without enabling 3rd party drivers, and all went smoothly, apart from the fan pushing a lot. This morning I tried to enable the drivers from the Ubuntu dedicated windows, and it started raining errors on me, like the one reported in the title. It seems that the kernel (5.13 OEM or HWE) and or the Intel (somerville) drivers are acting crazy. I can say that the freezes occur on two different laptop of the same kind, just after a fresh install and when using stuff like a browser, that leverages a bit the GPU. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-oem-5.13-headers-5.13.0-1010 (not installed) ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46 Uname: Linux 5.10.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 13 09:55:18 2021 ErrorMessage: impossibile aprire "/usr/src/linux-oem-5.13-headers-5.13.0-1010/sound/soc/jz4740/Kconfig.dpkg-new": Operazione non permessa InstallationDate: Installed on 2021-07-21 (53 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-oem-5.13 Title: package linux-oem-5.13-headers-5.13.0-1010 (not installed) failed to install/upgrade: impossibile aprire "/usr/src/linux-oem-5.13-headers-5.13.0-1010/sound/soc/jz4740/Kconfig.dpkg-new": Operazione non permessa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1943421/+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 1941955] Re: New upstream release 2021.08.28
This bug was fixed in the package wireless-regdb - 2021.08.28-0ubuntu1~20.04.1 --- wireless-regdb (2021.08.28-0ubuntu1~20.04.1) focal; urgency=medium * Backport to focal (LP: #1941955) -- Seth Forshee Sun, 29 Aug 2021 14:49:57 -0500 ** Changed in: wireless-regdb (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Bionic: Fix Released Status in wireless-regdb source package in Focal: Fix Released Status in wireless-regdb source package in Hirsute: Fix Released Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+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 1941955] Re: New upstream release 2021.08.28
This bug was fixed in the package wireless-regdb - 2021.08.28-0ubuntu1~18.04.1 --- wireless-regdb (2021.08.28-0ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic (LP: #1941955) -- Seth Forshee Sun, 29 Aug 2021 14:56:08 -0500 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Bionic: Fix Released Status in wireless-regdb source package in Focal: Fix Released Status in wireless-regdb source package in Hirsute: Fix Released Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+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 1941955] Re: New upstream release 2021.08.28
This bug was fixed in the package wireless-regdb - 2021.08.28-0ubuntu1~21.04.1 --- wireless-regdb (2021.08.28-0ubuntu1~21.04.1) hirsute; urgency=medium * Backport to hirsute (LP: #1941955) -- Seth Forshee Sun, 29 Aug 2021 14:00:29 -0500 ** Changed in: wireless-regdb (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: wireless-regdb (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Bionic: Fix Released Status in wireless-regdb source package in Focal: Fix Released Status in wireless-regdb source package in Hirsute: Fix Released Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+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 1941955] Update Released
The verification of the Stable Release Update for wireless-regdb has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Bionic: Fix Released Status in wireless-regdb source package in Focal: Fix Released Status in wireless-regdb source package in Hirsute: Fix Released Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+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 1941829] Re: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941829 Title: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+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 1937144] Re: The front mic can't be detected on a lenovo thinkstation machine
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.13 (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1937144 Title: The front mic can't be detected on a lenovo thinkstation machine Status in HWE Next: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Bug description: The patch is sent to oem-5.10 first, and other ubuntu kernels will merge this patch with stable update since this patch was already CCed to stable. [Impact] Users plug a headset or microphone to the front mic jack, but the system can't detect the plug and will not set the mic to be the active input device. [Fix] Backport a upstream patch, this will change the front mic jack's name from Front Mic to Mic, then the pulseaudio could handle the plug/unplug. [Test] Plug a headset to the front mic jack, open the gnome-sound-setting, the front mic is the active input device, use this device to record sound, it could record the sound successfully. [Where problems could occur] It could make the other mic can't be detected, but this possibility is very low and I alreaed tested all audio jacks on that machine, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937144/+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 1942043] Re: Noise will pop up during WB or stay in Ubuntu OS when external speaker attached
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942043 Title: Noise will pop up during WB or stay in Ubuntu OS when external speaker attached Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] HD-audio codec shutdown is not quite right when powering off the controller side. This causes pop noises on some platforms. [Fix] While previously in bug 1939541, a local fix for Cirrus CS8409 only is proposed the upstream as in https://lore.kernel.org/lkml/20210812183433.6330-2-vita...@opensource.cirrus.com/ . This initiated a discuss to create a generic solution as in https://lore.kernel.org/all/20210813081230.4268-1-ti...@suse.de/ . [Test Case] Shutdown Ubuntu that is running a patched kernel and see if a pop sound is still made. [Where problems could occur] While this tries to suspend the codec devices at shutting down, out of tree drivers without (runtime-)suspend support may fail to react correctly. And since this removes .reboot_notify callback from struct hda_codec_ops, it may break such oot drivers, too. [Other Info] This depends on patches for https://bugs.launchpad.net/bugs/1939541 . == original bug report == [Reproduce Steps] 1. Attach external speaker to SUT 2. Try to reboot SUT or stay in OS. [Results] Expected Result No noise. Actual Result Noise will pop up during WB or stay in Ubuntu OS when external speaker attached. [Others] [Scenario 1] Login to the Ubuntu OS. (Occurs only in Cirrus, within 5 seconds after logging in to OS) Can 100% reproduce on Cirrus MB with Ubuntu. Noise can be heard (咚咚 Sounds) after login the Ubuntu within 5 secs. [Scenario 2] Reboot Ubuntu OS (Both Curris and Realtek happen. WB/CB/shutdown OS) Can 100% reproduce on Cirrus MB with Ubuntu. Noise can be heard While both exiting OS and entering OS. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942043/+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 1942972] Re: Update fix for LP: #1936708
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => 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/1942972 Title: Update fix for LP: #1936708 Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] There's a new fix for LP: #1936708, and it's more reliable than the old approach. So replace it. [Fix] Use eDP as predicate to enable max params. [Test] Users confirmed the fix can resolve their issue. [Where problems could occur] This patch reverts to the old behavior, which is to use max parameters, for older panels. If there's any new panel reports with older eDP version, this might change the behavior on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942972/+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 1942994] Re: [SRU][OEM-5.13/OEM-5.14/U] Fix mt7921e wifi timeout error after resume
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942994 Title: [SRU][OEM-5.13/OEM-5.14/U] Fix mt7921e wifi timeout error after resume Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: SRU justification: [Impact] Mediatek 7921 wifi card is lost when stress S3. [Fix] Check the valid events from firmware, make it resume back. The patch is in maintainer's tree, but not merged to Linus's tree. Due to the schedule, send SRU as SAUCE patch. [Test] Verified on hardware, wifi works fine after stress S3. Tested on 3 platforms include the one platform that can reproduce the issue, all good. [Where problems could occur] Mediatek 7921 wifi may be broken. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942994/+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 1942299] Re: On booting (or wake from suspend) Ubuntu/Lubuntu impish daily - cd/dvd tray ejects
This issue still gets noticed daily; as I wake my primary box from it's suspended sleep. I just noticed https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1943379 which refers to https://bugzilla.kernel.org/show_bug.cgi?id=213759 and fix https://github.com/torvalds/linux/commit/5c04243a56a7977185b00400e59ca7e108004faf which maybe related... ** Bug watch added: Linux Kernel Bug Tracker #213759 https://bugzilla.kernel.org/show_bug.cgi?id=213759 -- 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/1942299 Title: On booting (or wake from suspend) Ubuntu/Lubuntu impish daily - cd/dvd tray ejects Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu impish daily boot on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) This daily was booted more than once, on each boot, just prior to plymouth screen appearing the cd/dvd tray would be ejected. If my installation media was on the cd/dvd - would that have crashed install? I've been noting this behavior on my primary box - dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) each day (Ubuntu impish, ubuntu, xubuntu & lubuntu desktops installed; occurs when Xfce or LXQt is running.. I don't think I've tried suspend with GNOME with 5.13 kernel) when I resume it in the morning (I suspend each night), likely the 11 days since `uptime` says I last rebooted (I tend to reboot only about once per fortnight) ** actual results On booting daily; the CD/DVD tray ejects ** expected results The CD/DVD is not being used on this boot; I'd expect the tray to remain as it was ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-14-generic 5.13.0-14.14 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1602 F pulseaudio /dev/snd/controlC1: lubuntu1602 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: LXQt Date: Wed Sep 1 07:03:31 2021 IwConfig: lono wireless extensions. enp0s25 no wireless extensions. LiveMediaBuild: Lubuntu 21.10 "Impish Indri" - Alpha amd64 (20210831) MachineType: Dell Inc. OptiPlex 780 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.13.0-14-generic N/A linux-backports-modules-5.13.0-14-generic N/A linux-firmware 1.199 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2010 dmi.bios.release: 3.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0200DY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/13/2010:br3.0:svnDellInc.:pnOptiPlex780:pvr:sku:rvnDellInc.:rn0200DY:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942299/+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 1942952] Re: Kernel Call Trace on Secure Boot
The slow CPU (N5000 CPU @ 1.10GHz) may play a role in the watchdog soft lockup. You can increase the watchdog time and check whether the messages will go away and pop up less frequently: $ echo 20 | sudo tee /proc/sys/kernel/watchdog_thresh The above command will change the default (10) to 20 -- 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/1942952 Title: Kernel Call Trace on Secure Boot Status in linux package in Ubuntu: Incomplete Bug description: Could the call traces in dmesg be related to UEFI secure boot? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 948 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Sep 7 21:05:54 2021 InstallationDate: Installed on 2021-09-06 (1 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M |__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic root=/dev/mapper/vgkubuntu-root ro ipv6.disable=1 elevator=deadline splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 15.63 dmi.bios.vendor: Insyde dmi.bios.version: F.63 dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 76.32 dmi.modalias: dmi:bvnInsyde:bvrF.63:bd03/25/2021:br15.63:efr76.32:svnHP:pn:pvr:sku:rvnHP:rn84B6:rvrKBCVersion76.32:cvnHP:ct10:cvrChassisVersion: dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942952/+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
