[Kernel-packages] [Bug 1864045] Re: [SRU] Hibernation events sometimes missed on repeated attempts
** Changed in: acpid (Ubuntu Bionic) Assignee: Balint Reczey (rbalint) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864045 Title: [SRU] Hibernation events sometimes missed on repeated attempts Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in acpid source package in Bionic: Incomplete Status in linux source package in Bionic: Incomplete Status in acpid source package in Eoan: Won't Fix Status in linux source package in Eoan: Won't Fix Bug description: When testing hibernation / resume on AWS with 5.0 or 5.3 kernels on bionic (using acpid 1:2.0.28-1ubuntu1), we sometimes see failure with repeated attempts. The first attempt will always be triggered, but the next attempt may not. The result is the agent never triggers the hibernation process and the instance will be forced to shutdown after a timeout period. Two workarounds have been identified. The first is to restart acpid during the resume handler. The second is to use the latest upstream acpid (as of Feb 1, 2020). This second workaround indicates there may be a patch missing in the acpid in bionic (1:2.0.28-1ubuntu1) to work with the 5.0+ kernels. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel on a bionic image with on-demand hibernation support enabled. 2) Hibernate and resume the instance, ensuring the system is fully resumed afterward and the swap file has been removed. 3) Hibernate and resume another time. The hibernate should be triggered immediately and the instance should become unresponsive as it saves state to disk. 4) Resume the instance, it should come back with the same processes running. 5) Repeat 3) - 4) as necessary. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: acpid 1:2.0.28-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1864045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
@ddstreed Could you please look into this SRU candidate? @gjolly What is the importance/urgency of landing this fix? ** Also affects: cloud-init (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux-azure (Ubuntu Hirsute) Status: New => Invalid ** Changed in: cloud-init (Ubuntu Hirsute) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1919177 Title: Azure: issues with accelerated networking on Hirsute Status in cloud-init: Incomplete Status in cloud-init package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Hirsute: Incomplete Status in linux-azure source package in Hirsute: Invalid Status in systemd source package in Hirsute: New Bug description: [General] On Azure, when provisioning a Hirsute VM with Accelerated Networking enabled, sometimes part of the cloud-init configuration is not applied. Especially, in those cases, the public SSH key is not setup properly. [how to reproduce] Start a VM with AN enabled: ``` az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South" --image 'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" --accelerated-networking ``` After a moment, try to SSH: if you succeed, delete and recreate a new VM. [troubleshooting] To be able to connect into the VM, run: az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME" ``` In "/run/cloud-init/instance-data.json", I can see: ``` "publicKeys": [ { "keyData": "", "path": "/home/ubuntu/.ssh/authorized_keys" } ], ``` as expected. [workaround] As mentioned, Azure allows the user to run command into the VM without SSH connection. To do so, one can use the Azure CLI: az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME" This example uses "ssh-import-id" but it's also possible to just echo a given public key into /home/ubuntu/.ssh/authorized_keys NOTE: this will only solves the SSH issue, I do not know if this bug affects other things. If so the user would have to apply those things manually. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1919177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
@gjolly There were networking-related changes in systemd which could have caused this but I also see that the kernel packages also changed between the Azure images: -ii linux-image-azure 5.8.0.1017.19+21.04.14 ... +ii linux-image-5.8.0-1022-azure 5.8.0-1022.24+21.04.2 Could you please prepare an image that has the older kernel and newer systemd to rule out kernel changes causing the issue? Also do you still observe the issue in Impish? It has systemd 248 now. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1919177 Title: Azure: issues with accelerated networking on Hirsute Status in cloud-init: Incomplete Status in cloud-init package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: [General] On Azure, when provisioning a Hirsute VM with Accelerated Networking enabled, sometimes part of the cloud-init configuration is not applied. Especially, in those cases, the public SSH key is not setup properly. [how to reproduce] Start a VM with AN enabled: ``` az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South" --image 'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" --accelerated-networking ``` After a moment, try to SSH: if you succeed, delete and recreate a new VM. [troubleshooting] To be able to connect into the VM, run: az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME" ``` In "/run/cloud-init/instance-data.json", I can see: ``` "publicKeys": [ { "keyData": "", "path": "/home/ubuntu/.ssh/authorized_keys" } ], ``` as expected. [workaround] As mentioned, Azure allows the user to run command into the VM without SSH connection. To do so, one can use the Azure CLI: az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME" This example uses "ssh-import-id" but it's also possible to just echo a given public key into /home/ubuntu/.ssh/authorized_keys NOTE: this will only solves the SSH issue, I do not know if this bug affects other things. If so the user would have to apply those things manually. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1919177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916070] Re: autopkgtest fails in hirsute on armhf with glibc 2.33
** Merge proposal unlinked: https://code.launchpad.net/~rbalint/britney/+git/hints-ubuntu/+merge/398293 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916070 Title: autopkgtest fails in hirsute on armhf with glibc 2.33 Status in linux package in Ubuntu: Confirmed Status in notepadqq package in Ubuntu: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/armhf/n/notepadqq/20210217_182537_f860b@/log.gz ... autopkgtest [18:25:08]: test gui: [--- ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 autopkgtest [18:25:16]: test gui: ---] autopkgtest [18:25:18]: test gui: - - - - - - - - - - results - - - - - - - - - - gui FAIL non-zero exit status 1 ... The syscall in question is futex_time64: https://github.com/seccomp/libseccomp/blob/v2.5.0/src/syscalls.csv#L99 The armhf autopgktests run in LXD running on Bionic with Linux 4.15 kernel: autopkgtest [18:22:22]: testbed running kernel: Linux 4.15.0-135-generic #139-Ubuntu SMP Mon Jan 18 17:40:29 UTC 2021 The test passes when running it on Focal as the LXD host, with Linux 5.4: Linux ip-172-31-21-155 5.4.0-1037-aws #39-Ubuntu SMP Thu Jan 14 02:53:31 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux In the 4.15 kernel the syscall is not implemented as observed using strace: gui.trace.5364:futex_time64(0xe55fd210, FUTEX_WAIT_BITSET_PRIVATE, 0, {tv_sec=7495146, tv_nsec=17321283297740747954}, FUTEX_BITSET_MATCH_ANY) = -1 ENOSYS (Function not implemented) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916070] Re: autopkgtest fails in hirsute on armhf with glibc 2.33
This case does not need more logs IMO. ** 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/1916070 Title: autopkgtest fails in hirsute on armhf with glibc 2.33 Status in linux package in Ubuntu: Confirmed Status in notepadqq package in Ubuntu: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/armhf/n/notepadqq/20210217_182537_f860b@/log.gz ... autopkgtest [18:25:08]: test gui: [--- ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 autopkgtest [18:25:16]: test gui: ---] autopkgtest [18:25:18]: test gui: - - - - - - - - - - results - - - - - - - - - - gui FAIL non-zero exit status 1 ... The syscall in question is futex_time64: https://github.com/seccomp/libseccomp/blob/v2.5.0/src/syscalls.csv#L99 The armhf autopgktests run in LXD running on Bionic with Linux 4.15 kernel: autopkgtest [18:22:22]: testbed running kernel: Linux 4.15.0-135-generic #139-Ubuntu SMP Mon Jan 18 17:40:29 UTC 2021 The test passes when running it on Focal as the LXD host, with Linux 5.4: Linux ip-172-31-21-155 5.4.0-1037-aws #39-Ubuntu SMP Thu Jan 14 02:53:31 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux In the 4.15 kernel the syscall is not implemented as observed using strace: gui.trace.5364:futex_time64(0xe55fd210, FUTEX_WAIT_BITSET_PRIVATE, 0, {tv_sec=7495146, tv_nsec=17321283297740747954}, FUTEX_BITSET_MATCH_ANY) = -1 ENOSYS (Function not implemented) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916070] Re: autopkgtest fails in hirsute on armhf with glibc 2.33
maybe the syscall could be backported to Bionic's linux package. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916070 Title: autopkgtest fails in hirsute on armhf with glibc 2.33 Status in linux package in Ubuntu: New Status in notepadqq package in Ubuntu: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/armhf/n/notepadqq/20210217_182537_f860b@/log.gz ... autopkgtest [18:25:08]: test gui: [--- ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 autopkgtest [18:25:16]: test gui: ---] autopkgtest [18:25:18]: test gui: - - - - - - - - - - results - - - - - - - - - - gui FAIL non-zero exit status 1 ... The syscall in question is futex_time64: https://github.com/seccomp/libseccomp/blob/v2.5.0/src/syscalls.csv#L99 The armhf autopgktests run in LXD running on Bionic with Linux 4.15 kernel: autopkgtest [18:22:22]: testbed running kernel: Linux 4.15.0-135-generic #139-Ubuntu SMP Mon Jan 18 17:40:29 UTC 2021 The test passes when running it on Focal as the LXD host, with Linux 5.4: Linux ip-172-31-21-155 5.4.0-1037-aws #39-Ubuntu SMP Thu Jan 14 02:53:31 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux In the 4.15 kernel the syscall is not implemented as observed using strace: gui.trace.5364:futex_time64(0xe55fd210, FUTEX_WAIT_BITSET_PRIVATE, 0, {tv_sec=7495146, tv_nsec=17321283297740747954}, FUTEX_BITSET_MATCH_ANY) = -1 ENOSYS (Function not implemented) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916070] [NEW] autopkgtest fails in hirsute on armhf with glibc 2.33
Public bug reported: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/armhf/n/notepadqq/20210217_182537_f860b@/log.gz ... autopkgtest [18:25:08]: test gui: [--- ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 autopkgtest [18:25:16]: test gui: ---] autopkgtest [18:25:18]: test gui: - - - - - - - - - - results - - - - - - - - - - gui FAIL non-zero exit status 1 ... The syscall in question is futex_time64: https://github.com/seccomp/libseccomp/blob/v2.5.0/src/syscalls.csv#L99 The armhf autopgktests run in LXD running on Bionic with Linux 4.15 kernel: autopkgtest [18:22:22]: testbed running kernel: Linux 4.15.0-135-generic #139-Ubuntu SMP Mon Jan 18 17:40:29 UTC 2021 The test passes when running it on Focal as the LXD host, with Linux 5.4: Linux ip-172-31-21-155 5.4.0-1037-aws #39-Ubuntu SMP Thu Jan 14 02:53:31 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux In the 4.15 kernel the syscall is not implemented as observed using strace: gui.trace.5364:futex_time64(0xe55fd210, FUTEX_WAIT_BITSET_PRIVATE, 0, {tv_sec=7495146, tv_nsec=17321283297740747954}, FUTEX_BITSET_MATCH_ANY) = -1 ENOSYS (Function not implemented) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: notepadqq (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916070 Title: autopkgtest fails in hirsute on armhf with glibc 2.33 Status in linux package in Ubuntu: New Status in notepadqq package in Ubuntu: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/armhf/n/notepadqq/20210217_182537_f860b@/log.gz ... autopkgtest [18:25:08]: test gui: [--- ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422 autopkgtest [18:25:16]: test gui: ---] autopkgtest [18:25:18]: test gui: - - - - - - - - - - results - - - - - - - - - - gui FAIL non-zero exit status 1 ... The syscall in question is futex_time64: https://github.com/seccomp/libseccomp/blob/v2.5.0/src/syscalls.csv#L99 The armhf autopgktests run in LXD running on Bionic with Linux 4.15 kernel: autopkgtest [18:22:22]: testbed running kernel: Linux 4.15.0-135-generic #139-Ubuntu SMP Mon Jan 18 17:40:29 UTC 2021 The test passes when running it on Focal as the LXD host, with Linux 5.4: Linux ip-172-31-21-155 5.4.0-1037-aws #39-Ubuntu SMP Thu Jan 14 02:53:31 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux In the 4.15 kernel the syscall is not implemented as observed using strace: gui.trace.5364:futex_time64(0xe55fd210, FUTEX_WAIT_BITSET_PRIVATE, 0, {tv_sec=7495146, tv_nsec=17321283297740747954}, FUTEX_BITSET_MATCH_ANY) = -1 ENOSYS (Function not implemented) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
Since this breaks systems unattended I'm marking the bug as High, but I recommend the Critical severity. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Medium => High -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
The linux packgages need to add breaks against in-archive dkms modules failing to build with the updated kernel, thus APT and APT frontends can hold back the upgrade until all dkms package updates become ready. ** Changed in: update-manager (Ubuntu) Status: New => Invalid ** Changed in: apt (Ubuntu) Status: New => 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This is only a linux package update process problem, and apt frontends can do nothing to prevent it. ** Changed in: unattended-upgrades (Ubuntu) Status: New => 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907298] Re: glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8
It seems there may be a kernel-side fix: https://lists.ozlabs.org/pipermail/linuxppc-dev/2021-January/223199.html I've committed XFAIL-ing the test for now, to be landed in Hirsute this/next week. ** Changed in: glibc (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907298 Title: glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8 Status in GLibC: Unknown Status in glibc package in Ubuntu: Fix Committed Status in linux package in Ubuntu: New Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/ppc64el/g/glibc/20201208_192946_04f11@/log.gz -- FAIL: misc/tst-sigcontext-get_pc original exit status 1 info: address in signal handler: 0x737faa11db44 info: call stack entry 0: 0x737faa311f58 info: call stack entry 1: 0x737faa3404c4 info: call stack entry 2: 0x0 info: call stack entry 3: 0x737faa312144 info: call stack entry 4: 0x737faa312870 info: call stack entry 5: 0x737faa313264 info: call stack entry 6: 0x737faa311c40 info: call stack entry 7: 0x737faa0f9e5c info: call stack entry 8: 0x737faa0fa040 error: ../sysdeps/unix/sysv/linux/tst-sigcontext-get_pc.c:60: not true: found error: 1 test failures -- To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1907298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776967] Re: glibc pkeys test fail on powerpc
** Changed in: glibc (Ubuntu Cosmic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776967 Title: glibc pkeys test fail on powerpc Status in glibc package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in glibc source package in Bionic: New Status in linux source package in Bionic: Invalid Status in glibc source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Fix Released Bug description: powerpc introduced protection keys support, now present on 4.17 kernel. glibc has a tst-pkey that fails on powerpc, and that needs further investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1776967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773363] Re: glibc tst-preadvwritev2 and tst-preadvwritev64v2 fail with Linux 4.16+
** Changed in: glibc (Ubuntu Cosmic) Status: Confirmed => Invalid ** Changed in: glibc (Ubuntu Cosmic) Status: Invalid => Won't Fix ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773363 Title: glibc tst-preadvwritev2 and tst-preadvwritev64v2 fail with Linux 4.16+ Status in GLibC: Fix Released Status in glibc package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in glibc source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in glibc source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/amd64/g/glibc/20180524_160944_1abf8@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/ppc64el/g/glibc/20180524_155206_1abf8@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1773363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
** Changed in: ec2-hibinit-agent (Ubuntu Xenial) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Xenial: Invalid Status in linux-aws source package in Xenial: New Status in ec2-hibinit-agent source package in Bionic: Fix Released Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: Fix Released Status in linux-aws source package in Eoan: Won't Fix Status in ec2-hibinit-agent source package in Focal: Fix Released Status in linux-aws source package in Focal: New Bug description: [Impact] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. [Test Case] 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. [Regression Potential] The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel module before restarting systemd-networkd. If the kernel module is removed (for example when hitting LP: #1615381) the module reloading fails and the instance can not restore network connections. This is expected to a be very rare situation and the module reload is the best workaround the Kernel Team found to mitigate the original issue. The workaround also adds a 2 second delay before reloading the modules to let things settle a bit after resuming. The 2 seconds is very short compared to the overall time needed resuming an instance. [Original Bug Text] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
@fginther Xenial does not need the backport, right? ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ec2-hibinit-agent (Ubuntu Xenial) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Xenial: Incomplete Status in linux-aws source package in Xenial: New Status in ec2-hibinit-agent source package in Bionic: Fix Released Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: Fix Released Status in linux-aws source package in Eoan: Won't Fix Status in ec2-hibinit-agent source package in Focal: Fix Released Status in linux-aws source package in Focal: New Bug description: [Impact] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. [Test Case] 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. [Regression Potential] The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel module before restarting systemd-networkd. If the kernel module is removed (for example when hitting LP: #1615381) the module reloading fails and the instance can not restore network connections. This is expected to a be very rare situation and the module reload is the best workaround the Kernel Team found to mitigate the original issue. The workaround also adds a 2 second delay before reloading the modules to let things settle a bit after resuming. The 2 seconds is very short compared to the overall time needed resuming an instance. [Original Bug Text] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1892728] Re: ec2-hibinit-agent needs to properly initialize swap file
It seems the kernel needs to be fixed, because fallocate changed in the kernel according to Andrea: https://lkml.org/lkml/2020/9/4/259 ** Package changed: ec2-hibinit-agent (Ubuntu Groovy) => linux (Ubuntu Groovy) ** Changed in: linux (Ubuntu Groovy) Assignee: Balint Reczey (rbalint) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892728 Title: ec2-hibinit-agent needs to properly initialize swap file Status in linux package in Ubuntu: Incomplete Status in linux source package in Groovy: Incomplete Bug description: With commit 30460e1ea3e6 ("fs: Enable bmap() function to properly return errors"), applied to v5.6-rc1, running swapon on a file that has holes returns an error (EINVAL); hibinit-agent is creating the swap file just using fallocate(), without touching the whole file by deafult, so there might be holes, swapon fails and hibernation cannot be performed. To prevent this problem we need to touch the swap file before using it and this can be done setting "touch-swap = True" in /etc/hibinit- config.cfg. The downside of this setting is that a new instance requires more time to be properly "initialized" the first time it boots due to the extra I/O required to touch the swap file (this additional I/O can be quite consistent in large instances, like c5.18xlarge for example), but I don't see a better way to make sure the file is all allocated without holes, so I guess we need to turn on this option if we want to use hibernation w/ kernels >= 5.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896736] Re: Black screen after resume from suspend invoked by lid close on Thinkpad
Does not occur on my Thinkpad Yoga X1, probably a driver issue. ** Package changed: systemd (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/1896736 Title: Black screen after resume from suspend invoked by lid close on Thinkpad Status in linux package in Ubuntu: New Bug description: I can resume my laptop without problems when suspend via window manager like xfce in my case. However when closing the lid the resume does not work, the screen remains blank when opened again while the system is working (CTRL-ALT-F2 working and so on). Looking at Xorg.0.log shows me no action right after suspend. So it looks like X does not get any resume trigger when the lid is opened again. So I assume a problem in the signal chain whoever is responsible for this? Xorg.0.log excerpt: [ 1745.027] (II) event8 - Logitech K750: device removed [ 1745.055] (II) event15 - Logitech MX Anywhere 2: device removed [ 1745.072] (II) event21 - MX Anywhere 2 Keyboard: device removed [ 1745.092] (II) event22 - MX Anywhere 2 Mouse: device removed [ 1745.139] (II) AIGLX: Suspending AIGLX clients for VT switch *** following section is missing when lid is opened *** [ 1749.149] (II) AIGLX: Resuming AIGLX clients after VT switch [ 1749.151] (II) modeset(0): EDID vendor "SDC", prod id 16705 [ 1749.151] (II) modeset(0): Printing DDC gathered Modelines: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Sep 23 10:57:19 2020 InstallationDate: Installed on 2019-12-19 (278 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=61de670d-9f3a-4c81-830c-6139384d0e13 ro modeprobe.blacklist=nouveau amd_iommu=off resume=UUID=3f5116a3-c5a3-490f-b029-2388b7adac74 quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET47W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET47W(1.34):bd08/06/2020:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.logind.conf: 2020-09-23T10:22:54.440796 mtime.conffile..etc.systemd.resolved.conf: 2020-06-01T22:34:53.022126 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890913] Re: init is using 100% of processor
*** This bug is a duplicate of bug 1891657 *** https://bugs.launchpad.net/bugs/1891657 ** This bug has been marked a duplicate of bug 1891657 systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890913 Title: init is using 100% of processor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890913] Re: init is using 100% of processor
*** This bug is a duplicate of bug 1891657 *** https://bugs.launchpad.net/bugs/1891657 Will be fixed in next upload, in 246.6-1ubuntu1 https://github.com/systemd/systemd/issues/16669 ** Bug watch added: github.com/systemd/systemd/issues #16669 https://github.com/systemd/systemd/issues/16669 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890913 Title: init is using 100% of processor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
@paelzer To correct myself this (s390x) regression is not due to the snapd seeding issue, but LP: #1895576 which may have been already fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
@paelzer I agree that the fact, i.e. that systemd autpkgtest is failing in Groovy/s390x, but this is a real regression which is not due to flakiness of tests-in-lxd. Please don't reopen this bug, but file a new one or find one already opened. As I see this is still LP: #1878225. I'm filing a hint for it for now. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the
[Kernel-packages] [Bug 1891336] Re: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel
** Tags added: update-excuse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891336 Title: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel Status in cpufreqd package in Ubuntu: New Status in gkrellm2-cpufreq package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I don't know how important that is as gkrellm2-cpufreq itself is scheduled for removal. But I wanted to make sure that it is known that the Debian kernel produces "libcpupower-dev" which isn't available in Ubuntu and thereby blocking various things in proposed. root@d10-sid:~# apt-cache show libcpupower-dev Package: libcpupower-dev Source: linux Version: 5.7.10-1 Installed-Size: 169 Maintainer: Debian Kernel Team Architecture: amd64 Replaces: libcpufreq-dev Provides: libcpufreq-dev Depends: libcpupower1 (= 5.7.10-1) Conflicts: libcpufreq-dev Description-en: CPU frequency and voltage scaling tools for Linux (development files) libcpupower is a library for inspecting and controlling cpufreq and cpuidle tunables. . This package is needed to compile programs against libcpupower. gkrellm2-cpufreq will most likely be removed from goovy as it makes no sense without that build-dep. Never the less the kernel Team could evaluate if providing "libcpupower-dev" makes sense for Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1891336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890913] Re: init is using 100% of processor
Systemd since then migrated and probably we don't want to have the kernel migrated as well to trigger the issue, thus I've added the block- proposed tag. ** Tags added: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890913 Title: init is using 100% of processor Status in linux package in Ubuntu: Incomplete Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890913] Re: init is using 100% of processor
Fastboot is known to cause issues on older CPUs: https://wiki.archlinux.org/index.php/intel_graphics#Fastboot If the i915.fastboot=1 option was _not_ set by you manually then please reopen the bug by settint status to New. ** Changed in: systemd (Ubuntu) Importance: High => Undecided ** Changed in: systemd (Ubuntu) Status: New => Incomplete ** Package changed: systemd (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890913 Title: init is using 100% of processor Status in linux package in Ubuntu: Invalid Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851663] Re: (In)consistent autopkgtest failures on ppc64el/s390x
** Summary changed: - Consistent autopkgtest failures on ppc64el/s390x + (In)consistent autopkgtest failures on ppc64el/s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1851663 Title: (In)consistent autopkgtest failures on ppc64el/s390x Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Eoan: Confirmed Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Bug description: Recently autopkgtest started to consistently fail in ppc64el / s390x. When testing manually, the kernel dump is collected and all works fine. By discussing with the package maintainer (Cascardo), it seems it started after a change in the instance type of the tests, to m1.large. This seems either a problem in the test infrastructure itself or a likely a "timing" problem in the test (i.e., requiring some pause or delay that is not currently enough). This demands investigation because those failures delay the package release for all arches, usually those releases contain important fixes. Also, the recurrent "workaround" is to mark the tests as "force- badtest" in ubuntu-hints for the 2 arches, which is in practice skipping the test, so those 2 arches are getting releases untested by the automatic infrastructure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
I've added the OEM Solutions Group team for awareness. I'm not sure what the final fix will be since servers' and desktops'/laptops' ideal default seem to be different, but most likely the certification tests should be adjusted if we don't end up restoring the previous behaviour of the ondemand.service unconditionally. The latest LTS release, 20.04 is not affected so the certification test changes are probably not very urgent. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Focal: New Status in systemd source package in Focal: Fix Released Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Focal: New Status in systemd source package in Focal: Fix Released Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888442] Re: upgrade did not go well
You seem to be using ZFS on root (which is EXPERIMENTAL AFAIK). ... update-initramfs: Generating /boot/initrd.img-5.4.0-41-generic cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu cryptsetup: WARNING: Couldn't determine root device ... ** Package changed: systemd (Ubuntu) => zfs-linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1888442 Title: upgrade did not go well Status in zfs-linux package in Ubuntu: New Bug description: Hello, I had some problems during my most recent apt upgrade. A confounding factor to these problems was removing my laptop from its docking station a few minutes earlier. $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-5.4.0-42 linux-headers-5.4.0-42-generic linux-image-5.4.0-42-generic linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic python3-click python3-colorama The following packages will be upgraded: base-files libnss-mymachines libnss-systemd libpam-systemd libpulse-mainloop-glib0 libpulse0 libpulsedsp libseccomp2 libsystemd0 libudev1 libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 linux-firmware linux-generic linux-headers-generic linux-image-generic pulseaudio pulseaudio-utils python3-distupgrade sudo systemd systemd-container systemd-journal-remote systemd-sysv systemd-timesyncd ubuntu-drivers-common ubuntu-release-upgrader-core udev 34 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 110 MB/184 MB of archives. After this operation, 360 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://wopr.domain/ubuntu focal-proposed/main amd64 base-files amd64 11ubuntu5.1 [60.1 kB] Get:2 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-systemd amd64 245.4-4ubuntu3.2 [95.6 kB] Get:3 http://wopr.domain/ubuntu focal-proposed/universe amd64 systemd-journal-remote amd64 245.4-4ubuntu3.2 [61.9 kB] Get:4 http://wopr.domain/ubuntu focal-proposed/main amd64 udev amd64 245.4-4ubuntu3.2 [1,363 kB] Get:5 http://wopr.domain/ubuntu focal-proposed/main amd64 libudev1 amd64 245.4-4ubuntu3.2 [78.9 kB] Get:6 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system amd64 6.0.0-0ubuntu8.2 [67.5 kB] Get:7 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-clients amd64 6.0.0-0ubuntu8.2 [343 kB] Get:8 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.2 [605 kB] Get:9 http://wopr.domain/ubuntu focal-proposed/universe amd64 libvirt-daemon-driver-storage-zfs amd64 6.0.0-0ubuntu8.2 [21.4 kB] Get:10 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-storage-rbd amd64 6.0.0-0ubuntu8.2 [28.3 kB] Get:11 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt0 amd64 6.0.0-0ubuntu8.2 [1,444 kB] Get:12 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon amd64 6.0.0-0ubuntu8.2 [404 kB] Get:13 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-mymachines amd64 245.4-4ubuntu3.2 [131 kB] Get:14 http://wopr.domain/ubuntu focal-proposed/main amd64 libseccomp2 amd64 2.4.3-1ubuntu3.20.04.3 [42.4 kB] Get:15 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-container amd64 245.4-4ubuntu3.2 [317 kB] Get:16 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system-systemd amd64 6.0.0-0ubuntu8.2 [12.3 kB] Get:17 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-sysv amd64 245.4-4ubuntu3.2 [10.3 kB] Get:18 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.2 [28.0 kB] Get:19 http://wopr.domain/ubuntu focal-proposed/main amd64 libpam-systemd amd64 245.4-4ubuntu3.2 [186 kB] Get:20 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd amd64 245.4-4ubuntu3.2 [3,796 kB] Get:21 http://wopr.domain/ubuntu focal-proposed/main amd64 libsystemd0 amd64 245.4-4ubuntu3.2 [271 kB] Get:22 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulse-mainloop-glib0 amd64 1:13.99.1-1ubuntu3.5 [11.7 kB] Get:23 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulsedsp amd64 1:13.99.1-1ubuntu3.5 [21.7 kB] Get:24 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio-utils amd64 1:13.99.1-1ubuntu3.5 [55.0 kB] Get:25 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio amd64 1:13.99.1-1ubuntu3.5 [815 kB] Get:26 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulse0 amd64 1:13.99.1-1ubuntu3.5 [263 kB] Get:27 http://wopr.domain/ubuntu focal/main amd64
[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
I have a freshly installed 20.10 system running on a 2012 MacBook Air (MBA 5,2) and it is completely silent and cold when being idle: rbalint@chaos:~$ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 2.80 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 2.80 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 915 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2600 MHz max turbo 4 active cores 2600 MHz max turbo 3 active cores 2600 MHz max turbo 2 active cores 2800 MHz max turbo 1 active cores @seb128, @juliank I'm not sure if there is anything to fix in the user space, but please report which laptops you experienced issues with. Those may need firmware/kernel fixes. ** Changed in: systemd (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
@xnox @juliank IMO there is no real need for different boot time and post-boot governor. I think where we would like to save power or be less noisy the (possibly) faster boot does not have huge impact on user satisfaction. I agree that fans should not be on all the time in laptops/desktops. If we agree that there is no need for separate boot time and post-boot governor then I think the proper place to set the right default is the kernel. I'd love to hear the Kernel Team's opinion on the matter because there were quite of lot of discussions in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: New Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
The commit message removing ondemand.service has several bug references, too: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=65f46a7d14b335e5743350dbbc5b5ef1e72826f7 remove Ubuntu-specific ondemand.service New processors handle scaling/throttling in internal firmware (e.g. intel_pstate), and do not require OS config. Additionally, nobody else does this, not even Debian. And finally, this has caused problems for years, e.g.: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1497375 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1503773 https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1480320 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806012 https://bugs.launchpad.net/charm-sysconfig/+bug/1873028 IMO the kernel is a better place for setting the default governor properly and can even set different governors in cloud-specific kernels. If the decision is to control the governor in user space in Ubuntu I'd prefer a solution shipped in an other package because systemd does too many things already. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
@raharper I've forwarded the systemd fix for you with minimal tidying of the commit message https://github.com/systemd/systemd/pull/16317 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: bcache-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-signed (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Reopening against bcache-tools according to @raharper's comment about preferring a different fix. https://bugs.launchpad.net/ubuntu/groovy/+source/bcache-tools/+bug/1861941/comments/28 ** Changed in: bcache-tools (Ubuntu Groovy) Status: Fix Released => Triaged ** Changed in: bcache-tools (Ubuntu Groovy) Assignee: Balint Reczey (rbalint) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Changed in: systemd (Ubuntu Focal) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Fix Released Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
@raharper Thanks, I've uploaded the systemd fix to Groovy. Could you please forward it to upstream? Also please update bcache-tools since it is Server Team's package and I also can't upload to Debian until the next keyring refresh. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in bcache-tools source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: New Status in systemd source package in Focal: Invalid Status in bcache-tools source package in Groovy: Fix Released Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: New Status in systemd source package in Groovy: Invalid Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
@raharper To my understanding with the change action udev removes the DEVLINKS which are not still valid. Udev can't tell which links are still valid in cache/by-*. The only reason udev knows about the links is because the rule added them with SYMLINK+= when the dev was created and it is a sane assumption that when a change action appears with DEVLINKS only the new DEVLINKS are valid. Hence the fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-signed package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bcache-tools source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: New Status in systemd source package in Focal: Invalid Status in bcache-tools source package in Groovy: Fix Released Status in linux source package in Groovy: Invalid Status in linux-signed source package in Groovy: Invalid Status in systemd source package in Groovy: Invalid Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
The reason for udev cleaning up the links is that they are missing from the change event's DEVLINKS. Since bcache-tools manages those symlinks IMO it should keep them around. Please take a look at the attached patch, I'll upload it if it is OK. ** Patch added: "bcache-tools_1.0.8-3ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941/+attachment/5374566/+files/bcache-tools_1.0.8-3ubuntu1.patch ** Also affects: bcache-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => Invalid ** Changed in: systemd (Ubuntu Groovy) Status: In Progress => Invalid ** Changed in: bcache-tools (Ubuntu Groovy) Importance: Undecided => High ** Changed in: bcache-tools (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-signed (Ubuntu Groovy) Status: New => Invalid ** Changed in: bcache-tools (Ubuntu Groovy) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in linux-signed package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bcache-tools source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: New Status in systemd source package in Focal: Invalid Status in bcache-tools source package in Groovy: In Progress Status in linux source package in Groovy: Invalid Status in linux-signed source package in Groovy: Invalid Status in systemd source package in Groovy: Invalid Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Changed in: systemd (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in systemd package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux-signed source package in Focal: New Status in systemd source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: New Status in systemd source package in Groovy: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721558] Re: ubuntu-regression-suite fails
Now it fails with: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/amd64/l/linux- oem-5.6/20200502_224124_fb091@/log.gz autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs /bin/sh: 1: python: not found ubuntu-regression-suite FAIL badpkg blame: linux-oem-5.6 badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. autopkgtest [22:41:04]: summary rebuild PASS ubuntu-regression-suite FAIL badpkg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1721558 Title: ubuntu-regression-suite fails Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Status in linux-aws source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-gcp source package in Xenial: New Status in linux-gke source package in Xenial: New Status in linux-hwe-edge source package in Xenial: New Status in linux-kvm source package in Xenial: New Bug description: ubuntu-regression-suite fails in xenial autopkgtest [22:34:48]: test ubuntu-regression-suite: [--- Source Package Version: 4.4.0-1035.44 Running Kernel Version: 4.4.0-96.119 ERROR: running version does not match source package Please note autopkgtests have quite elaborate setup for the kernels, thus I'm guessing that some of the setup is not done right, and the VMs are still running generic kernel instead of customized kernel. Maybe a reboot mark is needed in the ubuntu-regression-suite case to reboot the system if Source != Running. And if that doesn't help either, then fail the test? This affects a few packages which all trip up ADT testing whenever I SRU systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Tags added: 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-5.4 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871887] Re: oss4-dkms fails to install on armhf
** Branch unlinked: lp:~rbalint/britney/hints-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/1871887 Title: oss4-dkms fails to install on armhf Status in linux package in Ubuntu: Confirmed Status in oss4 package in Ubuntu: New Bug description: oss4 autopkgtest fails when building the dkms module: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/armhf/o/oss4/20200409_153053_073f6@/log.gz : ... Building initial module for 5.4.0-21-generic Error! Bad return status for module build on kernel: 5.4.0-21-generic (armv7l) Consult /var/lib/dkms/oss4/4.2-build2010/build/make.log for more information. dpkg: error processing package oss4-dkms (--configure): installed oss4-dkms package post-installation script subprocess returned error exit status 10 ... Apparently it is caused by kernel Makefiles setting hard and soft float on the same gcc line (soft is wrong for armhf): # cat /var/lib/dkms/oss4/4.2-build2010/build/make.log DKMS make.log for oss4-4.2-build2010 for kernel 5.4.0-21-generic (armv8l) Thu Apr 9 17:01:04 UTC 2020 make: Entering directory '/usr/src/linux-headers-5.4.0-21-generic' CC [M] /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o gcc: error: -mfloat-abi=soft and -mfloat-abi=hard may not be used together make[1]: *** [scripts/Makefile.build:275: /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o] Error 1 make: *** [Makefile:1719: /var/lib/dkms/oss4/4.2-build2010/build/core] Error 2 make: Leaving directory '/usr/src/linux-headers-5.4.0-21-generic' The source of the wrong flag seems to be: $ grep soft /usr/src/linux-headers-5.4.0-21/arch/arm/Makefile KBUILD_CFLAGS +=$(CFLAGS_ABI) $(CFLAGS_ISA) $(arch-y) $(tune-y) $(call cc-option,-mshort-load-bytes,$(call cc-option,-malignment-traps,)) -msoft-float -Uarm ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Merge proposal unlinked: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+merge/382712 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-5.4 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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.
** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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 gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: 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 logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871887] Re: oss4-dkms fails to install on armhf
** Branch linked: lp:~rbalint/britney/hints-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/1871887 Title: oss4-dkms fails to install on armhf Status in linux package in Ubuntu: Confirmed Status in oss4 package in Ubuntu: New Bug description: oss4 autopkgtest fails when building the dkms module: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/armhf/o/oss4/20200409_153053_073f6@/log.gz : ... Building initial module for 5.4.0-21-generic Error! Bad return status for module build on kernel: 5.4.0-21-generic (armv7l) Consult /var/lib/dkms/oss4/4.2-build2010/build/make.log for more information. dpkg: error processing package oss4-dkms (--configure): installed oss4-dkms package post-installation script subprocess returned error exit status 10 ... Apparently it is caused by kernel Makefiles setting hard and soft float on the same gcc line (soft is wrong for armhf): # cat /var/lib/dkms/oss4/4.2-build2010/build/make.log DKMS make.log for oss4-4.2-build2010 for kernel 5.4.0-21-generic (armv8l) Thu Apr 9 17:01:04 UTC 2020 make: Entering directory '/usr/src/linux-headers-5.4.0-21-generic' CC [M] /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o gcc: error: -mfloat-abi=soft and -mfloat-abi=hard may not be used together make[1]: *** [scripts/Makefile.build:275: /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o] Error 1 make: *** [Makefile:1719: /var/lib/dkms/oss4/4.2-build2010/build/core] Error 2 make: Leaving directory '/usr/src/linux-headers-5.4.0-21-generic' The source of the wrong flag seems to be: $ grep soft /usr/src/linux-headers-5.4.0-21/arch/arm/Makefile KBUILD_CFLAGS +=$(CFLAGS_ABI) $(CFLAGS_ISA) $(arch-y) $(tune-y) $(call cc-option,-mshort-load-bytes,$(call cc-option,-malignment-traps,)) -msoft-float -Uarm ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871887] Re: oss4-dkms fails to install on armhf
** 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/1871887 Title: oss4-dkms fails to install on armhf Status in linux package in Ubuntu: Confirmed Status in oss4 package in Ubuntu: New Bug description: oss4 autopkgtest fails when building the dkms module: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/armhf/o/oss4/20200409_153053_073f6@/log.gz : ... Building initial module for 5.4.0-21-generic Error! Bad return status for module build on kernel: 5.4.0-21-generic (armv7l) Consult /var/lib/dkms/oss4/4.2-build2010/build/make.log for more information. dpkg: error processing package oss4-dkms (--configure): installed oss4-dkms package post-installation script subprocess returned error exit status 10 ... Apparently it is caused by kernel Makefiles setting hard and soft float on the same gcc line (soft is wrong for armhf): # cat /var/lib/dkms/oss4/4.2-build2010/build/make.log DKMS make.log for oss4-4.2-build2010 for kernel 5.4.0-21-generic (armv8l) Thu Apr 9 17:01:04 UTC 2020 make: Entering directory '/usr/src/linux-headers-5.4.0-21-generic' CC [M] /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o gcc: error: -mfloat-abi=soft and -mfloat-abi=hard may not be used together make[1]: *** [scripts/Makefile.build:275: /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o] Error 1 make: *** [Makefile:1719: /var/lib/dkms/oss4/4.2-build2010/build/core] Error 2 make: Leaving directory '/usr/src/linux-headers-5.4.0-21-generic' The source of the wrong flag seems to be: $ grep soft /usr/src/linux-headers-5.4.0-21/arch/arm/Makefile KBUILD_CFLAGS +=$(CFLAGS_ABI) $(CFLAGS_ISA) $(arch-y) $(tune-y) $(call cc-option,-mshort-load-bytes,$(call cc-option,-malignment-traps,)) -msoft-float -Uarm ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871887] [NEW] oss4-dkms fails to install on armhf
Public bug reported: oss4 autopkgtest fails when building the dkms module: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/armhf/o/oss4/20200409_153053_073f6@/log.gz : ... Building initial module for 5.4.0-21-generic Error! Bad return status for module build on kernel: 5.4.0-21-generic (armv7l) Consult /var/lib/dkms/oss4/4.2-build2010/build/make.log for more information. dpkg: error processing package oss4-dkms (--configure): installed oss4-dkms package post-installation script subprocess returned error exit status 10 ... Apparently it is caused by kernel Makefiles setting hard and soft float on the same gcc line (soft is wrong for armhf): # cat /var/lib/dkms/oss4/4.2-build2010/build/make.log DKMS make.log for oss4-4.2-build2010 for kernel 5.4.0-21-generic (armv8l) Thu Apr 9 17:01:04 UTC 2020 make: Entering directory '/usr/src/linux-headers-5.4.0-21-generic' CC [M] /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o gcc: error: -mfloat-abi=soft and -mfloat-abi=hard may not be used together make[1]: *** [scripts/Makefile.build:275: /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o] Error 1 make: *** [Makefile:1719: /var/lib/dkms/oss4/4.2-build2010/build/core] Error 2 make: Leaving directory '/usr/src/linux-headers-5.4.0-21-generic' The source of the wrong flag seems to be: $ grep soft /usr/src/linux-headers-5.4.0-21/arch/arm/Makefile KBUILD_CFLAGS +=$(CFLAGS_ABI) $(CFLAGS_ISA) $(arch-y) $(tune-y) $(call cc-option,-mshort-load-bytes,$(call cc-option,-malignment-traps,)) -msoft-float -Uarm ... ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: oss4 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871887 Title: oss4-dkms fails to install on armhf Status in linux package in Ubuntu: New Status in oss4 package in Ubuntu: New Bug description: oss4 autopkgtest fails when building the dkms module: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/armhf/o/oss4/20200409_153053_073f6@/log.gz : ... Building initial module for 5.4.0-21-generic Error! Bad return status for module build on kernel: 5.4.0-21-generic (armv7l) Consult /var/lib/dkms/oss4/4.2-build2010/build/make.log for more information. dpkg: error processing package oss4-dkms (--configure): installed oss4-dkms package post-installation script subprocess returned error exit status 10 ... Apparently it is caused by kernel Makefiles setting hard and soft float on the same gcc line (soft is wrong for armhf): # cat /var/lib/dkms/oss4/4.2-build2010/build/make.log DKMS make.log for oss4-4.2-build2010 for kernel 5.4.0-21-generic (armv8l) Thu Apr 9 17:01:04 UTC 2020 make: Entering directory '/usr/src/linux-headers-5.4.0-21-generic' CC [M] /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o gcc: error: -mfloat-abi=soft and -mfloat-abi=hard may not be used together make[1]: *** [scripts/Makefile.build:275: /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o] Error 1 make: *** [Makefile:1719: /var/lib/dkms/oss4/4.2-build2010/build/core] Error 2 make: Leaving directory '/usr/src/linux-headers-5.4.0-21-generic' The source of the wrong flag seems to be: $ grep soft /usr/src/linux-headers-5.4.0-21/arch/arm/Makefile KBUILD_CFLAGS +=$(CFLAGS_ABI) $(CFLAGS_ISA) $(arch-y) $(tune-y) $(call cc-option,-mshort-load-bytes,$(call cc-option,-malignment-traps,)) -msoft-float -Uarm ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867338] Re: Is kerneloops still useful on Ubuntu?
Kerneloops in Debian is also affected by dbus-glib removal: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955906 ** Bug watch added: Debian Bug tracker #955906 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955906 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/1867338 Title: Is kerneloops still useful on Ubuntu? Status in kerneloops package in Ubuntu: New Status in kerneloops package in Debian: Confirmed Bug description: The package is scheduled for removal in Debian due to oops.kernel.org not accepting and showing uploaded oops-es anymore. In Ubuntu kerneloops is changes to collect OOPS-es via apport but it is still possible to configure it to send reports to oops.kernel.org. Kerneloops' removal in Debian may point to the direction of redesigning OOPS collection in Ubuntu without it, then this package should be removed in Ubuntu, too. If kerneloops is kept as an Ubuntu-only package it would be useful to add a note in the configuration file that oops.kernel.org does not accept submissions anymore and the relevant parts could be removed from the codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1867338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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.
** Changed in: systemd (Ubuntu) Status: Invalid => Confirmed ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: systemd (Ubuntu) Status: Invalid => Incomplete -- 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 gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: 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 logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[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.
Marking as invalid for systemd since there is not much pointing at systemd here. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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 gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: 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 logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
Is there anything left to do in systemd? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868568] Re: regression: systemctl suspend works in bionic but not in focal, network doesn't resume
There is a similar issue reported in LP: #1848771. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868568 Title: regression: systemctl suspend works in bionic but not in focal, network doesn't resume Status in linux package in Ubuntu: New Bug description: regression: systemctl suspend works in bionic but not in focal. in bionic the network resumes properly, in focal, it doesn't. also, systemctl hibernate, in both bionic and focal, seems to write to disk, and shuts down, but in both systems, boots up fresh, without restoring. fwiw bionic was installed by free geek before purchase, likely via ubuntu iso. focal was installed by me via lubuntu iso. might there perchance be any special setup needed? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 244.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Mon Mar 23 09:12:59 2020 InstallationDate: Installed on 2020-03-15 (7 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: LENOVO 20C6008SUS ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/fl/boot/vmlinuz ro root=UUID=cb3d9931-e086-4632-8216-1f0aab276d73 subroot=/fl panic=30 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848771] Re: Reboot after resume from suspend (deep)
** Project changed: ubuntu-release-upgrader => linux (Ubuntu) ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => 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/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868568] Re: regression: systemctl suspend works in bionic but not in focal, network doesn't resume
Seems to be kernel regression. It may worth a shot installing linux-oem in similar cases. ** Package changed: systemd (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/1868568 Title: regression: systemctl suspend works in bionic but not in focal, network doesn't resume Status in linux package in Ubuntu: New Bug description: regression: systemctl suspend works in bionic but not in focal. in bionic the network resumes properly, in focal, it doesn't. also, systemctl hibernate, in both bionic and focal, seems to write to disk, and shuts down, but in both systems, boots up fresh, without restoring. fwiw bionic was installed by free geek before purchase, likely via ubuntu iso. focal was installed by me via lubuntu iso. might there perchance be any special setup needed? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 244.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Mon Mar 23 09:12:59 2020 InstallationDate: Installed on 2020-03-15 (7 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: LENOVO 20C6008SUS ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/fl/boot/vmlinuz ro root=UUID=cb3d9931-e086-4632-8216-1f0aab276d73 subroot=/fl panic=30 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
** Description changed: [Impact] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. [Test Case] 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. [Regression Potential] The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel module before restarting systemd-networkd. If the kernel module is removed (for example when hitting LP: #1615381) the module reloading fails and the instance can not restore network connections. This is expected to a be very rare situation and the module reload is the best workaround the Kernel Team found to mitigate the original issue. + + The workaround also adds a 2 second delay before reloading the modules + to let things settle a bit after resuming. The 2 seconds is very short + compared to the overall time needed resuming an instance. [Original Bug Text] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Bionic: New Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: New Status in linux-aws source package in Eoan: New Status in ec2-hibinit-agent source package in Focal: Fix Released Status in linux-aws source package in Focal: New Bug description: [Impact] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. [Test Case] 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console
[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
** Description changed: + [Impact] + + The xen_netfront device is sometimes unresponsive after a hibernate and + resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance + families, all of which are xen based, and support hibernation. + + When the issue occurrs, the instance is inaccessible without a full + restart. Debugging by running a process which outputs regularly to the + serial console shows that the instance is still running. + + [Test Case] + + 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. + 2) Start a long-running process which generates messages to the serial console + 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). + 4) Suspend and resume the instance, continuing to refresh the console screenshot. + 5) The screenshot should continue to show updates even if ssh access is no longer working. + + [Regression Potential] + + The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel module before restarting systemd-networkd. If the kernel module is removed (for example when hitting LP: #1615381) the module reloading fails and + the instance can not restore network connections. This is expected to a be very rare situation and the module reload is the best workaround the Kernel Team found to mitigate the original issue. + + [Original Bug Text] + The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: - TERM=screen - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Bionic: New Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: New Status in linux-aws source package in Eoan: New Status in ec2-hibinit-agent source package in Focal: Fix Released Status in linux-aws source package in Focal: New Bug description: [Impact] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. [Test Case] 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4)
[Kernel-packages] [Bug 1866224] Re: mercurial autopkgtest is failing on s390x
Tests passed with the new glibc. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: git (Ubuntu) Status: New => Invalid ** Changed in: mercurial (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866224 Title: mercurial autopkgtest is failing on s390x Status in git package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in mercurial package in Ubuntu: Invalid Bug description: Mercurial autopkgtest started failing with git/1:2.25.1-1ubuntu1: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- focal/focal/s390x/m/mercurial/20200305_163916_8dbb2@/log.gz ... # Test test-bundle2-exchange.t#sshv1 ok test-bundle2-exchange.t#sshv1 test-bundle2-exchange.t#sshv1 ... # Running sh "/tmp/hgtests.30cCY5/child94/test-bundle2-exchange.t-sshv1.sh" --- /tmp/autopkgtest.9EkXym/build.U2r/src/tests/test-bundle2-exchange.t +++ /tmp/autopkgtest.9EkXym/build.U2r/src/tests/test-bundle2-exchange.t#sshv1.err @@ -880,42 +880,47 @@ adding changesets adding manifests adding file changes - transaction abort! - Cleaning up the mess... - rollback completed + pre-close-tip:e7ec4e813ba6 draft + added 1 changesets with 1 changes to 1 files pushkey: lock state after "phases" lock: free wlock: free - abort: Clown phase push failed - [255] + postclose-tip:e7ec4e813ba6 draft + txnclose hook: HG_BUNDLE2=1 HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose HG_NEW_OBSMARKERS=0 HG_NODE=e7ec4e813ba6b07be2a0516ce1a74bb4e503f91a HG_NODE_LAST=e7ec4e813ba6b07be2a0516ce1a74bb4e503f91a HG_SOURCE=push HG_TXNID=TXN:$ID$ HG_TXNNAME=push HG_URL=file:$TESTTMP/other + pre-close-tip:e7ec4e813ba6 draft + postclose-tip:e7ec4e813ba6 draft + txnclose hook: HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose HG_SOURCE=push-response HG_TXNID=TXN:$ID$ HG_TXNNAME=push-response + file:/*/$TESTTMP/other HG_URL=file:$TESTTMP/other (glob) $ hg -R main push ssh://user@dummy/other -r e7ec4e813ba6 pushing to ssh://user@dummy/other searching for changes - remote: adding changesets - remote: adding manifests - remote: adding file changes - remote: transaction abort! - remote: Cleaning up the mess... - remote: rollback completed + no changes found + remote: pre-close-tip:e7ec4e813ba6 draft remote: pushkey: lock state after "phases" remote: lock: free remote: wlock: free - abort: Clown phase push failed - [255] + remote: postclose-tip:e7ec4e813ba6 draft + remote: txnclose hook: HG_BUNDLE2=1 HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose HG_NEW_OBSMARKERS=0 HG_SOURCE=serve HG_TXNID=TXN:$ID$ HG_TXNNAME=serve HG_URL=remote:ssh:$LOCALIP + pre-close-tip:e7ec4e813ba6 draft + postclose-tip:e7ec4e813ba6 draft + txnclose hook: HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose HG_SOURCE=push-response HG_TXNID=TXN:$ID$ HG_TXNNAME=push-response + ssh://user@dummy/other HG_URL=ssh://user@dummy/other + [1] $ hg -R main push http://localhost:$HGPORT2/ -r e7ec4e813ba6 pushing to http://localhost:$HGPORT2/ searching for changes - remote: adding changesets - remote: adding manifests - remote: adding file changes - remote: transaction abort! - remote: Cleaning up the mess... - remote: rollback completed + no changes found + remote: pre-close-tip:e7ec4e813ba6 draft remote: pushkey: lock state after "phases" # Killing daemon process 21822 remote: lock: free remote: wlock: free - abort: Clown phase push failed - [255] + remote: postclose-tip:e7ec4e813ba6 draft + remote: txnclose hook: HG_BUNDLE2=1 HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose HG_NEW_OBSMARKERS=0 HG_SOURCE=serve HG_TXNID=TXN:$ID$ HG_TXNNAME=serve HG_URL=remote:http:$LOCALIP: + pre-close-tip:e7ec4e813ba6 draft + postclose-tip:e7ec4e813ba6 draft + txnclose hook: HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose HG_SOURCE=push-response HG_TXNID=TXN:$ID$ HG_TXNNAME=push-response + http://localhost:$HGPORT2/ HG_URL=http://localhost:$HGPORT2/ + [1] Test lazily acquiring the lock during unbundle $ cp $TESTTMP/hgrc.orig $HGRCPATH ERROR: test-bundle2-exchange.t#sshv1 output changed !# Ret was: 0 (test-bundle2-exchange.t#sshv1) test-bundle2-exchange.t#sshv2 test-bundle2-exchange.t#sshv2 ... # Test test-bundle2-exchange.t#sshv2 # Running sh "/tmp/hgtests.30cCY5/child95/test-bundle2-exchange.t-sshv2.sh" # Killing daemon process 22519 # Ret was: 0 (test-bundle2-exchange.t#sshv2) ok ... The tests are passing locally in lxc on bionic s390x host: Linux autopkgtest-lxd-narzvo 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:02 UTC 2020 s390x s390x s390x GNU/Linux I'm
[Kernel-packages] [Bug 1867338] [NEW] Is kerneloops still useful on Ubuntu?
Public bug reported: The package is scheduled for removal in Debian due to oops.kernel.org not accepting and showing uploaded oops-es anymore. In Ubuntu kerneloops is changes to collect OOPS-es via apport but it is still possible to configure it to send reports to oops.kernel.org. Kerneloops' removal in Debian may point to the direction of redesigning OOPS collection in Ubuntu without it, then this package should be removed in Ubuntu, too. If kerneloops is kept as an Ubuntu-only package it would be useful to add a note in the configuration file that oops.kernel.org does not accept submissions anymore and the relevant parts could be removed from the codebase. ** Affects: kerneloops (Ubuntu) Importance: Undecided Status: New ** Affects: kerneloops (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #953172 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953172 ** Also affects: kerneloops (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953172 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/1867338 Title: Is kerneloops still useful on Ubuntu? Status in kerneloops package in Ubuntu: New Status in kerneloops package in Debian: Unknown Bug description: The package is scheduled for removal in Debian due to oops.kernel.org not accepting and showing uploaded oops-es anymore. In Ubuntu kerneloops is changes to collect OOPS-es via apport but it is still possible to configure it to send reports to oops.kernel.org. Kerneloops' removal in Debian may point to the direction of redesigning OOPS collection in Ubuntu without it, then this package should be removed in Ubuntu, too. If kerneloops is kept as an Ubuntu-only package it would be useful to add a note in the configuration file that oops.kernel.org does not accept submissions anymore and the relevant parts could be removed from the codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1867338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
@fginther thanks, I keep a 2 second sleep to stay on the safe side. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Bionic: New Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: New Status in linux-aws source package in Eoan: New Status in ec2-hibinit-agent source package in Focal: In Progress Status in linux-aws source package in Focal: New Bug description: The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866224] Re: mercurial autopkgtest is failing on s390x
OK, so I've been able to reproduce the issue locally with 5.4 kernel, running Focal as the lxc host. Linux autopkgtest-lxd-eyhbbj 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:46:43 UTC 2020 s390x s390x s390x GNU/Linux I did not observe the failure with Eoan host, kernel 5.3.x ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866224 Title: mercurial autopkgtest is failing on s390x Status in git package in Ubuntu: New Status in linux package in Ubuntu: New Status in mercurial package in Ubuntu: New Bug description: Mercurial autopkgtest started failing with git/1:2.25.1-1ubuntu1: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- focal/focal/s390x/m/mercurial/20200305_163916_8dbb2@/log.gz ... # Test test-bundle2-exchange.t#sshv1 ok test-bundle2-exchange.t#sshv1 test-bundle2-exchange.t#sshv1 ... # Running sh "/tmp/hgtests.30cCY5/child94/test-bundle2-exchange.t-sshv1.sh" --- /tmp/autopkgtest.9EkXym/build.U2r/src/tests/test-bundle2-exchange.t +++ /tmp/autopkgtest.9EkXym/build.U2r/src/tests/test-bundle2-exchange.t#sshv1.err @@ -880,42 +880,47 @@ adding changesets adding manifests adding file changes - transaction abort! - Cleaning up the mess... - rollback completed + pre-close-tip:e7ec4e813ba6 draft + added 1 changesets with 1 changes to 1 files pushkey: lock state after "phases" lock: free wlock: free - abort: Clown phase push failed - [255] + postclose-tip:e7ec4e813ba6 draft + txnclose hook: HG_BUNDLE2=1 HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose HG_NEW_OBSMARKERS=0 HG_NODE=e7ec4e813ba6b07be2a0516ce1a74bb4e503f91a HG_NODE_LAST=e7ec4e813ba6b07be2a0516ce1a74bb4e503f91a HG_SOURCE=push HG_TXNID=TXN:$ID$ HG_TXNNAME=push HG_URL=file:$TESTTMP/other + pre-close-tip:e7ec4e813ba6 draft + postclose-tip:e7ec4e813ba6 draft + txnclose hook: HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose HG_SOURCE=push-response HG_TXNID=TXN:$ID$ HG_TXNNAME=push-response + file:/*/$TESTTMP/other HG_URL=file:$TESTTMP/other (glob) $ hg -R main push ssh://user@dummy/other -r e7ec4e813ba6 pushing to ssh://user@dummy/other searching for changes - remote: adding changesets - remote: adding manifests - remote: adding file changes - remote: transaction abort! - remote: Cleaning up the mess... - remote: rollback completed + no changes found + remote: pre-close-tip:e7ec4e813ba6 draft remote: pushkey: lock state after "phases" remote: lock: free remote: wlock: free - abort: Clown phase push failed - [255] + remote: postclose-tip:e7ec4e813ba6 draft + remote: txnclose hook: HG_BUNDLE2=1 HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose HG_NEW_OBSMARKERS=0 HG_SOURCE=serve HG_TXNID=TXN:$ID$ HG_TXNNAME=serve HG_URL=remote:ssh:$LOCALIP + pre-close-tip:e7ec4e813ba6 draft + postclose-tip:e7ec4e813ba6 draft + txnclose hook: HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose HG_SOURCE=push-response HG_TXNID=TXN:$ID$ HG_TXNNAME=push-response + ssh://user@dummy/other HG_URL=ssh://user@dummy/other + [1] $ hg -R main push http://localhost:$HGPORT2/ -r e7ec4e813ba6 pushing to http://localhost:$HGPORT2/ searching for changes - remote: adding changesets - remote: adding manifests - remote: adding file changes - remote: transaction abort! - remote: Cleaning up the mess... - remote: rollback completed + no changes found + remote: pre-close-tip:e7ec4e813ba6 draft remote: pushkey: lock state after "phases" # Killing daemon process 21822 remote: lock: free remote: wlock: free - abort: Clown phase push failed - [255] + remote: postclose-tip:e7ec4e813ba6 draft + remote: txnclose hook: HG_BUNDLE2=1 HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose HG_NEW_OBSMARKERS=0 HG_SOURCE=serve HG_TXNID=TXN:$ID$ HG_TXNNAME=serve HG_URL=remote:http:$LOCALIP: + pre-close-tip:e7ec4e813ba6 draft + postclose-tip:e7ec4e813ba6 draft + txnclose hook: HG_HOOKNAME=txnclose.env HG_HOOKTYPE=txnclose HG_SOURCE=push-response HG_TXNID=TXN:$ID$ HG_TXNNAME=push-response + http://localhost:$HGPORT2/ HG_URL=http://localhost:$HGPORT2/ + [1] Test lazily acquiring the lock during unbundle $ cp $TESTTMP/hgrc.orig $HGRCPATH ERROR: test-bundle2-exchange.t#sshv1 output changed !# Ret was: 0 (test-bundle2-exchange.t#sshv1) test-bundle2-exchange.t#sshv2 test-bundle2-exchange.t#sshv2 ... # Test test-bundle2-exchange.t#sshv2 # Running sh "/tmp/hgtests.30cCY5/child95/test-bundle2-exchange.t-sshv2.sh" # Killing daemon process 22519 # Ret was: 0 (test-bundle2-exchange.t#sshv2) ok ... The tests are passing locally in lxc on bionic s390x host: Linux
Re: [Kernel-packages] [Bug 1864045] Re: [SRU] Hibernation events sometimes missed on repeated attempts
> @rbalint if you can reproduce the problem easily, it would be > interesting to monitor the received ACPI events via acpi_listen. I believe the reproduction is very easy for everyone. I could not reproduce newer acpid fixing the problem OTOH. I'd like to have the reproduction steps for that experiment. > What I see during my tests is that acpi_listen is always showing the > sleep events, meaning that the kernel receives them correctly at least, > and then the failure happens in the delivery of these sleep events to > the proper user-space daemon (acpid). So my guess is that something > wrong is happening in the communication between kernel and user-space to > deliver these events. Since only the kernel changed it may be a regression in the kernel or a change in kernel's behaviour that is still valid but acpid somehow breaks. Please either provide the reproduction steps where a different acpid fixes the issue or point at the change in the kernel to which acpid should adapt. I believe this can be found by bisecting the kernel, but I don't have the setup to do it efficiently myself. > Just to make sure, when you say "the second hibernation attempt still > fails" you mean that the system is still up & running (you can still ssh > on it) and the sleep event is lost / not delivered properly, right? Yes, exactly. I can still log in back to the system after a few seconds. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864045 Title: [SRU] Hibernation events sometimes missed on repeated attempts Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in acpid source package in Bionic: Incomplete Status in linux source package in Bionic: Incomplete Status in acpid source package in Eoan: Confirmed Status in linux source package in Eoan: Incomplete Bug description: When testing hibernation / resume on AWS with 5.0 or 5.3 kernels on bionic (using acpid 1:2.0.28-1ubuntu1), we sometimes see failure with repeated attempts. The first attempt will always be triggered, but the next attempt may not. The result is the agent never triggers the hibernation process and the instance will be forced to shutdown after a timeout period. Two workarounds have been identified. The first is to restart acpid during the resume handler. The second is to use the latest upstream acpid (as of Feb 1, 2020). This second workaround indicates there may be a patch missing in the acpid in bionic (1:2.0.28-1ubuntu1) to work with the 5.0+ kernels. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel on a bionic image with on-demand hibernation support enabled. 2) Hibernate and resume the instance, ensuring the system is fully resumed afterward and the swap file has been removed. 3) Hibernate and resume another time. The hibernate should be triggered immediately and the instance should become unresponsive as it saves state to disk. 4) Resume the instance, it should come back with the same processes running. 5) Repeat 3) - 4) as necessary. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: acpid 1:2.0.28-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1864045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864045] Re: [SRU] Hibernation events sometimes missed on repeated attempts
I have tried the 'fixed' acpid version and also tried various versions with 5.0 and 5.3 kernels, but the issue does not seem to be fixed. I've backported acpid 1:2.0.32-1ubuntu1 in ppa:rbalint/scratch2 which is practically the same as 2.0.32-1 compiled on Ubuntu, but the second hibernation attempt still fails. Package versions used: linux-aws-wip/5.3.0.1012.13 acpid/1:2.0.32-1ubuntu1~18.04.0~rbalint3 from ppa:rbalint/scratch2 ec2-hibinit-agent/1.0.0-0ubuntu8~18.04.0~rbalint3 from ppa:rbalint/scratch2 Instance type: c4.large Vanilla Bionic, i.e. kernel 4.15.0-1060-aws and Bionic's acpid hibernates twice without any issue. Could you please add detailed reproduction steps that show how the new acpid was used to fix the issue? For now it looks like a kernel regression and bisecting the Linux commit changing the behaviour would be highly useful. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864045 Title: [SRU] Hibernation events sometimes missed on repeated attempts Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in acpid source package in Bionic: Incomplete Status in linux source package in Bionic: Incomplete Status in acpid source package in Eoan: Confirmed Status in linux source package in Eoan: Incomplete Bug description: When testing hibernation / resume on AWS with 5.0 or 5.3 kernels on bionic (using acpid 1:2.0.28-1ubuntu1), we sometimes see failure with repeated attempts. The first attempt will always be triggered, but the next attempt may not. The result is the agent never triggers the hibernation process and the instance will be forced to shutdown after a timeout period. Two workarounds have been identified. The first is to restart acpid during the resume handler. The second is to use the latest upstream acpid (as of Feb 1, 2020). This second workaround indicates there may be a patch missing in the acpid in bionic (1:2.0.28-1ubuntu1) to work with the 5.0+ kernels. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel on a bionic image with on-demand hibernation support enabled. 2) Hibernate and resume the instance, ensuring the system is fully resumed afterward and the swap file has been removed. 3) Hibernate and resume another time. The hibernate should be triggered immediately and the instance should become unresponsive as it saves state to disk. 4) Resume the instance, it should come back with the same processes running. 5) Repeat 3) - 4) as necessary. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: acpid 1:2.0.28-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1864045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864045] Re: [SRU] Hibernation events sometimes missed on repeated attempts
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864045 Title: [SRU] Hibernation events sometimes missed on repeated attempts Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in acpid source package in Bionic: Incomplete Status in linux source package in Bionic: Incomplete Status in acpid source package in Eoan: Confirmed Status in linux source package in Eoan: Incomplete Bug description: When testing hibernation / resume on AWS with 5.0 or 5.3 kernels on bionic (using acpid 1:2.0.28-1ubuntu1), we sometimes see failure with repeated attempts. The first attempt will always be triggered, but the next attempt may not. The result is the agent never triggers the hibernation process and the instance will be forced to shutdown after a timeout period. Two workarounds have been identified. The first is to restart acpid during the resume handler. The second is to use the latest upstream acpid (as of Feb 1, 2020). This second workaround indicates there may be a patch missing in the acpid in bionic (1:2.0.28-1ubuntu1) to work with the 5.0+ kernels. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel on a bionic image with on-demand hibernation support enabled. 2) Hibernate and resume the instance, ensuring the system is fully resumed afterward and the swap file has been removed. 3) Hibernate and resume another time. The hibernate should be triggered immediately and the instance should become unresponsive as it saves state to disk. 4) Resume the instance, it should come back with the same processes running. 5) Repeat 3) - 4) as necessary. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: acpid 1:2.0.28-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1864045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
In the proposed workaround there is a 15s sleep before the module reload. Is it needed and if so is this a lowest safe choice? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Bionic: New Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: New Status in linux-aws source package in Eoan: New Status in ec2-hibinit-agent source package in Focal: In Progress Status in linux-aws source package in Focal: New Bug description: The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
I'm ready to put the workaround to ec2-hibinit-agent, but it would be much better if the kernel could be fixed. ** Also affects: ec2-hibinit-agent (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: ec2-hibinit-agent (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Bionic: New Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: New Status in linux-aws source package in Eoan: New Status in ec2-hibinit-agent source package in Focal: In Progress Status in linux-aws source package in Focal: New Bug description: The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860672] Re: Autopkgtest failing badly since linux-5.4/5.4.0-11.14
Please find the logs on the links. ** 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/1860672 Title: Autopkgtest failing badly since linux-5.4/5.4.0-11.14 Status in linux package in Ubuntu: Confirmed Bug description: The autopkgtest on the CI infrastructure is failing consistently now: http://autopkgtest.ubuntu.com/packages/l/linux/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200117_130927_d1ea4@/log.gz : ... autopkgtest [13:09:05]: testbed dpkg architecture: amd64 autopkgtest [13:09:06]: apt-source linux blame: linux badpkg: rules extract failed with exit code 1 autopkgtest [13:09:16]: ERROR: erroneous package: rules extract failed with exit code 1 Exit request sent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860672] [NEW] Autopkgtest failing badly since linux-5.4/5.4.0-11.14
Public bug reported: The autopkgtest on the CI infrastructure is failing consistently now: http://autopkgtest.ubuntu.com/packages/l/linux/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200117_130927_d1ea4@/log.gz : ... autopkgtest [13:09:05]: testbed dpkg architecture: amd64 autopkgtest [13:09:06]: apt-source linux blame: linux badpkg: rules extract failed with exit code 1 autopkgtest [13:09:16]: ERROR: erroneous package: rules extract failed with exit code 1 Exit request sent. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860672 Title: Autopkgtest failing badly since linux-5.4/5.4.0-11.14 Status in linux package in Ubuntu: New Bug description: The autopkgtest on the CI infrastructure is failing consistently now: http://autopkgtest.ubuntu.com/packages/l/linux/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200117_130927_d1ea4@/log.gz : ... autopkgtest [13:09:05]: testbed dpkg architecture: amd64 autopkgtest [13:09:06]: apt-source linux blame: linux badpkg: rules extract failed with exit code 1 autopkgtest [13:09:16]: ERROR: erroneous package: rules extract failed with exit code 1 Exit request sent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721558] Re: ubuntu-regression-suite fails in
Also very often fails in later releases: http://autopkgtest.ubuntu.com/packages/l/linux-kvm ** Summary changed: - ubuntu-regression-suite fails in xenial + ubuntu-regression-suite fails in ** Summary changed: - ubuntu-regression-suite fails in + ubuntu-regression-suite fails ** Tags added: update-excuse ** Changed in: linux-kvm (Ubuntu) Status: New => Confirmed ** 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1721558 Title: ubuntu-regression-suite fails Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Status in linux-aws source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-gcp source package in Xenial: New Status in linux-gke source package in Xenial: New Status in linux-hwe-edge source package in Xenial: New Status in linux-kvm source package in Xenial: New Bug description: ubuntu-regression-suite fails in xenial autopkgtest [22:34:48]: test ubuntu-regression-suite: [--- Source Package Version: 4.4.0-1035.44 Running Kernel Version: 4.4.0-96.119 ERROR: running version does not match source package Please note autopkgtests have quite elaborate setup for the kernels, thus I'm guessing that some of the setup is not done right, and the VMs are still running generic kernel instead of customized kernel. Maybe a reboot mark is needed in the ubuntu-regression-suite case to reboot the system if Source != Running. And if that doesn't help either, then fail the test? This affects a few packages which all trip up ADT testing whenever I SRU systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
@tjaalton I find this bug report useful since I can receive updates on how the situation evolves. If there are know separate subclasses of the issue which are fixed separately I agree that it would be a good idea to provide debugging steps here to classify each subclass and track the subclass as a separate bug. When the error in the title fully goes away, the bug can be 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/1550779 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
I also set verification-done, since it is verified that the bug does not occur with .31 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image Status in Ubuntu on IBM z Systems: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Invalid Bug description: Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC image on a z/VM guest leads to a kernel panic: /lib/debian-installer/start-udev: line 15: can't create /sys/module/scsi_mod/par ameters/scan: Permission denied ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ exitcode=0x00 000100 ¬0.845071| ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic #157-Ubun tu ¬0.845077|7d107c20 7d107cb0 0002 000 0 7d107d50 7d107cc8 7d107cc8 00114732 008b 009a304c 009f11d0 000b 7d107d10 7d107cb0 040001cdf800 00114732 7d107cb0 7d107d10 ¬0.845089| Call Trace: ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) ¬0.845095| ¬<001146e2>| show_stack+0x72/0xf8 ¬0.845099| ¬<00555752>| dump_stack+0x82/0xb8 ¬0.845101| ¬<00286390>| panic+0x108/0x250 ¬0.845104| ¬<00166228>| do_exit+0xac0/0xba0 ¬0.845106| ¬<001663c8>| do_group_exit+0x50/0xe0 ¬0.845108| ¬<00166488>| __wake_up_parent+0x0/0x28 ¬0.845111| ¬<007eadda>| system_call+0xee/0x28c ¬0.845113| ¬<03ff8953983a>| 0x3ff8953983a 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0010F8CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
@frank-heimes, thank you for the testing and also for your additional comments. This fix was once accepted to bionic-proposed, while it does not have a test case in the bug description nor the description follows the SRU template: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template . Ensuring that is the job of the SRU uploader, and the first time is was skipped and I also missed that. Since the bug did not exist in 18.04 I'm marking it invalid instead of performing the SRU again. ** Changed in: systemd (Ubuntu Bionic) Status: Incomplete => Invalid ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image Status in Ubuntu on IBM z Systems: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Invalid Bug description: Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC image on a z/VM guest leads to a kernel panic: /lib/debian-installer/start-udev: line 15: can't create /sys/module/scsi_mod/par ameters/scan: Permission denied ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ exitcode=0x00 000100 ¬0.845071| ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic #157-Ubun tu ¬0.845077|7d107c20 7d107cb0 0002 000 0 7d107d50 7d107cc8 7d107cc8 00114732 008b 009a304c 009f11d0 000b 7d107d10 7d107cb0 040001cdf800 00114732 7d107cb0 7d107d10 ¬0.845089| Call Trace: ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) ¬0.845095| ¬<001146e2>| show_stack+0x72/0xf8 ¬0.845099| ¬<00555752>| dump_stack+0x82/0xb8 ¬0.845101| ¬<00286390>| panic+0x108/0x250 ¬0.845104| ¬<00166228>| do_exit+0xac0/0xba0 ¬0.845106| ¬<001663c8>| do_group_exit+0x50/0xe0 ¬0.845108| ¬<00166488>| __wake_up_parent+0x0/0x28 ¬0.845111| ¬<007eadda>| system_call+0xee/0x28c ¬0.845113| ¬<03ff8953983a>| 0x3ff8953983a 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0010F8CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845637] Re: Drop setting fs.protected_regular and fs.protected_fifos from sysctl defaults shipped by systemd
This is not a bug where logs can be collected. ** 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/1845637 Title: Drop setting fs.protected_regular and fs.protected_fifos from sysctl defaults shipped by systemd Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Those settings are typically set by the kernel in Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845637] Re: Drop setting fs.protected_regular and fs.protected_fifos from sysctl defaults shipped by systemd
Those defaults should probably be set by Linux, hence marking linux package as affected. With the systemd packaging dropping the new setting originating from systemd upstream Ubuntu's defaults become less secure in this area compared to other distros leaving upstream defaults applied, thus I also mark this bug as a public security issue. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845637 Title: Drop setting fs.protected_regular and fs.protected_fifos from sysctl defaults shipped by systemd Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Those settings are typically set by the kernel in Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841761] Re: Flaky autopkgtest
I referenced the logs in the bug text. ** 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/1841761 Title: Flaky autopkgtest Status in linux package in Ubuntu: Confirmed Bug description: Package's autopkgtest keeps failing due to trying to download dkms packages which are already removed from the archive. One example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/l/linux/20190813_212926_4bceb@/log.gz ... II: dkms-build downloading zfs (zfs-dkms_0.8.1-1ubuntu7_all.deb) --2019-08-13 21:14:21-- http://ftpmaster.internal/ubuntu/pool/universe/z/zfs-linux/zfs-dkms_0.8.1-1ubuntu7_all.deb Resolving ftpmaster.internal (ftpmaster.internal)... 91.189.89.99 Connecting to ftpmaster.internal (ftpmaster.internal)|91.189.89.99|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-08-13 21:14:21 ERROR 404: Not Found. --2019-08-13 21:14:21-- http://ftpmaster.internal/ubuntu/pool/main/z/zfs-linux/zfs-dkms_0.8.1-1ubuntu7_all.deb Resolving ftpmaster.internal (ftpmaster.internal)... 91.189.89.99 Connecting to ftpmaster.internal (ftpmaster.internal)|91.189.89.99|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-08-13 21:14:21 ERROR 404: Not Found. dpkg-deb: error: failed to read archive 'zfs-dkms_*.deb': No such file or directory make: *** [debian/rules.d/2-binary-arch.mk:220: install-generic] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 ... Due to flakiness we have to keep bumping the brintey hints to migrate other packages from -proposed. Please fix the flakiness by moving the .deb download step closer to the start of the autopkgtest or by other means. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841761] [NEW] Flaky autopkgtest
Public bug reported: Package's autopkgtest keeps failing due to trying to download dkms packages which are already removed from the archive. One example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/l/linux/20190813_212926_4bceb@/log.gz ... II: dkms-build downloading zfs (zfs-dkms_0.8.1-1ubuntu7_all.deb) --2019-08-13 21:14:21-- http://ftpmaster.internal/ubuntu/pool/universe/z/zfs-linux/zfs-dkms_0.8.1-1ubuntu7_all.deb Resolving ftpmaster.internal (ftpmaster.internal)... 91.189.89.99 Connecting to ftpmaster.internal (ftpmaster.internal)|91.189.89.99|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-08-13 21:14:21 ERROR 404: Not Found. --2019-08-13 21:14:21-- http://ftpmaster.internal/ubuntu/pool/main/z/zfs-linux/zfs-dkms_0.8.1-1ubuntu7_all.deb Resolving ftpmaster.internal (ftpmaster.internal)... 91.189.89.99 Connecting to ftpmaster.internal (ftpmaster.internal)|91.189.89.99|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-08-13 21:14:21 ERROR 404: Not Found. dpkg-deb: error: failed to read archive 'zfs-dkms_*.deb': No such file or directory make: *** [debian/rules.d/2-binary-arch.mk:220: install-generic] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 ... Due to flakiness we have to keep bumping the brintey hints to migrate other packages from -proposed. Please fix the flakiness by moving the .deb download step closer to the start of the autopkgtest or by other means. ** 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/1841761 Title: Flaky autopkgtest Status in linux package in Ubuntu: Incomplete Bug description: Package's autopkgtest keeps failing due to trying to download dkms packages which are already removed from the archive. One example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/l/linux/20190813_212926_4bceb@/log.gz ... II: dkms-build downloading zfs (zfs-dkms_0.8.1-1ubuntu7_all.deb) --2019-08-13 21:14:21-- http://ftpmaster.internal/ubuntu/pool/universe/z/zfs-linux/zfs-dkms_0.8.1-1ubuntu7_all.deb Resolving ftpmaster.internal (ftpmaster.internal)... 91.189.89.99 Connecting to ftpmaster.internal (ftpmaster.internal)|91.189.89.99|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-08-13 21:14:21 ERROR 404: Not Found. --2019-08-13 21:14:21-- http://ftpmaster.internal/ubuntu/pool/main/z/zfs-linux/zfs-dkms_0.8.1-1ubuntu7_all.deb Resolving ftpmaster.internal (ftpmaster.internal)... 91.189.89.99 Connecting to ftpmaster.internal (ftpmaster.internal)|91.189.89.99|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-08-13 21:14:21 ERROR 404: Not Found. dpkg-deb: error: failed to read archive 'zfs-dkms_*.deb': No such file or directory make: *** [debian/rules.d/2-binary-arch.mk:220: install-generic] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 ... Due to flakiness we have to keep bumping the brintey hints to migrate other packages from -proposed. Please fix the flakiness by moving the .deb download step closer to the start of the autopkgtest or by other means. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838476] Re: conntrack-tools autopkgtest failing with 5.2 kernel
Please see the logs on the link. ** 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/1838476 Title: conntrack-tools autopkgtest failing with 5.2 kernel Status in linux package in Ubuntu: Confirmed Bug description: It is passing with linux-image-5.0.0-1011-kvm in my local tests. See: http://autopkgtest.ubuntu.com/packages/c/conntrack-tools/eoan/amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838476] [NEW] conntrack-tools autopkgtest failing with 5.2 kernel
Public bug reported: It is passing with linux-image-5.0.0-1011-kvm in my local tests. See: http://autopkgtest.ubuntu.com/packages/c/conntrack-tools/eoan/amd64 ** 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/1838476 Title: conntrack-tools autopkgtest failing with 5.2 kernel Status in linux package in Ubuntu: New Bug description: It is passing with linux-image-5.0.0-1011-kvm in my local tests. See: http://autopkgtest.ubuntu.com/packages/c/conntrack-tools/eoan/amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Xorg and the kernel are doing the right thing here. ** No longer affects: linux (Ubuntu) ** Changed in: xorg-server (Ubuntu Bionic) Status: Confirmed => Invalid ** Changed in: xorg-server (Ubuntu Cosmic) Status: Confirmed => Invalid ** Changed in: xorg-server (Ubuntu Disco) Status: Confirmed => Invalid ** Changed in: xorg-server (Ubuntu Eoan) Status: Confirmed => 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/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Bionic: Fix Committed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Committed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Committed Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: Confirmed Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Workaround] Reboot (or restart X) and the problem will go away. [Test Case] [racb] Note that upgrading to the fixed package will not fix the problem for affected users; you must reboot (or restart X) as above. The fix only prevents the problem occurring again. * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same: $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
@samuel-thibault kbd_mode would check current state and only allow safe mode switches without -f, i.e. between unicode and ascii. Scripts changing between those modes would not have to be changed. I fixed postinst to not pass -f to setupcon, it is in eoan-proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: Confirmed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in console-setup source package in Cosmic: Confirmed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Status in console-setup source package in Disco: In Progress Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: Confirmed Status in kbd source package in Eoan: Confirmed Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Confirmed Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same: $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
** Description changed: + + (console-setup) + [Impact] + + * keyboard-configuration's postinst changes keyboard mode breaking X + keys. + + [Test Case] + + * Ssh to a system or open a terminal and unset DISPLAY + + $ echo $DISPLAY + + $ + + * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: +$ sudo kbd_mode +The keyboard is in some unknown mode +$ sudo kbd_mode +The keyboard is in raw (scancode) mode +$ + + * Install or reinstall kbd-configuration + +$ sudo apt install --reinstall keyboard-configuration +... +Setting up keyboard-configuration (1.178ubuntu11) ... +Your console font configuration will be updated the next time your system +boots. If you want to update it now, run 'setupcon' from a virtual console. +... + + * With the fixed package you should see the note above and the kbd mode + must stay the same: + +$ sudo kbd_mode +The keyboard is in raw (scancode) mode +$ + + * The unfixed package sets the kbd mode to unicode: + +$ sudo kbd_mode +The keyboard is in Unicode (UTF-8) mode +$ + + [Regression Potential] + + * The change may break debian-installer changing the keyboard mode, this should also be tested. + * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. + + [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: Confirmed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in console-setup source package in Cosmic: Confirmed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Status in console-setup source package in Disco: In Progress Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: Confirmed Status in kbd source package in Eoan: Confirmed Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Confirmed Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same: $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does
[Kernel-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
I also added kbd because I plan patching kbd_mode to perform only safe mode switches unless a new -f (force) option is passed. ** Also affects: kbd (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/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: Confirmed Status in kbd source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in console-setup source package in Cosmic: Confirmed Status in kbd source package in Cosmic: New Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Status in console-setup source package in Disco: In Progress Status in kbd source package in Disco: New Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: Confirmed Status in kbd source package in Eoan: New Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Confirmed Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816700] Re: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build
*** This bug is a duplicate of bug 1573508 *** https://bugs.launchpad.net/bugs/1573508 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1573508, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1573508 nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1816700 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: 111 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.4.0-143-generic Date: Fri Feb 15 10:55:29 2019 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-384/384.130/build/common/inc/nv-mm.h:44:9: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2019-01-15 (35 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageVersion: 384.130-0ubuntu0.16.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 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/nvidia-graphics-drivers-384/+bug/1816700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640181] Re: nvidia driver fails to build [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type]
*** This bug is a duplicate of bug 1573508 *** https://bugs.launchpad.net/bugs/1573508 ** This bug is no longer a duplicate of bug 1642241 nvidia-*: nvidia-* kernel module failed to build with kernel 4.9 [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type] ** This bug has been marked a duplicate of bug 1573508 nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640181 Title: nvidia driver fails to build [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type] Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: /var/lib/dkms/nvidia-370/370.28/build/nvidia/os-mlock.c:120:55: error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type [-Werror=incompatible-pointer-types] page_count, write, force, user_pages, NULL); ^~ - Can't go past the greeter loop with a nvidia driver. Compilation fails at dkms level. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.8.0-27-generic 4.8.0-27.29 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem1777 F pulseaudio /dev/snd/controlC0: oem1777 F pulseaudio CurrentDesktop: GNOME Date: Tue Nov 8 15:01:20 2016 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth1 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
@bhkolts Please just upgrade update-notifier-common. Timo's automated notification email referred to the source package from which both binary packages are built. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-notifier source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. [ Regression Potential ] If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. The fix is simple and was tested in several releases thus regressing in these ways is unlikely. [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
It looks like Brian can't do it either, but I uploaded the fix for update-notifier in Xenial. ** Description changed: + [Impact] + + The rationale behind the SRU to Xenial is that with latest unattended- + upgrades SRU it starts removing unused kernels, but all older kernels + are not removed in a single run. With update-notifier and u-u not fixed + they place /var/run/reboot-required asking for a reboot when it is not + needed. + + + [Test Case] + 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. + + [ Regression Potential ] + + If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. + The fix is simple and was tested in several releases thus regressing in these ways is unlikely. + + [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) - --- + --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: - linux-restricted-modules-3.13.0-53-generic N/A - linux-backports-modules-3.13.0-53-generic N/A - linux-firmware 1.127.12 + linux-restricted-modules-3.13.0-53-generic N/A + linux-backports-modules-3.13.0-53-generic N/A + linux-firmware 1.127.12 RfKill: - + Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: - + _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System
[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
No, I can't nominate it. :-) Brian, could you please do nominate this for u-n in 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
@bhkolts: Thank you for your feedback. Linux-image- extra-4.4.0-138-generic.postrm still runs /etc/kernel/postinst.d/update- notifier that places /var/run/reboot-required, the file u-u acts upon and reboots. Update-notifier is fixed in Bionic, but I'm hereby nominating the fix for 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1223241] Re: package linux-image-extra-3.8.0-30-generic 3.8.0-30.44 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
*** This bug is a duplicate of bug 1675079 *** https://bugs.launchpad.net/bugs/1675079 ** This bug is no longer a duplicate of bug 1357093 Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full ** This bug has been marked a duplicate of bug 1675079 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1223241 Title: package linux-image-extra-3.8.0-30-generic 3.8.0-30.44 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux package in Ubuntu: Incomplete Bug description: ? ProblemType: Package DistroRelease: Ubuntu 13.04 Package: linux-image-extra-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-30.22-lowlatency 3.8.13.6 Uname: Linux 3.8.0-30-lowlatency i686 ApportVersion: 2.9.2-0ubuntu8.3 AptOrdering: linux-image-extra-3.8.0-30-generic: Configure linux-image-generic: Configure linux-generic: Configure Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hans 3561 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri Sep 6 22:04:11 2013 DuplicateSignature: package:linux-image-extra-3.8.0-30-generic:3.8.0-30.44:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=fe29c59d-ac58-437f-99e4-5e9ef9611597 MachineType: LENOVO 7666WJ5 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-30-lowlatency root=UUID=67e0b1b8-90e3-4c3c-9a9b-d42f21ad104b ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.00-13ubuntu3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-image-extra-3.8.0-30-generic 3.8.0-30.44 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to raring on 2013-08-11 (29 days ago) dmi.bios.date: 04/18/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETB2WW (2.12 ) dmi.board.name: 7666WJ5 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7NETB2WW(2.12):bd04/18/2008:svnLENOVO:pn7666WJ5:pvrThinkPadX61s:rvnLENOVO:rn7666WJ5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7666WJ5 dmi.product.version: ThinkPad X61s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1222690] Re: small /boot partition for full system encryption becomes full after 7 updates and leads to failures
*** This bug is a duplicate of bug 1675079 *** https://bugs.launchpad.net/bugs/1675079 ** This bug is no longer a duplicate of bug 1357093 Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full ** This bug has been marked a duplicate of bug 1675079 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1222690 Title: small /boot partition for full system encryption becomes full after 7 updates and leads to failures Status in linux package in Ubuntu: Confirmed Bug description: During installation with full system encryption, the Ubuntu installer creates an adequate /boot partition of around 100Mb. However, after 10 updates to linux-image over the next few months, along with the running of update-initramfs the /boot partition becomes full. This causes further linux-image kernel updates to fail. Additionally, there are (undiagnosed) edge cases where improper handling of out-of-disk-space conditions in update-initramfs and/or update-grub this leads to additional failures. (I fixed a computer yesterday where /boot ran out of space, which caused grub to fail, which ended with "No Operating System" being displayed by the EFI BIOS. I previously fixed a system where a trivial upgrade failed on account of historical kernels in /boot - not a system failure, but a user interface disaster for Aunt Tilly.) To prevent /boot from filling up, it would help if there was a limit to the number of historic kernel versions maintained. Older kernel versions are of interest to many developers, but having multiple revisions of kernels that are not used is not helpful for regular users. A possible solution would be to "expire" automatically installed /boot updates which are not in active use. A wilder approach would be to move the large kernel files from /boot to some garbage collection point in /var ... or maybe not. Allocating more space to be wasted in /boot doesn't seem like a good idea. The following workaround is published to remove all kernel versions except the current one: dpkg --get-selections | \ grep 'linux-image*' | \ awk '{print $1}' | \ egrep -v "linux-image-$(uname -r)|linux-image-generic" | \ while read n do apt-get -y remove $n done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 417734] Re: Old kernels are not removed and horribly clutter the system
*** This bug is a duplicate of bug 1675079 *** https://bugs.launchpad.net/bugs/1675079 ** This bug is no longer a duplicate of bug 1357093 Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full ** This bug has been marked a duplicate of bug 1675079 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/417734 Title: Old kernels are not removed and horribly clutter the system Status in computer-janitor package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Triaged Bug description: I've been bitten twice by this - old kernels are not removed, slow down dpkg and use tons of space. As an example: vasil@shrike:~$ wc -l /var/lib/dpkg/info/*2.6.28*list 5656 /var/lib/dpkg/info/linux-headers-2.6.28-15-generic.list 10357 /var/lib/dpkg/info/linux-headers-2.6.28-15.list 2609 /var/lib/dpkg/info/linux-image-2.6.28-15-generic.list 65 /var/lib/dpkg/info/linux-restricted-modules-2.6.28-15-generic.list 18687 total So, from about 120k installed files one kernel takes 18k - a few of them can already use as much files in the dpkg database as the rest of the installed packages. Ubuntu updates its kernel at least 5 times during the normal distribution life, and some of us have stuff running since the dawn of time, so this starts to become a really nasty slowdown... (and, there's also bug #414943, old kernels might be a really bad idea for some people) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/computer-janitor/+bug/417734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
*** This bug is a duplicate of bug 1778219 *** https://bugs.launchpad.net/bugs/1778219 Since this issue is marked as invalid for linux i'm setting it as a duplicate of the u-u bug where SRU-ing the fix is tracked. ** This bug has been marked a duplicate of bug 1778219 unattended-upgrades hangs on shutdown, leaves system in a broken state -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in unattended-upgrades source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in unattended-upgrades source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in unattended-upgrades source package in Cosmic: Fix Released Status in linux source package in Disco: Invalid Status in unattended-upgrades source package in Disco: Fix Released Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798706] Re: Incomplete linking with boost_regex
** Package changed: linux (Ubuntu) => gce-compute-image-packages (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/1798706 Title: Incomplete linking with boost_regex Status in gce-compute-image-packages package in Ubuntu: In Progress Bug description: SRU Justification = [Impact] oslogin fails on Xenial and Trusty. In auth.log we see: Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to dlopen(pam_oslogin_login.so): /lib/security/pam_oslogin_login.so: cannot open shared object file: No such file or directory Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: pam_oslogin_login.so Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to dlopen(pam_oslogin_admin.so): /lib/security/pam_oslogin_admin.so: cannot open shared object file: No such file or directory Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: pam_oslogin_admin.so The error message is a bit deceptive - PAM tries to load the module from the correct location, fails, and then tries the other location where it is missing. It then reports the missing error rather than the real error. symlink the module into both paths leads to a much more useful error message: Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to dlopen(pam_oslogin_login.so): /lib/security/pam_oslogin_login.so: undefined symbol: _ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE Oct 18 06:45:12 dja-202158 sshd[16554]: PAM adding faulty module: pam_oslogin_login.so Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to dlopen(pam_oslogin_admin.so): /lib/security/pam_oslogin_admin.so: undefined symbol: _ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE [Test case] - set up GCE VM - turn on oslogin - attempt to log in [Fix] debian/patches/0002-Set-LDFLAGS-at-the-end-of-the-c-command-line-right-b.patch re-orders the link flags to link boost_regex for oslogin. However, this didn't change the flags for PAM module linking. So fix that too. [Regression Potential] - fixes a regression - limited to oslogin, and how it is linked. [Other Notes] We still see a scary list of warnings when building, but they don't seem to have an impact on the common path: dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail13put_mem_blockEPv used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail14verify_optionsEjNS_15regex_constants12_match_flagsE used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZNK5boost9re_detail31cpp_regex_traits_implementationIcE17transform_primaryEPKcS4_ used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost13match_resultsIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISB_12maybe_assignERKSF_ used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost11basic_regexIcNS_12regex_traitsIcNS_16cpp_regex_traitsIcE9do_assignEPKcS7_j used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail19raise_runtime_errorERKSt13runtime_error used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZNK5boost9re_detail31cpp_regex_traits_implementationIcE9transformEPKcS4_ used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps:
[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb
Next time you can just ask for that, i already tested them by manually loading them to the installer from a pendrive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771823 Title: Please include ax88179_178a and r8152 modules in d-i udeb Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: r8152 is used in a thunderbolt-connected docking station and ax88179_178a by an external USB dongle. Despite having two nics connected i can't install Bionic. :-) This is probably a subset of the modules to be included when fixing LP: #1503218. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1771823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb
** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771823 Title: Please include ax88179_178a and r8152 modules in d-i udeb Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: r8152 is used in a thunderbolt-connected docking station and ax88179_178a by an external USB dongle. Despite having two nics connected i can't install Bionic. :-) This is probably a subset of the modules to be included when fixing LP: #1503218. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1771823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb
I'm wondering why not just adding the modules to the udebs, but I'm happy with this solution, too. ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => New ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => 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/1771823 Title: Please include ax88179_178a and r8152 modules in d-i udeb Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Cosmic: Incomplete Bug description: r8152 is used in a thunderbolt-connected docking station and ax88179_178a by an external USB dongle. Despite having two nics connected i can't install Bionic. :-) This is probably a subset of the modules to be included when fixing LP: #1503218. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1771823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb
Thanks, both devices worked with the kernel, I tested them by booting the kernel in qemu VM and redirecting the USB devices to the VM. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771823 Title: Please include ax88179_178a and r8152 modules in d-i udeb Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Cosmic: Incomplete Bug description: r8152 is used in a thunderbolt-connected docking station and ax88179_178a by an external USB dongle. Despite having two nics connected i can't install Bionic. :-) This is probably a subset of the modules to be included when fixing LP: #1503218. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1771823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value
@xnox markig procps as wontfix since the kernel fix seems to be sufficient. ** Changed in: procps (Ubuntu) Status: New => Won't Fix ** Changed in: procps (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: procps (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1717224 Title: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value Status in Ubuntu on IBM z Systems: Fix Released Status in kvm package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Status in procps package in Ubuntu: Won't Fix Status in linux source package in Xenial: Fix Released Status in procps source package in Xenial: Won't Fix Status in linux source package in Artful: Fix Released Status in procps source package in Artful: Won't Fix Bug description: Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with the following error: root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038 error: Failed to start domain zs93kag70038 error: internal error: process exited while connecting to monitor: 2017-07-26T01:48:26.352534Z qemu-kvm: -drive file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native: Could not open backing file: Could not set AIO state: Inappropriate ioctl for device The previous 17 guests started fine: root@zm93k8# virsh start zs93kag70020 Domain zs93kag70020 started root@zm93k8# virsh start zs93kag70021 Domain zs93kag70021 started . . root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036 Domain zs93kag70036 started We ended up fixing the issue by adding the following line to /etc/sysctl.conf : fs.aio-max-nr = 4194304 ... then, reload the sysctl config file: root@zm93k8:/etc# sysctl -p /etc/sysctl.conf fs.aio-max-nr = 4194304 Now, we're able to start more guests... root@zm93k8:/etc# virsh start zs93kag70036 Domain zs93kag70036 started The default value was originally set to 65535: root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr 65536 Note, we chose the 4194304 value, because this is what our KVM on System Z hypervisor ships as its default value. Eg. on our zKVM system: [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr 4194304 ubuntu@zm93k8:/etc$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial ubuntu@zm93k8:/etc$ ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version Version: 1:2.5+dfsg-5ubuntu10.8 Is something already documented for Ubuntu KVM users warning them about the low default value, and some guidance as to how to select an appropriate value? Also, would you consider increasing the default aio-max-nr value to something much higher, to accommodate significantly more virtual guests? Thanks! ---uname output--- ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux Machine Type = z14 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- See Problem Description. The problem was happening a week ago, so this may not reflect that activity. This file was collected on Aug 7, one week after we were hitting the problem. If I need to reproduce the problem and get fresh data, please let me know. /var/log/messages doesn't exist on this system, so I provided syslog output instead. All data have been collected too late after the problem was observed over a week ago. If you need me to reproduce the problem and get new data, please let me know. That's not a problem. Also, we would have to make special arrangements for login access to these systems. I'm happy to run traces and data collection for you as needed. If that's not sufficient, then we'll explore log in access for you. Thanks... - Scott G. I was able to successfully recreate the problem and captured / attached new debug docs. Recreate procedure: # Started out with no virtual guests running. ubuntu@zm93k8:/home/scottg$ virsh list IdName State # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in /etc/sysctl.conf ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf fs.aio-max-nr = 65536 ## sysctl -a shows: fs.aio-max-nr = 4194304 ## Reload sysctl. ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf fs.aio-max-nr = 65536 ubuntu@zm93k8:~$ ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr fs.aio-max-nr = 65536 ubuntu@zm93k8:~$
[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb
There is no need for logs, the modules are missing from the udeb ** 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/1771823 Title: Please include ax88179_178a and r8152 modules in d-i udeb Status in linux package in Ubuntu: Confirmed Bug description: r8152 is used in a thunderbolt-connected docking station and ax88179_178a by an external USB dongle. Despite having two nics connected i can't install Bionic. :-) This is probably a subset of the modules to be included when fixing LP: #1503218. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771823] [NEW] Please include ax88179_178a and r8152 modules in d-i udeb
Public bug reported: r8152 is used in a thunderbolt-connected docking station and ax88179_178a by an external USB dongle. Despite having two nics connected i can't install Bionic. :-) This is probably a subset of the modules to be included when fixing LP: #1503218. ** 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/1771823 Title: Please include ax88179_178a and r8152 modules in d-i udeb Status in linux package in Ubuntu: New Bug description: r8152 is used in a thunderbolt-connected docking station and ax88179_178a by an external USB dongle. Despite having two nics connected i can't install Bionic. :-) This is probably a subset of the modules to be included when fixing LP: #1503218. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp