Re: [Kernel-packages] [Bug 2043733] Re: HP Zbook 17 G6 internal microphone causes hard crashes
Hi Team, Sorry for the delay, I forgot to mark myself as Out of Office for yesterday. The customer got back to me on this and indicated that there is no sensitive or secret information contained in the bug report as is, so it can be made public. Apologies for any sort of confusion this caused. On Thu, Nov 23, 2023 at 9:50 AM Marc Deslauriers <2043...@bugs.launchpad.net> wrote: > Can I make this bug public so that the appropriate developers can see > it? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2043733 > > Title: > HP Zbook 17 G6 internal microphone causes hard crashes > > Status in linux package in Ubuntu: > New > > Bug description: > Anything that changes the state of the internal microphone on the HP > Zbook 17 G6 can result in a hard crash of the entire system. This > includes things like noise reduction being applied by Google Meets, > but it can be reliably replicated by just changing the volume of the > microphone until the system crashes. When the crashes occur, the logs > cut off just as they would if the system's power were completely cut. > > This behavior only occurs with the internal microphone. External > microphones (both 3.5 mm TRRS and USB microphones) do not exhibit this > same behavior. > > This behavior has been tested on 20.04, 22.04, 23.04, and 23.10 and > reliably occurs on kernels 5.4, 5.15, 6.2, and 6.5. > > This is the system device that should be responsible for handling the > internal microphone. > > description: Multimedia audio controller >product: Cannon Lake PCH cAVS >vendor: Intel Corporation >physical id: 1f.3 >bus info: pci@:00:1f.3 >logical name: card0 >logical name: /dev/snd/controlC0 >logical name: /dev/snd/hwC0D0 >logical name: /dev/snd/hwC0D2 >logical name: /dev/snd/pcmC0D0c >logical name: /dev/snd/pcmC0D0p >logical name: /dev/snd/pcmC0D31p >logical name: /dev/snd/pcmC0D3p >logical name: /dev/snd/pcmC0D4p >logical name: /dev/snd/pcmC0D5p >logical name: /dev/snd/pcmC0D6c >logical name: /dev/snd/pcmC0D7c >version: 10 >width: 64 bits >clock: 33MHz >capabilities: pm msi bus_master cap_list >configuration: driver=sof-audio-pci-intel-cnl latency=64 >resources: iomemory:400-3ff iomemory:400-3ff irq:191 > memory:404a108000-404a10bfff memory:404a00-404a0f > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043733/+subscriptions > > ** Information type changed from Private Security to Public -- 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/2043733 Title: HP Zbook 17 G6 internal microphone causes hard crashes Status in linux package in Ubuntu: New Bug description: Anything that changes the state of the internal microphone on the HP Zbook 17 G6 can result in a hard crash of the entire system. This includes things like noise reduction being applied by Google Meets, but it can be reliably replicated by just changing the volume of the microphone until the system crashes. When the crashes occur, the logs cut off just as they would if the system's power were completely cut. This behavior only occurs with the internal microphone. External microphones (both 3.5 mm TRRS and USB microphones) do not exhibit this same behavior. This behavior has been tested on 20.04, 22.04, 23.04, and 23.10 and reliably occurs on kernels 5.4, 5.15, 6.2, and 6.5. This is the system device that should be responsible for handling the internal microphone. description: Multimedia audio controller product: Cannon Lake PCH cAVS vendor: Intel Corporation physical id: 1f.3 bus info: pci@:00:1f.3 logical name: card0 logical name: /dev/snd/controlC0 logical name: /dev/snd/hwC0D0 logical name: /dev/snd/hwC0D2 logical name: /dev/snd/pcmC0D0c logical name: /dev/snd/pcmC0D0p logical name: /dev/snd/pcmC0D31p logical name: /dev/snd/pcmC0D3p logical name: /dev/snd/pcmC0D4p logical name: /dev/snd/pcmC0D5p logical name: /dev/snd/pcmC0D6c logical name: /dev/snd/pcmC0D7c version: 10 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=sof-audio-pci-intel-cnl latency=64 resources:
[Kernel-packages] [Bug 2043733] Re: HP Zbook 17 G6 internal microphone causes hard crashes
Confirmed there is no sensitive data included and set to public. Apologies for any confusion. -- 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/2043733 Title: HP Zbook 17 G6 internal microphone causes hard crashes Status in linux package in Ubuntu: New Bug description: Anything that changes the state of the internal microphone on the HP Zbook 17 G6 can result in a hard crash of the entire system. This includes things like noise reduction being applied by Google Meets, but it can be reliably replicated by just changing the volume of the microphone until the system crashes. When the crashes occur, the logs cut off just as they would if the system's power were completely cut. This behavior only occurs with the internal microphone. External microphones (both 3.5 mm TRRS and USB microphones) do not exhibit this same behavior. This behavior has been tested on 20.04, 22.04, 23.04, and 23.10 and reliably occurs on kernels 5.4, 5.15, 6.2, and 6.5. This is the system device that should be responsible for handling the internal microphone. description: Multimedia audio controller product: Cannon Lake PCH cAVS vendor: Intel Corporation physical id: 1f.3 bus info: pci@:00:1f.3 logical name: card0 logical name: /dev/snd/controlC0 logical name: /dev/snd/hwC0D0 logical name: /dev/snd/hwC0D2 logical name: /dev/snd/pcmC0D0c logical name: /dev/snd/pcmC0D0p logical name: /dev/snd/pcmC0D31p logical name: /dev/snd/pcmC0D3p logical name: /dev/snd/pcmC0D4p logical name: /dev/snd/pcmC0D5p logical name: /dev/snd/pcmC0D6c logical name: /dev/snd/pcmC0D7c version: 10 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=sof-audio-pci-intel-cnl latency=64 resources: iomemory:400-3ff iomemory:400-3ff irq:191 memory:404a108000-404a10bfff memory:404a00-404a0f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043733/+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 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux
Worth noting that Windows 10 on this same desktop has never had an issue with sleep and wake - this is a Linux-specific issue. -- 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/1997178 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver redux Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia driver 515, screen is black, and never changes after 10 minutes of waiting. However journalctl shows activity after wake (see attached log excerpt, where wake occurs around Nov 20 10:28:37 with black screen, followed by forced REISUB reboot a couple minutes later when screen failed to update). This makes me think the issue is around Nvidia driver <-> Linux kernel communication. I [previously reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134) similar black screen after wake behavior that seemed resolve with a Linux kernel update, but subsequent Linux kernel and Nvidia driver updates steadily regressed back to the previous behavior. The most recent kernel update from a few days ago (5.15.0-53-generic) never wakes from suspend (so far out of 5 trials). Previous few kernels where regression was first noticed it was 50/50 odds of successful wake, so most recent kernel is a noticeable regression. Important note: most recent kernel (5.15.0-53) upgrade freezed system mid-upgrade (first time this has happened to me on Linux in at least 5 years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB, the kernel, Nvidia drivers, and a GRUB update (in that order). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-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..0d.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 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 20 11:20:45 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131] InstallationDate: Installed on 2022-08-17 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.70 dmi.board.name: X470 Taichi Ultimate dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx:
[Kernel-packages] [Bug 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux
Upgraded to a Nvidia RTX 4090, and initially sleep seemed to work for a few weeks. After the last few kernel updates, sleep again is frequently (but not always) failing to wake, sometimes resulting in a hang at a black screen (responsive to Alt+Print+REISUB), sometimes in a automatic reboot after a couple minutes. Attaching excerpt from systemd which covers the sleep, though it does not seem to record anything related to attempted wake before the force reboot. Oddly systemd is treating it as a single boot even though the system force rebooted. ** Attachment added: "systemd log of forced reboot after wake from sleep" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1997178/+attachment/5682375/+files/rtx_4090_sleep_cannot_wake.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/1997178 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver redux Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia driver 515, screen is black, and never changes after 10 minutes of waiting. However journalctl shows activity after wake (see attached log excerpt, where wake occurs around Nov 20 10:28:37 with black screen, followed by forced REISUB reboot a couple minutes later when screen failed to update). This makes me think the issue is around Nvidia driver <-> Linux kernel communication. I [previously reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134) similar black screen after wake behavior that seemed resolve with a Linux kernel update, but subsequent Linux kernel and Nvidia driver updates steadily regressed back to the previous behavior. The most recent kernel update from a few days ago (5.15.0-53-generic) never wakes from suspend (so far out of 5 trials). Previous few kernels where regression was first noticed it was 50/50 odds of successful wake, so most recent kernel is a noticeable regression. Important note: most recent kernel (5.15.0-53) upgrade freezed system mid-upgrade (first time this has happened to me on Linux in at least 5 years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB, the kernel, Nvidia drivers, and a GRUB update (in that order). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-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..0d.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 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 20 11:20:45 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131] InstallationDate: Installed on 2022-08-17 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.70 dmi.board.name: X470 Taichi Ultimate dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be
[Kernel-packages] [Bug 2013438] Re: Add support for Pensando SoC
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-iot in Ubuntu. https://bugs.launchpad.net/bugs/2013438 Title: Add support for Pensando SoC Status in linux-iot package in Ubuntu: Fix Committed Status in linux-meta-iot package in Ubuntu: Fix Committed Status in linux-iot source package in Focal: Fix Committed Status in linux-meta-iot source package in Focal: Fix Committed Bug description: This bug is for tracking the progress of adding Pensando SoC support in focal:linux-iot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-iot/+bug/2013438/+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 2013438] Re: Add support for Pensando SoC
** Changed in: linux-iot (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-meta-iot (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-iot in Ubuntu. https://bugs.launchpad.net/bugs/2013438 Title: Add support for Pensando SoC Status in linux-iot package in Ubuntu: New Status in linux-meta-iot package in Ubuntu: New Status in linux-iot source package in Focal: Fix Committed Status in linux-meta-iot source package in Focal: Fix Committed Bug description: This bug is for tracking the progress of adding Pensando SoC support in focal:linux-iot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-iot/+bug/2013438/+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 2013438] [NEW] Add support for Pensando SoC
Public bug reported: This bug is for tracking the progress of adding Pensando SoC support in focal:linux-iot. ** Affects: linux-iot (Ubuntu) Importance: Undecided Status: New ** Affects: linux-meta-iot (Ubuntu) Importance: Undecided Status: New ** Affects: linux-iot (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux-meta-iot (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-meta-iot (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-iot (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** Changed in: linux-iot (Ubuntu Focal) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux-meta-iot (Ubuntu Focal) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux-iot (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-meta-iot (Ubuntu Focal) Status: New => 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/2013438 Title: Add support for Pensando SoC Status in linux-iot package in Ubuntu: New Status in linux-meta-iot package in Ubuntu: New Status in linux-iot source package in Focal: In Progress Status in linux-meta-iot source package in Focal: In Progress Bug description: This bug is for tracking the progress of adding Pensando SoC support in focal:linux-iot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-iot/+bug/2013438/+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 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux
Suspend still doesn't work on kernel 5.15.0-58-generic, Nvidia driver 525.78.01. No change in behavior. -- 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/1997178 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver redux Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia driver 515, screen is black, and never changes after 10 minutes of waiting. However journalctl shows activity after wake (see attached log excerpt, where wake occurs around Nov 20 10:28:37 with black screen, followed by forced REISUB reboot a couple minutes later when screen failed to update). This makes me think the issue is around Nvidia driver <-> Linux kernel communication. I [previously reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134) similar black screen after wake behavior that seemed resolve with a Linux kernel update, but subsequent Linux kernel and Nvidia driver updates steadily regressed back to the previous behavior. The most recent kernel update from a few days ago (5.15.0-53-generic) never wakes from suspend (so far out of 5 trials). Previous few kernels where regression was first noticed it was 50/50 odds of successful wake, so most recent kernel is a noticeable regression. Important note: most recent kernel (5.15.0-53) upgrade freezed system mid-upgrade (first time this has happened to me on Linux in at least 5 years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB, the kernel, Nvidia drivers, and a GRUB update (in that order). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-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..0d.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 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 20 11:20:45 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131] InstallationDate: Installed on 2022-08-17 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.70 dmi.board.name: X470 Taichi Ultimate dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Kernel-packages] [Bug 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux
Tested and confirmed that wake from sleep results in a black screen 100% of the time on 5.15.0-53-generic, but only ~10% of the time on 5.15.0-52-generic. Thus on the surface it seems 5.15.0-53-generic caused a regression. ** Package changed: xorg (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/1997178 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver redux Status in linux package in Ubuntu: New Bug description: When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia driver 515, screen is black, and never changes after 10 minutes of waiting. However journalctl shows activity after wake (see attached log excerpt, where wake occurs around Nov 20 10:28:37 with black screen, followed by forced REISUB reboot a couple minutes later when screen failed to update). This makes me think the issue is around Nvidia driver <-> Linux kernel communication. I [previously reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134) similar black screen after wake behavior that seemed resolve with a Linux kernel update, but subsequent Linux kernel and Nvidia driver updates steadily regressed back to the previous behavior. The most recent kernel update from a few days ago (5.15.0-53-generic) never wakes from suspend (so far out of 5 trials). Previous few kernels where regression was first noticed it was 50/50 odds of successful wake, so most recent kernel is a noticeable regression. Important note: most recent kernel (5.15.0-53) upgrade freezed system mid-upgrade (first time this has happened to me on Linux in at least 5 years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB, the kernel, Nvidia drivers, and a GRUB update (in that order). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-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..0d.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 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 20 11:20:45 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131] InstallationDate: Installed on 2022-08-17 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.70 dmi.board.name: X470 Taichi Ultimate dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1
[Kernel-packages] [Bug 1980371] Re: Enable Ethernet controller : Aquantia Corp. Device [1d6a:14c0]
** Changed in: linux-iot (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-iot in Ubuntu. https://bugs.launchpad.net/bugs/1980371 Title: Enable Ethernet controller : Aquantia Corp. Device [1d6a:14c0] Status in HWE Next: New Status in linux-iot package in Ubuntu: Invalid Status in linux-iot source package in Focal: Fix Committed Bug description: [Impact] Need to enable Aquantia NIC [1d6a:14c0] for an IoT project. [Fix] This series of patch in v5.8 enable the NIC https://patchwork.ozlabs.org/project/netdev/cover/20200424072729.953-1-irussk...@marvell.com/ [Test] We don't have 10GbE equipment to measure the speed, but it reaches around 1Gb/s in my test environment. $ iperf3 -c 10.102.88.47 Connecting to host 10.102.88.47, port 5201 [ 5] local 10.102.80.195 port 53346 connected to 10.102.88.47 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 115 MBytes 966 Mbits/sec 39293 KBytes [ 5] 1.00-2.00 sec 111 MBytes 933 Mbits/sec 26291 KBytes [ 5] 2.00-3.00 sec 111 MBytes 933 Mbits/sec 26291 KBytes [ 5] 3.00-4.00 sec 112 MBytes 944 Mbits/sec 26291 KBytes [ 5] 4.00-5.00 sec 111 MBytes 933 Mbits/sec 26288 KBytes [ 5] 5.00-6.00 sec 112 MBytes 944 Mbits/sec 26291 KBytes [ 5] 6.00-7.00 sec 111 MBytes 933 Mbits/sec 26293 KBytes [ 5] 7.00-8.00 sec 111 MBytes 933 Mbits/sec 26293 KBytes [ 5] 8.00-9.00 sec 112 MBytes 944 Mbits/sec 26290 KBytes [ 5] 9.00-10.00 sec 111 MBytes 933 Mbits/sec 26291 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.09 GBytes 940 Mbits/sec 273 sender [ 5] 0.00-10.00 sec 1.09 GBytes 937 Mbits/sec receiver [Where problems could occur] The series of patches only affects atlantic NIC, added some new files for new devices, but hard to evaluate other the impacts on other series of atlantic NICs. Checked and applied the necessary "Fixes" and also done suspend/resume test make sure the driver and the system is stable with those commits. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980371/+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 1973626] Re: [BlueField] linux-libc-dev corresponding to the linux-image-5.4.0-1035-bluefield is not available
@Vladimir: There is only one linux-libc-dev in the archive which is built out of the generic kernel: > apt-cache policy linux-libc-dev linux-libc-dev: Installed: 5.4.0-113.127 Candidate: 5.4.0-113.127 Version table: *** 5.4.0-113.127 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0-26.30 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages Could you explain a bit about the use case of linux-libc-dev corresponding to linux-bluefield? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1973626 Title: [BlueField] linux-libc-dev corresponding to the linux- image-5.4.0-1035-bluefield is not available Status in linux-bluefield package in Ubuntu: New Bug description: linux-libc-dev corresponding to the linux-image-5.4.0-1035-bluefield is not available Here is the "linux-libc-dev" which is available on BlueField DPU: # dpkg --list linux-libc-dev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-- ii linux-libc-dev:arm64 5.4.0-110.124 arm64Linux Kernel Headers for development But this package is not in sync with linux-bluefield. Please provide corresponding "linux-libc-dev" with every SRU kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1973626/+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 1971667] Re: Skip setting ethernet LED on Dell EMC board
** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1971667 Title: Skip setting ethernet LED on Dell EMC board Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-iotg package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-intel-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg source package in Focal: Invalid Status in linux source package in Jammy: New Status in linux-intel-5.13 source package in Jammy: New Status in linux-intel-iotg source package in Jammy: In Progress Status in linux source package in Kinetic: Confirmed Status in linux-intel-5.13 source package in Kinetic: Invalid Status in linux-intel-iotg source package in Kinetic: New Bug description: [Impact] LED is not show networking status on the said Dell EMC board. [Fix] Don't set the LED on it. [Test] Check the LED and it's showing correct status. The LED continues to work after S3. [Where problems could occur] We use a UUID to match the board, so all other users are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971667/+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 1956413] Re: Intel EHL: Two of the on-board ethernet ports don't work
** Also affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-intel-5.13 (Ubuntu Kinetic) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: Fix Released ** Also affects: linux-intel-iotg (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-intel-5.13 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: linux-intel-iotg (Ubuntu Focal) ** No longer affects: linux-intel-5.13 (Ubuntu Jammy) ** No longer affects: linux-intel-5.13 (Ubuntu Kinetic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1956413 Title: Intel EHL: Two of the on-board ethernet ports don't work Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: Fix Released Status in linux-intel-iotg source package in Jammy: New Status in linux-intel-iotg source package in Kinetic: New Bug description: == Impact == Only one of the three on-board ethernet ports works. The other two can't get IP addresses. == Fix == commit 884d2b845477cd0a18302444dc20fe2d9a01743e Author: David Wu Date: Mon Dec 13 19:15:15 2021 +0800 net: stmmac: Add GFP_DMA32 for rx buffers if no 64 capability Use page_pool_alloc_pages instead of page_pool_dev_alloc_pages, which can give the gfp parameter, in the case of not supporting 64-bit width, using 32-bit address memory can reduce a copy from swiotlb. Signed-off-by: David Wu Signed-off-by: David S. Miller == Risk of Regression == Low. The commit changes gfp parameter only when there's no 64-bit capability, and it is already in mainline. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956413/+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 1960777] Re: Bail out when USB port is stuck in reset loop
Set as verified based on the QA test result from the linked project.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1960777
Title:
Bail out when USB port is stuck in reset loop
Status in HWE Next:
New
Status in linux-intel-5.13 package in Ubuntu:
Fix Committed
Bug description:
[Impact]
USB port stops working after unplug an USB device.
[Fix]
Commit c89686118c786a523eee3ef68ed38330319626d8 ("usb: core: Bail out when
port is stuck in reset loop")
[Test]
Affected vendor confirmed the patch can fix the issue after numerous round of
tests.
[Where problems could occur]
If there's any peculiar USB hub depends on the old (and buggy) behavior, this
can potentially bring a regression to the hub.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1960777/+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 1967257] Re: Ubuntu Server lose connection when download >1G large file
Changing the tag as verified based on the report from the linked project. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1967257 Title: Ubuntu Server lose connection when download >1G large file Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Fix Committed Bug description: [Impact] WW Field test reported Foxconn T99W175 5G module lose connection issue when download > 1G large file. Similar issue can also be reproduced on Quectel EM160 4G test. [Where problems could occur] This issue will randomly occur when device download speed reach to a certain value (60Mbps ~ 100Mbps) in Linux host. And once the issue happened, need to reboot system to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967257/+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 1962674] Re: Add IIO sensors ID for ACPI based platform
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1962674 Title: Add IIO sensors ID for ACPI based platform Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Fix Committed Bug description: [Impact] On ACPI based platforms, some sensors aren't probed because driver doesn't have ACPI IDs, so they are useless. [Fix] For pressure sensor: 72ff282819d0526d3e4417c2a61414557981b5af iio: pressure: dps310: Add ACPI HID table For humidity sensor: 711b6a3f4af137c4a7f759136ccd50d455095b95 iio: humidity: hdc100x: Add ACPI HID table For accelerator sensor: b9493d595226b598ed79b3769f7038fda1a5391b iio: accel: adxl345: Add ACPI HID table The commit is part of patch series, for the whole series, please cherry-pick 01676b0f3b625a9aa608d5b716898e9dba2fb63e^..4781f3e0e6cadf332f49f723ba820f35960a058d [Test] All sensors are working under /sys/bus/iio. [Where problems could occur] Unless there's an ID collision, these patches don't really bring any change, hence no regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1962674/+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 1967257] Re: Ubuntu Server lose connection when download >1G large file
** Changed in: linux-intel-5.13 (Ubuntu) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Changed in: linux-intel-5.13 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1967257 Title: Ubuntu Server lose connection when download >1G large file Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Fix Committed Bug description: [Impact] WW Field test reported Foxconn T99W175 5G module lose connection issue when download > 1G large file. Similar issue can also be reproduced on Quectel EM160 4G test. [Where problems could occur] This issue will randomly occur when device download speed reach to a certain value (60Mbps ~ 100Mbps) in Linux host. And once the issue happened, need to reboot system to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967257/+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 1962674] Re: Add IIO sensors ID for ACPI based platform
** Changed in: linux-intel-5.13 (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1962674 Title: Add IIO sensors ID for ACPI based platform Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Fix Committed Bug description: [Impact] On ACPI based platforms, some sensors aren't probed because driver doesn't have ACPI IDs, so they are useless. [Fix] For pressure sensor: 72ff282819d0526d3e4417c2a61414557981b5af iio: pressure: dps310: Add ACPI HID table For humidity sensor: 711b6a3f4af137c4a7f759136ccd50d455095b95 iio: humidity: hdc100x: Add ACPI HID table For accelerator sensor: b9493d595226b598ed79b3769f7038fda1a5391b iio: accel: adxl345: Add ACPI HID table The commit is part of patch series, for the whole series, please cherry-pick 01676b0f3b625a9aa608d5b716898e9dba2fb63e^..4781f3e0e6cadf332f49f723ba820f35960a058d [Test] All sensors are working under /sys/bus/iio. [Where problems could occur] Unless there's an ID collision, these patches don't really bring any change, hence no regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1962674/+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 1960777] Re: Bail out when USB port is stuck in reset loop
** Changed in: linux-intel-5.13 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1960777
Title:
Bail out when USB port is stuck in reset loop
Status in HWE Next:
New
Status in linux-intel-5.13 package in Ubuntu:
Fix Committed
Bug description:
[Impact]
USB port stops working after unplug an USB device.
[Fix]
Commit c89686118c786a523eee3ef68ed38330319626d8 ("usb: core: Bail out when
port is stuck in reset loop")
[Test]
Affected vendor confirmed the patch can fix the issue after numerous round of
tests.
[Where problems could occur]
If there's any peculiar USB hub depends on the old (and buggy) behavior, this
can potentially bring a regression to the hub.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1960777/+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 1956413] Re: Intel EHL: Two of the on-board ethernet ports don't work
** Changed in: linux-intel-5.13 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956413 Title: Intel EHL: Two of the on-board ethernet ports don't work Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Fix Released Status in linux-intel-5.13 source package in Focal: Fix Released Bug description: == Impact == Only one of the three on-board ethernet ports works. The other two can't get IP addresses. == Fix == commit 884d2b845477cd0a18302444dc20fe2d9a01743e Author: David Wu Date: Mon Dec 13 19:15:15 2021 +0800 net: stmmac: Add GFP_DMA32 for rx buffers if no 64 capability Use page_pool_alloc_pages instead of page_pool_dev_alloc_pages, which can give the gfp parameter, in the case of not supporting 64-bit width, using 32-bit address memory can reduce a copy from swiotlb. Signed-off-by: David Wu Signed-off-by: David S. Miller == Risk of Regression == Low. The commit changes gfp parameter only when there's no 64-bit capability, and it is already in mainline. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956413/+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 1948377] Re: [SRU][F] USB: serial: pl2303: add support for PL2303HXN
** Changed in: linux-iot (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-iot in Ubuntu. https://bugs.launchpad.net/bugs/1948377 Title: [SRU][F] USB: serial: pl2303: add support for PL2303HXN Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-iot package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-iot source package in Focal: Fix Released Bug description: [Impact] PL2303HXN is not supported by 5.4 kernel. 5.5 kernel starts to support it. so only SRU for focal 5.4 kernel. [Fix] Clean cherry-pick upstream commits. Add support for PL2303HXN. [Test] Verified on hardware, use minicom to test serial port, it works fine. [Where problems could occur] It may break the pl2303 ttyUSBx. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1948377/+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 1948377] Re: [SRU][F] USB: serial: pl2303: add support for PL2303HXN
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-iot in Ubuntu. https://bugs.launchpad.net/bugs/1948377 Title: [SRU][F] USB: serial: pl2303: add support for PL2303HXN Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-iot package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-iot source package in Focal: Fix Committed Bug description: [Impact] PL2303HXN is not supported by 5.4 kernel. 5.5 kernel starts to support it. so only SRU for focal 5.4 kernel. [Fix] Clean cherry-pick upstream commits. Add support for PL2303HXN. [Test] Verified on hardware, use minicom to test serial port, it works fine. [Where problems could occur] It may break the pl2303 ttyUSBx. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1948377/+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 1960777] Re: Bail out when USB port is stuck in reset loop
** Changed in: linux-intel-5.13 (Ubuntu)
Assignee: Jesse Sung (wenchien) => Jian Hui Lee (jianhuilee)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1960777
Title:
Bail out when USB port is stuck in reset loop
Status in HWE Next:
New
Status in linux-intel-5.13 package in Ubuntu:
New
Bug description:
[Impact]
USB port stops working after unplug an USB device.
[Fix]
Commit c89686118c786a523eee3ef68ed38330319626d8 ("usb: core: Bail out when
port is stuck in reset loop")
[Test]
Affected vendor confirmed the patch can fix the issue after numerous round of
tests.
[Where problems could occur]
If there's any peculiar USB hub depends on the old (and buggy) behavior, this
can potentially bring a regression to the hub.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1960777/+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 1962674] Re: Add IIO sensors ID for ACPI based platform
** Changed in: linux-intel-5.13 (Ubuntu) Assignee: Jesse Sung (wenchien) => Jian Hui Lee (jianhuilee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1962674 Title: Add IIO sensors ID for ACPI based platform Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Confirmed Bug description: [Impact] On ACPI based platforms, some sensors aren't probed because driver doesn't have ACPI IDs, so they are useless. [Fix] For pressure sensor: 72ff282819d0526d3e4417c2a61414557981b5af iio: pressure: dps310: Add ACPI HID table For humidity sensor: 711b6a3f4af137c4a7f759136ccd50d455095b95 iio: humidity: hdc100x: Add ACPI HID table For accelerator sensor: b9493d595226b598ed79b3769f7038fda1a5391b iio: accel: adxl345: Add ACPI HID table The commit is part of patch series, for the whole series, please cherry-pick 01676b0f3b625a9aa608d5b716898e9dba2fb63e^..4781f3e0e6cadf332f49f723ba820f35960a058d [Test] All sensors are working under /sys/bus/iio. [Where problems could occur] Unless there's an ID collision, these patches don't really bring any change, hence no regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1962674/+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 1956413] Re: Intel EHL: Two of the on-board ethernet ports don't work
** Changed in: linux-intel-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-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956413 Title: Intel EHL: Two of the on-board ethernet ports don't work Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Triaged Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: == Impact == Only one of the three on-board ethernet ports works. The other two can't get IP addresses. == Fix == commit 884d2b845477cd0a18302444dc20fe2d9a01743e Author: David Wu Date: Mon Dec 13 19:15:15 2021 +0800 net: stmmac: Add GFP_DMA32 for rx buffers if no 64 capability Use page_pool_alloc_pages instead of page_pool_dev_alloc_pages, which can give the gfp parameter, in the case of not supporting 64-bit width, using 32-bit address memory can reduce a copy from swiotlb. Signed-off-by: David Wu Signed-off-by: David S. Miller == Risk of Regression == Low. The commit changes gfp parameter only when there's no 64-bit capability, and it is already in mainline. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956413/+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 1956413] Re: Intel EHL: Two of the on-board ethernet ports don't work
** Tags added: intel oem-priority originate-from-1937146 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956413 Title: Intel EHL: Two of the on-board ethernet ports don't work Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Triaged Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: == Impact == Only one of the three on-board ethernet ports works. The other two can't get IP addresses. == Fix == commit 884d2b845477cd0a18302444dc20fe2d9a01743e Author: David Wu Date: Mon Dec 13 19:15:15 2021 +0800 net: stmmac: Add GFP_DMA32 for rx buffers if no 64 capability Use page_pool_alloc_pages instead of page_pool_dev_alloc_pages, which can give the gfp parameter, in the case of not supporting 64-bit width, using 32-bit address memory can reduce a copy from swiotlb. Signed-off-by: David Wu Signed-off-by: David S. Miller == Risk of Regression == Low. The commit changes gfp parameter only when there's no 64-bit capability, and it is already in mainline. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956413/+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 1956413] [NEW] Intel EHL: Two of the on-board ethernet ports don't work
Public bug reported: == Impact == Only one of the three on-board ethernet ports works. The other two can't get IP addresses. == Fix == commit 884d2b845477cd0a18302444dc20fe2d9a01743e Author: David Wu Date: Mon Dec 13 19:15:15 2021 +0800 net: stmmac: Add GFP_DMA32 for rx buffers if no 64 capability Use page_pool_alloc_pages instead of page_pool_dev_alloc_pages, which can give the gfp parameter, in the case of not supporting 64-bit width, using 32-bit address memory can reduce a copy from swiotlb. Signed-off-by: David Wu Signed-off-by: David S. Miller == Risk of Regression == Low. The commit changes gfp parameter only when there's no 64-bit capability, and it is already in mainline. ** Affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: Triaged ** Affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu Focal) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956413 Title: Intel EHL: Two of the on-board ethernet ports don't work Status in linux-intel-5.13 package in Ubuntu: Triaged Status in linux-intel-5.13 source package in Focal: In Progress Bug description: == Impact == Only one of the three on-board ethernet ports works. The other two can't get IP addresses. == Fix == commit 884d2b845477cd0a18302444dc20fe2d9a01743e Author: David Wu Date: Mon Dec 13 19:15:15 2021 +0800 net: stmmac: Add GFP_DMA32 for rx buffers if no 64 capability Use page_pool_alloc_pages instead of page_pool_dev_alloc_pages, which can give the gfp parameter, in the case of not supporting 64-bit width, using 32-bit address memory can reduce a copy from swiotlb. Signed-off-by: David Wu Signed-off-by: David S. Miller == Risk of Regression == Low. The commit changes gfp parameter only when there's no 64-bit capability, and it is already in mainline. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-5.13/+bug/1956413/+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 1952077] Re: System time doesn't sync with RTC time on boot
The patch was NAKed: https://lists.ubuntu.com/archives/kernel- team/2021-November/126087.html Change the status back to confirmed. ** Changed in: linux (Ubuntu) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Focal) Status: In Progress => 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/1952077 Title: System time doesn't sync with RTC time on boot Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: == Impact == Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE to "rtc0", system time would only be set if the RTC driver is built-in. This may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for amd64, however it is an issue for other architectures since there may not be a proper RTC driver enabled as built-in. Also making every RTC driver that may be used as built-in is not a good option. == Fix == The commit is in mainline since v5.7: commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f Author: Steve Muckle Date: Wed Nov 6 11:46:25 2019 -0800 rtc: class: support hctosys from modular RTC drivers Due to distribution constraints it may not be possible to statically compile the required RTC driver into the kernel. Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled or not) by checking at the end of RTC device registration whether the time should be synced. Signed-off-by: Steve Muckle Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com Signed-off-by: Alexandre Belloni == Risk of Regression == It's a clean cherry-pick for v5.4 and looks straight forward so risk should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952077/+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 1952077] Re: System time doesn't sync with RTC time on boot
** Description changed: == Impact == - Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE to "rtc0", system time would only be set if the RTC driver is built-in. This may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for amd64, however it is an issue for other architectures since there may not be a proper RTC driver enabled as built-in. Also make every RTC driver that may be used as built-in is not a good option. + Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE to "rtc0", system time would only be set if the RTC driver is built-in. This may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for amd64, however it is an issue for other architectures since there may not be a proper RTC driver enabled as built-in. Also making every RTC driver that may be used as built-in is not a good option. == Fix == The commit is in mainline since v5.7: commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f Author: Steve Muckle Date: Wed Nov 6 11:46:25 2019 -0800 - rtc: class: support hctosys from modular RTC drivers - - Due to distribution constraints it may not be possible to statically - compile the required RTC driver into the kernel. - - Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled - or not) by checking at the end of RTC device registration whether the - time should be synced. - - Signed-off-by: Steve Muckle - Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com - Signed-off-by: Alexandre Belloni + rtc: class: support hctosys from modular RTC drivers + + Due to distribution constraints it may not be possible to statically + compile the required RTC driver into the kernel. + + Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled + or not) by checking at the end of RTC device registration whether the + time should be synced. + + Signed-off-by: Steve Muckle + Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com + Signed-off-by: Alexandre Belloni == Risk of Regression == It's a clean cherry-pick for v5.4 and looks straight forward so risk should be 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/1952077 Title: System time doesn't sync with RTC time on boot Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: == Impact == Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE to "rtc0", system time would only be set if the RTC driver is built-in. This may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for amd64, however it is an issue for other architectures since there may not be a proper RTC driver enabled as built-in. Also making every RTC driver that may be used as built-in is not a good option. == Fix == The commit is in mainline since v5.7: commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f Author: Steve Muckle Date: Wed Nov 6 11:46:25 2019 -0800 rtc: class: support hctosys from modular RTC drivers Due to distribution constraints it may not be possible to statically compile the required RTC driver into the kernel. Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled or not) by checking at the end of RTC device registration whether the time should be synced. Signed-off-by: Steve Muckle Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com Signed-off-by: Alexandre Belloni == Risk of Regression == It's a clean cherry-pick for v5.4 and looks straight forward so risk should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952077/+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 1952077] Re: System time doesn't sync with RTC time on boot
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jesse Sung (wenchien) -- 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/1952077 Title: System time doesn't sync with RTC time on boot Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: == Impact == Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE to "rtc0", system time would only be set if the RTC driver is built-in. This may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for amd64, however it is an issue for other architectures since there may not be a proper RTC driver enabled as built-in. Also make every RTC driver that may be used as built-in is not a good option. == Fix == The commit is in mainline since v5.7: commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f Author: Steve Muckle Date: Wed Nov 6 11:46:25 2019 -0800 rtc: class: support hctosys from modular RTC drivers Due to distribution constraints it may not be possible to statically compile the required RTC driver into the kernel. Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled or not) by checking at the end of RTC device registration whether the time should be synced. Signed-off-by: Steve Muckle Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com Signed-off-by: Alexandre Belloni == Risk of Regression == It's a clean cherry-pick for v5.4 and looks straight forward so risk should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952077/+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 1952077] [NEW] System time doesn't sync with RTC time on boot
Public bug reported: == Impact == Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE to "rtc0", system time would only be set if the RTC driver is built-in. This may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for amd64, however it is an issue for other architectures since there may not be a proper RTC driver enabled as built-in. Also make every RTC driver that may be used as built-in is not a good option. == Fix == The commit is in mainline since v5.7: commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f Author: Steve Muckle Date: Wed Nov 6 11:46:25 2019 -0800 rtc: class: support hctosys from modular RTC drivers Due to distribution constraints it may not be possible to statically compile the required RTC driver into the kernel. Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled or not) by checking at the end of RTC device registration whether the time should be synced. Signed-off-by: Steve Muckle Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com Signed-off-by: Alexandre Belloni == Risk of Regression == It's a clean cherry-pick for v5.4 and looks straight forward so risk should be low. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Jesse Sung (wenchien) -- 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/1952077 Title: System time doesn't sync with RTC time on boot Status in linux package in Ubuntu: New Status in linux source package in Focal: In Progress Bug description: == Impact == Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE to "rtc0", system time would only be set if the RTC driver is built-in. This may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for amd64, however it is an issue for other architectures since there may not be a proper RTC driver enabled as built-in. Also make every RTC driver that may be used as built-in is not a good option. == Fix == The commit is in mainline since v5.7: commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f Author: Steve Muckle Date: Wed Nov 6 11:46:25 2019 -0800 rtc: class: support hctosys from modular RTC drivers Due to distribution constraints it may not be possible to statically compile the required RTC driver into the kernel. Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled or not) by checking at the end of RTC device registration whether the time should be synced. Signed-off-by: Steve Muckle Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com Signed-off-by: Alexandre Belloni == Risk of Regression == It's a clean cherry-pick for v5.4 and looks straight forward so risk should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952077/+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 1945938] Re: [impish] Remove the downstream xr-usb-uart driver
** Tags removed: verification-done-focal ** Tags added: verification-needed-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/1945938 Title: [impish] Remove the downstream xr-usb-uart driver Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: Fix Released Bug description: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. [This is a tracking bug, please do not triage] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945938/+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 1945938] Re: [impish] Remove the downstream xr-usb-uart driver
** Tags removed: verification-needed-focal ** Tags added: verification-done-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/1945938 Title: [impish] Remove the downstream xr-usb-uart driver Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: Fix Released Bug description: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. [This is a tracking bug, please do not triage] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945938/+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 1950721] Re: Re-enable CONFIG_PINCTRL_ELKHARTLAKE
** Changed in: linux-intel-5.13 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950721 Title: Re-enable CONFIG_PINCTRL_ELKHARTLAKE Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Fix Committed Bug description: We have test BIOS now for supporting pinctrl. From what we learnt, ODMs also got the BIOS fix, it's now time to re-enable this kernel config. [Impact] Without this fix, pinctrl functionality will be missing. [Test plan] 1. Make sure the computer has a BIOS that supports pinctrl for EHL 2. Before installing the new kernel, GPIO should not work 3. Install the new kernel, and confirm GPIO works [Where problems could occur] If the computer does not have a BIOS that support pinctrl, you will get an error like "kernel NULL pointer dereference in intel_pinctrl_get_soc_data" during system boot. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950721/+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 1950721] Re: Re-enable CONFIG_PINCTRL_ELKHARTLAKE
** Changed in: linux-intel-5.13 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950721 Title: Re-enable CONFIG_PINCTRL_ELKHARTLAKE Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: In Progress Bug description: We have test BIOS now for supporting pinctrl. From what we learnt, ODMs also got the BIOS fix, it's now time to re-enable this kernel config. [Impact] Without this fix, pinctrl functionality will be missing. [Test plan] 1. Make sure the computer has a BIOS that supports pinctrl for EHL 2. Before installing the new kernel, GPIO should not work 3. Install the new kernel, and confirm GPIO works [Where problems could occur] If the computer does not have a BIOS that support pinctrl, you will get an error like "kernel NULL pointer dereference in intel_pinctrl_get_soc_data" during system boot. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950721/+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 1948377] Re: [SRU][F] USB: serial: pl2303: add support for PL2303HXN
** Also affects: linux-iot (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-iot (Ubuntu) Status: New => Invalid ** Changed in: linux-iot (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-iot (Ubuntu Focal) Assignee: (unassigned) => AaronMa (mapengyu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-iot in Ubuntu. https://bugs.launchpad.net/bugs/1948377 Title: [SRU][F] USB: serial: pl2303: add support for PL2303HXN Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-iot package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-iot source package in Focal: Fix Committed Bug description: [Impact] PL2303HXN is not supported by 5.4 kernel. 5.5 kernel starts to support it. so only SRU for focal 5.4 kernel. [Fix] Clean cherry-pick upstream commits. Add support for PL2303HXN. [Test] Verified on hardware, use minicom to test serial port, it works fine. [Where problems could occur] It may break the pl2303 ttyUSBx. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1948377/+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 1946219] Re: liburing stops working after upgrading to 5.4.0-1012
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1946219 Title: liburing stops working after upgrading to 5.4.0-1012 Status in HWE Next: New Status in linux-bluefield package in Ubuntu: In Progress Status in linux-bluefield source package in Focal: Fix Committed Bug description: == Impact == After configuration multipath with io uring virtio_blk module is stuck == Fix == The issue was introduced by one of the stable updates merged in the base kernel Ubuntu-5.4.0-74.83. After reverting the commit the issue can not be reproduced any more. commit d6757b3e34831b7615edd3268b878536761f8b2e Author: Pavel Begunkov Date: Fri Nov 20 17:10:28 2020 + block: don't ignore REQ_NOWAIT for direct IO BugLink: https://bugs.launchpad.net/bugs/1926490 [ Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5 ] If IOCB_NOWAIT is set on submission, then that needs to get propagated to REQ_NOWAIT on the block side. Otherwise we completely lose this information, and any issuer of IOCB_NOWAIT IO will potentially end up blocking on eg request allocation on the storage side. Signed-off-by: Pavel Begunkov Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Stefan Bader == Risk of Regression == Medium. The commit has a good reason to be part of the stable updates. However the kernel passes Cert and Nvidia tests without the commit so reverting the commit should be an acceptable approach for now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946219/+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 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot
** Changed in: linux-intel-5.13 (Ubuntu Focal) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1946223 Title: [iotg][tgl][tgl-aaeon] 20211006 image does not boot Status in intel: In Progress Status in linux-intel-5.13 package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: The daily build containing the new kernel does not boot. It gets stuck about 2 seconds into the cycle with the message "Run /init as init process" (see attached image file for boot message sequence.) System: TGL-Aaeon (CID: 202110-29509) Steps to reproduce: Downloaded focal-preinstalled-desktop-amd64+intel-iot.img.xz from https://cdimage.ubuntu.com/focal/daily-preinstalled/20211006/ Uncompressed file with unxz -k Copied the .img file to my secondary USB drive. Boot 20.04 LTS from primary USB drive. Select Try Ubuntu Wipe out /dev/sda (primary storage) Use dd to copy the image from secondary USB drive to /dev/sda Reboot, removing USB drives when prompted. Expected Result: System should boot Ubuntu Desktop with kernel 5.13-1006 Actual Result: System hangs 2 seconds into the boot cycle with "Run /init as init process" Reproducibility: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1946223/+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 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot
** Also affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1946223 Title: [iotg][tgl][tgl-aaeon] 20211006 image does not boot Status in intel: In Progress Status in linux-intel-5.13 package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: The daily build containing the new kernel does not boot. It gets stuck about 2 seconds into the cycle with the message "Run /init as init process" (see attached image file for boot message sequence.) System: TGL-Aaeon (CID: 202110-29509) Steps to reproduce: Downloaded focal-preinstalled-desktop-amd64+intel-iot.img.xz from https://cdimage.ubuntu.com/focal/daily-preinstalled/20211006/ Uncompressed file with unxz -k Copied the .img file to my secondary USB drive. Boot 20.04 LTS from primary USB drive. Select Try Ubuntu Wipe out /dev/sda (primary storage) Use dd to copy the image from secondary USB drive to /dev/sda Reboot, removing USB drives when prompted. Expected Result: System should boot Ubuntu Desktop with kernel 5.13-1006 Actual Result: System hangs 2 seconds into the boot cycle with "Run /init as init process" Reproducibility: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1946223/+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 1946219] [NEW] liburing stops working after upgrading to 5.4.0-1012
Public bug reported: == Impact == After configuration multipath with io uring virtio_blk module is stuck == Fix == The issue was introduced by one of the stable updates merged in the base kernel Ubuntu-5.4.0-74.83. After reverting the commit the issue can not be reproduced any more. commit d6757b3e34831b7615edd3268b878536761f8b2e Author: Pavel Begunkov Date: Fri Nov 20 17:10:28 2020 + block: don't ignore REQ_NOWAIT for direct IO BugLink: https://bugs.launchpad.net/bugs/1926490 [ Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5 ] If IOCB_NOWAIT is set on submission, then that needs to get propagated to REQ_NOWAIT on the block side. Otherwise we completely lose this information, and any issuer of IOCB_NOWAIT IO will potentially end up blocking on eg request allocation on the storage side. Signed-off-by: Pavel Begunkov Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Stefan Bader == Risk of Regression == Medium. The commit has a good reason to be part of the stable updates. However the kernel passes Cert and Nvidia tests without the commit so reverting the commit should be an acceptable approach for now. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Tags: chelmsford oem-priority originate-from-1935996 ** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Jesse Sung (wenchien) ** Tags added: chelmsford oem-priority originate-from-1935996 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1946219 Title: liburing stops working after upgrading to 5.4.0-1012 Status in HWE Next: New Status in linux-bluefield package in Ubuntu: In Progress Status in linux-bluefield source package in Focal: In Progress Bug description: == Impact == After configuration multipath with io uring virtio_blk module is stuck == Fix == The issue was introduced by one of the stable updates merged in the base kernel Ubuntu-5.4.0-74.83. After reverting the commit the issue can not be reproduced any more. commit d6757b3e34831b7615edd3268b878536761f8b2e Author: Pavel Begunkov Date: Fri Nov 20 17:10:28 2020 + block: don't ignore REQ_NOWAIT for direct IO BugLink: https://bugs.launchpad.net/bugs/1926490 [ Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5 ] If IOCB_NOWAIT is set on submission, then that needs to get propagated to REQ_NOWAIT on the block side. Otherwise we completely lose this information, and any issuer of IOCB_NOWAIT IO will potentially end up blocking on eg request allocation on the storage side. Signed-off-by: Pavel Begunkov Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Stefan Bader == Risk of Regression == Medium. The commit has a good reason to be part of the stable updates. However the kernel passes Cert and Nvidia tests without the commit so reverting the commit should be an acceptable approach for now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946219/+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 1945461] Re: Integrated TSN controller for sprint 2
** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945461 Title: Integrated TSN controller for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945461/+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 1945462] Re: EHL graphics support for sprint 2
** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945462 Title: EHL graphics support for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945462/+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 1943524] Re: [EHL] Intel ishtp VNIC driver
** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1943524 Title: [EHL] Intel ishtp VNIC driver Status in intel: New Status in linux-intel-5.13 package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description The driver enables a virtual network interface for communicating with a dedicated low power chip over ISHTP Hardware: ElkhartLake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.13-yocto-210727T062416Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1943524/+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 1945494] Re: [EHL] Quadrature Encoder Peripheral support for sprint 2
** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945494 Title: [EHL] Quadrature Encoder Peripheral support for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945494/+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 1945464] Re: MEI (Intel Management Engine Interface) for sprint 2
** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945464 Title: MEI (Intel Management Engine Interface) for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945464/+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 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945548 Title: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board Status in intel: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: [Summary] I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board [Steps to reproduce] 1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to the system 2. Boot to desktop 3. Check if all Ethernet get IP address [Expected result] All Ethernet Port should up and runing and get the IP address. [Actual result] I225-IT Ethernet (8086:0d9f) does not work and did not get IP address [Failure rate] 100% [Additional information] CID: 202109-29492 SKU: N/A system-manufacturer: AAEON system-product-name: UPN-EHL01 bios-version: UNEHAM0D CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] (rev 01) kernel-version: 5.13.0-1004-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1945548/+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 1929889] Re: [TGL] Enable Tiger Lake ROP CET(Control-flow Enforcement Technology)
** Also affects: linux-intel (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel (Ubuntu Focal) Assignee: (unassigned) => Alex Hung (alexhung) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929889 Title: [TGL] Enable Tiger Lake ROP CET(Control-flow Enforcement Technology) Status in intel: New Status in linux-intel package in Ubuntu: Triaged Status in linux-intel source package in Focal: New Bug description: Description Enable Tiger Lake ROP CET(Control-flow Enforcement Technology) An upcoming Intel® processor family feature that counters return/jump-oriented programming (ROP) attacks Hardware: Tiger Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929889/+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 1929894] Re: [TGL][EHL] Enable MEI (Intel Management Engine Interface)
** Also affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-intel (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929894 Title: [TGL][EHL] Enable MEI (Intel Management Engine Interface) Status in intel: New Status in linux package in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: Triaged Status in linux-intel-5.13 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-intel source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description Enable MEI (Intel Management Engine Interface) Host communicates with secured apps in firmware with this interface Hardware: Tiger Lake & Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929894/+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 1929890] Re: [EHL][TGL] PMC Time-aware GPIO
** Also affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-intel (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929890 Title: [EHL][TGL] PMC Time-aware GPIO Status in intel: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: New Status in linux-intel source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description GPIO controller on CNL PCH has a new feature which allows for timed trigger of GPIO events. We should consider at least following aspects and if needed we can create subtasks: Translation of ART->System Time on input Any output GPIO Cross-timestamp and/or edge counting of input GPIOs supporting high frequency input Similar feature to input, counting output edges Time Aware GPIO Frequency Discipline - GPIO Frequency Adjustment Time Aware GPIO Output - Fire on Trigger Time Aware GPIO Input - Stamp on Edge Detection Hardware: Tiger Lake & Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929890/+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 1929895] Re: [EHL] Enable ISHTP
** Also affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929895 Title: [EHL] Enable ISHTP Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description This driver enables the OS to talk to eclite firmware on a dedicated low power chip over ISH Transport Protocol (ISHTP) Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929895/+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 1938298] Re: [EHL][Graphic]Removing force probe protection from EHL platform
** Also affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-intel (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: Ubuntu Focal Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1938298 Title: [EHL][Graphic]Removing force probe protection from EHL platform Status in intel: Fix Committed Status in Ubuntu: New Status in linux-intel package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: New Status in The Focal Fossa: New Status in linux-intel source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description The graphic driver i915 must be mounted manually instead of automatically. Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://anongit.freedesktop.org/git/drm-tip.git To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938298/+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 1929903] Re: [EHL][TGL] Enable Time Coordinated Compute interface driver
** Also affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-intel (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929903 Title: [EHL][TGL] Enable Time Coordinated Compute interface driver Status in intel: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: New Status in linux-intel source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology Hardware: Tiger Lake & Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z --- [Update, 2021-08-26] Please find the Getting Started Guide for Intel TCC Tools here, has steps to download, install and verify: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top.html You can find the BIOS settings to enable TCC here: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top/step-6-configure- intel-tcc-tools-in-bios.html To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929903/+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 1929890] Re: [EHL][TGL] PMC Time-aware GPIO
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929890 Title: [EHL][TGL] PMC Time-aware GPIO Status in intel: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Bug description: Description GPIO controller on CNL PCH has a new feature which allows for timed trigger of GPIO events. We should consider at least following aspects and if needed we can create subtasks: Translation of ART->System Time on input Any output GPIO Cross-timestamp and/or edge counting of input GPIOs supporting high frequency input Similar feature to input, counting output edges Time Aware GPIO Frequency Discipline - GPIO Frequency Adjustment Time Aware GPIO Output - Fire on Trigger Time Aware GPIO Input - Stamp on Edge Detection Hardware: Tiger Lake & Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929890/+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 1929894] Re: [TGL][EHL] Enable MEI (Intel Management Engine Interface)
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929894 Title: [TGL][EHL] Enable MEI (Intel Management Engine Interface) Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: Triaged Bug description: Description Enable MEI (Intel Management Engine Interface) Host communicates with secured apps in firmware with this interface Hardware: Tiger Lake & Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929894/+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 1929895] Re: [EHL] Enable ISHTP
** Information type changed from Private to Public -- 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/1929895 Title: [EHL] Enable ISHTP Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Description This driver enables the OS to talk to eclite firmware on a dedicated low power chip over ISH Transport Protocol (ISHTP) Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929895/+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 1929903] Re: [EHL][TGL] Enable Time Coordinated Compute interface driver
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929903 Title: [EHL][TGL] Enable Time Coordinated Compute interface driver Status in intel: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Bug description: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology Hardware: Tiger Lake & Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z --- [Update, 2021-08-26] Please find the Getting Started Guide for Intel TCC Tools here, has steps to download, install and verify: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top.html You can find the BIOS settings to enable TCC here: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top/step-6-configure- intel-tcc-tools-in-bios.html To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929903/+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 1938298] Re: [EHL][Graphic]Removing force probe protection from EHL platform
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938298 Title: [EHL][Graphic]Removing force probe protection from EHL platform Status in intel: Fix Committed Status in Ubuntu: New Status in linux-intel package in Ubuntu: Fix Committed Bug description: Description The graphic driver i915 must be mounted manually instead of automatically. Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://anongit.freedesktop.org/git/drm-tip.git To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938298/+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 1929902] Re: [EHL] enable USB-dw3
** Changed in: linux-intel (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929902 Title: [EHL] enable USB-dw3 Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: Fix Committed Bug description: Description Enable USB-dw3 for Elkhart Lake Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929902/+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 1938408] Re: EHL board does not support soft reboot
** Changed in: linux-intel (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938408 Title: EHL board does not support soft reboot Status in intel: New Status in linux-intel package in Ubuntu: Fix Committed Bug description: [Summary]Telling the EHL board to reboot from within Ubuntu causes it to hang, forcing you to do a hard reboot. [Steps to reproduce] 1. Open terminal window. 2. $ reboot [Expected result] System should gracefullyl reboot. [Actual result] Screen goes blank except for a cursor. System does not reboot. You must hard reboot (pull the plug) [Failure rate]100% [Additional information] CID: 202105-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938408/+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 1938413] Re: Shutdown hangs on EHL board
** Changed in: linux-intel (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938413 Title: Shutdown hangs on EHL board Status in intel: New Status in linux-intel package in Ubuntu: Fix Committed Bug description: [Summary]Go to Power -> Shutdown and the screen goes blank, but the system does not shut down. You cannot recover and have to perform a hard reboot. [Steps to reproduce] 1. Boot up Ubuntu 2. Power -> Shutdown (click ok) [Expected result] System should cleanly shut down. [Actual result] Screen blanks with a blinking cursor, the system does not shut down, the fan is still on. System is unresponsive, forcing you to do a hard reset. [Failure rate]100% [Additional information] CID: 20215-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel [Stage] Device froze, issue reported and logs collected right after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938413/+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 1929902] Re: [EHL] enable USB-dw3
@Chao Qin: Since the patch itself doesn't change the functionality or PM capabilities, do you mean that there are other patches (other than 457d22850b27de3aea336108272d08602c55fdf7) need to be merged in order to make the platform switch to low power mode when it can do so? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929902 Title: [EHL] enable USB-dw3 Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: In Progress Bug description: Description Enable USB-dw3 for Elkhart Lake Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929902/+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 1929902] Re: [EHL] enable USB-dw3
@Chao Qin: I'm wondering if we need this commit in order to fulfill the goal of enabling USB-dw3? Commit 457d22850b27de3aea336108272d08602c55fdf7 does nothing but `s/PCI_DEVICE_ID_INTEL_EHLLP/PCI_DEVICE_ID_INTEL_EHL/'. Although the commit makes it more clear, it should not affect the functionality of the driver? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929902 Title: [EHL] enable USB-dw3 Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: In Progress Bug description: Description Enable USB-dw3 for Elkhart Lake Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929902/+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 1929902] Re: [EHL] enable USB-dw3
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929902 Title: [EHL] enable USB-dw3 Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: In Progress Bug description: Description Enable USB-dw3 for Elkhart Lake Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929902/+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 1929892] Re: [TGL] enable USB-dw3
** Changed in: linux-intel (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929892 Title: [TGL] enable USB-dw3 Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: Fix Committed Bug description: Description Enable USB-dw3 for Tiger Lake Hardware: Tiger Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929892/+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 1929901] Re: [EHL][TGL] EDAC support
** Changed in: linux-intel (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929901 Title: [EHL][TGL] EDAC support Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: Fix Committed Bug description: Description EDAC driver support on EHL & TGL for reporting ECC error and DIMM location Hardware: Tiger Lake & Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929901/+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 1929892] Re: [TGL] enable USB-dw3
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929892 Title: [TGL] enable USB-dw3 Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: In Progress Bug description: Description Enable USB-dw3 for Tiger Lake Hardware: Tiger Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929892/+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 1929901] Re: [EHL][TGL] EDAC support
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929901 Title: [EHL][TGL] EDAC support Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: In Progress Bug description: Description EDAC driver support on EHL & TGL for reporting ECC error and DIMM location Hardware: Tiger Lake & Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929901/+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 1932042] Re: Change CONFIG_NF_CONNTRACK to y
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1932042 Title: Change CONFIG_NF_CONNTRACK to y Status in linux-bluefield package in Ubuntu: In Progress Status in linux-bluefield source package in Focal: Fix Committed Bug description: == Impact == NVIDIA would like to have CONFIG_NF_CONNTRACK as y instead of m. == Fix == CONFIG_NF_CONNTRACK=y The feature is already enabled as a module. Since it would always get loaded because they would enable firewall by default, changing it to builtin shouldn't make any harm. == Risk of Regression == Low. This is already enabled as a module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1932042/+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 1912752] Re: linux-uc20-efi: megaraid_sas required in the initrd
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Focal) Status: In Progress => Invalid ** Changed in: hwe-next Status: New => 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/1912752 Title: linux-uc20-efi: megaraid_sas required in the initrd Status in HWE Next: Invalid Status in ubuntu-core-initramfs: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Bug description: == Impact == Dell R340 fails to boot with UC20 pc-kernel snap because of unable to find the storage device. == Fix == In this case, storage disks are connected through a controller enabled by kernel module megaraid_sas, hence the module must be presented in the initrd in order to make the system boot. == Risk of Regression == Low. We're only adding an existing module into the initrd. The only downside may be the small increase of the snap size. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912752/+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 1912752] [NEW] linux-uc20-efi: megaraid_sas required in the initrd
Public bug reported: == Impact == Dell R340 fails to boot with UC20 pc-kernel snap because of unable to find the storage device. == Fix == In this case, storage disks are connected through a controller enabled by kernel module megaraid_sas, hence the module must be presented in the initrd in order to make the system boot. == Risk of Regression == Low. We're only adding an existing module into the initrd. The only downside may be the small increase of the snap size. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Tags: elgin oem-priority originate-from-1911361 ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Jesse Sung (wenchien) ** Tags added: elgin oem-priority originate-from-1911361 ** Description changed: == Impact == - System fails to boot with UC20 pc-kernel snap because of unable to find the storage device. + Dell R340 fails to boot with UC20 pc-kernel snap because of unable to find the storage device. == Fix == In this case, storage disks are connected through a controller enabled by kernel module megaraid_sas, hence the module must be presented in the initrd in order to make the system boot. == Risk of Regression == Low. We're only adding an existing module into the initrd. The only downside may be the small increase of the snap size. ** Summary changed: - linux-uc20-efi: extra kernel modules required in the initrd + linux-uc20-efi: megaraid_sas required in the initrd -- 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/1912752 Title: linux-uc20-efi: megaraid_sas required in the initrd Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: == Impact == Dell R340 fails to boot with UC20 pc-kernel snap because of unable to find the storage device. == Fix == In this case, storage disks are connected through a controller enabled by kernel module megaraid_sas, hence the module must be presented in the initrd in order to make the system boot. == Risk of Regression == Low. We're only adding an existing module into the initrd. The only downside may be the small increase of the snap size. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912752/+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 1895803] Re: uvcvideo: add mapping for HEVC payloads
** Tags removed: verification-needed-focal verification-needed-groovy ** Tags added: verification-done-focal verification-done-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/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895803/+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 1897299] Re: mwifiex stops working after kernel upgrade
** Tags removed: verification-needed-bionic verification-needed-focal
** Tags added: verification-done-bionic verification-done-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/1897299
Title:
mwifiex stops working after kernel upgrade
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Released
Bug description:
== Impact ==
Marvell WiFi cards supported by the mwifiex driver may fail to connect to
some access points after kernel upgrade.
This is caused by the commit
commit e18696786548244914f36ec3c46ac99c53df99c3
Author: Dan Carpenter
Date: Wed Jul 8 14:58:57 2020 +0300
mwifiex: Prevent memory corruption handling keys
The length of the key comes from the network and it's a 16 bit number. It
needs to be capped to prevent a buffer overflow.
Fixes: 5e6e3a92b9a4 ("wireless: mwifiex: initial commit for Marvell
mwifiex driver")
Signed-off-by: Dan Carpenter
Acked-by: Ganapathi Bhat
Signed-off-by: Kalle Valo
Link: https://lore.kernel.org/r/20200708115857.GA13729@mwanda
The commit added a check to mwifiex_ret_802_11_key_material_v2() to
make sure the key length doesn't larger than the key buffer size
before copying it. The allocated key buffer is 16-byte long. In some
cases the key would be 32-byte long and hence the check fails. One
thing to note is that this commit is not the cause of the problem,
instead it just makes the issue visible.
The commit is included in Ubuntu-4.4.0-190.220, Ubuntu-4.15.0-119.120,
Ubuntu-5.4.0-48.52, and Ubuntu-5.8.0-18.19.
== Fix ==
There's already a fix in the mainline which increase the key buffer size to
32 bytes:
commit 4afc850e2e9e781976fb2c7852ce7bac374af938
Author: Maximilian Luz
Date: Tue Aug 25 17:38:29 2020 +0200
mwifiex: Increase AES key storage size to 256 bits
Following commit e18696786548 ("mwifiex: Prevent memory corruption
handling keys") the mwifiex driver fails to authenticate with certain
networks, specifically networks with 256 bit keys, and repeatedly asks
for the password. The kernel log repeats the following lines (id and
bssid redacted):
mwifiex_pcie :01:00.0: info: trying to associate to '' bssid
mwifiex_pcie :01:00.0: info: associated to bssid
successfully
mwifiex_pcie :01:00.0: crypto keys added
mwifiex_pcie :01:00.0: info: successfully disconnected from
: reason code 3
Tracking down this problem lead to the overflow check introduced by the
aforementioned commit into mwifiex_ret_802_11_key_material_v2(). This
check fails on networks with 256 bit keys due to the current storage
size for AES keys in struct mwifiex_aes_param being only 128 bit.
To fix this issue, increase the storage size for AES keys to 256 bit.
Fixes: e18696786548 ("mwifiex: Prevent memory corruption handling keys")
Signed-off-by: Maximilian Luz
Reported-by: Kaloyan Nikolov
Tested-by: Kaloyan Nikolov
Reviewed-by: Dan Carpenter
Reviewed-by: Brian Norris
Tested-by: Brian Norris
Signed-off-by: Kalle Valo
Link:
https://lore.kernel.org/r/20200825153829.38043-1-luzmaximil...@gmail.com
== Regression Potential ==
Low. While the fix increases the buffer size, it still checks and make sure
data to be copy can fit into the buffer. Also the commit does fix the issue we
saw in the Cert lab.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1897299/+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 1895803] Re: uvcvideo: add mapping for HEVC payloads
** Changed in: hwe-next Status: Confirmed => Fix Released -- 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/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895803/+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 1895803] Re: uvcvideo: add mapping for HEVC payloads
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in HWE Next: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895803/+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 1897299] Re: mwifiex stops working after kernel upgrade
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1897299
Title:
mwifiex stops working after kernel upgrade
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Bug description:
== Impact ==
Marvell WiFi cards supported by the mwifiex driver may fail to connect to
some access points after kernel upgrade.
This is caused by the commit
commit e18696786548244914f36ec3c46ac99c53df99c3
Author: Dan Carpenter
Date: Wed Jul 8 14:58:57 2020 +0300
mwifiex: Prevent memory corruption handling keys
The length of the key comes from the network and it's a 16 bit number. It
needs to be capped to prevent a buffer overflow.
Fixes: 5e6e3a92b9a4 ("wireless: mwifiex: initial commit for Marvell
mwifiex driver")
Signed-off-by: Dan Carpenter
Acked-by: Ganapathi Bhat
Signed-off-by: Kalle Valo
Link: https://lore.kernel.org/r/20200708115857.GA13729@mwanda
The commit added a check to mwifiex_ret_802_11_key_material_v2() to
make sure the key length doesn't larger than the key buffer size
before copying it. The allocated key buffer is 16-byte long. In some
cases the key would be 32-byte long and hence the check fails. One
thing to note is that this commit is not the cause of the problem,
instead it just makes the issue visible.
The commit is included in Ubuntu-4.4.0-190.220, Ubuntu-4.15.0-119.120,
Ubuntu-5.4.0-48.52, and Ubuntu-5.8.0-18.19.
== Fix ==
There's already a fix in the mainline which increase the key buffer size to
32 bytes:
commit 4afc850e2e9e781976fb2c7852ce7bac374af938
Author: Maximilian Luz
Date: Tue Aug 25 17:38:29 2020 +0200
mwifiex: Increase AES key storage size to 256 bits
Following commit e18696786548 ("mwifiex: Prevent memory corruption
handling keys") the mwifiex driver fails to authenticate with certain
networks, specifically networks with 256 bit keys, and repeatedly asks
for the password. The kernel log repeats the following lines (id and
bssid redacted):
mwifiex_pcie :01:00.0: info: trying to associate to '' bssid
mwifiex_pcie :01:00.0: info: associated to bssid
successfully
mwifiex_pcie :01:00.0: crypto keys added
mwifiex_pcie :01:00.0: info: successfully disconnected from
: reason code 3
Tracking down this problem lead to the overflow check introduced by the
aforementioned commit into mwifiex_ret_802_11_key_material_v2(). This
check fails on networks with 256 bit keys due to the current storage
size for AES keys in struct mwifiex_aes_param being only 128 bit.
To fix this issue, increase the storage size for AES keys to 256 bit.
Fixes: e18696786548 ("mwifiex: Prevent memory corruption handling keys")
Signed-off-by: Maximilian Luz
Reported-by: Kaloyan Nikolov
Tested-by: Kaloyan Nikolov
Reviewed-by: Dan Carpenter
Reviewed-by: Brian Norris
Tested-by: Brian Norris
Signed-off-by: Kalle Valo
Link:
https://lore.kernel.org/r/20200825153829.38043-1-luzmaximil...@gmail.com
== Regression Potential ==
Low. While the fix increases the buffer size, it still checks and make sure
data to be copy can fit into the buffer. Also the commit does fix the issue we
saw in the Cert lab.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1897299/+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 1897299] Re: mwifiex stops working after kernel upgrade
** Changed in: hwe-next
Status: New => Fix Released
** Changed in: hwe-next
Assignee: (unassigned) => Jesse Sung (wenchien)
--
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/1897299
Title:
mwifiex stops working after kernel upgrade
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Bug description:
== Impact ==
Marvell WiFi cards supported by the mwifiex driver may fail to connect to
some access points after kernel upgrade.
This is caused by the commit
commit e18696786548244914f36ec3c46ac99c53df99c3
Author: Dan Carpenter
Date: Wed Jul 8 14:58:57 2020 +0300
mwifiex: Prevent memory corruption handling keys
The length of the key comes from the network and it's a 16 bit number. It
needs to be capped to prevent a buffer overflow.
Fixes: 5e6e3a92b9a4 ("wireless: mwifiex: initial commit for Marvell
mwifiex driver")
Signed-off-by: Dan Carpenter
Acked-by: Ganapathi Bhat
Signed-off-by: Kalle Valo
Link: https://lore.kernel.org/r/20200708115857.GA13729@mwanda
The commit added a check to mwifiex_ret_802_11_key_material_v2() to
make sure the key length doesn't larger than the key buffer size
before copying it. The allocated key buffer is 16-byte long. In some
cases the key would be 32-byte long and hence the check fails. One
thing to note is that this commit is not the cause of the problem,
instead it just makes the issue visible.
The commit is included in Ubuntu-4.4.0-190.220, Ubuntu-4.15.0-119.120,
Ubuntu-5.4.0-48.52, and Ubuntu-5.8.0-18.19.
== Fix ==
There's already a fix in the mainline which increase the key buffer size to
32 bytes:
commit 4afc850e2e9e781976fb2c7852ce7bac374af938
Author: Maximilian Luz
Date: Tue Aug 25 17:38:29 2020 +0200
mwifiex: Increase AES key storage size to 256 bits
Following commit e18696786548 ("mwifiex: Prevent memory corruption
handling keys") the mwifiex driver fails to authenticate with certain
networks, specifically networks with 256 bit keys, and repeatedly asks
for the password. The kernel log repeats the following lines (id and
bssid redacted):
mwifiex_pcie :01:00.0: info: trying to associate to '' bssid
mwifiex_pcie :01:00.0: info: associated to bssid
successfully
mwifiex_pcie :01:00.0: crypto keys added
mwifiex_pcie :01:00.0: info: successfully disconnected from
: reason code 3
Tracking down this problem lead to the overflow check introduced by the
aforementioned commit into mwifiex_ret_802_11_key_material_v2(). This
check fails on networks with 256 bit keys due to the current storage
size for AES keys in struct mwifiex_aes_param being only 128 bit.
To fix this issue, increase the storage size for AES keys to 256 bit.
Fixes: e18696786548 ("mwifiex: Prevent memory corruption handling keys")
Signed-off-by: Maximilian Luz
Reported-by: Kaloyan Nikolov
Tested-by: Kaloyan Nikolov
Reviewed-by: Dan Carpenter
Reviewed-by: Brian Norris
Tested-by: Brian Norris
Signed-off-by: Kalle Valo
Link:
https://lore.kernel.org/r/20200825153829.38043-1-luzmaximil...@gmail.com
== Regression Potential ==
Low. While the fix increases the buffer size, it still checks and make sure
data to be copy can fit into the buffer. Also the commit does fix the issue we
saw in the Cert lab.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1897299/+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 1897299] [NEW] mwifiex stops working after kernel upgrade
Public bug reported:
== Impact ==
Marvell WiFi cards supported by the mwifiex driver may fail to connect to some
access points after kernel upgrade.
This is caused by the commit
commit e18696786548244914f36ec3c46ac99c53df99c3
Author: Dan Carpenter
Date: Wed Jul 8 14:58:57 2020 +0300
mwifiex: Prevent memory corruption handling keys
The length of the key comes from the network and it's a 16 bit number. It
needs to be capped to prevent a buffer overflow.
Fixes: 5e6e3a92b9a4 ("wireless: mwifiex: initial commit for Marvell mwifiex
driver")
Signed-off-by: Dan Carpenter
Acked-by: Ganapathi Bhat
Signed-off-by: Kalle Valo
Link: https://lore.kernel.org/r/20200708115857.GA13729@mwanda
The commit added a check to mwifiex_ret_802_11_key_material_v2() to make
sure the key length doesn't larger than the key buffer size before
copying it. The allocated key buffer is 16-byte long. In some cases the
key would be 32-byte long and hence the check fails. One thing to note
is that this commit is not the cause of the problem, instead it just
makes the issue visible.
The commit is included in Ubuntu-4.4.0-190.220, Ubuntu-4.15.0-119.120,
Ubuntu-5.4.0-48.52, and Ubuntu-5.8.0-18.19.
== Fix ==
There's already a fix in the mainline which increase the key buffer size to 32
bytes:
commit 4afc850e2e9e781976fb2c7852ce7bac374af938
Author: Maximilian Luz
Date: Tue Aug 25 17:38:29 2020 +0200
mwifiex: Increase AES key storage size to 256 bits
Following commit e18696786548 ("mwifiex: Prevent memory corruption
handling keys") the mwifiex driver fails to authenticate with certain
networks, specifically networks with 256 bit keys, and repeatedly asks
for the password. The kernel log repeats the following lines (id and
bssid redacted):
mwifiex_pcie :01:00.0: info: trying to associate to '' bssid
mwifiex_pcie :01:00.0: info: associated to bssid
successfully
mwifiex_pcie :01:00.0: crypto keys added
mwifiex_pcie :01:00.0: info: successfully disconnected from
: reason code 3
Tracking down this problem lead to the overflow check introduced by the
aforementioned commit into mwifiex_ret_802_11_key_material_v2(). This
check fails on networks with 256 bit keys due to the current storage
size for AES keys in struct mwifiex_aes_param being only 128 bit.
To fix this issue, increase the storage size for AES keys to 256 bit.
Fixes: e18696786548 ("mwifiex: Prevent memory corruption handling keys")
Signed-off-by: Maximilian Luz
Reported-by: Kaloyan Nikolov
Tested-by: Kaloyan Nikolov
Reviewed-by: Dan Carpenter
Reviewed-by: Brian Norris
Tested-by: Brian Norris
Signed-off-by: Kalle Valo
Link:
https://lore.kernel.org/r/20200825153829.38043-1-luzmaximil...@gmail.com
== Regression Potential ==
Low. While the fix increases the buffer size, it still checks and make sure
data to be copy can fit into the buffer. Also the commit does fix the issue we
saw in the Cert lab.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Jesse Sung (wenchien)
Status: In Progress
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Assignee: Jesse Sung (wenchien)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: Jesse Sung (wenchien)
Status: In Progress
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: Jesse Sung (wenchien)
Status: In Progress
** Affects: linux (Ubuntu Groovy)
Importance: Undecided
Assignee: Jesse Sung (wenchien)
Status: In Progress
** Tags: oem-priority originate-from-1896647 plano
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Assignee: Jesse Sung (wenchien)
Status: In Progress
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Jesse Sung (wenchien)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Jesse Sung (wenchien)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Jesse Sung (wenchien)
** Tags added: oem-priority originate-from-1896647 plano
--
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/1897299
Title:
mw
[Kernel-packages] [Bug 1895803] Re: uvcvideo: add mapping for HEVC payloads
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: hwe-next Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: hwe-next 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/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in HWE Next: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895803/+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 1895803] Re: uvcvideo: add mapping for HEVC payloads
** Tags added: oem-priority originate-from-1877920 presidio -- 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/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895803/+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 1895803] Re: uvcvideo: add mapping for HEVC payloads
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => 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/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895803/+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 1895803] [NEW] uvcvideo: add mapping for HEVC payloads
Public bug reported: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Jesse Sung (wenchien) -- 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/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895803/+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 1885271] Re: kernel oops xr-usb-serial
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => 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/1885271 Title: kernel oops xr-usb-serial Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: # Steps to reproduce # Working case uname -a Linux ubuntu 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt lsusb -t >> xr-usb-serial-devices.txt # Unbind 2 xr-usb-serial devices echo '3-14.1' | tee /sys/bus/usb/drivers/usb/unbind echo '3-14.3' | tee /sys/bus/usb/drivers/usb/unbind dmesg > dmesg.txt # Non working case uname -a Linux ubuntu 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt dmesg > dmesg.txt This regression is almost certainly caused by one of the 2020-03-11 commits: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/log/ubuntu/xr-usb-serial?h=Ubuntu-4.15.0-99.100=5966ed54d467fa77e7dbd7355177a5a6d1db7004 files attached in tar file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885271/+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 1885271] Re: kernel oops xr-usb-serial
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jesse Sung (wenchien) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux (Ubuntu Bionic) 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/1885271 Title: kernel oops xr-usb-serial Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: # Steps to reproduce # Working case uname -a Linux ubuntu 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt lsusb -t >> xr-usb-serial-devices.txt # Unbind 2 xr-usb-serial devices echo '3-14.1' | tee /sys/bus/usb/drivers/usb/unbind echo '3-14.3' | tee /sys/bus/usb/drivers/usb/unbind dmesg > dmesg.txt # Non working case uname -a Linux ubuntu 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt dmesg > dmesg.txt This regression is almost certainly caused by one of the 2020-03-11 commits: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/log/ubuntu/xr-usb-serial?h=Ubuntu-4.15.0-99.100=5966ed54d467fa77e7dbd7355177a5a6d1db7004 files attached in tar file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885271/+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 1881124] Re: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1881124 Title: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210 Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: I2C stops working after kernel upgrade: [ 13.812210] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x [ 13.855837] i2c_designware 80860F41:01: timeout in enabling adapter [ 14.856276] i2c_designware 80860F41:01: controller timed out [ 14.856288] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x This is caused by the commit commit 5568c3f29fbd0ec0d9bb0f805bacc5755180c5cb Author: Andy Shevchenko Date: Fri Dec 4 23:49:18 2015 +0200 Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()" BugLink: https://bugs.launchpad.net/bugs/1878232 commit b5f88dd1d6efc472e35ca1b21a44e662c5422088 upstream. The specific power domain can't be used in a way provided by the commit 01ac170ba29a, i.e. pointer to platform device is a subject to change during unbound / bind cycle. This reverts commit 01ac170ba29a9903ee590e1ef2d8e6b27b49a16c. Fixes: 3df2da968744 (Revert "ACPI / LPSS: introduce a 'proxy' device to power on LPSS for DMA") Signed-off-by: Andy Shevchenko Signed-off-by: Rafael J. Wysocki Signed-off-by: Greg Kroah-Hartman Signed-off-by: Ian May Signed-off-by: Kleber Sacilotto de Souza To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881124/+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 1881124] Re: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210
** Tags added: oem-priority originate-from-1880661 plano ** Changed in: hwe-next Status: New => In Progress ** Changed in: hwe-next Assignee: (unassigned) => Jesse Sung (wenchien) -- 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/1881124 Title: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210 Status in HWE Next: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: I2C stops working after kernel upgrade: [ 13.812210] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x [ 13.855837] i2c_designware 80860F41:01: timeout in enabling adapter [ 14.856276] i2c_designware 80860F41:01: controller timed out [ 14.856288] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x This is caused by the commit commit 5568c3f29fbd0ec0d9bb0f805bacc5755180c5cb Author: Andy Shevchenko Date: Fri Dec 4 23:49:18 2015 +0200 Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()" BugLink: https://bugs.launchpad.net/bugs/1878232 commit b5f88dd1d6efc472e35ca1b21a44e662c5422088 upstream. The specific power domain can't be used in a way provided by the commit 01ac170ba29a, i.e. pointer to platform device is a subject to change during unbound / bind cycle. This reverts commit 01ac170ba29a9903ee590e1ef2d8e6b27b49a16c. Fixes: 3df2da968744 (Revert "ACPI / LPSS: introduce a 'proxy' device to power on LPSS for DMA") Signed-off-by: Andy Shevchenko Signed-off-by: Rafael J. Wysocki Signed-off-by: Greg Kroah-Hartman Signed-off-by: Ian May Signed-off-by: Kleber Sacilotto de Souza To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881124/+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 1881124] [NEW] I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210
Public bug reported: I2C stops working after kernel upgrade: [ 13.812210] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x [ 13.855837] i2c_designware 80860F41:01: timeout in enabling adapter [ 14.856276] i2c_designware 80860F41:01: controller timed out [ 14.856288] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x This is caused by the commit commit 5568c3f29fbd0ec0d9bb0f805bacc5755180c5cb Author: Andy Shevchenko Date: Fri Dec 4 23:49:18 2015 +0200 Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()" BugLink: https://bugs.launchpad.net/bugs/1878232 commit b5f88dd1d6efc472e35ca1b21a44e662c5422088 upstream. The specific power domain can't be used in a way provided by the commit 01ac170ba29a, i.e. pointer to platform device is a subject to change during unbound / bind cycle. This reverts commit 01ac170ba29a9903ee590e1ef2d8e6b27b49a16c. Fixes: 3df2da968744 (Revert "ACPI / LPSS: introduce a 'proxy' device to power on LPSS for DMA") Signed-off-by: Andy Shevchenko Signed-off-by: Rafael J. Wysocki Signed-off-by: Greg Kroah-Hartman Signed-off-by: Ian May Signed-off-by: Kleber Sacilotto de Souza ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: Confirmed ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Jesse Sung (wenchien) -- 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/1881124 Title: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210 Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: I2C stops working after kernel upgrade: [ 13.812210] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x [ 13.855837] i2c_designware 80860F41:01: timeout in enabling adapter [ 14.856276] i2c_designware 80860F41:01: controller timed out [ 14.856288] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x This is caused by the commit commit 5568c3f29fbd0ec0d9bb0f805bacc5755180c5cb Author: Andy Shevchenko Date: Fri Dec 4 23:49:18 2015 +0200 Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()" BugLink: https://bugs.launchpad.net/bugs/1878232 commit b5f88dd1d6efc472e35ca1b21a44e662c5422088 upstream. The specific power domain can't be used in a way provided by the commit 01ac170ba29a, i.e. pointer to platform device is a subject to change during unbound / bind cycle. This reverts commit 01ac170ba29a9903ee590e1ef2d8e6b27b49a16c. Fixes: 3df2da968744 (Revert "ACPI / LPSS: introduce a 'proxy' device to power on LPSS for DMA") Signed-off-by: Andy Shevchenko Signed-off-by: Rafael J. Wysocki Signed-off-by: Greg Kroah-Hartman Signed-off-by: Ian May Signed-off-by: Kleber Sacilotto de Souza To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881124/+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 1065400] Re: Support for loading Broadcom bluetooth firmware
@xnor: Naming rule of the firmware has been changed for some historical reasons... * In 14.04, it is "/lib/firmware/brcm/fw-_.hcd". ( https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/trusty/tree/drivers/bluetooth/btusb.c#n1410 ) * In 16.04, it is "/lib/firmware/brcm/.hcd". ( https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/tree/drivers/bluetooth/btbcm.c#n323 ) * In 18.04, it is either "/lib/firmware/brcm/.hcd" or "/lib/firmware/brcm/--.hcd". ( https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/drivers/bluetooth/btbcm.c#n478 and https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/drivers/bluetooth/btbcm.c#n499 ) Unfortunately because of its incompatible license, we're not able to include the firmware in linux-firmware package. Even in the linux- firmware upstream, there are only a very small amount of such bluebooth firmware files and those should already be included in 18.04 linux- firmware package. ( https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/brcm ) If it used to work on 14.04 but stops working after upgrade, you may already have "/lib/firmware/brcm/fw-_.hcd" in your 14.04 installation (maybe either from a preload Ubuntu system or it was downloaded from somewhere). Filename of the firmware needs to be changed after upgrade so that driver can find it. In this case: $ sudo mv /lib/firmware/brcm/fw-0a5c_21e6.hcd /lib/firmware/brcm/BCM20702A1-0a5c-21e6.hcd If you wiped the whole system before installing 18.04, you have to find the file elsewhere though. If you are not sure what the correct hcd filename is, please check the output of dmesg and you'll see the driver complaining about missing firmware. $ dmesg - For converting the hex formatted firmware to hcd, hex2hcd is included in newer bluez. In 18.04, simply install bluez then you'll have the tool: $ sudo apt-get install bluez Still you can use dmesg to determine the hcd filename to use: $ dmesg You'll have to find the hex firmware in Windows driver provided by laptop vendors, then convert it and place the output to the right place. For example: $ sudo hex2hcd -o /lib/firmware/brcm/BCM20702A1-0a5c-21e6.hcd Hope this helps. -- 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/1065400 Title: Support for loading Broadcom bluetooth firmware Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Saucy: Fix Released Status in linux source package in Trusty: Confirmed Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetooth=132039175324993=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+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 1869694] Re: Support SMO8840 as LIS2DH12
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- 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/1869694 Title: Support SMO8840 as LIS2DH12 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: === Impact === According to ST, HID SMO8840 is for LIS2DH12. In Ubuntu kernel, support for this ID is missing in Bionic, and it's mapped to LNG2DM in D/E/F. === Fix === * e43d110cdc20 - iio: st_sensors: remap SMO8840 to LIS2DH12 This is in mainline kernel 5.6, and also 4.19, 5.4, and 5.5 stable trees. === Risk of Regression === Low. Hans de Goede@redhat, who originally mapped SMO8840 to LNG2DM, confirmed the patch works for his Lenovo Ideapad Miix 320: https://lore.kernel.org/linux-iio/20200224095426.25681-1-jesse.s...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1869694/+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 1869694] Re: Support SMO8840 as LIS2DH12
** Tags removed: verification-needed-bionic verification-needed-eoan ** Tags added: verification-done-bionic verification-done-eoan -- 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/1869694 Title: Support SMO8840 as LIS2DH12 Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: In Progress Bug description: === Impact === According to ST, HID SMO8840 is for LIS2DH12. In Ubuntu kernel, support for this ID is missing in Bionic, and it's mapped to LNG2DM in D/E/F. === Fix === * e43d110cdc20 - iio: st_sensors: remap SMO8840 to LIS2DH12 This is in mainline kernel 5.6, and also 4.19, 5.4, and 5.5 stable trees. === Risk of Regression === Low. Hans de Goede@redhat, who originally mapped SMO8840 to LNG2DM, confirmed the patch works for his Lenovo Ideapad Miix 320: https://lore.kernel.org/linux-iio/20200224095426.25681-1-jesse.s...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1869694/+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 1869694] [NEW] Support SMO8840 as LIS2DH12
Public bug reported: === Impact === According to ST, HID SMO8840 is for LIS2DH12. In Ubuntu kernel, support for this ID is missing in Bionic, and it's mapped to LNG2DM in D/E/F. === Fix === * e43d110cdc20 - iio: st_sensors: remap SMO8840 to LIS2DH12 This is in mainline kernel 5.6, and also 4.19, 5.4, and 5.5 stable trees. === Risk of Regression === Low. Hans de Goede@redhat, who originally mapped SMO8840 to LNG2DM, confirmed the patch works for his Lenovo Ideapad Miix 320: https://lore.kernel.org/linux-iio/20200224095426.25681-1-jesse.s...@canonical.com/T/#u ** Affects: hwe-next Importance: Undecided Assignee: Jesse Sung (wenchien) Status: Fix Released ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Tags: oem-priority originate-from-1844631 presidio ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Tags added: oem-priority originate-from-1844631 presidio ** Changed in: hwe-next Status: New => Fix Released ** Changed in: hwe-next Assignee: (unassigned) => Jesse Sung (wenchien) -- 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/1869694 Title: Support SMO8840 as LIS2DH12 Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: === Impact === According to ST, HID SMO8840 is for LIS2DH12. In Ubuntu kernel, support for this ID is missing in Bionic, and it's mapped to LNG2DM in D/E/F. === Fix === * e43d110cdc20 - iio: st_sensors: remap SMO8840 to LIS2DH12 This is in mainline kernel 5.6, and also 4.19, 5.4, and 5.5 stable trees. === Risk of Regression === Low. Hans de Goede@redhat, who originally mapped SMO8840 to LNG2DM, confirmed the patch works for his Lenovo Ideapad Miix 320: https://lore.kernel.org/linux-iio/20200224095426.25681-1-jesse.s...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1869694/+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 1865495] Re: xenial/linux-deeplens: 4.15.0-1019.19 -proposed tracker
** Summary changed: - xenial/linux-deeplens: -proposed tracker + xenial/linux-deeplens: 4.15.0-1019.19 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) -- 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/1865495 Title: xenial/linux-deeplens: 4.15.0-1019.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865142 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Packaging phase-changed: Tuesday, 03. March 2020 04:53 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1864751 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865495/+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 1864751] Re: xenial/linux-deeplens: 4.15.0-1018.18 -proposed tracker
** Summary changed: - xenial/linux-deeplens: -proposed tracker + xenial/linux-deeplens: 4.15.0-1018.18 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) -- 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/1864751 Title: xenial/linux-deeplens: 4.15.0-1018.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864752 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Packaging phase-changed: Thursday, 27. February 2020 13:07 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1863348 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864751/+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 1863348] Re: xenial/linux-deeplens: 4.15.0-1017.17 -proposed tracker
** Summary changed: - xenial/linux-deeplens: -proposed tracker + xenial/linux-deeplens: 4.15.0-1017.17 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) -- 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/1863348 Title: xenial/linux-deeplens: 4.15.0-1017.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863349 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Packaging phase-changed: Wednesday, 19. February 2020 16:37 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863348/+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 1863337] Re: xenial/linux-oracle: 4.15.0-1034.37~16.04.1 -proposed tracker
** Summary changed: - xenial/linux-oracle: -proposed tracker + xenial/linux-oracle: 4.15.0-1034.37~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1863337 Title: xenial/linux-oracle: 4.15.0-1034.37~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863339 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Packaging phase-changed: Wednesday, 19. February 2020 14:11 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863337/+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 1863310] Re: bionic/linux-snapdragon: 4.15.0-1073.80 -proposed tracker
** Summary changed: - bionic/linux-snapdragon: -proposed tracker + bionic/linux-snapdragon: 4.15.0-1073.80 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1863310 Title: bionic/linux-snapdragon: 4.15.0-1073.80 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863350 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Packaging phase-changed: Wednesday, 19. February 2020 09:21 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1863308 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863310/+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 1861109] Re: xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker
** Summary changed: - xenial/linux-cascade: -proposed tracker + xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) -- 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/1861109 Title: xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1861122 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Packaging phase-changed: Wednesday, 05. February 2020 08:01 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: xenial/linux-cascade/cascade-kernel: bug 1861108 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861109/+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 1854807] Re: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker
** Summary changed: - xenial/linux-oracle: -proposed tracker + xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1854807 Title: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854808 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Packaging phase-changed: Thursday, 05. December 2019 10:11 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854807/+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 1854752] Re: eoan/linux-kvm: 5.3.0-1009.10 -proposed tracker
** Summary changed: - eoan/linux-kvm: -proposed tracker + eoan/linux-kvm: 5.3.0-1009.10 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1854752 Title: eoan/linux-kvm: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854762 packages: main: linux-kvm meta: linux-meta-kvm phase: Packaging phase-changed: Thursday, 05. December 2019 05:15 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854752/+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 1854824] Re: xenial/linux-aws: 4.4.0-1100.111 -proposed tracker
** Summary changed: - xenial/linux-aws: -proposed tracker + xenial/linux-aws: 4.4.0-1100.111 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1854824 Title: xenial/linux-aws: 4.4.0-1100.111 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854835 packages: main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Wednesday, 04. December 2019 10:16 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: xenial/linux-aws/aws-kernel: bug 1854823 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854824/+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 1854768] Re: disco/linux-aws: 5.0.0-1023.26 -proposed tracker
** Summary changed: - disco/linux-aws: -proposed tracker + disco/linux-aws: 5.0.0-1023.26 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Jesse Sung (wenchien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1854768 Title: disco/linux-aws: 5.0.0-1023.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854788 packages: main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Wednesday, 04. December 2019 08:26 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: bionic/linux-aws-5.0: bug 1854767 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854768/+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
