[Kernel-packages] [Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"
> I'll file a ticket with IS for their input... Canonical staff can see this at rt #130839 -- 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/1926955 Title: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x9BC11F38" Status in edk2 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 Steps to reproduce: 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). 2. Wait for it to come up, and then issue `sudo reboot` 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"
On Wed, May 05, 2021 at 03:12:43PM -, dann frazier wrote: > On ARM, accelerated guests have the host interrupt controller somewhat > "passed through". I say that while vigorously waving my hands because I > don't recall the details well - but I do know that we needed to teach > the entire stack (host kernel -> QEMU -> edk2) about GICv3 and that was > new in the xenial release. AIUI, the existing hosts in ScalingStack > would've been X-Gene w/ older GICv2m controllers. I suspect the root > cause of these issues lie somewhere in the GICv3 support in QEMU and/or > edk2 - see bug 1675522 for a similar report. I'd definitely suggest > upgrading to >= bionic if possible. Or, if not, maybe consider enabling > the cloud archive to get a newer virt stack. If neither is possible, we > could also of course try and bisect down the fixes for the xenial stack > and try and SRU them back - but that will certainly take some time. > Thanks for the analysis and for helping to look at this, it's really appreciated. I suspect getting Scalingstack dist-upgraded to a newer release will be a difficult task... upgrading the virt stack alone *may* be possible, we can check that (the cloud archive doesn't contain edk2 though). It's also running Launchpad buildds though. I would expect reluctance to do this from their side due to the risks and, annoying as it is, think we should plan on identifying & doing the backports. Sorry :( I'll file a ticket with IS for their input... -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.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/1926955 Title: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x9BC11F38" Status in edk2 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 Steps to reproduce: 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). 2. Wait for it to come up, and then issue `sudo reboot` 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVM
[Kernel-packages] [Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"
I've just noticed a few failing with "Synchronous Exception at 0x984FA4A8" instead of the IRQ Exception seen earlier. -- 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/1926955 Title: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 Steps to reproduce: 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). 2. Wait for it to come up, and then issue `sudo reboot` 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"
FTR, I just checked with Canonical IS and the affected host systems are running Xenial. (We also have some different hardware which is running the same versions too and doesn't suffer from this bug, so I do suspect it is somehow hw specific.) -- 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/1926955 Title: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 Steps to reproduce: 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). 2. Wait for it to come up, and then issue `sudo reboot` 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"
** Summary changed: - arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" + [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x9BC11F38" -- 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/1926955 Title: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 Steps to reproduce: 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). 2. Wait for it to come up, and then issue `sudo reboot` 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] Re: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x000000009BC11F38"
I captured the console log when the bug happens, was hoping there would be something interesting just before the exception starts spamming the console, but sadly not. [ OK ] Finished Reboot. [ OK ] Reached target Reboot. [ 17.856242] reboot: Restarting system IRQ Exception at 0xBBC11F38 IRQ Exception at 0xBBC11F38 IRQ Exception at 0xBBC11F38 IRQ Exception at 0xBBC11F38 (keeps spamming this message) -- 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/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 Steps to reproduce: 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). 2. Wait for it to come up, and then issue `sudo reboot` 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] Re: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x000000009BC11F38"
** Description changed: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: - IRQ Exception at 0x9BC11F38 + IRQ Exception at 0x9BC11F38 + + Steps to reproduce: + + 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). + 2. Wait for it to come up, and then issue `sudo reboot` + 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. + 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) - --- + --- ProblemType: Bug AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 May 3 12:45 seq - crw-rw 1 root audio 116, 33 May 3 12:45 timer + total 0 + crw-rw 1 root audio 116, 1 May 3 12:45 seq + crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: - -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge - \-01.0-[01-02]01.0-[02]-- + -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge + \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: - + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: - + ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: - linux-restricted-modules-5.11.0-16-generic N/A - linux-backports-modules-5.11.0-16-generic N/A - linux-firmware 1.197 + linux-restricted-modules-5.11.0-16-generic N/A + linux-backports-modules-5.11.0-16-generic N/A + linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: - + dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU -- 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/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 Steps to reproduce: 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). 2. Wait for it to come up, and then issue `sudo reboot` 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: Casper
[Kernel-packages] [Bug 1926955] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1926955/+attachment/5494399/+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/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1926955/+attachment/5494400/+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/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1926955/+attachment/5494398/+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/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1926955/+attachment/5494397/+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/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1926955/+attachment/5494396/+files/ProcEnviron.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/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1926955/+attachment/5494395/+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/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1926955/+attachment/5494394/+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/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1926955/+attachment/5494393/+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/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] Re: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x000000009BC11F38"
apport information ** Tags added: apport-collected ec2-images impish ** Description changed: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 (stand by, I will get something to attach shortly) + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 May 3 12:45 seq + crw-rw 1 root audio 116, 33 May 3 12:45 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu65 + Architecture: arm64 + 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: unknown + DistroRelease: Ubuntu 21.10 + Ec2AMI: ami-fd9f + Ec2AMIManifest: FIXME + Ec2AvailabilityZone: nova + Ec2InstanceType: m1.small + Ec2Kernel: unavailable + Ec2Ramdisk: unavailable + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lspci-vt: + -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge + \-01.0-[01-02]01.0-[02]-- + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: + + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: QEMU KVM Virtual Machine + Package: linux (not installed) + PciMultimedia: + + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off + ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-16-generic N/A + linux-backports-modules-5.11.0-16-generic N/A + linux-firmware 1.197 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: impish ec2-images + Uname: Linux 5.11.0-16-generic aarch64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: False + acpidump: + + dmi.bios.date: 02/06/2015 + dmi.bios.release: 0.0 + dmi.bios.vendor: EFI Development Kit II / OVMF + dmi.bios.version: 0.0.0 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: + dmi.product.name: KVM Virtual Machine + dmi.product.version: 1.0 + dmi.sys.vendor: QEMU ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1926955/+attachment/5494392/+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/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-imag
[Kernel-packages] [Bug 1926955] [NEW] arm64 eMAG system often failng to reboot with "IRQ Exception at 0x000000009BC11F38"
Public bug reported: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 (stand by, I will get something to attach shortly) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: New Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 (stand by, I will get something to attach shortly) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
** Tags removed: block-proposed block-proposed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: New Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: New Status in u-boot-menu source package in Hirsute: Fix Released Bug description: When booting v5.11 based riscv unmatched image in qemu with uboot, it fails to boot. When booting v5.11 based riscv unmatched kernel+initrd directly, it boots fine. Somehow, it seems that u-boot fails to correctly load & start v5.11 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923638] Re: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
Would have preferred this to come much earlier, but sounds like something we need to do ... Please make sure to keep an eye out for bugs. I'll accept, thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923638 Title: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 Status in evdi package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: evdi-dkms in hirsute cannot be used with the 5.11 kernel in hirsute as it will fail to build. Upstream updates for 5.11 proved problematic, and a working set of updates became available in the upstream project only recently. Unfortunately these updates are difficult to backport due to upstream changes, and if they are backported the kernel team has no access to hardware to confirm that the backports function as intended. Therefore the safest course of action seems to be to move forward to the latest upstream evdi release plus they fixes for 5.11 from git, which has been tested by a number of evdi users already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873052] Re: Showing two cursors after login
** Tags removed: rls-ff-incoming -- 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/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image
Are you saying that the live session worked and then the installed system did not? If that's right, we need the contents of /var/log/installer, please, to see what the installer did. -- 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/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image Status in linux package in Ubuntu: Incomplete Bug description: I've installed the focal-desktop-amd64.iso image with SHA-256 sum b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook 15 G7 laptop (CID 202009-28216). There are multiple issues: * The graphical desktop isn't launched. The screen remains black except for a cursor blinking erratically in the top left corner of the screen. If I hammer Control+Alt+F[12345] for a while, the graphical desktop starts eventually. * The screen resolution is 3840x2160 but there is no scaling, so everything is tiny. * The touchpad does not work. * WLAN does not work. * Ethernet does not work. I tried two dongles (a USB A as well as a USB C dongle). * No sound. $ cat /proc/version_signature Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910576] Re: [MIR] libbpf (dependency of iproute2)
laney@dev> ./change-override -S -c main -s hirsute libbpf Override component to main libbpf 0.3-2 in hirsute: universe/misc -> main libbpf-dev 1:0.3-2 in hirsute amd64: universe/libdevel/optional/100% -> main libbpf-dev 1:0.3-2 in hirsute arm64: universe/libdevel/optional/100% -> main libbpf-dev 1:0.3-2 in hirsute armhf: universe/libdevel/optional/100% -> main libbpf-dev 1:0.3-2 in hirsute ppc64el: universe/libdevel/optional/100% -> main libbpf-dev 1:0.3-2 in hirsute riscv64: universe/libdevel/optional/100% -> main libbpf-dev 1:0.3-2 in hirsute s390x: universe/libdevel/optional/100% -> main libbpf0 1:0.3-2 in hirsute amd64: universe/libs/optional/100% -> main libbpf0 1:0.3-2 in hirsute arm64: universe/libs/optional/100% -> main libbpf0 1:0.3-2 in hirsute armhf: universe/libs/optional/100% -> main libbpf0 1:0.3-2 in hirsute ppc64el: universe/libs/optional/100% -> main libbpf0 1:0.3-2 in hirsute riscv64: universe/libs/optional/100% -> main libbpf0 1:0.3-2 in hirsute s390x: universe/libs/optional/100% -> main Override [y|N]? y 13 publications overridden. ** Changed in: libbpf (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1910576 Title: [MIR] libbpf (dependency of iproute2) Status in iproute2 package in Ubuntu: Invalid Status in libbpf package in Ubuntu: Fix Released Bug description: [Availability] libbpf | 0.1.0-1 | groovy/universe | source libbpf | 0.3-2 | hirsute/universe | source [Rationale] Libbpf is (or is about to become) a dependency for building iproute2 which already is in main. Using BPF is becoming more wide-spread. The library allows to load and use eBPF programs from user-space (functionality provided by the kernel). It is already maintained in main for Debian (https://tracker.debian.org/pkg/libbpf) [Security] Since the code is taken out of the Linux kernel, this should be treated similar to the kernel for security. Research uncovered no records about security issues. [Quality assurance] At this point there are no open bug reports against libbpf (except this one) in Ubuntu. Also no open bugs found in Debian. Project is taken from the kernel source and claims static analysis via LGTM and Coverty. Also has CI via Travis (https://travis-ci.com/github/libbpf/libbpf). Right now there are no dep-8 tests. Though potentially it should be possible to create those, would this really add additional benefit beyond having upstream CI? A test build on hirsute was showing no warnings beyond lintian complaining about things which would be changed if we had delta (unstable as series for example). Otherwise was clean. [Dependencies] libc6: main libelf1: main zlib1g: main [Standards compliance] $ lintian --pedantic libbpf_0.3-2.dsc P: libbpf source: no-homepage-field P: libbpf source: silent-on-rules-requiring-root [Maintenance] As this is only taking out code from the kernel into a separate library package, the maintenance effort should be minimal. Packaging is done in Debian and is synced into Ubuntu (no delta). [Background information] A discourse about why this is packaged outside the kernel can be found at https://lwn.net/Articles/836911/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
The point for me is that we should be trying to avoid taking on indefinite technical debt (patches that have to be rebased forever). It's "fine" to include them ahead of any upstream schedule if we need to for hardware enablement, but we do need to have plans to make this be a non permanent situation. That's what Seb is asking for, and I'm totally on board with that. btw, I don't think it's fair to characterise code review as pedantry -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)
ah I see, OK - I will upload, thanks! can you update the test case to say that this version of alsa-utils is needed please? maybe provide a PPA link for people to install it with, until that is accepted into focal? ** Changed in: alsa-lib (Ubuntu Focal) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Bug description: [Impact] Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this results in the failure on setting the init mixer values for HDA sound card, and users experience the mute of audio after installing the 20.10. [Fix] Backport a patch from the latest alsa-lib (v1.2.3+) [Test] Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is muted. Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is not muted. [Regression Potential] This could make the ucm audio fail to initialize, but this possibility is very low, since this patch is from upstream, and I tested on a ucm based machine, the audio is good. On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)
I don't see the same problem on the Focal ISO - do we need to fix this in Focal? ** Changed in: alsa-lib (Ubuntu Focal) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Incomplete Status in alsa-lib source package in Groovy: Fix Committed Bug description: [Impact] Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this results in the failure on setting the init mixer values for HDA sound card, and users experience the mute of audio after installing the 20.10. [Fix] Backport a patch from the latest alsa-lib (v1.2.3+) [Test] Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is muted. Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is not muted. [Regression Potential] This could make the ucm audio fail to initialize, but this possibility is very low, since this patch is from upstream, and I tested on a ucm based machine, the audio is good. On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900865] Re: NVIDIA drivers aren't running after fresh groovy install with Secure Boot enabled
Removing 455 from groovy to groovy-proposed to fix (2). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1900865 Title: NVIDIA drivers aren't running after fresh groovy install with Secure Boot enabled Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in ubiquity package in Ubuntu: Invalid Bug description: Ran an installation enabling nvidia drivers setup, at reboot I used my key to sign it... However the module can't be loaded on reboot: [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.969187] Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 [2.445463] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 [3.197078] Lockdown: systemd-udevd: unsigned module loading is restricted; see man kernel_lockdown.7 [3.555760] Lockdown: systemd-udevd: unsigned module loading is restricted; see man kernel_lockdown.7 [7.522144] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 [ 11.260801] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 22.069746] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 23.863146] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 [ 24.152678] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 [ 198.092912] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 [ 4870.953205] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 Module should be signed though: marco@marco-HP-Pavilion-Notebook-15-bc5xxx:~$ modinfo nvidia filename: /lib/modules/5.8.0-25-generic/updates/dkms/nvidia.ko alias: char-major-195-* version:455.28 supported: external license:NVIDIA srcversion: 9C3C7EC5A6962563520EEFD alias: pci:v10DEd*sv*sd*bc03sc02i00* alias: pci:v10DEd*sv*sd*bc03sc00i00* depends: retpoline: Y name: nvidia vermagic: 5.8.0-25-generic SMP mod_unload sig_id: PKCS#7 signer: ubuntu Secure Boot Module Signature key sig_key:10:CE:AB:F5:60:0E:86:AA:FB:81:9B:80:D5:9E:11:32:B3:BF:86:B1 sig_hashalgo: sha512 signature: 57:C9:02:C9:D6:46:8A:F5:A5:B8:14:EF:2F:00:54:37:25:B3:24:0C: FF:12:6A:50:FC:91:E4:5F:16:7B:5E:95:9E:E1:5E:A2:F1:FC:8A:17: E3:36:86:00:CC:04:5A:9E:71:28:CC:A1:18:FE:27:FE:FF:9D:BE:D7: 7E:7E:0F:0D:EF:EE:BC:AE:8B:0C:77:53:50:7C:C0:70:90:D1:B9:7B: 6D:C4:FE:C0:62:88:A7:01:30:07:95:92:87:9C:E7:E5:37:74:1E:22: EB:17:E7:35:49:26:64:E5:92:22:5F:FA:DB:84:7A:DA:1D:D2:0C:F1: 05:55:89:92:10:7F:9B:F1:A6:04:B4:CD:16:98:92:56:3A:35:3B:E9: BB:26:03:02:F9:80:23:AA:24:2B:30:E8:BE:40:87:B9:7A:DB:BF:E2: A2:EB:3D:EB:13:55:A3:B9:0A:18:EA:3B:67:A8:A5:85:79:01:D6:A3: 47:8F:50:C3:18:DF:BD:AF:B4:2A:04:88:AE:A5:61:7E:86:B7:E2:D9: 9B:CF:DE:BE:33:27:A3:0A:E2:A2:F0:9F:E9:16:58:04:68:82:F5:3C: 31:42:50:6F:FC:51:09:E7:BE:16:52:41:00:C8:9E:42:D0:25:F8:CD: 4E:90:89:B8:44:64:A7:8E:D6:07:C2:29:4D:F0:43:DF parm: NvSwitchRegDwords:NvSwitch regkey (charp) parm: NvSwitchBlacklist:NvSwitchBlacklist=uuid[,uuid...] (charp) parm: nv_cap_enable_devfs:Enable (1) or disable (0) nv-caps devfs support. Default: 1 (int) parm: NVreg_ResmanDebugLevel:int parm: NVreg_RmLogonRC:int parm: NVreg_ModifyDeviceFiles:int parm: NVreg_DeviceFileUID:int parm: NVreg_DeviceFileGID:int parm: NVreg_DeviceFileMode:int parm: NVreg_InitializeSystemMemoryAllocations:int parm: NVreg_UsePageAttributeTable:int parm: NVreg_RegisterForACPIEvents:int parm: NVreg_EnablePCIeGen3:int parm: NVreg_EnableMSI:int parm: NVreg_TCEBypassMode:int parm: NVreg_EnableStreamMemOPs:int parm: NVreg_EnableBacklightHandler:int parm: NVreg_RestrictProfilingToAdminUsers:int parm: NVreg_PreserveVideoMemoryAllocations:int parm: NVreg_DynamicPowerManagement:int parm: NVreg_DynamicPowerManagementVideoMemoryThreshold:int parm: NVreg_EnableUserNUMAManagement:int parm: NVreg_MemoryPoolSize:int parm: NVreg_KMallocHeapMaxSize:int parm: NVreg_VMallocHeapMaxSize:int parm: NVreg_IgnoreMMIOCheck:int parm: NVreg_NvLinkDisable:int parm:
[Kernel-packages] [Bug 1900865] Re: NVIDIA drivers aren't running after fresh groovy install with Secure Boot enabled
** Changed in: ubiquity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1900865 Title: NVIDIA drivers aren't running after fresh groovy install with Secure Boot enabled Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in ubiquity package in Ubuntu: Invalid Bug description: Ran an installation enabling nvidia drivers setup, at reboot I used my key to sign it... However the module can't be loaded on reboot: [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.969187] Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 [2.445463] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 [3.197078] Lockdown: systemd-udevd: unsigned module loading is restricted; see man kernel_lockdown.7 [3.555760] Lockdown: systemd-udevd: unsigned module loading is restricted; see man kernel_lockdown.7 [7.522144] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 [ 11.260801] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 22.069746] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 23.863146] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 [ 24.152678] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 [ 198.092912] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 [ 4870.953205] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 Module should be signed though: marco@marco-HP-Pavilion-Notebook-15-bc5xxx:~$ modinfo nvidia filename: /lib/modules/5.8.0-25-generic/updates/dkms/nvidia.ko alias: char-major-195-* version:455.28 supported: external license:NVIDIA srcversion: 9C3C7EC5A6962563520EEFD alias: pci:v10DEd*sv*sd*bc03sc02i00* alias: pci:v10DEd*sv*sd*bc03sc00i00* depends: retpoline: Y name: nvidia vermagic: 5.8.0-25-generic SMP mod_unload sig_id: PKCS#7 signer: ubuntu Secure Boot Module Signature key sig_key:10:CE:AB:F5:60:0E:86:AA:FB:81:9B:80:D5:9E:11:32:B3:BF:86:B1 sig_hashalgo: sha512 signature: 57:C9:02:C9:D6:46:8A:F5:A5:B8:14:EF:2F:00:54:37:25:B3:24:0C: FF:12:6A:50:FC:91:E4:5F:16:7B:5E:95:9E:E1:5E:A2:F1:FC:8A:17: E3:36:86:00:CC:04:5A:9E:71:28:CC:A1:18:FE:27:FE:FF:9D:BE:D7: 7E:7E:0F:0D:EF:EE:BC:AE:8B:0C:77:53:50:7C:C0:70:90:D1:B9:7B: 6D:C4:FE:C0:62:88:A7:01:30:07:95:92:87:9C:E7:E5:37:74:1E:22: EB:17:E7:35:49:26:64:E5:92:22:5F:FA:DB:84:7A:DA:1D:D2:0C:F1: 05:55:89:92:10:7F:9B:F1:A6:04:B4:CD:16:98:92:56:3A:35:3B:E9: BB:26:03:02:F9:80:23:AA:24:2B:30:E8:BE:40:87:B9:7A:DB:BF:E2: A2:EB:3D:EB:13:55:A3:B9:0A:18:EA:3B:67:A8:A5:85:79:01:D6:A3: 47:8F:50:C3:18:DF:BD:AF:B4:2A:04:88:AE:A5:61:7E:86:B7:E2:D9: 9B:CF:DE:BE:33:27:A3:0A:E2:A2:F0:9F:E9:16:58:04:68:82:F5:3C: 31:42:50:6F:FC:51:09:E7:BE:16:52:41:00:C8:9E:42:D0:25:F8:CD: 4E:90:89:B8:44:64:A7:8E:D6:07:C2:29:4D:F0:43:DF parm: NvSwitchRegDwords:NvSwitch regkey (charp) parm: NvSwitchBlacklist:NvSwitchBlacklist=uuid[,uuid...] (charp) parm: nv_cap_enable_devfs:Enable (1) or disable (0) nv-caps devfs support. Default: 1 (int) parm: NVreg_ResmanDebugLevel:int parm: NVreg_RmLogonRC:int parm: NVreg_ModifyDeviceFiles:int parm: NVreg_DeviceFileUID:int parm: NVreg_DeviceFileGID:int parm: NVreg_DeviceFileMode:int parm: NVreg_InitializeSystemMemoryAllocations:int parm: NVreg_UsePageAttributeTable:int parm: NVreg_RegisterForACPIEvents:int parm: NVreg_EnablePCIeGen3:int parm: NVreg_EnableMSI:int parm: NVreg_TCEBypassMode:int parm: NVreg_EnableStreamMemOPs:int parm: NVreg_EnableBacklightHandler:int parm: NVreg_RestrictProfilingToAdminUsers:int parm: NVreg_PreserveVideoMemoryAllocations:int parm: NVreg_DynamicPowerManagement:int parm: NVreg_DynamicPowerManagementVideoMemoryThreshold:int parm: NVreg_EnableUserNUMAManagement:int parm: NVreg_MemoryPoolSize:int parm: NVreg_KMallocHeapMaxSize:int parm: NVreg_VMallocHeapMaxSize:int parm: NVreg_IgnoreMMIOCheck:int parm: NVreg_NvLinkDisable:int p
[Kernel-packages] [Bug 1899678] Re: No wifi after installation - does not work with secure boot enabled
New shim-signed is now on the latest images (20201021). I'm still not clear what happened when enabling Broadcom from the installer since it all looks fine to me. Perhaps you could try and let us know what doesn't work with detailed steps to reproduce? (but hopefully it does work) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899678] Re: No wifi after installation - does not work with secure boot enabled
I think the second part (apt install not showing the prompt on next boot) is fixed with shim-signed 1.45 as indicated by Andy in comment #8. But I'm not quite sure about your initial part where the installer didn't do the same. I can make that happen if I tick to install proprietary drivers and then untick "Configure secure boot". But that's to be expected. If I tick both and fill in a passphrase, then it works correctly and I'm prompted to enroll the key after completing the installation and rebooting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899678] Re: No wifi after installation - does not work with secure boot enabled
Yeah, fossfreedom, can you tell us what you ticked on the 'install third party drivers' page? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Uploaded to proposed, not the debdiff here but the new upstream release 3.36.3 which has the same fix in it ** Changed in: gnome-session (Ubuntu) Status: Confirmed => Invalid ** Changed in: grub2 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Confirmed => Invalid ** Also affects: gnome-session (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-390 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-430 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-435 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-440 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu Focal) Status: New => In Progress ** Changed in: gdm3 (Ubuntu Focal) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gnome-session (Ubuntu Focal) Status: New => Invalid ** Changed in: grub2 (Ubuntu Focal) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Focal) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-430 (Ubuntu Focal) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-435 (Ubuntu Focal) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Status: New => Invalid ** Changed in: gdm3 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: In Progress Status in gdm3 package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Invalid Status in grub2 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-430 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in gdm3 source package in Focal: In Progress Status in gnome-session source package in Focal: Invalid Status in grub2 source package in Focal: Invalid Status in nvidia-graphics-drivers-390 source package in Focal: Invalid Status in nvidia-graphics-drivers-430 source package in Focal: Invalid Status in nvidia-graphics-drivers-435 source package in Focal: Invalid Status in nvidia-graphics-drivers-440 source package in Focal: Invalid Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and log
[Kernel-packages] [Bug 1881699] Re: No analog output
there's an updated kernel in that bug, jibel can you test it please to confirm if this is a dupe or not? ** Tags removed: rls-gg-incoming -- 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/1881699 Title: No analog output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881699] Re: No analog output
please re-add the tag if it's not -- 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/1881699 Title: No analog output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880508] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common
** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-440 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Groovy) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: Confirmed ** Also affects: nvidia-graphics-drivers-440 (Ubuntu Groovy) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1880508 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in nvidia-graphics-drivers-340 source package in Focal: New Status in nvidia-graphics-drivers-440 source package in Focal: New Status in nvidia-graphics-drivers-340 source package in Groovy: Confirmed Status in nvidia-graphics-drivers-440 source package in Groovy: New Bug description: I can not connect my MackBook Pro to monitor and I need some feedback ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 08:10:28 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-05-23 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1880508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
** Also affects: gnome-control-center (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-435 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-440 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: nvidia-graphics-drivers-435 (Ubuntu Focal) Status: New => Won't Fix ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Status: New => Won't Fix ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: New Status in mutter source package in Focal: New Status in nvidia-graphics-drivers-340 source package in Focal: New Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 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.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: l
[Kernel-packages] [Bug 1874278] [NEW] Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity
Public bug reported: We are in the process of switching ubuntu-drivers to installing linux- restricted-modules versions of NVidia drivers when it can, but this fails when Ubiquity invokes ubuntu-drivers, like: Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ... /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 3: B ad file descriptor dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic (--con figure): installed linux-modules-nvidia-440-5.4.0-25-generic package post-installation script subprocess returned error exit status 2 dpkg: dependency problems prevent configuration of linux-modules-nvidia-440-gen eric-hwe-20.04: linux-modules-nvidia-440-generic-hwe-20.04 depends on linux-modules-nvidia-440 -5.4.0-25-generic (= 5.4.0-25.29); however: Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet. dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 (--configure): dependency problems - leaving unconfigured It's a problem with the nesting of debconf: Ubiquity itself is using debconf, and ubuntu-drivers is installing -nvidia- packages which themselves also use debconf, and we don't know how to connect ubuntu- drivers use of debconf with the ubiquity one. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Can't install any packages via ubuntu-drivers which use debconf + Can't install any packages from ubiquity via ubuntu-drivers which use debconf ** Summary changed: - Can't install any packages from ubiquity via ubuntu-drivers which use debconf + Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1874278 Title: Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity Status in linux-restricted-modules package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: We are in the process of switching ubuntu-drivers to installing linux- restricted-modules versions of NVidia drivers when it can, but this fails when Ubiquity invokes ubuntu-drivers, like: Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ... /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 3: B ad file descriptor dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic (--con figure): installed linux-modules-nvidia-440-5.4.0-25-generic package post-installation script subprocess returned error exit status 2 dpkg: dependency problems prevent configuration of linux-modules-nvidia-440-gen eric-hwe-20.04: linux-modules-nvidia-440-generic-hwe-20.04 depends on linux-modules-nvidia-440 -5.4.0-25-generic (= 5.4.0-25.29); however: Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet. dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 (--configure): dependency problems - leaving unconfigured It's a problem with the nesting of debconf: Ubiquity itself is using debconf, and ubuntu-drivers is installing -nvidia- packages which themselves also use debconf, and we don't know how to connect ubuntu- drivers use of debconf with the ubiquity one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1874278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
I don't think there's anything to fix in udisks2 here, since it's just using the filesystems that are available; invalidating the task. Perhaps you're arguing for exfat-fuse to be removed from the archive? See comment #3. ** Changed in: udisks2 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel Status in linux package in Ubuntu: Incomplete Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: In Progress Status in udisks2 package in Ubuntu: Invalid Bug description: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1860559] Re: [18.04.4] System fails to reboot after installation
On Fri, Jan 24, 2020 at 05:05:42PM -, Łukasz Zemczak wrote: > So finalrd is now in main for bionic-updates. The question now is: will > we need finalrd to be in bionic-security as well for this? I think we > won't, but I guess my brain is a bit fried right now. Don't see why you would. I think we just need the dependency. Thanks for handling this! -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.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/1860559 Title: [18.04.4] System fails to reboot after installation Status in casper package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in casper source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Bug description: bionic desktop 20190122 Since bionic 20191211 the system doesn't reboot after installation. After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console: [sdb] tag#0 access beyond end of device (in this context sdb is the USB stick) 20191211 includes a new kernel and a new gcc This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different on baremetal, it is identical in a VM. Installing finalrd helps to work around the issue. However in Bionic, finalrd is in universe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:17:58 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1860559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852122] Re: ocfs2-tools is causing kernel panics in Ubuntu Focal (Ubuntu-5.4.0-9.12)
awesome, thanks for following up! -- 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/1852122 Title: ocfs2-tools is causing kernel panics in Ubuntu Focal (Ubuntu-5.4.0-9.12) Status in OCFS2 Tools: Fix Released Status in linux package in Ubuntu: In Progress Status in ocfs2-tools package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Status in ocfs2-tools source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in ocfs2-tools source package in Focal: In Progress Bug description: I noticed the tests for ocfs2-tools/1.8.6-1ubuntu1 were constantly retrying themselves. It's a feature we have so that transient / occasional failures are auto-retried, but it's misfiring here because we're not detecting that it's a consistent failure. That particular bug is fixed, but it means that ocfs2-tools is failing on ppc64el. Here's the important part of the log, full output attached. [ 85.605738] BUG: Unable to handle kernel data access at 0x01744098 [ 85.605850] Faulting instruction address: 0xc0e81168 [ 85.605901] Oops: Kernel access of bad area, sig: 11 [#1] [ 85.605970] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries [ 85.606029] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_net virtio_blk net_failover failover [ 85.606291] CPU: 0 PID: 1 Comm: systemd Not tainted 5.3.0-18-generic #19-Ubuntu [ 85.606350] NIP: c0e81168 LR: c054f240 CTR: [ 85.606410] REGS: c0005a3e3700 TRAP: 0300 Not tainted (5.3.0-18-generic) [ 85.606469] MSR: 80009033 CR: 28024448 XER: [ 85.606531] CFAR: 701f9806f638 DAR: 01744098 DSISR: 4000 IRQMASK: 0 [ 85.606531] GPR00: 7374 c0005a3e3990 c19c9100 c0004fe462a8 [ 85.606531] GPR04: c0005856d840 000e 74656772 c0004fe4a568 [ 85.606531] GPR08: c00058568004 01744090 [ 85.606531] GPR12: e8086002 c1d6 7fffddd522d0 [ 85.606531] GPR16: c755e07c [ 85.606531] GPR20: c000598caca8 c0005a3e3a58 c00058292f00 [ 85.606531] GPR24: c0eea710 c0005856d840 c755e074 [ 85.606531] GPR28: 6518907d c0005a3e3a68 c0004fe4b160 027c47b6 [ 85.607079] NIP
[Kernel-packages] [Bug 1841661] Re: The cursor disappears, when I use GNOME on Wayland
Actually, I'm not certain it is a duplicate of that one - this bug I think is a regression in eoan due to some change in the kernel between disco and eoan. Perhaps they are related though. When I'm back from travelling I'll try to do a little bit of investigation (but I don't know anything about the DRM subsystem so bisecting is probably the best that I'm going to be able to achieve). ** This bug is no longer a duplicate of bug 1767654 [Intel Braswell/Apollo Lake] Cursor gets stuck on left side of the screen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841661 Title: The cursor disappears, when I use GNOME on Wayland Status in linux package in Ubuntu: Confirmed Bug description: Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8 P.S. Any screen recorders don't work on Wayland. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 27 22:36:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-25 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841661] Re: The cursor disappears, when I use GNOME on Wayland
On Tue, Aug 27, 2019 at 07:47:53PM -, Artyom Pozharov wrote: > Public bug reported: > > Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8 Yes, thanks for filing. I showed this to the upstream guys and they knew about it. It's apparently a kernel problem as if you revert to kernel 5.0 it goes away. So I'll reassign this bug to linux - maybe we can find out when it was introduced if the kernel team can help us to bisect. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841661 Title: The cursor disappears, when I use GNOME on Wayland Status in linux package in Ubuntu: Confirmed Bug description: Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8 P.S. Any screen recorders don't work on Wayland. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 27 22:36:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-25 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833916] Re: USB-C to HDMI converter is not working with thunderbolt port
** No longer affects: ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833916 Title: USB-C to HDMI converter is not working with thunderbolt port Status in linux package in Ubuntu: Incomplete Bug description: [Summary] There are 2 USB-C port on my XPS 13 9380, one is Display port on the right side, the other is thunderbolt on the left side. When I using a USB-C to HDMI converter to connect an external monitor, it does not work with the thunderbolt port, but display port is always working. I tried 4 different branding converters and get all the same result: DP port works, Thunderbolt port does NOT. Detail syslog and dmesg can be found here https://paste.ubuntu.com/p/V4DspmXTZc/ [Additional information] jerry@jerry-XPS-13-9380:~$ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 19.04 Release:19.04 Codename:disco kernel-version: 5.0.0-17-generic bios-version: 1.3.2 CPU: Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz (8x) system-product-name: XPS 13 9380 system-manufacturer: Dell Inc. GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Tags removed: rls-bb-incoming
--
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/1817738
Title:
Can't change virtual terminal when auto-login is enabled
Status in gdm3 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in gdm3 source package in Bionic:
In Progress
Status in linux source package in Bionic:
Invalid
Bug description:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs
forever, preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin =
3) Reboot your system and make sure AutoLogin works by not requesting
password before opening the session.
4) Print active VT
$ sudo fgconsole
Without the fix, it will be "1". # BAD
With the fix, it will be "2". # GOOD
5) sudo chvt 4 ## chvt will hang here.
Verification can be made from a 2nd terminal, run :
$ cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
It's basically waiting for the VT to be activated, but it never
happens.
[Potential regression]
Low.
Current gdm3 run autologin display on tty1. tty1 is really meant for
the login screen. This commit changes autologin to not use the initial
vt.
If one switch to tty1, the next VT switch attempt will hangs again and
one won't be able to switch it. tty1 is really the problem here, so by
forcing the autologin to not use tty1 we improve the current behaviour
where we can't switch VTs at all when autologin is enabled.
The tty1 behaviour will still need (normal behaviour or not ???) to be
investigated, but not mandatory required for the sake of this SRU
IMHO.
I suspect systemd-logind to be the reason of the tty1 behaviour:
# ps
root 1350 1 0 Mar03 ?00:00:03 /lib/systemd/systemd-logind
#lsof
systemd-l 1350 root 24u CHR4,1
0t0 45 /dev/tty1
But I haven't dig much in it for now.
So the fix will works as long as one doesn't do run on tty1.
Exactly like when autologin isn't enable.
* From a machine with autologin enable:
/etc/gdm3/customer.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin = user1
$ sudo fgconsole
1
* From a machine with autologin disable:
/etc/gdm3/customer.conf
# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1
$ sudo fgconsole
2
[Other information]
* Upstream fix:
https://github.com/GNOME/gdm/commit/39fb4ff6
$ git describe --contains 39fb4ff6
3.30.1~2^2~3
$ rmadision gdm3
==> gdm3 | 3.28.3-0ubuntu18.04.4 | bionic-updates | ...
gdm3 | 3.30.1-1ubuntu5 | cosmic | ...
gdm3 | 3.30.1-1ubuntu5 | disco| ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-security | ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-updates | ...
gdm3 | 3.31.4+git20190225-1ubuntu1 | disco-proposed | ...
[Original Description]
sudo strace chvt 4
execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
brk(NULL) = 0x561e1843
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f5059e7b000
mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5059878000
mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
mprotect(0x561e17e87000, 4096, PROT_READ) = 0
mp
[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Also affects: gnome-control-center (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: upower (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu Cosmic) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu Cosmic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu Cosmic) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Cosmic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: upower (Ubuntu Cosmic) Status: New => In Progress ** Changed in: upower (Ubuntu Cosmic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Status in gnome-control-center source package in Cosmic: In Progress Status in gnome-shell source package in Cosmic: In Progress Status in linux source package in Cosmic: New Status in upower source package in Cosmic: In Progress Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchp
[Kernel-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770271] Re: VegaM support
** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1770271 Title: VegaM support Status in amd: New Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in mesa source package in Xenial: Won't Fix Status in linux source package in Bionic: New Status in mesa source package in Bionic: New Bug description: VegaM is a new GPU. Please include support for VegaM in the next LTS (16.04.x and 18.04.x) and non-LTS releases. Kernel support starts here (32 patches): https://patchwork.freedesktop.org/patch/218839/ Mesa support: https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123 https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8 https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1770271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: Fix Committed Status in linux package in Ubuntu: In Progress Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: New Status in linux source package in Bionic: New Status in mutter source package in Bionic: New Bug description: [ Description ] GNome shell crashes after Xorg loggin [ Test case ] From GDM login in a GNOME Ubuntu session (so Xorg). It should start with no issues [ Regression potential ] We were deferencing a NULL pointer while outputting an error. This is pretty safe. Although the session might still not run properly as per a driver issue to be addressed in linux package. --- https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 https://salsa.debian.org/gnome-team/mutter/merge_requests/6 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
Just a heads up - this apparently became much harder for me to reproduce
at will. We're still seeing it in actual workloads but I'm having
trouble recreating manually.
My current strategy is to start stress-ng on a number of machines and
then constantly reboot them, with the idea that this will stress the
cloud and make the bug more likely, which relies on the assumption that
this bug is somehow to do with busyness on the underlying machines.
--
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/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
In Progress
Status in qemu-kvm package in Ubuntu:
Confirmed
Status in linux source package in Zesty:
Incomplete
Status in qemu-kvm source package in Zesty:
New
Status in linux source package in Artful:
In Progress
Status in qemu-kvm source package in Artful:
Confirmed
Status in linux source package in Bionic:
In Progress
Status in qemu-kvm source package in Bionic:
Confirmed
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive,
so the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it
doesn't feel to me like a host problem but rather a race condition
somewhere that's somehow either triggered or triggered much more often
by what lcy01 is running. I always saw this on the first reboot -
never on first boot, and never on n>1th boot. (But if it's a race then
that might not mean much.)
I'll attach a bad and a good console-log for reference.
If you're at Canonical then see internal rt #107135 for some other
details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
OK a few days ago apw pointed me at http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.13.8/ which is the mainline kernel that the artful-
proposed one I identified as bad is based on.
I ran 35 instances and rebooted them 30 times - all successful. So I
think that says this kernel is good.
Will try another one later on.
--
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/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
In Progress
Status in qemu-kvm package in Ubuntu:
Confirmed
Status in linux source package in Zesty:
Incomplete
Status in qemu-kvm source package in Zesty:
New
Status in linux source package in Artful:
In Progress
Status in qemu-kvm source package in Artful:
Confirmed
Status in linux source package in Bionic:
In Progress
Status in qemu-kvm source package in Bionic:
Confirmed
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive,
so the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it
doesn't feel to me like a host problem but rather a race condition
somewhere that's somehow either triggered or triggered much more often
by what lcy01 is running. I always saw this on the first reboot -
never on first boot, and never on n>1th boot. (But if it's a race then
that might not mean much.)
I'll attach a bad and a good console-log for reference.
If you're at Canonical then see internal rt #107135 for some other
details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
On Wed, Nov 08, 2017 at 06:57:46PM -, Joseph Salisbury wrote:
> Maybe give 4.13.0-16 a try:
>
> https://launchpad.net/~canonical-kernel-security-
> team/+archive/ubuntu/ppa2/+build/13567624
>
> It could also be the bug is being triggered by a Ubuntu specific SAUCE
> patch, so it won't happen with upstream kernels.
It looked to me like that's the same kernel that's in artful release, so
instead I tried with the kernel in artful-proposed (4.13.0-17.20) and
managed to reproduce the bug on 1/6 instances after a few reboot cycles.
So I think my method is okay to check candidate kernels. Feel free to
throw some more at me if you want to bisect.
(I think IS took some of the slower machines out of rotation so the
problem might become slightly harder to reproduce - definitely is still
happening though.)
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.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/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
Triaged
Status in qemu-kvm package in Ubuntu:
New
Status in linux source package in Artful:
Triaged
Status in qemu-kvm source package in Artful:
New
Status in linux source package in Bionic:
Triaged
Status in qemu-kvm source package in Bionic:
New
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive,
so the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it
doesn't feel to me like a host problem but rather a race condition
somewhere that's somehow either triggered or triggered much more often
by what lcy01 is running. I always saw this on the first reboot -
never on first boot, and never on n>1th boot. (But if it's a race then
that might not mean much.)
I'll attach a bad and a good console-log for reference.
If you're at Canonical then see internal rt #107135 for some other
details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
On Wed, Nov 08, 2017 at 03:16:29PM -, Joseph Salisbury wrote:
> @Laney, thanks for testing the mainline kernel. It's promising that a
> fix might be in that kernel. The time consuming part will be
> identifying what commit in that kernel is the actual fix. We could
> perform a "Reverse" kernel bisect, which would required testing 12 or so
> test kernels. However, it sounds like to set up a reproducer is time
> consuming as well.
>
> The easiest thing to try next would be to test the latest upstream 4.13
> stable kernels. It's possible the fix that is in 4.14-rc8 was also cc'd
> to upstream stable and made it's way into 4.13 thorough the normal
> stable update process.
>
> If possible to test, the latest 4.13 upstream kernel is 4.13.12 and is
> available here:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.12/
20 instances, all good.
Maybe I should try one that we think is 'bad' to confirm that the way
I'm doing this is actually capable of reproducing the issue? If you
think that's sensible, could you recommend me a kernel to try?
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.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/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
Triaged
Status in qemu-kvm package in Ubuntu:
New
Status in linux source package in Artful:
Triaged
Status in qemu-kvm source package in Artful:
New
Status in linux source package in Bionic:
Triaged
Status in qemu-kvm source package in Bionic:
New
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive,
so the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it
doesn't feel to me like a host problem but rather a race condition
somewhere that's somehow either triggered or triggered much more often
by what lcy01 is running. I always saw this on the first reboot -
never on first boot, and never on n>1th boot. (But if it's a race then
that might not mean much.)
I'll attach a bad and a good console-log for reference.
If you're at Canonical then see internal rt #107135 for some other
details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
On Wed, Nov 08, 2017 at 11:56:02AM -, ChristianEhrhardt wrote:
> Torkoal (our Jenkins node) was idle atm and Ryan reported he had seen the
> issues there before, so trying there as well.
> This is LTS + HWE - Kernel 4.10.0-38-generic, qemu: 1:2.5+dfsg-5ubuntu10
>
> I thought about your case since you seem just to start a lot of them and
> reboot,
> this shouldn't be so much different to:
> $ uvt-simplestreams-libvirt --verbose sync --source
> http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=artful
> $ for i in {1..30}; do uvt-kvm create --log-console-output --password=ubuntu
> artful-${i}-bug1730717 release=artful arch=amd64 label=daily; done
> $ for i in {1..30}; do uvt-kvm wait --insecure artful-${i}-bug1730717; done
> $ for i in {1..30}; do uvt-kvm ssh --insecure artful-${i}-bug1730717 "sudo
> reboot"; done
> $ sudo grep "soft lockup" /var/log/libvirt/qemu/artful-*-bug1730717.log
Sounds like it's similar, but maybe you have to put the system under
load - you might need more instances, or maybe start a whole bunch first
and get them to run something memory intensive before running that same
test again. In the cloud there will be buildds and tests running on the
compute nodes too, as well as these 'empty' instances that I use to
reproduce the problem.
> Waiting for your feedback if you can trigger the same issue on a non-
> busy openstack system (could after all be some openstack magic at work
> that makes it behave differently).
I don't have access to a non busy cloud I'm afraid.
ANYWAY! My results are in. I created an image by booting the stock
artful cloud image and installing the mainline kernel v4.14-rc8
(39dae59d66acd86d1de24294bd2f343fd5e7a625) packages, on lcy01 (the busy
cloud that exhibits this problem).
I started 34 (17 × 2 in two runs - that's all I could squeeze in before
I hit my quota) instances, and they were all good. This isn't definitive
proof, but it looks like that kernel might be good.
Cheers,
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.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/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
Triaged
Status in qemu-kvm package in Ubuntu:
New
Status in linux source package in Artful:
Triaged
Status in qemu-kvm source package in Artful:
New
Status in linux source package in Bionic:
Triaged
Status in qemu-kvm source package in Bionic:
New
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive,
so the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it
doesn't feel to me like a host
Re: [Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
On Wed, Nov 08, 2017 at 11:08:05AM -, ChristianEhrhardt wrote:
> @Laney I found it interesting that you essentially only needed to
> start+reboot.
> I assume on the host you had other workload goes on in the background (since
> it is lcy01)?
I don't have visibility into what else the hosts are doing - I'm just a
client here. But I do know that *I* had other workloads running at the
same time. I assume that there were a lot of buildd jobs too. These
compute nodes are probably loaded most of the time.
> If you'd have any sort of non-busy but otherwise comparable system - could
> you check to confirm the assumption we have so far that there all is fine?
> If yes - then the memory pressure theory gets more likely, if not we can
> focus on simpler reproducers - so we can only win by that check.
Afraid not, sorry. I did try on my artful+artful host but didn't
reproduce the problem - it probably wasn't under enough stress anyway.
> Crossing fingers for jsalisbury's hope that 4.14 might already have a
> fix.
Right now I'm trying to build a new cloud image with this kernel that I
can try.
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.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/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
Triaged
Status in qemu-kvm package in Ubuntu:
New
Status in linux source package in Artful:
Triaged
Status in qemu-kvm source package in Artful:
New
Status in linux source package in Bionic:
Triaged
Status in qemu-kvm source package in Bionic:
New
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive,
so the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it
doesn't feel to me like a host problem but rather a race condition
somewhere that's somehow either triggered or triggered much more often
by what lcy01 is running. I always saw this on the first reboot -
never on first boot, and never on n>1th boot. (But if it's a race then
that might not mean much.)
I'll attach a bad and a good console-log for reference.
If you're at Canonical then see internal rt #107135 for some other
details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
I tried 28 (then my quota ran out) xenial guests BTW and none of those
failed.
--
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/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
New
Status in qemu-kvm package in Ubuntu:
New
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive,
so the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it
doesn't feel to me like a host problem but rather a race condition
somewhere that's somehow either triggered or triggered much more often
by what lcy01 is running. I always saw this on the first reboot -
never on first boot, and never on n>1th boot. (But if it's a race then
that might not mean much.)
I'll attach a bad and a good console-log for reference.
If you're at Canonical then see internal rt #107135 for some other
details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
** Attachment added: "bad run console-log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+attachment/5005464/+files/laney-test25.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
New
Status in qemu-kvm package in Ubuntu:
New
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive,
so the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it
doesn't feel to me like a host problem but rather a race condition
somewhere that's somehow either triggered or triggered much more often
by what lcy01 is running. I always saw this on the first reboot -
never on first boot, and never on n>1th boot. (But if it's a race then
that might not mean much.)
I'll attach a bad and a good console-log for reference.
If you're at Canonical then see internal rt #107135 for some other
details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
Oh also see https://bugs.launchpad.net/ubuntu/+source/linux-
hwe/+bug/1713751 which has some superficially similar symptoms (cpu
stuck on shutdown).
** Description changed:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn and
backs off until the next reset (6 hourly).
- Guests are sometimes failing to reboot. When this happens, you see the
- following in the console
+ 17.10 (and bionic) guests are sometimes failing to reboot. When this
+ happens, you see the following in the console
- [[0;32m OK [0m] Reached target Shutdown.
- [ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
- [ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
- [ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
- [ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
- [ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
- [ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
+ [[0;32m OK [0m] Reached target Shutdown.
+ [ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
+ [ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
+ [ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
+ [ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
+ [ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
+ [ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
- Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
+ Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
- Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
+ Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive, so
the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
- $ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
- $ sudo reboot
- # wait a minute or so for the instances to all reboot
- $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
+ $ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
+ $ sudo reboot
+ # wait a minute or so for the instances to all reboot
+ $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it doesn't
feel to me like a host problem but rather a race condition somewhere
that's somehow either triggered or triggered much more often by what
lcy01 is running. I always saw this on the first reboot - never on first
boot, and never on n>1th boot. (But if it's a race then that might not
mean much.)
I'll attach a bad and a good console-log for reference.
If you're at Canonical then see internal rt #107135 for some other
details.
--
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/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
New
Status in qemu-kvm package in Ubuntu:
New
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
** Attachment added: "good run console-log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+attachment/5005465/+files/laney-test14.log
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
New
Status in qemu-kvm package in Ubuntu:
New
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive,
so the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it
doesn't feel to me like a host problem but rather a race condition
somewhere that's somehow either triggered or triggered much more often
by what lcy01 is running. I always saw this on the first reboot -
never on first boot, and never on n>1th boot. (But if it's a race then
that might not mean much.)
I'll attach a bad and a good console-log for reference.
If you're at Canonical then see internal rt #107135 for some other
details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730717] [NEW] Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
Public bug reported:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn and
backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346 f0x2
RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive, so
the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n} |
tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it doesn't
feel to me like a host problem but rather a race condition somewhere
that's somehow either triggered or triggered much more often by what
lcy01 is running. I always saw this on the first reboot - never on first
boot, and never on n>1th boot. (But if it's a race then that might not
mean much.)
I'll attach a bad and a good console-log for reference.
If you're at Canonical then see internal rt #107135 for some other
details.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
New
Status in qemu-kvm package in Ubuntu:
New
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive,
so the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it
doesn't feel to me like a host problem but rather a race condition
s
[Kernel-packages] [Bug 1711358] Re: 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver
** Tags added: rls-aa-incoming -- 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/1711358 Title: 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: New Status in ubiquity package in Ubuntu: Confirmed Bug description: Test Case 1. Boot artful desktop 20170817 under qemu with qxl 2. Wait until ubiquity-dm is displayed Expected result It boots Actual result It hangs on the splash screen and the dots below the Ubuntu logo are not blinking. If the option 'splash' is removed from the boot command line it boots successfully. It also boots successfully with -vga std but in this case the splash screen is in text mode not graphical unlike with the qxl driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706283] Re: ADT tests fail since 4.11.0-11.16
(ah, it was already closed) -- 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/1706283 Title: ADT tests fail since 4.11.0-11.16 Status in linux package in Ubuntu: Fix Released Bug description: The ADT tests started failing with 4.11.0-11.16 on amd64, i386 and ppc64el: all the arches we run using qemu over OpenStack. The virtual machines hang completely. The last lines in the log are: 12:11:18 DEBUG| [stdout] Test icebp [Ok] 12:11:18 DEBUG| [stdout] Test int 3 trap [Failed] 12:11:18 DEBUG| [stdout] selftests: breakpoint_test [PASS] 12:11:18 DEBUG| [stdout] /tmp/autopkgtest.zKFdZm/build.ham/linux-4.11.0/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/breakpoints ... and on the console we see a lot of messages like: ** 35 printk messages dropped ** [ 3577.683828] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 33 printk messages dropped ** [ 3577.686564] ACPI Error: Could not disable RealTimeClock events (20170119/evxfevnt-267) ** 25 printk messages dropped ** [ 3577.688566] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 35 printk messages dropped ** [ 3577.692788] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 29 printk messages dropped ** [ 3577.695184] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 34 printk messages dropped ** [ 3577.697955] ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20170119/evevent-286) I've attached the full log. In the log file there is the invocation I used to generate the failing log. You should be able to try similar using either `qemu' locally. If that doesn't reproduce, try on Canonistack. If *that* doesn't reproduce, apw or I can run test builds for you if there's a PPA to test from. This tickles an unfortunate behaviour in the way we run autopkgtest. What happens is: the machine hangs, autopkgtest notices this has happened, it tries to clean up the testbed and can't get into it because it is hung. This is counted as a 'temporary failure', and so the job is requeued forever. As a result, I've blacklisted linux from the workers. Please reach out to us for manual runs, and then once it is confirmed to not loop in this way we'll remove the blacklist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706283] Re: ADT tests fail since 4.11.0-11.16
ok, the test completes without hanging. It fails though: ubuntu-regression-suite FAIL non-zero exit status 253 but that's not what this bug was about, so closing & unblacklisting. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706283 Title: ADT tests fail since 4.11.0-11.16 Status in linux package in Ubuntu: Fix Released Bug description: The ADT tests started failing with 4.11.0-11.16 on amd64, i386 and ppc64el: all the arches we run using qemu over OpenStack. The virtual machines hang completely. The last lines in the log are: 12:11:18 DEBUG| [stdout] Test icebp [Ok] 12:11:18 DEBUG| [stdout] Test int 3 trap [Failed] 12:11:18 DEBUG| [stdout] selftests: breakpoint_test [PASS] 12:11:18 DEBUG| [stdout] /tmp/autopkgtest.zKFdZm/build.ham/linux-4.11.0/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/breakpoints ... and on the console we see a lot of messages like: ** 35 printk messages dropped ** [ 3577.683828] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 33 printk messages dropped ** [ 3577.686564] ACPI Error: Could not disable RealTimeClock events (20170119/evxfevnt-267) ** 25 printk messages dropped ** [ 3577.688566] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 35 printk messages dropped ** [ 3577.692788] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 29 printk messages dropped ** [ 3577.695184] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 34 printk messages dropped ** [ 3577.697955] ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20170119/evevent-286) I've attached the full log. In the log file there is the invocation I used to generate the failing log. You should be able to try similar using either `qemu' locally. If that doesn't reproduce, try on Canonistack. If *that* doesn't reproduce, apw or I can run test builds for you if there's a PPA to test from. This tickles an unfortunate behaviour in the way we run autopkgtest. What happens is: the machine hangs, autopkgtest notices this has happened, it tries to clean up the testbed and can't get into it because it is hung. This is counted as a 'temporary failure', and so the job is requeued forever. As a result, I've blacklisted linux from the workers. Please reach out to us for manual runs, and then once it is confirmed to not loop in this way we'll remove the blacklist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1706283] Re: ADT tests fail since 4.11.0-11.16
On Tue, Jul 25, 2017 at 06:49:02PM -, Stefan Bader wrote: > autotest-client-test repository updated now (on the positive side this > was no real regression in the kernel but a failure to disable a known > problematic part of the self tests). Alright - re-running, will unblacklist if it doesn't hang. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.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/1706283 Title: ADT tests fail since 4.11.0-11.16 Status in linux package in Ubuntu: Fix Released Bug description: The ADT tests started failing with 4.11.0-11.16 on amd64, i386 and ppc64el: all the arches we run using qemu over OpenStack. The virtual machines hang completely. The last lines in the log are: 12:11:18 DEBUG| [stdout] Test icebp [Ok] 12:11:18 DEBUG| [stdout] Test int 3 trap [Failed] 12:11:18 DEBUG| [stdout] selftests: breakpoint_test [PASS] 12:11:18 DEBUG| [stdout] /tmp/autopkgtest.zKFdZm/build.ham/linux-4.11.0/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/breakpoints ... and on the console we see a lot of messages like: ** 35 printk messages dropped ** [ 3577.683828] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 33 printk messages dropped ** [ 3577.686564] ACPI Error: Could not disable RealTimeClock events (20170119/evxfevnt-267) ** 25 printk messages dropped ** [ 3577.688566] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 35 printk messages dropped ** [ 3577.692788] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 29 printk messages dropped ** [ 3577.695184] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 34 printk messages dropped ** [ 3577.697955] ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20170119/evevent-286) I've attached the full log. In the log file there is the invocation I used to generate the failing log. You should be able to try similar using either `qemu' locally. If that doesn't reproduce, try on Canonistack. If *that* doesn't reproduce, apw or I can run test builds for you if there's a PPA to test from. This tickles an unfortunate behaviour in the way we run autopkgtest. What happens is: the machine hangs, autopkgtest notices this has happened, it tries to clean up the testbed and can't get into it because it is hung. This is counted as a 'temporary failure', and so the job is requeued forever. As a result, I've blacklisted linux from the workers. Please reach out to us for manual runs, and then once it is confirmed to not loop in this way we'll remove the blacklist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706283] [NEW] ADT tests fail since 4.11.0-11.16
Public bug reported: The ADT tests started failing with 4.11.0-11.16 on amd64, i386 and ppc64el: all the arches we run using qemu over OpenStack. The virtual machines hang completely. The last lines in the log are: 12:11:18 DEBUG| [stdout] Test icebp [Ok] 12:11:18 DEBUG| [stdout] Test int 3 trap [Failed] 12:11:18 DEBUG| [stdout] selftests: breakpoint_test [PASS] 12:11:18 DEBUG| [stdout] /tmp/autopkgtest.zKFdZm/build.ham/linux-4.11.0/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/breakpoints ... and on the console we see a lot of messages like: ** 35 printk messages dropped ** [ 3577.683828] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 33 printk messages dropped ** [ 3577.686564] ACPI Error: Could not disable RealTimeClock events (20170119/evxfevnt-267) ** 25 printk messages dropped ** [ 3577.688566] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 35 printk messages dropped ** [ 3577.692788] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 29 printk messages dropped ** [ 3577.695184] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 34 printk messages dropped ** [ 3577.697955] ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20170119/evevent-286) I've attached the full log. In the log file there is the invocation I used to generate the failing log. You should be able to try similar using either `qemu' locally. If that doesn't reproduce, try on Canonistack. If *that* doesn't reproduce, apw or I can run test builds for you if there's a PPA to test from. This tickles an unfortunate behaviour in the way we run autopkgtest. What happens is: the machine hangs, autopkgtest notices this has happened, it tries to clean up the testbed and can't get into it because it is hung. This is counted as a 'temporary failure', and so the job is requeued forever. As a result, I've blacklisted linux from the workers. Please reach out to us for manual runs, and then once it is confirmed to not loop in this way we'll remove the blacklist. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-stop-nagging ** Attachment added: "linux.tar.xz" https://bugs.launchpad.net/bugs/1706283/+attachment/4920916/+files/linux.tar.xz -- 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/1706283 Title: ADT tests fail since 4.11.0-11.16 Status in linux package in Ubuntu: Incomplete Bug description: The ADT tests started failing with 4.11.0-11.16 on amd64, i386 and ppc64el: all the arches we run using qemu over OpenStack. The virtual machines hang completely. The last lines in the log are: 12:11:18 DEBUG| [stdout] Test icebp [Ok] 12:11:18 DEBUG| [stdout] Test int 3 trap [Failed] 12:11:18 DEBUG| [stdout] selftests: breakpoint_test [PASS] 12:11:18 DEBUG| [stdout] /tmp/autopkgtest.zKFdZm/build.ham/linux-4.11.0/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/breakpoints ... and on the console we see a lot of messages like: ** 35 printk messages dropped ** [ 3577.683828] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 33 printk messages dropped ** [ 3577.686564] ACPI Error: Could not disable RealTimeClock events (20170119/evxfevnt-267) ** 25 printk messages dropped ** [ 3577.688566] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 35 printk messages dropped ** [ 3577.692788] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 29 printk messages dropped ** [ 3577.695184] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20170119/evevent-286) ** 34 printk messages dropped ** [ 3577.697955] ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20170119/evevent-286) I've attached the full log. In the log file there is the invocation I used to generate the failing log. You should be able to try similar using either `qemu' locally. If that doesn't reproduce, try on Canonistack. If *that* doesn't reproduce, apw or I can run test builds for you if there's a PPA to test from. This tickles an unfortunate behaviour in the way we run autopkgtest. What happens is: the machine hangs, autopkgtest notices this has happened, it tries to clean up the testbed and can't get into it because it is hung. This is counted as a 'temporary failure', and so the job is requeued forever. As a result, I've blacklisted linux from the workers. Please reach out to us for manual runs, and then once it is confirmed to not loop in th
[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0
Maybe IS happens to have a box that's not provisioned yet and you can borrow? Or you can borrow that one for a bit if lgw01 has some spare capacity? Or they'll upgrade to the current lts-xenial kernel so we maybe get lucky. :) -- 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/1682077 Title: nested KVM fails - KVM: entry failed, hardware error 0x0 Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Bug description: Hello, We just noticed that systemd's autopkgtests have started failing often on amd64 for all releases, when run in Canonical's scalingstack cloud. This is nested KVM I think. TEST RUN: Basic systemd setup + /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel /boot/vmlinuz-4.10.0-19-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.unFR7V/rootdisk.img -initrd /boot/initrd.img-4.10.0-19-generic -machine accel=kvm -enable-kvm -cpu host -append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no ' KVM: entry failed, hardware error 0x0 EAX= EBX= ECX= EDX=000206a1 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=d8 66 e8 d8 a2 ff ff 66 5b 66 83 c4 08 66 5b 66 5e 66 c3 90 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I have observed a failure on the compute node (region lgw01) Linux amemasu 4.4.0-59-generic #80~14.04.1-Ubuntu SMP Fri Jan 6 18:02:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and a pass of the exact same package on the compute node (region lcy01) Linux kissel 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Here's an example log- https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty-ci-train-ppa-service-2713/zesty/amd64/s/systemd/20170411_182221_b8bea@/log.gz I found bug #1329434 which looks more or less identical and was fixed for 3.13. Perhaps it regressed in 4.4? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681566] Re: nvidia-375 DKMS module not recompiled on upgrade to 17.04
** Changed in: nvidia-graphics-drivers-375 (Ubuntu) Status: Confirmed => Invalid ** Changed in: virtualbox (Ubuntu) Status: Confirmed => Invalid ** Also affects: virtualbox (Ubuntu Zesty) Importance: Undecided Status: Invalid ** Also affects: dkms (Ubuntu Zesty) Importance: Undecided Status: Confirmed ** Also affects: ubuntu-release-upgrader (Ubuntu Zesty) Importance: Undecided Status: Invalid ** Also affects: nvidia-graphics-drivers-375 (Ubuntu Zesty) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1681566 Title: nvidia-375 DKMS module not recompiled on upgrade to 17.04 Status in dkms package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-375 package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in dkms source package in Zesty: Confirmed Status in nvidia-graphics-drivers-375 source package in Zesty: Invalid Status in ubuntu-release-upgrader source package in Zesty: Invalid Status in virtualbox source package in Zesty: Invalid Bug description: When upgrading from 16.10 to 17.04 using `update-manager -d`, the `nvidia-375` DKMS modules are not compiled for the new kernel. The result is that the user must run `apt install --reinstall nvidia-375` and reboot. To reproduce this: - Clean install of 16.10 on a system with NVIDIA graphics - Install `nvidia-375` - Run `update-manager -d`, complete all steps, then reboot - You will be unable to login until running `apt install --reinstall nvidia-375` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1681566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681566] Re: nvidia-375 DKMS module not recompiled on upgrade to 17.04
With my patch, tested like so - boot a yakkety cloud vm - install bcmwl-kernel-source virtualbox-dkms ubuntu-release-upgrader-core from yakkety - install dkms from comment #19 - do-release-upgrade -d - [...] - dkms status ubuntu@autopkgtest:~$ sudo dkms status bcmwl, 6.30.223.271+bdcom, 4.10.0-19-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.8.0-46-generic, x86_64: installed virtualbox, 5.1.18, 4.10.0-19-generic, x86_64: installed virtualbox, 5.1.18, 4.8.0-46-generic, x86_64: installed But I would like someone that's not me to test please. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1681566 Title: nvidia-375 DKMS module not recompiled on upgrade to 17.04 Status in dkms package in Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Confirmed Bug description: When upgrading from 16.10 to 17.04 using `update-manager -d`, the `nvidia-375` DKMS modules are not compiled for the new kernel. The result is that the user must run `apt install --reinstall nvidia-375` and reboot. To reproduce this: - Clean install of 16.10 on a system with NVIDIA graphics - Install `nvidia-375` - Run `update-manager -d`, complete all steps, then reboot - You will be unable to login until running `apt install --reinstall nvidia-375` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1681566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681566] Re: nvidia-375 DKMS module not recompiled on upgrade to 17.04
Here's my take 2, which was forwarded upstream. Could someone review/test please? ** Patch added: "lp1661843-v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1681566/+attachment/4861224/+files/lp1661843-v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1681566 Title: nvidia-375 DKMS module not recompiled on upgrade to 17.04 Status in dkms package in Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Confirmed Bug description: When upgrading from 16.10 to 17.04 using `update-manager -d`, the `nvidia-375` DKMS modules are not compiled for the new kernel. The result is that the user must run `apt install --reinstall nvidia-375` and reboot. To reproduce this: - Clean install of 16.10 on a system with NVIDIA graphics - Install `nvidia-375` - Run `update-manager -d`, complete all steps, then reboot - You will be unable to login until running `apt install --reinstall nvidia-375` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1681566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681566] Re: nvidia-375 DKMS module not recompiled on upgrade to 17.04
Also this appears to not reproduce every time :( ubuntu@autopkgtest:/lib/modules$ find -name wl.ko ./4.10.0-19-generic/updates/dkms/wl.ko ./4.8.0-46-generic/updates/dkms/wl.ko -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1681566 Title: nvidia-375 DKMS module not recompiled on upgrade to 17.04 Status in dkms package in Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Confirmed Bug description: When upgrading from 16.10 to 17.04 using `update-manager -d`, the `nvidia-375` DKMS modules are not compiled for the new kernel. The result is that the user must run `apt install --reinstall nvidia-375` and reboot. To reproduce this: - Clean install of 16.10 on a system with NVIDIA graphics - Install `nvidia-375` - Run `update-manager -d`, complete all steps, then reboot - You will be unable to login until running `apt install --reinstall nvidia-375` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1681566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681566] Re: nvidia-375 DKMS module not recompiled on upgrade to 17.04
The function says above it "# Get the most recent kernel on Debian based systems. This keeps # into account both the version and the ABI. If the current kernel # is the most recent kernel then the function will print a null string." so I think that my previous patch is wrong. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1681566 Title: nvidia-375 DKMS module not recompiled on upgrade to 17.04 Status in dkms package in Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Confirmed Bug description: When upgrading from 16.10 to 17.04 using `update-manager -d`, the `nvidia-375` DKMS modules are not compiled for the new kernel. The result is that the user must run `apt install --reinstall nvidia-375` and reboot. To reproduce this: - Clean install of 16.10 on a system with NVIDIA graphics - Install `nvidia-375` - Run `update-manager -d`, complete all steps, then reboot - You will be unable to login until running `apt install --reinstall nvidia-375` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1681566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0
For me it's enough to boot an instance on an affected lgw01 compute node, install qemu-system-x86, download a cloud image and run "/usr/bin /qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -drive format=raw,cache=unsafe,file=zesty-server-cloudimg-amd64.img -machine accel=kvm -enable-kvm -cpu host" -- 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/1682077 Title: nested KVM fails - KVM: entry failed, hardware error 0x0 Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Bug description: Hello, We just noticed that systemd's autopkgtests have started failing often on amd64 for all releases, when run in Canonical's scalingstack cloud. This is nested KVM I think. TEST RUN: Basic systemd setup + /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel /boot/vmlinuz-4.10.0-19-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.unFR7V/rootdisk.img -initrd /boot/initrd.img-4.10.0-19-generic -machine accel=kvm -enable-kvm -cpu host -append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no ' KVM: entry failed, hardware error 0x0 EAX= EBX= ECX= EDX=000206a1 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=d8 66 e8 d8 a2 ff ff 66 5b 66 83 c4 08 66 5b 66 5e 66 c3 90 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I have observed a failure on the compute node (region lgw01) Linux amemasu 4.4.0-59-generic #80~14.04.1-Ubuntu SMP Fri Jan 6 18:02:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and a pass of the exact same package on the compute node (region lcy01) Linux kissel 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Here's an example log- https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty-ci-train-ppa-service-2713/zesty/amd64/s/systemd/20170411_182221_b8bea@/log.gz I found bug #1329434 which looks more or less identical and was fixed for 3.13. Perhaps it regressed in 4.4? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682077] [NEW] nested KVM fails - KVM: entry failed, hardware error 0x0
Public bug reported: Hello, We just noticed that systemd's autopkgtests have started failing often on amd64 for all releases, when run in Canonical's scalingstack cloud. This is nested KVM I think. TEST RUN: Basic systemd setup + /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel /boot/vmlinuz-4.10.0-19-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.unFR7V/rootdisk.img -initrd /boot/initrd.img-4.10.0-19-generic -machine accel=kvm -enable-kvm -cpu host -append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no ' KVM: entry failed, hardware error 0x0 EAX= EBX= ECX= EDX=000206a1 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=d8 66 e8 d8 a2 ff ff 66 5b 66 83 c4 08 66 5b 66 5e 66 c3 90 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I have observed a failure on the compute node (region lgw01) Linux amemasu 4.4.0-59-generic #80~14.04.1-Ubuntu SMP Fri Jan 6 18:02:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and a pass of the exact same package on the compute node (region lcy01) Linux kissel 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Here's an example log- https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty-ci-train-ppa-service-2713/zesty/amd64/s/systemd/20170411_182221_b8bea@/log.gz I found bug #1329434 which looks more or less identical and was fixed for 3.13. Perhaps it regressed in 4.4? ** Affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-lts-xenial (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682077 Title: nested KVM fails - KVM: entry failed, hardware error 0x0 Status in linux-lts-xenial package in Ubuntu: New Bug description: Hello, We just noticed that systemd's autopkgtests have started failing often on amd64 for all releases, when run in Canonical's scalingstack cloud. This is nested KVM I think. TEST RUN: Basic systemd setup + /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel /boot/vmlinuz-4.10.0-19-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.unFR7V/rootdisk.img -initrd /boot/initrd.img-4.10.0-19-generic -machine accel=kvm -enable-kvm -cpu host -append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no ' KVM: entry failed, hardware error 0x0 EAX= EBX= ECX= EDX=000206a1 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=d8 66 e8 d8 a2 ff ff 66 5b 66 83 c4 08 66 5b 66 5e 66 c3 90 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I have observed a failure on the compute node (region lgw01) Linux amemasu 4.4.0-59-generic #80~14.04.1-Ubuntu SMP Fri Jan 6 18:02:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and a pass of the exact same package on the compute node (region lcy01) Linux kissel 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Here's an example log- https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty-ci-train-ppa-service-2713/zesty/amd64/s/systemd/20170411_182221_b8bea@/log.gz I found bug #1329434 which looks more or less identical and was fixed for 3.13. Perhaps it regressed in 4.4? To manage noti
[Kernel-packages] [Bug 1581132] Re: [Xenial] net: updates to ethtool and virtio_net for speed/duplex support
** 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/1581132 Title: [Xenial] net: updates to ethtool and virtio_net for speed/duplex support Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Committed Bug description: Post 4.4, several changes landed upsteam to allow users to set interface speed for virtio_net backed devices. This feature is extremely useful for those doing large-scale networking simulations where Ubuntu-based VMs are used to simulate hosts. Not only does it allow hosts to report the same speed in simulations for monitoring tools, but it is required to simulate 802.3ad bonding where link-speed is reported to the peer device. Without proper speed setting there are cases where establishing LACP adjacency is not possible. After this patch setting the link speed and duplex now works just as one would expect. I'm running the kernel that contains this patch for these commands: $ sudo ethtool -s enp0s8 speed 10 duplex full $ sudo ethtool enp0s8 Settings for enp0s8: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: 10Mb/s Duplex: Full Port: Other PHYAD: 0 Transceiver: internal Auto-negotiation: off Link detected: yes I've already submitted patches to the kernel-team mailing list. Those patches can be found in this thread: https://lists.ubuntu.com/archives /kernel-team/2016-May/077286.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1592930] Re: failures building userspace packages that include ethtool.h
Seems to work, thanks ** 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/1592930 Title: failures building userspace packages that include ethtool.h Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Committed Bug description: Current -proposed kernel produces errors when building userspace packages that require ethtool.h from linux-headers. This was noted by Iain Lane when building systemd with this kernel: In file included from ../src/udev/net/ethtool-util.c:22:0: /usr/include/linux/ethtool.h: In function ‘ethtool_validate_speed’: /usr/include/linux/ethtool.h:1321:18: error: ‘INT_MAX’ undeclared (first use in this function) return speed <= INT_MAX || speed == SPEED_UNKNOWN; ^ /usr/include/linux/ethtool.h:1321:18: note: each undeclared identifier is reported only once for each function it appears in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581132] Re: [Xenial] net: updates to ethtool and virtio_net for speed/duplex support
** Changed in: linux (Ubuntu) Status: Fix Released => Triaged -- 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/1581132 Title: [Xenial] net: updates to ethtool and virtio_net for speed/duplex support Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Committed Bug description: Post 4.4, several changes landed upsteam to allow users to set interface speed for virtio_net backed devices. This feature is extremely useful for those doing large-scale networking simulations where Ubuntu-based VMs are used to simulate hosts. Not only does it allow hosts to report the same speed in simulations for monitoring tools, but it is required to simulate 802.3ad bonding where link-speed is reported to the peer device. Without proper speed setting there are cases where establishing LACP adjacency is not possible. After this patch setting the link speed and duplex now works just as one would expect. I'm running the kernel that contains this patch for these commands: $ sudo ethtool -s enp0s8 speed 10 duplex full $ sudo ethtool enp0s8 Settings for enp0s8: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: 10Mb/s Duplex: Full Port: Other PHYAD: 0 Transceiver: internal Auto-negotiation: off Link detected: yes I've already submitted patches to the kernel-team mailing list. Those patches can be found in this thread: https://lists.ubuntu.com/archives /kernel-team/2016-May/077286.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581132] Re: [Xenial] net: updates to ethtool and virtio_net for speed/duplex support
When building systemd with this kernel: In file included from ../src/udev/net/ethtool-util.c:22:0: /usr/include/linux/ethtool.h: In function ‘ethtool_validate_speed’: /usr/include/linux/ethtool.h:1321:18: error: ‘INT_MAX’ undeclared (first use in this function) return speed <= INT_MAX || speed == SPEED_UNKNOWN; ^ /usr/include/linux/ethtool.h:1321:18: note: each undeclared identifier is reported only once for each function it appears in ...I think you need to cherry-pick 14e2037902d65213842b4e40305ff54a64abbcb6 ** Tags removed: verification-done verification-done-xenial xenial ** Tags added: verification-failed ** Tags added: 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/1581132 Title: [Xenial] net: updates to ethtool and virtio_net for speed/duplex support Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: Post 4.4, several changes landed upsteam to allow users to set interface speed for virtio_net backed devices. This feature is extremely useful for those doing large-scale networking simulations where Ubuntu-based VMs are used to simulate hosts. Not only does it allow hosts to report the same speed in simulations for monitoring tools, but it is required to simulate 802.3ad bonding where link-speed is reported to the peer device. Without proper speed setting there are cases where establishing LACP adjacency is not possible. After this patch setting the link speed and duplex now works just as one would expect. I'm running the kernel that contains this patch for these commands: $ sudo ethtool -s enp0s8 speed 10 duplex full $ sudo ethtool enp0s8 Settings for enp0s8: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: 10Mb/s Duplex: Full Port: Other PHYAD: 0 Transceiver: internal Auto-negotiation: off Link detected: yes I've already submitted patches to the kernel-team mailing list. Those patches can be found in this thread: https://lists.ubuntu.com/archives /kernel-team/2016-May/077286.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1358966] Re: Broadcom kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given]
I showed my build logs. If you want me to help, I'm happy to, I just need better steps. Are you saying that broadcom-sta doesn't work for anyone? If that's right, what am I doing wrong? (I've unsubscribed ubuntu-sponsors since this is on the list and there is nothing to sponsor ATM, given my questions. Please re-subscribe them when there is.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1358966 Title: Broadcom kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given] Status in bcmwl package in Ubuntu: Fix Released Status in broadcom-sta package in Ubuntu: Incomplete Bug description: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 will not build with linux-3.17-rc1 from Ubuntu kernel ppa (Mainline). Tried custom kernel as well from kernel archives 3.17-rc1. APPORT ERROR ProblemType: Package DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 Uname: Linux 3.16.1-custom x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.17.0-031700rc1-generic Date: Tue Aug 19 19:42:02 2014 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu1:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:64: error: macro "alloc_netdev" requires 4 arguments, but only 3 given InstallationDate: Installed on 2014-07-05 (45 days ago) InstallationMedia: Ubuntu "Utopic" - Build amd64 LIVE Binary 20140703-15:52 PackageVersion: 6.30.223.248+bdcom-0ubuntu1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1358966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1358966] Re: Broadcom kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given]
I tried broadcom-sta on xenial > Setting up broadcom-sta-dkms (6.30.223.271-1) ... > Loading new broadcom-sta-6.30.223.271 DKMS files... > First Installation: checking all kernels... > Building for 4.2.0-19-generic and 4.3.0-2-generic > Building initial module for 4.2.0-19-generic > Done. > > wl: > Running module version sanity check. > - Original module >- No original module exists within this kernel > - Installation >- Installing to /lib/modules/4.2.0-19-generic/updates/dkms/ > > depmod > > Backing up initrd.img-4.2.0-19-generic to > /boot/initrd.img-4.2.0-19-generic.old-dkms > Making new initrd.img-4.2.0-19-generic > (If next boot fails, revert to initrd.img-4.2.0-19-generic.old-dkms image) > update-initramfs > > DKMS: install completed. > Building initial module for 4.3.0-2-generic > Done. > > wl: > Running module version sanity check. > - Original module >- No original module exists within this kernel > - Installation >- Installing to /lib/modules/4.3.0-2-generic/updates/dkms/ > > depmod > > Backing up initrd.img-4.3.0-2-generic to > /boot/initrd.img-4.3.0-2-generic.old-dkms > Making new initrd.img-4.3.0-2-generic > (If next boot fails, revert to initrd.img-4.3.0-2-generic.old-dkms image) > update-initramfs > > DKMS: install completed. and 14.04 > Loading new broadcom-sta-6.30.223.141 DKMS files... > First Installation: checking all kernels... > Building for 3.13.0-68-generic and 3.13.0-71-generic > Building initial module for 3.13.0-68-generic > Done. > > wl: > Running module version sanity check. > - Original module >- No original module exists within this kernel > - Installation >- Installing to /lib/modules/3.13.0-68-generic/updates/dkms/ > > depmod. > > Backing up initrd.img-3.13.0-68-generic to > /boot/initrd.img-3.13.0-68-generic.old-dkms > Making new initrd.img-3.13.0-68-generic > (If next boot fails, revert to initrd.img-3.13.0-68-generic.old-dkms image) > update-initramfs > > DKMS: install completed. > Building initial module for 3.13.0-71-generic > Done. > > wl: > Running module version sanity check. > - Original module >- No original module exists within this kernel > - Installation >- Installing to /lib/modules/3.13.0-71-generic/updates/dkms/ > > depmod > > Backing up initrd.img-3.13.0-71-generic to > /boot/initrd.img-3.13.0-71-generic.old-dkms > Making new initrd.img-3.13.0-71-generic > (If next boot fails, revert to initrd.img-3.13.0-71-generic.old-dkms image) > update-initramfs > > DKMS: install completed. so I don't understand what this bug is about. Can someone give reproduction steps for -sta please? ** Changed in: broadcom-sta (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1358966 Title: Broadcom kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given] Status in bcmwl package in Ubuntu: Fix Released Status in broadcom-sta package in Ubuntu: Incomplete Bug description: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 will not build with linux-3.17-rc1 from Ubuntu kernel ppa (Mainline). Tried custom kernel as well from kernel archives 3.17-rc1. APPORT ERROR ProblemType: Package DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 Uname: Linux 3.16.1-custom x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.17.0-031700rc1-generic Date: Tue Aug 19 19:42:02 2014 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu1:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:64: error: macro "alloc_netdev" requires 4 arguments, but only 3 given InstallationDate: Installed on 2014-07-05 (45 days ago) InstallationMedia: Ubuntu "Utopic" - Build amd64 LIVE Binary 20140703-15:52 PackageVersion: 6.30.223.248+bdcom-0ubuntu1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1358966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1478623] Re: [4.1.0 regression] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test
On Mon, Aug 24, 2015 at 06:14:48PM -, Joseph Salisbury wrote:
> Thanks, Iain. That got me a little further, but it seems I may still be
> missing something:
>
> ubuntu@autopkgtest:~/udisks2-2.1.6$ sudo debian/tests/upstream-system
> Testing installed system binaries
> Traceback (most recent call last):
> File "src/tests/integration-test", line 1475, in
> UDisksTestCase.init(logfile=args.logfile)
> File "src/tests/integration-test", line 108, in init
> for l in
> open('/usr/share/dbus-1/system-services/org.freedesktop.UDisks2.service'):
> FileNotFoundError: [Errno 2] No such file or directory:
> '/usr/share/dbus-1/system-services/org.freedesktop.UDisks2.service'
sounds like you want udisks2 (install *all* binaries built from the
udisks2 source package):
laney@nightingale> dpkg -S
/usr/share/dbus-1/system-services/org.freedesktop.UDisks2.service
udisks2: /usr/share/dbus-1/system-services/org.freedesktop.UDisks2.service
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.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/1478623
Title:
[4.1.0 regression] Kernel oops - blk_update_request: I/O error when
running udisks2 force_test_removal test
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Wily:
In Progress
Bug description:
We noticed that the udisks2 autopkgtest is failing on i386 in the
"forced removal" test, for example
https://jenkins.qa.ubuntu.com/job/wily-adt-
udisks2/ARCH=i386,label=adt/55/console
I reproduced this locally, on this kernel
ubuntu@autopkgtest:~$ uname -a
Linux autopkgtest 4.1.0-2-generic #2-Ubuntu SMP Wed Jul 22 18:17:34 UTC 2015
i686 i686 i686 GNU/Linux
and got the following spewed to console
fs: forced removal ... [ 303.782426] blk_update_request: I/O error, dev sdb,
sector 0
[ 303.807400] BUG: unable to handle kernel paging request at 1afde000
[ 303.808010] IP: [] __percpu_counter_add+0x16/0x90
[ 303.808010] *pdpt = 0ee9b001 *pde =
[ 303.808010] Oops: [#1] SMP
[ 303.808010] Modules linked in: scsi_debug btrfs xor raid6_pq ufs qnx4
hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ppdev kvm_intel kvm joydev
serio_raw 8250_fintek parport_pc parport i2c_piix4 mac_hid autofs4 psmouse
pata_acpi floppy
[ 303.808010] CPU: 0 PID: 22573 Comm: umount Not tainted 4.1.0-2-generic
#2-Ubuntu
[ 303.808010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
1.8.1-20150604_211837-tipua 04/01/2014
[ 303.808010] task: dc75e5e0 ti: ce85a000 task.ti: ce85a000
[ 303.808010] EIP: 0060:[] EFLAGS: 00010092 CPU: 0
[ 303.808010] EIP is at __percpu_counter_add+0x16/0x90
[ 303.808010] EAX: 0001 EBX: dbba9c08 ECX: EDX: 0001
[ 303.808010] ESI: EDI: EBP: ce85be6c ESP: ce85be54
[ 303.808010] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 303.808010] CR0: 8005003b CR2: 1afde000 CR3: 1e9c88c0 CR4: 07f0
[ 303.808010] Stack:
[ 303.808010] c1aa7b40 0001 dbba9be8 decbfd60
ce85be88 c115bca4
[ 303.808010] 0008 ddce5228 ddce5228 decbfd60 decbfd70 ce85bea4
c11e47f9
[ 303.808010] 0286 ddce5228 d559cbd0 cdd41400 ce85beb4 c11e496f
d3cc2000
[ 303.808010] Call Trace:
[ 303.808010] [] account_page_dirtied+0x74/0xf0
[ 303.808010] [] __set_page_dirty+0x39/0xc0
[ 303.808010] [] mark_buffer_dirty+0x4f/0xb0
[ 303.808010] [] ext4_commit_super+0x168/0x220
[ 303.808010] [] ext4_put_super+0xc1/0x310
[ 303.808010] [] ? dispose_list+0x32/0x40
[ 303.808010] [] ? evict_inodes+0xda/0xf0
[ 303.808010] [] generic_shutdown_super+0x64/0xe0
[ 303.808010] [] ? unregister_shrinker+0x40/0x50
[ 303.808010] [] kill_block_super+0x1f/0x70
[ 303.808010] [] deactivate_locked_super+0x3d/0x70
[ 303.808010] [] deactivate_super+0x57/0x60
[ 303.808010] [] cleanup_mnt+0x39/0x90
[ 303.808010] [] __cleanup_mnt+0x10/0x20
[ 303.808010] [] task_work_run+0xb1/0xd0
[ 303.808010] [] do_notify_resume+0x53/0x70
[ 303.808010] [] work_notifysig+0x26/0x2b
[ 303.808010] Code: 24 8b 54 24 04 83 c4 08 5b 5e 5f 5d c3 90 8d b4 26 00 00
00 00 55 89 e5 57 56 53 89 c3 89 d0 83 ec 0c 89 45 ec 89 4d f0 8b 7b 14 <64> 8b
37 89 7d e8 89 f7 c1 ff 1f 01 c6 11 cf 8b 4d 08 c1 f9 1f
[ 303.808010] EIP: [] __percpu_counter_add+0x16/0x90 SS:ESP
0068:ce85be54
[ 303.808010] CR2: 1afde000
[ 303.808010] ---[ end trace bd84bb1a9fa3ebd4 ]---
[ 304.463429] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0184
PQ: 0 ANSI: 6
[ 304.468098] sd 2:0:0:0:
Re: [Kernel-packages] [Bug 1478623] Re: [4.1.0 regression] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test
On Fri, Aug 21, 2015 at 04:58:30PM -, Joseph Salisbury wrote: > I have an environment setup to try and reproduce/bisect the bug. > However, I'm getting an error when running the test. Have you seen > this: > > > ubuntu@autopkgtest:~/udisks2-2.1.6$ sudo debian/tests/upstream-system > Traceback (most recent call last): > File "", line 2158, in _find_spec > AttributeError: 'DynamicImporter' object has no attribute 'find_spec' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "src/tests/integration-test", line 61, in > from gi.repository import GLib, Gio, UDisks > File "/usr/lib/python3/dist-packages/gi/importer.py", line 144, in > find_module > 'introspection typelib not found' % namespace) > ImportError: cannot import name UDisks, introspection typelib not found I guess you want gir1.2-udisks-2.0 - do you have this installed? The '@' in the test-depends means that you should install the binary packages produced by this source. Sorry for not being precise enough in the description. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.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/1478623 Title: [4.1.0 regression] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Bug description: We noticed that the udisks2 autopkgtest is failing on i386 in the "forced removal" test, for example https://jenkins.qa.ubuntu.com/job/wily-adt- udisks2/ARCH=i386,label=adt/55/console I reproduced this locally, on this kernel ubuntu@autopkgtest:~$ uname -a Linux autopkgtest 4.1.0-2-generic #2-Ubuntu SMP Wed Jul 22 18:17:34 UTC 2015 i686 i686 i686 GNU/Linux and got the following spewed to console fs: forced removal ... [ 303.782426] blk_update_request: I/O error, dev sdb, sector 0 [ 303.807400] BUG: unable to handle kernel paging request at 1afde000 [ 303.808010] IP: [] __percpu_counter_add+0x16/0x90 [ 303.808010] *pdpt = 0ee9b001 *pde = [ 303.808010] Oops: [#1] SMP [ 303.808010] Modules linked in: scsi_debug btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ppdev kvm_intel kvm joydev serio_raw 8250_fintek parport_pc parport i2c_piix4 mac_hid autofs4 psmouse pata_acpi floppy [ 303.808010] CPU: 0 PID: 22573 Comm: umount Not tainted 4.1.0-2-generic #2-Ubuntu [ 303.808010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.8.1-20150604_211837-tipua 04/01/2014 [ 303.808010] task: dc75e5e0 ti: ce85a000 task.ti: ce85a000 [ 303.808010] EIP: 0060:[] EFLAGS: 00010092 CPU: 0 [ 303.808010] EIP is at __percpu_counter_add+0x16/0x90 [ 303.808010] EAX: 0001 EBX: dbba9c08 ECX: EDX: 0001 [ 303.808010] ESI: EDI: EBP: ce85be6c ESP: ce85be54 [ 303.808010] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 303.808010] CR0: 8005003b CR2: 1afde000 CR3: 1e9c88c0 CR4: 07f0 [ 303.808010] Stack: [ 303.808010] c1aa7b40 0001 dbba9be8 decbfd60 ce85be88 c115bca4 [ 303.808010] 0008 ddce5228 ddce5228 decbfd60 decbfd70 ce85bea4 c11e47f9 [ 303.808010] 0286 ddce5228 d559cbd0 cdd41400 ce85beb4 c11e496f d3cc2000 [ 303.808010] Call Trace: [ 303.808010] [] account_page_dirtied+0x74/0xf0 [ 303.808010] [] __set_page_dirty+0x39/0xc0 [ 303.808010] [] mark_buffer_dirty+0x4f/0xb0 [ 303.808010] [] ext4_commit_super+0x168/0x220 [ 303.808010] [] ext4_put_super+0xc1/0x310 [ 303.808010] [] ? dispose_list+0x32/0x40 [ 303.808010] [] ? evict_inodes+0xda/0xf0 [ 303.808010] [] generic_shutdown_super+0x64/0xe0 [ 303.808010] [] ? unregister_shrinker+0x40/0x50 [ 303.808010] [] kill_block_super+0x1f/0x70 [ 303.808010] [] deactivate_locked_super+0x3d/0x70 [ 303.808010] [] deactivate_super+0x57/0x60 [ 303.808010] [] cleanup_mnt+0x39/0x90 [ 303.808010] [] __cleanup_mnt+0x10/0x20 [ 303.808010] [] task_work_run+0xb1/0xd0 [ 303.808010] [] do_notify_resume+0x53/0x70 [ 303.808010] [] work_notifysig+0x26/0x2b [ 303.808010] Code: 24 8b 54 24 04 83 c4 08 5b 5e 5f 5d c3 90 8d b4 26 00 00 00 00 55 89 e5 57 56 53 89 c3 89 d0 83 ec 0c 89 45 ec 89 4d f0 8b 7b 14 <64> 8b 37 89 7d e8 89 f7 c1 ff 1f 01 c6 11 cf 8b 4d 08 c1 f9 1f [ 303.808010] EIP: [] __percpu_counter_add+0x16/0x90 SS:ESP 0068:ce85be54 [ 303.808010] CR2: 1afde0
Re: [Kernel-packages] [Bug 1478623] Re: [4.1.0 regression] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test
On Mon, Aug 03, 2015 at 05:55:35PM -, Joseph Salisbury wrote: > Do you know if I perform the steps listed to reproduce the issue in a VM > or do I need some dedicated hardware? In a VM - the first command I listed (adt-buildvm-ubuntu-cloud from the `autopkgtest' package) will download and construct one for you, then you just need to boot into it and install the stuff to run udisks2's autopkgtest. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.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/1478623 Title: [4.1.0 regression] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Bug description: We noticed that the udisks2 autopkgtest is failing on i386 in the "forced removal" test, for example https://jenkins.qa.ubuntu.com/job/wily-adt- udisks2/ARCH=i386,label=adt/55/console I reproduced this locally, on this kernel ubuntu@autopkgtest:~$ uname -a Linux autopkgtest 4.1.0-2-generic #2-Ubuntu SMP Wed Jul 22 18:17:34 UTC 2015 i686 i686 i686 GNU/Linux and got the following spewed to console fs: forced removal ... [ 303.782426] blk_update_request: I/O error, dev sdb, sector 0 [ 303.807400] BUG: unable to handle kernel paging request at 1afde000 [ 303.808010] IP: [] __percpu_counter_add+0x16/0x90 [ 303.808010] *pdpt = 0ee9b001 *pde = [ 303.808010] Oops: [#1] SMP [ 303.808010] Modules linked in: scsi_debug btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ppdev kvm_intel kvm joydev serio_raw 8250_fintek parport_pc parport i2c_piix4 mac_hid autofs4 psmouse pata_acpi floppy [ 303.808010] CPU: 0 PID: 22573 Comm: umount Not tainted 4.1.0-2-generic #2-Ubuntu [ 303.808010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.8.1-20150604_211837-tipua 04/01/2014 [ 303.808010] task: dc75e5e0 ti: ce85a000 task.ti: ce85a000 [ 303.808010] EIP: 0060:[] EFLAGS: 00010092 CPU: 0 [ 303.808010] EIP is at __percpu_counter_add+0x16/0x90 [ 303.808010] EAX: 0001 EBX: dbba9c08 ECX: EDX: 0001 [ 303.808010] ESI: EDI: EBP: ce85be6c ESP: ce85be54 [ 303.808010] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 303.808010] CR0: 8005003b CR2: 1afde000 CR3: 1e9c88c0 CR4: 07f0 [ 303.808010] Stack: [ 303.808010] c1aa7b40 0001 dbba9be8 decbfd60 ce85be88 c115bca4 [ 303.808010] 0008 ddce5228 ddce5228 decbfd60 decbfd70 ce85bea4 c11e47f9 [ 303.808010] 0286 ddce5228 d559cbd0 cdd41400 ce85beb4 c11e496f d3cc2000 [ 303.808010] Call Trace: [ 303.808010] [] account_page_dirtied+0x74/0xf0 [ 303.808010] [] __set_page_dirty+0x39/0xc0 [ 303.808010] [] mark_buffer_dirty+0x4f/0xb0 [ 303.808010] [] ext4_commit_super+0x168/0x220 [ 303.808010] [] ext4_put_super+0xc1/0x310 [ 303.808010] [] ? dispose_list+0x32/0x40 [ 303.808010] [] ? evict_inodes+0xda/0xf0 [ 303.808010] [] generic_shutdown_super+0x64/0xe0 [ 303.808010] [] ? unregister_shrinker+0x40/0x50 [ 303.808010] [] kill_block_super+0x1f/0x70 [ 303.808010] [] deactivate_locked_super+0x3d/0x70 [ 303.808010] [] deactivate_super+0x57/0x60 [ 303.808010] [] cleanup_mnt+0x39/0x90 [ 303.808010] [] __cleanup_mnt+0x10/0x20 [ 303.808010] [] task_work_run+0xb1/0xd0 [ 303.808010] [] do_notify_resume+0x53/0x70 [ 303.808010] [] work_notifysig+0x26/0x2b [ 303.808010] Code: 24 8b 54 24 04 83 c4 08 5b 5e 5f 5d c3 90 8d b4 26 00 00 00 00 55 89 e5 57 56 53 89 c3 89 d0 83 ec 0c 89 45 ec 89 4d f0 8b 7b 14 <64> 8b 37 89 7d e8 89 f7 c1 ff 1f 01 c6 11 cf 8b 4d 08 c1 f9 1f [ 303.808010] EIP: [] __percpu_counter_add+0x16/0x90 SS:ESP 0068:ce85be54 [ 303.808010] CR2: 1afde000 [ 303.808010] ---[ end trace bd84bb1a9fa3ebd4 ]--- [ 304.463429] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0184 PQ: 0 ANSI: 6 [ 304.468098] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 304.472038] sd 2:0:0:0: [sdc] 585728 512-byte logical blocks: (299 MB/286 MiB) [ 304.476079] sd 2:0:0:0: [sdc] Write Protect is off [ 304.476661] sd 2:0:0:0: [sdc] Mode Sense: 73 00 10 08 [ 304.484045] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 304.572090] sd 2:0:0:0: [sdc] Attached SCSI disk To reproduce, do something like this: $ adt-buildvm-ubuntu-cloud -r wily -a i386 # download a cloud image, fettle it a bit to be more useful $ qemu-system-i386 -m 2048 -net user -net nic,model=virtio -enable-kvm -no
Re: [Kernel-packages] [Bug 1478623] Re: [4.1.0 regression] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test
On Fri, Jul 31, 2015 at 05:57:58PM -, Joseph Salisbury wrote: > I attempted to revert the other two commits. However, there are allot > of prereqs that also need to be removed. I think a bisect would be > faster due to that. > > I started a bisect between v4.0 final and v4.1 final. It will require > testing about 8 - 10 test kernels. > > I built the first test kernel up to commit: > d0a3997c0c3f9351e24029349dee65dd1d9e8d84 > > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1478623/ > > Can you test this kernel and see if it exhibits this bug? I'll build > the next test kernel based on your results. I can do if you want, but it will be much faster if you (or someone who can easily build the new kernels) does it... If you like, I can supply a .img with the pre-reqs installed (by running the steps I gave in the bug description). Let me know what you think. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.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/1478623 Title: [4.1.0 regression] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Bug description: We noticed that the udisks2 autopkgtest is failing on i386 in the "forced removal" test, for example https://jenkins.qa.ubuntu.com/job/wily-adt- udisks2/ARCH=i386,label=adt/55/console I reproduced this locally, on this kernel ubuntu@autopkgtest:~$ uname -a Linux autopkgtest 4.1.0-2-generic #2-Ubuntu SMP Wed Jul 22 18:17:34 UTC 2015 i686 i686 i686 GNU/Linux and got the following spewed to console fs: forced removal ... [ 303.782426] blk_update_request: I/O error, dev sdb, sector 0 [ 303.807400] BUG: unable to handle kernel paging request at 1afde000 [ 303.808010] IP: [] __percpu_counter_add+0x16/0x90 [ 303.808010] *pdpt = 0ee9b001 *pde = [ 303.808010] Oops: [#1] SMP [ 303.808010] Modules linked in: scsi_debug btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ppdev kvm_intel kvm joydev serio_raw 8250_fintek parport_pc parport i2c_piix4 mac_hid autofs4 psmouse pata_acpi floppy [ 303.808010] CPU: 0 PID: 22573 Comm: umount Not tainted 4.1.0-2-generic #2-Ubuntu [ 303.808010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.8.1-20150604_211837-tipua 04/01/2014 [ 303.808010] task: dc75e5e0 ti: ce85a000 task.ti: ce85a000 [ 303.808010] EIP: 0060:[] EFLAGS: 00010092 CPU: 0 [ 303.808010] EIP is at __percpu_counter_add+0x16/0x90 [ 303.808010] EAX: 0001 EBX: dbba9c08 ECX: EDX: 0001 [ 303.808010] ESI: EDI: EBP: ce85be6c ESP: ce85be54 [ 303.808010] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 303.808010] CR0: 8005003b CR2: 1afde000 CR3: 1e9c88c0 CR4: 07f0 [ 303.808010] Stack: [ 303.808010] c1aa7b40 0001 dbba9be8 decbfd60 ce85be88 c115bca4 [ 303.808010] 0008 ddce5228 ddce5228 decbfd60 decbfd70 ce85bea4 c11e47f9 [ 303.808010] 0286 ddce5228 d559cbd0 cdd41400 ce85beb4 c11e496f d3cc2000 [ 303.808010] Call Trace: [ 303.808010] [] account_page_dirtied+0x74/0xf0 [ 303.808010] [] __set_page_dirty+0x39/0xc0 [ 303.808010] [] mark_buffer_dirty+0x4f/0xb0 [ 303.808010] [] ext4_commit_super+0x168/0x220 [ 303.808010] [] ext4_put_super+0xc1/0x310 [ 303.808010] [] ? dispose_list+0x32/0x40 [ 303.808010] [] ? evict_inodes+0xda/0xf0 [ 303.808010] [] generic_shutdown_super+0x64/0xe0 [ 303.808010] [] ? unregister_shrinker+0x40/0x50 [ 303.808010] [] kill_block_super+0x1f/0x70 [ 303.808010] [] deactivate_locked_super+0x3d/0x70 [ 303.808010] [] deactivate_super+0x57/0x60 [ 303.808010] [] cleanup_mnt+0x39/0x90 [ 303.808010] [] __cleanup_mnt+0x10/0x20 [ 303.808010] [] task_work_run+0xb1/0xd0 [ 303.808010] [] do_notify_resume+0x53/0x70 [ 303.808010] [] work_notifysig+0x26/0x2b [ 303.808010] Code: 24 8b 54 24 04 83 c4 08 5b 5e 5f 5d c3 90 8d b4 26 00 00 00 00 55 89 e5 57 56 53 89 c3 89 d0 83 ec 0c 89 45 ec 89 4d f0 8b 7b 14 <64> 8b 37 89 7d e8 89 f7 c1 ff 1f 01 c6 11 cf 8b 4d 08 c1 f9 1f [ 303.808010] EIP: [] __percpu_counter_add+0x16/0x90 SS:ESP 0068:ce85be54 [ 303.808010] CR2: 1afde000 [ 303.808010] ---[ end trace bd84bb1a9fa3ebd4 ]--- [ 304.463429] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0184 PQ: 0 ANSI: 6 [ 304.468098] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 304.472038] sd 2:0:0:0: [sdc] 585
[Kernel-packages] [Bug 1478623] Re: [4.1.0 regression] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test
Cheers Joseph - it's still broken with that kernel I'm afraid. -- 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/1478623 Title: [4.1.0 regression] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Bug description: We noticed that the udisks2 autopkgtest is failing on i386 in the "forced removal" test, for example https://jenkins.qa.ubuntu.com/job/wily-adt- udisks2/ARCH=i386,label=adt/55/console I reproduced this locally, on this kernel ubuntu@autopkgtest:~$ uname -a Linux autopkgtest 4.1.0-2-generic #2-Ubuntu SMP Wed Jul 22 18:17:34 UTC 2015 i686 i686 i686 GNU/Linux and got the following spewed to console fs: forced removal ... [ 303.782426] blk_update_request: I/O error, dev sdb, sector 0 [ 303.807400] BUG: unable to handle kernel paging request at 1afde000 [ 303.808010] IP: [] __percpu_counter_add+0x16/0x90 [ 303.808010] *pdpt = 0ee9b001 *pde = [ 303.808010] Oops: [#1] SMP [ 303.808010] Modules linked in: scsi_debug btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ppdev kvm_intel kvm joydev serio_raw 8250_fintek parport_pc parport i2c_piix4 mac_hid autofs4 psmouse pata_acpi floppy [ 303.808010] CPU: 0 PID: 22573 Comm: umount Not tainted 4.1.0-2-generic #2-Ubuntu [ 303.808010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.8.1-20150604_211837-tipua 04/01/2014 [ 303.808010] task: dc75e5e0 ti: ce85a000 task.ti: ce85a000 [ 303.808010] EIP: 0060:[] EFLAGS: 00010092 CPU: 0 [ 303.808010] EIP is at __percpu_counter_add+0x16/0x90 [ 303.808010] EAX: 0001 EBX: dbba9c08 ECX: EDX: 0001 [ 303.808010] ESI: EDI: EBP: ce85be6c ESP: ce85be54 [ 303.808010] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 303.808010] CR0: 8005003b CR2: 1afde000 CR3: 1e9c88c0 CR4: 07f0 [ 303.808010] Stack: [ 303.808010] c1aa7b40 0001 dbba9be8 decbfd60 ce85be88 c115bca4 [ 303.808010] 0008 ddce5228 ddce5228 decbfd60 decbfd70 ce85bea4 c11e47f9 [ 303.808010] 0286 ddce5228 d559cbd0 cdd41400 ce85beb4 c11e496f d3cc2000 [ 303.808010] Call Trace: [ 303.808010] [] account_page_dirtied+0x74/0xf0 [ 303.808010] [] __set_page_dirty+0x39/0xc0 [ 303.808010] [] mark_buffer_dirty+0x4f/0xb0 [ 303.808010] [] ext4_commit_super+0x168/0x220 [ 303.808010] [] ext4_put_super+0xc1/0x310 [ 303.808010] [] ? dispose_list+0x32/0x40 [ 303.808010] [] ? evict_inodes+0xda/0xf0 [ 303.808010] [] generic_shutdown_super+0x64/0xe0 [ 303.808010] [] ? unregister_shrinker+0x40/0x50 [ 303.808010] [] kill_block_super+0x1f/0x70 [ 303.808010] [] deactivate_locked_super+0x3d/0x70 [ 303.808010] [] deactivate_super+0x57/0x60 [ 303.808010] [] cleanup_mnt+0x39/0x90 [ 303.808010] [] __cleanup_mnt+0x10/0x20 [ 303.808010] [] task_work_run+0xb1/0xd0 [ 303.808010] [] do_notify_resume+0x53/0x70 [ 303.808010] [] work_notifysig+0x26/0x2b [ 303.808010] Code: 24 8b 54 24 04 83 c4 08 5b 5e 5f 5d c3 90 8d b4 26 00 00 00 00 55 89 e5 57 56 53 89 c3 89 d0 83 ec 0c 89 45 ec 89 4d f0 8b 7b 14 <64> 8b 37 89 7d e8 89 f7 c1 ff 1f 01 c6 11 cf 8b 4d 08 c1 f9 1f [ 303.808010] EIP: [] __percpu_counter_add+0x16/0x90 SS:ESP 0068:ce85be54 [ 303.808010] CR2: 1afde000 [ 303.808010] ---[ end trace bd84bb1a9fa3ebd4 ]--- [ 304.463429] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0184 PQ: 0 ANSI: 6 [ 304.468098] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 304.472038] sd 2:0:0:0: [sdc] 585728 512-byte logical blocks: (299 MB/286 MiB) [ 304.476079] sd 2:0:0:0: [sdc] Write Protect is off [ 304.476661] sd 2:0:0:0: [sdc] Mode Sense: 73 00 10 08 [ 304.484045] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 304.572090] sd 2:0:0:0: [sdc] Attached SCSI disk To reproduce, do something like this: $ adt-buildvm-ubuntu-cloud -r wily -a i386 # download a cloud image, fettle it a bit to be more useful $ qemu-system-i386 -m 2048 -net user -net nic,model=virtio -enable-kvm -nographic adt-wily* # login with ubuntu/ubuntu # apt-get update # apt-get dist-upgrade $ apt-get source udisks2 $ cd udisks2-* $ cat debian/tests/control # install the test-deps # debian/tests/upstream-system # runs the testsuite, when it gets to test_force_removal you should see this bug. the testsuite hangs too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kern
Re: [Kernel-packages] [Bug 1478623] Re: Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test
On Wed, Jul 29, 2015 at 05:37:12PM -, Joseph Salisbury wrote: > This issue appears to be an upstream bug, since you tested the latest > upstream kernel. Would it be possible for you to open an upstream bug > report[0]? That will allow the upstream Developers to examine the issue, > and may provide a quicker resolution to the bug. > > Please follow the instructions on the wiki page[0]. The first step is to > email the appropriate mailing list. If no response is received, then a > bug may be opened on bugzilla.kernel.org. Probably want a better reproducer than the udisks2 testsuite before doing that, no? -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.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/1478623 Title: Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test Status in linux package in Ubuntu: Triaged Bug description: We noticed that the udisks2 autopkgtest is failing on i386 in the "forced removal" test, for example https://jenkins.qa.ubuntu.com/job/wily-adt- udisks2/ARCH=i386,label=adt/55/console I reproduced this locally, on this kernel ubuntu@autopkgtest:~$ uname -a Linux autopkgtest 4.1.0-2-generic #2-Ubuntu SMP Wed Jul 22 18:17:34 UTC 2015 i686 i686 i686 GNU/Linux and got the following spewed to console fs: forced removal ... [ 303.782426] blk_update_request: I/O error, dev sdb, sector 0 [ 303.807400] BUG: unable to handle kernel paging request at 1afde000 [ 303.808010] IP: [] __percpu_counter_add+0x16/0x90 [ 303.808010] *pdpt = 0ee9b001 *pde = [ 303.808010] Oops: [#1] SMP [ 303.808010] Modules linked in: scsi_debug btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ppdev kvm_intel kvm joydev serio_raw 8250_fintek parport_pc parport i2c_piix4 mac_hid autofs4 psmouse pata_acpi floppy [ 303.808010] CPU: 0 PID: 22573 Comm: umount Not tainted 4.1.0-2-generic #2-Ubuntu [ 303.808010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.8.1-20150604_211837-tipua 04/01/2014 [ 303.808010] task: dc75e5e0 ti: ce85a000 task.ti: ce85a000 [ 303.808010] EIP: 0060:[] EFLAGS: 00010092 CPU: 0 [ 303.808010] EIP is at __percpu_counter_add+0x16/0x90 [ 303.808010] EAX: 0001 EBX: dbba9c08 ECX: EDX: 0001 [ 303.808010] ESI: EDI: EBP: ce85be6c ESP: ce85be54 [ 303.808010] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 303.808010] CR0: 8005003b CR2: 1afde000 CR3: 1e9c88c0 CR4: 07f0 [ 303.808010] Stack: [ 303.808010] c1aa7b40 0001 dbba9be8 decbfd60 ce85be88 c115bca4 [ 303.808010] 0008 ddce5228 ddce5228 decbfd60 decbfd70 ce85bea4 c11e47f9 [ 303.808010] 0286 ddce5228 d559cbd0 cdd41400 ce85beb4 c11e496f d3cc2000 [ 303.808010] Call Trace: [ 303.808010] [] account_page_dirtied+0x74/0xf0 [ 303.808010] [] __set_page_dirty+0x39/0xc0 [ 303.808010] [] mark_buffer_dirty+0x4f/0xb0 [ 303.808010] [] ext4_commit_super+0x168/0x220 [ 303.808010] [] ext4_put_super+0xc1/0x310 [ 303.808010] [] ? dispose_list+0x32/0x40 [ 303.808010] [] ? evict_inodes+0xda/0xf0 [ 303.808010] [] generic_shutdown_super+0x64/0xe0 [ 303.808010] [] ? unregister_shrinker+0x40/0x50 [ 303.808010] [] kill_block_super+0x1f/0x70 [ 303.808010] [] deactivate_locked_super+0x3d/0x70 [ 303.808010] [] deactivate_super+0x57/0x60 [ 303.808010] [] cleanup_mnt+0x39/0x90 [ 303.808010] [] __cleanup_mnt+0x10/0x20 [ 303.808010] [] task_work_run+0xb1/0xd0 [ 303.808010] [] do_notify_resume+0x53/0x70 [ 303.808010] [] work_notifysig+0x26/0x2b [ 303.808010] Code: 24 8b 54 24 04 83 c4 08 5b 5e 5f 5d c3 90 8d b4 26 00 00 00 00 55 89 e5 57 56 53 89 c3 89 d0 83 ec 0c 89 45 ec 89 4d f0 8b 7b 14 <64> 8b 37 89 7d e8 89 f7 c1 ff 1f 01 c6 11 cf 8b 4d 08 c1 f9 1f [ 303.808010] EIP: [] __percpu_counter_add+0x16/0x90 SS:ESP 0068:ce85be54 [ 303.808010] CR2: 1afde000 [ 303.808010] ---[ end trace bd84bb1a9fa3ebd4 ]--- [ 304.463429] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0184 PQ: 0 ANSI: 6 [ 304.468098] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 304.472038] sd 2:0:0:0: [sdc] 585728 512-byte logical blocks: (299 MB/286 MiB) [ 304.476079] sd 2:0:0:0: [sdc] Write Protect is off [ 304.476661] sd 2:0:0:0: [sdc] Mode Sense: 73 00 10 08 [ 304.484045] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 304.572090] sd 2:0:0:0: [sdc] Attached SCSI disk To reproduce, do something like this: $ adt-buildvm-ubuntu-cloud -r wily -a i386 #
[Kernel-packages] [Bug 1478623] Re: Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test
Tried that, still fails fs: forced removal ... [ 103.792793] blk_update_request: I/O error, dev sdb, sector 0 [ 103.804099] BUG: unable to handle kernel paging request at 1af23000 [ 103.805253] IP: [] __percpu_counter_add+0x14/0xa0 [ 103.806244] *pdpt = 15588001 *pde = [ 103.807201] Oops: [#1] SMP [ 103.807776] Modules linked in: scsi_debug ppdev input_leds joydev serio_raw parport_pc 8250_fintek parport i2c_piix4 mac_hid autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear psmouse floppy pata_acpi [ 103.808017] CPU: 0 PID: 1546 Comm: umount Not tainted 4.2.0-040200rc4-generic #201507271733 [ 103.808017] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.8.1-20150604_211837-tipua 04/01/2014 [ 103.808017] task: de8a9180 ti: d5d5c000 task.ti: d5d5c000 [ 103.808017] EIP: 0060:[] EFLAGS: 00010096 CPU: 0 [ 103.808017] EIP is at __percpu_counter_add+0x14/0xa0 [ 103.808017] EAX: EBX: c007b394 ECX: EDX: 0001 [ 103.808017] ESI: EDI: ddd3d0c0 EBP: d5d5de60 ESP: d5d5de48 [ 103.808017] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 103.808017] CR0: 8005003b CR2: 1af23000 CR3: 1effb6c0 CR4: 06b0 [ 103.808017] Stack: [ 103.808017] c1a972c0 0001 c007b364 ddd3d0c0 d5d5de84 c11552be [ 103.808017] 0008 dc731800 dbd26c8c ddd3d0c0 ddd3d0c0 dbd26d70 dbd26d80 d5d5dea0 [ 103.808017] c11d994c dc731800 0292 ddd3d0c0 dc731800 dbd26d70 d5d5deb8 c11d9b09 [ 103.808017] Call Trace: [ 103.808017] [] account_page_dirtied+0xae/0x180 [ 103.808017] [] __set_page_dirty+0x3c/0xb0 [ 103.808017] [] mark_buffer_dirty+0x69/0xf0 [ 103.808017] [] ext4_commit_super+0x169/0x220 [ 103.808017] [] ? mb_cache_shrink+0x28/0x190 [ 103.808017] [] ext4_put_super+0xc1/0x320 [ 103.808017] [] ? dispose_list+0x32/0x40 [ 103.808017] [] ? evict_inodes+0x9b/0xf0 [ 103.808017] [] generic_shutdown_super+0x64/0xe0 [ 103.808017] [] ? unregister_shrinker+0x40/0x50 [ 103.808017] [] kill_block_super+0x1f/0x70 [ 103.808017] [] deactivate_locked_super+0x3d/0x70 [ 103.808017] [] deactivate_super+0x3a/0x60 [ 103.808017] [] cleanup_mnt+0x39/0x80 [ 103.808017] [] __cleanup_mnt+0x10/0x20 [ 103.808017] [] task_work_run+0x91/0xb0 [ 103.808017] [] do_notify_resume+0x53/0x80 [ 103.808017] [] work_notifysig+0x26/0x2b [ 103.808017] Code: b3 3e 3a 00 8b 44 24 04 8b 54 24 08 83 c4 0c 5b 5e 5f 5d c3 8d 76 00 55 89 e5 57 56 53 89 c3 83 ec 0c 89 55 ec 89 4d f0 8b 40 14 <64> 8b 30 89 f7 c1 ff 1f 01 d6 8b 55 08 11 cf 89 d1 c1 f9 1f 39 [ 103.808017] EIP: [] __percpu_counter_add+0x14/0xa0 SS:ESP 0068:d5d5de48 [ 103.808017] CR2: 1af23000 [ 103.808017] ---[ end trace 4f2efe63047f95c9 ]--- [ 104.455856] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0184 PQ: 0 ANSI: 6 [ 104.462147] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 104.468103] sd 2:0:0:0: [sdc] 585728 512-byte logical blocks: (299 MB/286 MiB) [ 104.472387] sd 2:0:0:0: [sdc] Write Protect is off [ 104.473314] sd 2:0:0:0: [sdc] Mode Sense: 73 00 10 08 [ 104.480096] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 104.568088] sd 2:0:0:0: [sdc] Attached SCSI disk root@autopkgtest:/home/ubuntu/udisks2-2.1.6# uname -a Linux autopkgtest 4.2.0-040200rc4-generic #201507271733 SMP Mon Jul 27 21:47:26 UTC 2015 i686 i686 i686 GNU/Linux ** Tags added: bug-exists-upstream ** Tags removed: bot-stop-nagging ** Tags added: kernel-bot-stop-nagging ** Tags removed: bug-exists-upstream kernel-bot-stop-nagging ** Tags added: bot-stop-nagging kernel-bug-exists-upstream -- 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/1478623 Title: Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test Status in linux package in Ubuntu: Confirmed Bug description: We noticed that the udisks2 autopkgtest is failing on i386 in the "forced removal" test, for example https://jenkins.qa.ubuntu.com/job/wily-adt- udisks2/ARCH=i386,label=adt/55/console I reproduced this locally, on this kernel ubuntu@autopkgtest:~$ uname -a Linux autopkgtest 4.1.0-2-generic #2-Ubuntu SMP Wed Jul 22 18:17:34 UTC 2015 i686 i686 i686 GNU/Linux and got the following spewed to console fs: forced removal ... [ 303.782426] blk_update_request: I/O error, dev sdb, sector 0 [ 303.807400] BUG: unable to handle kernel paging request at 1afde000 [ 303.808010] IP: [] __percpu_counter_add+0x16/0x90 [ 303.808010] *pdpt = 0ee9b001 *pde = [ 303.808010] Oops: [#1] SMP [ 303.808010] Modules linked in: scsi_debug btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ppdev kvm_intel kvm joydev serio_raw 8250_fintek parport_pc parport i2c_piix4 mac_hid auto
[Kernel-packages] [Bug 1478623] Re: Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test
** Tags added: bot-stop-nagging -- 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/1478623 Title: Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test Status in linux package in Ubuntu: Confirmed Bug description: We noticed that the udisks2 autopkgtest is failing on i386 in the "forced removal" test, for example https://jenkins.qa.ubuntu.com/job/wily-adt- udisks2/ARCH=i386,label=adt/55/console I reproduced this locally, on this kernel ubuntu@autopkgtest:~$ uname -a Linux autopkgtest 4.1.0-2-generic #2-Ubuntu SMP Wed Jul 22 18:17:34 UTC 2015 i686 i686 i686 GNU/Linux and got the following spewed to console fs: forced removal ... [ 303.782426] blk_update_request: I/O error, dev sdb, sector 0 [ 303.807400] BUG: unable to handle kernel paging request at 1afde000 [ 303.808010] IP: [] __percpu_counter_add+0x16/0x90 [ 303.808010] *pdpt = 0ee9b001 *pde = [ 303.808010] Oops: [#1] SMP [ 303.808010] Modules linked in: scsi_debug btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ppdev kvm_intel kvm joydev serio_raw 8250_fintek parport_pc parport i2c_piix4 mac_hid autofs4 psmouse pata_acpi floppy [ 303.808010] CPU: 0 PID: 22573 Comm: umount Not tainted 4.1.0-2-generic #2-Ubuntu [ 303.808010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.8.1-20150604_211837-tipua 04/01/2014 [ 303.808010] task: dc75e5e0 ti: ce85a000 task.ti: ce85a000 [ 303.808010] EIP: 0060:[] EFLAGS: 00010092 CPU: 0 [ 303.808010] EIP is at __percpu_counter_add+0x16/0x90 [ 303.808010] EAX: 0001 EBX: dbba9c08 ECX: EDX: 0001 [ 303.808010] ESI: EDI: EBP: ce85be6c ESP: ce85be54 [ 303.808010] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 303.808010] CR0: 8005003b CR2: 1afde000 CR3: 1e9c88c0 CR4: 07f0 [ 303.808010] Stack: [ 303.808010] c1aa7b40 0001 dbba9be8 decbfd60 ce85be88 c115bca4 [ 303.808010] 0008 ddce5228 ddce5228 decbfd60 decbfd70 ce85bea4 c11e47f9 [ 303.808010] 0286 ddce5228 d559cbd0 cdd41400 ce85beb4 c11e496f d3cc2000 [ 303.808010] Call Trace: [ 303.808010] [] account_page_dirtied+0x74/0xf0 [ 303.808010] [] __set_page_dirty+0x39/0xc0 [ 303.808010] [] mark_buffer_dirty+0x4f/0xb0 [ 303.808010] [] ext4_commit_super+0x168/0x220 [ 303.808010] [] ext4_put_super+0xc1/0x310 [ 303.808010] [] ? dispose_list+0x32/0x40 [ 303.808010] [] ? evict_inodes+0xda/0xf0 [ 303.808010] [] generic_shutdown_super+0x64/0xe0 [ 303.808010] [] ? unregister_shrinker+0x40/0x50 [ 303.808010] [] kill_block_super+0x1f/0x70 [ 303.808010] [] deactivate_locked_super+0x3d/0x70 [ 303.808010] [] deactivate_super+0x57/0x60 [ 303.808010] [] cleanup_mnt+0x39/0x90 [ 303.808010] [] __cleanup_mnt+0x10/0x20 [ 303.808010] [] task_work_run+0xb1/0xd0 [ 303.808010] [] do_notify_resume+0x53/0x70 [ 303.808010] [] work_notifysig+0x26/0x2b [ 303.808010] Code: 24 8b 54 24 04 83 c4 08 5b 5e 5f 5d c3 90 8d b4 26 00 00 00 00 55 89 e5 57 56 53 89 c3 89 d0 83 ec 0c 89 45 ec 89 4d f0 8b 7b 14 <64> 8b 37 89 7d e8 89 f7 c1 ff 1f 01 c6 11 cf 8b 4d 08 c1 f9 1f [ 303.808010] EIP: [] __percpu_counter_add+0x16/0x90 SS:ESP 0068:ce85be54 [ 303.808010] CR2: 1afde000 [ 303.808010] ---[ end trace bd84bb1a9fa3ebd4 ]--- [ 304.463429] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0184 PQ: 0 ANSI: 6 [ 304.468098] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 304.472038] sd 2:0:0:0: [sdc] 585728 512-byte logical blocks: (299 MB/286 MiB) [ 304.476079] sd 2:0:0:0: [sdc] Write Protect is off [ 304.476661] sd 2:0:0:0: [sdc] Mode Sense: 73 00 10 08 [ 304.484045] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 304.572090] sd 2:0:0:0: [sdc] Attached SCSI disk To reproduce, do something like this: $ adt-buildvm-ubuntu-cloud -r wily -a i386 # download a cloud image, fettle it a bit to be more useful $ qemu-system-i386 -m 2048 -net user -net nic,model=virtio -enable-kvm -nographic adt-wily* # login with ubuntu/ubuntu # apt-get update # apt-get dist-upgrade $ apt-get source udisks2 $ cd udisks2-* $ cat debian/tests/control # install the test-deps # debian/tests/upstream-system # runs the testsuite, when it gets to test_force_removal you should see this bug. the testsuite hangs too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1478623] [NEW] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test
Public bug reported: We noticed that the udisks2 autopkgtest is failing on i386 in the "forced removal" test, for example https://jenkins.qa.ubuntu.com/job/wily-adt- udisks2/ARCH=i386,label=adt/55/console I reproduced this locally, on this kernel ubuntu@autopkgtest:~$ uname -a Linux autopkgtest 4.1.0-2-generic #2-Ubuntu SMP Wed Jul 22 18:17:34 UTC 2015 i686 i686 i686 GNU/Linux and got the following spewed to console fs: forced removal ... [ 303.782426] blk_update_request: I/O error, dev sdb, sector 0 [ 303.807400] BUG: unable to handle kernel paging request at 1afde000 [ 303.808010] IP: [] __percpu_counter_add+0x16/0x90 [ 303.808010] *pdpt = 0ee9b001 *pde = [ 303.808010] Oops: [#1] SMP [ 303.808010] Modules linked in: scsi_debug btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ppdev kvm_intel kvm joydev serio_raw 8250_fintek parport_pc parport i2c_piix4 mac_hid autofs4 psmouse pata_acpi floppy [ 303.808010] CPU: 0 PID: 22573 Comm: umount Not tainted 4.1.0-2-generic #2-Ubuntu [ 303.808010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.8.1-20150604_211837-tipua 04/01/2014 [ 303.808010] task: dc75e5e0 ti: ce85a000 task.ti: ce85a000 [ 303.808010] EIP: 0060:[] EFLAGS: 00010092 CPU: 0 [ 303.808010] EIP is at __percpu_counter_add+0x16/0x90 [ 303.808010] EAX: 0001 EBX: dbba9c08 ECX: EDX: 0001 [ 303.808010] ESI: EDI: EBP: ce85be6c ESP: ce85be54 [ 303.808010] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 303.808010] CR0: 8005003b CR2: 1afde000 CR3: 1e9c88c0 CR4: 07f0 [ 303.808010] Stack: [ 303.808010] c1aa7b40 0001 dbba9be8 decbfd60 ce85be88 c115bca4 [ 303.808010] 0008 ddce5228 ddce5228 decbfd60 decbfd70 ce85bea4 c11e47f9 [ 303.808010] 0286 ddce5228 d559cbd0 cdd41400 ce85beb4 c11e496f d3cc2000 [ 303.808010] Call Trace: [ 303.808010] [] account_page_dirtied+0x74/0xf0 [ 303.808010] [] __set_page_dirty+0x39/0xc0 [ 303.808010] [] mark_buffer_dirty+0x4f/0xb0 [ 303.808010] [] ext4_commit_super+0x168/0x220 [ 303.808010] [] ext4_put_super+0xc1/0x310 [ 303.808010] [] ? dispose_list+0x32/0x40 [ 303.808010] [] ? evict_inodes+0xda/0xf0 [ 303.808010] [] generic_shutdown_super+0x64/0xe0 [ 303.808010] [] ? unregister_shrinker+0x40/0x50 [ 303.808010] [] kill_block_super+0x1f/0x70 [ 303.808010] [] deactivate_locked_super+0x3d/0x70 [ 303.808010] [] deactivate_super+0x57/0x60 [ 303.808010] [] cleanup_mnt+0x39/0x90 [ 303.808010] [] __cleanup_mnt+0x10/0x20 [ 303.808010] [] task_work_run+0xb1/0xd0 [ 303.808010] [] do_notify_resume+0x53/0x70 [ 303.808010] [] work_notifysig+0x26/0x2b [ 303.808010] Code: 24 8b 54 24 04 83 c4 08 5b 5e 5f 5d c3 90 8d b4 26 00 00 00 00 55 89 e5 57 56 53 89 c3 89 d0 83 ec 0c 89 45 ec 89 4d f0 8b 7b 14 <64> 8b 37 89 7d e8 89 f7 c1 ff 1f 01 c6 11 cf 8b 4d 08 c1 f9 1f [ 303.808010] EIP: [] __percpu_counter_add+0x16/0x90 SS:ESP 0068:ce85be54 [ 303.808010] CR2: 1afde000 [ 303.808010] ---[ end trace bd84bb1a9fa3ebd4 ]--- [ 304.463429] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0184 PQ: 0 ANSI: 6 [ 304.468098] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 304.472038] sd 2:0:0:0: [sdc] 585728 512-byte logical blocks: (299 MB/286 MiB) [ 304.476079] sd 2:0:0:0: [sdc] Write Protect is off [ 304.476661] sd 2:0:0:0: [sdc] Mode Sense: 73 00 10 08 [ 304.484045] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 304.572090] sd 2:0:0:0: [sdc] Attached SCSI disk To reproduce, do something like this: $ adt-buildvm-ubuntu-cloud -r wily -a i386 # download a cloud image, fettle it a bit to be more useful $ qemu-system-i386 -m 2048 -net user -net nic,model=virtio -enable-kvm -nographic adt-wily* # login with ubuntu/ubuntu # apt-get update # apt-get dist-upgrade $ apt-get source udisks2 $ cd udisks2-* $ cat debian/tests/control # install the test-deps # debian/tests/upstream-system # runs the testsuite, when it gets to test_force_removal you should see this bug. the testsuite hangs too. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1478623 Title: Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test Status in linux package in Ubuntu: Incomplete Bug description: We noticed that the udisks2 autopkgtest is failing on i386 in the "forced removal" test, for example https://jenkins.qa.ubuntu.com/job/wily-adt- udisks2/ARCH=i386,label=adt/55/console I reproduced this locally, on this kernel ubuntu@autopkgtest:~$ uname -a Linux autopkgtest 4.1.0-2-generic #2-Ubuntu SMP Wed Jul 22 18:17:34 UTC 2015 i686 i686 i686 GNU/Linux and got the following spewed to console fs: forced
[Kernel-packages] [Bug 1447143] Re: [SKL, i915_bpo] Rotation doesn't work
** No longer affects: xserver-xorg-video-intel (Ubuntu Utopic) -- 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/1447143 Title: [SKL, i915_bpo] Rotation doesn't work Status in linux package in Ubuntu: Triaged Status in xserver-xorg-video-intel package in Ubuntu: In Progress Status in linux source package in Utopic: New Status in linux source package in Vivid: Triaged Status in xserver-xorg-video-intel source package in Vivid: In Progress Bug description: [Impact] Rotating the display on Skylake results in a blank screen, needs this for the X driver commit 15c307d70e00bc035bb61be5d8b6f727925e3d34 Author: Chris Wilson Date: Tue Mar 10 08:48:48 2015 + sna: Force frontbuffer to CPU for randr fallback and these two for i915_bpo in kernel commit 3b7a5119b5d2def1161226a4c6a643db537dff7e Author: Sonika Jindal Date: Fri Apr 10 14:37:29 2015 +0530 drm/i915/skl: Support for 90/270 rotation commit d81063669a99b216eb6b9dfb17add4f38a839674 Author: Sonika Jindal Date: Fri Apr 10 14:37:28 2015 +0530 drm/i915/skl: Allow universal planes to position [Test Case] Use the display capplet, select rotate and apply. It should rotate instead of blanking the display. [Regression potential] Nope. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447143] Re: [SKL, i915_bpo] Rotation doesn't work
** Also affects: xserver-xorg-video-intel (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1447143 Title: [SKL, i915_bpo] Rotation doesn't work Status in linux package in Ubuntu: Triaged Status in xserver-xorg-video-intel package in Ubuntu: In Progress Status in linux source package in Utopic: New Status in linux source package in Vivid: Triaged Status in xserver-xorg-video-intel source package in Vivid: In Progress Bug description: [Impact] Rotating the display on Skylake results in a blank screen, needs this for the X driver commit 15c307d70e00bc035bb61be5d8b6f727925e3d34 Author: Chris Wilson Date: Tue Mar 10 08:48:48 2015 + sna: Force frontbuffer to CPU for randr fallback and these two for i915_bpo in kernel commit 3b7a5119b5d2def1161226a4c6a643db537dff7e Author: Sonika Jindal Date: Fri Apr 10 14:37:29 2015 +0530 drm/i915/skl: Support for 90/270 rotation commit d81063669a99b216eb6b9dfb17add4f38a839674 Author: Sonika Jindal Date: Fri Apr 10 14:37:28 2015 +0530 drm/i915/skl: Allow universal planes to position [Test Case] Use the display capplet, select rotate and apply. It should rotate instead of blanking the display. [Regression potential] Nope. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380143] Re: [Apple Inc. MacBookPro7, 1] suspend/resume failure [non-free: nvidia wl]
** Tags added: kernel-unable-to-test-upstream ** 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/1380143 Title: [Apple Inc. MacBookPro7,1] suspend/resume failure [non-free: nvidia wl] Status in “linux” package in Ubuntu: Confirmed Bug description: I tried to suspend and the suspend process failed. There was a blinking cursor but I couldn't get the system to do anything. Hopefully the attached logs are good. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 NonfreeKernelModules: nvidia wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laney 2981 F pulseaudio Date: Sat Oct 11 18:29:34 2014 DuplicateSignature: suspend/resume:Apple Inc. MacBookPro7,1:MBP71.88Z.0039.B05.1003251322 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=2e47774e-17bc-4401-b353-8adf33732c5e InstallationDate: Installed on 2012-10-18 (723 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookPro7,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=e57ded1c-a0ed-4f14-944c-1353387547ed ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.135 SourcePackage: linux Title: [Apple Inc. MacBookPro7,1] suspend/resume failure [non-free: nvidia wl] UpgradeStatus: Upgraded to utopic on 2014-07-30 (73 days ago) UserGroups: dmi.bios.date: 03/25/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B05.1003251322 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B05.1003251322:bd03/25/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380788] Re: BUG: Bad page map in process HTMLParserThrea pte:6c004700690070 pmd:0008f067
** 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/1380788 Title: BUG: Bad page map in process HTMLParserThrea pte:6c004700690070 pmd:0008f067 Status in “linux” package in Ubuntu: Confirmed Bug description: This seems to be something chromium-ish which died (my tabs were all "He's dead, Jim", but I don't know where the bug lies. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 NonfreeKernelModules: nvidia wl Annotation: Your system might become unstablenow and might need to be restarted. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laney 2981 F pulseaudio Date: Mon Oct 13 21:35:08 2014 Failure: oops HibernationDevice: RESUME=UUID=2e47774e-17bc-4401-b353-8adf33732c5e InstallationDate: Installed on 2012-10-18 (725 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: Apple Inc. MacBookPro7,1 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=e57ded1c-a0ed-4f14-944c-1353387547ed ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 SourcePackage: linux Title: BUG: Bad page map in process HTMLParserThrea pte:6c004700690070 pmd:0008f067 UpgradeStatus: Upgraded to utopic on 2014-07-30 (75 days ago) dmi.bios.date: 03/25/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B05.1003251322 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B05.1003251322:bd03/25/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380788] [NEW] BUG: Bad page map in process HTMLParserThrea pte:6c004700690070 pmd:0008f067
Public bug reported: This seems to be something chromium-ish which died (my tabs were all "He's dead, Jim", but I don't know where the bug lies. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 NonfreeKernelModules: nvidia wl Annotation: Your system might become unstablenow and might need to be restarted. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laney 2981 F pulseaudio Date: Mon Oct 13 21:35:08 2014 Failure: oops HibernationDevice: RESUME=UUID=2e47774e-17bc-4401-b353-8adf33732c5e InstallationDate: Installed on 2012-10-18 (725 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: Apple Inc. MacBookPro7,1 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=e57ded1c-a0ed-4f14-944c-1353387547ed ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 SourcePackage: linux Title: BUG: Bad page map in process HTMLParserThrea pte:6c004700690070 pmd:0008f067 UpgradeStatus: Upgraded to utopic on 2014-07-30 (75 days ago) dmi.bios.date: 03/25/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B05.1003251322 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B05.1003251322:bd03/25/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops utopic -- 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/1380788 Title: BUG: Bad page map in process HTMLParserThrea pte:6c004700690070 pmd:0008f067 Status in “linux” package in Ubuntu: New Bug description: This seems to be something chromium-ish which died (my tabs were all "He's dead, Jim", but I don't know where the bug lies. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 NonfreeKernelModules: nvidia wl Annotation: Your system might become unstablenow and might need to be restarted. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laney 2981 F pulseaudio Date: Mon Oct 13 21:35:08 2014 Failure: oops HibernationDevice: RESUME=UUID=2e47774e-17bc-4401-b353-8adf33732c5e InstallationDate: Installed on 2012-10-18 (725 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: Apple Inc. MacBookPro7,1 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=e57ded1c-a0ed-4f14-944c-1353387547ed ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 SourcePackage: linux Title: BUG: Bad page map in process HTMLParserThrea pte:6c004700690070 pmd:0008f067 UpgradeStatus: Upgraded to utopic on 2014-07-30 (75 days ago) dmi.bios.date: 03/25/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B05.1003251322 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B05.1003251322:bd03/25/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1380143] Re: [Apple Inc. MacBookPro7, 1] suspend/resume failure [non-free: nvidia wl]
I don't know how to reproduce the bug, so I'm not sure if this will help? On Mon, Oct 13, 2014 at 09:52:01AM -, Joseph Salisbury wrote: > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v3.17 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > If you are unable to test the mainline kernel, for example it will not boot, > please add the tag: 'kernel-unable-to-test-upstream'. > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-utopic/ > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1380143 > > Title: > [Apple Inc. MacBookPro7,1] suspend/resume failure [non-free: nvidia > wl] > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380143/+subscriptions > -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.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/1380143 Title: [Apple Inc. MacBookPro7,1] suspend/resume failure [non-free: nvidia wl] Status in “linux” package in Ubuntu: Incomplete Bug description: I tried to suspend and the suspend process failed. There was a blinking cursor but I couldn't get the system to do anything. Hopefully the attached logs are good. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 NonfreeKernelModules: nvidia wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laney 2981 F pulseaudio Date: Sat Oct 11 18:29:34 2014 DuplicateSignature: suspend/resume:Apple Inc. MacBookPro7,1:MBP71.88Z.0039.B05.1003251322 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=2e47774e-17bc-4401-b353-8adf33732c5e InstallationDate: Installed on 2012-10-18 (723 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookPro7,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=e57ded1c-a0ed-4f14-944c-1353387547ed ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.135 SourcePackage: linux Title: [Apple Inc. MacBookPro7,1] suspend/resume failure [non-free: nvidia wl] UpgradeStatus: Upgraded to utopic on 2014-07-30 (73 days ago) UserGroups: dmi.bios.date: 03/25/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B05.1003251322 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B05.1003251322:bd03/25/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380143] [NEW] [Apple Inc. MacBookPro7, 1] suspend/resume failure [non-free: nvidia wl]
Public bug reported: I tried to suspend and the suspend process failed. There was a blinking cursor but I couldn't get the system to do anything. Hopefully the attached logs are good. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 NonfreeKernelModules: nvidia wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laney 2981 F pulseaudio Date: Sat Oct 11 18:29:34 2014 DuplicateSignature: suspend/resume:Apple Inc. MacBookPro7,1:MBP71.88Z.0039.B05.1003251322 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=2e47774e-17bc-4401-b353-8adf33732c5e InstallationDate: Installed on 2012-10-18 (723 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookPro7,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=e57ded1c-a0ed-4f14-944c-1353387547ed ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.135 SourcePackage: linux Title: [Apple Inc. MacBookPro7,1] suspend/resume failure [non-free: nvidia wl] UpgradeStatus: Upgraded to utopic on 2014-07-30 (73 days ago) UserGroups: dmi.bios.date: 03/25/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B05.1003251322 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B05.1003251322:bd03/25/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend utopic -- 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/1380143 Title: [Apple Inc. MacBookPro7,1] suspend/resume failure [non-free: nvidia wl] Status in “linux” package in Ubuntu: New Bug description: I tried to suspend and the suspend process failed. There was a blinking cursor but I couldn't get the system to do anything. Hopefully the attached logs are good. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 NonfreeKernelModules: nvidia wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laney 2981 F pulseaudio Date: Sat Oct 11 18:29:34 2014 DuplicateSignature: suspend/resume:Apple Inc. MacBookPro7,1:MBP71.88Z.0039.B05.1003251322 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=2e47774e-17bc-4401-b353-8adf33732c5e InstallationDate: Installed on 2012-10-18 (723 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookPro7,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=e57ded1c-a0ed-4f14-944c-1353387547ed ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.135 SourcePackage: linux Title: [Apple Inc. MacBookPro7,1] suspend/resume failure [non-free: nvidia wl] UpgradeStatus: Upgraded to utopic on 2014-07-30 (73 days ago) UserGroups: dmi.bios.date: 03/25/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B05.1003251322 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc.
[Kernel-packages] [Bug 1217474] Re: basic autopkgtest for crash
Thanks, uploading ** Changed in: crash (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1217474 Title: basic autopkgtest for crash Status in “crash” package in Ubuntu: Fix Committed Status in “crash” package in Debian: New Bug description: We should have an autopkgtest for crash to ensure it works! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1217474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
