[Kernel-packages] [Bug 1827912] Re: [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound
Update: After some unmeasured amount of time, for the first time since ubuntu install on this machine (2017), there is no crackling sound at any moment. -- 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/1827912 Title: [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound Status in linux package in Ubuntu: Incomplete Bug description: Issue: Audio Crackling Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though Testing: There is crackling coming from any speakers (headsets or brand-new speakers with no known issues). Crackling does not seem to be related to audio (it can occur even with sound turned off in the sound-control menu). (it does stop when power to speakers are removed) Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though. The screen being on, or connected made no difference though. No change based on keyboard or mouse. Fixes tried: https://wiki.ubuntu.com/Audio/PositionReporting ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.0.7-steamvr-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: andruid1668 F pulseaudio /dev/snd/controlC0: andruid1668 F pulseaudio /dev/snd/pcmC0D0p: andruid1668 F...m pulseaudio /dev/snd/controlC1: andruid1668 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 12:38:45 2019 InstallationDate: Installed on 2019-02-16 (78 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: May 06 12:22:43 Workstation-0 dbus-daemon[1113]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=1668 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="kernel") Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [All Series, Realtek ALC1150, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87I-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd11/26/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87I-DELUXE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-06T12:22:03.874818 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-16 (80 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.0.7-steamvr-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker friends lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827912] Re: [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound
apport information ** Tags added: apport-collected ** Description changed: Issue: Audio Crackling Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though Testing: There is crackling coming from any speakers (headsets or brand-new speakers with no known issues). Crackling does not seem to be related to audio (it can occur even with sound turned off in the sound-control menu). (it does stop when power to speakers are removed) Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though. The screen being on, or connected made no difference though. No change based on keyboard or mouse. Fixes tried: https://wiki.ubuntu.com/Audio/PositionReporting ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.0.7-steamvr-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: andruid1668 F pulseaudio /dev/snd/controlC0: andruid1668 F pulseaudio /dev/snd/pcmC0D0p: andruid1668 F...m pulseaudio /dev/snd/controlC1: andruid1668 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 12:38:45 2019 InstallationDate: Installed on 2019-02-16 (78 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: May 06 12:22:43 Workstation-0 dbus-daemon[1113]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=1668 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="kernel") Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [All Series, Realtek ALC1150, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87I-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd11/26/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87I-DELUXE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-06T12:22:03.874818 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-02-16 (80 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: bionic + Uname: Linux 5.0.7-steamvr-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker friends lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1827912/+attachment/5262204/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827912 Title: [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound Status in linux package in Ubuntu: Incomplete Bug description: Issue: Audio Crackling Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though Testing: There is crackling coming from any speakers (headsets or brand-new speakers with no known issues). Crackling does not seem to be related to audio (it can occur even with sound turned off in the sound-control menu). (it does stop when power to speakers are removed) Video play back and during games seems to be when
[Kernel-packages] [Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
Same issue here on dell xps 13. Last working kernel 5.0.0-36. Have tried up to 5.3.0-29 but not working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic). Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10): acpi=off dis_ucode_ldr disabling secure boot recovery mode making sure all packages are up to date I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?) I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system. Hardware Dell XPS 9550 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 91 structures occupying 5683 bytes. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.11.2 Release Date: 07/30/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.11 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: XPS 15 9550 Version: Not Specified Serial Number: 5QRHRF2 UUID: 4c4c4544-0051-5210-8048-b5c04f524632 Wake-up Type: Power Switch SKU Number: 06E4 Family: XPS Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0N7TVV Version: A01 Serial Number: /5QRHRF2/CN129636CS0026/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Dell Inc. Type: Laptop Lock: Not Present Version: Not Specified Serial Number: 5QRHRF2 Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Laptop Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB2 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0006, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSBC1 Internal Connector Type: None External Reference Designator: USB TYPEC External Connector Type: Access Bus (USB)
[Kernel-packages] [Bug 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Committed Bug description: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft DefaultDependencies=no After=systemd-remount-fs.service Before=shutdown.target cloud-init-local.service walinuxagent.service Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv The hv-kvp-daemon service is not currently part of the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.809s └─multi-user.target @10.723s └─ephemeral-disk-warning.service @10.538s +31ms └─cloud-config.service @8.249s +2.252s └─basic.target @8.044s └─sockets.target @8.019s └─snapd.socket @7.692s +264ms └─sysinit.target @6.719s └─cloud-init.service @5.803s +842ms └─networking.service @5.137s +612ms └─network-pre.target @5.074s └─cloud-init-local.service @2.257s +2.783s └─systemd-remount-fs.service @1.368s +656ms └─systemd-journald.socket @1.218s └─-.mount @649ms └─system.slice @653ms └─-.slice @649ms In an Azure VM, the current startup time of my test is: $ systemd-analyze Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s After making the suggested change, the startup time is similar: $ systemd-analyze Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.666s └─multi-user.target @10.636s └─ephemeral-disk-warning.service @10.556s +36ms └─cloud-config.service @8.423s +2.095s └─basic.target @8.124s └─sockets.target @8.101s └─lxd.socket @7.677s +326ms └─sysinit.target @6.755s └─cloud-init.service @5.814s +908ms └─networking.service @5.111s +651ms └─network-pre.target @5.087s └─cloud-init-local.service @2.345s +2.707s └─hv-kvp-daemon.service @2.316s └─systemd-remount-fs.service @1.253s +680ms └─system.slice @1.225s └─-.slice @650ms The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) by checking whether the system is executed in a virtualized environment and optionally test whether it is a specific implementation, in this case "microsoft" for Hyper-V. https://www.freedesktop.org/software/systemd/man/systemd-detect-virt.html# microsoft = Hyper-V, also known as Viridian or Windows Server Virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Committed Bug description: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft DefaultDependencies=no After=systemd-remount-fs.service Before=shutdown.target cloud-init-local.service walinuxagent.service Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv The hv-kvp-daemon service is not currently part of the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.809s └─multi-user.target @10.723s └─ephemeral-disk-warning.service @10.538s +31ms └─cloud-config.service @8.249s +2.252s └─basic.target @8.044s └─sockets.target @8.019s └─snapd.socket @7.692s +264ms └─sysinit.target @6.719s └─cloud-init.service @5.803s +842ms └─networking.service @5.137s +612ms └─network-pre.target @5.074s └─cloud-init-local.service @2.257s +2.783s └─systemd-remount-fs.service @1.368s +656ms └─systemd-journald.socket @1.218s └─-.mount @649ms └─system.slice @653ms └─-.slice @649ms In an Azure VM, the current startup time of my test is: $ systemd-analyze Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s After making the suggested change, the startup time is similar: $ systemd-analyze Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.666s └─multi-user.target @10.636s └─ephemeral-disk-warning.service @10.556s +36ms └─cloud-config.service @8.423s +2.095s └─basic.target @8.124s └─sockets.target @8.101s └─lxd.socket @7.677s +326ms └─sysinit.target @6.755s └─cloud-init.service @5.814s +908ms └─networking.service @5.111s +651ms └─network-pre.target @5.087s └─cloud-init-local.service @2.345s +2.707s └─hv-kvp-daemon.service @2.316s └─systemd-remount-fs.service @1.253s +680ms └─system.slice @1.225s └─-.slice @650ms The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) by checking whether the system is executed in a virtualized environment and optionally test whether it is a specific implementation, in this case "microsoft" for Hyper-V. https://www.freedesktop.org/software/systemd/man/systemd-detect-virt.html# microsoft = Hyper-V, also known as Viridian or Windows Server Virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
** Merge proposal linked: https://code.launchpad.net/~andyliuliming/ubuntu/+source/linux/+git/xenial/+merge/349032 -- 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/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: New Status in linux source package in Zesty: New Status in linux source package in Artful: New Status in linux source package in Bionic: Triaged Bug description: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft DefaultDependencies=no After=systemd-remount-fs.service Before=shutdown.target cloud-init-local.service walinuxagent.service Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv The hv-kvp-daemon service is not currently part of the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.809s └─multi-user.target @10.723s └─ephemeral-disk-warning.service @10.538s +31ms └─cloud-config.service @8.249s +2.252s └─basic.target @8.044s └─sockets.target @8.019s └─snapd.socket @7.692s +264ms └─sysinit.target @6.719s └─cloud-init.service @5.803s +842ms └─networking.service @5.137s +612ms └─network-pre.target @5.074s └─cloud-init-local.service @2.257s +2.783s └─systemd-remount-fs.service @1.368s +656ms └─systemd-journald.socket @1.218s └─-.mount @649ms └─system.slice @653ms └─-.slice @649ms In an Azure VM, the current startup time of my test is: $ systemd-analyze Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s After making the suggested change, the startup time is similar: $ systemd-analyze Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.666s └─multi-user.target @10.636s └─ephemeral-disk-warning.service @10.556s +36ms └─cloud-config.service @8.423s +2.095s └─basic.target @8.124s └─sockets.target @8.101s └─lxd.socket @7.677s +326ms └─sysinit.target @6.755s └─cloud-init.service @5.814s +908ms └─networking.service @5.111s +651ms └─network-pre.target @5.087s └─cloud-init-local.service @2.345s +2.707s └─hv-kvp-daemon.service @2.316s └─systemd-remount-fs.service @1.253s +680ms └─system.slice @1.225s └─-.slice @650ms The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
@Eric Desrochers, I'm from azure team. and the xenial bionic are tested. and it works well. will test the zesty and artful today and post the result here. ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy (andyliuliming) -- 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/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Incomplete Status in linux source package in Zesty: Incomplete Status in linux source package in Artful: Incomplete Status in linux source package in Bionic: Incomplete Bug description: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft DefaultDependencies=no After=systemd-remount-fs.service Before=shutdown.target cloud-init-local.service walinuxagent.service Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv The hv-kvp-daemon service is not currently part of the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.809s └─multi-user.target @10.723s └─ephemeral-disk-warning.service @10.538s +31ms └─cloud-config.service @8.249s +2.252s └─basic.target @8.044s └─sockets.target @8.019s └─snapd.socket @7.692s +264ms └─sysinit.target @6.719s └─cloud-init.service @5.803s +842ms └─networking.service @5.137s +612ms └─network-pre.target @5.074s └─cloud-init-local.service @2.257s +2.783s └─systemd-remount-fs.service @1.368s +656ms └─systemd-journald.socket @1.218s └─-.mount @649ms └─system.slice @653ms └─-.slice @649ms In an Azure VM, the current startup time of my test is: $ systemd-analyze Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s After making the suggested change, the startup time is similar: $ systemd-analyze Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.666s └─multi-user.target @10.636s └─ephemeral-disk-warning.service @10.556s +36ms └─cloud-config.service @8.423s +2.095s └─basic.target @8.124s └─sockets.target @8.101s └─lxd.socket @7.677s +326ms └─sysinit.target @6.755s └─cloud-init.service @5.814s +908ms └─networking.service @5.111s +651ms └─network-pre.target @5.087s └─cloud-init-local.service @2.345s +2.707s └─hv-kvp-daemon.service @2.316s └─systemd-remount-fs.service @1.253s +680ms └─system.slice @1.225s └─-.slice @650ms The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Andy (andyliuliming) ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Andy (andyliuliming) ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Andy (andyliuliming) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Andy (andyliuliming) ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Zesty) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Artful) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft DefaultDependencies=no After=systemd-remount-fs.service Before=shutdown.target cloud-init-local.service walinuxagent.service Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv The hv-kvp-daemon service is not currently part of the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.809s └─multi-user.target @10.723s └─ephemeral-disk-warning.service @10.538s +31ms └─cloud-config.service @8.249s +2.252s └─basic.target @8.044s └─sockets.target @8.019s └─snapd.socket @7.692s +264ms └─sysinit.target @6.719s └─cloud-init.service @5.803s +842ms └─networking.service @5.137s +612ms └─network-pre.target @5.074s └─cloud-init-local.service @2.257s +2.783s └─systemd-remount-fs.service @1.368s +656ms └─systemd-journald.socket @1.218s └─-.mount @649ms └─system.slice @653ms └─-.slice @649ms In an Azure VM, the current startup time of my test is: $ systemd-analyze Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s After making the suggested change, the startup time is similar: $ systemd-analyze Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.666s └─multi-user.target @10.636s └─ephemeral-disk-warning.service @10.556s +36ms └─cloud-config.service @8.423s +2.095s └─basic.target @8.124s └─sockets.target @8.101s └─lxd.socket @7.677s +326ms └─sysinit.target @6.755s └─cloud-init.service @5.814s +908ms └─networking.service @5.111s +651ms └─network-pre.target @5.087s └─cloud-init-local.service @2.345s +2.707s └─hv-kvp-daemon.service @2.316s └─systemd-remount-fs.service @1.253s +680ms └─system.slice @1.225s └─-.slice @650ms The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
verified, all works. could you please help "submitting to kernel-team ML", through I do not know what does it mean :) maybe it's a process before merging the PRs :) ** Changed in: linux (Ubuntu) Assignee: Andy (andyliuliming) => (unassigned) ** Changed in: linux (Ubuntu Xenial) Assignee: Andy (andyliuliming) => (unassigned) ** Changed in: linux (Ubuntu Zesty) Assignee: Andy (andyliuliming) => (unassigned) ** Changed in: linux (Ubuntu Bionic) Assignee: Andy (andyliuliming) => (unassigned) ** Changed in: linux (Ubuntu Artful) Assignee: Andy (andyliuliming) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft DefaultDependencies=no After=systemd-remount-fs.service Before=shutdown.target cloud-init-local.service walinuxagent.service Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv The hv-kvp-daemon service is not currently part of the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.809s └─multi-user.target @10.723s └─ephemeral-disk-warning.service @10.538s +31ms └─cloud-config.service @8.249s +2.252s └─basic.target @8.044s └─sockets.target @8.019s └─snapd.socket @7.692s +264ms └─sysinit.target @6.719s └─cloud-init.service @5.803s +842ms └─networking.service @5.137s +612ms └─network-pre.target @5.074s └─cloud-init-local.service @2.257s +2.783s └─systemd-remount-fs.service @1.368s +656ms └─systemd-journald.socket @1.218s └─-.mount @649ms └─system.slice @653ms └─-.slice @649ms In an Azure VM, the current startup time of my test is: $ systemd-analyze Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s After making the suggested change, the startup time is similar: $ systemd-analyze Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.666s └─multi-user.target @10.636s └─ephemeral-disk-warning.service @10.556s +36ms └─cloud-config.service @8.423s +2.095s └─basic.target @8.124s └─sockets.target @8.101s └─lxd.socket @7.677s +326ms └─sysinit.target @6.755s └─cloud-init.service @5.814s +908ms └─networking.service @5.111s +651ms └─network-pre.target @5.087s └─cloud-init-local.service @2.345s +2.707s └─hv-kvp-daemon.service @2.316s └─systemd-remount-fs.service @1.253s +680ms └─system.slice @1.225s └─-.slice @650ms The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
#294 Worked for me also, on a lenovo y50-70. I upgraded the Kernel through the Ukuu commands in terminal, then rebooted into the new kernel, then rebooted into the bios and it was fixed. Rebooting back into 4.13.0-21-generic without any further bricking because nvidia drivers don't work for 4.14.9. -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (22/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM Bug may effect machines from any manufacturer that uses BIOS based on Insyde Software. Insyde is responding to emails acknowledging that they are aware of issue but are not providing details. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577113] Re: 50/50 chance for BCM43602 to come up correctly during boot
I believe this is similar to the issue im getting with my BCM43602 on macbookpro running 16.04. It worked fine on 15.10. Ive updated to the upstream xenial kernel but the bug still exists : $uname -a Linux 4.4.9-040409-generic #201605041832 SMP Wed May 4 22:34:16 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $lspci | grep -i wire 03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) $dmesg | grep -i brcmf [ 10.242291] usbcore: registered new interface driver brcmfmac [ 10.381196] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 [ 10.864481] brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c [ 10.892497] brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 10.897532] brcmfmac :03:00.0 wlp3s0: renamed from wlan0 [ 10.968018] brcmf_add_if: ERROR: netdev:wlp3s0 already exists [ 10.968051] brcmf_add_if: ignore IF event [ 11.080205] brcmf_add_if: ERROR: netdev:wlp3s0 already exists [ 11.080208] brcmf_add_if: ignore IF event -- 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/1577113 Title: 50/50 chance for BCM43602 to come up correctly during boot Status in linux package in Ubuntu: Incomplete Bug description: My BCM43602 has a 50/50 chance during boot of ever becoming "ready" and pulling an IP address. The problem seems to be this "link is not ready" and "already exists" loop. The log I sent was one of the cases where things eventually worked. If I get unlucky, it simply repeats the "already exists" / "not ready" loop indefinitely. I get a similar situation when suspending/resuming. I've already pulled the firmware and stuck it under /lib (see dmesg output for version). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg.taylor 2418 F pulseaudio CurrentDesktop: Unity Date: Sun May 1 01:11:42 2016 HibernationDevice: RESUME=UUID=efd205da-4a67-4d8a-9c0e-6f3036178157 InstallationDate: Installed on 2016-04-28 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577113] Re: 50/50 chance for BCM43602 to come up correctly during boot
For me, a manual workaround is run the following after boot. When this is done the wireless comes back to life and is visible in network manager : sudo modprobe -r brcmfmac && sudo modprobe brcmfmac -- 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/1577113 Title: 50/50 chance for BCM43602 to come up correctly during boot Status in linux package in Ubuntu: Incomplete Bug description: My BCM43602 has a 50/50 chance during boot of ever becoming "ready" and pulling an IP address. The problem seems to be this "link is not ready" and "already exists" loop. The log I sent was one of the cases where things eventually worked. If I get unlucky, it simply repeats the "already exists" / "not ready" loop indefinitely. I get a similar situation when suspending/resuming. I've already pulled the firmware and stuck it under /lib (see dmesg output for version). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg.taylor 2418 F pulseaudio CurrentDesktop: Unity Date: Sun May 1 01:11:42 2016 HibernationDevice: RESUME=UUID=efd205da-4a67-4d8a-9c0e-6f3036178157 InstallationDate: Installed on 2016-04-28 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
@S.M. Al Mahi (syed-al-mahi) I as well bought a wifi dongle and it disconnects from the internet all the time. I even think it did something to my Killer wireless in my Windows OS, because when I logged into Windows it couldn't even find the Killer card. I think this is a cheap fix for any high end WiFi card. Is there any news yet? -- 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/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in linux package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
How much will it take to fix 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/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in linux package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
I am currently having the same issue with my MYTHLOGIC Dia 1614 Chassis (Clevo P650Sx) machine. Turns out the option I chose for a wireless card was the 'KILLER Wireless-AC 1525 2*2 802.11 ac/a/b/g/n + BT 4.0 350/867MB Total Bandwidth' as stated on the site. When typing command 'lspci -v' into terminal I get this for my wired and wireless connection cards: 03:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12) Subsystem: CLEVO/KAPOK Computer Device 6556 Flags: bus master, fast devsel, latency 0, IRQ 46 I/O ports at d000 [size=256] Memory at f7a14000 (64-bit, non-prefetchable) [size=4K] Memory at f7a1 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: r8169 04:00.0 Network controller: Qualcomm Atheros Device 003e (rev 20) Subsystem: Bigfoot Networks, Inc. Device 1525 Flags: fast devsel, IRQ 3 Memory at f780 (64-bit, non-prefetchable) [disabled] [size=2M] Capabilities: It seems I am not the only one having issues with this wireless card. Qualcomm Atheros Device 003e (rev 20) I currently have a dual boot setup with Windows 8.1 and Linux Mint 7.1 Cinnamon Rebecca edition which is based off Ubuntu (Debian) anyway so I guess we are all in the same boat. Is there a work-around yet?? because at this point I am getting extremely frustrated since I need to use Linux on the go immediately and will donate as-well to get this working ASAP. I am having buyers remorse since my machine is only a week old and that I should have chose a different option for Wireless cards like the 'Intel Centrino Advanced-AC 7265 2*2 802.11 ac/a/b/g/n + BT 4.0 350/867MB Total Bandwidth' If someone has a solution please don't hesitate to email me at ape...@gmail.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/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in linux package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHel
[Kernel-packages] [Bug 1173941] Re: Ubuntu 13.04 doesn't start/ show login screen/ after intallation or upgrade
Same problem here, I have a Dell XPS 13 (l322x) and I used a workaround but since the new kernel installed on this machine the problem is back. -- 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/1173941 Title: Ubuntu 13.04 doesn't start/ show login screen/ after intallation or upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: After upgrading from 12.10 to 13.04 the system doesn't show neither a splash screen nor a login screen when booting the 3.8.x kernel but the drum beat login sound is audible. Only if the upgraded system was booted with the previous kernel 3.5.x, the boot splash and login was visible and working. I've read that some other people who have also an Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller, are suffering the same problem. I suspect either plymouth to cause this problem, or the intel graphics driver in the 3.8.x kernel. Currently I'm using a workaround: I've added these two options to /etc/default/grub GRUB_GFXMODE=800x600 GRUB_GFXPAYLOAD_LINUX=text After running sudo update-grub the system boots normally, but without the splash screen. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: plymouth 0.8.8-0ubuntu6.1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CurrentDmesg: [ 16.605025] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 16.605544] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 16.608178] e100 :02:08.0 eth0: NIC Link is Up 100 Mbps Full Duplex [ 16.608251] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Sun Apr 28 14:34:14 2013 DefaultPlymouth: /lib/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth InstallationDate: Installed on 2013-04-26 (1 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) Lsusb: Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 05e1:0408 Syntek Semiconductor Co., Ltd STK1160 Video Capture Device MachineType: Hewlett-Packard HP 530 Notebook PC(KD092AA#ABD) MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=e4e5bf5d-0238-4cae-aa50-f937913b79ce ro quiet splash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=e4e5bf5d-0238-4cae-aa50-f937913b79ce ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/xubuntu-text/xubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVU Ver. F.04 dmi.board.name: 30D5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 82.14 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVUVer.F.04:bd05/23/2007:svnHewlett-Packard:pnHP530NotebookPC(KD092AA#ABD):pvrF.04:rvnHewlett-Packard:rn30D5:rvrKBCVersion82.14:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP 530 Notebook PC(KD092AA#ABD) dmi.product.version: F.04 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1522388] [NEW] Soft Lockup - CPU Stuck
Public bug reported: The Server was running: * openstack icehouse * Linux 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux(Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16) The kernel log: [13551520.909322] BUG: soft lockup - CPU#4 stuck for 23s! [migration/4:76] [13551520.909357] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev veth ipt_MASQUERA DE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge ip6table_filter ip6_ta bles iptable_filter ip_tables ebtable_nat ebtables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_is csi openvswitch gre vxlan ip_tunnel dm_crypt usb_storage gpio_ich joydev dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul c rc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw ipmi_si sb_edac edac_core mei_me mei lpc_ich shpchp mac_hid k vm_intel kvm 8021q garp stp mrp llc lp parport btrfs xor hid_generic usbhid hid raid6_pq libcrc32c ses enclosure ast syscopyarea sysfillrect sysimgblt ttm psmouse drm_kms _helper isci drm igb ahci libsas dca libahci ptp pps_core scsi_transport_sas i2c_algo_bit megaraid_sas wmi [13551520.909377] CPU: 4 PID: 76 Comm: migration/4 Tainted: G D W 3.13.0-48-generic #80-Ubuntu [13551520.909378] Hardware name: ASUSTek Computer INC. RS720-E7-RS12-E/Z9PE-D16 Series, BIOS 5302 11/08/2013 [13551520.909379] task: 881029391800 ti: 88102938c000 task.ti: 88102938c000 [13551520.909386] RIP: 0010:[] [] multi_cpu_stop+0x6b/0xf0 [13551520.909387] RSP: 0018:88102938dd98 EFLAGS: 0293 [13551520.909388] RAX: 8180ae00 RBX: 88103fc934c0 RCX: 7c34 [13551520.909389] RDX: 0001 RSI: RDI: 881083bd37b8 [13551520.909390] RBP: 88102938ddb8 R08: 0282 R09: 0001 [13551520.909391] R10: b590 R11: R12: 88102938dd20 [13551520.909392] R13: 88035499e000 R14: 81098235 R15: 88035499e000 [13551520.909394] FS: () GS:88103fc8() knlGS: [13551520.909395] CS: 0010 DS: ES: CR0: 80050033 [13551520.909396] CR2: 7f0206b09000 CR3: 0008ee4ad000 CR4: 000427e0 [13551520.909397] Stack: [13551520.909401] 881083bd37e0 88103fc8de20 88103fc8de28 881083bd37b8 [13551520.909404] 88102938de78 810f63de [13551520.909408] 88103fc934c0 881024f38700 88103fc934c0 [13551520.909409] Call Trace: [13551520.909413] [] cpu_stopper_thread+0x7e/0x150 [13551520.909418] [] ? __schedule+0x381/0x7d0 [13551520.909423] [] smpboot_thread_fn+0xff/0x1b0 [13551520.909426] [] ? SyS_setgroups+0x180/0x180 [13551520.909429] [] kthread+0xd2/0xf0 [13551520.909432] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909436] [] ret_from_fork+0x7c/0xb0 [13551520.909439] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909459] Code: 31 f6 31 d2 eb 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 <41> 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 fa 66 66 90 66 66 90 [13551520.971633] [] try_to_unmap_one+0x36/0x480 [13551520.973089] [] ? rmap_walk+0x186/0x210 [13551520.974528] [] try_to_unmap_anon+0xa7/0x120 [13551520.975958] [] try_to_unmap+0x4d/0x60 [13551520.977372] [] migrate_pages+0x43e/0x780 [13551520.978769] [] ? isolate_freepages_block+0x310/0x310 [13551520.980165] [] compact_zone+0x299/0x410 [13551520.981549] [] compact_zone_order+0x8e/0xd0 [13551520.982916] [] try_to_compact_pages+0x101/0x180 [13551520.984279] [] __alloc_pages_direct_compact+0xac/0x196 [13551520.985641] [] __alloc_pages_nodemask+0x760/0xb80 [13551520.986971] [] alloc_pages_vma+0x9a/0x140 [13551520.988267] [] do_huge_pmd_anonymous_page+0x10b/0x3f0 [13551520.989540] [] ? __rb_insert_augmented+0x8f/0x1f0 [13551520.990779] [] handle_mm_fault+0x198/0xf10 [13551520.991984] [] ? vma_link+0xb7/0xc0 [13551520.993153] [] __do_page_fault+0x184/0x560 [13551520.994289] [] ? do_mmap_pgoff+0x34e/0x3d0 [13551520.995387] [] ? vm_mmap_pgoff+0x99/0xc0 [13551520.996443] [] do_page_fault+0x1a/0x70 [13551520.997476] [] ? sigprocmask+0x57/0x90 [13551520.998481] [] page_fault+0x28/0x30 [13551520.999462] Code: 55 48 89 e5 b8 00 00 02 00 f0 0f c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 83 e2 fe 0f b7 f2 b8 00 80 00 00 eb 0c 0f 1f 44 00 00 90 83 e8 01 74 0a 0f b7 0f 66 39 ca 75 f1 5d c3 66 66 66 90 [13551521.013327] BUG: soft lockup - CPU#6 stuck for 22s! [qemu-system-x86:14068] [13551521.014492] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_phy
[Kernel-packages] [Bug 1522388] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1522388/+attachment/4529323/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522388 Title: Soft Lockup - CPU Stuck Status in linux package in Ubuntu: Confirmed Bug description: The Server was running: * openstack icehouse * Linux 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux(Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16) The kernel log: [13551520.909322] BUG: soft lockup - CPU#4 stuck for 23s! [migration/4:76] [13551520.909357] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev veth ipt_MASQUERA DE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge ip6table_filter ip6_ta bles iptable_filter ip_tables ebtable_nat ebtables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_is csi openvswitch gre vxlan ip_tunnel dm_crypt usb_storage gpio_ich joydev dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul c rc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw ipmi_si sb_edac edac_core mei_me mei lpc_ich shpchp mac_hid k vm_intel kvm 8021q garp stp mrp llc lp parport btrfs xor hid_generic usbhid hid raid6_pq libcrc32c ses enclosure ast syscopyarea sysfillrect sysimgblt ttm psmouse drm_kms _helper isci drm igb ahci libsas dca libahci ptp pps_core scsi_transport_sas i2c_algo_bit megaraid_sas wmi [13551520.909377] CPU: 4 PID: 76 Comm: migration/4 Tainted: G D W 3.13.0-48-generic #80-Ubuntu [13551520.909378] Hardware name: ASUSTek Computer INC. RS720-E7-RS12-E/Z9PE-D16 Series, BIOS 5302 11/08/2013 [13551520.909379] task: 881029391800 ti: 88102938c000 task.ti: 88102938c000 [13551520.909386] RIP: 0010:[] [] multi_cpu_stop+0x6b/0xf0 [13551520.909387] RSP: 0018:88102938dd98 EFLAGS: 0293 [13551520.909388] RAX: 8180ae00 RBX: 88103fc934c0 RCX: 7c34 [13551520.909389] RDX: 0001 RSI: RDI: 881083bd37b8 [13551520.909390] RBP: 88102938ddb8 R08: 0282 R09: 0001 [13551520.909391] R10: b590 R11: R12: 88102938dd20 [13551520.909392] R13: 88035499e000 R14: 81098235 R15: 88035499e000 [13551520.909394] FS: () GS:88103fc8() knlGS: [13551520.909395] CS: 0010 DS: ES: CR0: 80050033 [13551520.909396] CR2: 7f0206b09000 CR3: 0008ee4ad000 CR4: 000427e0 [13551520.909397] Stack: [13551520.909401] 881083bd37e0 88103fc8de20 88103fc8de28 881083bd37b8 [13551520.909404] 88102938de78 810f63de [13551520.909408] 88103fc934c0 881024f38700 88103fc934c0 [13551520.909409] Call Trace: [13551520.909413] [] cpu_stopper_thread+0x7e/0x150 [13551520.909418] [] ? __schedule+0x381/0x7d0 [13551520.909423] [] smpboot_thread_fn+0xff/0x1b0 [13551520.909426] [] ? SyS_setgroups+0x180/0x180 [13551520.909429] [] kthread+0xd2/0xf0 [13551520.909432] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909436] [] ret_from_fork+0x7c/0xb0 [13551520.909439] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909459] Code: 31 f6 31 d2 eb 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 <41> 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 fa 66 66 90 66 66 90 [13551520.971633] [] try_to_unmap_one+0x36/0x480 [13551520.973089] [] ? rmap_walk+0x186/0x210 [13551520.974528] [] try_to_unmap_anon+0xa7/0x120 [13551520.975958] [] try_to_unmap+0x4d/0x60 [13551520.977372] [] migrate_pages+0x43e/0x780 [13551520.978769] [] ? isolate_freepages_block+0x310/0x310 [13551520.980165] [] compact_zone+0x299/0x410 [13551520.981549] [] compact_zone_order+0x8e/0xd0 [13551520.982916] [] try_to_compact_pages+0x101/0x180 [13551520.984279] [] __alloc_pages_direct_compact+0xac/0x196 [13551520.985641] [] __alloc_pages_nodemask+0x760/0xb80 [13551520.986971] [] alloc_pages_vma+0x9a/0x140 [13551520.988267] [] do_huge_pmd_anonymous_page+0x10b/0x3f0 [13551520.989540] [] ? __rb_insert_augmented+0x8f/0x1f0 [13551520.990779] [] handle_mm_fault+0x198/0xf10 [13551520.991984] [] ? vma_link+0xb7/0xc0 [13551520.993153] [] __do_page_fault+0x184/0x560 [13551520.994289] [] ? do_mmap_pgoff+0x34e/0x3d0 [13551520.995387] [] ? vm_mmap_pgoff+0x99/0xc0 [13551520.996443] [] do_page_fault+0x1a/
[Kernel-packages] [Bug 1522388] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1522388/+attachment/4529317/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522388 Title: Soft Lockup - CPU Stuck Status in linux package in Ubuntu: Confirmed Bug description: The Server was running: * openstack icehouse * Linux 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux(Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16) The kernel log: [13551520.909322] BUG: soft lockup - CPU#4 stuck for 23s! [migration/4:76] [13551520.909357] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev veth ipt_MASQUERA DE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge ip6table_filter ip6_ta bles iptable_filter ip_tables ebtable_nat ebtables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_is csi openvswitch gre vxlan ip_tunnel dm_crypt usb_storage gpio_ich joydev dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul c rc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw ipmi_si sb_edac edac_core mei_me mei lpc_ich shpchp mac_hid k vm_intel kvm 8021q garp stp mrp llc lp parport btrfs xor hid_generic usbhid hid raid6_pq libcrc32c ses enclosure ast syscopyarea sysfillrect sysimgblt ttm psmouse drm_kms _helper isci drm igb ahci libsas dca libahci ptp pps_core scsi_transport_sas i2c_algo_bit megaraid_sas wmi [13551520.909377] CPU: 4 PID: 76 Comm: migration/4 Tainted: G D W 3.13.0-48-generic #80-Ubuntu [13551520.909378] Hardware name: ASUSTek Computer INC. RS720-E7-RS12-E/Z9PE-D16 Series, BIOS 5302 11/08/2013 [13551520.909379] task: 881029391800 ti: 88102938c000 task.ti: 88102938c000 [13551520.909386] RIP: 0010:[] [] multi_cpu_stop+0x6b/0xf0 [13551520.909387] RSP: 0018:88102938dd98 EFLAGS: 0293 [13551520.909388] RAX: 8180ae00 RBX: 88103fc934c0 RCX: 7c34 [13551520.909389] RDX: 0001 RSI: RDI: 881083bd37b8 [13551520.909390] RBP: 88102938ddb8 R08: 0282 R09: 0001 [13551520.909391] R10: b590 R11: R12: 88102938dd20 [13551520.909392] R13: 88035499e000 R14: 81098235 R15: 88035499e000 [13551520.909394] FS: () GS:88103fc8() knlGS: [13551520.909395] CS: 0010 DS: ES: CR0: 80050033 [13551520.909396] CR2: 7f0206b09000 CR3: 0008ee4ad000 CR4: 000427e0 [13551520.909397] Stack: [13551520.909401] 881083bd37e0 88103fc8de20 88103fc8de28 881083bd37b8 [13551520.909404] 88102938de78 810f63de [13551520.909408] 88103fc934c0 881024f38700 88103fc934c0 [13551520.909409] Call Trace: [13551520.909413] [] cpu_stopper_thread+0x7e/0x150 [13551520.909418] [] ? __schedule+0x381/0x7d0 [13551520.909423] [] smpboot_thread_fn+0xff/0x1b0 [13551520.909426] [] ? SyS_setgroups+0x180/0x180 [13551520.909429] [] kthread+0xd2/0xf0 [13551520.909432] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909436] [] ret_from_fork+0x7c/0xb0 [13551520.909439] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909459] Code: 31 f6 31 d2 eb 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 <41> 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 fa 66 66 90 66 66 90 [13551520.971633] [] try_to_unmap_one+0x36/0x480 [13551520.973089] [] ? rmap_walk+0x186/0x210 [13551520.974528] [] try_to_unmap_anon+0xa7/0x120 [13551520.975958] [] try_to_unmap+0x4d/0x60 [13551520.977372] [] migrate_pages+0x43e/0x780 [13551520.978769] [] ? isolate_freepages_block+0x310/0x310 [13551520.980165] [] compact_zone+0x299/0x410 [13551520.981549] [] compact_zone_order+0x8e/0xd0 [13551520.982916] [] try_to_compact_pages+0x101/0x180 [13551520.984279] [] __alloc_pages_direct_compact+0xac/0x196 [13551520.985641] [] __alloc_pages_nodemask+0x760/0xb80 [13551520.986971] [] alloc_pages_vma+0x9a/0x140 [13551520.988267] [] do_huge_pmd_anonymous_page+0x10b/0x3f0 [13551520.989540] [] ? __rb_insert_augmented+0x8f/0x1f0 [13551520.990779] [] handle_mm_fault+0x198/0xf10 [13551520.991984] [] ? vma_link+0xb7/0xc0 [13551520.993153] [] __do_page_fault+0x184/0x560 [13551520.994289] [] ? do_mmap_pgoff+0x34e/0x3d0 [13551520.995387] [] ? vm_mmap_pgoff+0x99/0xc0 [13551520.996443] [] do_page_fault+0x1
[Kernel-packages] [Bug 1522388] Re: Soft Lockup - CPU Stuck
apport information ** Tags added: apport-collected ** Description changed: The Server was running: * openstack icehouse * Linux 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux(Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16) The kernel log: [13551520.909322] BUG: soft lockup - CPU#4 stuck for 23s! [migration/4:76] [13551520.909357] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev veth ipt_MASQUERA DE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge ip6table_filter ip6_ta bles iptable_filter ip_tables ebtable_nat ebtables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_is csi openvswitch gre vxlan ip_tunnel dm_crypt usb_storage gpio_ich joydev dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul c rc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw ipmi_si sb_edac edac_core mei_me mei lpc_ich shpchp mac_hid k vm_intel kvm 8021q garp stp mrp llc lp parport btrfs xor hid_generic usbhid hid raid6_pq libcrc32c ses enclosure ast syscopyarea sysfillrect sysimgblt ttm psmouse drm_kms _helper isci drm igb ahci libsas dca libahci ptp pps_core scsi_transport_sas i2c_algo_bit megaraid_sas wmi [13551520.909377] CPU: 4 PID: 76 Comm: migration/4 Tainted: G D W 3.13.0-48-generic #80-Ubuntu [13551520.909378] Hardware name: ASUSTek Computer INC. RS720-E7-RS12-E/Z9PE-D16 Series, BIOS 5302 11/08/2013 [13551520.909379] task: 881029391800 ti: 88102938c000 task.ti: 88102938c000 [13551520.909386] RIP: 0010:[] [] multi_cpu_stop+0x6b/0xf0 [13551520.909387] RSP: 0018:88102938dd98 EFLAGS: 0293 [13551520.909388] RAX: 8180ae00 RBX: 88103fc934c0 RCX: 7c34 [13551520.909389] RDX: 0001 RSI: RDI: 881083bd37b8 [13551520.909390] RBP: 88102938ddb8 R08: 0282 R09: 0001 [13551520.909391] R10: b590 R11: R12: 88102938dd20 [13551520.909392] R13: 88035499e000 R14: 81098235 R15: 88035499e000 [13551520.909394] FS: () GS:88103fc8() knlGS: [13551520.909395] CS: 0010 DS: ES: CR0: 80050033 [13551520.909396] CR2: 7f0206b09000 CR3: 0008ee4ad000 CR4: 000427e0 [13551520.909397] Stack: [13551520.909401] 881083bd37e0 88103fc8de20 88103fc8de28 881083bd37b8 [13551520.909404] 88102938de78 810f63de [13551520.909408] 88103fc934c0 881024f38700 88103fc934c0 [13551520.909409] Call Trace: [13551520.909413] [] cpu_stopper_thread+0x7e/0x150 [13551520.909418] [] ? __schedule+0x381/0x7d0 [13551520.909423] [] smpboot_thread_fn+0xff/0x1b0 [13551520.909426] [] ? SyS_setgroups+0x180/0x180 [13551520.909429] [] kthread+0xd2/0xf0 [13551520.909432] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909436] [] ret_from_fork+0x7c/0xb0 [13551520.909439] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909459] Code: 31 f6 31 d2 eb 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 <41> 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 fa 66 66 90 66 66 90 [13551520.971633] [] try_to_unmap_one+0x36/0x480 [13551520.973089] [] ? rmap_walk+0x186/0x210 [13551520.974528] [] try_to_unmap_anon+0xa7/0x120 [13551520.975958] [] try_to_unmap+0x4d/0x60 [13551520.977372] [] migrate_pages+0x43e/0x780 [13551520.978769] [] ? isolate_freepages_block+0x310/0x310 [13551520.980165] [] compact_zone+0x299/0x410 [13551520.981549] [] compact_zone_order+0x8e/0xd0 [13551520.982916] [] try_to_compact_pages+0x101/0x180 [13551520.984279] [] __alloc_pages_direct_compact+0xac/0x196 [13551520.985641] [] __alloc_pages_nodemask+0x760/0xb80 [13551520.986971] [] alloc_pages_vma+0x9a/0x140 [13551520.988267] [] do_huge_pmd_anonymous_page+0x10b/0x3f0 [13551520.989540] [] ? __rb_insert_augmented+0x8f/0x1f0 [13551520.990779] [] handle_mm_fault+0x198/0xf10 [13551520.991984] [] ? vma_link+0xb7/0xc0 [13551520.993153] [] __do_page_fault+0x184/0x560 [13551520.994289] [] ? do_mmap_pgoff+0x34e/0x3d0 [13551520.995387] [] ? vm_mmap_pgoff+0x99/0xc0 [13551520.996443] [] do_page_fault+0x1a/0x70 [13551520.997476] [] ? sigprocmask+0x57/0x90 [13551520.998481] [] page_fault+0x28/0x30 [13551520.999462] Code: 55 48 89 e5 b8 00 00 02 00 f0 0f c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 83 e2 fe 0f b7 f2 b8 00 80 00 00 eb 0c 0f 1f 44 00 00 90 83 e8 01 74 0a 0f b7 0f 66 39 ca 75 f1 5d c3 66 66 66 90 [135
[Kernel-packages] [Bug 1522388] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1522388/+attachment/4529324/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522388 Title: Soft Lockup - CPU Stuck Status in linux package in Ubuntu: Confirmed Bug description: The Server was running: * openstack icehouse * Linux 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux(Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16) The kernel log: [13551520.909322] BUG: soft lockup - CPU#4 stuck for 23s! [migration/4:76] [13551520.909357] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev veth ipt_MASQUERA DE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge ip6table_filter ip6_ta bles iptable_filter ip_tables ebtable_nat ebtables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_is csi openvswitch gre vxlan ip_tunnel dm_crypt usb_storage gpio_ich joydev dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul c rc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw ipmi_si sb_edac edac_core mei_me mei lpc_ich shpchp mac_hid k vm_intel kvm 8021q garp stp mrp llc lp parport btrfs xor hid_generic usbhid hid raid6_pq libcrc32c ses enclosure ast syscopyarea sysfillrect sysimgblt ttm psmouse drm_kms _helper isci drm igb ahci libsas dca libahci ptp pps_core scsi_transport_sas i2c_algo_bit megaraid_sas wmi [13551520.909377] CPU: 4 PID: 76 Comm: migration/4 Tainted: G D W 3.13.0-48-generic #80-Ubuntu [13551520.909378] Hardware name: ASUSTek Computer INC. RS720-E7-RS12-E/Z9PE-D16 Series, BIOS 5302 11/08/2013 [13551520.909379] task: 881029391800 ti: 88102938c000 task.ti: 88102938c000 [13551520.909386] RIP: 0010:[] [] multi_cpu_stop+0x6b/0xf0 [13551520.909387] RSP: 0018:88102938dd98 EFLAGS: 0293 [13551520.909388] RAX: 8180ae00 RBX: 88103fc934c0 RCX: 7c34 [13551520.909389] RDX: 0001 RSI: RDI: 881083bd37b8 [13551520.909390] RBP: 88102938ddb8 R08: 0282 R09: 0001 [13551520.909391] R10: b590 R11: R12: 88102938dd20 [13551520.909392] R13: 88035499e000 R14: 81098235 R15: 88035499e000 [13551520.909394] FS: () GS:88103fc8() knlGS: [13551520.909395] CS: 0010 DS: ES: CR0: 80050033 [13551520.909396] CR2: 7f0206b09000 CR3: 0008ee4ad000 CR4: 000427e0 [13551520.909397] Stack: [13551520.909401] 881083bd37e0 88103fc8de20 88103fc8de28 881083bd37b8 [13551520.909404] 88102938de78 810f63de [13551520.909408] 88103fc934c0 881024f38700 88103fc934c0 [13551520.909409] Call Trace: [13551520.909413] [] cpu_stopper_thread+0x7e/0x150 [13551520.909418] [] ? __schedule+0x381/0x7d0 [13551520.909423] [] smpboot_thread_fn+0xff/0x1b0 [13551520.909426] [] ? SyS_setgroups+0x180/0x180 [13551520.909429] [] kthread+0xd2/0xf0 [13551520.909432] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909436] [] ret_from_fork+0x7c/0xb0 [13551520.909439] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909459] Code: 31 f6 31 d2 eb 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 <41> 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 fa 66 66 90 66 66 90 [13551520.971633] [] try_to_unmap_one+0x36/0x480 [13551520.973089] [] ? rmap_walk+0x186/0x210 [13551520.974528] [] try_to_unmap_anon+0xa7/0x120 [13551520.975958] [] try_to_unmap+0x4d/0x60 [13551520.977372] [] migrate_pages+0x43e/0x780 [13551520.978769] [] ? isolate_freepages_block+0x310/0x310 [13551520.980165] [] compact_zone+0x299/0x410 [13551520.981549] [] compact_zone_order+0x8e/0xd0 [13551520.982916] [] try_to_compact_pages+0x101/0x180 [13551520.984279] [] __alloc_pages_direct_compact+0xac/0x196 [13551520.985641] [] __alloc_pages_nodemask+0x760/0xb80 [13551520.986971] [] alloc_pages_vma+0x9a/0x140 [13551520.988267] [] do_huge_pmd_anonymous_page+0x10b/0x3f0 [13551520.989540] [] ? __rb_insert_augmented+0x8f/0x1f0 [13551520.990779] [] handle_mm_fault+0x198/0xf10 [13551520.991984] [] ? vma_link+0xb7/0xc0 [13551520.993153] [] __do_page_fault+0x184/0x560 [13551520.994289] [] ? do_mmap_pgoff+0x34e/0x3d0 [13551520.995387] [] ? vm_mmap_pgoff+0x99/0xc0 [13551520.996443] [] do_page_fault+0x1a/0x70 [135
[Kernel-packages] [Bug 1522388] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1522388/+attachment/4529319/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522388 Title: Soft Lockup - CPU Stuck Status in linux package in Ubuntu: Confirmed Bug description: The Server was running: * openstack icehouse * Linux 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux(Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16) The kernel log: [13551520.909322] BUG: soft lockup - CPU#4 stuck for 23s! [migration/4:76] [13551520.909357] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev veth ipt_MASQUERA DE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge ip6table_filter ip6_ta bles iptable_filter ip_tables ebtable_nat ebtables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_is csi openvswitch gre vxlan ip_tunnel dm_crypt usb_storage gpio_ich joydev dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul c rc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw ipmi_si sb_edac edac_core mei_me mei lpc_ich shpchp mac_hid k vm_intel kvm 8021q garp stp mrp llc lp parport btrfs xor hid_generic usbhid hid raid6_pq libcrc32c ses enclosure ast syscopyarea sysfillrect sysimgblt ttm psmouse drm_kms _helper isci drm igb ahci libsas dca libahci ptp pps_core scsi_transport_sas i2c_algo_bit megaraid_sas wmi [13551520.909377] CPU: 4 PID: 76 Comm: migration/4 Tainted: G D W 3.13.0-48-generic #80-Ubuntu [13551520.909378] Hardware name: ASUSTek Computer INC. RS720-E7-RS12-E/Z9PE-D16 Series, BIOS 5302 11/08/2013 [13551520.909379] task: 881029391800 ti: 88102938c000 task.ti: 88102938c000 [13551520.909386] RIP: 0010:[] [] multi_cpu_stop+0x6b/0xf0 [13551520.909387] RSP: 0018:88102938dd98 EFLAGS: 0293 [13551520.909388] RAX: 8180ae00 RBX: 88103fc934c0 RCX: 7c34 [13551520.909389] RDX: 0001 RSI: RDI: 881083bd37b8 [13551520.909390] RBP: 88102938ddb8 R08: 0282 R09: 0001 [13551520.909391] R10: b590 R11: R12: 88102938dd20 [13551520.909392] R13: 88035499e000 R14: 81098235 R15: 88035499e000 [13551520.909394] FS: () GS:88103fc8() knlGS: [13551520.909395] CS: 0010 DS: ES: CR0: 80050033 [13551520.909396] CR2: 7f0206b09000 CR3: 0008ee4ad000 CR4: 000427e0 [13551520.909397] Stack: [13551520.909401] 881083bd37e0 88103fc8de20 88103fc8de28 881083bd37b8 [13551520.909404] 88102938de78 810f63de [13551520.909408] 88103fc934c0 881024f38700 88103fc934c0 [13551520.909409] Call Trace: [13551520.909413] [] cpu_stopper_thread+0x7e/0x150 [13551520.909418] [] ? __schedule+0x381/0x7d0 [13551520.909423] [] smpboot_thread_fn+0xff/0x1b0 [13551520.909426] [] ? SyS_setgroups+0x180/0x180 [13551520.909429] [] kthread+0xd2/0xf0 [13551520.909432] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909436] [] ret_from_fork+0x7c/0xb0 [13551520.909439] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909459] Code: 31 f6 31 d2 eb 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 <41> 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 fa 66 66 90 66 66 90 [13551520.971633] [] try_to_unmap_one+0x36/0x480 [13551520.973089] [] ? rmap_walk+0x186/0x210 [13551520.974528] [] try_to_unmap_anon+0xa7/0x120 [13551520.975958] [] try_to_unmap+0x4d/0x60 [13551520.977372] [] migrate_pages+0x43e/0x780 [13551520.978769] [] ? isolate_freepages_block+0x310/0x310 [13551520.980165] [] compact_zone+0x299/0x410 [13551520.981549] [] compact_zone_order+0x8e/0xd0 [13551520.982916] [] try_to_compact_pages+0x101/0x180 [13551520.984279] [] __alloc_pages_direct_compact+0xac/0x196 [13551520.985641] [] __alloc_pages_nodemask+0x760/0xb80 [13551520.986971] [] alloc_pages_vma+0x9a/0x140 [13551520.988267] [] do_huge_pmd_anonymous_page+0x10b/0x3f0 [13551520.989540] [] ? __rb_insert_augmented+0x8f/0x1f0 [13551520.990779] [] handle_mm_fault+0x198/0xf10 [13551520.991984] [] ? vma_link+0xb7/0xc0 [13551520.993153] [] __do_page_fault+0x184/0x560 [13551520.994289] [] ? do_mmap_pgoff+0x34e/0x3d0 [13551520.995387] [] ? vm_mmap_pgoff+0x99/0xc0 [13551520.996443] [] do_page_fault+0x1a/0x70 [13551
[Kernel-packages] [Bug 1522388] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1522388/+attachment/4529321/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522388 Title: Soft Lockup - CPU Stuck Status in linux package in Ubuntu: Confirmed Bug description: The Server was running: * openstack icehouse * Linux 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux(Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16) The kernel log: [13551520.909322] BUG: soft lockup - CPU#4 stuck for 23s! [migration/4:76] [13551520.909357] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev veth ipt_MASQUERA DE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge ip6table_filter ip6_ta bles iptable_filter ip_tables ebtable_nat ebtables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_is csi openvswitch gre vxlan ip_tunnel dm_crypt usb_storage gpio_ich joydev dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul c rc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw ipmi_si sb_edac edac_core mei_me mei lpc_ich shpchp mac_hid k vm_intel kvm 8021q garp stp mrp llc lp parport btrfs xor hid_generic usbhid hid raid6_pq libcrc32c ses enclosure ast syscopyarea sysfillrect sysimgblt ttm psmouse drm_kms _helper isci drm igb ahci libsas dca libahci ptp pps_core scsi_transport_sas i2c_algo_bit megaraid_sas wmi [13551520.909377] CPU: 4 PID: 76 Comm: migration/4 Tainted: G D W 3.13.0-48-generic #80-Ubuntu [13551520.909378] Hardware name: ASUSTek Computer INC. RS720-E7-RS12-E/Z9PE-D16 Series, BIOS 5302 11/08/2013 [13551520.909379] task: 881029391800 ti: 88102938c000 task.ti: 88102938c000 [13551520.909386] RIP: 0010:[] [] multi_cpu_stop+0x6b/0xf0 [13551520.909387] RSP: 0018:88102938dd98 EFLAGS: 0293 [13551520.909388] RAX: 8180ae00 RBX: 88103fc934c0 RCX: 7c34 [13551520.909389] RDX: 0001 RSI: RDI: 881083bd37b8 [13551520.909390] RBP: 88102938ddb8 R08: 0282 R09: 0001 [13551520.909391] R10: b590 R11: R12: 88102938dd20 [13551520.909392] R13: 88035499e000 R14: 81098235 R15: 88035499e000 [13551520.909394] FS: () GS:88103fc8() knlGS: [13551520.909395] CS: 0010 DS: ES: CR0: 80050033 [13551520.909396] CR2: 7f0206b09000 CR3: 0008ee4ad000 CR4: 000427e0 [13551520.909397] Stack: [13551520.909401] 881083bd37e0 88103fc8de20 88103fc8de28 881083bd37b8 [13551520.909404] 88102938de78 810f63de [13551520.909408] 88103fc934c0 881024f38700 88103fc934c0 [13551520.909409] Call Trace: [13551520.909413] [] cpu_stopper_thread+0x7e/0x150 [13551520.909418] [] ? __schedule+0x381/0x7d0 [13551520.909423] [] smpboot_thread_fn+0xff/0x1b0 [13551520.909426] [] ? SyS_setgroups+0x180/0x180 [13551520.909429] [] kthread+0xd2/0xf0 [13551520.909432] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909436] [] ret_from_fork+0x7c/0xb0 [13551520.909439] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909459] Code: 31 f6 31 d2 eb 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 <41> 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 fa 66 66 90 66 66 90 [13551520.971633] [] try_to_unmap_one+0x36/0x480 [13551520.973089] [] ? rmap_walk+0x186/0x210 [13551520.974528] [] try_to_unmap_anon+0xa7/0x120 [13551520.975958] [] try_to_unmap+0x4d/0x60 [13551520.977372] [] migrate_pages+0x43e/0x780 [13551520.978769] [] ? isolate_freepages_block+0x310/0x310 [13551520.980165] [] compact_zone+0x299/0x410 [13551520.981549] [] compact_zone_order+0x8e/0xd0 [13551520.982916] [] try_to_compact_pages+0x101/0x180 [13551520.984279] [] __alloc_pages_direct_compact+0xac/0x196 [13551520.985641] [] __alloc_pages_nodemask+0x760/0xb80 [13551520.986971] [] alloc_pages_vma+0x9a/0x140 [13551520.988267] [] do_huge_pmd_anonymous_page+0x10b/0x3f0 [13551520.989540] [] ? __rb_insert_augmented+0x8f/0x1f0 [13551520.990779] [] handle_mm_fault+0x198/0xf10 [13551520.991984] [] ? vma_link+0xb7/0xc0 [13551520.993153] [] __do_page_fault+0x184/0x560 [13551520.994289] [] ? do_mmap_pgoff+0x34e/0x3d0 [13551520.995387] [] ? vm_mmap_pgoff+0x99/0xc0 [13551520.996443] [] do_page_fault+0x1a/
[Kernel-packages] [Bug 1522388] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1522388/+attachment/4529318/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522388 Title: Soft Lockup - CPU Stuck Status in linux package in Ubuntu: Confirmed Bug description: The Server was running: * openstack icehouse * Linux 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux(Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16) The kernel log: [13551520.909322] BUG: soft lockup - CPU#4 stuck for 23s! [migration/4:76] [13551520.909357] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev veth ipt_MASQUERA DE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge ip6table_filter ip6_ta bles iptable_filter ip_tables ebtable_nat ebtables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_is csi openvswitch gre vxlan ip_tunnel dm_crypt usb_storage gpio_ich joydev dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul c rc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw ipmi_si sb_edac edac_core mei_me mei lpc_ich shpchp mac_hid k vm_intel kvm 8021q garp stp mrp llc lp parport btrfs xor hid_generic usbhid hid raid6_pq libcrc32c ses enclosure ast syscopyarea sysfillrect sysimgblt ttm psmouse drm_kms _helper isci drm igb ahci libsas dca libahci ptp pps_core scsi_transport_sas i2c_algo_bit megaraid_sas wmi [13551520.909377] CPU: 4 PID: 76 Comm: migration/4 Tainted: G D W 3.13.0-48-generic #80-Ubuntu [13551520.909378] Hardware name: ASUSTek Computer INC. RS720-E7-RS12-E/Z9PE-D16 Series, BIOS 5302 11/08/2013 [13551520.909379] task: 881029391800 ti: 88102938c000 task.ti: 88102938c000 [13551520.909386] RIP: 0010:[] [] multi_cpu_stop+0x6b/0xf0 [13551520.909387] RSP: 0018:88102938dd98 EFLAGS: 0293 [13551520.909388] RAX: 8180ae00 RBX: 88103fc934c0 RCX: 7c34 [13551520.909389] RDX: 0001 RSI: RDI: 881083bd37b8 [13551520.909390] RBP: 88102938ddb8 R08: 0282 R09: 0001 [13551520.909391] R10: b590 R11: R12: 88102938dd20 [13551520.909392] R13: 88035499e000 R14: 81098235 R15: 88035499e000 [13551520.909394] FS: () GS:88103fc8() knlGS: [13551520.909395] CS: 0010 DS: ES: CR0: 80050033 [13551520.909396] CR2: 7f0206b09000 CR3: 0008ee4ad000 CR4: 000427e0 [13551520.909397] Stack: [13551520.909401] 881083bd37e0 88103fc8de20 88103fc8de28 881083bd37b8 [13551520.909404] 88102938de78 810f63de [13551520.909408] 88103fc934c0 881024f38700 88103fc934c0 [13551520.909409] Call Trace: [13551520.909413] [] cpu_stopper_thread+0x7e/0x150 [13551520.909418] [] ? __schedule+0x381/0x7d0 [13551520.909423] [] smpboot_thread_fn+0xff/0x1b0 [13551520.909426] [] ? SyS_setgroups+0x180/0x180 [13551520.909429] [] kthread+0xd2/0xf0 [13551520.909432] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909436] [] ret_from_fork+0x7c/0xb0 [13551520.909439] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909459] Code: 31 f6 31 d2 eb 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 <41> 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 fa 66 66 90 66 66 90 [13551520.971633] [] try_to_unmap_one+0x36/0x480 [13551520.973089] [] ? rmap_walk+0x186/0x210 [13551520.974528] [] try_to_unmap_anon+0xa7/0x120 [13551520.975958] [] try_to_unmap+0x4d/0x60 [13551520.977372] [] migrate_pages+0x43e/0x780 [13551520.978769] [] ? isolate_freepages_block+0x310/0x310 [13551520.980165] [] compact_zone+0x299/0x410 [13551520.981549] [] compact_zone_order+0x8e/0xd0 [13551520.982916] [] try_to_compact_pages+0x101/0x180 [13551520.984279] [] __alloc_pages_direct_compact+0xac/0x196 [13551520.985641] [] __alloc_pages_nodemask+0x760/0xb80 [13551520.986971] [] alloc_pages_vma+0x9a/0x140 [13551520.988267] [] do_huge_pmd_anonymous_page+0x10b/0x3f0 [13551520.989540] [] ? __rb_insert_augmented+0x8f/0x1f0 [13551520.990779] [] handle_mm_fault+0x198/0xf10 [13551520.991984] [] ? vma_link+0xb7/0xc0 [13551520.993153] [] __do_page_fault+0x184/0x560 [13551520.994289] [] ? do_mmap_pgoff+0x34e/0x3d0 [13551520.995387] [] ? vm_mmap_pgoff+0x99/0xc0 [13551520.996443] [] do_page_fault+0x1a/0x70
[Kernel-packages] [Bug 1522388] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1522388/+attachment/4529325/+files/UdevLog.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/1522388 Title: Soft Lockup - CPU Stuck Status in linux package in Ubuntu: Confirmed Bug description: The Server was running: * openstack icehouse * Linux 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux(Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16) The kernel log: [13551520.909322] BUG: soft lockup - CPU#4 stuck for 23s! [migration/4:76] [13551520.909357] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev veth ipt_MASQUERA DE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge ip6table_filter ip6_ta bles iptable_filter ip_tables ebtable_nat ebtables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_is csi openvswitch gre vxlan ip_tunnel dm_crypt usb_storage gpio_ich joydev dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul c rc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw ipmi_si sb_edac edac_core mei_me mei lpc_ich shpchp mac_hid k vm_intel kvm 8021q garp stp mrp llc lp parport btrfs xor hid_generic usbhid hid raid6_pq libcrc32c ses enclosure ast syscopyarea sysfillrect sysimgblt ttm psmouse drm_kms _helper isci drm igb ahci libsas dca libahci ptp pps_core scsi_transport_sas i2c_algo_bit megaraid_sas wmi [13551520.909377] CPU: 4 PID: 76 Comm: migration/4 Tainted: G D W 3.13.0-48-generic #80-Ubuntu [13551520.909378] Hardware name: ASUSTek Computer INC. RS720-E7-RS12-E/Z9PE-D16 Series, BIOS 5302 11/08/2013 [13551520.909379] task: 881029391800 ti: 88102938c000 task.ti: 88102938c000 [13551520.909386] RIP: 0010:[] [] multi_cpu_stop+0x6b/0xf0 [13551520.909387] RSP: 0018:88102938dd98 EFLAGS: 0293 [13551520.909388] RAX: 8180ae00 RBX: 88103fc934c0 RCX: 7c34 [13551520.909389] RDX: 0001 RSI: RDI: 881083bd37b8 [13551520.909390] RBP: 88102938ddb8 R08: 0282 R09: 0001 [13551520.909391] R10: b590 R11: R12: 88102938dd20 [13551520.909392] R13: 88035499e000 R14: 81098235 R15: 88035499e000 [13551520.909394] FS: () GS:88103fc8() knlGS: [13551520.909395] CS: 0010 DS: ES: CR0: 80050033 [13551520.909396] CR2: 7f0206b09000 CR3: 0008ee4ad000 CR4: 000427e0 [13551520.909397] Stack: [13551520.909401] 881083bd37e0 88103fc8de20 88103fc8de28 881083bd37b8 [13551520.909404] 88102938de78 810f63de [13551520.909408] 88103fc934c0 881024f38700 88103fc934c0 [13551520.909409] Call Trace: [13551520.909413] [] cpu_stopper_thread+0x7e/0x150 [13551520.909418] [] ? __schedule+0x381/0x7d0 [13551520.909423] [] smpboot_thread_fn+0xff/0x1b0 [13551520.909426] [] ? SyS_setgroups+0x180/0x180 [13551520.909429] [] kthread+0xd2/0xf0 [13551520.909432] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909436] [] ret_from_fork+0x7c/0xb0 [13551520.909439] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909459] Code: 31 f6 31 d2 eb 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 <41> 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 fa 66 66 90 66 66 90 [13551520.971633] [] try_to_unmap_one+0x36/0x480 [13551520.973089] [] ? rmap_walk+0x186/0x210 [13551520.974528] [] try_to_unmap_anon+0xa7/0x120 [13551520.975958] [] try_to_unmap+0x4d/0x60 [13551520.977372] [] migrate_pages+0x43e/0x780 [13551520.978769] [] ? isolate_freepages_block+0x310/0x310 [13551520.980165] [] compact_zone+0x299/0x410 [13551520.981549] [] compact_zone_order+0x8e/0xd0 [13551520.982916] [] try_to_compact_pages+0x101/0x180 [13551520.984279] [] __alloc_pages_direct_compact+0xac/0x196 [13551520.985641] [] __alloc_pages_nodemask+0x760/0xb80 [13551520.986971] [] alloc_pages_vma+0x9a/0x140 [13551520.988267] [] do_huge_pmd_anonymous_page+0x10b/0x3f0 [13551520.989540] [] ? __rb_insert_augmented+0x8f/0x1f0 [13551520.990779] [] handle_mm_fault+0x198/0xf10 [13551520.991984] [] ? vma_link+0xb7/0xc0 [13551520.993153] [] __do_page_fault+0x184/0x560 [13551520.994289] [] ? do_mmap_pgoff+0x34e/0x3d0 [13551520.995387] [] ? vm_mmap_pgoff+0x99/0xc0 [13551520.996443] [] do_page_fault+0x1a/0x70 [
[Kernel-packages] [Bug 1522388] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1522388/+attachment/4529320/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522388 Title: Soft Lockup - CPU Stuck Status in linux package in Ubuntu: Confirmed Bug description: The Server was running: * openstack icehouse * Linux 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux(Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16) The kernel log: [13551520.909322] BUG: soft lockup - CPU#4 stuck for 23s! [migration/4:76] [13551520.909357] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev veth ipt_MASQUERA DE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge ip6table_filter ip6_ta bles iptable_filter ip_tables ebtable_nat ebtables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_is csi openvswitch gre vxlan ip_tunnel dm_crypt usb_storage gpio_ich joydev dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul c rc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw ipmi_si sb_edac edac_core mei_me mei lpc_ich shpchp mac_hid k vm_intel kvm 8021q garp stp mrp llc lp parport btrfs xor hid_generic usbhid hid raid6_pq libcrc32c ses enclosure ast syscopyarea sysfillrect sysimgblt ttm psmouse drm_kms _helper isci drm igb ahci libsas dca libahci ptp pps_core scsi_transport_sas i2c_algo_bit megaraid_sas wmi [13551520.909377] CPU: 4 PID: 76 Comm: migration/4 Tainted: G D W 3.13.0-48-generic #80-Ubuntu [13551520.909378] Hardware name: ASUSTek Computer INC. RS720-E7-RS12-E/Z9PE-D16 Series, BIOS 5302 11/08/2013 [13551520.909379] task: 881029391800 ti: 88102938c000 task.ti: 88102938c000 [13551520.909386] RIP: 0010:[] [] multi_cpu_stop+0x6b/0xf0 [13551520.909387] RSP: 0018:88102938dd98 EFLAGS: 0293 [13551520.909388] RAX: 8180ae00 RBX: 88103fc934c0 RCX: 7c34 [13551520.909389] RDX: 0001 RSI: RDI: 881083bd37b8 [13551520.909390] RBP: 88102938ddb8 R08: 0282 R09: 0001 [13551520.909391] R10: b590 R11: R12: 88102938dd20 [13551520.909392] R13: 88035499e000 R14: 81098235 R15: 88035499e000 [13551520.909394] FS: () GS:88103fc8() knlGS: [13551520.909395] CS: 0010 DS: ES: CR0: 80050033 [13551520.909396] CR2: 7f0206b09000 CR3: 0008ee4ad000 CR4: 000427e0 [13551520.909397] Stack: [13551520.909401] 881083bd37e0 88103fc8de20 88103fc8de28 881083bd37b8 [13551520.909404] 88102938de78 810f63de [13551520.909408] 88103fc934c0 881024f38700 88103fc934c0 [13551520.909409] Call Trace: [13551520.909413] [] cpu_stopper_thread+0x7e/0x150 [13551520.909418] [] ? __schedule+0x381/0x7d0 [13551520.909423] [] smpboot_thread_fn+0xff/0x1b0 [13551520.909426] [] ? SyS_setgroups+0x180/0x180 [13551520.909429] [] kthread+0xd2/0xf0 [13551520.909432] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909436] [] ret_from_fork+0x7c/0xb0 [13551520.909439] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909459] Code: 31 f6 31 d2 eb 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 <41> 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 fa 66 66 90 66 66 90 [13551520.971633] [] try_to_unmap_one+0x36/0x480 [13551520.973089] [] ? rmap_walk+0x186/0x210 [13551520.974528] [] try_to_unmap_anon+0xa7/0x120 [13551520.975958] [] try_to_unmap+0x4d/0x60 [13551520.977372] [] migrate_pages+0x43e/0x780 [13551520.978769] [] ? isolate_freepages_block+0x310/0x310 [13551520.980165] [] compact_zone+0x299/0x410 [13551520.981549] [] compact_zone_order+0x8e/0xd0 [13551520.982916] [] try_to_compact_pages+0x101/0x180 [13551520.984279] [] __alloc_pages_direct_compact+0xac/0x196 [13551520.985641] [] __alloc_pages_nodemask+0x760/0xb80 [13551520.986971] [] alloc_pages_vma+0x9a/0x140 [13551520.988267] [] do_huge_pmd_anonymous_page+0x10b/0x3f0 [13551520.989540] [] ? __rb_insert_augmented+0x8f/0x1f0 [13551520.990779] [] handle_mm_fault+0x198/0xf10 [13551520.991984] [] ? vma_link+0xb7/0xc0 [13551520.993153] [] __do_page_fault+0x184/0x560 [13551520.994289] [] ? do_mmap_pgoff+0x34e/0x3d0 [13551520.995387] [] ? vm_mmap_pgoff+0x99/0xc0 [13551520.996443] [] do_page_fault+0x1a/0x70 [13551
[Kernel-packages] [Bug 1522388] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1522388/+attachment/4529322/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522388 Title: Soft Lockup - CPU Stuck Status in linux package in Ubuntu: Confirmed Bug description: The Server was running: * openstack icehouse * Linux 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux(Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16) The kernel log: [13551520.909322] BUG: soft lockup - CPU#4 stuck for 23s! [migration/4:76] [13551520.909357] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev veth ipt_MASQUERA DE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge ip6table_filter ip6_ta bles iptable_filter ip_tables ebtable_nat ebtables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_is csi openvswitch gre vxlan ip_tunnel dm_crypt usb_storage gpio_ich joydev dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul c rc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw ipmi_si sb_edac edac_core mei_me mei lpc_ich shpchp mac_hid k vm_intel kvm 8021q garp stp mrp llc lp parport btrfs xor hid_generic usbhid hid raid6_pq libcrc32c ses enclosure ast syscopyarea sysfillrect sysimgblt ttm psmouse drm_kms _helper isci drm igb ahci libsas dca libahci ptp pps_core scsi_transport_sas i2c_algo_bit megaraid_sas wmi [13551520.909377] CPU: 4 PID: 76 Comm: migration/4 Tainted: G D W 3.13.0-48-generic #80-Ubuntu [13551520.909378] Hardware name: ASUSTek Computer INC. RS720-E7-RS12-E/Z9PE-D16 Series, BIOS 5302 11/08/2013 [13551520.909379] task: 881029391800 ti: 88102938c000 task.ti: 88102938c000 [13551520.909386] RIP: 0010:[] [] multi_cpu_stop+0x6b/0xf0 [13551520.909387] RSP: 0018:88102938dd98 EFLAGS: 0293 [13551520.909388] RAX: 8180ae00 RBX: 88103fc934c0 RCX: 7c34 [13551520.909389] RDX: 0001 RSI: RDI: 881083bd37b8 [13551520.909390] RBP: 88102938ddb8 R08: 0282 R09: 0001 [13551520.909391] R10: b590 R11: R12: 88102938dd20 [13551520.909392] R13: 88035499e000 R14: 81098235 R15: 88035499e000 [13551520.909394] FS: () GS:88103fc8() knlGS: [13551520.909395] CS: 0010 DS: ES: CR0: 80050033 [13551520.909396] CR2: 7f0206b09000 CR3: 0008ee4ad000 CR4: 000427e0 [13551520.909397] Stack: [13551520.909401] 881083bd37e0 88103fc8de20 88103fc8de28 881083bd37b8 [13551520.909404] 88102938de78 810f63de [13551520.909408] 88103fc934c0 881024f38700 88103fc934c0 [13551520.909409] Call Trace: [13551520.909413] [] cpu_stopper_thread+0x7e/0x150 [13551520.909418] [] ? __schedule+0x381/0x7d0 [13551520.909423] [] smpboot_thread_fn+0xff/0x1b0 [13551520.909426] [] ? SyS_setgroups+0x180/0x180 [13551520.909429] [] kthread+0xd2/0xf0 [13551520.909432] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909436] [] ret_from_fork+0x7c/0xb0 [13551520.909439] [] ? kthread_create_on_node+0x1c0/0x1c0 [13551520.909459] Code: 31 f6 31 d2 eb 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 <41> 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 fa 66 66 90 66 66 90 [13551520.971633] [] try_to_unmap_one+0x36/0x480 [13551520.973089] [] ? rmap_walk+0x186/0x210 [13551520.974528] [] try_to_unmap_anon+0xa7/0x120 [13551520.975958] [] try_to_unmap+0x4d/0x60 [13551520.977372] [] migrate_pages+0x43e/0x780 [13551520.978769] [] ? isolate_freepages_block+0x310/0x310 [13551520.980165] [] compact_zone+0x299/0x410 [13551520.981549] [] compact_zone_order+0x8e/0xd0 [13551520.982916] [] try_to_compact_pages+0x101/0x180 [13551520.984279] [] __alloc_pages_direct_compact+0xac/0x196 [13551520.985641] [] __alloc_pages_nodemask+0x760/0xb80 [13551520.986971] [] alloc_pages_vma+0x9a/0x140 [13551520.988267] [] do_huge_pmd_anonymous_page+0x10b/0x3f0 [13551520.989540] [] ? __rb_insert_augmented+0x8f/0x1f0 [13551520.990779] [] handle_mm_fault+0x198/0xf10 [13551520.991984] [] ? vma_link+0xb7/0xc0 [13551520.993153] [] __do_page_fault+0x184/0x560 [13551520.994289] [] ? do_mmap_pgoff+0x34e/0x3d0 [13551520.995387] [] ? vm_mmap_pgoff+0x99/0xc0 [13551520.996443] [] do_page_fault
[Kernel-packages] [Bug 2073267] Re: Guru meditation on VM start
I think the question is what is the correct kernel package to list it against. "linux-signed-hwe-5.15" is a hardware enablement kernel package but the issue is not specific to that build of the kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Guru meditation on VM start Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: It worked yesterday, but today I get a Guru Meditation trying to start some of my virtual machines. This shows up in VBox.log as "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". I suspect this may have started due to a Linux kernel upgrade I installed this morning. A fresh VM with no disk shows the issue. Sometimes turning off the I/O APIC makes the issue go away, sometimes not. Turning off nested paging sometimes lets VirtualBox make a little bit of progress w.r.t. booting VMs, but that usually still crashes before the VM finishes starting. This may be related to this bug reported on the VirtualBox forums: https://forums.virtualbox.org/viewtopic.php?t=111889&sid=5cd33c0872a03b689e7e9f84d850f538 Ubuntu is 22.04.4 LTS, kernel is 5.15.0-116-generic, VirtualBox is 6.1.50-dfsg-1~ubuntu1.22.04.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2073267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2074136] Re: VirtualBox 6.1.5 does not work anymore.
*** This bug is a duplicate of bug 2073267 *** https://bugs.launchpad.net/bugs/2073267 @rickywu: FYI, apport information has been uploaded to the bug that this is a duplicate of, https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2073267, starting at comment #43. -- 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/2074136 Title: VirtualBox 6.1.5 does not work anymore. Status in linux package in Ubuntu: New Bug description: Kernel 5.15.0.116 and 117: VirtualBox 6.1.5 does not work anymore. Ok with Kernel 5.15.0.113 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
Putting Virtualbox 7 into the Ubuntu LTS repos is problematic too, since as per comment #25, that change will also break people's VMs. 5.15 is a LTS kernel version. I think it is reasonable to expect it to continue to support the applications that ran on it at the time it went into LTS, even if those applications are themselves out of support and would not work on the latest kernel. LTS is supposed to be stable, not breaking combinations of things that worked yesterday, at least not without a very good reason. Good luck with the upstream bug, @mapengyu, and thanks for your efforts. It's great to know that the root cause has been isolated, and the possibility of a solution is in sight. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 Status in linux package in Ubuntu: Triaged Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: It worked yesterday, but today I get a Guru Meditation trying to start some of my virtual machines. This shows up in VBox.log as "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". I suspect this may have started due to a Linux kernel upgrade I installed this morning. A fresh VM with no disk shows the issue. Sometimes turning off the I/O APIC makes the issue go away, sometimes not. Turning off nested paging sometimes lets VirtualBox make a little bit of progress w.r.t. booting VMs, but that usually still crashes before the VM finishes starting. This may be related to this bug reported on the VirtualBox forums: https://forums.virtualbox.org/viewtopic.php?t=111889&sid=5cd33c0872a03b689e7e9f84d850f538 Ubuntu is 22.04.4 LTS, kernel is 5.15.0-116-generic, VirtualBox is 6.1.50-dfsg-1~ubuntu1.22.04.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
Though I have to concede, if a change to stack randomization broke Virtualbox (and only Virtualbox), then it suggests perhaps Virtualbox was doing something it shouldn't, and just happened to get away with it all this time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 Status in linux package in Ubuntu: Triaged Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: It worked yesterday, but today I get a Guru Meditation trying to start some of my virtual machines. This shows up in VBox.log as "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". I suspect this may have started due to a Linux kernel upgrade I installed this morning. A fresh VM with no disk shows the issue. Sometimes turning off the I/O APIC makes the issue go away, sometimes not. Turning off nested paging sometimes lets VirtualBox make a little bit of progress w.r.t. booting VMs, but that usually still crashes before the VM finishes starting. This may be related to this bug reported on the VirtualBox forums: https://forums.virtualbox.org/viewtopic.php?t=111889&sid=5cd33c0872a03b689e7e9f84d850f538 Ubuntu is 22.04.4 LTS, kernel is 5.15.0-116-generic, VirtualBox is 6.1.50-dfsg-1~ubuntu1.22.04.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
I tried the workaround suggested by @kees, and it works for me on the latest jammy kernel (now 5.15.0-117). With randomize_kstack_offset not specified on the kernel command line, VMs fail to start with the guru meditation error. With randomize_kstack_offset=off on the kernel command line of the host machine, guest VMs start successfully. This seems like a valuable workaround for any affected users who need other kernel fixes that were made in -116 or -117. If I've understood the discussions correctly, the downside of this approach is that it disables kernel stack offset randomization completely; whereas reverting to the 5.15.0-113 kernel will retain that security safety net, albeit with a reduced level of entropy in the randomization. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Committed Status in linux-signed-hwe-5.15 source package in Jammy: Invalid Status in virtualbox source package in Jammy: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2073267 SRU Justification: [Impact] Commit "randomize_kstack: Improve entropy diffusion" changed the kernel stack for entropy to 1KiB, limiting the thread kernel stack to 15Kib. This impacts virtualbox 6.1.50 on jammy, that is no longer maintained upstream. The issue does not persist on version 7.0.20 due to a code refactoring that probably resulted in less stack usage. Fixing it on the jammy virtualbox package side is not straightfoward because the fix is not easy to backport to 6.x and upgrading the jammy package to 7.x breaks current users machines that run Windows, but not only. Users need to uninstall the Guest additions drivers, migrate the virtualbox package to 7.x, boot each VMs and install the Guest additions drivers in each VM. This impacts: 1. jammy:linux 2. jammy:linux-hwe-6.8 3. focal:linux-hwe-5.15 [Fix] Revert commit "randomize_kstack: Improve entropy diffusion" [Test Plan] Without this fix, a VM would crash, showing with "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". After the kernel upgrade, all VMs should run with no problem. [Where problems could occur] This may have an impact on security. The commit is a fix to improve the stack entropy. Original description: It worked yesterday, but today I get a Guru Meditation trying to start some of my virtual machines. This shows up in VBox.log as "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". I suspect this may have started due to a Linux kernel upgrade I installed this morning. A fresh VM with no disk shows the issue. Sometimes turning off the I/O APIC makes the issue go away, sometimes not. Turning off nested paging sometimes lets VirtualBox make a little bit of progress w.r.t. booting VMs, but that usually still crashes before the VM finishes starting. This may be related to this bug reported on the VirtualBox forums: https://forums.virtualbox.org/viewtopic.php?t=111889&sid=5cd33c0872a03b689e7e9f84d850f538 https://forums.virtualbox.org/viewtopic.php?t=111918 Ubuntu is 22.04.4 LTS, kernel is 5.15.0-116-generic, VirtualBox is 6.1.50-dfsg-1~ubuntu1.22.04.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
Something interesting I came across when looking up the documentation for the randomize_kstack_offset parameter: apparently Virtualbox had a similar problem when this feature was introduced in the 5.13 kernel, and they made a change to fix it in Virtualbox 6.1.24. I wonder what they did? https://www.virtualbox.org/ticket/20452 ** Bug watch added: Virtualbox Trac #20452 http://www.virtualbox.org/ticket/20452 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Committed Status in linux-signed-hwe-5.15 source package in Jammy: Invalid Status in virtualbox source package in Jammy: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2073267 SRU Justification: [Impact] Commit "randomize_kstack: Improve entropy diffusion" changed the kernel stack for entropy to 1KiB, limiting the thread kernel stack to 15Kib. This impacts virtualbox 6.1.50 on jammy, that is no longer maintained upstream. The issue does not persist on version 7.0.20 due to a code refactoring that probably resulted in less stack usage. Fixing it on the jammy virtualbox package side is not straightfoward because the fix is not easy to backport to 6.x and upgrading the jammy package to 7.x breaks current users machines that run Windows, but not only. Users need to uninstall the Guest additions drivers, migrate the virtualbox package to 7.x, boot each VMs and install the Guest additions drivers in each VM. This impacts: 1. jammy:linux 2. jammy:linux-hwe-6.8 3. focal:linux-hwe-5.15 [Fix] Revert commit "randomize_kstack: Improve entropy diffusion" [Test Plan] Without this fix, a VM would crash, showing with "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". After the kernel upgrade, all VMs should run with no problem. [Where problems could occur] This may have an impact on security. The commit is a fix to improve the stack entropy. Original description: It worked yesterday, but today I get a Guru Meditation trying to start some of my virtual machines. This shows up in VBox.log as "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". I suspect this may have started due to a Linux kernel upgrade I installed this morning. A fresh VM with no disk shows the issue. Sometimes turning off the I/O APIC makes the issue go away, sometimes not. Turning off nested paging sometimes lets VirtualBox make a little bit of progress w.r.t. booting VMs, but that usually still crashes before the VM finishes starting. This may be related to this bug reported on the VirtualBox forums: https://forums.virtualbox.org/viewtopic.php?t=111889&sid=5cd33c0872a03b689e7e9f84d850f538 https://forums.virtualbox.org/viewtopic.php?t=111918 Ubuntu is 22.04.4 LTS, kernel is 5.15.0-116-generic, VirtualBox is 6.1.50-dfsg-1~ubuntu1.22.04.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
This Virtualbox ticket contains a diff that looks like it might be the change they did to fix compatibility with RANDOMIZE_KSTACK_OFFSET in the 5.13 kernel. https://www.virtualbox.org/ticket/20456 ** Bug watch added: Virtualbox Trac #20456 http://www.virtualbox.org/ticket/20456 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Committed Status in linux-signed-hwe-5.15 source package in Jammy: Invalid Status in virtualbox source package in Jammy: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2073267 SRU Justification: [Impact] Commit "randomize_kstack: Improve entropy diffusion" changed the kernel stack for entropy to 1KiB, limiting the thread kernel stack to 15Kib. This impacts virtualbox 6.1.50 on jammy, that is no longer maintained upstream. The issue does not persist on version 7.0.20 due to a code refactoring that probably resulted in less stack usage. Fixing it on the jammy virtualbox package side is not straightfoward because the fix is not easy to backport to 6.x and upgrading the jammy package to 7.x breaks current users machines that run Windows, but not only. Users need to uninstall the Guest additions drivers, migrate the virtualbox package to 7.x, boot each VMs and install the Guest additions drivers in each VM. This impacts: 1. jammy:linux 2. jammy:linux-hwe-6.8 3. focal:linux-hwe-5.15 [Fix] Revert commit "randomize_kstack: Improve entropy diffusion" [Test Plan] Without this fix, a VM would crash, showing with "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". After the kernel upgrade, all VMs should run with no problem. [Where problems could occur] This may have an impact on security. The commit is a fix to improve the stack entropy. Original description: It worked yesterday, but today I get a Guru Meditation trying to start some of my virtual machines. This shows up in VBox.log as "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". I suspect this may have started due to a Linux kernel upgrade I installed this morning. A fresh VM with no disk shows the issue. Sometimes turning off the I/O APIC makes the issue go away, sometimes not. Turning off nested paging sometimes lets VirtualBox make a little bit of progress w.r.t. booting VMs, but that usually still crashes before the VM finishes starting. This may be related to this bug reported on the VirtualBox forums: https://forums.virtualbox.org/viewtopic.php?t=111889&sid=5cd33c0872a03b689e7e9f84d850f538 https://forums.virtualbox.org/viewtopic.php?t=111918 Ubuntu is 22.04.4 LTS, kernel is 5.15.0-116-generic, VirtualBox is 6.1.50-dfsg-1~ubuntu1.22.04.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
That's right, it was a fix for a Virtualbox error that arose when kernel stack randomization was first introduced in the 5.13 kernel. My speculation was that it might have been a similar issue, and if so, its fix might give a clue to a way to fix the current issue in Virtualbox. One might naively observe that when the available kernel stack space was reduced by 0.25kb in kernel 5.13, Virtualbox was fixed by adding 256 to STACK_FUZZ_SIZE. Now kernel 5.15.0-116 has reduced the available stack space by another 0.75kb; could Virtualbox be fixed by adding another 768 to STACK_FUZZ_SIZE? I don't know enough about what's going on under the hood to know if that's even plausible, or what undesirable side effects it might have. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Committed Status in linux-signed-hwe-5.15 source package in Jammy: Invalid Status in virtualbox source package in Jammy: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2073267 SRU Justification: [Impact] Commit "randomize_kstack: Improve entropy diffusion" changed the kernel stack for entropy to 1KiB, limiting the thread kernel stack to 15Kib. This impacts virtualbox 6.1.50 on jammy, that is no longer maintained upstream. The issue does not persist on version 7.0.20 due to a code refactoring that probably resulted in less stack usage. Fixing it on the jammy virtualbox package side is not straightfoward because the fix is not easy to backport to 6.x and upgrading the jammy package to 7.x breaks current users machines that run Windows, but not only. Users need to uninstall the Guest additions drivers, migrate the virtualbox package to 7.x, boot each VMs and install the Guest additions drivers in each VM. This impacts: 1. jammy:linux 2. jammy:linux-hwe-6.8 3. focal:linux-hwe-5.15 [Fix] Revert commit "randomize_kstack: Improve entropy diffusion" [Test Plan] Without this fix, a VM would crash, showing with "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". After the kernel upgrade, all VMs should run with no problem. [Where problems could occur] This may have an impact on security. The commit is a fix to improve the stack entropy. Original description: It worked yesterday, but today I get a Guru Meditation trying to start some of my virtual machines. This shows up in VBox.log as "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". I suspect this may have started due to a Linux kernel upgrade I installed this morning. A fresh VM with no disk shows the issue. Sometimes turning off the I/O APIC makes the issue go away, sometimes not. Turning off nested paging sometimes lets VirtualBox make a little bit of progress w.r.t. booting VMs, but that usually still crashes before the VM finishes starting. This may be related to this bug reported on the VirtualBox forums: https://forums.virtualbox.org/viewtopic.php?t=111889&sid=5cd33c0872a03b689e7e9f84d850f538 https://forums.virtualbox.org/viewtopic.php?t=111918 Ubuntu is 22.04.4 LTS, kernel is 5.15.0-116-generic, VirtualBox is 6.1.50-dfsg-1~ubuntu1.22.04.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
@Detlef: There are a number of workarounds to address this problem while waiting for the long-term fix in the -119 kernel. You can change your grub configuration to either boot an older kernel by default, or to add randomize_kstack_offset=off to the kernel command line (see comment #85). Alternatively, use apt to uninstall the recent kernel and revert to the -113 kernel. All 3 of these options work equally well so it's just a question of which one you find most convenient. Note that this specific bug has been precisely traced to a change introduced in the 5.15.0-116 kernel, so any problems you've had with any earlier kernel versions are a different issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Committed Status in linux-signed-hwe-5.15 source package in Jammy: Invalid Status in virtualbox source package in Jammy: Confirmed Bug description: BugLink: https://bugs.launchpad.net/bugs/2073267 SRU Justification: [Impact] Commit "randomize_kstack: Improve entropy diffusion" changed the kernel stack for entropy to 1KiB, limiting the thread kernel stack to 15Kib. This impacts virtualbox 6.1.50 on jammy, that is no longer maintained upstream. The issue does not persist on version 7.0.20 due to a code refactoring that probably resulted in less stack usage. Fixing it on the jammy virtualbox package side is not straightfoward because the fix is not easy to backport to 6.x and upgrading the jammy package to 7.x breaks current users machines that run Windows, but not only. Users need to uninstall the Guest additions drivers, migrate the virtualbox package to 7.x, boot each VMs and install the Guest additions drivers in each VM. This impacts: 1. jammy:linux 2. jammy:linux-hwe-6.8 3. focal:linux-hwe-5.15 [Fix] Revert commit "randomize_kstack: Improve entropy diffusion" [Test Plan] Without this fix, a VM would crash, showing with "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". After the kernel upgrade, all VMs should run with no problem. [Where problems could occur] This may have an impact on security. The commit is a fix to improve the stack entropy. Original description: It worked yesterday, but today I get a Guru Meditation trying to start some of my virtual machines. This shows up in VBox.log as "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". I suspect this may have started due to a Linux kernel upgrade I installed this morning. A fresh VM with no disk shows the issue. Sometimes turning off the I/O APIC makes the issue go away, sometimes not. Turning off nested paging sometimes lets VirtualBox make a little bit of progress w.r.t. booting VMs, but that usually still crashes before the VM finishes starting. This may be related to this bug reported on the VirtualBox forums: https://forums.virtualbox.org/viewtopic.php?t=111889&sid=5cd33c0872a03b689e7e9f84d850f538 https://forums.virtualbox.org/viewtopic.php?t=111918 Ubuntu is 22.04.4 LTS, kernel is 5.15.0-116-generic, VirtualBox is 6.1.50-dfsg-1~ubuntu1.22.04.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Re: NFSv4 performance problem with newer kernels
apport-collect 1960826 just writings out "." endlessly. The documentation says that apport-bug collects the same info so I have manually created a file locally which I have attached here. HTH, if something else is required please let me know. ** Attachment added: "1960826.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+attachment/5561011/+files/1960826.apport ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Re: NFSv4 performance problem with newer kernels
apport information ** Tags added: apport-collected focal uec-images ** Description changed: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 - The problem is seen on dissimilar hardware, ie this problem exists when - testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to - Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet - connected to a Netgear switch (just to name two of several - configurations that have been tested). The clients vary in each test - case also, but are desktop PCs and laptops. + The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq + crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2022-02-14 (0 days ago) + InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: Dell Inc. PowerEdge R430 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 mgag200drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro + ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-28-generic N/A + linux-backports-modules-5.13.0-28-generic N/A + linux-firmware 1.187.26 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.13.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 06/07/2021 + dmi.bios.release: 2.13 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 2.13.0 + dmi.board.name: 0CN7X8 + dmi.board.vendor: Dell Inc. + dmi.board.version: A04 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: + dmi.product.name: PowerEdge R430 + dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 + dmi.sys.vendor: Dell Inc. ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561012/+files/CRDA.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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is conne
[Kernel-packages] [Bug 1960826] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561013/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561017/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561015/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561016/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561014/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561023/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561021/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561025/+files/acpidump.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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561018/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561020/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561022/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561024/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561019/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Re: NFSv4 performance problem with newer kernels
I have found the root cause, in my test environment the clients are all clones with unique machine-id but the same hostname. The issue is resolve by either changing the hostname of each client, or by setting a unique value here: echo options nfs nfs4_unique_id=[string] > /etc/modprobe.d/nfsclient.conf In my production environment the clients all share the same NFS root, and I'm not sure how to set a random value in nfsclient.conf (I tried nfs4_unique_id=`cat /proc/sys/kernel/random/uuid` but this doesn't work). Currently I can work around by setting a random hostname. If anyone can suggest how to do this via nfsclient.conf instead that might be neater. -- 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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/
[Kernel-packages] [Bug 1960826] Re: NFSv4 performance problem with newer kernels
OK, to set a random nfs4_unique_id you can just cat/echo a string like this: cat /proc/sys/kernel/random/uuid |tr -d '\n' > /sys/module/nfs/parameters/nfs4_unique_id so long as you do this before your first NFS mount, which in my case is not a problem. -- 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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Re: NFSv4 performance problem with newer kernels
so as not to duplicate effort, I see there is a request for enhancement over at Redhat: https://bugzilla.redhat.com/show_bug.cgi?id=1801326 ** Bug watch added: Red Hat Bugzilla #1801326 https://bugzilla.redhat.com/show_bug.cgi?id=1801326 -- 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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025560] Re: lubuntu does not boot after upgrade
** Attachment added: "IMG_20230703_003916.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025560/+attachment/5683463/+files/IMG_20230703_003916.jpg -- 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/2025560 Title: lubuntu does not boot after upgrade Status in linux package in Ubuntu: New Bug description: lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 This morning upgrade installed a bunch of new kernels which made my computer unbootable. Manged to boot with old kernel: 5.15.0-76-generic, and none of new ones work. From /var/log/apt/history.log: Start-Date: 2023-07-02 12:06:38 Commandline: aptdaemon role='role-upgrade-system' sender=':1.69' Install: linux-modules-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1, automatic), linux-objects-nvidia-535-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-6.1.0-1015-oem:amd64 (6.1.0-1015.15+2, automatic), linux-image-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-signatures-nvidia-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), dctrl-tools:amd64 (2.24-3build2, automatic), linux-signatures-nvidia-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-modules-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-image- 5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic), linux-modules-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), nvidia-firmware-535-535.54.03:amd64 (535.54.03-0ubuntu0.22.04.1, automatic), linux-modules-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-objects-nvidia-535-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-image-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), linux-signatures-nvidia-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-objects-nvidia-535-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-objects-nvidia-535-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-6.1.0-1015-oem:amd64 (6.1.0-1015.15, automatic), linux-image-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), linux-image-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-image-5.19.0-1026-oracle:amd64 (5.19.0- 1026.29~22.04.1, automatic), linux-modules-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), linux-objects-nvidia-535-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-image-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-objects-nvidia-535-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-modules-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), dkms:amd64 (2.8.7-2ubuntu2.1, automatic), linux-modules-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-modules-5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic) Works to start in recovery mode on any kernel and guessing that the problem is related to the nvidia-driver, which is native: neofetch `-mddhddmss` kris@lubuntu ./mdhh. :mdhhhm` OS: Lubuntu 22.04.2 LTS x86_64 :ymhhhyyhy: Kernel: 5.15.0-76-generic `odhyyyhy+-./syo` Uptime: 22 mins `hhy..:oyhhhy-`:osso/..:/++oosyyyh`Packages: 2100 (dpkg), 13 (snap) dhhs .-/sys`shhhsShell: bash 5.1.16 :hhhy` yso/:+syhy/yhshh: Resolution: 1920x1080, 1920x1080, 1920x1080 ho. +hhhys++oyyyh-yhs DE: LXQt 0.17.1
[Kernel-packages] [Bug 2025560] Re: lubuntu does not boot after upgrade
Same problem here with lubuntu 22.04. Last night I did the updates Unfortunately, as of today I cannot boot either in the new 5.19 lowlatency nvidia or 5.15.0.76 generic or anywhere else I can enter safe mode, but do not know what to do there When trying to boot in 5.19 the attached img appears and halts When trying to boot in 5.15, the system just halts - blank screen ** Attachment added: "IMG_20230703_003916.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025560/+attachment/5683464/+files/IMG_20230703_003916.jpg -- 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/2025560 Title: lubuntu does not boot after upgrade Status in linux package in Ubuntu: New Bug description: lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 This morning upgrade installed a bunch of new kernels which made my computer unbootable. Manged to boot with old kernel: 5.15.0-76-generic, and none of new ones work. From /var/log/apt/history.log: Start-Date: 2023-07-02 12:06:38 Commandline: aptdaemon role='role-upgrade-system' sender=':1.69' Install: linux-modules-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1, automatic), linux-objects-nvidia-535-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-6.1.0-1015-oem:amd64 (6.1.0-1015.15+2, automatic), linux-image-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-signatures-nvidia-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), dctrl-tools:amd64 (2.24-3build2, automatic), linux-signatures-nvidia-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-modules-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-image- 5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic), linux-modules-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), nvidia-firmware-535-535.54.03:amd64 (535.54.03-0ubuntu0.22.04.1, automatic), linux-modules-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-objects-nvidia-535-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-image-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), linux-signatures-nvidia-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-objects-nvidia-535-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-objects-nvidia-535-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-6.1.0-1015-oem:amd64 (6.1.0-1015.15, automatic), linux-image-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), linux-image-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-image-5.19.0-1026-oracle:amd64 (5.19.0- 1026.29~22.04.1, automatic), linux-modules-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), linux-objects-nvidia-535-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-image-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-objects-nvidia-535-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-modules-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), dkms:amd64 (2.8.7-2ubuntu2.1, automatic), linux-modules-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-modules-5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic) Works to start in recovery mode on any kernel and guessing that the problem is related to the nvidia-driver, which is native: neofetch `-mddhddmss` kris@lubuntu ./mdhh. :mdhhhm` OS: Lubuntu 22.04.2 LTS x86_64 :ymhhhyyhy: Kernel: 5.15.0-76-generic `odhyyyhy+-./syo` Uptime: 22 mins `hhy..:oyhhhy-`:osso/..:/++oosyyyh`Packages: 2100 (dpkg), 13 (snap) dhhs .-/sys`shhhsShell: bash 5.1
[Kernel-packages] [Bug 2025560] Re: lubuntu does not boot after upgrade
Kerjes thanks a lot for the info Worked for me as well! -- 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/2025560 Title: lubuntu does not boot after upgrade Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 This morning upgrade installed a bunch of new kernels which made my computer unbootable. Manged to boot with old kernel: 5.15.0-76-generic, and none of new ones work. From /var/log/apt/history.log: Start-Date: 2023-07-02 12:06:38 Commandline: aptdaemon role='role-upgrade-system' sender=':1.69' Install: linux-modules-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1, automatic), linux-objects-nvidia-535-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-6.1.0-1015-oem:amd64 (6.1.0-1015.15+2, automatic), linux-image-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-signatures-nvidia-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), dctrl-tools:amd64 (2.24-3build2, automatic), linux-signatures-nvidia-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-modules-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-image- 5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic), linux-modules-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), nvidia-firmware-535-535.54.03:amd64 (535.54.03-0ubuntu0.22.04.1, automatic), linux-modules-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-objects-nvidia-535-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-image-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), linux-signatures-nvidia-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-objects-nvidia-535-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-objects-nvidia-535-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-6.1.0-1015-oem:amd64 (6.1.0-1015.15, automatic), linux-image-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), linux-image-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-image-5.19.0-1026-oracle:amd64 (5.19.0- 1026.29~22.04.1, automatic), linux-modules-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), linux-objects-nvidia-535-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-image-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-objects-nvidia-535-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-modules-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), dkms:amd64 (2.8.7-2ubuntu2.1, automatic), linux-modules-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-modules-5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic) Works to start in recovery mode on any kernel and guessing that the problem is related to the nvidia-driver, which is native: neofetch `-mddhddmss` kris@lubuntu ./mdhh. :mdhhhm` OS: Lubuntu 22.04.2 LTS x86_64 :ymhhhyyhy: Kernel: 5.15.0-76-generic `odhyyyhy+-./syo` Uptime: 22 mins `hhy..:oyhhhy-`:osso/..:/++oosyyyh`Packages: 2100 (dpkg), 13 (snap) dhhs .-/sys`shhhsShell: bash 5.1.16 :hhhy` yso/:+syhy/yhshh: Resolution: 1920x1080, 1920x1080, 1920x1080 ho. +hhhys++oyyyh-yhs DE: LXQt 0.17.1 hhs-`/syyssyy:-yh WM: Openbox
[Kernel-packages] [Bug 1834926] Re: linux-oem: 4.15.0-1046.51 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1834926 Title: linux-oem: 4.15.0-1046.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Promote to Proposed phase-changed: Thursday, 04. July 2019 10:38 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834941] Re: linux-ibm-gt: 4.15.0-1027.29 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1834941 Title: linux-ibm-gt: 4.15.0-1027.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Promote to Proposed phase-changed: Friday, 05. July 2019 06:39 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835270] Re: linux: 3.2.0-142.189 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1835270 Title: linux: 3.2.0-142.189 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Saturday, 06. July 2019 11:03 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835436] Re: linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1835436 Title: linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835438 phase: Ready for Promote to Proposed phase-changed: Friday, 05. July 2019 14:14 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834950] Re: linux-azure: 4.15.0-1051.56 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1834950 Title: linux-azure: 4.15.0-1051.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834948 (trusty/linux-azure) derivatives: bug 1834945 (azure-kernel), bug 1834946 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Promote to Proposed phase-changed: Wednesday, 10. July 2019 13:13 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834948] Re: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1834948 Title: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834950 phase: Promote to Proposed phase-changed: Wednesday, 10. July 2019 13:40 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834948] Re: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834948 Title: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834950 phase: Promote to Proposed phase-changed: Wednesday, 10. July 2019 14:50 UTC reason: promote-signing-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834925] Re: linux-snapdragon: 4.15.0-1058.64 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834925 Title: linux-snapdragon: 4.15.0-1058.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834924 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Promote to Proposed phase-changed: Thursday, 11. July 2019 11:10 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835112] Re: linux-fips: 4.15.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835112 Title: linux-fips: 4.15.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Testing phase-changed: Monday, 08. July 2019 10:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834925] Re: linux-snapdragon: 4.15.0-1058.64 -proposed tracker
** Changed in: linux-snapdragon (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834925 Title: linux-snapdragon: 4.15.0-1058.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834924 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Thursday, 11. July 2019 13:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834925] Re: linux-snapdragon: 4.15.0-1058.64 -proposed tracker
** Changed in: linux-snapdragon (Ubuntu Bionic) Status: Confirmed => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834925 Title: linux-snapdragon: 4.15.0-1058.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834924 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Thursday, 11. July 2019 13:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834925] Re: linux-snapdragon: 4.15.0-1058.64 -proposed tracker
** Changed in: linux-snapdragon (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834925 Title: linux-snapdragon: 4.15.0-1058.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834924 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Thursday, 11. July 2019 13:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.60 -proposed tracker
** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834954 Title: linux: 4.15.0-55.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe) derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 (linux-oem) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 03. July 2019 13:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834925] Re: linux-snapdragon: 4.15.0-1058.64 -proposed tracker
** Tags added: kernel-fake-testing-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834925 Title: linux-snapdragon: 4.15.0-1058.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834924 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Thursday, 11. July 2019 13:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834944] Re: linux-fips: 4.15.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834944 Title: linux-fips: 4.15.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834954 phase: Packaging phase-changed: Tuesday, 09. July 2019 15:42 UTC reason: prepare-package: Pending -- package tag not yet published prepare-package-signed: Pending -- package tag not yet published promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834464] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.3 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 and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1834464 Title: Missing bluetooth firmware for Intel Wireless-AC 9462/9560 Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: In Progress Bug description: [Impact] Bluetooth on Intel Wireless-AC 9462/9560 requires new firmware blobs to be enabled. [Fix] Backport newly released firmware blobs from linux-firmware. This will also requires minor change to the WHENCE file to resolve cherry-pick conflicts. B/C/D would requires this explicitly and Eoan should be rebased onto linux-firmware master branch HEAD as usual. [Test Case] Verified with hardware platforms with corresponding devices. Completely power off and power on to trigger firmware reload, check from dmesg to see if Bluetooth firmware has been correctly loaded. [Regression Risk] Low. This adds new binary firmware blobs that are only loaded by targeting hardware. == original bug description == On systems with Intel Wireless-AC 9462/9560 cards, following failed- to-load-firmware kernel messages found: bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi failed with error -2 See also Bug #1833065 for wireless firmware & driver fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835345] Please test proposed package
Hello AceLan, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.3 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 and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1835345 Title: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] BT fails to enable again after disabled it by hotkey with the following message Bus 001 Device 004: ID 8087:0029 Intel Corp. [248987.643125] usb 1-10: device descriptor read/64, error -110 [249003.247721] usb 1-10: device descriptor read/64, error -110 [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249018.855466] usb 1-10: device descriptor read/64, error -110 [249034.467589] usb 1-10: device descriptor read/64, error -110 [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249045.299399] usb 1-10: device not accepting address 4, error -62 [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249050.675715] usb 1-10: Device not responding to setup address. [249050.883541] usb 1-10: device not accepting address 4, error -71 [Fix] Found the updated firmware fixes the issue [Test] Verify on the machine couple days, and can't duplicate the issue anymore. [Regression Potential] Low, the system keeps running for 5 days, and pass s3 tests 30 times, everything works well. [Misc] The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards require the new fw_revision, so SRU both of them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834464] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.9 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 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1834464 Title: Missing bluetooth firmware for Intel Wireless-AC 9462/9560 Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: In Progress Bug description: [Impact] Bluetooth on Intel Wireless-AC 9462/9560 requires new firmware blobs to be enabled. [Fix] Backport newly released firmware blobs from linux-firmware. This will also requires minor change to the WHENCE file to resolve cherry-pick conflicts. B/C/D would requires this explicitly and Eoan should be rebased onto linux-firmware master branch HEAD as usual. [Test Case] Verified with hardware platforms with corresponding devices. Completely power off and power on to trigger firmware reload, check from dmesg to see if Bluetooth firmware has been correctly loaded. [Regression Risk] Low. This adds new binary firmware blobs that are only loaded by targeting hardware. == original bug description == On systems with Intel Wireless-AC 9462/9560 cards, following failed- to-load-firmware kernel messages found: bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi failed with error -2 See also Bug #1833065 for wireless firmware & driver fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836372] Re: Update firmware in nic-firmware udeb for 5.0 hwe kernel
Hello Seth, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.9 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 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. ** Changed in: linux-firmware (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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836372 Title: Update firmware in nic-firmware udeb for 5.0 hwe kernel Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Bug description: SRU Justification Impact: Recent updates to linux-firmware means that there are new and updated firmware files relevant to the 5.0 hwe kernel from disco. Adding these files to give a better install experience for the 18.04.3 release. Fix: Add the new firmware files to the nic-firmware udeb. Test Case: Confirm that the new files are present in the nic-firmware udeb. Regression Potential: New firmware versions could contain regressions. These versions have already been released into bionic with no reported regressions though, and are known to fix actual problems, so the benefit seems to outweigh the potential risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835449] Please test proposed package
Hello Vincent, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.9 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 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1835449 Title: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9260) Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Bug description: [Impact] Intel Wireless-AC 9260 Bluetooth doesn't pair to Bluetooth 5.0 HID devices. [Fix] Bluetooth FW Build REL0329 or newer is known to have fixed this problem on Cosmic, and for Disco we have REL0420. On Bionic and Xenial it takes a firmware backport from upstream commit c2d8f1b7f820b31b6120d741c23db23340a72821. Original patch modified to fix conflicts in the WHENCE file. [Test Case] Verified on hardware platforms with Intel Wireless AC 9260 installed, e.g. Dell Precision 7530. Copied the two blobs to /lib/firmware/intel and power off the device completely to trigger firmware reload at the next boot. [Regression Risk] Low. Tried following kernels with REL0329 firmware blobs: * 4.4.0-154-generic: Xenial, WiFi/Bluetooth doesn't work * 4.8.0-58-generic: Xenial, even doesn't boot to console * 4.10.0-42-generic: Xenial, WiFi/Bluetooth doesn't work * 4.11.0-14-generic: Xenial, WiFi/Bluetooth doesn't work * 4.13.0-45-generic: Xenial * 4.15.0-54-generic: Xenial, Bionic * 4.15.0-1043-oem: Xenial, Bionic For those WiFi/Bluetooth doesn't work versions, WiFi/Bluetooth doesn't work even with current firmware blobs shipped in Xenial's linux-firmware REL0186. So overall, these updated blobs are only loaded by hardware requires them, and they doesn't bring harm to known working configurations. Original Bug Description Same problem exactly as encountered with Intel 9560 is also happening with Intel 9260. Update to linux-firmware 1.173.8 did not fix the problem. Everything is working fine when using 4.15 kernel, but not for 4.18+ 5.0+. Reference problem: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1829737 You-Sheng Yang advised to do this by email and it fixed my issue, so I think the 9260 driver would need to be updated in the bionic branch (it seems to be updated in newer branches). -- Basically you should try copy the latest firmware (ibt-*) under https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel , power off the device completely and power on, then have a check on bluetooth pairing. -- Linux ideapad 5.0.0-20-generic #21~18.04.1-Ubuntu SMP Thu Jun 27 04:04:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux OS: Linux Mint 19.1 Tessa x86_64 Host: 81JB Lenovo ideapad 730S-13IWL Wifi/Bluetooth card is Intel 9260 @:/etc$ dmesg | egrep -i 'blue|firm' [0.099619] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.173124] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.379392] [Firmware Bug]: Invalid critical threshold (0) [2.699758] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [6.259427] iwlwifi :73:00.0: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [6.337749] Bluetooth: Core ver 2.22 [6.337767] Bluetooth: HCI device and connection manager initialized [6.337770] Bluetooth: HCI socket layer initialized [6.337773] Bluetooth: L2CAP socket layer initialized [6.33] Bluetooth: SCO socket layer initialized [6.368073] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [7.309936] Bluetooth: BNEP (Ethernet E
[Kernel-packages] [Bug 1835345] Please test proposed package
Hello AceLan, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.9 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 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1835345 Title: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] BT fails to enable again after disabled it by hotkey with the following message Bus 001 Device 004: ID 8087:0029 Intel Corp. [248987.643125] usb 1-10: device descriptor read/64, error -110 [249003.247721] usb 1-10: device descriptor read/64, error -110 [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249018.855466] usb 1-10: device descriptor read/64, error -110 [249034.467589] usb 1-10: device descriptor read/64, error -110 [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249045.299399] usb 1-10: device not accepting address 4, error -62 [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249050.675715] usb 1-10: Device not responding to setup address. [249050.883541] usb 1-10: device not accepting address 4, error -71 [Fix] Found the updated firmware fixes the issue [Test] Verify on the machine couple days, and can't duplicate the issue anymore. [Regression Potential] Low, the system keeps running for 5 days, and pass s3 tests 30 times, everything works well. [Misc] The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards require the new fw_revision, so SRU both of them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835449] Please test proposed package
Hello Vincent, or anyone else affected, Accepted linux-firmware into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.157.22 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 and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1835449 Title: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9260) Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Bug description: [Impact] Intel Wireless-AC 9260 Bluetooth doesn't pair to Bluetooth 5.0 HID devices. [Fix] Bluetooth FW Build REL0329 or newer is known to have fixed this problem on Cosmic, and for Disco we have REL0420. On Bionic and Xenial it takes a firmware backport from upstream commit c2d8f1b7f820b31b6120d741c23db23340a72821. Original patch modified to fix conflicts in the WHENCE file. [Test Case] Verified on hardware platforms with Intel Wireless AC 9260 installed, e.g. Dell Precision 7530. Copied the two blobs to /lib/firmware/intel and power off the device completely to trigger firmware reload at the next boot. [Regression Risk] Low. Tried following kernels with REL0329 firmware blobs: * 4.4.0-154-generic: Xenial, WiFi/Bluetooth doesn't work * 4.8.0-58-generic: Xenial, even doesn't boot to console * 4.10.0-42-generic: Xenial, WiFi/Bluetooth doesn't work * 4.11.0-14-generic: Xenial, WiFi/Bluetooth doesn't work * 4.13.0-45-generic: Xenial * 4.15.0-54-generic: Xenial, Bionic * 4.15.0-1043-oem: Xenial, Bionic For those WiFi/Bluetooth doesn't work versions, WiFi/Bluetooth doesn't work even with current firmware blobs shipped in Xenial's linux-firmware REL0186. So overall, these updated blobs are only loaded by hardware requires them, and they doesn't bring harm to known working configurations. Original Bug Description Same problem exactly as encountered with Intel 9560 is also happening with Intel 9260. Update to linux-firmware 1.173.8 did not fix the problem. Everything is working fine when using 4.15 kernel, but not for 4.18+ 5.0+. Reference problem: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1829737 You-Sheng Yang advised to do this by email and it fixed my issue, so I think the 9260 driver would need to be updated in the bionic branch (it seems to be updated in newer branches). -- Basically you should try copy the latest firmware (ibt-*) under https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel , power off the device completely and power on, then have a check on bluetooth pairing. -- Linux ideapad 5.0.0-20-generic #21~18.04.1-Ubuntu SMP Thu Jun 27 04:04:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux OS: Linux Mint 19.1 Tessa x86_64 Host: 81JB Lenovo ideapad 730S-13IWL Wifi/Bluetooth card is Intel 9260 @:/etc$ dmesg | egrep -i 'blue|firm' [0.099619] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.173124] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.379392] [Firmware Bug]: Invalid critical threshold (0) [2.699758] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [6.259427] iwlwifi :73:00.0: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [6.337749] Bluetooth: Core ver 2.22 [6.337767] Bluetooth: HCI device and connection manager initialized [6.337770] Bluetooth: HCI socket layer initialized [6.337773] Bluetooth: L2CAP socket layer initialized [6.33] Bluetooth: SCO socket layer initialized [6.368073] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [7.309936] Bluetooth: BNEP (Ethernet
[Kernel-packages] [Bug 1834944] Re: linux-fips: 4.15.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1834944 Title: linux-fips: 4.15.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Promote to Proposed phase-changed: Friday, 12. July 2019 16:12 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1836202 Title: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 13:10 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.19 -proposed tracker
** Tags added: kernel-block-ppa -- 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/1834915 Title: linux-fips: 4.4.0-1014.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 10:05 UTC reason: promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836880] Re: linux: 4.4.0-156.183 -proposed tracker
** Changed in: linux (Ubuntu Xenial) 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/1836880 Title: linux: 4.4.0-156.183 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836879 (trusty/linux-lts-xenial) derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 (linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 (linux-snapdragon) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 12:03 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836876] Re: linux-raspi2: 4.4.0-1116.125 -proposed tracker
** Changed in: linux-raspi2 (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1836876 Title: linux-raspi2: 4.4.0-1116.125 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836875 (pi2-kernel) -- swm properties -- kernel-stable-master-bug: 1836880 phase: Packaging phase-changed: Wednesday, 17. July 2019 12:48 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker
** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836202 Title: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 phase: Testing phase-changed: Tuesday, 16. July 2019 16:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- Nvidia objects not found -- current-driver-5.0.0-1011-gke-d1809-0-amd64 regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836172] Re: linux-oem: -proposed tracker
** Changed in: linux-oem (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1836172 Title: linux-oem: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834954 phase: Ready for Packaging phase-changed: Thursday, 11. July 2019 08:48 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836878] Re: linux-snapdragon: -proposed tracker
** Changed in: linux-snapdragon (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1836878 Title: linux-snapdragon: 4.4.0-1120.126 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836877 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1836880 phase: Ready for Packaging phase-changed: Wednesday, 17. July 2019 12:11 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835189] Re: linux-lts-trusty: 3.13.0-172.223~12.04.1 -proposed tracker
** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1835189 Title: linux-lts-trusty: 3.13.0-172.223~12.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835190 phase: Ready for Testing phase-changed: Thursday, 11. July 2019 18:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834935] Re: linux-gcp: 4.15.0-1037.39~16.04.1 -proposed tracker
** Changed in: linux-gcp (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834935 Title: linux-gcp: 4.15.0-1037.39~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834932 (gcp-kernel), bug 1834934 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834936 phase: Ready for Testing phase-changed: Thursday, 11. July 2019 00:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834943] Re: linux-oracle: 4.15.0-1018.20 -proposed tracker
** Changed in: linux-oracle (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1834943 Title: linux-oracle: 4.15.0-1018.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834942 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834950] Re: linux-azure: 4.15.0-1051.56 -proposed tracker
** Changed in: linux-azure (Ubuntu Xenial) Status: New => Confirmed -- 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/1834950 Title: linux-azure: 4.15.0-1051.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834948 (trusty/linux-azure) derivatives: bug 1834945 (azure-kernel), bug 1834946 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834904] Re: linux: 4.18.0-26.27 -proposed tracker
** Changed in: linux (Ubuntu Cosmic) 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/1834904 Title: linux: 4.18.0-26.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834880 (linux-raspi2), bug 1834883 (linux-aws), bug 1834899 (linux-gcp), bug 1834901 (linux-kvm), bug 1835438 (linux- azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 12. July 2019 20:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834902] Re: linux: 5.0.0-21.22 -proposed tracker
** Changed in: linux (Ubuntu Disco) 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/1834902 Title: linux: 5.0.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835388 (bionic/linux-hwe), bug 1836856 (bionic/linux-oem-osp1) derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 12. July 2019 20:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.19 -proposed tracker
** Changed in: linux (Ubuntu Xenial) 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/1834915 Title: linux-fips: 4.4.0-1014.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1836880 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 10:05 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834923] Re: linux-raspi2: 4.15.0-1041.44 -proposed tracker
** Changed in: linux-raspi2 (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1834923 Title: linux-raspi2: 4.15.0-1041.44 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834922 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Thursday, 11. July 2019 00:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834936] Re: linux-gcp: 4.15.0-1037.39 -proposed tracker
** Changed in: linux-gcp (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834936 Title: linux-gcp: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834935 (xenial/linux-gcp) derivatives: bug 1834931 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Wednesday, 03. July 2019 22:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834891] Re: linux-gcp: 5.0.0-1011.11 -proposed tracker
** Changed in: linux-gcp (Ubuntu Disco) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834891 Title: linux-gcp: 5.0.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835904 (bionic/linux-gcp-edge), bug 1836202 (bionic /linux-gke-5.0) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Changed in: linux (Ubuntu Trusty) 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/1835190 Title: linux: 3.13.0-172.223 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Thursday, 11. July 2019 19:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834942] Re: linux-oracle: 4.15.0-1018.20~16.04.1 -proposed tracker
** Changed in: linux-oracle (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1834942 Title: linux-oracle: 4.15.0-1018.20~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834943 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834899] Re: linux-gcp: 4.18.0-1016.17 -proposed tracker
** Changed in: linux-gcp (Ubuntu Cosmic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834899 Title: linux-gcp: 4.18.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Holding before Release phase-changed: Thursday, 11. July 2019 17:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
