[Kernel-packages] [Bug 1912066] Re: Roccat ISKU Keyboard not working, Kernel 5.8.x
Might be related. https://askubuntu.com/questions/1309849/kernel- updates-dont-install-some-packages-on-ubuntu-20-04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912066 Title: Roccat ISKU Keyboard not working, Kernel 5.8.x Status in linux package in Ubuntu: Incomplete Bug description: see attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-62-generic 5.4.0-62.70 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: comp83-user 2059 F pulseaudio /dev/snd/controlC0: comp83-user 2059 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Jan 16 11:50:45 2021 InstallationDate: Installed on 2020-12-09 (37 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-62-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-62-generic N/A linux-backports-modules-5.4.0-62-generic N/A linux-firmware1.187.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.asset.tag: P14-1324 dmi.board.name: 3397 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: P14-1324 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Elite 8300 SFF dmi.product.sku: B9C43AW#ABA dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912066/+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 1912066] Re: Roccat ISKU Keyboard not working, Kernel 5.8.x
"Can you describe how the 5.8 kernel was installed in this machine?" I've attached a history log for the earliest time that I can see 5.8 showing up. I'm not sure if it came from an apt update or Synaptic. I've also checked Synaptic history which shows 01/09/21 Installed the following packages: linux-image-unsigned-5.8.0-36-generic (5.8.0-36.40~20.04.1). I believe that I tried to remove it when it was first causing the keyboard issue. "Is linux-generic-hwe-20.04 or linux-generic-hwe-20.04-edge installed?" linux-generic-hwe-20.04, no linux-generic-hwe-20.04-edge, no This is Xubuntu 20.04.1 LTS. ** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912066/+attachment/5457288/+files/history.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/1912066 Title: Roccat ISKU Keyboard not working, Kernel 5.8.x Status in linux package in Ubuntu: Incomplete Bug description: see attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-62-generic 5.4.0-62.70 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: comp83-user 2059 F pulseaudio /dev/snd/controlC0: comp83-user 2059 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Jan 16 11:50:45 2021 InstallationDate: Installed on 2020-12-09 (37 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-62-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-62-generic N/A linux-backports-modules-5.4.0-62-generic N/A linux-firmware1.187.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.asset.tag: P14-1324 dmi.board.name: 3397 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: P14-1324 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Elite 8300 SFF dmi.product.sku: B9C43AW#ABA dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912066/+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 1913388] [NEW] clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
Public bug reported: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene-core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s3903164 bugnameltc-191033 severity-medium targetmilestone-inin2104 ** Tags added: architecture-s3903164 bugnameltc-191033 severity-medium targetmilestone-inin2104 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in linux package in Ubuntu: New Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913388/+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 1913388] [NEW] clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
You have been subscribed to a public bug: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene-core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s3903164 bugnameltc-191033 severity-medium targetmilestone-inin2104 -- clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 https://bugs.launchpad.net/bugs/1913388 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913309] Re: Error upgrading Ubuntu armhf from 18.04 to 20.04 on RPI4 - package linux-firmware 1.187.9 failed to install/upgrade
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1913309 Title: Error upgrading Ubuntu armhf from 18.04 to 20.04 on RPI4 - package linux-firmware 1.187.9 failed to install/upgrade Status in linux-firmware package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: New Bug description: Error upgrading Ubuntu armhf from 18.04 to 20.04 on RPI4 - package linux-firmware 1.187.9 failed to install/upgrade: il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 This should be the most relevant part: -- Configurazione di linux-firmware (1.187.9)... update-initramfs: Generating /boot/initrd.img-5.3.0-1008-raspi2 Using DTB: bcm2711-rpi-4-b.dtb Installing /lib/firmware/5.3.0-1008-raspi2/device-tree/bcm2711-rpi-4-b.dtb into /boot/dtbs/5.3.0-1008-raspi2/./bcm2711-rpi-4-b.dtb Installing new bcm2711-rpi-4-b.dtb. Ignoring old or unknown version 5.3.0-1008-raspi2 (latest is 5.4.0-1028-raspi) update-initramfs: Generating /boot/initrd.img-4.15.0-1073-raspi2 Using DTB: bcm2711-rpi-4-b.dtb Couldn't find DTB bcm2711-rpi-4-b.dtb on the following paths: /etc/flash-kernel/dtbs /usr/lib/linux-image-4.15.0-1073-raspi2 /lib/firmware/4.15.0-1073-raspi2/device-tree/ Installing into /boot/dtbs/4.15.0-1073-raspi2/./bcm2711-rpi-4-b.dtb cp: cannot stat '': No such file or directory run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: errore nell'elaborare il pacchetto linux-firmware (--configure): il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 -- ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.9 Uname: Linux 5.10.9-v7l+ armv7l ApportVersion: 2.20.11-0ubuntu27 Architecture: armhf CasperMD5CheckResult: skip Date: Tue Jan 26 14:40:00 2021 Dependencies: ErrorMessage: il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: linux-firmware Title: package linux-firmware 1.187.9 failed to install/upgrade: il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to focal on 2021-01-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1913309/+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 1902004] Re: perf: Add support for Rocket Lake
** Changed in: linux-oem-5.10 (Ubuntu) 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/1902004 Title: perf: Add support for Rocket Lake Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Fix Released Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: perf support for Rocket Lake needs this series https://lore.kernel.org/patchwork/patch/1322440/ which is targeted for 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902004/+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 1902457] Re: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade
Still no sound cards but at least my touchpad works again. Dmesg attached. ** Attachment added: "dmesg-5.11.0-6-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902457/+attachment/5457285/+files/dmesg-5.11.0-6-generic -- 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/1902457 Title: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Groovy, my sound cards no longer work. Alsa-info says "no soundcards detected" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (465 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 8: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: False dmi.bios.date: 10/09/2018 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN32WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:br1.32:efr1.32:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (487 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: linux (not installed) Tags: groovy Uname: Linux 5.10.0-051000rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to groovy on 2020-10-30 (24 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (496 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-31-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 RelatedPackageVersions: linux-restricted-modules-5.8.0-31-generic N/A
[Kernel-packages] [Bug 1912963] Re: [ThinkPad E14 Gen2] Internal microphone is not detected
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc5/amd64/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912963 Title: [ThinkPad E14 Gen2] Internal microphone is not detected Status in linux package in Ubuntu: Incomplete Bug description: The internal microphone is not detected when I use the stock kernel 5.8.0-40-generic: pavucontrol does not show it in the list of input devices, the applications like Zoom or Skype do not see it too. It looks similar to https://askubuntu.com/questions/1277606/internal- microphone-not-working-on-lenovo-thinkpad-e14-gen-2-amd. I tried the workaround mentioned there: switched to kernel 5.9.0-050900-generic from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9/amd64/ - and now the microphone was detected and seemed to work OK (I checked that with pavucontrol and Zoom). Here is the output of 'pacmd list-sources' for the kernels I tried: 5.8.0-40-generic: -- 1 source(s) available. * index: 0 name: driver: flags: DECIBEL_VOLUME LATENCY state: SUSPENDED suspend cause: IDLE priority: 1030 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max rewind: 0 KiB sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 fixed latency: 100,14 ms monitor_of: 0 card: 0 module: 7 properties: device.description = "Monitor of Family 17h (Models 10h-1fh) HD Audio Controller Analog Stereo" device.class = "monitor" alsa.card = "1" alsa.card_name = "HD-Audio Generic" alsa.long_card_name = "HD-Audio Generic at 0xfd3c irq 99" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:05:00.6" sysfs.path = "/devices/pci:00/:00:08.1/:05:00.6/sound/card1" device.bus = "pci" device.vendor.id = "1022" device.vendor.name = "Advanced Micro Devices, Inc. [AMD]" device.product.id = "15e3" device.product.name = "Family 17h (Models 10h-1fh) HD Audio Controller" device.string = "1" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" -- 5.9.0-050900-generic: -- 2 source(s) available. index: 0 name: driver: flags: DECIBEL_VOLUME LATENCY state: SUSPENDED suspend cause: IDLE priority: 1030 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max rewind: 0 KiB sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 fixed latency: 100,14 ms monitor_of: 0 card: 0 module: 7 properties: device.description = "Monitor of Family 17h (Models 10h-1fh) HD Audio Controller Analog Stereo" device.class = "monitor" alsa.card = "1" alsa.card_name = "HD-Audio Generic" alsa.long_card_name = "HD-Audio Generic at 0xfd3c irq 99" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:05:00.6" sysfs.path = "/devices/pci:00/:00:08.1/:05:00.6/sound/card1" device.bus = "pci" device.vendor.id = "1022" device.vendor.name = "Advanced Micro Devices, Inc. [AMD]" device.product.id = "15e3" device.product.name = "Family 17h (Models 10h-1fh) HD Audio Controller" device.string = "1" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" * index: 1 name: driver: flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY state: SUSPENDED suspend cause: IDLE priority: 9039 volume: front-left: 10387 / 16% / -48,00 dB, front-right: 10387 / 16% / -48,00 dB balance 0,00 base volume: 6554 / 10% / -60,00 dB volume steps: 65537 muted: no current latency: 0,00 ms
[Kernel-packages] [Bug 1902457] Re: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade
It includes this patch: https://lore.kernel.org/alsa-devel/20210125115441.10383-1-cezary.rojew...@intel.com/ -- 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/1902457 Title: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Groovy, my sound cards no longer work. Alsa-info says "no soundcards detected" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (465 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 8: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: False dmi.bios.date: 10/09/2018 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN32WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:br1.32:efr1.32:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (487 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: linux (not installed) Tags: groovy Uname: Linux 5.10.0-051000rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to groovy on 2020-10-30 (24 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (496 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-31-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 RelatedPackageVersions: linux-restricted-modules-5.8.0-31-generic N/A linux-backports-modules-5.8.0-31-generic N/A linux-firmware1.190.1 Tags: groovy Uname: Linux
[Kernel-packages] [Bug 1902457] Re: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade
Please give this another try, thanks! https://people.canonical.com/~khfeng/lp1902457+4/ -- 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/1902457 Title: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Groovy, my sound cards no longer work. Alsa-info says "no soundcards detected" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (465 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 8: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: False dmi.bios.date: 10/09/2018 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN32WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:br1.32:efr1.32:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (487 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: linux (not installed) Tags: groovy Uname: Linux 5.10.0-051000rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to groovy on 2020-10-30 (24 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (496 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-31-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 RelatedPackageVersions: linux-restricted-modules-5.8.0-31-generic N/A linux-backports-modules-5.8.0-31-generic N/A linux-firmware1.190.1 Tags: groovy Uname: Linux 5.8.0-31-generic x86_64
[Kernel-packages] [Bug 1913361] Re: Laptop Trackpad Stopped Working
Maybe install `linux-modules-extra` can help? -- 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/1913361 Title: Laptop Trackpad Stopped Working Status in linux package in Ubuntu: Confirmed Bug description: Hi - all of a sudden my laptop trackpad has stopped working. I am also having a difficult time with boot. I am running dual boot with Windows. If i select the normal boot option, it immediately goes to black screen. If i boot into secure mode, i can then have it boot by continuing to boot. Appreciate any help. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geigs 2763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 21:54:25 2021 InstallationDate: Installed on 2021-01-22 (5 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 004: ID 045e:07b2 Microsoft Corp. 2.4GHz Transceiver v8.0 used by mouse Wireless Desktop 900 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305UAB ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=3130c8a3-5f87-4ab5-9490-6a92e2fb5344 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305UAB.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305UAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305UAB.201:bd04/14/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnUX305UAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305UAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305UAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913361/+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 1912940] Re: Bluetooth disabled every time on startup
** Summary changed: - disabled everytime startup + Bluetooth disabled every time on startup ** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1912940 Title: Bluetooth disabled every time on startup Status in bluez package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: [Policy] AutoEnable=true not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Jan 24 19:49:49 2021 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81CG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-051000-generic root=UUID=0281b4fb-589a-46ed-b8ee-896d3505e7bd ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: 6NCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 520-12IKB dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvr6NCN39WW:bd10/10/2019:br1.39:efr1.39:svnLENOVO:pn81CG:pvrMIIX520-12IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct32:cvrMIIX520-12IKB: dmi.product.family: MIIX 520-12IKB dmi.product.name: 81CG dmi.product.sku: LENOVO_MT_81CG_BU_idea_FM_MIIX 520-12IKB dmi.product.version: MIIX 520-12IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 3C:6A:A7:BB:B7:63 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:213889 acl:13940 sco:0 events:310 errors:0 TX bytes:40352 acl:45 sco:0 commands:249 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1912940/+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 1912953] Re: [nvidia] Xorg freezes after suspend
Please follow all the steps in https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1912953 Title: [nvidia] Xorg freezes after suspend Status in nvidia-graphics-drivers-450 package in Ubuntu: Incomplete Bug description: To reproduce this bug, I click the power icon in the activity bar in the top right of the screen and select Power Off/Logout > Suspend. The computer will suspend. I can unsuspend within a few minutes without error. If I close my clamshell and leave the laptop suspended for more than a few minutes, when I re-open the clamshell and attempt to unsuspend, the power indicator is lit, but xorg is unresponsive. The computer remains suspended and I am forced to hard reboot holding the power button. Upon reboot, the computer will display various errors during bootup, often freezing during the process and I am forced to hard reboot. I repeat hard reboots until the computer is able to resume bootup and the operating system comes back online. This occurs daily, with recgularity. It did not happen like this when I ran xfce with an ubuntu server base installation. It did not happen when I first installed Ubuntu 20.04 from a bare metal installation. I expected the computer to suspend and unsuspend without issues. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 450.102.04 Tue Dec 29 06:51:23 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 24 10:19:49 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.102.04, 5.8.0-38-generic, x86_64: installed nvidia, 450.102.04, 5.8.0-40-generic, x86_64: installed tuxedo-keyboard, 2.1.0, 5.8.0-38-generic, x86_64: installed tuxedo-keyboard, 2.1.0, 5.8.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:95e1] NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1ba1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1070 Mobile] [1558:95e1] InstallationDate: Installed on 2020-12-08 (47 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Notebook P95xER ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=5ef82453-315d-49f8-85ac-9f03fb88f2fd ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2018 dmi.bios.release: 7.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.07.15A dmi.board.asset.tag: Tag 12345 dmi.board.name: P95xER dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.8 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.07.15A:bd12/06/2018:br7.15:efr7.8:svnNotebook:pnP95xER:pvrNotApplicable:rvnNotebook:rnP95xER:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95xER dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
[Kernel-packages] [Bug 1913372] Re: Fix the video can't output through WD19TB connected on TGL's Type-C port during cold-boot
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Tags added: oem-priority originate-from-1912449 somerville -- 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/1913372 Title: Fix the video can't output through WD19TB connected on TGL's Type-C port during cold-boot Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: New Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] WD19TB would report the number of lane(2-lane) and it works well on Type-C port of TGL platform. Change the LTTPR mode to non-transparent mode, WD19TB would report the larger number of lane(4-lane). It's over the type-c port's bandwidth. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/series/86267/). Calculate the PBN divider value based on the rate and lane count link parameters that the driver uses for all other computation. [Test Case] 1. Connected the WD19TB with the TGL platform's Type-C port and connected the external monitor on WD19TB with HDMI/Displayport. 2. Cold boot the TGL platform. 3. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] It's more reasonable to calculate the PBN divider based on the source's rate and lane count, not the mst's capability. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1913372/+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 1913372] Re: Fix the video can't output through WD19TB connected on TGL's Type-C port during cold-boot
** Description changed: [Impact] WD19TB would report the number of lane(2-lane) and it works well on Type-C port of TGL platform. Change the LTTPR mode to non-transparent mode, WD19TB would report the larger number of lane(4-lane). It's over the type-c port's bandwidth. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/series/86267/). Calculate the PBN divider value based on the rate and lane count link parameters that the driver uses for all other computation. [Test Case] 1. Connected the WD19TB with the TGL platform's Type-C port and connected the external monitor on WD19TB with HDMI/Displayport. 2. Cold boot the TGL platform. - 4. Check the monitor can be blinked and the video can output to the monitor. + 3. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] It's more reasonable to calculate the PBN divider based on the source's rate and lane count, not the mst's capability. -- 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/1913372 Title: Fix the video can't output through WD19TB connected on TGL's Type-C port during cold-boot Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: New Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] WD19TB would report the number of lane(2-lane) and it works well on Type-C port of TGL platform. Change the LTTPR mode to non-transparent mode, WD19TB would report the larger number of lane(4-lane). It's over the type-c port's bandwidth. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/series/86267/). Calculate the PBN divider value based on the rate and lane count link parameters that the driver uses for all other computation. [Test Case] 1. Connected the WD19TB with the TGL platform's Type-C port and connected the external monitor on WD19TB with HDMI/Displayport. 2. Cold boot the TGL platform. 3. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] It's more reasonable to calculate the PBN divider based on the source's rate and lane count, not the mst's capability. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913372/+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 1913372] [NEW] Fix the video can't output through WD19TB connected on TGL's Type-C port during cold-boot
Public bug reported: [Impact] WD19TB would report the number of lane(2-lane) and it works well on Type-C port of TGL platform. Change the LTTPR mode to non-transparent mode, WD19TB would report the larger number of lane(4-lane). It's over the type-c port's bandwidth. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/series/86267/). Calculate the PBN divider value based on the rate and lane count link parameters that the driver uses for all other computation. [Test Case] 1. Connected the WD19TB with the TGL platform's Type-C port and connected the external monitor on WD19TB with HDMI/Displayport. 2. Cold boot the TGL platform. 4. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] It's more reasonable to calculate the PBN divider based on the source's rate and lane count, not the mst's capability. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Description changed: [Impact] WD19TB would report the number of lane(2-lane) and it works well on Type-C port of TGL platform. - Change the LTTPR mode to non-transparent mode, WD19TB would report the larger number of lane(4-lane). It's over the type-c port's bandwidth. + Change the LTTPR mode to non-transparent mode, WD19TB would report the larger number of lane(4-lane). It's over the type-c port's bandwidth. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/series/86267/). - Calculate the PBN divider value based on the rate and lane count link parameters - that the driver uses for all other computation. + Calculate the PBN divider value based on the rate and lane count link parameters that the driver uses for all other computation. [Test Case] 1. Connected the WD19TB with the TGL platform's Type-C port and connected the external monitor on WD19TB with HDMI/Displayport. 2. Cold boot the TGL platform. 4. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] - It's more reasonable to calculate the PBN divider based on the source's rate and lane count, - not the mst's capability. + It's more reasonable to calculate the PBN divider based on the source's rate and lane count, not the mst's capability. -- 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/1913372 Title: Fix the video can't output through WD19TB connected on TGL's Type-C port during cold-boot Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] WD19TB would report the number of lane(2-lane) and it works well on Type-C port of TGL platform. Change the LTTPR mode to non-transparent mode, WD19TB would report the larger number of lane(4-lane). It's over the type-c port's bandwidth. [Fix] The patch is provided by Imre(https://patchwork.freedesktop.org/series/86267/). Calculate the PBN divider value based on the rate and lane count link parameters that the driver uses for all other computation. [Test Case] 1. Connected the WD19TB with the TGL platform's Type-C port and connected the external monitor on WD19TB with HDMI/Displayport. 2. Cold boot the TGL platform. 4. Check the monitor can be blinked and the video can output to the monitor. [Where problems could occur] It's
[Kernel-packages] [Bug 1913342] Re: zfs.8 man page snapshot listing instructions are confusing
listsnaps is an alias of listsnapshots, but you're right that it's on the pool. Can you file this upstream: https://github.com/openzfs/zfs/issues/new/choose If you want, you could take a stab at submitting a pull request. It's a pretty simple sounding change. The repo is here: https://github.com/openzfs/zfs The man pages are in the "man" subdirectory. For your "Extra Credit" piece, "zfs list -t filesystem,snapshot" shows both filesystems and snapshots for everything. "zfs list -t snapshot dataset" shows snapshots for the specified dataset. But if you combine those together as "zfs list -t filesystem,snapshot dataset", you do not get snapshots. However, "zfs list -t filesystem,snapshot -r dataset" does show the snapshots. Whether that's a bug or not, I can't say. But that's a more detailed explanation of that problem that will be helpful if you file a bug report on that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1913342 Title: zfs.8 man page snapshot listing instructions are confusing Status in zfs-linux package in Ubuntu: New Bug description: The zfs.8 man page describes in 3 places how to include snapshots in "zfs list": 1) Snapshots are displayed if the listsnaps property is on (the default is off). 2) Snapshots are displayed if the listsnaps property is on. The default is off. See zpool(8) for more information on pool properties. 3) For example, specifying -t snapshot displays only snapshots. The first of these has twice now (I'm just learning zfs) sent me down a rabbit hole, looking for a zfs dataset property "listsnaps". There is no such property (of datasets). I'm on version 0.8.3 of zfsutils-linux that has this man page, but when I look at https://zfsonlinux.org/manpages/0.8.6/man8/zfs.8.html it seems that the above is still true in 0.8.6 Suggestion, to help us newbies reduce our learning time to list snapshots: Change both of the first 2 of the above 3 places in zfs.8 to: " "zfs list" displays snapshots only if either the "listsnapshots" property of the underlying zpool is on, or if the "zfs list -t snapshot" option is specified. Extra Credit: Just now it seems to me that the following command does _NOT_ list snapshots, on a dataset that has some snapshots ... so the zfs.8 documentation that the "zfs list -t type" can be a "comma-separated list of types to display" seems incorrect: zfs list -t filesystem,snapshot myzfsdataset Whether this "Extra Credit" discrepancy is a bug in the documentation, or in the zfs command code, or newbie operator error, I'll leave as an exercise to the reader . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.5 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jan 26 13:41:16 2021 SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1913342/+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 1902895] Re: WiFi loses connection on an irregular basis probably due to buffer overflow
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1902895 Title: WiFi loses connection on an irregular basis probably due to buffer overflow Status in linux package in Ubuntu: Expired Bug description: Dell XPS13, Ubuntu 20.10, kernel 5.8. I cannot pinpoint the exact scenario, but it happens most often when trying to build Xorg-master from source via their build.sh script. Setup: WiFi connected, xorg is built in terminal window. Speculatively I would say it say realted to trasferring large number of small files, but I don't have any hard evidence to prove that. To depict it better: A Main terminal (and let it run): $ ./util/modular/build.sh --clone $HOME/build B Second terminal (and let it run): $ ping www.onet.pl #any host should do, just using popular news site as an example C Third terminal (optionally) # dmesg -w At some point of build.sh cloning, the other terminal (B) starts to display this: 64 bytes from sg1.any.onet.pl (213.180.141.140): icmp_seq=151 ttl=58 time=20.2 ms #that's ok ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available It usually happens when A is in the middle of git clone, which just hangs there. Nothing displayed by dmesg. All other network activity stalls (but not fails). Waiting ca. 5 minutes does not help. WiFi icon indicates everything's fine. Restarting WiFi (either using the icon or with rfkill, ifconfig should probably work too) restores connectivity, but breaks all the stalled activity, e.g. scripts, git etc. Increasing /proc/sys/net/core/wmem_max delays the problem and allows one or two clones to complete in the given example. I have observed that on 18.04, 20.04 and 20.10, with the default kernels i.e. 5.4 and 5.8. Scenario in each case is exactly the same. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dladmin1368 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 15:51:00 2020 InstallationDate: Installed on 2020-10-26 (9 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Integrated Webcam HD Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=746d5f05-e21a-42c5-9191-a65c526a3305 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:br2.13:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902895/+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 1905993] Re: Actual kernel don't want to make more than 64 cpus available
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1905993 Title: Actual kernel don't want to make more than 64 cpus available Status in linux package in Ubuntu: Expired Bug description: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Tags: bionic uec-images Uname: Linux 4.19.160-0419160-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 27 21:50 seq crw-rw 1 root audio 116, 33 Nov 27 21:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-63-generic root=UUID=17d2bcf1-3687-426a-8219-978743746d51 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.0.0-63.69-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-63-generic N/A linux-backports-modules-5.0.0-63-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.0.0-63-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr20.1.1:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 20.1.1 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+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 1913361] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913361 Title: Laptop Trackpad Stopped Working Status in linux package in Ubuntu: Confirmed Bug description: Hi - all of a sudden my laptop trackpad has stopped working. I am also having a difficult time with boot. I am running dual boot with Windows. If i select the normal boot option, it immediately goes to black screen. If i boot into secure mode, i can then have it boot by continuing to boot. Appreciate any help. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geigs 2763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 21:54:25 2021 InstallationDate: Installed on 2021-01-22 (5 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 004: ID 045e:07b2 Microsoft Corp. 2.4GHz Transceiver v8.0 used by mouse Wireless Desktop 900 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305UAB ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=3130c8a3-5f87-4ab5-9490-6a92e2fb5344 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305UAB.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305UAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305UAB.201:bd04/14/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnUX305UAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305UAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305UAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913361/+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 1912066] Re: Roccat ISKU Keyboard not working, Kernel 5.8.x
Hi! Thanks for all the information. Can you describe how the 5.8 kernel was installed in this machine? Is linux-generic-hwe-20.04 or linux-generic-hwe-20.04-edge installed? Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912066 Title: Roccat ISKU Keyboard not working, Kernel 5.8.x Status in linux package in Ubuntu: Incomplete Bug description: see attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-62-generic 5.4.0-62.70 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: comp83-user 2059 F pulseaudio /dev/snd/controlC0: comp83-user 2059 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Jan 16 11:50:45 2021 InstallationDate: Installed on 2020-12-09 (37 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-62-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-62-generic N/A linux-backports-modules-5.4.0-62-generic N/A linux-firmware1.187.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.asset.tag: P14-1324 dmi.board.name: 3397 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: P14-1324 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Elite 8300 SFF dmi.product.sku: B9C43AW#ABA dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912066/+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 1913361] [NEW] Laptop Trackpad Stopped Working
Public bug reported: Hi - all of a sudden my laptop trackpad has stopped working. I am also having a difficult time with boot. I am running dual boot with Windows. If i select the normal boot option, it immediately goes to black screen. If i boot into secure mode, i can then have it boot by continuing to boot. Appreciate any help. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geigs 2763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 21:54:25 2021 InstallationDate: Installed on 2021-01-22 (5 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 004: ID 045e:07b2 Microsoft Corp. 2.4GHz Transceiver v8.0 used by mouse Wireless Desktop 900 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305UAB ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=3130c8a3-5f87-4ab5-9490-6a92e2fb5344 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305UAB.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305UAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305UAB.201:bd04/14/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnUX305UAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305UAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305UAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1913361 Title: Laptop Trackpad Stopped Working Status in linux package in Ubuntu: New Bug description: Hi - all of a sudden my laptop trackpad has stopped working. I am also having a difficult time with boot. I am running dual boot with Windows. If i select the normal boot option, it immediately goes to black screen. If i boot into secure mode, i can then have it boot by continuing to boot. Appreciate any help. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geigs 2763 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 21:54:25 2021 InstallationDate: Installed on 2021-01-22 (5 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 004: ID 045e:07b2 Microsoft Corp. 2.4GHz Transceiver v8.0 used by mouse Wireless Desktop 900 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305UAB ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=3130c8a3-5f87-4ab5-9490-6a92e2fb5344 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305UAB.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305UAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0
[Kernel-packages] [Bug 1912898] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912898 Title: [i915] With kernel 5.8, video crashes, system freezes. But 5.4 works. Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.8 package in Ubuntu: New Bug description: 1) Chromebox 2955U trying to run Ubuntu 20.04 with updates. Has been running Ubuntu for many years. 2) Video seems to crash when ANY program, menu item or terminal is started after reboot. Flashing screen fields, boxes, menus. Cursor freezes or stutters. 3) 18.02 ran and runs fine in other partitions. 4) Latest Debian runs fine in other partiton. 5) Ubuntu 20.04 runs fine when running directly from USB flashdrive. This is really wierd. 6) Occurs immediately after a fresh installation of 20.04 in any partition. Verified sha256sums. 7) Can make system usable with nomodeset in grub linux line but runs very slow. 8) Tried "sudo apt-get install xserver-xorg-video-intel". ... Already running latest. 9) Memtest86 ran 2 full iterations, no errors. 10) Seems like I verified an older kernel worked fine, but an "autoremove" removed it/them. 11) I've been fighting this for a few months now. Thank you for any support you can give... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 23 08:41:43 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Google, Inc. Haswell-ULT Integrated Graphics Controller [1ae0:c000] InstallationDate: Installed on 2020-10-03 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3393 IMC Networks Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Panther ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=3124be5d-3014-4ee1-ac5b-8c48babfde15 ro quiet splash nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2014 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.bios.version: 4.0-7565-gc6e3a3a-dirty dmi.board.name: Panther dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.0-7565-gc6e3a3a-dirty:bd12/10/2014:br4.0:efr0.0:svnGoogle:pnPanther:pvr1.0:rvnGoogle:rnPanther:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.name: Panther dmi.product.version: 1.0 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912898/+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 1912898] Re: [i915] With kernel 5.8, video crashes, system freezes. But 5.4 works.
** Summary changed: - [i915] Last few kernel updates, video crashes, system freezes + [i915] With kernel 5.8, video crashes, system freezes. But 5.4 works. ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Also affects: linux-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags added: regression-update -- 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/1912898 Title: [i915] With kernel 5.8, video crashes, system freezes. But 5.4 works. Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.8 package in Ubuntu: New Bug description: 1) Chromebox 2955U trying to run Ubuntu 20.04 with updates. Has been running Ubuntu for many years. 2) Video seems to crash when ANY program, menu item or terminal is started after reboot. Flashing screen fields, boxes, menus. Cursor freezes or stutters. 3) 18.02 ran and runs fine in other partitions. 4) Latest Debian runs fine in other partiton. 5) Ubuntu 20.04 runs fine when running directly from USB flashdrive. This is really wierd. 6) Occurs immediately after a fresh installation of 20.04 in any partition. Verified sha256sums. 7) Can make system usable with nomodeset in grub linux line but runs very slow. 8) Tried "sudo apt-get install xserver-xorg-video-intel". ... Already running latest. 9) Memtest86 ran 2 full iterations, no errors. 10) Seems like I verified an older kernel worked fine, but an "autoremove" removed it/them. 11) I've been fighting this for a few months now. Thank you for any support you can give... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 23 08:41:43 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Google, Inc. Haswell-ULT Integrated Graphics Controller [1ae0:c000] InstallationDate: Installed on 2020-10-03 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3393 IMC Networks Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Panther ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=3124be5d-3014-4ee1-ac5b-8c48babfde15 ro quiet splash nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2014 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.bios.version: 4.0-7565-gc6e3a3a-dirty dmi.board.name: Panther dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.0-7565-gc6e3a3a-dirty:bd12/10/2014:br4.0:efr0.0:svnGoogle:pnPanther:pvr1.0:rvnGoogle:rnPanther:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.name: Panther dmi.product.version: 1.0 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912898/+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 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
Then the fix in the kernel will help. Currently only linux-oem-5.6 has the fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Confirmed Status in Gentoo Linux: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+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 1913350] Re: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly
** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => High -- 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/1913350 Title: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly. Sometimes after 1h of using my laptop, and sometimes after resuming from sleep. It can't work again until I reboot my laptop. The most relevant error message is: sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Failed to wake NIC for hcmd sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5 I'm using Ubuntu 20.04 that was upgraded from 18.04 and earlier 16.04. I've searched for similar bugs, but it looks like my error message and card model is a bit different. The workaround script from bug 1673344 works to fix the wifi without rebooting. The card works fine in Windows 10 so it's not a hardware issue. This is not a stock card from HP EliteBook 8470w, I've replaced it to gain Wifi 802.11ac transfer speeds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: azrael 2915 F pulseaudio /dev/snd/controlC1: azrael 2915 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 23:23:06 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-08 (1632 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8470w ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/rootvg-rootlv ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-01-10 (16 days ago) dmi.bios.date: 04/11/2019 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.74 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.38 dmi.chassis.asset.tag: CNU2499X8F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.74:bd04/11/2019:svnHewlett-Packard:pnHPEliteBook8470w:pvrA1029D1102:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8470w dmi.product.sku: LY541EA#AKD dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1913350/+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 1912789] Re: Add support for selective build of special drivers
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1912789 Title: Add support for selective build of special drivers Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Bug description: [SRU Justification] = Impact = We want to add some driver code which exists in the primary kernel source but will not get included unless specifically asked for. As long as there are no drivers using this, there is no user-visible change. = Impact = This will be done by adding a new config option which gets turned on via build setup rules. The default will be off. = Testcase = As long as there are no consumers changes can only be seen by inspecting the build logs (if even that). = Regression Potential = This prepares for future consumers. At this stage either the build will fail completely or pass and in that case the produced kernel binaries are the same as they were before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912789/+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 1912066] Re: Roccat ISKU Keyboard not working, Kernel 5.8.x
"Is package "linux-modules-extra" installed?" That fixed it. linux-modules-extra-5.4.0-62-generic was installed, linux-modules-extra-5.8.0-40-generic was not installed. I usually just run the Software Updater. However, after installing linux-modules- extra-5.8.0-40-generic, everything appears to be working. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912066 Title: Roccat ISKU Keyboard not working, Kernel 5.8.x Status in linux package in Ubuntu: Incomplete Bug description: see attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-62-generic 5.4.0-62.70 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: comp83-user 2059 F pulseaudio /dev/snd/controlC0: comp83-user 2059 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Jan 16 11:50:45 2021 InstallationDate: Installed on 2020-12-09 (37 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-62-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-62-generic N/A linux-backports-modules-5.4.0-62-generic N/A linux-firmware1.187.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.asset.tag: P14-1324 dmi.board.name: 3397 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: P14-1324 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Elite 8300 SFF dmi.product.sku: B9C43AW#ABA dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912066/+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 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Introduce the new NVIDIA 460-server series and update the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460-server == * Initial release: - Added support for the following GPUs: NVIDIA A40 NVIDIA RTX A6000 - Added support for CUDA 11.2. == 460 == * New upstream release: - Added support for the following GPUs: GeForce RTX 3080 Laptop GPU GeForce RTX 3070 Laptop GPU GeForce RTX 3060 Laptop GPU GeForce GT 1010 - Updated the NVIDIA driver to restore functionality of some features, including runtime power management, hotplugging audio-capable display devices, and S0ix-based system suspend, with recent kernels such as Linux 5.10. - Fixed a bug that caused bindless texture samplers to be incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS limit. - Fixed a bug that could cause the GPU to hang when attempting to perform link training on an HDMI 2.1 Fixed Rate Link (FRL) display, while the display is powered off. - Fixed a bug that could intermittently cause NvFBC applications to fail with the error message "Unable to send exported fds". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+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 1913342] Re: zfs.8 man page snapshot listing instructions are confusing
** Package changed: ubuntu => zfs-linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1913342 Title: zfs.8 man page snapshot listing instructions are confusing Status in zfs-linux package in Ubuntu: New Bug description: The zfs.8 man page describes in 3 places how to include snapshots in "zfs list": 1) Snapshots are displayed if the listsnaps property is on (the default is off). 2) Snapshots are displayed if the listsnaps property is on. The default is off. See zpool(8) for more information on pool properties. 3) For example, specifying -t snapshot displays only snapshots. The first of these has twice now (I'm just learning zfs) sent me down a rabbit hole, looking for a zfs dataset property "listsnaps". There is no such property (of datasets). I'm on version 0.8.3 of zfsutils-linux that has this man page, but when I look at https://zfsonlinux.org/manpages/0.8.6/man8/zfs.8.html it seems that the above is still true in 0.8.6 Suggestion, to help us newbies reduce our learning time to list snapshots: Change both of the first 2 of the above 3 places in zfs.8 to: " "zfs list" displays snapshots only if either the "listsnapshots" property of the underlying zpool is on, or if the "zfs list -t snapshot" option is specified. Extra Credit: Just now it seems to me that the following command does _NOT_ list snapshots, on a dataset that has some snapshots ... so the zfs.8 documentation that the "zfs list -t type" can be a "comma-separated list of types to display" seems incorrect: zfs list -t filesystem,snapshot myzfsdataset Whether this "Extra Credit" discrepancy is a bug in the documentation, or in the zfs command code, or newbie operator error, I'll leave as an exercise to the reader . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.5 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jan 26 13:41:16 2021 SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1913342/+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 1913342] [NEW] zfs.8 man page snapshot listing instructions are confusing
You have been subscribed to a public bug: The zfs.8 man page describes in 3 places how to include snapshots in "zfs list": 1) Snapshots are displayed if the listsnaps property is on (the default is off). 2) Snapshots are displayed if the listsnaps property is on. The default is off. See zpool(8) for more information on pool properties. 3) For example, specifying -t snapshot displays only snapshots. The first of these has twice now (I'm just learning zfs) sent me down a rabbit hole, looking for a zfs dataset property "listsnaps". There is no such property (of datasets). I'm on version 0.8.3 of zfsutils-linux that has this man page, but when I look at https://zfsonlinux.org/manpages/0.8.6/man8/zfs.8.html it seems that the above is still true in 0.8.6 Suggestion, to help us newbies reduce our learning time to list snapshots: Change both of the first 2 of the above 3 places in zfs.8 to: " "zfs list" displays snapshots only if either the "listsnapshots" property of the underlying zpool is on, or if the "zfs list -t snapshot" option is specified. Extra Credit: Just now it seems to me that the following command does _NOT_ list snapshots, on a dataset that has some snapshots ... so the zfs.8 documentation that the "zfs list -t type" can be a "comma-separated list of types to display" seems incorrect: zfs list -t filesystem,snapshot myzfsdataset Whether this "Extra Credit" discrepancy is a bug in the documentation, or in the zfs command code, or newbie operator error, I'll leave as an exercise to the reader . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.5 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jan 26 13:41:16 2021 SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- zfs.8 man page snapshot listing instructions are confusing https://bugs.launchpad.net/bugs/1913342 You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913350] Re: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly
This is a likely upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=207557 ** Bug watch added: Linux Kernel Bug Tracker #207557 https://bugzilla.kernel.org/show_bug.cgi?id=207557 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=207557 Importance: Unknown Status: Unknown -- 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/1913350 Title: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly. Sometimes after 1h of using my laptop, and sometimes after resuming from sleep. It can't work again until I reboot my laptop. The most relevant error message is: sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Failed to wake NIC for hcmd sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5 I'm using Ubuntu 20.04 that was upgraded from 18.04 and earlier 16.04. I've searched for similar bugs, but it looks like my error message and card model is a bit different. The workaround script from bug 1673344 works to fix the wifi without rebooting. The card works fine in Windows 10 so it's not a hardware issue. This is not a stock card from HP EliteBook 8470w, I've replaced it to gain Wifi 802.11ac transfer speeds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: azrael 2915 F pulseaudio /dev/snd/controlC1: azrael 2915 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 23:23:06 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-08 (1632 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8470w ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/rootvg-rootlv ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-01-10 (16 days ago) dmi.bios.date: 04/11/2019 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.74 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.38 dmi.chassis.asset.tag: CNU2499X8F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.74:bd04/11/2019:svnHewlett-Packard:pnHPEliteBook8470w:pvrA1029D1102:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8470w dmi.product.sku: LY541EA#AKD dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1913350/+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 1913350] Re: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly
** Attachment added: "journalctl-24012021.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913350/+attachment/5457146/+files/journalctl-24012021.txt ** Description changed: - Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly. + Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly. Sometimes after 1h of using my laptop, and sometimes after resuming from sleep. It can't work again until I reboot my laptop. The most relevant error message is: sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Failed to wake NIC for hcmd sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5 I'm using Ubuntu 20.04 that was upgraded from 18.04 and earlier 16.04. I've searched for similar bugs, but it looks like my error message and card model is a bit different. - The workaround script from bug 1673344 works to fix the wifi without - rebooting. + The workaround script from bug 1673344 works to fix the wifi without rebooting. + The card works fine in Windows 10 so it's not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: azrael 2915 F pulseaudio - /dev/snd/controlC1: azrael 2915 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: azrael 2915 F pulseaudio + /dev/snd/controlC1: azrael 2915 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 23:23:06 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-08 (1632 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8470w ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pl_PL.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pl_PL.UTF-8 + SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/rootvg-rootlv ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-64-generic N/A - linux-backports-modules-5.4.0-64-generic N/A - linux-firmware1.187.8 + linux-restricted-modules-5.4.0-64-generic N/A + linux-backports-modules-5.4.0-64-generic N/A + linux-firmware1.187.8 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-01-10 (16 days ago) dmi.bios.date: 04/11/2019 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.74 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.38 dmi.chassis.asset.tag: CNU2499X8F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.74:bd04/11/2019:svnHewlett-Packard:pnHPEliteBook8470w:pvrA1029D1102:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8470w dmi.product.sku: LY541EA#AKD dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard ** Description changed: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly. Sometimes after 1h of using my laptop, and sometimes after resuming from sleep. It can't work again until I reboot my laptop. The most relevant error message is: sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Failed to wake NIC for hcmd sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5 I'm using Ubuntu 20.04 that was upgraded from 18.04 and earlier 16.04. I've searched for similar bugs, but it looks like my error message and card model is a bit different. The workaround script from bug 1673344 works to fix the wifi without rebooting. The card works fine in Windows 10 so it's not a hardware issue. + This is not a stock card from HP EliteBook 8470w, I've replaced it to gain Wifi 802.11ac transfer speeds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: azrael 2915 F pulseaudio /dev/snd/controlC1: azrael 2915 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 23:23:06 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-08 (1632 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial
[Kernel-packages] [Bug 1913350] Re: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly
** Attachment added: "journalctl-25012021.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913350/+attachment/5457145/+files/journalctl-25012021.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913350 Title: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly. Sometimes after 1h of using my laptop, and sometimes after resuming from sleep. It can't work again until I reboot my laptop. The most relevant error message is: sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Failed to wake NIC for hcmd sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5 I'm using Ubuntu 20.04 that was upgraded from 18.04 and earlier 16.04. I've searched for similar bugs, but it looks like my error message and card model is a bit different. The workaround script from bug 1673344 works to fix the wifi without rebooting. The card works fine in Windows 10 so it's not a hardware issue. This is not a stock card from HP EliteBook 8470w, I've replaced it to gain Wifi 802.11ac transfer speeds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: azrael 2915 F pulseaudio /dev/snd/controlC1: azrael 2915 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 23:23:06 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-08 (1632 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8470w ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/rootvg-rootlv ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-01-10 (16 days ago) dmi.bios.date: 04/11/2019 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.74 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.38 dmi.chassis.asset.tag: CNU2499X8F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.74:bd04/11/2019:svnHewlett-Packard:pnHPEliteBook8470w:pvrA1029D1102:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8470w dmi.product.sku: LY541EA#AKD dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1913350/+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 1913350] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913350 Title: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly Status in linux package in Ubuntu: Confirmed Bug description: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly. Sometimes after 1h of using my laptop, and sometimes after resuming from sleep. It can't work again until I reboot my laptop. The most relevant error message is: sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Failed to wake NIC for hcmd sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5 I'm using Ubuntu 20.04 that was upgraded from 18.04 and earlier 16.04. I've searched for similar bugs, but it looks like my error message and card model is a bit different. The workaround script from bug 1673344 works to fix the wifi without rebooting. The card works fine in Windows 10 so it's not a hardware issue. This is not a stock card from HP EliteBook 8470w, I've replaced it to gain Wifi 802.11ac transfer speeds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: azrael 2915 F pulseaudio /dev/snd/controlC1: azrael 2915 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 23:23:06 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-08 (1632 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8470w ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/rootvg-rootlv ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-01-10 (16 days ago) dmi.bios.date: 04/11/2019 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.74 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.38 dmi.chassis.asset.tag: CNU2499X8F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.74:bd04/11/2019:svnHewlett-Packard:pnHPEliteBook8470w:pvrA1029D1102:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8470w dmi.product.sku: LY541EA#AKD dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913350/+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 1913350] [NEW] Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly
Public bug reported: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly. Sometimes after 1h of using my laptop, and sometimes after resuming from sleep. It can't work again until I reboot my laptop. The most relevant error message is: sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Failed to wake NIC for hcmd sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5 I'm using Ubuntu 20.04 that was upgraded from 18.04 and earlier 16.04. I've searched for similar bugs, but it looks like my error message and card model is a bit different. The workaround script from bug 1673344 works to fix the wifi without rebooting. The card works fine in Windows 10 so it's not a hardware issue. This is not a stock card from HP EliteBook 8470w, I've replaced it to gain Wifi 802.11ac transfer speeds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: azrael 2915 F pulseaudio /dev/snd/controlC1: azrael 2915 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 23:23:06 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-08 (1632 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8470w ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/rootvg-rootlv ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-01-10 (16 days ago) dmi.bios.date: 04/11/2019 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.74 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.38 dmi.chassis.asset.tag: CNU2499X8F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.74:bd04/11/2019:svnHewlett-Packard:pnHPEliteBook8470w:pvrA1029D1102:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8470w dmi.product.sku: LY541EA#AKD dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913350 Title: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly Status in linux package in Ubuntu: Confirmed Bug description: Intel Wireless-AC 7260 (rev bb) wifi card crashes randomly. Sometimes after 1h of using my laptop, and sometimes after resuming from sleep. It can't work again until I reboot my laptop. The most relevant error message is: sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Failed to wake NIC for hcmd sty 25 14:42:13 leetbook kernel: iwlwifi :25:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5 I'm using Ubuntu 20.04 that was upgraded from 18.04 and earlier 16.04. I've searched for similar bugs, but it looks like my error message and card model is a bit different. The workaround script from bug 1673344 works to fix the wifi without rebooting. The card works fine in Windows 10 so it's not a hardware issue. This is not a stock card from HP EliteBook 8470w, I've replaced it to gain Wifi 802.11ac transfer speeds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: azrael 2915 F pulseaudio /dev/snd/controlC1: azrael 2915 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 23:23:06 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-08 (1632 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8470w ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/rootvg-rootlv ro quiet splash vt.handoff=7
[Kernel-packages] [Bug 1912188] Re: Load growing continously
I get the same with ZFS 2.0.1, dmesg output attached, if it helps. ** Attachment added: "dmesg-zfs.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912188/+attachment/5457148/+files/dmesg-zfs.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912188 Title: Load growing continously Status in zfs-ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Recently load started growing with no end. After a while random processes become zombies. 11:32:22 up 26 min, 1 user, load average: 196.16, 186.30, 138.60 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-generic 5.8.0.36.40+21.04.38 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tompos 2361 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 18 11:30:11 2021 InstallationDate: Installed on 2020-12-31 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP EliteBook x360 1030 G3 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic root=UUID=086c6507-b389-4208-a8bc-d0b99071b5cd ro rootflags=subvol=@ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.194 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-01-02 (15 days ago) dmi.bios.date: 10/22/2020 dmi.bios.release: 14.1 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.14.01 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.4E.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 20.78 dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.14.01:bd10/22/2020:br14.1:efr20.78:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.4E.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 5DT80EC#BH4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/zfs-ubuntu/+bug/1912188/+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 1673344] Re: Intel Wireless-AC 7260 [8086:08b1] Subsystem [8086:4070] Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely even when I try to restart networ
Similar bug: bug 1913350 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1673344 Title: Intel Wireless-AC 7260 [8086:08b1] Subsystem [8086:4070] Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely even when I try to restart network manager Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: My wireless connection completely disappears and isn't recognized along with my NIC card and doesn't come back until I reboot even if I restart network manager. I've attached the required files showing what my wifi information looks like connected and what it looks like when the problem occurs hopefully a fix or workaround can be found this happens several times a day. Steps: 1) I boot up type in sudo iwconfig wlp3s0 power off (turn off power management) 2) $ iwconfig enp4s0f2 no wireless extensions. lono wireless extensions. wlp3s0IEEE 802.11 ESSID:"2.4ghz" Mode:Managed Frequency:2.437 GHz Access Point: E0:3F:29:93:3F:20 Bit Rate=144.4 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=60/70 Signal level=-50 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:55 Missed beacon:0 3) I loose wifi using 5ghz or 2.4ghz after a certain amount of time 4) sudo rmmod iwlmvm iwlwifi && sudo modprobe iwlmvm iwlwifi 5) sudo systemctl restart network-manager.service I do a **iwconfig** and **I'm missing wlp3s0IEEE 802.11 ESSID:"2.4ghz"** $ iwconfig enp4s0f2 no wireless extensions. lono wireless extensions. I have to reboot to get my wifi back and for ubunutu to recognize my wifi card back how can I prevent this. $ uname -a Linux sys76 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ dmesg | grep iwlwifi 876.891600] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 876.891602] iwlwifi :03:00.0: Scan failed! ret -5 [ 877.909370] iwlwifi :03:00.0: Failed to wake NIC for hcmd [ 877.909397] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 877.909409] iwlwifi :03:00.0: Scan failed! ret -5 [ 878.928277] iwlwifi :03:00.0: Failed to wake NIC for hcmd [ 878.928364] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 878.928366] iwlwifi :03:00.0: Scan failed! ret -5 [ 879.947120] iwlwifi :03:00.0: Failed to wake NIC for hcmd [ 879.947170] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 879.947172] iwlwifi :03:00.0: Scan failed! ret -5 $ sudo lshw -C network [sudo] password for rt: *-network description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 73 serial: 0c:8b:fd:2e:64:8e width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.8.0-41-generic firmware=17.352738.0 ip=192.168.1.8 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:31 memory:f7d0-f7d01fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0.2 bus info: pci@:04:00.2 logical name: enp4s0f2 version: 0a serial: 00:90:f5:f9:d4:f8 size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8411-1_0.0.3 06/18/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:27 ioport:e000(size=256) memory:f0004000-f0004fff memory:f000-f0003fff $ ethtool -i wlp3s0 | grep driver driver: iwlwifi $ dmesg |
[Kernel-packages] [Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 Same problem for a BCM4360 card. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 Status in bcmwl package in Ubuntu: Confirmed Bug description: Recently kernel was updated on Focal from 5.4 to 5.8. From that moment on WiFi doesn't work anymore. After a try rebuild (reconfigure) the result is: --- # dpkg-reconfigure bcmwl-kernel-source Removing all DKMS Modules Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-59-generic 5.8.0-34-generic Building for architecture x86_64 Building initial module for 5.4.0-59-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-59-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 5.8.0-34-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. --- As could be seen, the build for 5.4 completes successfully (and works on same kernel), but for 5.8 fails. Seems something is going wrong with missing function declaration - function "ioremap_nocache", as could be seen in attached make.log. I'm guessing, driver code may need be updated according to the new kernel headers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 17:13:05 2021 InstallationDate: Installed on 2020-06-22 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+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 1866149] Re: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl
This bug was fixed in the package linux-kvm - 5.8.0-1016.18 --- linux-kvm (5.8.0-1016.18) groovy; urgency=medium * groovy/linux-kvm: 5.8.0-1016.18 -proposed tracker (LP: #1911344) * CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl (LP: #1866149) - [Config]: set CONFIG_BASE_FULL * Missing module nfsv4 in linux-kvm (LP: #1907266) - [Config] kvm: Enable NFSv4 [ Ubuntu: 5.8.0-39.44 ] * groovy/linux: 5.8.0-39.44 -proposed tracker (LP: #1911350) * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME [ Ubuntu: 5.8.0-38.43 ] * groovy/linux: 5.8.0-38.43 -proposed tracker (LP: #1911143) * CVE-2020-28374 - SAUCE: target: fix XCOPY NAA identifier lookup * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.8.0-36.40 ] * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly [ Ubuntu: 5.8.0-35.39 ] * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-1052 // CVE-2021-1053 - [Packaging] NVIDIA -- Add the NVIDIA 460 driver -- Kelsey Skunberg Thu, 14 Jan 2021 16:31:26 -0700 ** Changed in: linux-kvm (Ubuntu Xenial) Status: Fix Committed => 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/1866149 Title: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Incomplete Status in linux source package in Xenial: Invalid Status in linux-kvm source package in Xenial: Fix Released Status in linux source package in Bionic: Invalid Status in linux-kvm source package in Bionic: Fix Released Status in linux source package in Focal: Invalid Status in linux-kvm source package in Focal: Fix Released Status in linux source package in Groovy: Invalid Status in linux-kvm source package in Groovy: Fix Released Bug description: [Impact] systemd-systemctl will fail to set kernel.pid_max, leading to a degraded boot. [Fix] Set CONFIG_BASE_FULL=y, CONFIG_BASE_SMALL=0. [Test case] Write 419304 to /proc/sys/kernel/pid_max. [Potential regression] Boot time may be affected. I'm not completely sure which package to log this against. I'm running the kvm focal minimal cloud image from 20200302. I noticed on boot that there was an error complaining that systemd-systemctl couldn't update pid_max to the value it wanted: systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf: # Bump the numeric PID range to its maximum of 2^22 (from the in-kernel default # of 2^16), to make PID collisions less likely. kernel.pid_max = 4194304 However, the linux-image-kvm kernel is compiled with CONFIG_BASE_SMALL=1 and this triggers the following code in include/linux/threads.h #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \ (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT)) which means that if CONFIG_BASE_SMALL is set we get a maximum limit of PAGE_SIZE * 8, which on x86 would be 32768. As a workaround I can override it with a file in /etc/sysctl.d/ but this shouldn't be needed. I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud images, they really aren't small machines in the scheme of things! Cheers David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866149/+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 1866149] Re: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl
This bug was fixed in the package linux-kvm - 4.4.0-1087.96
---
linux-kvm (4.4.0-1087.96) xenial; urgency=medium
* xenial/linux-kvm: 4.4.0-1087.96 -proposed tracker (LP: #1911257)
* CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd
default sysctl (LP: #1866149)
- [Config]: set CONFIG_BASE_FULL
[ Ubuntu: 4.4.0-201.233 ]
* xenial/linux: 4.4.0-201.233 -proposed tracker (LP: #1911265)
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- powerpc/rtas: Restrict RTAS requests from userspace
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Xenial update: v4.4.247 upstream stable release (LP: #1906703)
- btrfs: tree-checker: Enhance chunk checker to validate chunk profile
- btrfs: inode: Verify inode mode to avoid NULL pointer dereference
- HID: cypress: Support Varmilo Keyboards' media hotkeys
- Input: i8042 - allow insmod to succeed on devices without an i8042
controller
- HID: hid-sensor-hub: Fix issue with devices with no report ID
- x86/xen: don't unbind uninitialized lock_kicker_irq
- proc: don't allow async path resolution of /proc/self components
- dmaengine: pl330: _prep_dma_memcpy: Fix wrong burst size
- scsi: libiscsi: Fix NOP race condition
- scsi: target: iscsi: Fix cmd abort fabric stop race
- scsi: ufs: Fix race between shutdown and runtime resume flow
- bnxt_en: fix error return code in bnxt_init_board()
- video: hyperv_fb: Fix the cache type when mapping the VRAM
- bnxt_en: Release PCI regions when DMA mask setup fails during probe.
- IB/mthca: fix return value of error branch in mthca_init_cq()
- nfc: s3fwrn5: use signed integer for parsing GPIO numbers
- efivarfs: revert "fix memory leak in efivarfs_create()"
- perf probe: Fix to die_entrypc() returns error correctly
- USB: core: Change %pK for __user pointers to %px
- x86/speculation: Fix prctl() when spectre_v2_user={seccomp,prctl},ibpb
- USB: core: add endpoint-blacklist quirk
- USB: core: Fix regression in Hercules audio card
- btrfs: fix lockdep splat when reading qgroup config on mount
- Linux 4.4.247
* Xenial update: v4.4.246 upstream stable release (LP: #1906700)
- ah6: fix error return code in ah6_input()
- atm: nicstar: Unmap DMA on send error
- net: b44: fix error return code in b44_init_one()
- net: bridge: add missing counters to ndo_get_stats64 callback
- netlabel: fix our progress tracking in netlbl_unlabel_staticlist()
- netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist()
- net/mlx4_core: Fix init_hca fields offset
- net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request
- qlcnic: fix error return code in qlcnic_83xx_restart_hw()
- sctp: change to hold/put transport for proto_unreach_timer
- net: usb: qmi_wwan: Set DTR quirk for MR400
- net: Have netpoll bring-up DSA management interface
- pinctrl: rockchip: enable gpio pclk for rockchip_gpio_to_irq
- arm64: psci: Avoid printing in cpu_psci_cpu_die()
- MIPS: Fix BUILD_ROLLBACK_PROLOGUE for microMIPS
- Input: adxl34x - clean up a data type in adxl34x_probe()
- arm: dts: imx6qdl-udoo: fix rgmii phy-mode for ksz9031 phy
- ARM: dts: imx50-evk: Fix the chip select 1 IOMUX
- perf lock: Don't free "lock_seq_stat" if read_count isn't zero
- can: dev: can_restart(): post buffer from the right context
- can: peak_usb: fix potential integer overflow on shift of a int
- can: m_can: m_can_handle_state_change(): fix state change
- MIPS: Alchemy: Fix memleak in alchemy_clk_setup_cpu
- regulator: ti-abb: Fix array out of bound read access on the first
transition
- libfs: fix error cast of negative value in simple_attr_write()
- ALSA: ctl: fix error path at adding user-defined element set
- ALSA: mixart: Fix mutex deadlock
- tty: serial: imx: keep console clocks always on
- efivarfs: fix memory leak in efivarfs_create()
- ext4: fix bogus warning in ext4_update_dx_flag()
- xtensa: disable preemption around cache alias management calls
- mac80211: minstrel: remove deferred sampling code
- mac80211: minstrel: fix tx status processing corner case
- mac80211: allow driver to prevent two stations w/ same address
- mac80211: free sta in sta_info_insert_finish() on errors
- s390/cpum_sf.c: fix file permission for cpum_sfb_size
- x86/microcode/intel: Check patch signature before saving microcode for
early
loading
- Linux 4.4.246
* Xenial update: v4.4.245 upstream stable release (LP: #1906698)
- i2c: imx: Fix external abort on interrupt in exit paths
- xfs: catch inode allocation state mismatch corruption
- xfs: validate cached inodes are free when allocated
-
[Kernel-packages] [Bug 1866149] Re: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl
This bug was fixed in the package linux-kvm - 5.4.0-1032.33 --- linux-kvm (5.4.0-1032.33) focal; urgency=medium * focal/linux-kvm: 5.4.0-1032.33 -proposed tracker (LP: #1911326) * CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl (LP: #1866149) - [Config]: set CONFIG_BASE_FULL * Missing module nfsv4 in linux-kvm (LP: #1907266) - [Config] kvm: Enable NFSv4 [ Ubuntu: 5.4.0-63.71 ] * focal/linux: 5.4.0-63.71 -proposed tracker (LP: #1911333) * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME * Focal update: v5.4.79 upstream stable release (LP: #1907151) - net/mlx5: Use async EQ setup cleanup helpers for multiple EQs - net/mlx5: poll cmd EQ in case of command timeout - net/mlx5: Fix a race when moving command interface to events mode - net/mlx5: Add retry mechanism to the command entry index allocation * Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770) - mt76: fix fix ampdu locking * [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander (LP: #1899802) - scsi: mpt3sas: Define hba_port structure - scsi: mpt3sas: Allocate memory for hba_port objects - scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device() - scsi: mpt3sas: Update hba_port's sas_address & phy_mask - scsi: mpt3sas: Get device objects using sas_address & portID - scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port() - scsi: mpt3sas: Get sas_device objects using device's rphy - scsi: mpt3sas: Update hba_port objects after host reset - scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough - scsi: mpt3sas: Handling HBA vSES device - scsi: mpt3sas: Add bypass_dirty_port_flag parameter - scsi: mpt3sas: Handle vSES vphy object during HBA reset - scsi: mpt3sas: Add module parameter multipath_on_hba - scsi: mpt3sas: Bump driver version to 35.101.00.00 [ Ubuntu: 5.4.0-62.70 ] * focal/linux: 5.4.0-62.70 -proposed tracker (LP: #1911144) * CVE-2020-28374 - SAUCE: target: fix XCOPY NAA identifier lookup * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.4.0-60.67 ] * Packaging resync (LP: #1786013) - [Packaging] update variants - update dkms package versions * CVE-2021-1052 // CVE-2021-1053 - [Packaging] NVIDIA -- Add the NVIDIA 460 driver -- Kelsey Skunberg Thu, 14 Jan 2021 15:25:42 -0700 ** Changed in: linux-kvm (Ubuntu Groovy) Status: Fix Committed => 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/1866149 Title: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Incomplete Status in linux source package in Xenial: Invalid Status in linux-kvm source package in Xenial: Fix Released Status in linux source package in Bionic: Invalid Status in linux-kvm source package in Bionic: Fix Released Status in linux source package in Focal: Invalid Status in linux-kvm source package in Focal: Fix Released Status in linux source package in Groovy: Invalid Status in linux-kvm source package in Groovy: Fix Released Bug description: [Impact] systemd-systemctl will fail to set kernel.pid_max, leading to a degraded boot. [Fix] Set CONFIG_BASE_FULL=y, CONFIG_BASE_SMALL=0. [Test case] Write 419304 to /proc/sys/kernel/pid_max. [Potential regression] Boot time may be affected. I'm not completely sure which package to log this against. I'm running the kvm focal minimal cloud image from 20200302. I noticed on boot that there was an error complaining that systemd-systemctl couldn't update pid_max to the value it wanted: systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf: # Bump the numeric PID range to its maximum of 2^22 (from the in-kernel default # of 2^16), to make PID collisions less likely. kernel.pid_max = 4194304 However, the linux-image-kvm kernel is compiled with CONFIG_BASE_SMALL=1 and this triggers the following code in include/linux/threads.h #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \ (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT)) which means that if CONFIG_BASE_SMALL is set we get a maximum limit of PAGE_SIZE * 8, which on x86 would be 32768. As a workaround I can override it with a file in /etc/sysctl.d/ but this shouldn't be needed. I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud
[Kernel-packages] [Bug 1866149] Re: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl
This bug was fixed in the package linux-kvm - 4.15.0-1084.86
---
linux-kvm (4.15.0-1084.86) bionic; urgency=medium
* bionic/linux-kvm: 4.15.0-1084.86 -proposed tracker (LP: #1911288)
* CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd
default sysctl (LP: #1866149)
- [Config]: set CONFIG_BASE_FULL
[ Ubuntu: 4.15.0-133.137 ]
* bionic/linux: 4.15.0-133.137 -proposed tracker (LP: #1911295)
* [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
context
- can: dev: __can_get_echo_skb(): fix real payload length return value for
RTR
frames
- can: can_create_echo_skb(): fix echo skb generation: always use
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback
is
on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
!CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
- drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
- pinctrl: amd: use higher precision for 512 RtcClk
- pinctrl: amd: fix incorrect way to disable debounce filter
- swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
- IPv6: Set SIT tunnel hard_header_len to zero
- net/af_iucv: fix null pointer dereference on shutdown
- net/x25: Fix null-ptr-deref in x25_connect
[Kernel-packages] [Bug 1906128] Re: Touchpad not detected on ByteSpeed C15B laptop
This bug was fixed in the package linux - 4.4.0-201.233
---
linux (4.4.0-201.233) xenial; urgency=medium
* xenial/linux: 4.4.0-201.233 -proposed tracker (LP: #1911265)
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- powerpc/rtas: Restrict RTAS requests from userspace
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Xenial update: v4.4.247 upstream stable release (LP: #1906703)
- btrfs: tree-checker: Enhance chunk checker to validate chunk profile
- btrfs: inode: Verify inode mode to avoid NULL pointer dereference
- HID: cypress: Support Varmilo Keyboards' media hotkeys
- Input: i8042 - allow insmod to succeed on devices without an i8042
controller
- HID: hid-sensor-hub: Fix issue with devices with no report ID
- x86/xen: don't unbind uninitialized lock_kicker_irq
- proc: don't allow async path resolution of /proc/self components
- dmaengine: pl330: _prep_dma_memcpy: Fix wrong burst size
- scsi: libiscsi: Fix NOP race condition
- scsi: target: iscsi: Fix cmd abort fabric stop race
- scsi: ufs: Fix race between shutdown and runtime resume flow
- bnxt_en: fix error return code in bnxt_init_board()
- video: hyperv_fb: Fix the cache type when mapping the VRAM
- bnxt_en: Release PCI regions when DMA mask setup fails during probe.
- IB/mthca: fix return value of error branch in mthca_init_cq()
- nfc: s3fwrn5: use signed integer for parsing GPIO numbers
- efivarfs: revert "fix memory leak in efivarfs_create()"
- perf probe: Fix to die_entrypc() returns error correctly
- USB: core: Change %pK for __user pointers to %px
- x86/speculation: Fix prctl() when spectre_v2_user={seccomp,prctl},ibpb
- USB: core: add endpoint-blacklist quirk
- USB: core: Fix regression in Hercules audio card
- btrfs: fix lockdep splat when reading qgroup config on mount
- Linux 4.4.247
* Xenial update: v4.4.246 upstream stable release (LP: #1906700)
- ah6: fix error return code in ah6_input()
- atm: nicstar: Unmap DMA on send error
- net: b44: fix error return code in b44_init_one()
- net: bridge: add missing counters to ndo_get_stats64 callback
- netlabel: fix our progress tracking in netlbl_unlabel_staticlist()
- netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist()
- net/mlx4_core: Fix init_hca fields offset
- net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request
- qlcnic: fix error return code in qlcnic_83xx_restart_hw()
- sctp: change to hold/put transport for proto_unreach_timer
- net: usb: qmi_wwan: Set DTR quirk for MR400
- net: Have netpoll bring-up DSA management interface
- pinctrl: rockchip: enable gpio pclk for rockchip_gpio_to_irq
- arm64: psci: Avoid printing in cpu_psci_cpu_die()
- MIPS: Fix BUILD_ROLLBACK_PROLOGUE for microMIPS
- Input: adxl34x - clean up a data type in adxl34x_probe()
- arm: dts: imx6qdl-udoo: fix rgmii phy-mode for ksz9031 phy
- ARM: dts: imx50-evk: Fix the chip select 1 IOMUX
- perf lock: Don't free "lock_seq_stat" if read_count isn't zero
- can: dev: can_restart(): post buffer from the right context
- can: peak_usb: fix potential integer overflow on shift of a int
- can: m_can: m_can_handle_state_change(): fix state change
- MIPS: Alchemy: Fix memleak in alchemy_clk_setup_cpu
- regulator: ti-abb: Fix array out of bound read access on the first
transition
- libfs: fix error cast of negative value in simple_attr_write()
- ALSA: ctl: fix error path at adding user-defined element set
- ALSA: mixart: Fix mutex deadlock
- tty: serial: imx: keep console clocks always on
- efivarfs: fix memory leak in efivarfs_create()
- ext4: fix bogus warning in ext4_update_dx_flag()
- xtensa: disable preemption around cache alias management calls
- mac80211: minstrel: remove deferred sampling code
- mac80211: minstrel: fix tx status processing corner case
- mac80211: allow driver to prevent two stations w/ same address
- mac80211: free sta in sta_info_insert_finish() on errors
- s390/cpum_sf.c: fix file permission for cpum_sfb_size
- x86/microcode/intel: Check patch signature before saving microcode for
early
loading
- Linux 4.4.246
* Xenial update: v4.4.245 upstream stable release (LP: #1906698)
- i2c: imx: Fix external abort on interrupt in exit paths
- xfs: catch inode allocation state mismatch corruption
- xfs: validate cached inodes are free when allocated
- powerpc/8xx: Always fault when _PAGE_ACCESSED is not set
- Input: sunkbd - avoid use-after-free in teardown paths
- mac80211: always wind down STA state
- KVM: x86: clflushopt should be treated as a no-op by emulation
- Linux
[Kernel-packages] [Bug 1903596] Re: stack trace in kernel
This bug was fixed in the package linux - 4.4.0-201.233
---
linux (4.4.0-201.233) xenial; urgency=medium
* xenial/linux: 4.4.0-201.233 -proposed tracker (LP: #1911265)
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- powerpc/rtas: Restrict RTAS requests from userspace
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Xenial update: v4.4.247 upstream stable release (LP: #1906703)
- btrfs: tree-checker: Enhance chunk checker to validate chunk profile
- btrfs: inode: Verify inode mode to avoid NULL pointer dereference
- HID: cypress: Support Varmilo Keyboards' media hotkeys
- Input: i8042 - allow insmod to succeed on devices without an i8042
controller
- HID: hid-sensor-hub: Fix issue with devices with no report ID
- x86/xen: don't unbind uninitialized lock_kicker_irq
- proc: don't allow async path resolution of /proc/self components
- dmaengine: pl330: _prep_dma_memcpy: Fix wrong burst size
- scsi: libiscsi: Fix NOP race condition
- scsi: target: iscsi: Fix cmd abort fabric stop race
- scsi: ufs: Fix race between shutdown and runtime resume flow
- bnxt_en: fix error return code in bnxt_init_board()
- video: hyperv_fb: Fix the cache type when mapping the VRAM
- bnxt_en: Release PCI regions when DMA mask setup fails during probe.
- IB/mthca: fix return value of error branch in mthca_init_cq()
- nfc: s3fwrn5: use signed integer for parsing GPIO numbers
- efivarfs: revert "fix memory leak in efivarfs_create()"
- perf probe: Fix to die_entrypc() returns error correctly
- USB: core: Change %pK for __user pointers to %px
- x86/speculation: Fix prctl() when spectre_v2_user={seccomp,prctl},ibpb
- USB: core: add endpoint-blacklist quirk
- USB: core: Fix regression in Hercules audio card
- btrfs: fix lockdep splat when reading qgroup config on mount
- Linux 4.4.247
* Xenial update: v4.4.246 upstream stable release (LP: #1906700)
- ah6: fix error return code in ah6_input()
- atm: nicstar: Unmap DMA on send error
- net: b44: fix error return code in b44_init_one()
- net: bridge: add missing counters to ndo_get_stats64 callback
- netlabel: fix our progress tracking in netlbl_unlabel_staticlist()
- netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist()
- net/mlx4_core: Fix init_hca fields offset
- net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request
- qlcnic: fix error return code in qlcnic_83xx_restart_hw()
- sctp: change to hold/put transport for proto_unreach_timer
- net: usb: qmi_wwan: Set DTR quirk for MR400
- net: Have netpoll bring-up DSA management interface
- pinctrl: rockchip: enable gpio pclk for rockchip_gpio_to_irq
- arm64: psci: Avoid printing in cpu_psci_cpu_die()
- MIPS: Fix BUILD_ROLLBACK_PROLOGUE for microMIPS
- Input: adxl34x - clean up a data type in adxl34x_probe()
- arm: dts: imx6qdl-udoo: fix rgmii phy-mode for ksz9031 phy
- ARM: dts: imx50-evk: Fix the chip select 1 IOMUX
- perf lock: Don't free "lock_seq_stat" if read_count isn't zero
- can: dev: can_restart(): post buffer from the right context
- can: peak_usb: fix potential integer overflow on shift of a int
- can: m_can: m_can_handle_state_change(): fix state change
- MIPS: Alchemy: Fix memleak in alchemy_clk_setup_cpu
- regulator: ti-abb: Fix array out of bound read access on the first
transition
- libfs: fix error cast of negative value in simple_attr_write()
- ALSA: ctl: fix error path at adding user-defined element set
- ALSA: mixart: Fix mutex deadlock
- tty: serial: imx: keep console clocks always on
- efivarfs: fix memory leak in efivarfs_create()
- ext4: fix bogus warning in ext4_update_dx_flag()
- xtensa: disable preemption around cache alias management calls
- mac80211: minstrel: remove deferred sampling code
- mac80211: minstrel: fix tx status processing corner case
- mac80211: allow driver to prevent two stations w/ same address
- mac80211: free sta in sta_info_insert_finish() on errors
- s390/cpum_sf.c: fix file permission for cpum_sfb_size
- x86/microcode/intel: Check patch signature before saving microcode for
early
loading
- Linux 4.4.246
* Xenial update: v4.4.245 upstream stable release (LP: #1906698)
- i2c: imx: Fix external abort on interrupt in exit paths
- xfs: catch inode allocation state mismatch corruption
- xfs: validate cached inodes are free when allocated
- powerpc/8xx: Always fault when _PAGE_ACCESSED is not set
- Input: sunkbd - avoid use-after-free in teardown paths
- mac80211: always wind down STA state
- KVM: x86: clflushopt should be treated as a no-op by emulation
- Linux
[Kernel-packages] [Bug 1906698] Re: Xenial update: v4.4.245 upstream stable release
This bug was fixed in the package linux - 4.4.0-201.233
---
linux (4.4.0-201.233) xenial; urgency=medium
* xenial/linux: 4.4.0-201.233 -proposed tracker (LP: #1911265)
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- powerpc/rtas: Restrict RTAS requests from userspace
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Xenial update: v4.4.247 upstream stable release (LP: #1906703)
- btrfs: tree-checker: Enhance chunk checker to validate chunk profile
- btrfs: inode: Verify inode mode to avoid NULL pointer dereference
- HID: cypress: Support Varmilo Keyboards' media hotkeys
- Input: i8042 - allow insmod to succeed on devices without an i8042
controller
- HID: hid-sensor-hub: Fix issue with devices with no report ID
- x86/xen: don't unbind uninitialized lock_kicker_irq
- proc: don't allow async path resolution of /proc/self components
- dmaengine: pl330: _prep_dma_memcpy: Fix wrong burst size
- scsi: libiscsi: Fix NOP race condition
- scsi: target: iscsi: Fix cmd abort fabric stop race
- scsi: ufs: Fix race between shutdown and runtime resume flow
- bnxt_en: fix error return code in bnxt_init_board()
- video: hyperv_fb: Fix the cache type when mapping the VRAM
- bnxt_en: Release PCI regions when DMA mask setup fails during probe.
- IB/mthca: fix return value of error branch in mthca_init_cq()
- nfc: s3fwrn5: use signed integer for parsing GPIO numbers
- efivarfs: revert "fix memory leak in efivarfs_create()"
- perf probe: Fix to die_entrypc() returns error correctly
- USB: core: Change %pK for __user pointers to %px
- x86/speculation: Fix prctl() when spectre_v2_user={seccomp,prctl},ibpb
- USB: core: add endpoint-blacklist quirk
- USB: core: Fix regression in Hercules audio card
- btrfs: fix lockdep splat when reading qgroup config on mount
- Linux 4.4.247
* Xenial update: v4.4.246 upstream stable release (LP: #1906700)
- ah6: fix error return code in ah6_input()
- atm: nicstar: Unmap DMA on send error
- net: b44: fix error return code in b44_init_one()
- net: bridge: add missing counters to ndo_get_stats64 callback
- netlabel: fix our progress tracking in netlbl_unlabel_staticlist()
- netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist()
- net/mlx4_core: Fix init_hca fields offset
- net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request
- qlcnic: fix error return code in qlcnic_83xx_restart_hw()
- sctp: change to hold/put transport for proto_unreach_timer
- net: usb: qmi_wwan: Set DTR quirk for MR400
- net: Have netpoll bring-up DSA management interface
- pinctrl: rockchip: enable gpio pclk for rockchip_gpio_to_irq
- arm64: psci: Avoid printing in cpu_psci_cpu_die()
- MIPS: Fix BUILD_ROLLBACK_PROLOGUE for microMIPS
- Input: adxl34x - clean up a data type in adxl34x_probe()
- arm: dts: imx6qdl-udoo: fix rgmii phy-mode for ksz9031 phy
- ARM: dts: imx50-evk: Fix the chip select 1 IOMUX
- perf lock: Don't free "lock_seq_stat" if read_count isn't zero
- can: dev: can_restart(): post buffer from the right context
- can: peak_usb: fix potential integer overflow on shift of a int
- can: m_can: m_can_handle_state_change(): fix state change
- MIPS: Alchemy: Fix memleak in alchemy_clk_setup_cpu
- regulator: ti-abb: Fix array out of bound read access on the first
transition
- libfs: fix error cast of negative value in simple_attr_write()
- ALSA: ctl: fix error path at adding user-defined element set
- ALSA: mixart: Fix mutex deadlock
- tty: serial: imx: keep console clocks always on
- efivarfs: fix memory leak in efivarfs_create()
- ext4: fix bogus warning in ext4_update_dx_flag()
- xtensa: disable preemption around cache alias management calls
- mac80211: minstrel: remove deferred sampling code
- mac80211: minstrel: fix tx status processing corner case
- mac80211: allow driver to prevent two stations w/ same address
- mac80211: free sta in sta_info_insert_finish() on errors
- s390/cpum_sf.c: fix file permission for cpum_sfb_size
- x86/microcode/intel: Check patch signature before saving microcode for
early
loading
- Linux 4.4.246
* Xenial update: v4.4.245 upstream stable release (LP: #1906698)
- i2c: imx: Fix external abort on interrupt in exit paths
- xfs: catch inode allocation state mismatch corruption
- xfs: validate cached inodes are free when allocated
- powerpc/8xx: Always fault when _PAGE_ACCESSED is not set
- Input: sunkbd - avoid use-after-free in teardown paths
- mac80211: always wind down STA state
- KVM: x86: clflushopt should be treated as a no-op by emulation
- Linux
[Kernel-packages] [Bug 1906700] Re: Xenial update: v4.4.246 upstream stable release
This bug was fixed in the package linux - 4.4.0-201.233
---
linux (4.4.0-201.233) xenial; urgency=medium
* xenial/linux: 4.4.0-201.233 -proposed tracker (LP: #1911265)
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- powerpc/rtas: Restrict RTAS requests from userspace
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Xenial update: v4.4.247 upstream stable release (LP: #1906703)
- btrfs: tree-checker: Enhance chunk checker to validate chunk profile
- btrfs: inode: Verify inode mode to avoid NULL pointer dereference
- HID: cypress: Support Varmilo Keyboards' media hotkeys
- Input: i8042 - allow insmod to succeed on devices without an i8042
controller
- HID: hid-sensor-hub: Fix issue with devices with no report ID
- x86/xen: don't unbind uninitialized lock_kicker_irq
- proc: don't allow async path resolution of /proc/self components
- dmaengine: pl330: _prep_dma_memcpy: Fix wrong burst size
- scsi: libiscsi: Fix NOP race condition
- scsi: target: iscsi: Fix cmd abort fabric stop race
- scsi: ufs: Fix race between shutdown and runtime resume flow
- bnxt_en: fix error return code in bnxt_init_board()
- video: hyperv_fb: Fix the cache type when mapping the VRAM
- bnxt_en: Release PCI regions when DMA mask setup fails during probe.
- IB/mthca: fix return value of error branch in mthca_init_cq()
- nfc: s3fwrn5: use signed integer for parsing GPIO numbers
- efivarfs: revert "fix memory leak in efivarfs_create()"
- perf probe: Fix to die_entrypc() returns error correctly
- USB: core: Change %pK for __user pointers to %px
- x86/speculation: Fix prctl() when spectre_v2_user={seccomp,prctl},ibpb
- USB: core: add endpoint-blacklist quirk
- USB: core: Fix regression in Hercules audio card
- btrfs: fix lockdep splat when reading qgroup config on mount
- Linux 4.4.247
* Xenial update: v4.4.246 upstream stable release (LP: #1906700)
- ah6: fix error return code in ah6_input()
- atm: nicstar: Unmap DMA on send error
- net: b44: fix error return code in b44_init_one()
- net: bridge: add missing counters to ndo_get_stats64 callback
- netlabel: fix our progress tracking in netlbl_unlabel_staticlist()
- netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist()
- net/mlx4_core: Fix init_hca fields offset
- net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request
- qlcnic: fix error return code in qlcnic_83xx_restart_hw()
- sctp: change to hold/put transport for proto_unreach_timer
- net: usb: qmi_wwan: Set DTR quirk for MR400
- net: Have netpoll bring-up DSA management interface
- pinctrl: rockchip: enable gpio pclk for rockchip_gpio_to_irq
- arm64: psci: Avoid printing in cpu_psci_cpu_die()
- MIPS: Fix BUILD_ROLLBACK_PROLOGUE for microMIPS
- Input: adxl34x - clean up a data type in adxl34x_probe()
- arm: dts: imx6qdl-udoo: fix rgmii phy-mode for ksz9031 phy
- ARM: dts: imx50-evk: Fix the chip select 1 IOMUX
- perf lock: Don't free "lock_seq_stat" if read_count isn't zero
- can: dev: can_restart(): post buffer from the right context
- can: peak_usb: fix potential integer overflow on shift of a int
- can: m_can: m_can_handle_state_change(): fix state change
- MIPS: Alchemy: Fix memleak in alchemy_clk_setup_cpu
- regulator: ti-abb: Fix array out of bound read access on the first
transition
- libfs: fix error cast of negative value in simple_attr_write()
- ALSA: ctl: fix error path at adding user-defined element set
- ALSA: mixart: Fix mutex deadlock
- tty: serial: imx: keep console clocks always on
- efivarfs: fix memory leak in efivarfs_create()
- ext4: fix bogus warning in ext4_update_dx_flag()
- xtensa: disable preemption around cache alias management calls
- mac80211: minstrel: remove deferred sampling code
- mac80211: minstrel: fix tx status processing corner case
- mac80211: allow driver to prevent two stations w/ same address
- mac80211: free sta in sta_info_insert_finish() on errors
- s390/cpum_sf.c: fix file permission for cpum_sfb_size
- x86/microcode/intel: Check patch signature before saving microcode for
early
loading
- Linux 4.4.246
* Xenial update: v4.4.245 upstream stable release (LP: #1906698)
- i2c: imx: Fix external abort on interrupt in exit paths
- xfs: catch inode allocation state mismatch corruption
- xfs: validate cached inodes are free when allocated
- powerpc/8xx: Always fault when _PAGE_ACCESSED is not set
- Input: sunkbd - avoid use-after-free in teardown paths
- mac80211: always wind down STA state
- KVM: x86: clflushopt should be treated as a no-op by emulation
- Linux
[Kernel-packages] [Bug 1906703] Re: Xenial update: v4.4.247 upstream stable release
This bug was fixed in the package linux - 4.4.0-201.233
---
linux (4.4.0-201.233) xenial; urgency=medium
* xenial/linux: 4.4.0-201.233 -proposed tracker (LP: #1911265)
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- powerpc/rtas: Restrict RTAS requests from userspace
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Xenial update: v4.4.247 upstream stable release (LP: #1906703)
- btrfs: tree-checker: Enhance chunk checker to validate chunk profile
- btrfs: inode: Verify inode mode to avoid NULL pointer dereference
- HID: cypress: Support Varmilo Keyboards' media hotkeys
- Input: i8042 - allow insmod to succeed on devices without an i8042
controller
- HID: hid-sensor-hub: Fix issue with devices with no report ID
- x86/xen: don't unbind uninitialized lock_kicker_irq
- proc: don't allow async path resolution of /proc/self components
- dmaengine: pl330: _prep_dma_memcpy: Fix wrong burst size
- scsi: libiscsi: Fix NOP race condition
- scsi: target: iscsi: Fix cmd abort fabric stop race
- scsi: ufs: Fix race between shutdown and runtime resume flow
- bnxt_en: fix error return code in bnxt_init_board()
- video: hyperv_fb: Fix the cache type when mapping the VRAM
- bnxt_en: Release PCI regions when DMA mask setup fails during probe.
- IB/mthca: fix return value of error branch in mthca_init_cq()
- nfc: s3fwrn5: use signed integer for parsing GPIO numbers
- efivarfs: revert "fix memory leak in efivarfs_create()"
- perf probe: Fix to die_entrypc() returns error correctly
- USB: core: Change %pK for __user pointers to %px
- x86/speculation: Fix prctl() when spectre_v2_user={seccomp,prctl},ibpb
- USB: core: add endpoint-blacklist quirk
- USB: core: Fix regression in Hercules audio card
- btrfs: fix lockdep splat when reading qgroup config on mount
- Linux 4.4.247
* Xenial update: v4.4.246 upstream stable release (LP: #1906700)
- ah6: fix error return code in ah6_input()
- atm: nicstar: Unmap DMA on send error
- net: b44: fix error return code in b44_init_one()
- net: bridge: add missing counters to ndo_get_stats64 callback
- netlabel: fix our progress tracking in netlbl_unlabel_staticlist()
- netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist()
- net/mlx4_core: Fix init_hca fields offset
- net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request
- qlcnic: fix error return code in qlcnic_83xx_restart_hw()
- sctp: change to hold/put transport for proto_unreach_timer
- net: usb: qmi_wwan: Set DTR quirk for MR400
- net: Have netpoll bring-up DSA management interface
- pinctrl: rockchip: enable gpio pclk for rockchip_gpio_to_irq
- arm64: psci: Avoid printing in cpu_psci_cpu_die()
- MIPS: Fix BUILD_ROLLBACK_PROLOGUE for microMIPS
- Input: adxl34x - clean up a data type in adxl34x_probe()
- arm: dts: imx6qdl-udoo: fix rgmii phy-mode for ksz9031 phy
- ARM: dts: imx50-evk: Fix the chip select 1 IOMUX
- perf lock: Don't free "lock_seq_stat" if read_count isn't zero
- can: dev: can_restart(): post buffer from the right context
- can: peak_usb: fix potential integer overflow on shift of a int
- can: m_can: m_can_handle_state_change(): fix state change
- MIPS: Alchemy: Fix memleak in alchemy_clk_setup_cpu
- regulator: ti-abb: Fix array out of bound read access on the first
transition
- libfs: fix error cast of negative value in simple_attr_write()
- ALSA: ctl: fix error path at adding user-defined element set
- ALSA: mixart: Fix mutex deadlock
- tty: serial: imx: keep console clocks always on
- efivarfs: fix memory leak in efivarfs_create()
- ext4: fix bogus warning in ext4_update_dx_flag()
- xtensa: disable preemption around cache alias management calls
- mac80211: minstrel: remove deferred sampling code
- mac80211: minstrel: fix tx status processing corner case
- mac80211: allow driver to prevent two stations w/ same address
- mac80211: free sta in sta_info_insert_finish() on errors
- s390/cpum_sf.c: fix file permission for cpum_sfb_size
- x86/microcode/intel: Check patch signature before saving microcode for
early
loading
- Linux 4.4.246
* Xenial update: v4.4.245 upstream stable release (LP: #1906698)
- i2c: imx: Fix external abort on interrupt in exit paths
- xfs: catch inode allocation state mismatch corruption
- xfs: validate cached inodes are free when allocated
- powerpc/8xx: Always fault when _PAGE_ACCESSED is not set
- Input: sunkbd - avoid use-after-free in teardown paths
- mac80211: always wind down STA state
- KVM: x86: clflushopt should be treated as a no-op by emulation
- Linux
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
This bug was fixed in the package linux - 5.4.0-65.73 --- linux (5.4.0-65.73) focal; urgency=medium * focal/linux: 5.4.0-65.73 -proposed tracker (LP: #1912220) * initramfs unpacking failed (LP: #1835660) - SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around initrds. * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME * Focal update: v5.4.79 upstream stable release (LP: #1907151) - net/mlx5: Use async EQ setup cleanup helpers for multiple EQs - net/mlx5: poll cmd EQ in case of command timeout - net/mlx5: Fix a race when moving command interface to events mode - net/mlx5: Add retry mechanism to the command entry index allocation * Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770) - mt76: fix fix ampdu locking * [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander (LP: #1899802) - scsi: mpt3sas: Define hba_port structure - scsi: mpt3sas: Allocate memory for hba_port objects - scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device() - scsi: mpt3sas: Update hba_port's sas_address & phy_mask - scsi: mpt3sas: Get device objects using sas_address & portID - scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port() - scsi: mpt3sas: Get sas_device objects using device's rphy - scsi: mpt3sas: Update hba_port objects after host reset - scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough - scsi: mpt3sas: Handling HBA vSES device - scsi: mpt3sas: Add bypass_dirty_port_flag parameter - scsi: mpt3sas: Handle vSES vphy object during HBA reset - scsi: mpt3sas: Add module parameter multipath_on_hba - scsi: mpt3sas: Bump driver version to 35.101.00.00 -- Kleber Sacilotto de Souza Mon, 18 Jan 2021 17:31:23 +0100 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120 ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
This bug was fixed in the package linux - 5.8.0-41.46 --- linux (5.8.0-41.46) groovy; urgency=medium * groovy/linux: 5.8.0-41.46 -proposed tracker (LP: #1912219) * Groovy update: upstream stable patchset 2020-12-17 (LP: #1908555) // nvme drive fails after some time (LP: #1910866) - Revert "nvme-pci: remove last_sq_tail" * initramfs unpacking failed (LP: #1835660) - SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around initrds. * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME -- Kleber Sacilotto de Souza Mon, 18 Jan 2021 17:01:08 +0100 -- 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1890487] Re: rpi3b+ wifi doesn't get used if ethernet disconnected
This bug was fixed in the package linux-raspi - 5.8.0-1013.16 --- linux-raspi (5.8.0-1013.16) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1013.16 -proposed tracker (LP: #1911336) * rpi3b+ wifi doesn't get used if ethernet disconnected (LP: #1890487) - net: lan78xx: Ack pending PHY ints when resetting * groovy/linux-raspi: Upstream raspberrypi patchset 2020-11-05 (LP: #1903541) - brcmfmac: Increase power saving delay to 2s - overlays: Update i2c0 overlay to disable the i2c0mux. - dt: Remove duplicate assignment for i2c0 pinctrl config - overlays: Add option for composite to vc4-kms-v3d-pi4. - overlays: minor typo in instructions - overlays: Regenerate upstream-pi4 overlay - overlays: Add parameters to adafruit18, sainsmart18 - rpivid_h265: Fix width/height typo - overlays: Add extra CMA sizes (up to 512M) - overlays: Add note to BCM2711 overlays - configs: Remove I2C_BRCMSTB from the kernel - net: bcmgenet: Reset RBUF on first open - ASoC: cs42xx8: Only define cs42xx8_of_match once - configs: Regenerate the defconfigs - staging: bcm2835-codec: Use a define the completion timeout - staging: bcm2835-codec: Correct buffer number change on start streaming - USB: gadget: f_hid: avoid crashes and log spam - Update hy28b-overlay.dts - overlays: Update display GPIO declarations - configs: Add CONFIG_RTC_DRV_SD3078=m - overlays: Add sd3078 to the i2c-rtc overlay - configs: Restore SND_PCM_OSS=m - dwc_otg: initialise sched_frame for periodic QHs that were parked - arm64: configs: Enable Unicam support - arm64: configs: Enable V4L2 test module support - staging: bcm2835-camera: Replace deprecated V4L2_PIX_FMT_BGR32 - staging: bcm2835-codec: Replace deprecated V4L2_PIX_FMT_BGR32 - ARM: bcm2711-rpi.dts: Unlock DMA channels 9 & 10 - gpio: Add gpio-fsm driver - configs: Add CONFIG_GPIO_FSM=m - overlays: Add fsm-demo overlay - overlays: Add ghost-amp overlay - Fixes a problem when module probes before i2c module is available - [Config] raspi: updateconfigs after update to rpi-5.8.y 2020-11-05 * Raspberry Pi 400 Kernel Panic (LP: #1907432) - SAUCE: Revert "mailbox: avoid timer start from callback" [ Ubuntu: 5.8.0-39.44 ] * groovy/linux: 5.8.0-39.44 -proposed tracker (LP: #1911350) * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME [ Ubuntu: 5.8.0-38.43 ] * groovy/linux: 5.8.0-38.43 -proposed tracker (LP: #1911143) * CVE-2020-28374 - SAUCE: target: fix XCOPY NAA identifier lookup * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.8.0-36.40 ] * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly [ Ubuntu: 5.8.0-35.39 ] * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-1052 // CVE-2021-1053 - [Packaging] NVIDIA -- Add the NVIDIA 460 driver -- Ian May Wed, 13 Jan 2021 22:57:35 -0600 ** Changed in: linux-raspi (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28374 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1052 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1053 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1890487 Title: rpi3b+ wifi doesn't get used if ethernet disconnected Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Focal: Fix Committed Status in linux-raspi source package in Groovy: Fix Released Bug description: [Impact] When testing 20.04.1, I noticed some different behavior on rpi3b+ that I didn't see on rpi3b or rpi4. I have configured the device with ethernet, added netplan yaml for my wifi network, and rebooted. So both eth0 and wlan0 have an ip address. On all other devices (rpi3b, rpi4, etc), if I unplug eth0 wile pinging something, I'll miss maybe 1 ping and then it will continue to work and just switch over to wlan0. However, on rpi3b+ it just stops being able to access the network completely. If I re-run netplan apply, it will start using wifi again, but if I plug eth0 back in, then unplug it, it stops just like before. I am seeing this with the current 20.04.1 release: Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I also went back and tested the original 20.04 release and it happens there too, so this is not a regression: Linux ubuntu 5.4.0-1008-raspi #8-Ubuntu
[Kernel-packages] [Bug 1896784] Re: Use Azure host for time keeping in all images
This bug was fixed in the package linux-azure - 5.4.0-1039.41
---
linux-azure (5.4.0-1039.41) focal; urgency=medium
* focal/linux-azure: 5.4.0-1039.41 -proposed tracker (LP: #1912002)
* Use Azure host for time keeping in all images (LP: #1896784)
- hv_utils: return error if host timesysnc update is stale
- hv_utils: drain the timesync packets on onchannelcallback
* [linux-azure] Batch hibernate and resume IO requests (LP: #1904458)
- PM: hibernate: Batch hibernate and resume IO requests
linux-azure (5.4.0-1038.40) focal; urgency=medium
* focal/linux-azure: 5.4.0-1038.40 -proposed tracker (LP: #1911317)
[ Ubuntu: 5.4.0-63.71 ]
* focal/linux: 5.4.0-63.71 -proposed tracker (LP: #1911333)
* overlay: permission regression in 5.4.0-51.56 due to patches related to
CVE-2020-16120 (LP: #1900141)
- ovl: do not fail because of O_NOATIME
* Focal update: v5.4.79 upstream stable release (LP: #1907151)
- net/mlx5: Use async EQ setup cleanup helpers for multiple EQs
- net/mlx5: poll cmd EQ in case of command timeout
- net/mlx5: Fix a race when moving command interface to events mode
- net/mlx5: Add retry mechanism to the command entry index allocation
* Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770)
- mt76: fix fix ampdu locking
* [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports
topology where zoning is enabled in expander (LP: #1899802)
- scsi: mpt3sas: Define hba_port structure
- scsi: mpt3sas: Allocate memory for hba_port objects
- scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device()
- scsi: mpt3sas: Update hba_port's sas_address & phy_mask
- scsi: mpt3sas: Get device objects using sas_address & portID
- scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port()
- scsi: mpt3sas: Get sas_device objects using device's rphy
- scsi: mpt3sas: Update hba_port objects after host reset
- scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough
- scsi: mpt3sas: Handling HBA vSES device
- scsi: mpt3sas: Add bypass_dirty_port_flag parameter
- scsi: mpt3sas: Handle vSES vphy object during HBA reset
- scsi: mpt3sas: Add module parameter multipath_on_hba
- scsi: mpt3sas: Bump driver version to 35.101.00.00
[ Ubuntu: 5.4.0-62.70 ]
* focal/linux: 5.4.0-62.70 -proposed tracker (LP: #1911144)
* CVE-2020-28374
- SAUCE: target: fix XCOPY NAA identifier lookup
* Packaging resync (LP: #1786013)
- update dkms package versions
-- Marcelo Henrique Cerri Mon, 18 Jan
2021 09:44:59 -0300
** Changed in: linux-azure (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28374
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1896784
Title:
Use Azure host for time keeping in all images
Status in linux-azure package in Ubuntu:
New
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Committed
Status in linux-azure source package in Focal:
Fix Released
Status in linux-azure-4.15 source package in Focal:
Invalid
Bug description:
SRU Justification:
[Impact]
Microsoft would like to request a change to the time keeping method in
the Azure images.
We would like to request that an Azure image uses the Azure host for
time sync by default. This will require the use of the Chrony
package.
The Chrony package would need to be installed by default in all images
and be configured to use /dev/ptp0 for timekeeping.
There is a request for two patches to be backported so Chrony time can
stay in sync before being set as the default.
Patches are already in the 5.8 kernel. Only needed for azure 5.4 and
4.15
[Fix]
backport these two patches:
b46b4a8a57c3 ("hv_utils: drain the timesync packets on onchannelcallback")
90b125f4cd26 ("hv_utils: return error if host timesysnc update is stale")
[Test Case]
Desired test cases:
- verify Chrony time can stay in sync
- verify caller is notified if host timesync update is stale
- verify all timesync packets are drained on onchannelcallback to avoid
stale packets
Microsoft holds test cases for the above. They verified a 4.15 and 5.4
test kernels with the above patches backported to work as expected.
[Regression Potential]
Caller may get an error now if host timesync messages were not
processed by the guest. This wasn't getting reported to the caller
before and may appear to be a regression if it occurs.
Regression potential may also lay in still incorrectly managing
timesync packets on onchannelcallback.
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1899802] Re: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander
This bug was fixed in the package linux - 5.4.0-65.73 --- linux (5.4.0-65.73) focal; urgency=medium * focal/linux: 5.4.0-65.73 -proposed tracker (LP: #1912220) * initramfs unpacking failed (LP: #1835660) - SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around initrds. * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME * Focal update: v5.4.79 upstream stable release (LP: #1907151) - net/mlx5: Use async EQ setup cleanup helpers for multiple EQs - net/mlx5: poll cmd EQ in case of command timeout - net/mlx5: Fix a race when moving command interface to events mode - net/mlx5: Add retry mechanism to the command entry index allocation * Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770) - mt76: fix fix ampdu locking * [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander (LP: #1899802) - scsi: mpt3sas: Define hba_port structure - scsi: mpt3sas: Allocate memory for hba_port objects - scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device() - scsi: mpt3sas: Update hba_port's sas_address & phy_mask - scsi: mpt3sas: Get device objects using sas_address & portID - scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port() - scsi: mpt3sas: Get sas_device objects using device's rphy - scsi: mpt3sas: Update hba_port objects after host reset - scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough - scsi: mpt3sas: Handling HBA vSES device - scsi: mpt3sas: Add bypass_dirty_port_flag parameter - scsi: mpt3sas: Handle vSES vphy object during HBA reset - scsi: mpt3sas: Add module parameter multipath_on_hba - scsi: mpt3sas: Bump driver version to 35.101.00.00 -- Kleber Sacilotto de Souza Mon, 18 Jan 2021 17:31:23 +0100 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120 -- 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/1899802 Title: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: Request to include patch set "PATCH 00/14] mpt3sas: Add support for multi-port path topology" which will support the topologies where zoning is enabled in the expander as shown below, Zone 1 Zone 2 |-| || | HD1 . HD25 | | HD26 ..HD50| | |==| | | | | | | | | | Expander| | | |==| | | | | || | |---|-| ||---| x8| |x8 ___|__|___ |HBA | || Current driver doesn't support this type of topology and will add only one zoned drives to the OS. So to support these types of topology we need below patch set in the driver. https://marc.info/?l=linux-scsi=160226366707807=2 So, requesting you include this patch for next upcoming Ubuntu kernel release. Currently we have posted this patch set to upstream community and they yet to review this patch set. Meanwhile If I get the base kernel source code for next upcoming Ubuntu kernel then I can prepare the patches over this base kernel source and share it in this BZ. Thanks, Sreekanth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899802/+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 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
This bug was fixed in the package linux - 5.8.0-41.46
---
linux (5.8.0-41.46) groovy; urgency=medium
* groovy/linux: 5.8.0-41.46 -proposed tracker (LP: #1912219)
* Groovy update: upstream stable patchset 2020-12-17 (LP: #1908555) // nvme
drive fails after some time (LP: #1910866)
- Revert "nvme-pci: remove last_sq_tail"
* initramfs unpacking failed (LP: #1835660)
- SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around
initrds.
* overlay: permission regression in 5.4.0-51.56 due to patches related to
CVE-2020-16120 (LP: #1900141)
- ovl: do not fail because of O_NOATIME
-- Kleber Sacilotto de Souza Mon, 18 Jan
2021 17:01:08 +0100
--
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/1900141
Title:
overlay: permission regression in 5.4.0-51.56 due to patches related
to CVE-2020-16120
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
SRU Justification
[Impact]
The backports to fix CVE-2020-16120 introduced a regression for
overlay mounts within user namespaces. Files with ownership outside of
the user namespace can no longer be accessed, even if allowed by both
DAC and MAC.
This issue is fixed by the following upstream commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b6650dab404c701d7fe08a108b746542a934da84
This commit relaxes the check to remove O_NOATIME from the open flags
for the file in the lower filesystem when the overlay filesystem
mounter is not privileged with respect to the underlying inode, rather
than failing the open as happens now.
[Test Case]
The attached lp1900141.sh script reproduces the issue.
[Where problems could occur]
For the most part this patch restores previous behavior of allowing
access to these files while keeping the enhanced permission checks
towards the lower filesystem to help prevent unauthorized access to
file data in the lower filesystem. The one difference in behavior is
that files in the lower filesystem may no longer be opened with the
O_NOATIME flag, potentially causing atime updates for these files
which were not happening before. If any software expects O_NOATIME
behavior in this situation then it could cause problems for that
software. However, the correct behavior is that only the inode owner
or a process with CAP_FOWNER towards the inode owner is allowed to
open with O_NOATIME (as documented in open(2)).
---
We use unprivileged user namespaces with overlay mounts for
containers. After recently upgrading our Focal kernels to 5.4.0-51.56
this breaks, one cannot access files through the overlay mount in the
container anymore. This is very likely caused by some of the patches
that were added in relation to CVE-2020-16120.
The following commands allow to reproduce the problem when executed as
an arbitrary non-root user:
mkdir /tmp/test /tmp/test/upper /tmp/test/work /tmp/test/usr
unshare -m -U -r /bin/sh -c "mount -t overlay none /tmp/test/usr -o
lowerdir=/usr,upperdir=/tmp/test/upper,workdir=/tmp/test/work; ls -l
/tmp/test/usr/bin/id; file /tmp/test/usr/bin/id; /tmp/test/usr/bin/id"
The output when broken is this:
-rwxr-xr-x 1 nobody nogroup 47480 Sep 5 2019 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: executable, regular file, no read permission
/bin/sh: 1: /tmp/test/usr/bin/id: Operation not permitted
The expected output is this:
-rwxr-xr-x 1 nobody nogroup 43224 Jan 18 2018 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: ELF 64-bit LSB shared object, ...
uid=0(root) gid=0(root) groups=0(root),65534(nogroup)
These commands create a user namespace and within it mount an overlay
of /usr to /tmp/test/usr and then try to access something in it.
This works on Ubuntu Bionic with kernel 4.15.0-121.123 (note that this
already includes a fix for CVE-2020-16120) and on kernel 5.4.0-48.52
but is broken on kernel 5.4.0-51.56, no matter whether on Bionic or
Focal.
So I strongly suspect that not the actual security fixes for
CVE-2020-16120 are the cause, but one of the following two patches
that according to the changelogs were applied in the same revision but
only to 5.4, not to 4.15:
ovl: call secutiry hook in ovl_real_ioctl()
ovl: check permission to open real file
The mail with the announcement (https://www.openwall.com/lists/oss-
security/2020/10/13/6) lists these two commits as separate from the
actual security fixes ("may be desired or necessary").
Is it possible to revert these two changes or fix them such that our
unprivileged containers work again on Ubuntu kernel 5.4? Or is there a
workaround that I can add to my container solution such that this use
case works again?
ProblemType: Bug
[Kernel-packages] [Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
This bug was fixed in the package linux - 5.4.0-65.73 --- linux (5.4.0-65.73) focal; urgency=medium * focal/linux: 5.4.0-65.73 -proposed tracker (LP: #1912220) * initramfs unpacking failed (LP: #1835660) - SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around initrds. * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME * Focal update: v5.4.79 upstream stable release (LP: #1907151) - net/mlx5: Use async EQ setup cleanup helpers for multiple EQs - net/mlx5: poll cmd EQ in case of command timeout - net/mlx5: Fix a race when moving command interface to events mode - net/mlx5: Add retry mechanism to the command entry index allocation * Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770) - mt76: fix fix ampdu locking * [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander (LP: #1899802) - scsi: mpt3sas: Define hba_port structure - scsi: mpt3sas: Allocate memory for hba_port objects - scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device() - scsi: mpt3sas: Update hba_port's sas_address & phy_mask - scsi: mpt3sas: Get device objects using sas_address & portID - scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port() - scsi: mpt3sas: Get sas_device objects using device's rphy - scsi: mpt3sas: Update hba_port objects after host reset - scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough - scsi: mpt3sas: Handling HBA vSES device - scsi: mpt3sas: Add bypass_dirty_port_flag parameter - scsi: mpt3sas: Handle vSES vphy object during HBA reset - scsi: mpt3sas: Add module parameter multipath_on_hba - scsi: mpt3sas: Bump driver version to 35.101.00.00 -- Kleber Sacilotto de Souza Mon, 18 Jan 2021 17:31:23 +0100 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120 ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => 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/1900141 Title: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: SRU Justification [Impact] The backports to fix CVE-2020-16120 introduced a regression for overlay mounts within user namespaces. Files with ownership outside of the user namespace can no longer be accessed, even if allowed by both DAC and MAC. This issue is fixed by the following upstream commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b6650dab404c701d7fe08a108b746542a934da84 This commit relaxes the check to remove O_NOATIME from the open flags for the file in the lower filesystem when the overlay filesystem mounter is not privileged with respect to the underlying inode, rather than failing the open as happens now. [Test Case] The attached lp1900141.sh script reproduces the issue. [Where problems could occur] For the most part this patch restores previous behavior of allowing access to these files while keeping the enhanced permission checks towards the lower filesystem to help prevent unauthorized access to file data in the lower filesystem. The one difference in behavior is that files in the lower filesystem may no longer be opened with the O_NOATIME flag, potentially causing atime updates for these files which were not happening before. If any software expects O_NOATIME behavior in this situation then it could cause problems for that software. However, the correct behavior is that only the inode owner or a process with CAP_FOWNER towards the inode owner is allowed to open with O_NOATIME (as documented in open(2)). --- We use unprivileged user namespaces with overlay mounts for containers. After recently upgrading our Focal kernels to 5.4.0-51.56 this breaks, one cannot access files through the overlay mount in the container anymore. This is very likely caused by some of the patches that were added in relation to CVE-2020-16120. The following commands allow to reproduce the problem when executed as an arbitrary non-root user: mkdir /tmp/test /tmp/test/upper /tmp/test/work /tmp/test/usr unshare -m -U -r /bin/sh -c "mount -t overlay none /tmp/test/usr -o lowerdir=/usr,upperdir=/tmp/test/upper,workdir=/tmp/test/work; ls -l /tmp/test/usr/bin/id; file /tmp/test/usr/bin/id; /tmp/test/usr/bin/id" The output when broken is this: -rwxr-xr-x 1 nobody nogroup 47480 Sep 5 2019 /tmp/test/usr/bin/id
[Kernel-packages] [Bug 1904458] Re: [linux-azure] Batch hibernate and resume IO requests
This bug was fixed in the package linux-azure - 5.8.0-1020.22
---
linux-azure (5.8.0-1020.22) groovy; urgency=medium
* groovy/linux-azure: 5.8.0-1020.22 -proposed tracker (LP: #1912236)
* [linux-azure] Batch hibernate and resume IO requests (LP: #1904458)
- PM: hibernate: Batch hibernate and resume IO requests
[ Ubuntu: 5.8.0-41.46 ]
* groovy/linux: 5.8.0-41.46 -proposed tracker (LP: #1912219)
* Groovy update: upstream stable patchset 2020-12-17 (LP: #1908555) // nvme
drive fails after some time (LP: #1910866)
- Revert "nvme-pci: remove last_sq_tail"
* initramfs unpacking failed (LP: #1835660)
- SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around
initrds.
* overlay: permission regression in 5.4.0-51.56 due to patches related to
CVE-2020-16120 (LP: #1900141)
- ovl: do not fail because of O_NOATIME
-- Kleber Sacilotto de Souza Tue, 19 Jan
2021 10:09:49 +0100
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1904458
Title:
[linux-azure] Batch hibernate and resume IO requests
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Focal:
Fix Released
Status in linux-azure source package in Groovy:
Fix Released
Bug description:
[Impact]
Microsoft would like to request the following upstream commit in all
releases supported on Azure. This commit improves a signification
delay in hibernation/resume:
55c4478a8f0e("PM: hibernate: Batch hibernate and resume IO requests")
Details of this commit:
Hibernate and resume process submits individual IO requests for each page of
the data, so use blk_plug to improve the batching of these requests.
Testing this change with hibernate and resumes consistently shows
merging of the IO requests and more than an order of magnitude
improvement in hibernate and resume speed is observed.
One hibernate and resume cycle for 16GB RAM out of 32GB in use takes
around 21 minutes before the change, and 1 minutes after the change on
a system with limited storage IOPS.
[Test Case]
Follow the steps described here:
https://bugs.launchpad.net/ubuntu/+source/linux-
azure/+bug/1880032/comments/14
And compare the time need to save the instance state.
[Where problems could occur]
Considering the size of the patch and the code it touches, the most
likely issues are related to hibernation itself. Considering the
hibernation isn't officially support, any hibernation issues should
even considered regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1904458/+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 1903541] Re: groovy/linux-raspi: Upstream raspberrypi patchset 2020-11-05
This bug was fixed in the package linux-raspi - 5.8.0-1013.16 --- linux-raspi (5.8.0-1013.16) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1013.16 -proposed tracker (LP: #1911336) * rpi3b+ wifi doesn't get used if ethernet disconnected (LP: #1890487) - net: lan78xx: Ack pending PHY ints when resetting * groovy/linux-raspi: Upstream raspberrypi patchset 2020-11-05 (LP: #1903541) - brcmfmac: Increase power saving delay to 2s - overlays: Update i2c0 overlay to disable the i2c0mux. - dt: Remove duplicate assignment for i2c0 pinctrl config - overlays: Add option for composite to vc4-kms-v3d-pi4. - overlays: minor typo in instructions - overlays: Regenerate upstream-pi4 overlay - overlays: Add parameters to adafruit18, sainsmart18 - rpivid_h265: Fix width/height typo - overlays: Add extra CMA sizes (up to 512M) - overlays: Add note to BCM2711 overlays - configs: Remove I2C_BRCMSTB from the kernel - net: bcmgenet: Reset RBUF on first open - ASoC: cs42xx8: Only define cs42xx8_of_match once - configs: Regenerate the defconfigs - staging: bcm2835-codec: Use a define the completion timeout - staging: bcm2835-codec: Correct buffer number change on start streaming - USB: gadget: f_hid: avoid crashes and log spam - Update hy28b-overlay.dts - overlays: Update display GPIO declarations - configs: Add CONFIG_RTC_DRV_SD3078=m - overlays: Add sd3078 to the i2c-rtc overlay - configs: Restore SND_PCM_OSS=m - dwc_otg: initialise sched_frame for periodic QHs that were parked - arm64: configs: Enable Unicam support - arm64: configs: Enable V4L2 test module support - staging: bcm2835-camera: Replace deprecated V4L2_PIX_FMT_BGR32 - staging: bcm2835-codec: Replace deprecated V4L2_PIX_FMT_BGR32 - ARM: bcm2711-rpi.dts: Unlock DMA channels 9 & 10 - gpio: Add gpio-fsm driver - configs: Add CONFIG_GPIO_FSM=m - overlays: Add fsm-demo overlay - overlays: Add ghost-amp overlay - Fixes a problem when module probes before i2c module is available - [Config] raspi: updateconfigs after update to rpi-5.8.y 2020-11-05 * Raspberry Pi 400 Kernel Panic (LP: #1907432) - SAUCE: Revert "mailbox: avoid timer start from callback" [ Ubuntu: 5.8.0-39.44 ] * groovy/linux: 5.8.0-39.44 -proposed tracker (LP: #1911350) * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME [ Ubuntu: 5.8.0-38.43 ] * groovy/linux: 5.8.0-38.43 -proposed tracker (LP: #1911143) * CVE-2020-28374 - SAUCE: target: fix XCOPY NAA identifier lookup * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.8.0-36.40 ] * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly [ Ubuntu: 5.8.0-35.39 ] * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-1052 // CVE-2021-1053 - [Packaging] NVIDIA -- Add the NVIDIA 460 driver -- Ian May Wed, 13 Jan 2021 22:57:35 -0600 ** Changed in: linux-raspi (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28374 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1052 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1053 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1903541 Title: groovy/linux-raspi: Upstream raspberrypi patchset 2020-11-05 Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Groovy: Fix Released Bug description: Upstream raspberrypi patchset 2020-11-05 Ported from the following raspberrypi branch: rpi-5.8.y from https://github.com/raspberrypi/linux.git ASoC: cros_ec_codec: fix kconfig dependency warning for SND_SOC_CROS_EC_CODEC mm/page_owner: change split_page_owner to take a count mm: khugepaged: recalculate min_free_kbytes after memory hotplug as expected by khugepaged mm/error_inject: Fix allow_error_inject function signatures. fbmem: add margin check to fb_check_caps() xhci: don't create endpoint debugfs entry before ring buffer is set. serial: pl011: Fix lockdep splat when handling magic-sysrq interrupt media: tc358743: cleanup tc358743_cec_isr media: tc358743: initialize variable gpiolib: Disable compat ->read() code in UML case clk: bcm2835: add missing release if devm_clk_hw_register fails Fixes a problem when module probes before i2c module is available overlays: Add ghost-amp overlay overlays: Add fsm-demo overlay configs: Add CONFIG_GPIO_FSM=m gpio: Add gpio-fsm
[Kernel-packages] [Bug 1904458] Re: [linux-azure] Batch hibernate and resume IO requests
This bug was fixed in the package linux-azure - 5.4.0-1039.41
---
linux-azure (5.4.0-1039.41) focal; urgency=medium
* focal/linux-azure: 5.4.0-1039.41 -proposed tracker (LP: #1912002)
* Use Azure host for time keeping in all images (LP: #1896784)
- hv_utils: return error if host timesysnc update is stale
- hv_utils: drain the timesync packets on onchannelcallback
* [linux-azure] Batch hibernate and resume IO requests (LP: #1904458)
- PM: hibernate: Batch hibernate and resume IO requests
linux-azure (5.4.0-1038.40) focal; urgency=medium
* focal/linux-azure: 5.4.0-1038.40 -proposed tracker (LP: #1911317)
[ Ubuntu: 5.4.0-63.71 ]
* focal/linux: 5.4.0-63.71 -proposed tracker (LP: #1911333)
* overlay: permission regression in 5.4.0-51.56 due to patches related to
CVE-2020-16120 (LP: #1900141)
- ovl: do not fail because of O_NOATIME
* Focal update: v5.4.79 upstream stable release (LP: #1907151)
- net/mlx5: Use async EQ setup cleanup helpers for multiple EQs
- net/mlx5: poll cmd EQ in case of command timeout
- net/mlx5: Fix a race when moving command interface to events mode
- net/mlx5: Add retry mechanism to the command entry index allocation
* Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770)
- mt76: fix fix ampdu locking
* [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports
topology where zoning is enabled in expander (LP: #1899802)
- scsi: mpt3sas: Define hba_port structure
- scsi: mpt3sas: Allocate memory for hba_port objects
- scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device()
- scsi: mpt3sas: Update hba_port's sas_address & phy_mask
- scsi: mpt3sas: Get device objects using sas_address & portID
- scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port()
- scsi: mpt3sas: Get sas_device objects using device's rphy
- scsi: mpt3sas: Update hba_port objects after host reset
- scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough
- scsi: mpt3sas: Handling HBA vSES device
- scsi: mpt3sas: Add bypass_dirty_port_flag parameter
- scsi: mpt3sas: Handle vSES vphy object during HBA reset
- scsi: mpt3sas: Add module parameter multipath_on_hba
- scsi: mpt3sas: Bump driver version to 35.101.00.00
[ Ubuntu: 5.4.0-62.70 ]
* focal/linux: 5.4.0-62.70 -proposed tracker (LP: #1911144)
* CVE-2020-28374
- SAUCE: target: fix XCOPY NAA identifier lookup
* Packaging resync (LP: #1786013)
- update dkms package versions
-- Marcelo Henrique Cerri Mon, 18 Jan
2021 09:44:59 -0300
** Changed in: linux-azure (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28374
** Changed in: linux-azure (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1904458
Title:
[linux-azure] Batch hibernate and resume IO requests
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Focal:
Fix Released
Status in linux-azure source package in Groovy:
Fix Released
Bug description:
[Impact]
Microsoft would like to request the following upstream commit in all
releases supported on Azure. This commit improves a signification
delay in hibernation/resume:
55c4478a8f0e("PM: hibernate: Batch hibernate and resume IO requests")
Details of this commit:
Hibernate and resume process submits individual IO requests for each page of
the data, so use blk_plug to improve the batching of these requests.
Testing this change with hibernate and resumes consistently shows
merging of the IO requests and more than an order of magnitude
improvement in hibernate and resume speed is observed.
One hibernate and resume cycle for 16GB RAM out of 32GB in use takes
around 21 minutes before the change, and 1 minutes after the change on
a system with limited storage IOPS.
[Test Case]
Follow the steps described here:
https://bugs.launchpad.net/ubuntu/+source/linux-
azure/+bug/1880032/comments/14
And compare the time need to save the instance state.
[Where problems could occur]
Considering the size of the patch and the code it touches, the most
likely issues are related to hibernation itself. Considering the
hibernation isn't officially support, any hibernation issues should
even considered regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1904458/+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 1905786] Re: perf_event_open is not restricted to admin by default
This bug was fixed in the package linux-raspi2 - 4.15.0-1078.83
---
linux-raspi2 (4.15.0-1078.83) bionic; urgency=medium
* bionic/linux-raspi2: 4.15.0-1078.83 -proposed tracker (LP: #1911270)
* perf_event_open is not restricted to admin by default (LP: #1905786)
- [Config]: set CONFIG_SECURITY_PERF_EVENTS_RESTRICT
[ Ubuntu: 4.15.0-133.137 ]
* bionic/linux: 4.15.0-133.137 -proposed tracker (LP: #1911295)
* [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
context
- can: dev: __can_get_echo_skb(): fix real payload length return value for
RTR
frames
- can: can_create_echo_skb(): fix echo skb generation: always use
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback
is
on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
!CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
- drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
- pinctrl: amd: use higher precision for 512 RtcClk
- pinctrl: amd: fix incorrect way to disable debounce filter
- swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
- IPv6: Set SIT tunnel hard_header_len to zero
- net/af_iucv: fix null pointer dereference on shutdown
- net/x25: Fix null-ptr-deref in x25_connect
-
[Kernel-packages] [Bug 1906770] Re: Kernel 5.4.0-56 Wi-Fi does not connect
This bug was fixed in the package linux - 5.4.0-65.73 --- linux (5.4.0-65.73) focal; urgency=medium * focal/linux: 5.4.0-65.73 -proposed tracker (LP: #1912220) * initramfs unpacking failed (LP: #1835660) - SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around initrds. * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME * Focal update: v5.4.79 upstream stable release (LP: #1907151) - net/mlx5: Use async EQ setup cleanup helpers for multiple EQs - net/mlx5: poll cmd EQ in case of command timeout - net/mlx5: Fix a race when moving command interface to events mode - net/mlx5: Add retry mechanism to the command entry index allocation * Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770) - mt76: fix fix ampdu locking * [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander (LP: #1899802) - scsi: mpt3sas: Define hba_port structure - scsi: mpt3sas: Allocate memory for hba_port objects - scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device() - scsi: mpt3sas: Update hba_port's sas_address & phy_mask - scsi: mpt3sas: Get device objects using sas_address & portID - scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port() - scsi: mpt3sas: Get sas_device objects using device's rphy - scsi: mpt3sas: Update hba_port objects after host reset - scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough - scsi: mpt3sas: Handling HBA vSES device - scsi: mpt3sas: Add bypass_dirty_port_flag parameter - scsi: mpt3sas: Handle vSES vphy object during HBA reset - scsi: mpt3sas: Add module parameter multipath_on_hba - scsi: mpt3sas: Bump driver version to 35.101.00.00 -- Kleber Sacilotto de Souza Mon, 18 Jan 2021 17:31:23 +0100 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120 -- 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/1906770 Title: Kernel 5.4.0-56 Wi-Fi does not connect Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Bug description: After updating to 5.4.0-56 (generic) on Mint 19.3, Wi-Fi cannot complete connection to network with Netgear A6210 USB adapter (Mediatek MT7612U chipset). Network manager can see available networks, but attempting to connect to a network stalls on "connecting" and does not complete connection. Reverting to 5.4.0-54 solves problem. I did not see this problem after updating to 5.4.0-56 on a 10-year-old Toshiba Satellite laptop (also Mint 19.3), so it appears related to the Netgear/Mediatek hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906770/+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 1906850] Re: aws: xen-netfront: prevent potential error on hibernate
This bug was fixed in the package linux-aws - 4.15.0-1093.99
---
linux-aws (4.15.0-1093.99) bionic; urgency=medium
* bionic/linux-aws: 4.15.0-1093.99 -proposed tracker (LP: #1911275)
* aws: network performance regression due to initial TCP receive buffer size
change (LP: #1910200)
- tcp: select sane initial rcvq_space.space for big MSS
* arm64: prevent losing page dirty state (LP: #1908503)
- arm64: pgtable: Ensure dirty bit is preserved across pte_wrprotect()
* Disable Atari partition support for cloud kernels (LP: #1908264)
- [Config] Disable Atari partition support
* aws: xen-netfront: prevent potential error on hibernate (LP: #1906850)
- SAUCE: xen-netfront: prevent unnecessary close on hibernate
[ Ubuntu: 4.15.0-133.137 ]
* bionic/linux: 4.15.0-133.137 -proposed tracker (LP: #1911295)
* [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
context
- can: dev: __can_get_echo_skb(): fix real payload length return value for
RTR
frames
- can: can_create_echo_skb(): fix echo skb generation: always use
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback
is
on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
!CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
-
[Kernel-packages] [Bug 1906850] Re: aws: xen-netfront: prevent potential error on hibernate
This bug was fixed in the package linux-aws - 5.4.0-1037.39 --- linux-aws (5.4.0-1037.39) focal; urgency=medium * focal/linux-aws: 5.4.0-1037.39 -proposed tracker (LP: #1911314) * aws: network performance regression due to initial TCP receive buffer size change (LP: #1910200) - tcp: select sane initial rcvq_space.space for big MSS * Disable Atari partition support for linux-aws (LP: #1908264) - [Config] Disable Atari partition support * aws: xen-netfront: prevent potential error on hibernate (LP: #1906850) - SAUCE: xen-netfront: prevent unnecessary close on hibernate [ Ubuntu: 5.4.0-63.71 ] * focal/linux: 5.4.0-63.71 -proposed tracker (LP: #1911333) * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME * Focal update: v5.4.79 upstream stable release (LP: #1907151) - net/mlx5: Use async EQ setup cleanup helpers for multiple EQs - net/mlx5: poll cmd EQ in case of command timeout - net/mlx5: Fix a race when moving command interface to events mode - net/mlx5: Add retry mechanism to the command entry index allocation * Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770) - mt76: fix fix ampdu locking * [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander (LP: #1899802) - scsi: mpt3sas: Define hba_port structure - scsi: mpt3sas: Allocate memory for hba_port objects - scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device() - scsi: mpt3sas: Update hba_port's sas_address & phy_mask - scsi: mpt3sas: Get device objects using sas_address & portID - scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port() - scsi: mpt3sas: Get sas_device objects using device's rphy - scsi: mpt3sas: Update hba_port objects after host reset - scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough - scsi: mpt3sas: Handling HBA vSES device - scsi: mpt3sas: Add bypass_dirty_port_flag parameter - scsi: mpt3sas: Handle vSES vphy object during HBA reset - scsi: mpt3sas: Add module parameter multipath_on_hba - scsi: mpt3sas: Bump driver version to 35.101.00.00 [ Ubuntu: 5.4.0-62.70 ] * focal/linux: 5.4.0-62.70 -proposed tracker (LP: #1911144) * CVE-2020-28374 - SAUCE: target: fix XCOPY NAA identifier lookup * Packaging resync (LP: #1786013) - update dkms package versions -- Kelsey Skunberg Wed, 13 Jan 2021 19:01:10 -0700 -- 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/1906850 Title: aws: xen-netfront: prevent potential error on hibernate Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux-aws source package in Groovy: Fix Committed Bug description: [Impact] On hibernation xen-netfront is setting the device state on the xenbus to "Closing" and then it's waiting for the backend state to acknowledge that state (with a timeout). However, if the device is already in the state "Closed" this opteration will always hit the timeout, preventing the system to hibernate correctly. [Test case] It is a quite rare condition that can be reproduced hibernating/resuming a Xen instance multiple times. When the problem happens we should in the log a Xen error message like the following: Freezing timed out; the device may become inconsistent state [Fix] If the device is already in the state "Closed", simply tear it down without notifying the Xen backend. [Regression potential] The fix would just prevent aborting hibernation if the netfront device is already in a "Closed" state. The resume callback is forcing the device into the "Initializing" state anyway, basically forcing a reset of the device, so nothing else in the state machine can be potentially broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1906850/+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 1907151] Re: Focal update: v5.4.79 upstream stable release
This bug was fixed in the package linux - 5.4.0-65.73 --- linux (5.4.0-65.73) focal; urgency=medium * focal/linux: 5.4.0-65.73 -proposed tracker (LP: #1912220) * initramfs unpacking failed (LP: #1835660) - SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around initrds. * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME * Focal update: v5.4.79 upstream stable release (LP: #1907151) - net/mlx5: Use async EQ setup cleanup helpers for multiple EQs - net/mlx5: poll cmd EQ in case of command timeout - net/mlx5: Fix a race when moving command interface to events mode - net/mlx5: Add retry mechanism to the command entry index allocation * Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770) - mt76: fix fix ampdu locking * [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander (LP: #1899802) - scsi: mpt3sas: Define hba_port structure - scsi: mpt3sas: Allocate memory for hba_port objects - scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device() - scsi: mpt3sas: Update hba_port's sas_address & phy_mask - scsi: mpt3sas: Get device objects using sas_address & portID - scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port() - scsi: mpt3sas: Get sas_device objects using device's rphy - scsi: mpt3sas: Update hba_port objects after host reset - scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough - scsi: mpt3sas: Handling HBA vSES device - scsi: mpt3sas: Add bypass_dirty_port_flag parameter - scsi: mpt3sas: Handle vSES vphy object during HBA reset - scsi: mpt3sas: Add module parameter multipath_on_hba - scsi: mpt3sas: Bump driver version to 35.101.00.00 -- Kleber Sacilotto de Souza Mon, 18 Jan 2021 17:31:23 +0100 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120 -- 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/1907151 Title: Focal update: v5.4.79 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.79 upstream stable release from git://git.kernel.org/ powerpc: Only include kup-radix.h for 64-bit Book3S MIPS: PCI: Fix MIPS build net/mlx5: Use async EQ setup cleanup helpers for multiple EQs net/mlx5: poll cmd EQ in case of command timeout net/mlx5: Fix a race when moving command interface to events mode net/mlx5: Add retry mechanism to the command entry index allocation powerpc/8xx: Always fault when _PAGE_ACCESSED is not set net: lantiq: Add locking for TX DMA channel Input: sunkbd - avoid use-after-free in teardown paths mac80211: always wind down STA state can: proc: can_remove_proc(): silence remove_proc_entry warning KVM: x86: clflushopt should be treated as a no-op by emulation ACPI: GED: fix -Wformat Linux 5.4.79 UBUNTU: upstream stable to v5.4.79 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907151/+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 1907266] Re: Missing module nfsv4 in linux-kvm
This bug was fixed in the package linux-kvm - 5.8.0-1016.18 --- linux-kvm (5.8.0-1016.18) groovy; urgency=medium * groovy/linux-kvm: 5.8.0-1016.18 -proposed tracker (LP: #1911344) * CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl (LP: #1866149) - [Config]: set CONFIG_BASE_FULL * Missing module nfsv4 in linux-kvm (LP: #1907266) - [Config] kvm: Enable NFSv4 [ Ubuntu: 5.8.0-39.44 ] * groovy/linux: 5.8.0-39.44 -proposed tracker (LP: #1911350) * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME [ Ubuntu: 5.8.0-38.43 ] * groovy/linux: 5.8.0-38.43 -proposed tracker (LP: #1911143) * CVE-2020-28374 - SAUCE: target: fix XCOPY NAA identifier lookup * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.8.0-36.40 ] * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly [ Ubuntu: 5.8.0-35.39 ] * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-1052 // CVE-2021-1053 - [Packaging] NVIDIA -- Add the NVIDIA 460 driver -- Kelsey Skunberg Thu, 14 Jan 2021 16:31:26 -0700 -- 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/1907266 Title: Missing module nfsv4 in linux-kvm Status in linux-kvm package in Ubuntu: Fix Committed Status in linux-kvm source package in Focal: Fix Released Status in linux-kvm source package in Groovy: Fix Released Status in linux-kvm source package in Hirsute: Fix Committed Bug description: [Impact] The nfsv4 module is not enabled in the linux-kvm kernel. There are customers and users of linux-kvm that want/need to use NFS version 4. [Test Case] $ modinfo nfsv4 modinfo: ERROR: Module nfsv4 not found. [Where problems could occur] It's a new module and loading it could crash a system (if the module is buggy). In addition, the kernel now provides its own DNS resolver for CIFS, NFS and AFS (and potentially others) and those lookups might fail if that particular code is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1907266/+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 1907266] Re: Missing module nfsv4 in linux-kvm
This bug was fixed in the package linux-kvm - 5.4.0-1032.33 --- linux-kvm (5.4.0-1032.33) focal; urgency=medium * focal/linux-kvm: 5.4.0-1032.33 -proposed tracker (LP: #1911326) * CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl (LP: #1866149) - [Config]: set CONFIG_BASE_FULL * Missing module nfsv4 in linux-kvm (LP: #1907266) - [Config] kvm: Enable NFSv4 [ Ubuntu: 5.4.0-63.71 ] * focal/linux: 5.4.0-63.71 -proposed tracker (LP: #1911333) * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME * Focal update: v5.4.79 upstream stable release (LP: #1907151) - net/mlx5: Use async EQ setup cleanup helpers for multiple EQs - net/mlx5: poll cmd EQ in case of command timeout - net/mlx5: Fix a race when moving command interface to events mode - net/mlx5: Add retry mechanism to the command entry index allocation * Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770) - mt76: fix fix ampdu locking * [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander (LP: #1899802) - scsi: mpt3sas: Define hba_port structure - scsi: mpt3sas: Allocate memory for hba_port objects - scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device() - scsi: mpt3sas: Update hba_port's sas_address & phy_mask - scsi: mpt3sas: Get device objects using sas_address & portID - scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port() - scsi: mpt3sas: Get sas_device objects using device's rphy - scsi: mpt3sas: Update hba_port objects after host reset - scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough - scsi: mpt3sas: Handling HBA vSES device - scsi: mpt3sas: Add bypass_dirty_port_flag parameter - scsi: mpt3sas: Handle vSES vphy object during HBA reset - scsi: mpt3sas: Add module parameter multipath_on_hba - scsi: mpt3sas: Bump driver version to 35.101.00.00 [ Ubuntu: 5.4.0-62.70 ] * focal/linux: 5.4.0-62.70 -proposed tracker (LP: #1911144) * CVE-2020-28374 - SAUCE: target: fix XCOPY NAA identifier lookup * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.4.0-60.67 ] * Packaging resync (LP: #1786013) - [Packaging] update variants - update dkms package versions * CVE-2021-1052 // CVE-2021-1053 - [Packaging] NVIDIA -- Add the NVIDIA 460 driver -- Kelsey Skunberg Thu, 14 Jan 2021 15:25:42 -0700 ** Changed in: linux-kvm (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28374 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1052 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1053 ** Changed in: linux-kvm (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1907266 Title: Missing module nfsv4 in linux-kvm Status in linux-kvm package in Ubuntu: Fix Committed Status in linux-kvm source package in Focal: Fix Released Status in linux-kvm source package in Groovy: Fix Released Status in linux-kvm source package in Hirsute: Fix Committed Bug description: [Impact] The nfsv4 module is not enabled in the linux-kvm kernel. There are customers and users of linux-kvm that want/need to use NFS version 4. [Test Case] $ modinfo nfsv4 modinfo: ERROR: Module nfsv4 not found. [Where problems could occur] It's a new module and loading it could crash a system (if the module is buggy). In addition, the kernel now provides its own DNS resolver for CIFS, NFS and AFS (and potentially others) and those lookups might fail if that particular code is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1907266/+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 1907432] Re: Raspberry Pi 400 Kernel Panic
This bug was fixed in the package linux-raspi - 5.8.0-1013.16 --- linux-raspi (5.8.0-1013.16) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1013.16 -proposed tracker (LP: #1911336) * rpi3b+ wifi doesn't get used if ethernet disconnected (LP: #1890487) - net: lan78xx: Ack pending PHY ints when resetting * groovy/linux-raspi: Upstream raspberrypi patchset 2020-11-05 (LP: #1903541) - brcmfmac: Increase power saving delay to 2s - overlays: Update i2c0 overlay to disable the i2c0mux. - dt: Remove duplicate assignment for i2c0 pinctrl config - overlays: Add option for composite to vc4-kms-v3d-pi4. - overlays: minor typo in instructions - overlays: Regenerate upstream-pi4 overlay - overlays: Add parameters to adafruit18, sainsmart18 - rpivid_h265: Fix width/height typo - overlays: Add extra CMA sizes (up to 512M) - overlays: Add note to BCM2711 overlays - configs: Remove I2C_BRCMSTB from the kernel - net: bcmgenet: Reset RBUF on first open - ASoC: cs42xx8: Only define cs42xx8_of_match once - configs: Regenerate the defconfigs - staging: bcm2835-codec: Use a define the completion timeout - staging: bcm2835-codec: Correct buffer number change on start streaming - USB: gadget: f_hid: avoid crashes and log spam - Update hy28b-overlay.dts - overlays: Update display GPIO declarations - configs: Add CONFIG_RTC_DRV_SD3078=m - overlays: Add sd3078 to the i2c-rtc overlay - configs: Restore SND_PCM_OSS=m - dwc_otg: initialise sched_frame for periodic QHs that were parked - arm64: configs: Enable Unicam support - arm64: configs: Enable V4L2 test module support - staging: bcm2835-camera: Replace deprecated V4L2_PIX_FMT_BGR32 - staging: bcm2835-codec: Replace deprecated V4L2_PIX_FMT_BGR32 - ARM: bcm2711-rpi.dts: Unlock DMA channels 9 & 10 - gpio: Add gpio-fsm driver - configs: Add CONFIG_GPIO_FSM=m - overlays: Add fsm-demo overlay - overlays: Add ghost-amp overlay - Fixes a problem when module probes before i2c module is available - [Config] raspi: updateconfigs after update to rpi-5.8.y 2020-11-05 * Raspberry Pi 400 Kernel Panic (LP: #1907432) - SAUCE: Revert "mailbox: avoid timer start from callback" [ Ubuntu: 5.8.0-39.44 ] * groovy/linux: 5.8.0-39.44 -proposed tracker (LP: #1911350) * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME [ Ubuntu: 5.8.0-38.43 ] * groovy/linux: 5.8.0-38.43 -proposed tracker (LP: #1911143) * CVE-2020-28374 - SAUCE: target: fix XCOPY NAA identifier lookup * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.8.0-36.40 ] * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly [ Ubuntu: 5.8.0-35.39 ] * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-1052 // CVE-2021-1053 - [Packaging] NVIDIA -- Add the NVIDIA 460 driver -- Ian May Wed, 13 Jan 2021 22:57:35 -0600 ** Changed in: linux-raspi (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28374 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1052 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1053 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1907432 Title: Raspberry Pi 400 Kernel Panic Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Groovy: Fix Released Bug description: When I power the Pi 400 down (with the key-combination on the pi 400 or with the navigation from the top right), a line like this is on screen: [59095.049506] reboot: Power down or that: [25784.810857] reboot: Power down Under this line, the cursor is frozen. After a while, suddenly, the text scrolls and stops after a while. I can read something about "Kernel Panic" on screen. I cannot power the device off. I have to pull the power plug to shut it down, or to re-plug it to reset it. The power-button (2sec) does not work, 10 seconds reset signal, neither. Here you can find my initial question to this phenomenon: https://answers.launchpad.net/ubuntu/+question/694349 This I should include: Linux version 5.8.0-1008-raspi (buildd@bos02-arm64-062) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #11-Ubuntu SMP PREEMPT Thu Nov 12 15:49:32 UTC 2020 I hope this report includes enough information. If not, please do not hesitate to contact me! Thanks so much for this project and thx for
[Kernel-packages] [Bug 1908264] Re: Disable Atari partition support for cloud kernels
This bug was fixed in the package linux-aws - 5.4.0-1037.39 --- linux-aws (5.4.0-1037.39) focal; urgency=medium * focal/linux-aws: 5.4.0-1037.39 -proposed tracker (LP: #1911314) * aws: network performance regression due to initial TCP receive buffer size change (LP: #1910200) - tcp: select sane initial rcvq_space.space for big MSS * Disable Atari partition support for linux-aws (LP: #1908264) - [Config] Disable Atari partition support * aws: xen-netfront: prevent potential error on hibernate (LP: #1906850) - SAUCE: xen-netfront: prevent unnecessary close on hibernate [ Ubuntu: 5.4.0-63.71 ] * focal/linux: 5.4.0-63.71 -proposed tracker (LP: #1911333) * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME * Focal update: v5.4.79 upstream stable release (LP: #1907151) - net/mlx5: Use async EQ setup cleanup helpers for multiple EQs - net/mlx5: poll cmd EQ in case of command timeout - net/mlx5: Fix a race when moving command interface to events mode - net/mlx5: Add retry mechanism to the command entry index allocation * Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770) - mt76: fix fix ampdu locking * [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander (LP: #1899802) - scsi: mpt3sas: Define hba_port structure - scsi: mpt3sas: Allocate memory for hba_port objects - scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device() - scsi: mpt3sas: Update hba_port's sas_address & phy_mask - scsi: mpt3sas: Get device objects using sas_address & portID - scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port() - scsi: mpt3sas: Get sas_device objects using device's rphy - scsi: mpt3sas: Update hba_port objects after host reset - scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough - scsi: mpt3sas: Handling HBA vSES device - scsi: mpt3sas: Add bypass_dirty_port_flag parameter - scsi: mpt3sas: Handle vSES vphy object during HBA reset - scsi: mpt3sas: Add module parameter multipath_on_hba - scsi: mpt3sas: Bump driver version to 35.101.00.00 [ Ubuntu: 5.4.0-62.70 ] * focal/linux: 5.4.0-62.70 -proposed tracker (LP: #1911144) * CVE-2020-28374 - SAUCE: target: fix XCOPY NAA identifier lookup * Packaging resync (LP: #1786013) - update dkms package versions -- Kelsey Skunberg Wed, 13 Jan 2021 19:01:10 -0700 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1908264 Title: Disable Atari partition support for cloud kernels Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Invalid Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Committed Status in linux-aws source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-aws source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: Fix Committed Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-aws source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Invalid Status in linux-azure-4.15 source package in Hirsute: Invalid Bug description: [Impact] Atari partition tables have very broad specifications, and can spontaneously show up on uncleared disks with "garbage" data. There have been reports of misinterpreted AHDI partition tables before (see [0] and [1]), usually as an unintended side-effect of using non-zeroed disks. Users of this specific partition scheme are unlikely to be on AWS instances, so we should disable them. [0] https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/ [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html [Test Case] Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r) [Fix] Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu [Regression Potential] There could be unexpected dependencies on Atari partitions that are impacted by this change. Considering Atari hardware hasn't been produced in a long time, and is unlikely to be used in AWS instances, the regression potential should be very low. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1908264] Re: Disable Atari partition support for cloud kernels
This bug was fixed in the package linux-aws - 4.15.0-1093.99
---
linux-aws (4.15.0-1093.99) bionic; urgency=medium
* bionic/linux-aws: 4.15.0-1093.99 -proposed tracker (LP: #1911275)
* aws: network performance regression due to initial TCP receive buffer size
change (LP: #1910200)
- tcp: select sane initial rcvq_space.space for big MSS
* arm64: prevent losing page dirty state (LP: #1908503)
- arm64: pgtable: Ensure dirty bit is preserved across pte_wrprotect()
* Disable Atari partition support for cloud kernels (LP: #1908264)
- [Config] Disable Atari partition support
* aws: xen-netfront: prevent potential error on hibernate (LP: #1906850)
- SAUCE: xen-netfront: prevent unnecessary close on hibernate
[ Ubuntu: 4.15.0-133.137 ]
* bionic/linux: 4.15.0-133.137 -proposed tracker (LP: #1911295)
* [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
context
- can: dev: __can_get_echo_skb(): fix real payload length return value for
RTR
frames
- can: can_create_echo_skb(): fix echo skb generation: always use
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback
is
on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
!CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
-
[Kernel-packages] [Bug 1908555] Re: Groovy update: upstream stable patchset 2020-12-17
This bug was fixed in the package linux - 5.8.0-41.46 --- linux (5.8.0-41.46) groovy; urgency=medium * groovy/linux: 5.8.0-41.46 -proposed tracker (LP: #1912219) * Groovy update: upstream stable patchset 2020-12-17 (LP: #1908555) // nvme drive fails after some time (LP: #1910866) - Revert "nvme-pci: remove last_sq_tail" * initramfs unpacking failed (LP: #1835660) - SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around initrds. * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME -- Kleber Sacilotto de Souza Mon, 18 Jan 2021 17:01:08 +0100 ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120 -- 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/1908555 Title: Groovy update: upstream stable patchset 2020-12-17 Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-12-17 Ported from the following upstream stable releases: v5.4.78, v5.9.9 from git://git.kernel.org/ drm/i915: Hold onto an explicit ref to i915_vma_work.pinned drm/i915/gem: Flush coherency domains on first set-domain-ioctl mm: memcg: link page counters to root if use_hierarchy is false nbd: don't update block size after device is started KVM: arm64: Force PTE mapping on fault resulting in a device mapping ASoC: Intel: kbl_rt5663_max98927: Fix kabylake_ssp_fixup function genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY hv_balloon: disable warning when floor reached net: xfrm: fix a race condition during allocing spi ASoC: codecs: wsa881x: add missing stream rates and format irqchip/sifive-plic: Fix broken irq_set_affinity() callback kunit: Fix kunit.py --raw_output option kunit: Don't fail test suites if one of them is empty usb: gadget: fsl: fix null pointer checking selftests: filter kselftest headers from command in lib.mk ASoC: codecs: wcd934x: Set digital gain range correctly ASoC: codecs: wcd9335: Set digital gain range correctly mtd: spi-nor: Fix address width on flash chips > 16MB xfs: set xefi_discard when creating a deferred agfl free log intent item mac80211: don't require VHT elements for HE on 2.4 GHz netfilter: nftables: fix netlink report logic in flowtable and genid netfilter: use actual socket sk rather than skb sk when routing harder netfilter: nf_tables: missing validation from the abort path netfilter: ipset: Update byte and packet counters regardless of whether they match irqchip/sifive-plic: Fix chip_data access within a hierarchy powerpc/eeh_cache: Fix a possible debugfs deadlock drm/vc4: bo: Add a managed action to cleanup the cache IB/srpt: Fix memory leak in srpt_add_one mm: memcontrol: correct the NR_ANON_THPS counter of hierarchical memcg drm/panfrost: rename error labels in device_init drm/panfrost: move devfreq_init()/fini() in device drm/panfrost: Fix module unload perf trace: Fix segfault when trying to trace events by cgroup perf tools: Add missing swap for ino_generation perf tools: Add missing swap for cgroup events ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link() iommu/vt-d: Fix a bug for PDP check in prq_event_thread afs: Fix warning due to unadvanced marshalling pointer afs: Fix incorrect freeing of the ACL passed to the YFS ACL store op vfio/pci: Implement ioeventfd thread handler for contended memory lock can: rx-offload: don't call kfree_skb() from IRQ context can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context can: dev: __can_get_echo_skb(): fix real payload length return value for RTR frames can: can_create_echo_skb(): fix echo skb generation: always use skb_clone() can: j1939: swap addr and pgn in the send example can: j1939: j1939_sk_bind(): return failure if netdev is down can: ti_hecc: ti_hecc_probe(): add missed clk_disable_unprepare() in error path can: xilinx_can: handle failure cases of pm_runtime_get_sync can: peak_usb: add range checking in decode operations can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping can: peak_canfd: pucan_handle_can_rx(): fix echo
[Kernel-packages] [Bug 1910200] Re: aws: network performance regression due to initial TCP receive buffer size change
This bug was fixed in the package linux-aws - 5.4.0-1037.39
---
linux-aws (5.4.0-1037.39) focal; urgency=medium
* focal/linux-aws: 5.4.0-1037.39 -proposed tracker (LP: #1911314)
* aws: network performance regression due to initial TCP receive buffer size
change (LP: #1910200)
- tcp: select sane initial rcvq_space.space for big MSS
* Disable Atari partition support for linux-aws (LP: #1908264)
- [Config] Disable Atari partition support
* aws: xen-netfront: prevent potential error on hibernate (LP: #1906850)
- SAUCE: xen-netfront: prevent unnecessary close on hibernate
[ Ubuntu: 5.4.0-63.71 ]
* focal/linux: 5.4.0-63.71 -proposed tracker (LP: #1911333)
* overlay: permission regression in 5.4.0-51.56 due to patches related to
CVE-2020-16120 (LP: #1900141)
- ovl: do not fail because of O_NOATIME
* Focal update: v5.4.79 upstream stable release (LP: #1907151)
- net/mlx5: Use async EQ setup cleanup helpers for multiple EQs
- net/mlx5: poll cmd EQ in case of command timeout
- net/mlx5: Fix a race when moving command interface to events mode
- net/mlx5: Add retry mechanism to the command entry index allocation
* Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770)
- mt76: fix fix ampdu locking
* [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports
topology where zoning is enabled in expander (LP: #1899802)
- scsi: mpt3sas: Define hba_port structure
- scsi: mpt3sas: Allocate memory for hba_port objects
- scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device()
- scsi: mpt3sas: Update hba_port's sas_address & phy_mask
- scsi: mpt3sas: Get device objects using sas_address & portID
- scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port()
- scsi: mpt3sas: Get sas_device objects using device's rphy
- scsi: mpt3sas: Update hba_port objects after host reset
- scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough
- scsi: mpt3sas: Handling HBA vSES device
- scsi: mpt3sas: Add bypass_dirty_port_flag parameter
- scsi: mpt3sas: Handle vSES vphy object during HBA reset
- scsi: mpt3sas: Add module parameter multipath_on_hba
- scsi: mpt3sas: Bump driver version to 35.101.00.00
[ Ubuntu: 5.4.0-62.70 ]
* focal/linux: 5.4.0-62.70 -proposed tracker (LP: #1911144)
* CVE-2020-28374
- SAUCE: target: fix XCOPY NAA identifier lookup
* Packaging resync (LP: #1786013)
- update dkms package versions
-- Kelsey Skunberg Wed, 13 Jan 2021
19:01:10 -0700
--
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/1910200
Title:
aws: network performance regression due to initial TCP receive buffer
size change
Status in linux-aws package in Ubuntu:
New
Status in linux-aws source package in Bionic:
Fix Released
Status in linux-aws source package in Focal:
Fix Released
Status in linux-aws source package in Groovy:
Fix Committed
Bug description:
[Impact]
AWS has seen some customers reporting networking performance
degradation after they upgraded their Ubuntu instanceses. This
regression is highly impacting customers who are using MTU=9000 (which
is the default in EC2).
[Test case]
Bug reproduced internally in AWS (no test case provided), but
apparently it is very easy to reproduce simply by measuring networking
performance.
[Fix]
AWS worked internally and found that the regression has been
introduced by:
a337531b942b ("tcp: up initial rmem to 128KB and SYN rwin to around
64KB")
To solve the problem we need to apply the following upstream commit
that explicitly fixes the problem introduced by the commit above:
33ae7b5bb841 ("tcp: select sane initial rcvq_space.space for big
MSS")
[Regression potential]
Upstream fix that is only affecting the initial TCP buffer space and
allows the TCP window size to be dynamically increased, basically
restoring the previous (correct) behavior, so regression potential is
minimal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1910200/+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 1910200] Re: aws: network performance regression due to initial TCP receive buffer size change
This bug was fixed in the package linux-aws - 4.15.0-1093.99
---
linux-aws (4.15.0-1093.99) bionic; urgency=medium
* bionic/linux-aws: 4.15.0-1093.99 -proposed tracker (LP: #1911275)
* aws: network performance regression due to initial TCP receive buffer size
change (LP: #1910200)
- tcp: select sane initial rcvq_space.space for big MSS
* arm64: prevent losing page dirty state (LP: #1908503)
- arm64: pgtable: Ensure dirty bit is preserved across pte_wrprotect()
* Disable Atari partition support for cloud kernels (LP: #1908264)
- [Config] Disable Atari partition support
* aws: xen-netfront: prevent potential error on hibernate (LP: #1906850)
- SAUCE: xen-netfront: prevent unnecessary close on hibernate
[ Ubuntu: 4.15.0-133.137 ]
* bionic/linux: 4.15.0-133.137 -proposed tracker (LP: #1911295)
* [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
context
- can: dev: __can_get_echo_skb(): fix real payload length return value for
RTR
frames
- can: can_create_echo_skb(): fix echo skb generation: always use
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback
is
on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
!CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
-
[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time
This bug was fixed in the package linux - 5.8.0-41.46 --- linux (5.8.0-41.46) groovy; urgency=medium * groovy/linux: 5.8.0-41.46 -proposed tracker (LP: #1912219) * Groovy update: upstream stable patchset 2020-12-17 (LP: #1908555) // nvme drive fails after some time (LP: #1910866) - Revert "nvme-pci: remove last_sq_tail" * initramfs unpacking failed (LP: #1835660) - SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around initrds. * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME -- Kleber Sacilotto de Souza Mon, 18 Jan 2021 17:01:08 +0100 ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120 -- 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/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Fix Released Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
[Kernel-packages] [Bug 1906875] Re: Bionic update: upstream stable patchset 2020-12-04
This bug was fixed in the package linux - 4.15.0-135.139
---
linux (4.15.0-135.139) bionic; urgency=medium
* bionic/linux: 4.15.0-135.139 -proposed tracker (LP: #1912223)
* [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
context
- can: dev: __can_get_echo_skb(): fix real payload length return value for
RTR
frames
- can: can_create_echo_skb(): fix echo skb generation: always use
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback
is
on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
!CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
- drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
- pinctrl: amd: use higher precision for 512 RtcClk
- pinctrl: amd: fix incorrect way to disable debounce filter
- swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
- IPv6: Set SIT tunnel hard_header_len to zero
- net/af_iucv: fix null pointer dereference on shutdown
- net/x25: Fix null-ptr-deref in x25_connect
- vrf: Fix fast path output packet handling with async Netfilter rules
- r8169: fix potential skb double free in an error path
- net: Update window_clamp if SOCK_RCVBUF is set
- random32: make prandom_u32() output unpredictable
[Kernel-packages] [Bug 1903596] Re: stack trace in kernel
This bug was fixed in the package linux - 4.15.0-135.139
---
linux (4.15.0-135.139) bionic; urgency=medium
* bionic/linux: 4.15.0-135.139 -proposed tracker (LP: #1912223)
* [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
context
- can: dev: __can_get_echo_skb(): fix real payload length return value for
RTR
frames
- can: can_create_echo_skb(): fix echo skb generation: always use
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback
is
on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
!CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
- drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
- pinctrl: amd: use higher precision for 512 RtcClk
- pinctrl: amd: fix incorrect way to disable debounce filter
- swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
- IPv6: Set SIT tunnel hard_header_len to zero
- net/af_iucv: fix null pointer dereference on shutdown
- net/x25: Fix null-ptr-deref in x25_connect
- vrf: Fix fast path output packet handling with async Netfilter rules
- r8169: fix potential skb double free in an error path
- net: Update window_clamp if SOCK_RCVBUF is set
- random32: make prandom_u32() output unpredictable
[Kernel-packages] [Bug 1906128] Re: Touchpad not detected on ByteSpeed C15B laptop
This bug was fixed in the package linux - 4.15.0-135.139
---
linux (4.15.0-135.139) bionic; urgency=medium
* bionic/linux: 4.15.0-135.139 -proposed tracker (LP: #1912223)
* [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
context
- can: dev: __can_get_echo_skb(): fix real payload length return value for
RTR
frames
- can: can_create_echo_skb(): fix echo skb generation: always use
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback
is
on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
!CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
- drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
- pinctrl: amd: use higher precision for 512 RtcClk
- pinctrl: amd: fix incorrect way to disable debounce filter
- swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
- IPv6: Set SIT tunnel hard_header_len to zero
- net/af_iucv: fix null pointer dereference on shutdown
- net/x25: Fix null-ptr-deref in x25_connect
- vrf: Fix fast path output packet handling with async Netfilter rules
- r8169: fix potential skb double free in an error path
- net: Update window_clamp if SOCK_RCVBUF is set
- random32: make prandom_u32() output unpredictable
[Kernel-packages] [Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM
This bug was fixed in the package linux - 4.15.0-135.139
---
linux (4.15.0-135.139) bionic; urgency=medium
* bionic/linux: 4.15.0-135.139 -proposed tracker (LP: #1912223)
* [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
context
- can: dev: __can_get_echo_skb(): fix real payload length return value for
RTR
frames
- can: can_create_echo_skb(): fix echo skb generation: always use
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback
is
on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
!CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
- drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
- pinctrl: amd: use higher precision for 512 RtcClk
- pinctrl: amd: fix incorrect way to disable debounce filter
- swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
- IPv6: Set SIT tunnel hard_header_len to zero
- net/af_iucv: fix null pointer dereference on shutdown
- net/x25: Fix null-ptr-deref in x25_connect
- vrf: Fix fast path output packet handling with async Netfilter rules
- r8169: fix potential skb double free in an error path
- net: Update window_clamp if SOCK_RCVBUF is set
- random32: make prandom_u32() output unpredictable
[Kernel-packages] [Bug 1908503] Re: arm64: prevent losing page dirty state
This bug was fixed in the package linux-aws - 4.15.0-1093.99
---
linux-aws (4.15.0-1093.99) bionic; urgency=medium
* bionic/linux-aws: 4.15.0-1093.99 -proposed tracker (LP: #1911275)
* aws: network performance regression due to initial TCP receive buffer size
change (LP: #1910200)
- tcp: select sane initial rcvq_space.space for big MSS
* arm64: prevent losing page dirty state (LP: #1908503)
- arm64: pgtable: Ensure dirty bit is preserved across pte_wrprotect()
* Disable Atari partition support for cloud kernels (LP: #1908264)
- [Config] Disable Atari partition support
* aws: xen-netfront: prevent potential error on hibernate (LP: #1906850)
- SAUCE: xen-netfront: prevent unnecessary close on hibernate
[ Ubuntu: 4.15.0-133.137 ]
* bionic/linux: 4.15.0-133.137 -proposed tracker (LP: #1911295)
* [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
context
- can: dev: __can_get_echo_skb(): fix real payload length return value for
RTR
frames
- can: can_create_echo_skb(): fix echo skb generation: always use
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback
is
on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
!CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
-
[Kernel-packages] [Bug 1908219] Re: [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors config:
This bug was fixed in the package linux - 4.15.0-135.139
---
linux (4.15.0-135.139) bionic; urgency=medium
* bionic/linux: 4.15.0-135.139 -proposed tracker (LP: #1912223)
* [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (LP: #1908219)
- qxl: remove qxl_io_log()
- qxl: move qxl_send_monitors_config()
- qxl: hook monitors_config updates into crtc, not encoder.
* Touchpad not detected on ByteSpeed C15B laptop (LP: #1906128)
- Input: i8042 - add ByteSpeed touchpad to noloop table
* vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 /
B-oracle-4.15 / X-KVM / B-KVM (LP: #1872401)
- KVM: nVMX: Always reflect #NM VM-exits to L1
* stack trace in kernel (LP: #1903596)
- net: napi: remove useless stack trace
* CVE-2020-2
- [Config]: Set CONFIG_PPC_RTAS_FILTER
* Bionic update: upstream stable patchset 2020-12-04 (LP: #1906875)
- regulator: defer probe when trying to get voltage from unresolved supply
- ring-buffer: Fix recursion protection transitions between interrupt
context
- time: Prevent undefined behaviour in timespec64_to_ns()
- nbd: don't update block size after device is started
- btrfs: sysfs: init devices outside of the chunk_mutex
- btrfs: reschedule when cloning lots of extents
- genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
- hv_balloon: disable warning when floor reached
- net: xfrm: fix a race condition during allocing spi
- perf tools: Add missing swap for ino_generation
- ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
- can: rx-offload: don't call kfree_skb() from IRQ context
- can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ
context
- can: dev: __can_get_echo_skb(): fix real payload length return value for
RTR
frames
- can: can_create_echo_skb(): fix echo skb generation: always use
skb_clone()
- can: peak_usb: add range checking in decode operations
- can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
- can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback
is
on
- xfs: flush new eof page on truncate to avoid post-eof corruption
- Btrfs: fix missing error return if writeback for extent buffer never
started
- ath9k_htc: Use appropriate rs_datalen type
- usb: gadget: goku_udc: fix potential crashes in probe
- gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
- gfs2: Add missing truncate_inode_pages_final for sd_aspace
- gfs2: check for live vs. read-only file system in gfs2_fitrim
- scsi: hpsa: Fix memory leak in hpsa_init_one()
- drm/amdgpu: perform srbm soft reset always on SDMA resume
- mac80211: fix use of skb payload instead of header
- cfg80211: regulatory: Fix inconsistent format argument
- scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
- iommu/amd: Increase interrupt remapping table limit to 512 entries
- pinctrl: intel: Set default bias in case no particular value given
- ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
- pinctrl: aspeed: Fix GPI only function problem.
- nbd: fix a block_device refcount leak in nbd_release
- xfs: fix flags argument to rmap lookup when converting shared file rmaps
- xfs: fix rmap key and record comparison functions
- xfs: fix a missing unlock on error in xfs_fs_map_blocks
- of/address: Fix of_node memory leak in of_dma_is_coherent
- cosa: Add missing kfree in error path of cosa_write
- perf: Fix get_recursion_context()
- ext4: correctly report "not supported" for {usr,grp}jquota when
!CONFIG_QUOTA
- ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
- thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
- uio: Fix use-after-free in uio_unregister_device()
- usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
- mei: protect mei_cl_mtu from null dereference
- futex: Don't enable IRQs unconditionally in put_pi_state()
- ocfs2: initialize ip_next_orphan
- selinux: Fix error return code in sel_ib_pkey_sid_slow()
- don't dump the threads that had been already exiting when zapped.
- drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
- pinctrl: amd: use higher precision for 512 RtcClk
- pinctrl: amd: fix incorrect way to disable debounce filter
- swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
- IPv6: Set SIT tunnel hard_header_len to zero
- net/af_iucv: fix null pointer dereference on shutdown
- net/x25: Fix null-ptr-deref in x25_connect
- vrf: Fix fast path output packet handling with async Netfilter rules
- r8169: fix potential skb double free in an error path
- net: Update window_clamp if SOCK_RCVBUF is set
- random32: make prandom_u32() output unpredictable
[Kernel-packages] [Bug 1913200] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-460-server into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-460-server/460.32.03-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: New Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Introduce the new NVIDIA 460-server series and update the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460-server == * Initial release: - Added support for the following GPUs: NVIDIA A40 NVIDIA RTX A6000 - Added support for CUDA 11.2. == 460 == * New upstream release: - Added support for the following GPUs: GeForce RTX 3080 Laptop GPU GeForce RTX 3070 Laptop GPU GeForce RTX 3060 Laptop GPU GeForce GT 1010 - Updated the NVIDIA driver to restore functionality of some features, including runtime power management, hotplugging audio-capable display devices, and S0ix-based system suspend, with recent kernels such as Linux 5.10. - Fixed a bug that caused bindless texture samplers to be incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS limit. - Fixed a bug that could cause the GPU to hang when attempting to perform link training on an HDMI 2.1 Fixed Rate Link (FRL) display, while the display is powered off. - Fixed a bug that could intermittently cause NvFBC applications to fail with the error message "Unable to send exported fds". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+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 1913200] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-460-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-460-server/460.32.03-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: New Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Introduce the new NVIDIA 460-server series and update the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460-server == * Initial release: - Added support for the following GPUs: NVIDIA A40 NVIDIA RTX A6000 - Added support for CUDA 11.2. == 460 == * New upstream release: - Added support for the following GPUs: GeForce RTX 3080 Laptop GPU GeForce RTX 3070 Laptop GPU GeForce RTX 3060 Laptop GPU GeForce GT 1010 - Updated the NVIDIA driver to restore functionality of some features, including runtime power management, hotplugging audio-capable display devices, and S0ix-based system suspend, with recent kernels such as Linux 5.10. - Fixed a bug that caused bindless texture samplers to be incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS limit. - Fixed a bug that could cause the GPU to hang when attempting to perform link training on an HDMI 2.1 Fixed Rate Link (FRL) display, while the display is powered off. - Fixed a bug that could intermittently cause NvFBC applications to fail with the error message "Unable to send exported fds". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+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 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-460-server into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-460-server/460.32.03-0ubuntu0.20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: nvidia-graphics-drivers-460-server (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 in Ubuntu. https://bugs.launchpad.net/bugs/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: New Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Introduce the new NVIDIA 460-server series and update the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460-server == * Initial release: - Added support for the following GPUs: NVIDIA A40 NVIDIA RTX A6000 - Added support for CUDA 11.2. == 460 == * New upstream release: - Added support for the following GPUs: GeForce RTX 3080 Laptop GPU GeForce RTX 3070 Laptop GPU GeForce RTX 3060 Laptop GPU GeForce GT 1010 - Updated the NVIDIA driver to restore functionality of some features, including runtime power management, hotplugging audio-capable display devices, and S0ix-based system suspend, with recent kernels such as Linux 5.10. - Fixed a bug that caused bindless texture samplers to be incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS limit. - Fixed a bug that could cause the GPU to hang when attempting to perform link training on an HDMI 2.1 Fixed Rate Link (FRL) display, while the display is powered off. - Fixed a bug that could intermittently cause NvFBC applications to fail with the error message "Unable to send exported fds". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series
** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Bionic) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Focal) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Focal) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Groovy) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Groovy) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Groovy) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Focal) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: New Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Introduce the new NVIDIA 460-server series and update the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460-server == * Initial release: - Added support for the following GPUs: NVIDIA A40 NVIDIA RTX A6000 - Added support for CUDA 11.2. == 460 == * New upstream release: - Added support for the following GPUs: GeForce RTX 3080 Laptop GPU GeForce RTX 3070 Laptop GPU GeForce RTX 3060 Laptop GPU GeForce GT 1010 - Updated the NVIDIA driver to restore functionality of some features, including runtime power management, hotplugging
[Kernel-packages] [Bug 1913200] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-460 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-460/460.39-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: In Progress Status in linux source package in Groovy: New Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: In Progress Bug description: Introduce the new NVIDIA 460-server series and update the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460-server == * Initial release: - Added support for the following GPUs: NVIDIA A40 NVIDIA RTX A6000 - Added support for CUDA 11.2. == 460 == * New upstream release: - Added support for the following GPUs: GeForce RTX 3080 Laptop GPU GeForce RTX 3070 Laptop GPU GeForce RTX 3060 Laptop GPU GeForce GT 1010 - Updated the NVIDIA driver to restore functionality of some features, including runtime power management, hotplugging audio-capable display devices, and S0ix-based system suspend, with recent kernels such as Linux 5.10. - Fixed a bug that caused bindless texture samplers to be incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS limit. - Fixed a bug that could cause the GPU to hang when attempting to perform link training on an HDMI 2.1 Fixed Rate Link (FRL) display, while the display is powered off. - Fixed a bug that could intermittently cause NvFBC applications to fail with the error message "Unable to send exported fds". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+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 1913200] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-460 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-460/460.39-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-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/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: In Progress Status in linux source package in Groovy: New Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: In Progress Bug description: Introduce the new NVIDIA 460-server series and update the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460-server == * Initial release: - Added support for the following GPUs: NVIDIA A40 NVIDIA RTX A6000 - Added support for CUDA 11.2. == 460 == * New upstream release: - Added support for the following GPUs: GeForce RTX 3080 Laptop GPU GeForce RTX 3070 Laptop GPU GeForce RTX 3060 Laptop GPU GeForce GT 1010 - Updated the NVIDIA driver to restore functionality of some features, including runtime power management, hotplugging audio-capable display devices, and S0ix-based system suspend, with recent kernels such as Linux 5.10. - Fixed a bug that caused bindless texture samplers to be incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS limit. - Fixed a bug that could cause the GPU to hang when attempting to perform link training on an HDMI 2.1 Fixed Rate Link (FRL) display, while the display is powered off. - Fixed a bug that could intermittently cause NvFBC applications to fail with the error message "Unable to send exported fds". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+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 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-460 into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-460/460.39-0ubuntu0.20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Focal) Status: New => Fix Committed ** 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/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: In Progress Status in linux source package in Groovy: New Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: In Progress Bug description: Introduce the new NVIDIA 460-server series and update the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460-server == * Initial release: - Added support for the following GPUs: NVIDIA A40 NVIDIA RTX A6000 - Added support for CUDA 11.2. == 460 == * New upstream release: - Added support for the following GPUs: GeForce RTX 3080 Laptop GPU GeForce RTX 3070 Laptop GPU GeForce RTX 3060 Laptop GPU GeForce GT 1010 - Updated the NVIDIA driver to restore functionality of some features, including runtime power management, hotplugging audio-capable display devices, and S0ix-based system suspend, with recent kernels such as Linux 5.10. - Fixed a bug that caused bindless texture samplers to be incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS limit. - Fixed a bug that could cause the GPU to hang when attempting to perform link training on an HDMI 2.1 Fixed Rate Link (FRL) display, while the display is powered off. - Fixed a bug that could intermittently cause NvFBC applications to fail with the error message "Unable to send exported fds". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series
** Also affects: nvidia-graphics-drivers-460-server (Ubuntu) Importance: Undecided Status: New ** Package changed: nvidia-graphics-drivers-450-server (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460 (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460-server (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460-server (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450-server in Ubuntu. https://bugs.launchpad.net/bugs/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: In Progress Status in linux source package in Focal: New Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: In Progress Status in linux source package in Groovy: New Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: New Bug description: Introduce the new NVIDIA 460-server series and update the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460-server == * Initial release: - Added support for the following GPUs: NVIDIA A40 NVIDIA RTX A6000 - Added support for CUDA 11.2. == 460 == * New upstream release: - Added support for the following GPUs: GeForce RTX 3080 Laptop GPU GeForce RTX 3070 Laptop GPU GeForce RTX 3060 Laptop GPU GeForce GT 1010 - Updated the NVIDIA driver to restore functionality of some features, including runtime power management, hotplugging audio-capable display devices, and S0ix-based system suspend, with recent kernels such as Linux 5.10. - Fixed a bug that caused bindless texture samplers to be incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS limit. - Fixed a bug that could cause the GPU to hang when attempting to perform link training on an HDMI 2.1 Fixed Rate Link (FRL) display, while the display is powered off. - Fixed a bug that could intermittently cause NvFBC applications to fail with the error message "Unable to send exported fds". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+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 1870189] Re: initramfs does not get loaded
Is there any update on this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
Confirmed
Status in grub2 package in Ubuntu:
Won't Fix
Status in linux-azure package in Ubuntu:
Invalid
Status in livecd-rootfs package in Ubuntu:
Triaged
Status in grub2 source package in Focal:
Confirmed
Status in linux-azure source package in Focal:
Invalid
Status in livecd-rootfs source package in Focal:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+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 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
Hello bugproxy, or anyone else affected,
Accepted s390-tools into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/s390-tools/2.12.0-0ubuntu3.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: s390-tools (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags removed: verification-done-focal
** Tags added: verification-needed 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/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Release Notes for Ubuntu:
New
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
** Attachment added: "dmesg.rc4+" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5457093/+files/dmesg.rc4+ -- 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/1912057 Title: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA Status in linux package in Ubuntu: Incomplete Bug description: After boot the idle power consumption is around 2.3 W but after suspend it is 4.7 W. The measurement is 5-10 min after boot/resume - looking at "top" to see system was idle. This is consistent - I have tried more that 10 times. BIOS is updated to latest version. I have checked power consumption with external meter - and confirmed that it is higher. I have attached output of: sudo powertop -t 60 -r --html=before.html (and after) I have noticed that Package C-state 6 is reached before suspend but not after. I expect that idle power consumption after suspend should be the same as before. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-38-generic 5.8.0-38.43 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hjh1448 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 15:49:32 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-01-03 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425JA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425JA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425JA_UX425JA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+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
Re: [Kernel-packages] [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
The workaround is to unload the thermal kernel module that overreacts to short-lived temperature changes due to CPU load while charging. sudo rmmod int3403_thermal On Wed, Dec 2, 2020, 01:21 Magdalena S <1873...@bugs.launchpad.net> wrote: > I also have the same issue with the Lenovo Yoga C940 regarding the > regular thermal shutdowns on Manjaro 20.2. They occur mainly during > charging and in particular during video conferences (Zoom, etc.), which > is really annoying. I have also tried different linux kernels (5.4 - > 5.10) but the shutdowns remained. This way, the lenovo yoga notebook is > simply not serviceable under Linux. > > If there is any solution for that I would be really thankful. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1873083 > > Title: > Lenovo Yoga C940 frequently does thermal shutdown > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Confirmed Status in Gentoo Linux: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+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
Re: [Kernel-packages] [Bug 1912898] Re: Last few kernel updates, video crashes, system freezes
Thanks Daniel,
1) I uninstalled xserver-xorg-video-intel. No change.
2) I noticed that. 18.04 and Debian works fine on same machine.
Using a recent installation of 20.04 desktop with updates but little to
no changes from stock:
5.4.0-42-generic WORKS FINE on /dev/sda1:
5.8.0-38-generic on /dev/sda1 boots to desktop, cursor OK, but 1st or
2nd user action immediately renders system unusable. Freezes, various
screen flashing, reboots or reverts to user login.
Verified the above multiple times.
What else can I do to help?
Thanks!
... Duane Shults
On 1/25/21 12:17 AM, Daniel van Vugt wrote:
> Thanks for the bug report. A few thoughts:
>
> 1. xserver-xorg-video-intel is old and not supported. Please uninstall
> it to make sure you're using the newer default driver ('modesetting').
>
> 2. Your kernel log shows constant hardware errors from the 'Intel
> Corporation 8 Series PCI Express Root Port 3':
>
> [ 69.485800] pcieport :00:1c.0: AER: Corrected error received:
> :00:1c.0
> [ 69.485812] pcieport :00:1c.0: AER: PCIe Bus Error:
> severity=Corrected, type=Data Link Layer, (Transmitter ID)
> [ 69.485817] pcieport :00:1c.0: AER: device [8086:9c14] error
> status/mask=1000/2000
> [ 69.485821] pcieport :00:1c.0: AER:[12] Timeout
>
> I don't know if that's a real hardware problem or a kernel bug. So
> please try some older kernels like: https://kernel.ubuntu.com/~kernel-
> ppa/mainline/v5.4.92/
>
> 3. Please check the system for non-kernel crashes using these
> instructions:
> https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
>
>
> ** Summary changed:
>
> - Last few kernel updates, video crashes, system freezes
> + [i915] Last few kernel updates, video crashes, system freezes
>
> ** Package changed: xorg (Ubuntu) => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912898
Title:
[i915] Last few kernel updates, video crashes, system freezes
Status in linux package in Ubuntu:
Incomplete
Bug description:
1) Chromebox 2955U trying to run Ubuntu 20.04 with updates. Has been running
Ubuntu for many years.
2) Video seems to crash when ANY program, menu item or terminal is started
after reboot. Flashing screen fields, boxes, menus. Cursor freezes or stutters.
3) 18.02 ran and runs fine in other partitions.
4) Latest Debian runs fine in other partiton.
5) Ubuntu 20.04 runs fine when running directly from USB flashdrive. This is
really wierd.
6) Occurs immediately after a fresh installation of 20.04 in any partition.
Verified sha256sums.
7) Can make system usable with nomodeset in grub linux line but runs very
slow.
8) Tried "sudo apt-get install xserver-xorg-video-intel". ... Already running
latest.
9) Memtest86 ran 2 full iterations, no errors.
10) Seems like I verified an older kernel worked fine, but an "autoremove"
removed it/them.
11) I've been fighting this for a few months now.
Thank you for any support you can give...
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 23 08:41:43 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06]
(rev 09) (prog-if 00 [VGA controller])
Subsystem: Google, Inc. Haswell-ULT Integrated Graphics Controller
[1ae0:c000]
InstallationDate: Installed on 2020-10-03 (111 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 13d3:3393 IMC Networks
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Google Panther
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic
root=UUID=3124be5d-3014-4ee1-ac5b-8c48babfde15 ro quiet splash nomodeset
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2014
dmi.bios.release: 4.0
dmi.bios.vendor: coreboot
dmi.bios.version: 4.0-7565-gc6e3a3a-dirty
dmi.board.name: Panther
dmi.board.vendor: Google
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Google
[Kernel-packages] [Bug 1913187] Re: iproute2 segfaults when filtering sockets
$ git-ubuntu tag --upload
$ git describe
upload/4.15.0-2ubuntu1.3
$ git push pkg upload/4.15.0-2ubuntu1.3
Counting objects: 11, done.
Delta compression using up to 24 threads.
Compressing objects: 100% (11/11), done.
Writing objects: 100% (11/11), 2.07 KiB | 176.00 KiB/s, done.
Total 11 (delta 7), reused 0 (delta 0)
To ssh://git.launchpad.net/ubuntu/+source/iproute2
* [new tag] upload/4.15.0-2ubuntu1.3 -> upload/4.15.0-2ubuntu1.3
$ debdiff *.dsc | diffstat
changelog | 7 +++
patches/lp1913187-ss-fix-NULL-dereference-when-rendering.patch | 40
patches/series | 1 +
3 files changed, 48 insertions(+)
[rafaeldtinoco@iproute2issue ubuntu]$ dput ubuntu
./iproute2_4.15.0-2ubuntu1.3_source.changes
Checking signature on .changes
gpg: ./iproute2_4.15.0-2ubuntu1.3_source.changes: Valid signature from
A93E0E0AD83C0D0F
Checking signature on .dsc
gpg: ./iproute2_4.15.0-2ubuntu1.3.dsc: Valid signature from A93E0E0AD83C0D0F
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading iproute2_4.15.0-2ubuntu1.3.dsc: done.
Uploading iproute2_4.15.0-2ubuntu1.3.debian.tar.xz: done.
Uploading iproute2_4.15.0-2ubuntu1.3_source.buildinfo: done.
Uploading iproute2_4.15.0-2ubuntu1.3_source.changes: done.
Successfully uploaded packages.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1913187
Title:
iproute2 segfaults when filtering sockets
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Bionic:
Confirmed
Bug description:
[Impact]
* The ss tool crashes when a query returns no results (seg fault)
[Test Case]
* $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1
Segmentation fault
* PPA with the fix:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187
[Where problems could occur]
* The ss tool is impacted and it has its code changed for the fix.
* The fix is a clean cherry-pick and straightforward (moving
declaration after a NULL check).
[Other Info]
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1840043] Re: bcache: Performance degradation when querying priority_stats
@pponnuvel stat(2) doesn't perform a read(2) on the file, so it won't
call the show() method for priority_stats (which was the problematic
call for this specific sysfs attribute).
In any case, this should be fixed in all supported Ubuntu series, so
even read(2) shouldn't be an issue anymore. Please let us know if you
see any performance regressions related to this change!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1840043
Title:
bcache: Performance degradation when querying priority_stats
Status in Linux:
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 Released
Status in linux source package in Disco:
Fix Released
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
Querying bcache's priority_stats attribute in sysfs causes severe performance
degradation for read/write workloads and occasional system stalls
[Test Case]
Note: As the sorting step has the most noticeable performance impact, the
test case below pins a workload and the sysfs query to the same CPU. CPU
contention issues still occur without any pinning, this just removes the
scheduling factor of landing in different CPUs and affecting different tasks.
1) Start a read/write workload on the bcache device with e.g. fio or dd,
pinned to a certain CPU:
# taskset 0x10 dd if=/dev/zero of=/dev/bcache0 bs=4k status=progress
2) Start a sysfs query loop for the priority_stats attribute pinned to the
same CPU:
# for i in {1..10}; do taskset 0x10 cat
/sys/fs/bcache/*/cache0/priority_stats > /dev/null; done
3) Monitor the read/write workload for any performance impact
[Fix]
To fix CPU contention and performance impact, a cond_resched() call is
introduced in the priority_stats sort comparison.
[Regression Potential]
Regression potential is low, as the change is confined to the priority_stats
sysfs query. In cases where frequent queries to bcache priority_stats take
place (e.g. node_exporter), the impact should be more noticeable as those could
now take a bit longer to complete. A regression due to this patch would most
likely show up as a performance degradation in bcache-focused workloads.
--
[Description]
In the latest bcache drivers, there's a sysfs attribute that calculates
bucket priority statistics in /sys/fs/bcache/*/cache0/priority_stats. Querying
this file has a big performance impact on tasks that run in the same CPU, and
also affects read/write performance of the bcache device itself.
This is due to the way the driver calculates the stats: the bcache
buckets are locked and iterated through, collecting information about
each individual bucket. An array of nbucket elements is constructed
and sorted afterwards, which can cause very high CPU contention in
cases of larger bcache setups.
From our tests, the sorting step of the priority_stats query causes
the most expressive performance reduction, as it can hinder tasks that
are not even doing any bcache IO. If a task is "unlucky" to be
scheduled in the same CPU as the sysfs query, its performance will be
harshly reduced as both compete for CPU time. We've had users report
systems stalls of up to ~6s due to this, as a result from monitoring
tools that query the priority_stats periodically (e.g. Prometheus Node
Exporter from [0]). These system stalls have triggered several other
issues such as ceph-mon re-elections, problems in percona-cluster and
general network stalls, so the impact is not isolated to bcache IO
workloads.
An example benchmark can be seen in [1], where the read performance on
a bcache device suffered quite heavily (going from ~40k IOPS to ~4k
IOPS due to priority_stats). Other comparison charts are found under
[2].
[0] https://github.com/prometheus/node_exporter
[1]
https://people.canonical.com/~halves/priority_stats/read/4k-iops-2Dsmooth.png
[2] https://people.canonical.com/~halves/priority_stats/
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1840043/+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 1876632] Re: [nvidia] Corrupted shell textures when switching users or resuming from suspend
I've seen the same issue with focal and System76 Stable PPA's 460.32.03-1pop0~1611601564~20.04~11a4029~dev nvidia packaging. All text was corrupted after waking from suspend but it has only occurred once so far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+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 1905211] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed focal fossa in kernel v5.9
Also reported here by me: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899866 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1905211 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed focal fossa in kernel v5.9 Status in bcmwl package in Ubuntu: New Bug description: Impact The DKMS package won't work with new kernel v5.9 on focal fossa. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 Uname: Linux 5.9.0-050900-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.12 AptOrdering: bcmwl-kernel-source:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 17:23:01 2020 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-11-16 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1905211/+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 1899866] Re: bcmwl-6.30.223.271+bdcom on kernel 5.9.0-050900-generic fails to install module
I can also confirm that the bcmwl package will not install with a 5.10
kernel either.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1899866
Title:
bcmwl-6.30.223.271+bdcom on kernel 5.9.0-050900-generic fails to
install module
Status in bcmwl package in Ubuntu:
Confirmed
Bug description:
When installing the 5.9 kernel with bcmwl6.30.223.271+bdcom package on
focal, the process fails to build the module.
bcmwl package: 6.30.223.271+bdcom-0ubuntu5
Below is the build log:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.9.0-050900-generic
(x86_64)
Mon 12 Oct 2020 02:45:20 PM MDT
make: Entering directory '/usr/src/linux-headers-5.9.0-050900-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_ioctl’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:1654:6:
error: implicit declaration of function ‘segment_eq’
[-Werror=implicit-function-declaration]
1654 | if (segment_eq(get_fs(), KERNEL_DS))
| ^~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:283:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [Makefile:1784: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build] Error
2
make: Leaving directory '/usr/src/linux-headers-5.9.0-050900-generic'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899866/+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 1913309] Re: Error upgrading Ubuntu armhf from 18.04 to 20.04 on RPI4 - package linux-firmware 1.187.9 failed to install/upgrade
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1913309 Title: Error upgrading Ubuntu armhf from 18.04 to 20.04 on RPI4 - package linux-firmware 1.187.9 failed to install/upgrade Status in linux-firmware package in Ubuntu: New Bug description: Error upgrading Ubuntu armhf from 18.04 to 20.04 on RPI4 - package linux-firmware 1.187.9 failed to install/upgrade: il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 This should be the most relevant part: -- Configurazione di linux-firmware (1.187.9)... update-initramfs: Generating /boot/initrd.img-5.3.0-1008-raspi2 Using DTB: bcm2711-rpi-4-b.dtb Installing /lib/firmware/5.3.0-1008-raspi2/device-tree/bcm2711-rpi-4-b.dtb into /boot/dtbs/5.3.0-1008-raspi2/./bcm2711-rpi-4-b.dtb Installing new bcm2711-rpi-4-b.dtb. Ignoring old or unknown version 5.3.0-1008-raspi2 (latest is 5.4.0-1028-raspi) update-initramfs: Generating /boot/initrd.img-4.15.0-1073-raspi2 Using DTB: bcm2711-rpi-4-b.dtb Couldn't find DTB bcm2711-rpi-4-b.dtb on the following paths: /etc/flash-kernel/dtbs /usr/lib/linux-image-4.15.0-1073-raspi2 /lib/firmware/4.15.0-1073-raspi2/device-tree/ Installing into /boot/dtbs/4.15.0-1073-raspi2/./bcm2711-rpi-4-b.dtb cp: cannot stat '': No such file or directory run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: errore nell'elaborare il pacchetto linux-firmware (--configure): il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 -- ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.9 Uname: Linux 5.10.9-v7l+ armv7l ApportVersion: 2.20.11-0ubuntu27 Architecture: armhf CasperMD5CheckResult: skip Date: Tue Jan 26 14:40:00 2021 Dependencies: ErrorMessage: il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: linux-firmware Title: package linux-firmware 1.187.9 failed to install/upgrade: il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to focal on 2021-01-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1913309/+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 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
Thanks! Can you please also do the same for the kernel in comment #14? -- 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/1912057 Title: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA Status in linux package in Ubuntu: Incomplete Bug description: After boot the idle power consumption is around 2.3 W but after suspend it is 4.7 W. The measurement is 5-10 min after boot/resume - looking at "top" to see system was idle. This is consistent - I have tried more that 10 times. BIOS is updated to latest version. I have checked power consumption with external meter - and confirmed that it is higher. I have attached output of: sudo powertop -t 60 -r --html=before.html (and after) I have noticed that Package C-state 6 is reached before suspend but not after. I expect that idle power consumption after suspend should be the same as before. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-38-generic 5.8.0-38.43 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hjh1448 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 15:49:32 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-01-03 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425JA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425JA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425JA_UX425JA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+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 1913309] [NEW] Error upgrading Ubuntu armhf from 18.04 to 20.04 on RPI4 - package linux-firmware 1.187.9 failed to install/upgrade
Public bug reported: Error upgrading Ubuntu armhf from 18.04 to 20.04 on RPI4 - package linux-firmware 1.187.9 failed to install/upgrade: il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 This should be the most relevant part: -- Configurazione di linux-firmware (1.187.9)... update-initramfs: Generating /boot/initrd.img-5.3.0-1008-raspi2 Using DTB: bcm2711-rpi-4-b.dtb Installing /lib/firmware/5.3.0-1008-raspi2/device-tree/bcm2711-rpi-4-b.dtb into /boot/dtbs/5.3.0-1008-raspi2/./bcm2711-rpi-4-b.dtb Installing new bcm2711-rpi-4-b.dtb. Ignoring old or unknown version 5.3.0-1008-raspi2 (latest is 5.4.0-1028-raspi) update-initramfs: Generating /boot/initrd.img-4.15.0-1073-raspi2 Using DTB: bcm2711-rpi-4-b.dtb Couldn't find DTB bcm2711-rpi-4-b.dtb on the following paths: /etc/flash-kernel/dtbs /usr/lib/linux-image-4.15.0-1073-raspi2 /lib/firmware/4.15.0-1073-raspi2/device-tree/ Installing into /boot/dtbs/4.15.0-1073-raspi2/./bcm2711-rpi-4-b.dtb cp: cannot stat '': No such file or directory run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: errore nell'elaborare il pacchetto linux-firmware (--configure): il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 -- ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.9 Uname: Linux 5.10.9-v7l+ armv7l ApportVersion: 2.20.11-0ubuntu27 Architecture: armhf CasperMD5CheckResult: skip Date: Tue Jan 26 14:40:00 2021 Dependencies: ErrorMessage: il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: linux-firmware Title: package linux-firmware 1.187.9 failed to install/upgrade: il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to focal on 2021-01-26 (0 days ago) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf focal package-from-proposed ** Description changed: Error upgrading Ubuntu armhf from 18.04 to 20.04 on RPI4 - package linux-firmware 1.187.9 failed to install/upgrade: il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 + + + This should be the most relevant part: + -- + Configurazione di linux-firmware (1.187.9)... + update-initramfs: Generating /boot/initrd.img-5.3.0-1008-raspi2 + Using DTB: bcm2711-rpi-4-b.dtb + Installing /lib/firmware/5.3.0-1008-raspi2/device-tree/bcm2711-rpi-4-b.dtb into /boot/dtbs/5.3.0-1008-raspi2/./bcm2711-rpi-4-b.dtb + Installing new bcm2711-rpi-4-b.dtb. + Ignoring old or unknown version 5.3.0-1008-raspi2 (latest is 5.4.0-1028-raspi) + update-initramfs: Generating /boot/initrd.img-4.15.0-1073-raspi2 + Using DTB: bcm2711-rpi-4-b.dtb + Couldn't find DTB bcm2711-rpi-4-b.dtb on the following paths: /etc/flash-kernel/dtbs /usr/lib/linux-image-4.15.0-1073-raspi2 /lib/firmware/4.15.0-1073-raspi2/device-tree/ + Installing into /boot/dtbs/4.15.0-1073-raspi2/./bcm2711-rpi-4-b.dtb + cp: cannot stat '': No such file or directory + run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 + dpkg: errore nell'elaborare il pacchetto linux-firmware (--configure): + il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 + -- + ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.9 Uname: Linux 5.10.9-v7l+ armv7l ApportVersion: 2.20.11-0ubuntu27 Architecture: armhf CasperMD5CheckResult: skip Date: Tue Jan 26 14:40:00 2021 Dependencies: - + ErrorMessage: il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: - dpkg 1.19.7ubuntu3 - apt 2.0.2 + dpkg 1.19.7ubuntu3 + apt 2.0.2 SourcePackage: linux-firmware Title: package linux-firmware 1.187.9 failed to install/upgrade: il sottoprocesso installato pacchetto linux-firmware script post-installation ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to focal on 2021-01-26 (0 days ago) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to
[Kernel-packages] [Bug 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
No, linux is the correct package. And I just subscribe the sound maintainer to this bug. -- 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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+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
