[Kernel-packages] [Bug 1844201] Re: turbostat is over constrained by dependencies
** 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/1844201 Title: turbostat is over constrained by dependencies Status in linux package in Ubuntu: Confirmed Bug description: For processors on which it works, turbostat is a very very good diagnostic tool. For many upstream escalations, it is the preferred tool. However the Ubuntu implementation doesn't actually execute turbostat directly, but rather goes to some script with incredibly tight, and unnecessary, kernel version dependency checks. This makes it difficult when trying to help others when we want them to try a newer or older kernel, and often we have to get them to override this and use turbostat directly. While turbostat is part of the kernel source tree, it does not depend on the kernel version at all. Here is an excerpt from a recent e-mail [1] from the turbostat maintainer: > FWIW, > > The latest turbostat and x86_energy_perf_policy utilities > in the upstream kernel tree should always be backward compatible > with all old kernels. If that is EVER not the case, I want to know about it. > > Yes, I know that some distros ship old versions of these utilities built > out of their matching kernel tree snapshots. > Yes, applying upstream fixes to .stable for such distros is a good thing. > > However, the better solution for these particular utilities, is that they > simply always use upstream utilities -- even with old kernels. > > When somebody reports a problem and I need them to run these tools, > 100% of the time, I start by sending them the latest upstream version > to replace the old version shipped by the distro. I have been using turbostat for several years, minus the Ubuntu part, and never had a problem with any version of turbostat with any kernel. This bug report is to request the deletion of the dependency check for Ubuntu. I am not saying it always has to be the latest version, but it should not be crippled by the dependency check. [1] https://marc.info/?l=linux-pm=156770359620861=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844201] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1844201 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844201 Title: turbostat is over constrained by dependencies Status in linux package in Ubuntu: Incomplete Bug description: For processors on which it works, turbostat is a very very good diagnostic tool. For many upstream escalations, it is the preferred tool. However the Ubuntu implementation doesn't actually execute turbostat directly, but rather goes to some script with incredibly tight, and unnecessary, kernel version dependency checks. This makes it difficult when trying to help others when we want them to try a newer or older kernel, and often we have to get them to override this and use turbostat directly. While turbostat is part of the kernel source tree, it does not depend on the kernel version at all. Here is an excerpt from a recent e-mail [1] from the turbostat maintainer: > FWIW, > > The latest turbostat and x86_energy_perf_policy utilities > in the upstream kernel tree should always be backward compatible > with all old kernels. If that is EVER not the case, I want to know about it. > > Yes, I know that some distros ship old versions of these utilities built > out of their matching kernel tree snapshots. > Yes, applying upstream fixes to .stable for such distros is a good thing. > > However, the better solution for these particular utilities, is that they > simply always use upstream utilities -- even with old kernels. > > When somebody reports a problem and I need them to run these tools, > 100% of the time, I start by sending them the latest upstream version > to replace the old version shipped by the distro. I have been using turbostat for several years, minus the Ubuntu part, and never had a problem with any version of turbostat with any kernel. This bug report is to request the deletion of the dependency check for Ubuntu. I am not saying it always has to be the latest version, but it should not be crippled by the dependency check. [1] https://marc.info/?l=linux-pm=156770359620861=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844201] Re: turbostat is over constrained by dependencies
You do not need any logs for this bug report. ** Changed in: linux (Ubuntu) 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/1844201 Title: turbostat is over constrained by dependencies Status in linux package in Ubuntu: New Bug description: For processors on which it works, turbostat is a very very good diagnostic tool. For many upstream escalations, it is the preferred tool. However the Ubuntu implementation doesn't actually execute turbostat directly, but rather goes to some script with incredibly tight, and unnecessary, kernel version dependency checks. This makes it difficult when trying to help others when we want them to try a newer or older kernel, and often we have to get them to override this and use turbostat directly. While turbostat is part of the kernel source tree, it does not depend on the kernel version at all. Here is an excerpt from a recent e-mail [1] from the turbostat maintainer: > FWIW, > > The latest turbostat and x86_energy_perf_policy utilities > in the upstream kernel tree should always be backward compatible > with all old kernels. If that is EVER not the case, I want to know about it. > > Yes, I know that some distros ship old versions of these utilities built > out of their matching kernel tree snapshots. > Yes, applying upstream fixes to .stable for such distros is a good thing. > > However, the better solution for these particular utilities, is that they > simply always use upstream utilities -- even with old kernels. > > When somebody reports a problem and I need them to run these tools, > 100% of the time, I start by sending them the latest upstream version > to replace the old version shipped by the distro. I have been using turbostat for several years, minus the Ubuntu part, and never had a problem with any version of turbostat with any kernel. This bug report is to request the deletion of the dependency check for Ubuntu. I am not saying it always has to be the latest version, but it should not be crippled by the dependency check. [1] https://marc.info/?l=linux-pm=156770359620861=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
I also hit Fn-A, which I saw somewhere (sorry to not have the link) that would disable adaptive brightness. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Alright, here we go. I have the kernel listed above installed: Linux shadeball 5.2.0-9-generic #10~bfo110511 SMP Tue Jul 16 13:17:28 CST 2019 x86_64 x86_64 x86_64 GNU/Linux I then went into the Power settings and turned Dim Screen When Inactive to off, Blank Screen to Never and so far there have been basically no flickers. There may have been one or two, but I can't confirm that I saw them and cannot reproduce them. I have tried it both on AC power and on battery, and with success on both. Thank you so much! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844201] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1844201 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844201 Title: turbostat is over constrained by dependencies Status in linux package in Ubuntu: Incomplete Bug description: For processors on which it works, turbostat is a very very good diagnostic tool. For many upstream escalations, it is the preferred tool. However the Ubuntu implementation doesn't actually execute turbostat directly, but rather goes to some script with incredibly tight, and unnecessary, kernel version dependency checks. This makes it difficult when trying to help others when we want them to try a newer or older kernel, and often we have to get them to override this and use turbostat directly. While turbostat is part of the kernel source tree, it does not depend on the kernel version at all. Here is an excerpt from a recent e-mail [1] from the turbostat maintainer: > FWIW, > > The latest turbostat and x86_energy_perf_policy utilities > in the upstream kernel tree should always be backward compatible > with all old kernels. If that is EVER not the case, I want to know about it. > > Yes, I know that some distros ship old versions of these utilities built > out of their matching kernel tree snapshots. > Yes, applying upstream fixes to .stable for such distros is a good thing. > > However, the better solution for these particular utilities, is that they > simply always use upstream utilities -- even with old kernels. > > When somebody reports a problem and I need them to run these tools, > 100% of the time, I start by sending them the latest upstream version > to replace the old version shipped by the distro. I have been using turbostat for several years, minus the Ubuntu part, and never had a problem with any version of turbostat with any kernel. This bug report is to request the deletion of the dependency check for Ubuntu. I am not saying it always has to be the latest version, but it should not be crippled by the dependency check. [1] https://marc.info/?l=linux-pm=156770359620861=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844201] [NEW] turbostat is over constrained by dependencies
Public bug reported: For processors on which it works, turbostat is a very very good diagnostic tool. For many upstream escalations, it is the preferred tool. However the Ubuntu implementation doesn't actually execute turbostat directly, but rather goes to some script with incredibly tight, and unnecessary, kernel version dependency checks. This makes it difficult when trying to help others when we want them to try a newer or older kernel, and often we have to get them to override this and use turbostat directly. While turbostat is part of the kernel source tree, it does not depend on the kernel version at all. Here is an excerpt from a recent e-mail [1] from the turbostat maintainer: > FWIW, > > The latest turbostat and x86_energy_perf_policy utilities > in the upstream kernel tree should always be backward compatible > with all old kernels. If that is EVER not the case, I want to know about it. > > Yes, I know that some distros ship old versions of these utilities built > out of their matching kernel tree snapshots. > Yes, applying upstream fixes to .stable for such distros is a good thing. > > However, the better solution for these particular utilities, is that they > simply always use upstream utilities -- even with old kernels. > > When somebody reports a problem and I need them to run these tools, > 100% of the time, I start by sending them the latest upstream version > to replace the old version shipped by the distro. I have been using turbostat for several years, minus the Ubuntu part, and never had a problem with any version of turbostat with any kernel. This bug report is to request the deletion of the dependency check for Ubuntu. I am not saying it always has to be the latest version, but it should not be crippled by the dependency check. [1] https://marc.info/?l=linux-pm=156770359620861=2 ** 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/1844201 Title: turbostat is over constrained by dependencies Status in linux package in Ubuntu: New Bug description: For processors on which it works, turbostat is a very very good diagnostic tool. For many upstream escalations, it is the preferred tool. However the Ubuntu implementation doesn't actually execute turbostat directly, but rather goes to some script with incredibly tight, and unnecessary, kernel version dependency checks. This makes it difficult when trying to help others when we want them to try a newer or older kernel, and often we have to get them to override this and use turbostat directly. While turbostat is part of the kernel source tree, it does not depend on the kernel version at all. Here is an excerpt from a recent e-mail [1] from the turbostat maintainer: > FWIW, > > The latest turbostat and x86_energy_perf_policy utilities > in the upstream kernel tree should always be backward compatible > with all old kernels. If that is EVER not the case, I want to know about it. > > Yes, I know that some distros ship old versions of these utilities built > out of their matching kernel tree snapshots. > Yes, applying upstream fixes to .stable for such distros is a good thing. > > However, the better solution for these particular utilities, is that they > simply always use upstream utilities -- even with old kernels. > > When somebody reports a problem and I need them to run these tools, > 100% of the time, I start by sending them the latest upstream version > to replace the old version shipped by the distro. I have been using turbostat for several years, minus the Ubuntu part, and never had a problem with any version of turbostat with any kernel. This bug report is to request the deletion of the dependency check for Ubuntu. I am not saying it always has to be the latest version, but it should not be crippled by the dependency check. [1] https://marc.info/?l=linux-pm=156770359620861=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831899] Comment bridged from LTC Bugzilla
--- Comment From rjbr...@us.ibm.com 2019-09-16 16:29 EDT--- updated one system to 4.15.0-62.69-generic and we no longer get the crash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831899 Title: Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in kernel virtual address space Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: == Comment: #0 - Robert J. Brenneman - 2019-05-30 11:16:45 == ---Problem Description--- Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in virtual kernel address space Contact Information = rjbr...@us.ibm.com ---uname output--- Linux ECOS0018 4.15.0-50-generic #54-Ubuntu SMP Tue May 7 05:57:08 UTC 2019 s390x s390x s390x GNU/Linux Machine Type = z13 2964 NE1 ---System Hang--- z/VM took a VMDUMP and reIPLed (the attached and available dumps are Linux dumps) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- boot system, start jenkins, let it run a couple days Stack trace output: 05/29/19 13:24:06 Call Trace: 05/29/19 13:24:06 (?<0012b97a>? __tlb_remove_table+0x6a/0xd0) 05/29/19 13:24:06 ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70 05/29/19 13:24:06 ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570 05/29/19 13:24:06 ?<008e92d4>? __do_softirq+0x124/0x358 05/29/19 13:24:06 ?<00179d52>? irq_exit+0xba/0xd0 05/29/19 13:24:06 ?<0010c412>? do_IRQ+0x8a/0xb8 05/29/19 13:24:06 ?<008e87f0>? ext_int_handler+0x134/0x138 05/29/19 13:24:06 ?<00102cee>? enabled_wait+0x4e/0xe0 05/29/19 13:24:06 (?<1201>? 0x1201) 05/29/19 13:24:06 ?<0010303a>? arch_cpu_idle+0x32/0x48 05/29/19 13:24:06 ?<001c5ae8>? do_idle+0xe8/0x1a8 Oops output: 05/29/19 13:24:06 User process fault: interruption code 003b ilc:3 in libc-2.23.so?3ffaca0+185000? 05/29/19 13:24:06 Failing address: TEID: 0800 05/29/19 13:24:06 Fault in primary space mode while using user ASCE. 05/29/19 13:24:06 AS:000710b241c7 R3:0024 05/29/19 13:24:06 Unable to handle kernel pointer dereference in virtual kernel address space 05/29/19 13:24:06 Failing address: 03dbe000 TEID: 03dbe403 05/29/19 13:24:06 Fault in home space mode while using kernel ASCE. 05/29/19 13:24:06 AS:00ea8007 R3:0024 05/29/19 13:24:06 Oops: 003b ilc:3 ?#1? SMP 05/29/19 13:24:06 Modules linked in: veth xt_nat xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_con 05/29/19 13:24:06 ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 dasd_fba_mod dasd_eckd_mod sha1_s390 sha_common dasd_mod 05/29/19 13:24:06 CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.15.0-50-generic #54-Ubuntu 05/29/19 13:24:06 Hardware name: IBM 2964 NE1 798 (z/VM 6.4.0) 05/29/19 13:24:06 Krnl PSW : dcb002be 72762961 (__tlb_remove_table+0x56/0xd0) 05/29/19 13:24:06 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 05/29/19 13:24:06 Krnl GPRS: ffba 02b8 02b80003 00eacac8 05/29/19 13:24:06 ffba 00b9 0700 000a 05/29/19 13:24:06 0404c001 0007d2fb5c38 0007cf71fdf0 03dbe000 05/29/19 13:24:06 03dbe018 008fe740 0007cf71fd08 0007cf71fcd8 05/29/19 13:24:06 Krnl Code: 0012b956: ec2c002a027f clij %r2,2,12,12b9aa 05/29/19 13:24:06 0012b95c: ec26001d037e cij %r2,3,6,12b996 05/29/19 13:24:06#0012b962: 41c0b018 la %r12,24(%r11) 05/29/19 13:24:06>0012b966: e548b008 mvghi 8(%r11),0 05/29/19 13:24:06 0012b96c: a7390008 lghi %r3,8 05/29/19 13:24:06 0012b970: b904002b lgr %r2,%r11 05/29/19 13:24:06 0012b974: c0e5000e8f8a brasl %r14,2fd888 05/29/19 13:24:06 0012b97a: a718 lhi %r1,-1 05/29/19 13:24:06 Call Trace: 05/29/19 13:24:06 (?<0012b97a>? __tlb_remove_table+0x6a/0xd0) 05/29/19 13:24:06 ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70 05/29/19 13:24:06 ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570 05/29/19 13:24:06 ?<008e92d4>? __do_softirq+0x124/0x358 05/29/19 13:24:06 ?<00179d52>? irq_exit+0xba/0xd0 05/29/19 13:24:06 ?<0010c412>?
[Kernel-packages] [Bug 1843644] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1843644 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1843644 Title: touchpad not working on LHMZNIY Yepbook Status in linux package in Ubuntu: Incomplete Bug description: Fresh install, but the touchpad isn't showing in the device list at all.And it perfectly work on Windows. Device list attached. Works ok if you attach a mouse. ProblemType: Bug Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-27-generic 5.0.0-27.28~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 21:40:32 2019 InstallationDate: Installed on 2019-09-10 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843644] Re: touchpad not working on LHMZNIY Yepbook
** Package changed: linux-signed-hwe (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/1843644 Title: touchpad not working on LHMZNIY Yepbook Status in linux package in Ubuntu: New Bug description: Fresh install, but the touchpad isn't showing in the device list at all.And it perfectly work on Windows. Device list attached. Works ok if you attach a mouse. ProblemType: Bug Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-27-generic 5.0.0-27.28~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 21:40:32 2019 InstallationDate: Installed on 2019-09-10 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools
Hi Juerg! This is a step towards what we want, but ideally it would be nice to have an unversioned package (like linux-tools-dev) that would ship some symlinks in /usr/include and /usr/lib, so that we don’t need to pass -I and -L to gcc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1215411 Title: libcpupower.so is not installed from linux-tools Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: Invalid Status in linux source package in Eoan: In Progress Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843644] [NEW] touchpad not working on LHMZNIY Yepbook
You have been subscribed to a public bug: Fresh install, but the touchpad isn't showing in the device list at all.And it perfectly work on Windows. Device list attached. Works ok if you attach a mouse. ProblemType: Bug Description:Ubuntu 18.04.3 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-27-generic 5.0.0-27.28~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 21:40:32 2019 InstallationDate: Installed on 2019-09-10 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- touchpad not working on LHMZNIY Yepbook https://bugs.launchpad.net/bugs/1843644 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844186] Re: [regression] NoNewPrivileges incompatible with Apparmor
** Description changed: Description: Host: Bionic 64 bit with GA kernel (4.15) Container: Bionic 64 bit The container runs a binary (/usr/sbin/nsd) locked by an Apparmor profile. The systemd service is configured with NoNewPrivileges=yes. # systemctl show nsd | grep ^NoNew NoNewPrivileges=yes This setup worked fine with 4.15.0-58-generic and before but stopped working with the 4.15.0-60-generic update. When running the bogus kernel, starting the nsd service fails and the following is logged in the host's dmesg: audit: type=1400 audit(1568387834.381:73): apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="lxd-ns0_" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="lxd-ns0_//&:lxd-ns0_:/usr/sbin/nsd" audit: type=1400 audit(1568387834.381:74): apparmor="DENIED" operation="exec" info="no new privs" error=-1 namespace="root//lxd-ns0_" profile="unconfined" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="/usr/sbin/nsd" Disabling the Apparmor profile OR setting NoNewPrivileges=no in the container makes it work again. I check with a couple of kernels: 4.15.0-52-generic works 4.15.0-58-generic works 4.15.0-60-generic is broken The 5.0 HWE kernel has always been broken it seems: 5.0.0-15-generic is broken 5.0.0-17-generic is broken 5.0.0-20-generic is broken 5.0.0-23-generic is broken 5.0.0-25-generic is broken 5.0.0-27-generic is broken - - I have another similar setup but using Xenial host/container and it broke in a similar fashion where 4.4.0-159-generic works but where 4.4.0-161-generic is broken. - + I have another similar setup but using Xenial host/container and it + broke in a similar fashion where 4.4.0-159-generic works but + 4.4.0-161-generic is broken. Additional information: # lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 # apt-cache policy nsd nsd: Installed: 4.1.26-1ubuntu0.18.04.1~ppa2 Candidate: 4.1.26-1ubuntu0.18.04.1~ppa2 Version table: *** 4.1.26-1ubuntu0.18.04.1~ppa2 500 500 http://ppa.launchpad.net/sdeziel.info/infra/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 4.1.17-1build1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages nsd comes from a custom backport this should be irrelevant. nsd's custom Apparmor profile: https://paste.ubuntu.com/p/BB3ZYzH8WQ/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 16 18:02 seq crw-rw 1 root audio 116, 33 Sep 16 18:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 16 18:14:02 2019 InstallationDate: Installed on 2019-08-22 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. Inspiron 530s PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=7c11931f-ee1e-4d07-bc03-d167b9c39ef0 ro apt-setup/restricted=false apt-setup/multiverse=false kaslr nmi_watchdog=0 nr_cpus=2 pti=on vsyscall=none RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.18 dmi.board.name: 0RY007 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.18:bd02/24/2009:svnDellInc.:pnInspiron530s:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530s dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1844166] Re: linux-aws: update EFA driver to version 1.4.0
** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Disco) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Disco) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1844166 Title: linux-aws: update EFA driver to version 1.4.0 Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Xenial: In Progress Status in linux-aws source package in Bionic: In Progress Status in linux-aws source package in Disco: In Progress Bug description: Update drivers/infiniband/hw/efa to upstream driver version 1.4.0 from https://github.com/amzn/amzn-drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1844166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844186] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844186 Title: [regression] NoNewPrivileges incompatible with Apparmor Status in linux package in Ubuntu: Confirmed Bug description: Description: Host: Bionic 64 bit with GA kernel (4.15) Container: Bionic 64 bit The container runs a binary (/usr/sbin/nsd) locked by an Apparmor profile. The systemd service is configured with NoNewPrivileges=yes. # systemctl show nsd | grep ^NoNew NoNewPrivileges=yes This setup worked fine with 4.15.0-58-generic and before but stopped working with the 4.15.0-60-generic update. When running the bogus kernel, starting the nsd service fails and the following is logged in the host's dmesg: audit: type=1400 audit(1568387834.381:73): apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="lxd-ns0_" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="lxd-ns0_//&:lxd-ns0_:/usr/sbin/nsd" audit: type=1400 audit(1568387834.381:74): apparmor="DENIED" operation="exec" info="no new privs" error=-1 namespace="root//lxd-ns0_" profile="unconfined" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="/usr/sbin/nsd" Disabling the Apparmor profile OR setting NoNewPrivileges=no in the container makes it work again. I check with a couple of kernels: 4.15.0-52-generic works 4.15.0-58-generic works 4.15.0-60-generic is broken The 5.0 HWE kernel has always been broken it seems: 5.0.0-15-generic is broken 5.0.0-17-generic is broken 5.0.0-20-generic is broken 5.0.0-23-generic is broken 5.0.0-25-generic is broken 5.0.0-27-generic is broken I have another similar setup but using Xenial host/container and it broke in a similar fashion where 4.4.0-159-generic works but where 4.4.0-161-generic is broken. Additional information: # lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 # apt-cache policy nsd nsd: Installed: 4.1.26-1ubuntu0.18.04.1~ppa2 Candidate: 4.1.26-1ubuntu0.18.04.1~ppa2 Version table: *** 4.1.26-1ubuntu0.18.04.1~ppa2 500 500 http://ppa.launchpad.net/sdeziel.info/infra/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 4.1.17-1build1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages nsd comes from a custom backport this should be irrelevant. nsd's custom Apparmor profile: https://paste.ubuntu.com/p/BB3ZYzH8WQ/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 16 18:02 seq crw-rw 1 root audio 116, 33 Sep 16 18:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 16 18:14:02 2019 InstallationDate: Installed on 2019-08-22 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. Inspiron 530s PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=7c11931f-ee1e-4d07-bc03-d167b9c39ef0 ro apt-setup/restricted=false apt-setup/multiverse=false kaslr nmi_watchdog=0 nr_cpus=2 pti=on vsyscall=none RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.18 dmi.board.name: 0RY007 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.18:bd02/24/2009:svnDellInc.:pnInspiron530s:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530s dmi.sys.vendor:
[Kernel-packages] [Bug 1844186] Re: [regression] NoNewPrivileges incompatible with Apparmor
** Description changed: Description: Host: Bionic 64 bit with GA kernel (4.15) Container: Bionic 64 bit The container runs a binary (/usr/sbin/nsd) locked by an Apparmor profile. The systemd service is configured with NoNewPrivileges=yes. - # systemctl show nsd | grep ^NoNew - NoNewPrivileges=yes + # systemctl show nsd | grep ^NoNew + NoNewPrivileges=yes This setup worked fine with 4.15.0-58-generic and before but stopped working with the 4.15.0-60-generic update. When running the bogus kernel, starting the nsd service fails and the following is logged in the host's dmesg: audit: type=1400 audit(1568387834.381:73): apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="lxd-ns0_" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="lxd-ns0_//&:lxd-ns0_:/usr/sbin/nsd" audit: type=1400 audit(1568387834.381:74): apparmor="DENIED" operation="exec" info="no new privs" error=-1 namespace="root//lxd-ns0_" profile="unconfined" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="/usr/sbin/nsd" Disabling the Apparmor profile OR setting NoNewPrivileges=no in the container makes it work again. I check with a couple of kernels: 4.15.0-52-generic works 4.15.0-58-generic works 4.15.0-60-generic is broken The 5.0 HWE kernel has always been broken it seems: 5.0.0-15-generic is broken 5.0.0-17-generic is broken 5.0.0-20-generic is broken 5.0.0-23-generic is broken 5.0.0-25-generic is broken 5.0.0-27-generic is broken + I have another similar setup but using Xenial host/container and it broke in a similar fashion where 4.4.0-159-generic works but where 4.4.0-161-generic is broken. + + Additional information: # lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 # apt-cache policy nsd nsd: - Installed: 4.1.26-1ubuntu0.18.04.1~ppa2 - Candidate: 4.1.26-1ubuntu0.18.04.1~ppa2 - Version table: - *** 4.1.26-1ubuntu0.18.04.1~ppa2 500 - 500 http://ppa.launchpad.net/sdeziel.info/infra/ubuntu bionic/main amd64 Packages - 100 /var/lib/dpkg/status - 4.1.17-1build1 500 - 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages + Installed: 4.1.26-1ubuntu0.18.04.1~ppa2 + Candidate: 4.1.26-1ubuntu0.18.04.1~ppa2 + Version table: + *** 4.1.26-1ubuntu0.18.04.1~ppa2 500 + 500 http://ppa.launchpad.net/sdeziel.info/infra/ubuntu bionic/main amd64 Packages + 100 /var/lib/dpkg/status + 4.1.17-1build1 500 + 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages nsd comes from a custom backport this should be irrelevant. nsd's custom Apparmor profile: https://paste.ubuntu.com/p/BB3ZYzH8WQ/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Sep 16 18:02 seq - crw-rw 1 root audio 116, 33 Sep 16 18:02 timer + total 0 + crw-rw 1 root audio 116, 1 Sep 16 18:02 seq + crw-rw 1 root audio 116, 33 Sep 16 18:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 16 18:14:02 2019 InstallationDate: Installed on 2019-08-22 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. Inspiron 530s PciMultimedia: - + ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash - TERM=xterm-256color - PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=7c11931f-ee1e-4d07-bc03-d167b9c39ef0 ro apt-setup/restricted=false apt-setup/multiverse=false kaslr nmi_watchdog=0 nr_cpus=2 pti=on vsyscall=none RelatedPackageVersions: - linux-restricted-modules-5.0.0-27-generic N/A - linux-backports-modules-5.0.0-27-generic N/A - linux-firmware1.173.9 + linux-restricted-modules-5.0.0-27-generic N/A + linux-backports-modules-5.0.0-27-generic N/A + linux-firmware1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux
[Kernel-packages] [Bug 1844186] [NEW] [regression] NoNewPrivileges incompatible with Apparmor
Public bug reported: Description: Host: Bionic 64 bit with GA kernel (4.15) Container: Bionic 64 bit The container runs a binary (/usr/sbin/nsd) locked by an Apparmor profile. The systemd service is configured with NoNewPrivileges=yes. # systemctl show nsd | grep ^NoNew NoNewPrivileges=yes This setup worked fine with 4.15.0-58-generic and before but stopped working with the 4.15.0-60-generic update. When running the bogus kernel, starting the nsd service fails and the following is logged in the host's dmesg: audit: type=1400 audit(1568387834.381:73): apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="lxd-ns0_" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="lxd-ns0_//&:lxd-ns0_:/usr/sbin/nsd" audit: type=1400 audit(1568387834.381:74): apparmor="DENIED" operation="exec" info="no new privs" error=-1 namespace="root//lxd-ns0_" profile="unconfined" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="/usr/sbin/nsd" Disabling the Apparmor profile OR setting NoNewPrivileges=no in the container makes it work again. I check with a couple of kernels: 4.15.0-52-generic works 4.15.0-58-generic works 4.15.0-60-generic is broken The 5.0 HWE kernel has always been broken it seems: 5.0.0-15-generic is broken 5.0.0-17-generic is broken 5.0.0-20-generic is broken 5.0.0-23-generic is broken 5.0.0-25-generic is broken 5.0.0-27-generic is broken I have another similar setup but using Xenial host/container and it broke in a similar fashion where 4.4.0-159-generic works but where 4.4.0-161-generic is broken. Additional information: # lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 # apt-cache policy nsd nsd: Installed: 4.1.26-1ubuntu0.18.04.1~ppa2 Candidate: 4.1.26-1ubuntu0.18.04.1~ppa2 Version table: *** 4.1.26-1ubuntu0.18.04.1~ppa2 500 500 http://ppa.launchpad.net/sdeziel.info/infra/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 4.1.17-1build1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages nsd comes from a custom backport this should be irrelevant. nsd's custom Apparmor profile: https://paste.ubuntu.com/p/BB3ZYzH8WQ/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 16 18:02 seq crw-rw 1 root audio 116, 33 Sep 16 18:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 16 18:14:02 2019 InstallationDate: Installed on 2019-08-22 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. Inspiron 530s PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=7c11931f-ee1e-4d07-bc03-d167b9c39ef0 ro apt-setup/restricted=false apt-setup/multiverse=false kaslr nmi_watchdog=0 nr_cpus=2 pti=on vsyscall=none RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.18 dmi.board.name: 0RY007 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.18:bd02/24/2009:svnDellInc.:pnInspiron530s:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530s dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic ** Summary changed: - [regression] NoNewPrivileges breaks Apparmor + [regression] NoNewPrivileges incompatible with Apparmor -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844186 Title: [regression] NoNewPrivileges incompatible with Apparmor Status in linux package in Ubuntu: Confirmed Bug
[Kernel-packages] [Bug 1831482] Re: VIMC module not available (CONFIG_VIDEO_VIMC not set)
Tested on bionic proposed kernel by manually installing the dpkgs. modprobe vim2m modprobe vivid modprobe vimc kbingham@Q:$ uname -a Linux Q 4.15.0-63-generic #72-Ubuntu SMP Fri Sep 6 10:12:25 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux kbingham@Q:$ lsv4l2 video0: HP Wide Vision FHD Camera: HP W video1: HP Wide Vision FHD Camera: HP I video2: Raw Capture 0 video3: Raw Capture 1 video4: RGB/YUV Capture video5: vivid-000-vid-cap video6: vivid-000-vid-out video7: vim2m ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831482 Title: VIMC module not available (CONFIG_VIDEO_VIMC not set) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: == SRU Justification == VIMC is a virtual media controller that can emulate a real media device. This is useful for automated tests, and development of multimedia frameworks. == Fix == Enable VIMC as a module in B/D/E kernel configs. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1831482-cfg-vimc/ User has reported that the Eoan kernel works as expected. I have also smoke tested the B/D kernel to make sure the VIMC modules can be loaded properly. == Regression Potential == Low, this patchset enables the VIMC module support, we might see some bug reports against this module in the future. However the acutal impact for a non-vimc user should be minimum. There is a null pointer deference issue was found while inserting the vimc module on some system (lp:1840028), it will be handled in that bug. == Original Bug report == The Multimedia VIMC module provides a test interface for the linux-media media controller framework. This is useful for automated tests, and development of multimedia frameworks. Other components similar to this such as VIVID (CONFIG_VIDEO_VIVID=m) are enabled, but VIMC is missing from the linux-modules packages: $ grep VIMC /boot/config-* /boot/config-4.15.0-32-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.17.9-041709-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.4-041804-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.7-041807-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-13-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-15-generic:# CONFIG_VIDEO_VIMC is not set Could this be enabled in future releases as a module please? I'm running Ubuntu 19.04, with Ubuntu 5.0.0-13.14-generic 5.0.6, however I believe this issue affects all current Ubuntu kernel releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844166] [NEW] linux-aws: update EFA driver to version 1.4.0
Public bug reported: Update drivers/infiniband/hw/efa to upstream driver version 1.4.0 from https://github.com/amzn/amzn-drivers ** Affects: linux-aws (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: 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/1844166 Title: linux-aws: update EFA driver to version 1.4.0 Status in linux-aws package in Ubuntu: In Progress Bug description: Update drivers/infiniband/hw/efa to upstream driver version 1.4.0 from https://github.com/amzn/amzn-drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1844166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
(In reply to txrx from comment #651) Typical Current Idle might not be working. Read the sensor output. If voltage is not higher than without enabling it, try to increase the core voltage. My Ryzen 7 1800X seems to not produce hangs since I upgraded to 1003ABB with an ASUS Crosshair VI Hero and enabled Typical current idle. > I was able to update my BIOS to version 18, but my system still locks up. > I tried the following with the new BIOS: > - use factory defaults > - disable SMT > - disable SMT with Typical Current Idle > - all of the above with SVM disabled/enabled > Right now I set the power supply idle control to "Low ..." and will report > back. > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago)
[Kernel-packages] [Bug 1844155] Re: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes
** Changed in: linux (Debian) Status: Unknown => 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/1844155 Title: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes Status in linux package in Ubuntu: Confirmed Status in linux package in Debian: Fix Released Bug description: This seems to have been fixed in 4.15 (finally), but is still an issue in the 4.4 kernel used on our builders, and possibly others as well (needs investigation). The original Debian bug report linked has more info, as well as the patchset on lkml at https://lkml.org/lkml/2018/7/25/409 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844153] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1844153/+attachment/5289064/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Opinion ** Changed in: linux (Ubuntu) Status: Opinion => 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/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruslan 1637 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-16 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Tags: bionic Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip
[Kernel-packages] [Bug 1844153] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1844153/+attachment/5289063/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruslan 1637 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-16 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Tags: bionic Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox
[Kernel-packages] [Bug 1844153] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1844153/+attachment/5289057/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruslan 1637 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-16 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Tags: bionic Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version:
[Kernel-packages] [Bug 1844153] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1844153/+attachment/5289058/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruslan 1637 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-16 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Tags: bionic Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH
[Kernel-packages] [Bug 1844153] Re: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot
apport information ** Tags added: apport-collected bionic ** Description changed: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ruslan 1637 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-09-16 (0 days ago) + InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + IwConfig: + lono wireless extensions. + + enp0s3no wireless extensions. + Lsusb: + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: innotek GmbH VirtualBox + Package: linux (not installed) + ProcFB: 0 vboxdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-27-generic N/A + linux-backports-modules-5.0.0-27-generic N/A + linux-firmware1.173.9 + RfKill: + + Tags: bionic + Uname: Linux 5.0.0-27-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/01/2006 + dmi.bios.vendor: innotek GmbH + dmi.bios.version: VirtualBox + dmi.board.name: VirtualBox + dmi.board.vendor: Oracle Corporation + dmi.board.version: 1.2 + dmi.chassis.type: 1 + dmi.chassis.vendor: Oracle Corporation + dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: +
[Kernel-packages] [Bug 1844153] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1844153/+attachment/5289059/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruslan 1637 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-16 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Tags: bionic Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version:
[Kernel-packages] [Bug 1844153] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1844153/+attachment/5289061/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruslan 1637 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-16 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Tags: bionic Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version:
[Kernel-packages] [Bug 1844153] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1844153/+attachment/5289054/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruslan 1637 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-16 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Tags: bionic Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox
[Kernel-packages] [Bug 1844153] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1844153/+attachment/5289055/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruslan 1637 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-16 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Tags: bionic Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH
[Kernel-packages] [Bug 1844153] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1844153/+attachment/5289056/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruslan 1637 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-16 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Tags: bionic Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox
[Kernel-packages] [Bug 1844153] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1844153/+attachment/5289060/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruslan 1637 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-16 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Tags: bionic Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH
[Kernel-packages] [Bug 1844153] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1844153/+attachment/5289062/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruslan 1637 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-16 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Tags: bionic Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version:
[Kernel-packages] [Bug 1829991] Re: zram01 from kernel_misc test suite in LTP failed
** Tags added: ubuntu-ltp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829991 Title: zram01 from kernel_misc test suite in LTP failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Bug description: startup='Wed May 22 07:02:19 2019' zram01 1 TINFO: create '4' zram device(s) zram01 1 TPASS: test succeeded zram01 2 TCONF: The device attribute max_comp_streams was introduced in kernel 3.15 and deprecated in 4.7 zram01 2 TINFO: test that we can set compression algorithm /opt/ltp/testcases/bin/zram01.sh: 101: local: 842: bad variable name tag=zram01 stime=1558508539 dur=0 exit=exited stat=2 core=no cu=0 cs=1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-20-generic 4.18.0-20.21 ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 06:28 seq crw-rw 1 root audio 116, 33 May 22 06:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 07:21:09 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-20-generic N/A linux-backports-modules-4.18.0-20-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829359] Re: TRACE_syscall.ptrace_syscall_errno in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC
** Tags added: ubuntu-kernel-selftests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829359 Title: TRACE_syscall.ptrace_syscall_errno in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: This test will fail on Bionic / Cosmic PowerPC: [ RUN ] TRACE_syscall.ptrace_syscall_errno seccomp_bpf.c:1826:TRACE_syscall.ptrace_syscall_errno:Expected -(-3) (3) == (*__errno_location ()) (38) TRACE_syscall.ptrace_syscall_errno: Test failed at step #13 This test will pass on PowerPC with Disco kernel. As this issue can be reproduced with the upsteam kernel tree, so it looks like a kernel issue instead of a test case issue to me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-20-generic 4.18.0-20.21~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el Date: Thu May 16 09:48:18 2019 ProcLoadAvg: 0.38 0.64 0.48 1/1316 6114 ProcLocks: 1: POSIX ADVISORY WRITE 1767 00:17:402 0 EOF 2: POSIX ADVISORY WRITE 3941 00:17:825 0 EOF 3: FLOCK ADVISORY WRITE 3492 00:17:390 0 EOF 4: FLOCK ADVISORY WRITE 3947 00:17:820 0 EOF 5: POSIX ADVISORY WRITE 3872 00:17:799 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.18.0-20-generic (buildd@bos02-ppc64el-019) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21~18.04.1-Ubuntu SMP Wed May 8 08:51:08 UTC 2019 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 159) max: 3.695 GHz (cpu 1) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829363] Re: TRACE_syscall.ptrace_syscall_faked in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC
** Tags added: ubuntu-kernel-selftests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829363 Title: TRACE_syscall.ptrace_syscall_faked in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: This test will fail on Bionic / Cosmic PowerPC: [ RUN ] TRACE_syscall.ptrace_syscall_faked seccomp_bpf.c:1837:TRACE_syscall.ptrace_syscall_faked:Expected 45000 (45000) == syscall(207) (18446744073709551615) TRACE_syscall.ptrace_syscall_faked: Test failed at step #13 [ FAIL ] TRACE_syscall.ptrace_syscall_faked This test will pass on PowerPC with Disco kernel. As this issue can be reproduced with the upsteam kernel tree, so it looks like a kernel issue instead of a test case issue to me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-20-generic 4.18.0-20.21~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el Date: Thu May 16 09:59:19 2019 ProcLoadAvg: 0.07 0.40 0.68 1/1315 7583 ProcLocks: 1: POSIX ADVISORY WRITE 1767 00:17:402 0 EOF 2: POSIX ADVISORY WRITE 3941 00:17:825 0 EOF 3: FLOCK ADVISORY WRITE 3492 00:17:390 0 EOF 4: FLOCK ADVISORY WRITE 3947 00:17:820 0 EOF 5: POSIX ADVISORY WRITE 3872 00:17:799 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.18.0-20-generic (buildd@bos02-ppc64el-019) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21~18.04.1-Ubuntu SMP Wed May 8 08:51:08 UTC 2019 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 159) max: 3.695 GHz (cpu 0) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed with B
** Tags added: ubuntu-ltp ** Tags added: 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/1829849 Title: proc01 in fs from ubuntu_ltp failed with B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 17 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 18 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 19 TFAIL :
[Kernel-packages] [Bug 1828165] Re: gicv2-mmio in ubuntu_kvm_unit_tests failed on X ARM64 Moonshot
** Tags added: ubuntu-kvm-unit-tests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828165 Title: gicv2-mmio in ubuntu_kvm_unit_tests failed on X ARM64 Moonshot Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: This test passed with X-HWE on ARM64 Moonshot: TESTNAME=gicv2-mmio TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'mmio' PASS gicv2-mmio (17 tests, 1 skipped) So this feels like a kernel issue to me. # MAX_SMP=8 # TESTNAME=gicv2-mmio TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'mmio' timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/gic.flat -smp 8 -machine gic-version=2 -append mmio # -initrd /tmp/tmp.OlzPYOZSZn INFO: gicv2: mmio: number of implemented SPIs: 256 PASS: gicv2: mmio: all 8 CPUs have interrupts INFO: gicv2: mmio: IIDR: 0x4b00043b PASS: gicv2: mmio: GICD_TYPER is read-only PASS: gicv2: mmio: GICD_IIDR is read-only PASS: gicv2: mmio: ICPIDR2 is read-only (0x) PASS: gicv2: mmio: IPRIORITYR: consistent priority masking (0x) PASS: gicv2: mmio: IPRIORITYR: implements at least 4 priority bits (8) PASS: gicv2: mmio: IPRIORITYR: clearing priorities PASS: gicv2: mmio: IPRIORITYR: accesses beyond limit RAZ/WI PASS: gicv2: mmio: IPRIORITYR: accessing last SPIs PASS: gicv2: mmio: IPRIORITYR: priorities are preserved PASS: gicv2: mmio: IPRIORITYR: byte reads successful (0xff7fbf3f => 0xbf) PASS: gicv2: mmio: IPRIORITYR: byte writes successful (0x1f => 0xff1fbf3f) SKIP: gicv2: mmio: ITARGETSR: CPU masking (all CPUs implemented) PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI FAIL: gicv2: mmio: ITARGETSR: register content preserved (0103020f => 01010201) PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x0103020f => 0x02) FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x01010201) SUMMARY: 17 tests, 2 unexpected failures, 1 skipped ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-146-generic 4.4.0-146.172 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 8 02:17 seq crw-rw 1 root audio 116, 33 May 8 02:17 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed May 8 06:36:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828380] Re: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes failed on D i386
** Tags added: ubuntu-btrfs-kernel-fixes -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828380 Title: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes failed on D i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Confirmed Bug description: Test failed with: btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43 Test log: * Command: BINDIR=/home/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes /home /ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes/ubuntu_btrfs_kerne l_fixes.sh /home/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes/fi xes/f88ba6a2a44ee98e8d59654463dc157bb6d13c43.sh 2>&1 Exit status: 1 Duration: 11.0287649632 stdout: Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43 Btrfs: skip submitting barrier for missing device I got an error on v3.13: BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO failure (errors while submitting device barriers.) how to reproduce: > mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2 > wipefs -a /dev/sdf2 > mount -o degraded /dev/sdf1 /mnt > btrfs balance start -f -sconvert=single -mconvert=single -dconvert=single /mnt The reason of the error is that barrier_all_devices() failed to submit barrier to the missing device. However it is clear that we cannot do anything on missing device, and also it is not necessary to care chunks on the missing device. This patch stops sending/waiting barrier if device is missing. btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43 FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1) Syslog: kernel: [ 1531.598180] Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 kernel: [ 1531.822544] BTRFS: device fsid 28683721-4c7a-4922-a753-e61ca95c0726 devid 1 transid 5 /dev/loop2 kernel: [ 1531.917840] BTRFS: device fsid 28683721-4c7a-4922-a753-e61ca95c0726 devid 2 transid 5 /dev/loop3 kernel: [ 1532.314274] BTRFS info (device loop2): allowing degraded mounts kernel: [ 1532.314276] BTRFS info (device loop2): disk space caching is enabled kernel: [ 1532.314277] BTRFS info (device loop2): has skinny extents kernel: [ 1532.314278] BTRFS info (device loop2): flagging fs with big metadata feature kernel: [ 1532.315442] BTRFS warning (device loop2): devid 2 uuid b6fe3a66-6a6d-42fe-9b57-5373a2f8d014 is missing kernel: [ 1532.315882] BTRFS info (device loop2): checking UUID tree kernel: [ 1532.319154] BTRFS error (device loop2): balance: invalid convert data profile single systemd[965]: tmp-mnt\x2df88ba6a2a44ee98e8d59654463dc157bb6d13c43.mount: Succeeded. systemd[1]: tmp-mnt\x2df88ba6a2a44ee98e8d59654463dc157bb6d13c43.mount: Succeeded. kernel: [ 1532.524774] Test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 returned 0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:31 seq crw-rw 1 root audio 116, 33 May 9 09:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu May 9 09:33:18 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc.
[Kernel-packages] [Bug 1828796] Re: ubuntu_ftrace_smoke_test failed on T-4.4 AWS node i3en
** Tags added: ubuntu-ftrace-smoke-test ** Tags added: aws ** Tags added: 4.4 trusty -- 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/1828796 Title: ubuntu_ftrace_smoke_test failed on T-4.4 AWS node i3en Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Bug description: This issue was only spotted on this instance, test passed on other instances: FAILED (SyS_write or ksys_write traces found must be > 32, got 27) Reproduce rate: 4/4 stdout: PASSED (CONFIG_FUNCTION_TRACER=y in /boot/config-4.4.0-1043-aws) PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in /boot/config-4.4.0-1043-aws) PASSED (CONFIG_STACK_TRACER=y in /boot/config-4.4.0-1043-aws) PASSED (CONFIG_DYNAMIC_FTRACE=y in /boot/config-4.4.0-1043-aws) PASSED all expected /sys/kernel/debug/tracing files exist PASSED (function_graph in /sys/kernel/debug/tracing/available_tracers) PASSED (function in /sys/kernel/debug/tracing/available_tracers) PASSED (nop in /sys/kernel/debug/tracing/available_tracers) PASSED (function can be enabled) FAILED (SyS_write or ksys_write traces found must be > 32, got 27) PASSED (function_graph can be enabled) PASSED (vfs_write traces found must be > 32, got 180104) PASSED (tracer blk can be enabled (got 2 lines of tracing output)) PASSED (tracer mmiotrace can be enabled (got 11 lines of tracing output)) PASSED (tracer function_graph can be enabled (got 124685 lines of tracing output)) PASSED (tracer wakeup_dl can be enabled (got 2 lines of tracing output)) PASSED (tracer wakeup_rt can be enabled (got 81 lines of tracing output)) PASSED (tracer wakeup can be enabled (got 45 lines of tracing output)) PASSED (tracer function can be enabled (got 118968 lines of tracing output)) Summary: 18 passed, 1 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828545] Re: psci in ubuntu_kvm_unit_tests failed with Disco ARM64
** Tags added: ubuntu-kvm-unit-tests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828545 Title: psci in ubuntu_kvm_unit_tests failed with Disco ARM64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: TESTNAME=psci TIMEOUT=90s ACCEL= ./arm/run arm/psci.flat -smp $MAX_SMP FAIL psci (4 tests, 1 unexpected failures) # MAX_SMP=48 # TESTNAME=psci TIMEOUT=90s ACCEL= ./arm/run arm/psci.flat -smp $MAX_SMP timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/psci.flat -smp 48 # -initrd /tmp/tmp.XqPOvHgIuL INFO: PSCI version 1.0 PASS: invalid-function PASS: affinity-info-on PASS: affinity-info-off INFO: unexpected cpu_on return value: caller=CPU46, ret=-2 FAIL: cpu-on SUMMARY: 4 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 08:43 seq crw-rw 1 root audio 116, 33 May 9 08:43 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri May 10 11:31:36 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Cavium ThunderX CRB PciMultimedia: ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 0 dmi.chassis.vendor: Cavium dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: ThunderX CRB dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Cavium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Hello Same issue with purple screen when login screen should be displayed. By adding nomodeset to the Linux kernel line in Grub I was able to get to the login screen. But now I am just left at the purple screen once I have entered my login credentials and pressed enter. I have checked for BIOS update, none available. I am on a Dell Inspiron 7720. Moving the mouse on the login screen is also very sluggish. Regards Jason -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 WORKAROUND 3: upgrade BIOS Asus has released updated BIOSes, which probably include the newest microcode. After upgrading workarounds 1,2 are not needed. Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be (easily) reverted. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1828391] Re: xfstests failed to build on Cosmic/Disco
** Tags added: xfstests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828391 Title: xfstests failed to build on Cosmic/Disco Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: This issue was addressed before in bug 1802486 But it's failing again now, looks like something wrong in the upstream repo: ./configure: line 8704: test: $(SHELL): binary operator expected Please find the attachment for the build log. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 08:43 seq crw-rw 1 root audio 116, 33 May 9 08:43 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu May 9 11:05:42 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Cavium ThunderX CRB PciMultimedia: ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 0 dmi.chassis.vendor: Cavium dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: ThunderX CRB dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Cavium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824136] Re: ubuntu_k8s_unit_tests failed with GCP
** Tags added: ubuntu-k8s-unit-tests
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1824136
Title:
ubuntu_k8s_unit_tests failed with GCP
Status in ubuntu-kernel-tests:
Confirmed
Status in linux-signed-gcp package in Ubuntu:
New
Bug description:
There are 3 failures found on Cosmic GCP (n1-highcpu-16)
* k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler
* k8s.io/kubernetes/pkg/master
* k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/httpstream/spdy
[build failed]
Steps to reproduce:
sudo apt-get install git python-minimal python-yaml gdb -y
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local
--verbose autotest/client/tests/ubuntu_k8s_unit_tests/control
Error messages:
* k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler
--- FAIL: TestUpdateNodeWithMultiplePods (2.56s)
taint_manager_test.go:486: Starting testcase "Pods with different toleration
times are evicted appropriately"
taint_manager_test.go:512: Sleeping for 499.999448ms
taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:538: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:512: Sleeping for 594.563805ms
taint_manager_test.go:532: Failed to deleted pod pod2 after 0
taint_manager_test.go:486: Starting testcase "Evict all pods not matching
all taints instantly"
taint_manager_test.go:512: Sleeping for 499.999844ms
taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:538: Found not-delete action with verb list. Ignoring.
FAIL
FAIL k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler
35.544s
* k8s.io/kubernetes/pkg/master
2019-03-21 16:02:16.793715 I | integration: launching 2444030890339279063
(unix://localhost:24440308903392790630)
2019-03-21 16:02:16.798460 I | etcdserver: name = 2444030890339279063
2019-03-21 16:02:16.798550 I | etcdserver: data dir = /tmp/etcd396328703
2019-03-21 16:02:16.798566 I | etcdserver: member dir =
/tmp/etcd396328703/member
2019-03-21 16:02:16.798576 I | etcdserver: heartbeat = 10ms
2019-03-21 16:02:16.798585 I | etcdserver: election = 100ms
2019-03-21 16:02:16.798594 I | etcdserver: snapshot count = 0
2019-03-21 16:02:16.798635 I | etcdserver: advertise client URLs =
unix://127.0.0.1:2100211086
2019-03-21 16:02:16.798657 I | etcdserver: initial advertise peer URLs =
unix://127.0.0.1:2100111086
2019-03-21 16:02:16.798676 I | etcdserver: initial cluster =
2444030890339279063=unix://127.0.0.1:2100111086
2019-03-21 16:02:16.804030 I | etcdserver: starting member d951fd13cdcf6e11
in cluster b8d26aa038f828d
2019-03-21 16:02:16.804137 I | raft: d951fd13cdcf6e11 became follower at
term 0
2019-03-21 16:02:16.804164 I | raft: newRaft d951fd13cdcf6e11 [peers: [],
term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
2019-03-21 16:02:16.804206 I | raft: d951fd13cdcf6e11 became follower at
term 1
2019-03-21 16:02:16.818807 W | auth: simple token is not cryptographically
signed
2019-03-21 16:02:16.822703 I | etcdserver: set snapshot count to default
10
2019-03-21 16:02:16.822805 I | etcdserver: starting server... [version:
3.2.13, cluster version: to_be_decided]
2019-03-21 16:02:16.823182 I | integration: launched 2444030890339279063
(unix://localhost:24440308903392790630)
2019-03-21 16:02:16.825229 I | etcdserver/membership: added member
d951fd13cdcf6e11 [unix://127.0.0.1:2100111086] to cluster b8d26aa038f828d
2019-03-21 16:02:16.885057 I | raft: d951fd13cdcf6e11 is starting a new
election at term 1
2019-03-21 16:02:16.885151 I | raft: d951fd13cdcf6e11 became candidate at
term 2
2019-03-21 16:02:16.885168 I | raft: d951fd13cdcf6e11 received MsgVoteResp
from d951fd13cdcf6e11 at term 2
2019-03-21 16:02:16.885180 I | raft: d951fd13cdcf6e11 became leader at term 2
2019-03-21 16:02:16.885187 I | raft: raft.node: d951fd13cdcf6e11 elected
leader d951fd13cdcf6e11 at term 2
2019-03-21 16:02:16.885759 I | etcdserver: setting up the initial cluster
version to 3.2
2019-03-21 16:02:16.886707 N | etcdserver/membership: set the initial
cluster version to 3.2
2019-03-21 16:02:16.886797 I | etcdserver/api: enabled capabilities for
version 3.2
2019-03-21 16:02:16.886857 I | etcdserver: published
{Name:2444030890339279063 ClientURLs:[unix://127.0.0.1:2100211086]} to cluster
b8d26aa038f828d
[Kernel-packages] [Bug 1822274] Re: 9e622d6bea0202e9fe267955362c01918562c09b in ubuntu_btrfs_kernel_fixes timeouted on B/C P9
** Tags added: ubuntu-btrfs-kernel-fixes -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822274 Title: 9e622d6bea0202e9fe267955362c01918562c09b in ubuntu_btrfs_kernel_fixes timeouted on B/C P9 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: This test will timeout on our P9 node "baltar" (it's the most time- consuming job) A manual run shows that the sysbench command in this test will take about 2 hours to complete: # sysbench --num-threads=1 --test=fileio --file-num=81920 --file-total-size=80M --file-block-size=1K --file-io-mode=sync --file-test-mode=seqwr prepare ... ... ... Creating file test_file.81917 Creating file test_file.81918 Creating file test_file.81919 83886080 bytes written in 7231.40 seconds (0.01 MiB/sec). # And our timeout threshold is exactly 2 hours. An easy fix for this is to bump the threshold. But it's weird that this test only fail on Bionic 4.15. Here is the performance matrix for how long does it take for this test to execute: * Bionic 4.18 - 90 minutes * Disco 5.0 - 99 minutes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 29 07:04 seq crw-rw 1 root audio 116, 33 Mar 29 07:04 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 29 09:55:09 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.09 0.04 0.27 1/1367 5463 ProcLocks: 1: FLOCK ADVISORY WRITE 3539 00:17:524 0 EOF 2: POSIX ADVISORY WRITE 3875 00:17:602 0 EOF 3: FLOCK ADVISORY WRITE 3912 00:17:598 0 EOF 4: POSIX ADVISORY WRITE 3902 00:17:580 0 EOF 5: POSIX ADVISORY WRITE 1820 00:17:373 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-46-generic (buildd@bos02-ppc64el-009) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_dscr: DSCR is 16 cpu_freq: min: 2.862 GHz (cpu 159) max: 2.862 GHz (cpu 1) avg: 2.862 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824293] Re: eventinj in ubuntu_kvm_unit_tests failed on Trusty
** Tags added: ubuntu-kvm-unit-tests -- 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/1824293 Title: eventinj in ubuntu_kvm_unit_tests failed on Trusty Status in ubuntu-kernel-tests: New Status in linux-signed package in Ubuntu: New Status in linux-signed source package in Trusty: New Bug description: # TESTNAME=eventinj TIMEOUT=90s ACCEL= ./x86/run x86/eventinj.flat -smp 1 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/eventinj.flat -smp 1 # -initrd /tmp/tmp.koPP3I8E97 enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 Try to divide by 0 DE isr running divider is 0 Result is 150 PASS: DE exception Try int 3 BP isr running After int 3 PASS: BP exception Sending vec 33 to self irq1 running After vec 33 to self PASS: vec 33 Try int $33 irq1 running After int $33 PASS: int $33 Sending vec 32 and 33 to self irq1 running irq0 running After vec 32 and 33 to self PASS: vec 32/33 Sending vec 32 and int $33 irq1 running irq0 running After vec 32 and int $33 PASS: vec 32/int $33 Sending vec 33 and 62 and mask one with TPR irq1 running After 33/62 TPR test PASS: TPR irq0 running Before NP test NP isr running 400a37 err=18 irq1 running After int33 PASS: NP exception Sending NMI to self NMI isr running 0x403d58 Sending nested NMI to self After nested NMI to self qemu: terminating on signal 15 from pid 16434 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-169-generic 3.13.0-169.219 ProcVersionSignature: User Name 3.13.0-169.219-generic 3.13.11-ckt39 Uname: Linux 3.13.0-169-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Thu Apr 11 06:26:12 2019 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1824293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822579] Re: Remove btrfs module after a failed fallocate attempt will cause error on 4.4 i386
** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822579 Title: Remove btrfs module after a failed fallocate attempt will cause error on 4.4 i386 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: SRU Justification: [Impact] * If fallocate() is failing on a btrfs subvolume when its qgroup quota limit exceeded, a previously allocated extent map isn't correctly released, causing a memory leak from the pool btrfs_extent_map. * Fix by correctly deallocating the object in case of failure [Test Case] * https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822579/+attachment/5252459/+files/btrfs-fallocate-test.sh [Fix] * https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=be2d253cc98244765323a7c94cc1ac5cd5a17072 Fix the memory leak by adding the proper free_extent_map() call to the failure path. [Regression Potential] * This is an upstream fix, tested on the affected platform. The patch is really small, backport changes are minimal. All the other Ubuntu releases are including this fix already. [Original bug report] If one issues a rmmod (or modprobe -r) command after a failed fallocate attempt, it will cause error with call trace: = BUG btrfs_extent_map (Not tainted): Objects remaining in btrfs_extent_map on kmem_cache_close() - Disabling lock debugging due to kernel taint INFO: Slab 0xf7526fb0 objects=34 used=1 fp=0xf43fef78 flags=0x2800080 CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 c1b0d967 35a7d73c 0286 f4ed9ddc c13c034f f7526fb0 f4ed9dfc f4ed9e70 c11ccc42 c1a164b0 f7526fb0 0022 0001 f43fef78 02800080 656a624f 20737463 616d6572 6e696e69 6e692067 72746220 655f7366 6e657478 616d5f74 Call Trace: [] dump_stack+0x58/0x79 [] slab_err+0x82/0xa0 [] ? __kmalloc+0x22d/0x240 [] ? __free_slab+0xa0/0x130 [] ? free_partial+0xa9/0x1b0 [] ? free_partial+0xa9/0x1b0 [] free_partial+0xce/0x1b0 [] ? __flush_cpu_slab+0x40/0x40 [] __kmem_cache_shutdown+0x42/0x80 [] kmem_cache_destroy+0x162/0x1e0 [] extent_map_exit+0x16/0x20 [btrfs] [] exit_btrfs_fs+0x26/0x206 [btrfs] [] SyS_delete_module+0x1af/0x200 [] ? fput+0xd/0x10 [] ? task_work_run+0x8f/0xa0 [] ? exit_to_usermode_loop+0xb6/0xe0 [] do_fast_syscall_32+0x9f/0x160 [] sysenter_past_esp+0x3d/0x61 INFO: Object 0xf43fe078 @offset=120 kmem_cache_destroy btrfs_extent_map: Slab cache still has objects CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 c1b0d967 35a7d73c 0286 f4ed9ed4 c13c034f ef34f600 ef34f674 f4ed9f0c c119e630 c1a14d18 f55f3220 f4ed9f04 000d96ab f4ed9eec f4ed9eec f4ed9ef4 f4ed9ef4 35a7d73c 022ffd44 f8e46880 f4ed8000 f4ed9f14 f8dc0ac6 f4ed9f1c Call Trace: [] dump_stack+0x58/0x79 [] kmem_cache_destroy+0x1b0/0x1e0 [] extent_map_exit+0x16/0x20 [btrfs] [] exit_btrfs_fs+0x26/0x206 [btrfs] [] SyS_delete_module+0x1af/0x200 [] ? fput+0xd/0x10 [] ? task_work_run+0x8f/0xa0 [] ? exit_to_usermode_loop+0xb6/0xe0 [] do_fast_syscall_32+0x9f/0x160 [] sysenter_past_esp+0x3d/0x61 Steps to reproduce this: TMP=/tmp MNT=/tmp/mnt mkdir $MNT TMPIMG0=$TMP/test0.img DEV0=`losetup -f` truncate --size 512M $TMPIMG0 losetup $DEV0 $TMPIMG0 mkfs.btrfs -f $DEV0 >& /dev/null mount $DEV0 $MNT btrfs quota enable $MNT btrfs sub create $MNT/subv btrfs qgroup limit 10M $MNT/subv fallocate --length 20M $MNT/subv/data rmmod btrfs ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169 ProcVersionSignature: User Name 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 1 11:43 seq crw-rw 1 root audio 116, 33 Apr 1 11:43 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Apr 1 11:55:56 2019 IwConfig: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 1824294] Re: realmode in ubuntu_kvm_unit_tests failed on Trusty
** Tags added: ubuntu-kvm-unit-tests -- 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/1824294 Title: realmode in ubuntu_kvm_unit_tests failed on Trusty Status in ubuntu-kernel-tests: New Status in linux-signed package in Ubuntu: New Status in linux-signed source package in Trusty: New Bug description: # TESTNAME=realmode TIMEOUT=90s ACCEL= ./x86/run x86/realmode.flat -smp 1 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/realmode.flat -smp 1 # -initrd /tmp/tmp.Onqv4FRzvE PASS: null PASS: shld PASS: push/pop 1 PASS: push/pop 2 PASS: push/pop 3 PASS: push/pop 4 PASS: push/pop 5 PASS: push/pop 6 PASS: push/pop with high bits set in %esp PASS: pusha/popa 1 PASS: pusha/popa 1 PASS: mov 1 PASS: mov 2 PASS: mov 3 PASS: mov 4 PASS: mov 5 PASS: cmp 1 PASS: cmp 2 PASS: cmp 3 PASS: add 1 PASS: add 2 PASS: sub 1 PASS: sub 2 PASS: sub 3 PASS: sub 4 PASS: xor 1 PASS: xor 2 PASS: xor 3 PASS: xor 4 PASS: pio 1 PASS: pio 2 PASS: pio 3 PASS: pio 4 PASS: pio 5 PASS: pio 6 PASS: clc PASS: stc PASS: cli PASS: sti PASS: cld PASS: std PASS: jnz short 1 PASS: jnz short 2 PASS: jmp short 1 PASS: jnz near 1 PASS: jnz near 2 PASS: jmp near 1 PASS: call 1 PASS: call near 1 PASS: call near 2 PASS: call far 1 PASS: call far 2 PASS: ret imm 1 PASS: retf imm 1 PASS: jmp far 1 PASS: xchg 1 PASS: xchg 2 PASS: xchg 3 PASS: xchg 4 PASS: xchg 5 PASS: xchg 6 PASS: xchg 7 PASS: xchg 8 PASS: iret 1 PASS: iret 2 PASS: iret 3 PASS: rflags.rf PASS: iret 4 PASS: int 1 PASS: imul 1 PASS: imul 2 PASS: imul 3 PASS: imul 4 PASS: imul 5 PASS: imul 6 PASS: mul 1 PASS: mul 2 PASS: mul 3 PASS: div 1 PASS: div 2 PASS: div 3 PASS: idiv 1 PASS: idiv 2 PASS: idiv 3 PASS: LOOPcc short 1 PASS: LOOPcc short 2 PASS: LOOPcc short 3 PASS: cbq 1 PASS: cwde 1 PASS: cwd 1 PASS: cwd 2 PASS: cdq 1 PASS: cdq 2 PASS: DAS PASS: lds PASS: les PASS: lfs PASS: lgs PASS: lss PASS: jcxz short 1 PASS: jcxz short 2 PASS: jcxz short 3 PASS: jecxz short 1 PASS: jecxz short 2 PASS: cpuid PASS: ss relative addressing (1) PASS: ss relative addressing (2) PASS: sgdt PASS: sidt PASS: lahf PASS: sahf PASS: movsx PASS: movzx PASS: movsx ah PASS: movzx ah PASS: bswap PASS: aad PASS: aam PASS: xlat PASS: salc (1) PASS: salc (2) PASS: fninit PASS: mov dr with mod bits FAIL: smsw PASS: nopl PASS: xadd 1 cycles/emulated jump instruction 0 cycles/emulated move instruction 0 cycles/emulated arithmetic instruction 0 cycles/emulated memory load instruction 0 cycles/emulated memory store instruction 5 cycles/emulated memory RMW instruction ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-169-generic 3.13.0-169.219 ProcVersionSignature: User Name 3.13.0-169.219-generic 3.13.11-ckt39 Uname: Linux 3.13.0-169-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Thu Apr 11 06:37:17 2019 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1824294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824289] Re: ioapic in ubuntu_kvm_unit_tests failed on Trusty
** Tags added: ubuntu-kvm-unit-tests -- 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/1824289 Title: ioapic in ubuntu_kvm_unit_tests failed on Trusty Status in ubuntu-kernel-tests: New Status in linux-signed package in Ubuntu: New Status in linux-signed source package in Trusty: New Bug description: # TESTNAME=ioapic TIMEOUT=90s ACCEL= ./x86/run x86/ioapic.flat -smp 1 -cpu qemu64 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/ioapic.flat -smp 1 -cpu qemu64 # -initrd /tmp/tmp.KVrgShiIao enabling apic paging enabled cr0 = 80010011 cr3 = 45a000 cr4 = 20 x2apic enabled PASS: version register read only test PASS: id register only bits [24:27] writable PASS: arbitration register set by id PASS: arbtration register read only PASS: edge triggered intr PASS: level triggered intr PASS: ioapic simultaneous edge interrupts PASS: coalesce simultaneous level interrupts PASS: sequential level interrupts PASS: retriggered level interrupts without masking PASS: masked level interrupt PASS: unmasked level interrupt PASS: masked level interrupt PASS: unmasked level interrupt PASS: retriggered level interrupts with mask PASS: TMR for ioapic edge interrupts (expected false) FAIL: TMR for ioapic level interrupts (expected false) PASS: TMR for ioapic level interrupts (expected true) FAIL: TMR for ioapic edge interrupts (expected true) SUMMARY: 19 tests, 2 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-169-generic 3.13.0-169.219 ProcVersionSignature: User Name 3.13.0-169.219-generic 3.13.11-ckt39 Uname: Linux 3.13.0-169-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Thu Apr 11 06:20:44 2019 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1824289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825778] Re: False positive test result in run_afpackettests from net in ubuntu_kernel_selftest
** Tags added: ubuntu-kernel-selftests ** Tags added: disco xenial ** Tags added: 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/1825778 Title: False positive test result in run_afpackettests from net in ubuntu_kernel_selftest Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: New Bug description: The run_afpackettests will be marked as passed regardless the return value of those sub-tests in the script: running psock_tpacket test [FAIL] selftests: run_afpackettests [PASS] Fix this by changing the return value for each tests. Patch sent to upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827845] Re: ubuntu_bpf_jit report result in D on s390x is a bit confusing
** Tags added: ubuntu-bpf-jit -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827845 Title: ubuntu_bpf_jit report result in D on s390x is a bit confusing Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The only failure is the test_bpf module load failure, and there are 378 tests (0-377) But the result shows "Summary: 377 PASSED, 1 FAILED" Module test_bpf load failure [ 873.481738] test_bpf: #0 TAX jited:1 36 34 35 PASS [ 873.481888] test_bpf: #1 TXA jited:1 17 17 17 PASS [ 873.481960] test_bpf: #2 ADD_SUB_MUL_K jited:1 18 PASS [ 873.481997] test_bpf: #3 DIV_MOD_KX jited:1 35 PASS [ 873.482054] test_bpf: #4 AND_OR_LSH_K jited:1 16 16 PASS [ 873.482106] test_bpf: #5 LD_IMM_0 jited:1 16 PASS [ 873.482141] test_bpf: #6 LD_IND jited:1 48 47 47 PASS [ 873.482305] test_bpf: #7 LD_ABS jited:1 49 49 49 PASS [ 873.482472] test_bpf: #8 LD_ABS_LL jited:1 72 72 PASS [ 873.482637] test_bpf: #9 LD_IND_LL jited:1 49 49 49 PASS [ 873.482804] test_bpf: #10 LD_ABS_NET jited:1 71 71 PASS [ 873.482966] test_bpf: #11 LD_IND_NET jited:1 48 48 48 PASS [ 873.483132] test_bpf: #12 LD_PKTTYPE jited:1 18 18 PASS [ 873.483189] test_bpf: #13 LD_MARK jited:1 18 18 PASS [ 873.483242] test_bpf: #14 LD_RXHASH jited:1 18 18 PASS [ 873.483295] test_bpf: #15 LD_QUEUE jited:1 18 18 PASS [ 873.483347] test_bpf: #16 LD_PROTOCOL jited:1 20 20 PASS [ 873.483410] test_bpf: #17 LD_VLAN_TAG jited:1 18 18 PASS [ 873.483463] test_bpf: #18 LD_VLAN_TAG_PRESENT jited:1 17 17 PASS [ 873.483515] test_bpf: #19 LD_IFINDEX jited:1 17 17 PASS [ 873.483567] test_bpf: #20 LD_HATYPE jited:1 17 17 PASS [ 873.483618] test_bpf: #21 LD_CPU jited:1 52 52 PASS [ 873.483742] test_bpf: #22 LD_NLATTR jited:1 34 44 PASS [ 873.483839] test_bpf: #23 LD_NLATTR_NEST jited:1 155 236 PASS [ 873.484254] test_bpf: #24 LD_PAYLOAD_OFF jited:1 295 325 PASS [ 873.484894] test_bpf: #25 LD_ANC_XOR jited:1 16 16 PASS [ 873.484945] test_bpf: #26 SPILL_FILL jited:1 20 20 20 PASS [ 873.485026] test_bpf: #27 JEQ jited:1 47 18 18 PASS [ 873.485131] test_bpf: #28 JGT jited:1 47 18 18 PASS [ 873.485236] test_bpf: #29 JGE (jt 0), test 1 jited:1 46 18 18 PASS [ 873.485339] test_bpf: #30 JGE (jt 0), test 2 jited:1 18 18 18 PASS [ 873.485414] test_bpf: #31 JGE jited:1 34 35 35 PASS [ 873.485540] test_bpf: #32 JSET jited:1 37 36 39 PASS [ 873.485678] test_bpf: #33 tcpdump port 22 jited:1 47 52 57 PASS [ 873.485871] test_bpf: #34 tcpdump complex jited:1 47 50 74 PASS [ 873.486082] test_bpf: #35 RET_A jited:1 16 16 PASS [ 873.486132] test_bpf: #36 INT: ADD trivial jited:1 16 PASS [ 873.486165] test_bpf: #37 INT: MUL_X jited:1 16 PASS [ 873.486197] test_bpf: #38 INT: MUL_X2 jited:1 17 PASS [ 873.486230] test_bpf: #39 INT: MUL32_X jited:1 17 PASS [ 873.486263] test_bpf: #40 INT: ADD 64-bit jited:1 36 PASS [ 873.486331] test_bpf: #41 INT: ADD 32-bit jited:1 50 PASS [ 873.486411] test_bpf: #42 INT: SUB jited:1 33 PASS [ 873.486472] test_bpf: #43 INT: XOR jited:1 22 PASS [ 873.486516] test_bpf: #44 INT: MUL jited:1 71 PASS [ 873.486609] test_bpf: #45 MOV REG64 jited:1 19 PASS [ 873.486647] test_bpf: #46 MOV REG32 jited:1 19 PASS [ 873.486685] test_bpf: #47 LD IMM64 jited:1 20 PASS [ 873.486725] test_bpf: #48 INT: ALU MIX jited:1 24 PASS [ 873.486788] test_bpf: #49 INT: shifts by register jited:1 19 PASS [ 873.486827] test_bpf: #50 check: missing ret PASS [ 873.486834] test_bpf: #51 check: div_k_0 PASS [ 873.486840] test_bpf: #52 check: unknown insn PASS [ 873.486846] test_bpf: #53 check: out of range spill/fill PASS [ 873.486851] test_bpf: #54 JUMPS + HOLES jited:1 21 PASS [ 873.486964] test_bpf: #55 check: RET X PASS [ 873.486970] test_bpf: #56 check: LDX + RET X PASS [ 873.486976] test_bpf: #57 M[]: alt STX + LDX jited:1 57 PASS [ 873.487065] test_bpf: #58 M[]: full STX + full LDX jited:1 27 PASS [ 873.487122] test_bpf: #59 check: SKF_AD_MAX PASS [ 873.487128] test_bpf: #60 LD [SKF_AD_OFF-1] jited:1 48 PASS [ 873.487196] test_bpf: #61 load 64-bit immediate jited:1 17 PASS [ 873.487231] test_bpf: #62 ALU_MOV_X: dst = 2 jited:1 16 PASS [ 873.487265] test_bpf: #63 ALU_MOV_X: dst = 4294967295 jited:1 16 PASS [ 873.487298] test_bpf: #64 ALU64_MOV_X: dst = 2 jited:1 16 PASS [ 873.487331] test_bpf: #65 ALU64_MOV_X: dst = 4294967295 jited:1 16 PASS [ 873.487364] test_bpf: #66 ALU_MOV_K: dst = 2 jited:1 16 PASS [ 873.487397] test_bpf: #67 ALU_MOV_K: dst = 4294967295 jited:1 16 PASS [ 873.487430] test_bpf: #68 ALU_MOV_K: 0x = 0x jited:1 16 PASS [ 873.487463] test_bpf: #69 ALU64_MOV_K: dst = 2 jited:1 16 PASS [ 873.487496] test_bpf: #70 ALU64_MOV_K: dst = 2147483647 jited:1 16 PASS [
[Kernel-packages] [Bug 1828026] Re: gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64
** Tags added: ubuntu-kvm-unit-tests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828026 Title: gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Failed on Moonshot nodes. FAIL gicv2-mmio-up (17 tests, 2 unexpected failures) # TESTNAME=gicv2-mmio-up TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 1 -machine gic-version=2 -append 'mmio' timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/gic.flat -smp 1 -machine gic-version=2 -append mmio # -initrd /tmp/tmp.6k28Ehxzim INFO: gicv2: mmio: number of implemented SPIs: 256 PASS: gicv2: mmio: all 1 CPUs have interrupts INFO: gicv2: mmio: IIDR: 0x PASS: gicv2: mmio: GICD_TYPER is read-only PASS: gicv2: mmio: GICD_IIDR is read-only PASS: gicv2: mmio: ICPIDR2 is read-only (0x0004) PASS: gicv2: mmio: IPRIORITYR: consistent priority masking (0x) PASS: gicv2: mmio: IPRIORITYR: implements at least 4 priority bits (8) PASS: gicv2: mmio: IPRIORITYR: clearing priorities PASS: gicv2: mmio: IPRIORITYR: accesses beyond limit RAZ/WI PASS: gicv2: mmio: IPRIORITYR: accessing last SPIs PASS: gicv2: mmio: IPRIORITYR: priorities are preserved PASS: gicv2: mmio: IPRIORITYR: byte reads successful (0xff7fbf3f => 0xbf) PASS: gicv2: mmio: IPRIORITYR: byte writes successful (0x1f => 0xff1fbf3f) PASS: gicv2: mmio: ITARGETSR: bits for 7 non-existent CPUs masked PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI FAIL: gicv2: mmio: ITARGETSR: register content preserved (01010001 => ) PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x01010001 => 0x00) FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x) SUMMARY: 17 tests, 2 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51~16.04.1 ProcVersionSignature: User Name 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic aarch64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 Date: Tue May 7 11:25:30 2019 SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827977] Re: eventinj in ubuntu_kvm_unit_tests failed on B-KVM
** Tags added: ubuntu-kvm-unit-tests -- 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/1827977 Title: eventinj in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: FAIL eventinj (13 tests, 1 unexpected failures) # TESTNAME=eventinj TIMEOUT=90s ACCEL= ./x86/run x86/eventinj.flat -smp 1 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/eventinj.flat -smp 1 # -initrd /tmp/tmp.0h33pnhsnZ qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 Try to divide by 0 DE isr running divider is 0 Result is 150 PASS: DE exception Try int 3 BP isr running After int 3 PASS: BP exception Sending vec 33 to self irq1 running After vec 33 to self PASS: vec 33 Try int $33 irq1 running After int $33 PASS: int $33 Sending vec 32 and 33 to self irq1 running irq0 running After vec 32 and 33 to self PASS: vec 32/33 Sending vec 32 and int $33 irq1 running irq0 running After vec 32 and int $33 PASS: vec 32/int $33 Sending vec 33 and 62 and mask one with TPR irq1 running After 33/62 TPR test PASS: TPR irq0 running Before NP test NP isr running 400a3d err=18 irq1 running After int33 PASS: NP exception Sending NMI to self After NMI to self FAIL: NMI Before NMI IRET test Sending NMI to self NMI isr running stack 0x465000 Sending nested NMI to self After nested NMI to self Nested NMI isr running rip=4003e4 After iret After NMI to self PASS: NMI Try to divide by 0 PF running DE isr running divider is 0 Result is 150 PASS: DE PF exceptions Before NP test PF running NP isr running 400ccd err=18 irq1 running After int33 PASS: NP PF exceptions Try int 33 with shadowed stack irq1 running After int 33 with shadowed stack PASS: int 33 with shadowed stack SUMMARY: 13 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:26:45 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827866] Re: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X-KVM
** Tags added: ubuntu-kvm-unit-tests -- 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/1827866 Title: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: New Status in linux-kvm source package in Bionic: New Bug description: vmx_apicv_test from ubuntu_kvm_unit_tests failed on X-KVM: FAIL vmx_apicv_test (timeout; duration=10) the test was terminated with return code 124: # TESTNAME=vmx_apicv_test TIMEOUT=10 ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "apic_reg_virt_test virt_x2apic_mode_test" timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,+vmx -append apic_reg_virt_test virt_x2apic_mode_test # -initrd /tmp/tmp.K6b7rjmgp8 enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: apic_reg_virt_test --- Virtualize APIC accesses test --- PASS: xapic - reading 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - writing 0x12345678 to 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - reading 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - writing 0x12345678 to 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - reading 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - writing 0x12345678 to 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - reading 0x030: got APIC access exit @ page offset 0x030, want 0x030 PASS: xapic - writing 0x12345678 to 0x380: non-virtualized write; val is 0x12345678, want 0x12345678 PASS: xapic - reading 0x390: read 0x12345678, expected 0x12345678. PASS: xapic - writing 0x12345678 to 0x390: non-virtualized writqemu-system-x86_64: terminating on signal 15 from pid 1327 # echo $? 124 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1044-kvm 4.4.0-1044.50 ProcVersionSignature: Ubuntu 4.4.0-1044.50-kvm 4.4.177 Uname: Linux 4.4.0-1044-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon May 6 10:47:17 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827982] Re: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM
** Tags added: ubuntu-kvm-unit-tests -- 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/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Test timeouted. # TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM
** Tags added: ubuntu-kvm-unit-tests -- 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/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827979] Re: pcid in ubuntu_kvm_unit_tests failed on B-KVM
** Tags added: ubuntu-kvm-unit-tests -- 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/1827979 Title: pcid in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: FAIL pcid (3 tests, 1 unexpected failures) # TESTNAME=pcid TIMEOUT=90s ACCEL= ./x86/run x86/pcid.flat -smp 1 -cpu qemu64,+pcid timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/pcid.flat -smp 1 -cpu qemu64,+pcid # -initrd /tmp/tmp.a4xQyF7juj qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic PASS: CPUID consistency PASS: Test on PCID when disabled FAIL: Test on INVPCID when disabled SUMMARY: 3 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:31:38 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831899] Comment bridged from LTC Bugzilla
--- Comment From mbri...@us.ibm.com 2019-09-16 11:05 EDT--- (In reply to comment #36) > Is this easily reproducible? Can you retry with the latest released kernel > 4.15.0-58.64? I haven't been able to reproduce the problem locally so far. > It would help if you could share the container and workload, if that's > possible at all. I'm still looking through the dumpfiles but haven't made > much progress yet towards finding the root cause. Robert: Please answer questions from 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/1831899 Title: Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in kernel virtual address space Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: == Comment: #0 - Robert J. Brenneman - 2019-05-30 11:16:45 == ---Problem Description--- Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in virtual kernel address space Contact Information = rjbr...@us.ibm.com ---uname output--- Linux ECOS0018 4.15.0-50-generic #54-Ubuntu SMP Tue May 7 05:57:08 UTC 2019 s390x s390x s390x GNU/Linux Machine Type = z13 2964 NE1 ---System Hang--- z/VM took a VMDUMP and reIPLed (the attached and available dumps are Linux dumps) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- boot system, start jenkins, let it run a couple days Stack trace output: 05/29/19 13:24:06 Call Trace: 05/29/19 13:24:06 (?<0012b97a>? __tlb_remove_table+0x6a/0xd0) 05/29/19 13:24:06 ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70 05/29/19 13:24:06 ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570 05/29/19 13:24:06 ?<008e92d4>? __do_softirq+0x124/0x358 05/29/19 13:24:06 ?<00179d52>? irq_exit+0xba/0xd0 05/29/19 13:24:06 ?<0010c412>? do_IRQ+0x8a/0xb8 05/29/19 13:24:06 ?<008e87f0>? ext_int_handler+0x134/0x138 05/29/19 13:24:06 ?<00102cee>? enabled_wait+0x4e/0xe0 05/29/19 13:24:06 (?<1201>? 0x1201) 05/29/19 13:24:06 ?<0010303a>? arch_cpu_idle+0x32/0x48 05/29/19 13:24:06 ?<001c5ae8>? do_idle+0xe8/0x1a8 Oops output: 05/29/19 13:24:06 User process fault: interruption code 003b ilc:3 in libc-2.23.so?3ffaca0+185000? 05/29/19 13:24:06 Failing address: TEID: 0800 05/29/19 13:24:06 Fault in primary space mode while using user ASCE. 05/29/19 13:24:06 AS:000710b241c7 R3:0024 05/29/19 13:24:06 Unable to handle kernel pointer dereference in virtual kernel address space 05/29/19 13:24:06 Failing address: 03dbe000 TEID: 03dbe403 05/29/19 13:24:06 Fault in home space mode while using kernel ASCE. 05/29/19 13:24:06 AS:00ea8007 R3:0024 05/29/19 13:24:06 Oops: 003b ilc:3 ?#1? SMP 05/29/19 13:24:06 Modules linked in: veth xt_nat xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_con 05/29/19 13:24:06 ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 dasd_fba_mod dasd_eckd_mod sha1_s390 sha_common dasd_mod 05/29/19 13:24:06 CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.15.0-50-generic #54-Ubuntu 05/29/19 13:24:06 Hardware name: IBM 2964 NE1 798 (z/VM 6.4.0) 05/29/19 13:24:06 Krnl PSW : dcb002be 72762961 (__tlb_remove_table+0x56/0xd0) 05/29/19 13:24:06 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 05/29/19 13:24:06 Krnl GPRS: ffba 02b8 02b80003 00eacac8 05/29/19 13:24:06 ffba 00b9 0700 000a 05/29/19 13:24:06 0404c001 0007d2fb5c38 0007cf71fdf0 03dbe000 05/29/19 13:24:06 03dbe018 008fe740 0007cf71fd08 0007cf71fcd8 05/29/19 13:24:06 Krnl Code: 0012b956: ec2c002a027f clij %r2,2,12,12b9aa 05/29/19 13:24:06 0012b95c: ec26001d037e cij %r2,3,6,12b996 05/29/19 13:24:06#0012b962: 41c0b018 la %r12,24(%r11) 05/29/19 13:24:06>0012b966: e548b008 mvghi 8(%r11),0 05/29/19 13:24:06 0012b96c: a7390008 lghi %r3,8 05/29/19 13:24:06 0012b970: b904002b lgr %r2,%r11 05/29/19 13:24:06 0012b974: c0e5000e8f8a brasl %r14,2fd888 05/29/19 13:24:06 0012b97a: a718 lhi %r1,-1 05/29/19 13:24:06 Call Trace: 05/29/19 13:24:06 (?<0012b97a>?
[Kernel-packages] [Bug 1842023] Re: run_netsocktests from net in ubuntu_kernel_selftests failed with X-4.15
Upstream patch: https://lkml.org/lkml/2019/9/16/470 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842023 Title: run_netsocktests from net in ubuntu_kernel_selftests failed with X-4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-hwe source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: Invalid Bug description: Just like bug 1830016 This test failed with the same error on X-4.15: selftests: run_netsocktests running socket test socket(41, 0, 0) expected err (Address family not supported by protocol) got (Socket type not supported) [FAIL] not ok 1..6 selftests: run_netsocktests [FAIL] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67~16.04.1 ProcVersionSignature: User Name 4.15.0-60.67~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-60-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Fri Aug 30 06:49:48 2019 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1842023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822235] Re: All 29 tests in kvm-unit-test failed (timeouted) on i386
** Tags added: ubuntu-kvm-unit-tests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822235 Title: All 29 tests in kvm-unit-test failed (timeouted) on i386 Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: All the available tests in kvm-unit-test have failed on Cosmic i386 with node "onza". They all timeout with the default 90 second threshold. TESTNAME=smptest TIMEOUT=90s ACCEL= ./x86/run x86/smptest.flat -smp 2 FAIL smptest (timeout; duration=90s) TESTNAME=smptest3 TIMEOUT=90s ACCEL= ./x86/run x86/smptest.flat -smp 3 FAIL smptest3 (timeout; duration=90s) TESTNAME=vmexit_cpuid TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'cpuid' FAIL vmexit_cpuid (timeout; duration=90s) TESTNAME=vmexit_vmcall TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'vmcall' FAIL vmexit_vmcall (timeout; duration=90s) TESTNAME=vmexit_mov_from_cr8 TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'mov_from_cr8' FAIL vmexit_mov_from_cr8 (timeout; duration=90s) TESTNAME=vmexit_mov_to_cr8 TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'mov_to_cr8' FAIL vmexit_mov_to_cr8 (timeout; duration=90s) TESTNAME=vmexit_inl_pmtimer TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'inl_from_pmtimer' FAIL vmexit_inl_pmtimer (timeout; duration=90s) TESTNAME=vmexit_ipi TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 2 -append 'ipi' FAIL vmexit_ipi (timeout; duration=90s) TESTNAME=vmexit_ipi_halt TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 2 -append 'ipi_halt' FAIL vmexit_ipi_halt (timeout; duration=90s) TESTNAME=vmexit_ple_round_robin TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'ple_round_robin' FAIL vmexit_ple_round_robin (timeout; duration=90s) TESTNAME=vmexit_tscdeadline TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -cpu qemu64,+x2apic,+tsc-deadline -append tscdeadline FAIL vmexit_tscdeadline (timeout; duration=90s) TESTNAME=vmexit_tscdeadline_immed TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -cpu qemu64,+x2apic,+tsc-deadline -append tscdeadline_immed FAIL vmexit_tscdeadline_immed (timeout; duration=90s) TESTNAME=smap TIMEOUT=90s ACCEL= ./x86/run x86/smap.flat -smp 1 -cpu host FAIL smap (timeout; duration=90s) TESTNAME=eventinj TIMEOUT=90s ACCEL= ./x86/run x86/eventinj.flat -smp 1 FAIL eventinj (timeout; duration=90s) TESTNAME=hypercall TIMEOUT=90s ACCEL= ./x86/run x86/hypercall.flat -smp 1 FAIL hypercall (timeout; duration=90s) TESTNAME=msr TIMEOUT=90s ACCEL= ./x86/run x86/msr.flat -smp 1 FAIL msr (timeout; duration=90s) TESTNAME=port80 TIMEOUT=90s ACCEL= ./x86/run x86/port80.flat -smp 1 FAIL port80 (timeout; duration=90s) TESTNAME=realmode TIMEOUT=90s ACCEL= ./x86/run x86/realmode.flat -smp 1 FAIL realmode (timeout; duration=90s) TESTNAME=s3 TIMEOUT=90s ACCEL= ./x86/run x86/s3.flat -smp 1 FAIL s3 (timeout; duration=90s) TESTNAME=sieve TIMEOUT=90s ACCEL= ./x86/run x86/sieve.flat -smp 1 FAIL sieve (timeout; duration=90s) TESTNAME=tsc TIMEOUT=90s ACCEL= ./x86/run x86/tsc.flat -smp 1 -cpu kvm64,+rdtscp FAIL tsc (timeout; duration=90s) TESTNAME=tsc_adjust TIMEOUT=90s ACCEL= ./x86/run x86/tsc_adjust.flat -smp 1 -cpu host FAIL tsc_adjust (timeout; duration=90s) TESTNAME=taskswitch TIMEOUT=90s ACCEL= ./x86/run x86/taskswitch.flat -smp 1 FAIL taskswitch (timeout; duration=90s) TESTNAME=taskswitch2 TIMEOUT=90s ACCEL= ./x86/run x86/taskswitch2.flat -smp 1 FAIL taskswitch2 (timeout; duration=90s) TESTNAME=kvmclock_test TIMEOUT=90s ACCEL= ./x86/run x86/kvmclock_test.flat -smp 2 --append "1000 `date +%s`" FAIL kvmclock_test (timeout; duration=90s) TESTNAME=umip TIMEOUT=90s ACCEL= ./x86/run x86/umip.flat -smp 1 -cpu qemu64,+umip FAIL umip (timeout; duration=90s) TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev FAIL hyperv_synic (timeout; duration=90s) TESTNAME=hyperv_connections TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_connections.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev FAIL hyperv_connections (timeout; duration=90s) TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev FAIL hyperv_stimer (timeout; duration=90s) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-16-generic 4.18.0-16.17 ProcVersionSignature: User Name 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic i686 AlsaDevices:
[Kernel-packages] [Bug 1821905] Re: umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4
** Tags added: ubuntu-kvm-unit-tests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821905 Title: umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This umip test failed on T-3.13 and T-4.4 On X-4.4 this was skipped: SKIP umip (qemu-system-x86_64: CPU feature umip not found) So it looks like a qemu issue to me. root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=umip TIMEOUT=90s ACCEL= ./x86/run x86/umip.flat -smp 1 -cpu qemu64,+umip timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/umip.flat -smp 1 -cpu qemu64,+umip # -initrd /tmp/tmp.WBWyPcleSg CPU feature umip not found enabling apic UMIP=0, CPL=0 PASS: no exception from smsw PASS: no exception from sgdt PASS: no exception from sidt PASS: no exception from sldt PASS: no exception from str UMIP=0, CPL=3 PASS: no exception from smsw PASS: no exception from sgdt PASS: no exception from sidt PASS: no exception from sldt PASS: no exception from str PASS: exception from mov %cr0, %eax UMIP not available SUMMARY: 11 tests ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2 ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Mar 27 11:10:13 2019 SourcePackage: linux-signed-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822542] Re: All 12 tests in kvm-unit-test failed (timeouted) on X s390x KVM
** Tags added: ubuntu-kvm-unit-tests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822542 Title: All 12 tests in kvm-unit-test failed (timeouted) on X s390x KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: I think this bug is just a place holder, as the nested KVM is out-of- scope especially on s390x TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./s390x/run s390x/selftest.elf -smp 1 -append 'test 123' FAIL selftest-setup (timeout; duration=90s) TESTNAME=intercept TIMEOUT=90s ACCEL= ./s390x/run s390x/intercept.elf -smp 1 FAIL intercept (timeout; duration=90s) TESTNAME=emulator TIMEOUT=90s ACCEL= ./s390x/run s390x/emulator.elf -smp 1 FAIL emulator (timeout; duration=90s) TESTNAME=sieve TIMEOUT=600 ACCEL= ./s390x/run s390x/sieve.elf -smp 1 FAIL sieve (timeout; duration=600) TESTNAME=sthyi TIMEOUT=90s ACCEL= ./s390x/run s390x/sthyi.elf -smp 1 FAIL sthyi (timeout; duration=90s) TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1 FAIL skey (timeout; duration=90s) TESTNAME=diag10 TIMEOUT=90s ACCEL= ./s390x/run s390x/diag10.elf -smp 1 FAIL diag10 (timeout; duration=90s) TESTNAME=pfmf TIMEOUT=90s ACCEL= ./s390x/run s390x/pfmf.elf -smp 1 FAIL pfmf (timeout; duration=90s) TESTNAME=cmm TIMEOUT=90s ACCEL= ./s390x/run s390x/cmm.elf -smp 1 FAIL cmm (timeout; duration=90s) TESTNAME=vector TIMEOUT=90s ACCEL= ./s390x/run s390x/vector.elf -smp 1 FAIL vector (timeout; duration=90s) TESTNAME=gs TIMEOUT=90s ACCEL= ./s390x/run s390x/gs.elf -smp 1 FAIL gs (timeout; duration=90s) TESTNAME=iep TIMEOUT=90s ACCEL= ./s390x/run s390x/iep.elf -smp 1 FAIL iep (timeout; duration=90s) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-145-generic 4.4.0-145.171 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Mon Apr 1 03:04:02 2019 HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.4.0-145-generic N/A linux-backports-modules-4.4.0-145-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822246] Re: binfmt_misc02 in LTP kernel/fs/ failed with Bionic
** Tags added: ubuntu-ltp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822246 Title: binfmt_misc02 in LTP kernel/fs/ failed with Bionic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Found on a KVM node, I think this test case might need some investigation, as the LTP suite should be chop down into pieces like the syscalls variant. <<>> tag=binfmt_misc02 stime=1553796942 cmdline="binfmt_misc02.sh" contacts="" analysis=exit <<>> binfmt_misc02 1 TINFO: timeout per run is 0h 5m 0s binfmt_misc02 1 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 2 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 3 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 4 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 5 TFAIL: Recognise a binary type successfully binfmt_misc02 6 TFAIL: Recognise a binary type successfully binfmt_misc02 7 TINFO: AppArmor enabled, this may affect test results binfmt_misc02 7 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 (requires super/root) binfmt_misc02 7 TINFO: loaded AppArmor profiles: none Summary: passed 0 failed 6 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=14 cstime=6 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 29 06:45 seq crw-rw 1 root audio 116, 33 Mar 29 06:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 29 06:48:07 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822247] Re: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel
Test passed with 4.15.0-63.72 - generic on P9
** Changed in: ubuntu-kernel-tests
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/1822247
Title:
ubuntu_nbd_smoke_test failed on P9 with Bionic kernel
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification, BIONIC ==
[Impact]
Running the autotest regression test ubuntu_nbd_smoke occasionally
trips I/O errors such as:
[ 700.668758] print_req_error: I/O error, dev nbd0, sector 0
[ 700.668840] Buffer I/O error on dev nbd0, logical block 0, async page read
This happens when the nbd client detaches and the backing store is
removed. The fix is to ensure a rescan occurs.
[Fix]
Upstream fix fe1f9e6659ca6124f500a0f829202c7c902fab0c (" nbd: fix how we set
bd_invalidated"). If a disconnect action happens the
partition table gets invalidated and rescanned properly.
[Test]
Without the fix running the Ubuntu Kernel Team nbd smoke test will
occasionally trip the bug and the error message from the kernel
appears and the test fails. With the fix, this test has been run tens
of times without showing the failure.
To test run:
autotest/client/local-test autotest/client/tests/ubuntu_nbd_smoke_test/control
[Regression Potential]
This fix touches just the NBD driver and has been upstream since May
2018 without any subsequent bug reports against it, so it is a known
good fix. At most it sets the bd_invalidated flag more aggressively,
so the rescan will occur, so I believe the regression potential is
very limited just to ndb client connect/disconnect activity.
-
Reproduce rate: 2 out of 3 runs
This issue can be found on other arches as well, normally it will fail with
the first run and pass with the second attempt.
* Command:
/home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke
_test.sh
Exit status: 1
Duration: 7.90551400185
stdout:
creating backing nbd image /tmp/nbd_image.img
Image path:/tmp/nbd_image.img
Mount point: /mnt/nbd-test-13924
Date: Fri Mar 29 06:06:04 UTC 2019
Host: baltar
Kernel:4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019
Machine: baltar ppc64le ppc64le
CPUs online: 160
CPUs total:160
Page size: 65536
Pages avail: 1904339
Pages total: 2089666
Free space:
Filesystem Size Used Avail Use% Mounted on
udev 61G 0 61G 0% /dev
tmpfs13G 12M 13G 1% /run
/dev/sda2 1.8T 11G 1.7T 1% /
tmpfs64G 0 64G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs64G 0 64G 0% /sys/fs/cgroup
tmpfs13G 0 13G 0% /run/user/1000
NBD device /dev/nbd0 created
found nbd export
NBD exports found:
test
starting client with NBD device /dev/nbd0
Negotiation: ..size = 128MB
creating ext4 on /dev/nbd0
mkfs on /dev/nbd0 succeeded after 0 attempt(s)
checking ext4 on /dev/nbd0
fsck from util-linux 2.31.1
/dev/nbd0: clean, 11/32768 files, 9787/131072 blocks
mount:
/dev/nbd0 on /mnt/nbd-test-13924 type ext4 (rw,relatime,data=ordered)
mounted on /dev/nbd0
free:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/nbd0 122835 1550112111 2% /mnt/nbd-test-13924
creating large file /mnt/nbd-test-13924/largefile
-rw-r--r-- 1 root root 100M Mar 29 06:06 /mnt/nbd-test-13924/largefile
free:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-13924
removing file /mnt/nbd-test-13924/largefile
unmounting /mnt/nbd-test-13924
stopping client
disconnect, sock, done
Found kernel warning, IO error and/or call trace
echo
[ 694.662746] creating backing nbd image /tmp/nbd_image.img
[ 695.821047] NBD device /dev/nbd0 created
[ 696.271555] found nbd export
[ 697.318393] starting client with NBD device /dev/nbd0
[ 697.323210] creating ext4 on /dev/nbd0
[ 697.589620] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
[ 697.821953] checking ext4 on /dev/nbd0
[ 697.919173] EXT4-fs (nbd0): mounted filesystem with ordered data mode.
Opts: (null)
[ 697.925418] mounted on /dev/nbd0
[ 697.927107] creating large file /mnt/nbd-test-13924/largefile
[ 698.839327] removing file /mnt/nbd-test-13924/largefile
[ 699.596736]
[Kernel-packages] [Bug 1821152] Re: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com'
** Tags added: ubuntu-lxc -- 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/1821152 Title: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com' Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: It seems this failure only exist in KVM instances. FAIL: lxc-tests: lxc-test-no-new-privs (37s) --- + DONE=0 + trap cleanup EXIT SIGHUP SIGINT SIGTERM + mkdir -p /etc/lxc/ + cat + ARCH=i386 + type dpkg ++ dpkg --print-architecture + ARCH=amd64 + lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64 Setting up the GPG keyring Downloading the image index Downloading the rootfs Downloading the metadata The image cache is now ready Unpacking the rootfs --- You just created an Ubuntu xenial amd64 (20190320_07:42) container. To enable SSH, run: apt install openssh-server No default root or user password are set by LXC. + echo 'lxc.no_new_privs = 1' + lxc-start -n c1 ++ lxc-info -n c1 -p -H + p1=8818 + '[' 8818 '!=' -1 ']' + sleep 5s + lxc-attach -n c1 --clear-env -- apt update -y WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'archive.ubuntu.com' Reading package lists... Building dependency tree... Reading state information... All packages are up to date. W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. + lxc-attach -n c1 --clear-env -- apt install -y gcc make WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: binutils cpp cpp-5 gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages manpages-dev Suggested packages: binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc make-doc man-browser The following NEW packages will be installed: binutils cpp cpp-5 gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev make manpages manpages-dev 0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded. Need to get 28.7 MB of archives. After this operation, 102 MB of additional disk space will be used. Err:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpfr4 amd64 3.1.4-1 Temporary failure resolving 'archive.ubuntu.com' Err:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpc3 amd64 1.0.3-1 Temporary failure resolving 'archive.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 manpages all 4.04-2 Temporary failure resolving 'archive.ubuntu.com' Err:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 binutils amd64 2.26.1-1ubuntu1~16.04.8 Temporary failure resolving 'archive.ubuntu.com' Err:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 libisl15 amd64 0.16.1-1 Temporary failure resolving 'archive.ubuntu.com' It's a bit weird that if I run the command manually, it looks OK lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64 lxc-start -n c1 lxc-attach -n c1 --clear-env -- apt update -y Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB] Get:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [925 kB]
[Kernel-packages] [Bug 1821393] Re: vmware_backdoors will fail on kvm_unit_tests on aws i3.metal
** Tags added: ubuntu-kvm-unit-tests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821393 Title: vmware_backdoors will fail on kvm_unit_tests on aws i3.metal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Reproducible: Yes, every time. Series: cosmic Kernel: "linux-aws 4.18.0-1012.14" Steps: 1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) TESTNAME=vmware_backdoors TIMEOUT=90s ACCEL= ./x86/run x86/vmware_backdoors.flat -smp 1 -machine vmport=on root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=vmware_backdoors TIMEOUT=90s ACCEL= ./x86/run x86/vmware_backdoors.flat -smp 1 -machine vmport=on timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmware_backdoors.flat -smp 1 -machine vmport=on # -initrd /tmp/tmp.QldMaGLdve qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic paging enabled cr0 = 80010011 cr3 = 45b000 cr4 = 20 PASS: vmware_backdoors: rdpmc_test: HOST_TSC kernel PASS: vmware_backdoors: rdpmc_test: REAL_TIME kernel PASS: vmware_backdoors: rdpmc_test: APPARENT_TIME kernel FAIL: vmware_backdoors: rdpmc_test: HOST_TSC user FAIL: vmware_backdoors: rdpmc_test: REAL_TIME user FAIL: vmware_backdoors: rdpmc_test: APPARENT_TIME user PASS: vmware_backdoors: rdpmc_test: RANDOM PMC user FAIL: vmware_backdoors: port_test: CMD_GETVERSION user PASS: vmware_backdoors: port_test: CMD_GETVERSION kernel FAIL: vmware_backdoors: port_test: CMD_ILLEGAL user PASS: vmware_backdoors: port_test: RANDOM port user SUMMARY: 11 tests, 5 unexpected failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844153] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1844153 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Incomplete Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775784] Re: inotify08 in LTP syscall test failed with X/X-LTS/X-HWE/A/B kernel
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775784 Title: inotify08 in LTP syscall test failed with X/X-LTS/X-HWE/A/B kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Released Bug description: <<>> tag=inotify08 stime=1527762360 cmdline="inotify08" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s inotify08.c:201: INFO: ovl/test_file ino=27918358, dev=8:1 inotify08.c:212: INFO: ovl/test_file ino=27918363, dev=8:1 inotify08.c:150: FAIL: didn't get event: mask=4 inotify08.c:150: FAIL: didn't get event: mask=20 inotify08.c:150: FAIL: didn't get event: mask=8 Summary: passed 0 failed 3 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24~16.04.1 ProcVersionSignature: User Name 4.15.0-22.24~16.04.1-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jun 8 08:08:27 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814237] Re: ubuntu_nbd_smoke_test failed with I/O error on X-4.15
** Tags added: 4.15 xenial -- 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/1814237 Title: ubuntu_nbd_smoke_test failed with I/O error on X-4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Bug description: Kernel: 4.15.0-45.48~16.04.1 creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-25789 Date: Thu Jan 31 14:42:42 UTC 2019 Host: onibi Kernel:4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 Machine: onibi x86_64 x86_64 CPUs online: 4 CPUs total:4 Page size: 4096 Pages avail: 1351388 Pages total: 2038431 Free space: Filesystem Size Used Avail Use% Mounted on udev3.9G 0 3.9G 0% /dev tmpfs 797M 17M 780M 3% /run /dev/sda1 917G 9.1G 861G 2% / tmpfs 3.9G 4.0K 3.9G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 797M 0 797M 0% /run/user/1000 tmpfs 100K 0 100K 0% /var/lib/lxd/shmounts tmpfs 100K 0 100K 0% /var/lib/lxd/devlxd cgmfs 100K 0 100K 0% /run/cgmanager/fs NBD device /dev/nbd0 created found nbd export NBD exports found: test starting client with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 succeeded after 0 attempt(s) checking ext4 on /dev/nbd0 fsck from util-linux 2.27.1 /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks mount: /dev/nbd0 on /mnt/nbd-test-25789 type ext4 (rw,relatime,data=ordered) mounted on /dev/nbd0 free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 1550112111 2% /mnt/nbd-test-25789 creating large file /mnt/nbd-test-25789/largefile -rw-r--r-- 1 root root 100M Jan 31 14:42 /mnt/nbd-test-25789/largefile free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-25789 removing file /mnt/nbd-test-25789/largefile unmounting /mnt/nbd-test-25789 stopping client disconnect, sock, done Found kernel warning, IO error and/or call trace echo [ 4593.254552] creating backing nbd image /tmp/nbd_image.img [ 4595.506134] NBD device /dev/nbd0 created [ 4595.557990] found nbd export [ 4596.604855] starting client with NBD device /dev/nbd0 [ 4596.606795] creating ext4 on /dev/nbd0 [ 4597.013721] mkfs on /dev/nbd0 succeeded after 0 attempt(s) [ 4597.390241] checking ext4 on /dev/nbd0 [ 4597.455371] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ 4597.460552] mounted on /dev/nbd0 [ 4597.461810] creating large file /mnt/nbd-test-25789/largefile [ 4599.056704] removing file /mnt/nbd-test-25789/largefile [ 4599.276298] unmounting /mnt/nbd-test-25789 [ 4600.319460] stopping client [ 4600.320083] block nbd0: NBD_DISCONNECT [ 4600.320127] block nbd0: shutting down sockets [ 4600.320267] nbd0: detected capacity change from 0 to 134217728 [ 4600.320306] print_req_error: 7 callbacks suppressed [ 4600.320308] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.325890] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.333002] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.338653] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.345687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.351253] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.358279] ldm_validate_partition_table(): Disk read failed. [ 4600.358305] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.363892] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.371075] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.376645] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.383687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.389230] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.396307] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.401819] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.408826] Dev nbd0: unable to read RDB block 0 [ 4600.413467] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.418955] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.425858] print_req_error: I/O error, dev nbd0, sector 24 [ 4600.431433] Buffer I/O error on dev nbd0, logical block 3, async page read [ 4600.438422]
[Kernel-packages] [Bug 1814295] Re: qa-regression-testing test_ulimit_stack_small fails on ppc64el/i386
** Tags added: i386 ppc64el ** Tags added: ubuntu-qrt-kernel-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/1814295 Title: qa-regression-testing test_ulimit_stack_small fails on ppc64el/i386 Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/ppc64el/l/linux/20190201_153123_8340c@/log.gz == FAIL: test_ulimit_stack_small (__main__.KernelNonSecurityTest) Ensure small stack limits are enforced -- Traceback (most recent call last): File "./test-kernel-security.py", line 2847, in test_ulimit_stack_small self.assertShellExitIn(expected, self._unpriv_cmd(["sh", "-c", "ulimit -s 1 && /bin/true"])) File "/tmp/autopkgtest.aOkL2y/build.mxm/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1151, in assertShellExitIn self.assertIn(rc, expected, msg + result + report) AssertionError: Got exit code 0, expected one of 139 Command: 'sudo', '-u', 'ubuntu', 'sh', '-c', 'ulimit -s 1 && /bin/true' Output: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1814295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814240] Re: ubuntu_zfs_xfs_generic 129 timeouted on node gonzo with X-4.15
** Tags added: 4.15 xenial ** Tags added: ubuntu-zfs-xfs-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814240 Title: ubuntu_zfs_xfs_generic 129 timeouted on node gonzo with X-4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Kernel: 4.15.0-45.48~16.04.1 Test 129 timeouted (20 min) on node gonzo, and all the following 30 tests have failed too. 1.01/31 15:53:20 INFO |ubuntu_zfs:0134| Running: /home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh 129 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src 2.01/31 15:53:20 DEBUG| utils:0116| Running '/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh 129 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src' 3.01/31 15:53:20 DEBUG| utils:0153| [stdout] Creating zfs pool testpool.. 4.01/31 15:53:23 DEBUG| utils:0153| [stdout] Creating zfs file systems test and scratch in testpool.. 5.01/31 15:53:25 DEBUG| utils:0153| [stdout] VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src 6.01/31 15:53:25 DEBUG| utils:0153| [stdout] FSTYP -- zfs 7.01/31 15:53:25 DEBUG| utils:0153| [stdout] PLATFORM -- Linux/x86_64 gonzo 4.15.0-45-generic 8.01/31 15:53:25 DEBUG| utils:0153| [stdout] MKFS_OPTIONS -- testpool/scratch 9.01/31 15:53:25 DEBUG| utils:0153| [stdout] MOUNT_OPTIONS -- testpool/scratch /mnt/scratch 10. 01/31 15:53:25 DEBUG| utils:0153| [stdout] I didn't see this issue in 4.15.0-44.47~16.04.1, but this test was not run with gonzo back then To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844153] Re: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot
My hypothesis on this is that grub boot stage UUID detection mechanism are not able to read UUID for crypto_LUKS partition. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Incomplete Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844153] [NEW] Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot
Public bug reported: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: boot grub luks uuid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Incomplete Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB
[Kernel-packages] [Bug 1844155] Re: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes
** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844155 Title: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes Status in linux package in Ubuntu: Confirmed Status in linux package in Debian: Unknown Bug description: This seems to have been fixed in 4.15 (finally), but is still an issue in the 4.4 kernel used on our builders, and possibly others as well (needs investigation). The original Debian bug report linked has more info, as well as the patchset on lkml at https://lkml.org/lkml/2018/7/25/409 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844153] Re: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot
I was able to completely reproduce it using VirtualBox environment by installing Ubuntu from scratch with encryption enabled and then adding the second disk and enabling encryption on it manually. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844153 Title: Manual root and boot encrypted LUKS non-lvm partition on EFI unable to boot Status in linux package in Ubuntu: Incomplete Bug description: Hello! I followed cryptsetup manual to setup LUKS encrypted root partition https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html - EFI bios - EFI partition 700Mb - LUKS encrypted partition containing both / and /boot - LUKS mapped device directly contains ext4 partition without LVM To do this I added a second disk, added EFI and root partions on it and copied all files preserving attributes and permissions. I modified files in etc and after chroot I executed: > update-grub > grub-install /dev/sdb After rebooting and disabling first disk (/dev/sda) I was immediately brought into grub shell I can notice what there is an error message flashes before booting "No such device: c740ceea-853c-487c-82ef-3d2138f9a7d7" I can also "source" (hd1,gpt1)/efi/ubuntu/grub.cfg and it will produce the same error. Also cryptodisk.mod module is not loaded. I can also add insmod ... lines into the (hd1,gpt1)/efi/ubuntu/grub.cfg but it does not help find partioon using following line: search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 If I try to type ls (hd1 it will show me following information: grub> ls (hd1) Possible partitions are: Device hd1: No known filesystem detected - Sector size 512B - Total size 10485760KiB Partition hd1,gpt1: Filesystem type fat, UUID C3AC-7168 - Partition start at 1024KiB - Total size 716800KiB Partition hd1,gpt2: No known filesystem detected - Partition start at 717824KiB - Total size 9767919.5KiB Relevant files: Mounting script I used to mount everything before chroot: cryptsetup open /dev/sdb2 root mount /dev/mapper/root root mount /dev/sdb1 root/boot/efi mount --bind /dev root/dev mount --bind /sys root/sys mount --bind /proc root/proc /etc/crypttab root UUID=c740ceea-853c-487c-82ef-3d2138f9a7d7 none luks,discard /etc/default/grub GRUB_DISABLE_OS_PROBER=true GRUB_ENABLE_CRYPTODISK=y /boot/efi/EFI/ubuntu/grub.cfg search.fs_uuid 85030321-f93d-47dc-aa4c-70bf751ad3f7 root cryptouuid/c740ceea853c487c82ef3d2138f9a7d7 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg > blkid /dev/sdb1: UUID="C3AC-7168" TYPE="vfat" PARTUUID="d50cd38a-ada3-f44a-bd39-0ea2f8355158" /dev/sdb2: UUID="c740ceea-853c-487c-82ef-3d2138f9a7d7" TYPE="crypto_LUKS" PARTUUID="e527fa37-f546-6041-b376-40d2463d0812" /dev/mapper/root: UUID="85030321-f93d-47dc-aa4c-70bf751ad3f7" TYPE="ext2" Relevant versions: Ubuntu 18.04.3 LTS cryptsetup 2:2.0.2-1ubuntu1.1 grub2-common 2.02-2ubuntu8.13 Cleanup script: umount root/dev umount root/sys umount root/proc umount root/boot/efi umount root sync Added GRUB_PRELOAD_MODULES: crypto gcry_rijndael gcry_sha256 pbkdf2 cryptodisk luks More links: - https://gitlab.com/cryptsetup/cryptsetup/wikis/LUKS-standard/on-disk-format.pdf - https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html#Simple-configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844155] [NEW] arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes
Public bug reported: This seems to have been fixed in 4.15 (finally), but is still an issue in the 4.4 kernel used on our builders, and possibly others as well (needs investigation). The original Debian bug report linked has more info, as well as the patchset on lkml at https://lkml.org/lkml/2018/7/25/409 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #904385 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904385 ** Also affects: linux (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904385 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844155 Title: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes Status in linux package in Ubuntu: Confirmed Status in linux package in Debian: Unknown Bug description: This seems to have been fixed in 4.15 (finally), but is still an issue in the 4.4 kernel used on our builders, and possibly others as well (needs investigation). The original Debian bug report linked has more info, as well as the patchset on lkml at https://lkml.org/lkml/2018/7/25/409 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842865] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289038/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842865] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289039/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774387] Re: inotify07 in LTP syscall test failed with X/X-LTS/A kernel
** Changed in: linux (Ubuntu Xenial) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Summary changed: - inotify07 in LTP syscall test failed with X/X-LTS/A kernel + inotify07 in LTP syscall test failed with X kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774387 Title: inotify07 in LTP syscall test failed with X kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: In Progress Status in linux source package in Artful: Won't Fix Bug description: The "inotify07" from the LTP syscall tests have failed on a testing node with X-LTS i386 kernel installed. <<>> tag=inotify07 stime=1527762360 cmdline="inotify07" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s inotify07.c:206: INFO: ovl/test_dir ino=27918358 inotify07.c:216: INFO: ovl/test_dir ino=27918358 inotify07.c:157: FAIL: didn't get event: mask=4004 inotify07.c:157: FAIL: didn't get event: mask=0020 inotify07.c:157: FAIL: didn't get event: mask=0008 inotify07.c:157: FAIL: didn't get event: mask=0004 Summary: passed 0 failed 4 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=37 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153~14.04.1 ProcVersionSignature: User Name 4.4.0-127.153~14.04.1-generic 4.4.128 Uname: Linux 4.4.0-127-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 Date: Thu May 31 10:19:30 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842865] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289036/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838921] Autopkgtest regression report (dkms/2.3-3ubuntu9.6)
All autopkgtests for the newly accepted dkms (2.3-3ubuntu9.6) for bionic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-430/430.26-0ubuntu0.18.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#dkms [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1838921 Title: priority of OBSOLETE_BY should higher than "force" Status in OEM Priority Project: New Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Committed Status in dkms source package in Disco: Fix Committed Bug description: [Impact] the priority of OBSOLETE_BY should higher than "force". #89 https://github.com/dell/dkms/issues/89 [Test case] 1. install the dkms package which already patched (also can be found from my test ppa[1]) 2. install a DKMS which has OBSOLETE_BY and FORCE e.g.ath10k of my testing ppa : [2] - the target dkms defined OBSOLETE_BY and FORCE - user install dkms on a system which installed kernel version less than OBSOLETE_BY and another kernel higher than OBSOLETE_BY - the dkms can be installed well. [Regression potential] medium as it touched the version sanity. This change land a change from upstream. [1]:https://code.launchpad.net/~alextu/+recipe/2.3-3ubuntu9.5-closes89 [2]:https://code.launchpad.net/~alextu/+recipe/2.3-3ubuntu9.5-closes89-dkms To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1838921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842865] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289037/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842865] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289042/+files/WifiSyslog.txt ** 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/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842865] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289041/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842865] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289040/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842865] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289033/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842865] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289034/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842865] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289035/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo
apport information ** Tags added: apport-collected ** Description changed: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: max1055 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-08-09 (37 days ago) + InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + IwConfig: + enp0s25 no wireless extensions. + + enp7s4no wireless extensions. + + lono wireless extensions. + MachineType: Hewlett-Packard HP Compaq dc5800 Microtower + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-62-generic N/A + linux-backports-modules-4.15.0-62-generic N/A + linux-firmware 1.173.9 + RfKill: + + Tags: bionic + Uname: Linux 4.15.0-62-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/26/2015 + dmi.bios.vendor: Hewlett-Packard + dmi.bios.version: 786F2 v01.60 + dmi.board.asset.tag: CZC8107S1Y + dmi.board.name: 2820h + dmi.board.vendor: Hewlett-Packard + dmi.chassis.asset.tag: CZC8107S1Y + dmi.chassis.type: 6 + dmi.chassis.vendor: Hewlett-Packard + dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: + dmi.product.family: 103C_53307F + dmi.product.name: HP Compaq dc5800 Microtower + dmi.sys.vendor: Hewlett-Packard ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289030/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq
[Kernel-packages] [Bug 1842865] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289031/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842865] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1842865/+attachment/5289032/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in gvfs: New Status in linux package in Ubuntu: Confirmed Bug description: When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
Hi Timo, if I remember correctly, there were some schools that were affected by this issue, but I wasn't able to reproduce it in the office due to lack of similar hardware. Unfortunately it's not easy to check which were those schools; but I can keep an eye on this issue, in case I hear about black screens in the near future -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814231] Re: linux 4.4.0-142.168 ADT test failure (ubuntu_vfat_stress): hung task on i386
** Tags added: ubuntu-vfat-stress ** Tags added: i386 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814231 Title: linux 4.4.0-142.168 ADT test failure (ubuntu_vfat_stress): hung task on i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190201_082722_4cb3e@/log.gz ubuntu_vfat_stress is causing a kernel hung task on xenial/linux i386: Started, PID 23212 Timed out waiting for stress-ng to finish Forcefully killing, PID 23212 (after 121 seconds) Found kernel warning and/or call trace: [ 3998.807995] Testing: --verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M --fallocate-bytes 2M --chdir 2 --rename 2 --hdd-write-size 512 [ 3998.832802] Created loop image vfat-test-23176/vfat-image-23176.img on /dev/loop0 [ 3999.936713] ubuntu_vfat_str (23176): drop_caches: 1 [ 3999.944908] ubuntu_vfat_str (23176): drop_caches: 2 [ 3999.949450] ubuntu_vfat_str (23176): drop_caches: 3 [ 3999.967248] VFAT options: allow_utime=20 [ 3999.967299] Stress test: /tmp/autopkgtest.ytglRN/build.6Ql/src/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng --verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M --fallocate-bytes 2M --chdir 2 --rename 2 --hdd-write-size 512 [ 3999.967318] Mount point: /mnt/vfat-test-23176 [ 3999.967994] Started, PID 23212 [ 4121.902337] Timed out waiting for stress-ng to finish [ 4121.902488] Forcefully killing, PID 23212 (after 121 seconds) [ 4200.180102] INFO: task stress-ng:23229 blocked for more than 120 seconds. [ 4200.18] Tainted: G OE 4.4.0-142-generic #168-Ubuntu [ 4200.185438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4200.186581] stress-ng D c1214654 0 23229 1 0x0004 [ 4200.186587] c5bc9ebc 0086 c5bc9ea4 c1214654 ce0a5b00 64d56897 03a3 [ 4200.186591] 6497d7cf 03a3 d8185dc0 d239a800 c5bca000 d00ce5e0 c5bc9f08 c5bc9ec8 [ 4200.186595] c17e194d c5bc9f08 c5bc9ef0 c12146ad d239a800 c10b5340 d00ce5e4 [ 4200.186598] Call Trace: [ 4200.186608] [] ? wb_queue_work+0xe4/0xf0 [ 4200.186613] [] schedule+0x2d/0x80 [ 4200.186616] [] wb_wait_for_completion+0x4d/0x90 [ 4200.186620] [] ? wake_atomic_t_function+0x70/0x70 [ 4200.186622] [] sync_inodes_sb+0x7d/0x1a0 [ 4200.186624] [] sync_inodes_one_sb+0x15/0x20 [ 4200.186628] [] iterate_supers+0xcd/0xd0 [ 4200.186630] [] ? SyS_tee+0x2a0/0x2a0 [ 4200.186632] [] sys_sync+0x3a/0xa0 [ 4200.186636] [] do_fast_syscall_32+0x9f/0x160 [ 4200.186639] [] sysenter_past_esp+0x3d/0x61 [ 4200.186641] INFO: task stress-ng:23242 blocked for more than 120 seconds. [ 4200.187628] Tainted: G OE 4.4.0-142-generic #168-Ubuntu [ 4200.188667] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4200.189947] stress-ng D c1214654 0 23242 1 0x0004 [ 4200.189952] c011bebc 0086 c011bea4 c1214654 dd922680 65d2d986 03a3 [ 4200.189955] 65bb3d70 03a3 d8185dc0 cef0b200 c011c000 d00ce5e0 c011bf08 c011bec8 [ 4200.189958] c17e194d c011bf08 c011bef0 c12146ad cef0b200 c10b5340 c5bc9edc [ 4200.189962] Call Trace: [ 4200.189965] [] ? wb_queue_work+0xe4/0xf0 [ 4200.189968] [] schedule+0x2d/0x80 [ 4200.189971] [] wb_wait_for_completion+0x4d/0x90 [ 4200.189973] [] ? wake_atomic_t_function+0x70/0x70 [ 4200.189975] [] sync_inodes_sb+0x7d/0x1a0 [ 4200.189978] [] sync_inodes_one_sb+0x15/0x20 [ 4200.189980] [] iterate_supers+0xcd/0xd0 [ 4200.189983] [] ? SyS_tee+0x2a0/0x2a0 [ 4200.189985] [] sys_sync+0x3a/0xa0 [ 4200.189987] [] do_fast_syscall_32+0x9f/0x160 [ 4200.189989] [] sysenter_past_esp+0x3d/0x61 This is not a regression, different call traces or errors have been reported by older versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1842865] [NEW] Xubuntu 18.04 sometimes freezes when turned on on logo
You have been subscribed to a public bug by Maxim Smih (stafik1993): When I turn off the computer, it hangs on the logo. The light on the system unit continues to light. Does not respond to the keyboard. Kernel version 5.0.0-27. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 5 09:44:35 2019 InstallationDate: Installed on 2019-08-09 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-09 (37 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. enp7s4no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-62-generic N/A linux-backports-modules-4.15.0-62-generic N/A linux-firmware 1.173.9 RfKill: Tags: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board.asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard ** Affects: gvfs Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug apport-collected bionic disco -- Xubuntu 18.04 sometimes freezes when turned on on logo https://bugs.launchpad.net/bugs/1842865 You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814237] Re: ubuntu_nbd_smoke_test failed with I/O error on X-4.15
** Tags added: ubuntu-nbd-smoke-test -- 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/1814237 Title: ubuntu_nbd_smoke_test failed with I/O error on X-4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Bug description: Kernel: 4.15.0-45.48~16.04.1 creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-25789 Date: Thu Jan 31 14:42:42 UTC 2019 Host: onibi Kernel:4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 Machine: onibi x86_64 x86_64 CPUs online: 4 CPUs total:4 Page size: 4096 Pages avail: 1351388 Pages total: 2038431 Free space: Filesystem Size Used Avail Use% Mounted on udev3.9G 0 3.9G 0% /dev tmpfs 797M 17M 780M 3% /run /dev/sda1 917G 9.1G 861G 2% / tmpfs 3.9G 4.0K 3.9G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 797M 0 797M 0% /run/user/1000 tmpfs 100K 0 100K 0% /var/lib/lxd/shmounts tmpfs 100K 0 100K 0% /var/lib/lxd/devlxd cgmfs 100K 0 100K 0% /run/cgmanager/fs NBD device /dev/nbd0 created found nbd export NBD exports found: test starting client with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 succeeded after 0 attempt(s) checking ext4 on /dev/nbd0 fsck from util-linux 2.27.1 /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks mount: /dev/nbd0 on /mnt/nbd-test-25789 type ext4 (rw,relatime,data=ordered) mounted on /dev/nbd0 free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 1550112111 2% /mnt/nbd-test-25789 creating large file /mnt/nbd-test-25789/largefile -rw-r--r-- 1 root root 100M Jan 31 14:42 /mnt/nbd-test-25789/largefile free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-25789 removing file /mnt/nbd-test-25789/largefile unmounting /mnt/nbd-test-25789 stopping client disconnect, sock, done Found kernel warning, IO error and/or call trace echo [ 4593.254552] creating backing nbd image /tmp/nbd_image.img [ 4595.506134] NBD device /dev/nbd0 created [ 4595.557990] found nbd export [ 4596.604855] starting client with NBD device /dev/nbd0 [ 4596.606795] creating ext4 on /dev/nbd0 [ 4597.013721] mkfs on /dev/nbd0 succeeded after 0 attempt(s) [ 4597.390241] checking ext4 on /dev/nbd0 [ 4597.455371] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ 4597.460552] mounted on /dev/nbd0 [ 4597.461810] creating large file /mnt/nbd-test-25789/largefile [ 4599.056704] removing file /mnt/nbd-test-25789/largefile [ 4599.276298] unmounting /mnt/nbd-test-25789 [ 4600.319460] stopping client [ 4600.320083] block nbd0: NBD_DISCONNECT [ 4600.320127] block nbd0: shutting down sockets [ 4600.320267] nbd0: detected capacity change from 0 to 134217728 [ 4600.320306] print_req_error: 7 callbacks suppressed [ 4600.320308] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.325890] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.333002] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.338653] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.345687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.351253] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.358279] ldm_validate_partition_table(): Disk read failed. [ 4600.358305] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.363892] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.371075] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.376645] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.383687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.389230] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.396307] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.401819] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.408826] Dev nbd0: unable to read RDB block 0 [ 4600.413467] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.418955] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.425858] print_req_error: I/O error, dev nbd0, sector 24 [ 4600.431433] Buffer I/O error on dev nbd0, logical block 3, async page read [
[Kernel-packages] [Bug 1764618] Re: python-API test in ubuntu_lxc will fail on X-kvm kernel
** Changed in: linux-kvm (Ubuntu)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
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/1764618
Title:
python-API test in ubuntu_lxc will fail on X-kvm kernel
Status in ubuntu-kernel-tests:
New
Status in linux-kvm package in Ubuntu:
New
Bug description:
Steps:
1. Deploy a KVM node with Xenial, install linux-kvm on it
2. Run the ubutnu_lxc test from autotest-client-tests
Output:
FAIL: python3: API
---
Using image from local cache
Unpacking the rootfs
---
You just created an Ubuntu container (release=xenial, arch=amd64,
variant=default)
To enable sshd, run: apt-get install openssh-server
For security reason, container images ship without user accounts
and without a root password.
Use lxc-attach or chroot directly into the rootfs to set a root password
or create user accounts.
Getting instance for '785bd96e-41ef-11e8-a707-5254004f0f0f'
Creating rootfs using 'download', arch=amd64
Testing the configuration
Testing the networking
Starting the container
Getting the interface names
Traceback (most recent call last):
File "/tmp/tmp.jDauiqznXt", line 109, in
assert(set(container.get_interfaces()) == set(('lo', 'eth0')))
AssertionError
If you try to intercept the ontainer.get_interfaces() result, you'll see:
('eth0', 'lo', 'sit0')
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1021-kvm 4.4.0-1021.26
ProcVersionSignature: User Name 4.4.0-1021.26-kvm 4.4.117
Uname: Linux 4.4.0-1021-kvm x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Tue Apr 17 03:46:14 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1764618/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842266] Re: Operation against ntfs in ubuntu_ltp_syscalls test will fail with EROFS
** No longer affects: ubuntu-kernel-tests ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => AaronMa (mapengyu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842266 Title: Operation against ntfs in ubuntu_ltp_syscalls test will fail with EROFS Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: New Bug description: This issue can only be found on AMD64 / i386 and s390x KVM (failed: EACCES on s390x KVM) Passed with ARM64. For P8, it will fail with btrfs before this. This issue seems to be new, as the test does not report that it supports ntfs with older kernel (4.4.0-157) tst_supported_fs_types.c:44: INFO: mkfs.btrfs does exist tst_supported_fs_types.c:60: INFO: Kernel supports vfat tst_supported_fs_types.c:44: INFO: mkfs.vfat does exist tst_supported_fs_types.c:83: INFO: Filesystem exfat is not supported tst_supported_fs_types.c:88: INFO: Skipping FUSE as requested by the test But with 4.4.161: tst_supported_fs_types.c:44: INFO: mkfs.vfat does exist tst_supported_fs_types.c:83: INFO: Filesystem exfat is not supported tst_supported_fs_types.c:60: INFO: Kernel supports ntfs tst_supported_fs_types.c:44: INFO: mkfs.ntfs does exist tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ntfs opts='' extra opts='' Failed to set locale, using default 'C'. The partition start sector was not specified for /dev/loop1 and it could not be obtained automatically. It has been set to 0. The number of sectors per track was not specified for /dev/loop1 and it could not be obtained automatically. It has been set to 0. The number of heads was not specified for /dev/loop1 and it could not be obtained automatically. It has been set to 0. To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set. Windows will not be able to boot from this device. tst_test.c:1108: INFO: Timeout per run is 0h 05m 00s safe_macros.c:225: BROK: sync_file_range02.c:47: open(mnt_point/test1,66,0644) failed: EROFS ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67~16.04.1 ProcVersionSignature: User Name 4.15.0-60.67~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-60-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Mon Sep 2 03:04:48 2019 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1842266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838961] Re: timer_create01 from ubuntu_ltp_syscalls failed on X-kvm / B-KVM
** Changed in: linux-kvm (Ubuntu) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- 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/1838961 Title: timer_create01 from ubuntu_ltp_syscalls failed on X-kvm / B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: New Status in linux-kvm source package in Bionic: New Bug description: The timer_create01 failed on X-kvm Steps to reproduce: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "timer_create01 timer_create01" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs <<>> tag=timer_create01 stime=1565000454 cmdline="timer_create01" contacts="" analysis=exit <<>> tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s incrementing stop timer_create01.c:48: INFO: Testing notification type: SIGEV_NONE timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: SIGEV_SIGNAL timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: SIGEV_THREAD timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: SIGEV_THREAD_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: NULL timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI Summary: passed 30 failed 10 skipped 0 warnings 0 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1052-kvm 4.4.0-1052.59 ProcVersionSignature: User Name 4.4.0-1052.59-kvm 4.4.181 Uname: Linux 4.4.0-1052-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Mon Aug 5 10:17:57 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage
[Kernel-packages] [Bug 1838961] Re: timer_create01 from ubuntu_ltp_syscalls failed on X-kvm / B-KVM
** Changed in: ubuntu-kernel-tests Assignee: Kai-Heng Feng (kaihengfeng) => Thadeu Lima de Souza Cascardo (cascardo) -- 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/1838961 Title: timer_create01 from ubuntu_ltp_syscalls failed on X-kvm / B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: New Status in linux-kvm source package in Bionic: New Bug description: The timer_create01 failed on X-kvm Steps to reproduce: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "timer_create01 timer_create01" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs <<>> tag=timer_create01 stime=1565000454 cmdline="timer_create01" contacts="" analysis=exit <<>> tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s incrementing stop timer_create01.c:48: INFO: Testing notification type: SIGEV_NONE timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: SIGEV_SIGNAL timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: SIGEV_THREAD timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: SIGEV_THREAD_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: NULL timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI Summary: passed 30 failed 10 skipped 0 warnings 0 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1052-kvm 4.4.0-1052.59 ProcVersionSignature: User Name 4.4.0-1052.59-kvm 4.4.181 Uname: Linux 4.4.0-1052-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Mon Aug 5 10:17:57 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1838961] Re: timer_create01 from ubuntu_ltp_syscalls failed on X-kvm / B-KVM
Hi, I found this same issue on a Power system. The RTC does not support
alarm there, so this will fail with -ENOTSUPP, which should be
-EOPNOTSUPP instead. See kernel patch at [1].
[1]
https://lore.kernel.org/lkml/20190903171802.28314-1-casca...@canonical.com/T/#u
That still require a change on LTP. That should be something like:
diff --git a/testcases/kernel/syscalls/timer_create/timer_create01.c
b/testcases/kernel/syscalls/timer_create/timer_create01.c
index 258b6444c..f1ed00e03 100644
--- a/testcases/kernel/syscalls/timer_create/timer_create01.c
+++ b/testcases/kernel/syscalls/timer_create/timer_create01.c
@@ -77,7 +77,7 @@ static void run(unsigned int n)
_timer_id));
if (TST_RET != 0) {
- if (possibly_unsupported(clock) && TST_ERR == EINVAL) {
+ if (possibly_unsupported(clock) && (TST_ERR == EINVAL
|| TST_ERR == ENOTSUP)) {
tst_res(TPASS | TTERRNO,
"%s unsupported, failed as expected",
get_clock_str(clock));
--
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/1838961
Title:
timer_create01 from ubuntu_ltp_syscalls failed on X-kvm / B-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-kvm package in Ubuntu:
New
Status in linux-kvm source package in Xenial:
New
Status in linux-kvm source package in Bionic:
New
Bug description:
The timer_create01 failed on X-kvm
Steps to reproduce:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "timer_create01 timer_create01" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs
<<>>
tag=timer_create01 stime=1565000454
cmdline="timer_create01"
contacts=""
analysis=exit
<<>>
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
incrementing stop
timer_create01.c:48: INFO: Testing notification type: SIGEV_NONE
timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME
timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC
timer_create01.c:93: PASS: Timer successfully created for
CLOCK_PROCESS_CPUTIME_ID
timer_create01.c:93: PASS: Timer successfully created for
CLOCK_THREAD_CPUTIME_ID
timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME
timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM:
???
timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM:
???
timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI
timer_create01.c:48: INFO: Testing notification type: SIGEV_SIGNAL
timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME
timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC
timer_create01.c:93: PASS: Timer successfully created for
CLOCK_PROCESS_CPUTIME_ID
timer_create01.c:93: PASS: Timer successfully created for
CLOCK_THREAD_CPUTIME_ID
timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME
timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM:
???
timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM:
???
timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI
timer_create01.c:48: INFO: Testing notification type: SIGEV_THREAD
timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME
timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC
timer_create01.c:93: PASS: Timer successfully created for
CLOCK_PROCESS_CPUTIME_ID
timer_create01.c:93: PASS: Timer successfully created for
CLOCK_THREAD_CPUTIME_ID
timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME
timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM:
???
timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM:
???
timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI
timer_create01.c:48: INFO: Testing notification type: SIGEV_THREAD_ID
timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME
timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC
timer_create01.c:93: PASS: Timer successfully created for
CLOCK_PROCESS_CPUTIME_ID
timer_create01.c:93: PASS: Timer successfully created for
CLOCK_THREAD_CPUTIME_ID
timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME
timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM:
???
timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM:
???
timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI
timer_create01.c:48: INFO: Testing notification type: NULL
timer_create01.c:93: PASS: Timer successfully created for
