[Kernel-packages] [Bug 1824569] Re: linux-aws 4.4.0-1080.90 ADT test failure for kernel selftests psock_tpacket
** Tags added: ubuntu-kernel-selftests ** Tags added: 4.4 aws -- 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/1824569 Title: linux-aws 4.4.0-1080.90 ADT test failure for kernel selftests psock_tpacket Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Xenial: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux-aws/20190412_071828_dc7ce@/log.gz 06:52:09 DEBUG| [stdout] running psock_tpacket test 06:52:09 DEBUG| [stdout] 06:52:09 ERROR| [stderr] info: count=0,0, expect=0,0 06:52:09 ERROR| [stderr] info: count=5,15, expect=15,5 06:52:09 ERROR| [stderr] info: count=20,15, expect=15,20 06:52:09 ERROR| [stderr] test: datapath 0x7 06:52:09 ERROR| [stderr] info: count=0,0, expect=0,0 06:52:09 ERROR| [stderr] info: count=5,15, expect=15,5 06:52:09 ERROR| [stderr] info: count=20,15, expect=15,20 06:52:09 ERROR| [stderr] test: datapath 0x2 06:52:09 ERROR| [stderr] info: count=0,0, expect=0,0 06:52:09 ERROR| [stderr] info: count=20,0, expect=20,0 06:52:09 ERROR| [stderr] info: count=20,0, expect=20,0 06:52:09 DEBUG| [stdout] [FAIL] 06:52:09 DEBUG| [stdout] selftests: run_afpackettests [PASS] 06:52:09 ERROR| [stderr] test: TPACKET_V1 with PACKET_RX_RING .walk_v0_rx: received 201 out of 100 pkts 06:52:11 DEBUG| [stdout] test_bpf: ok To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1824569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 kernel
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You 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: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix 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 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid 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 1831899] Re: Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in kernel virtual address space
Thx for re-trying on latest bionic kernel and confirming that the issue is gone. Closing ticket. -- You 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>? do_IRQ+0x8a/0xb8 05/29/19 13:24:06 ?<008e87f0>?
[Kernel-packages] [Bug 1843860] Re: 5.3.0-10 doesn't boot on my t480s with secure boot enabled
*** This bug is a duplicate of bug 1844101 *** https://bugs.launchpad.net/bugs/1844101 Yes, I assume it's the same bug. Julian and I were actually sitting next to each other yesterday trying to diagnose things. As the other bug has logs, let's mark this a duplicate of the other. ** This bug has been marked a duplicate of bug 1844101 5.3.0-10 crashes immediately in init_tis -> ... -> tpm_init -> ... -> tpm_tis_core_init.cold -> ... (never boots) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1843860 Title: 5.3.0-10 doesn't boot on my t480s with secure boot enabled Status in linux package in Ubuntu: Confirmed Bug description: I have no further information, sadly. The boot stops at the message "EFI stub: UEFI Secure Boot is enabled". Disabling secure boot or selecting an older kernel both work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831449] Re: memory in ubuntu_kvm_unit_tests failed on Oracle X-4.15
** Tags added: 4.15 oracle ubuntu-kvm-unit-tests xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1831449 Title: memory in ubuntu_kvm_unit_tests failed on Oracle X-4.15 Status in ubuntu-kernel-tests: New Status in linux-oracle package in Ubuntu: New Bug description: Need to run this on oracle manually to get the full output: TESTNAME=memory TIMEOUT=90s ACCEL= ./x86/run x86/memory.flat -smp 1 -cpu host FAIL memory (8 tests, 2 unexpected failures) But so far Oracle X-4.15 is the only cloud that's failing with this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831451] Re: access in ubuntu_kvm_unit_tests failed on Oracle 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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1831451 Title: access in ubuntu_kvm_unit_tests failed on Oracle X-4.15 Status in ubuntu-kernel-tests: New Status in linux-oracle package in Ubuntu: New Bug description: Need to run this on oracle manually to get the full output: TESTNAME=access TIMEOUT=90s ACCEL= ./x86/run x86/access.flat -smp 1 -cpu host FAIL access (timeout; duration=90s) But so far Oracle X-4.15 is the only cloud that's failing with this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831543] Re: Standard_A2_v2 Azure instance will have CPU in offline state
** Tags added: ubuntu-kernel-selftests -- 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/1831543 Title: Standard_A2_v2 Azure instance will have CPU in offline state Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Bug description: This needs to be investigated to see if it's been disabled intentionally. The cpu-hot-plug test shows there are 126 offlined CPUs. selftests: cpu-on-off-test.sh pid 9824's current affinity mask: 3 pid 9824's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-1 present_max = 1 Cpus in online state: 0-1 Cpus in offline state: 2-127 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 not ok 1..1 selftests: cpu-on-off-test.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743908] Re: MODSIGN: Couldn't get UEFI db list
Present on 18.04.3 and 16.04.6 (64 bit, LTS with latest updates) - $ dmesg | grep Couldn [2.215723] Couldn't get size: 0x800e [2.215759] MODSIGN: Couldn't get UEFI MokListRT $lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $ uname -a Linux ubuntu-bellera 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Acer TravelMate B118-M (TMB118-M-C4AL manufactured date 2019/05/23) - $ dmesg | grep Couldn [2.305514] Couldn't get size: 0x800e [2.305575] MODSIGN: Couldn't get UEFI MokListRT $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 Codename: xenial $ uname -a Linux ubuntu-bellera 4.15.0-62-generic #69~16.04.1-Ubuntu SMP Fri Sep 6 02:43:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Acer TravelMate B117-M (TMB117-M-C661 manufactured date 2016/07/18) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743908 Title: MODSIGN: Couldn't get UEFI db list Status in linux package in Ubuntu: Fix Released Bug description: Kernel is having problem loading or validating certificates. Looking over the internet looks like this is a kernel issue. Patchs from other distro: https://bugzilla.redhat.com/show_bug.cgi?id=1497559 - 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch - 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch - 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch [1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734' [1.203352] Couldn't get size: 0x800e [1.203354] MODSIGN: Couldn't get UEFI db list [1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys keyring [1.205102] Couldn't get size: 0x800e [1.205103] MODSIGN: Couldn't get UEFI dbx list ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wellington 1429 F pulseaudio /dev/snd/pcmC1D3p: wellington 1429 F...m pulseaudio /dev/snd/controlC1: wellington 1429 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 22:37:13 2018 HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e InstallationDate: Installed on 2018-01-16 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed root=UUID=aa7179de-345d-4e48-8bbd-6397120a155a ro amd_iommu=fullflush iommu=pt RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.169.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD5 R5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5R5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844245] [NEW] Integrate Intel SGX driver into linux-azure
Public bug reported: Intel is still trying to upstream the SGX driver, but in the meantime it would be desirable to have it available on the linux-azure kernel. The following version relies only on Kbuild: https://github.com/haimc-intel/SGXDataCenterAttestationPrimitives inker- ph1 ** Affects: linux-azure (Ubuntu) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1844245 Title: Integrate Intel SGX driver into linux-azure Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Xenial: New Status in linux-azure source package in Disco: New Bug description: Intel is still trying to upstream the SGX driver, but in the meantime it would be desirable to have it available on the linux-azure kernel. The following version relies only on Kbuild: https://github.com/haimc-intel/SGXDataCenterAttestationPrimitives inker-ph1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1844245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844247] [NEW] BT advertising packet wakes up the system from S3 and suspend-to-idle
Public bug reported:
[Impact]
The new feature added by below commit let BT device to wake the system from S3
and/or s2idle by its advertising packets
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
This feature wakes up the system randomly from an unpaired BLE device.
[Fix]
There is no easy way to fix this, so current solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by BT
devices after entered suspended.
[Regression]
Yes, it reverts the feature by waking up system from BT devices, but this
feature introduces regression, so I'd suggest to revert it.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem (Ubuntu Disco)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Eoan)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem (Ubuntu Eoan)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Ff-series)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem (Ubuntu Ff-series)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu Ff-series)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-oem (Ubuntu)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Ff-series)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Ff-series)
Status: New => In Progress
** Changed in: linux (Ubuntu Eoan)
Status: New => In Progress
** Changed in: linux (Ubuntu Disco)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1844247
Title:
BT advertising packet wakes up the system from S3 and suspend-to-idle
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux-oem source package in Bionic:
New
Status in linux source package in Disco:
In Progress
Status in linux-oem source package in Disco:
New
Status in linux source package in Eoan:
In Progress
Status in linux-oem source package in Eoan:
New
Status in linux source package in FF-Series:
In Progress
Status in linux-oem source package in FF-Series:
New
Bug description:
[Impact]
The new feature added by below commit let BT device to wake the system from
S3 and/or s2idle by its advertising packets
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
This feature wakes up the system randomly from an unpaired BLE device.
[Fix]
There is no easy way to fix this, so current solution for this is to revert
it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
Yes, it reverts the feature by waking up system from BT devices, but this
feature introduces regression, so I'd suggest to revert it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844247/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743908] Re: MODSIGN: Couldn't get UEFI db list
Oops! Sorry! Forgot to say that we are using Secure Boot Disabled on both computers (Acer TravelMate B117-M & B118-M). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743908 Title: MODSIGN: Couldn't get UEFI db list Status in linux package in Ubuntu: Fix Released Bug description: Kernel is having problem loading or validating certificates. Looking over the internet looks like this is a kernel issue. Patchs from other distro: https://bugzilla.redhat.com/show_bug.cgi?id=1497559 - 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch - 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch - 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch [1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734' [1.203352] Couldn't get size: 0x800e [1.203354] MODSIGN: Couldn't get UEFI db list [1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys keyring [1.205102] Couldn't get size: 0x800e [1.205103] MODSIGN: Couldn't get UEFI dbx list ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wellington 1429 F pulseaudio /dev/snd/pcmC1D3p: wellington 1429 F...m pulseaudio /dev/snd/controlC1: wellington 1429 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 22:37:13 2018 HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e InstallationDate: Installed on 2018-01-16 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed root=UUID=aa7179de-345d-4e48-8bbd-6397120a155a ro amd_iommu=fullflush iommu=pt RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.169.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD5 R5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5R5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844247] Re: BT advertising packet wakes up the system from S3 and suspend-to-idle
** Description changed:
[Impact]
The new feature added by below commit let BT device to wake the system from
S3 and/or s2idle by its advertising packets
-a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
+ a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
This feature wakes up the system randomly from an unpaired BLE device.
[Fix]
There is no easy way to fix this, so current solution for this is to revert
it.
-1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
+ 1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
- Yes, it reverts the feature by waking up system from BT devices, but this
feature introduces regression, so I'd suggest to revert it.
+ Yes, it reverts the feature by waking up system from s2idle by paired non-BLE
BT devices, but this feature introduces regression, so I'd suggest to revert it.
** Description changed:
[Impact]
- The new feature added by below commit let BT device to wake the system from
S3 and/or s2idle by its advertising packets
+ The new feature added by below commit let BT device to wake the system from
S3 and/or s2idle.
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
- This feature wakes up the system randomly from an unpaired BLE device.
+ But this feature also wakes up the system randomly from an unpaired BLE
device by its advertising packets.
[Fix]
- There is no easy way to fix this, so current solution for this is to revert
it.
+ There is no easy way to fix this and may requires firmware update, so current
solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
- Yes, it reverts the feature by waking up system from s2idle by paired non-BLE
BT devices, but this feature introduces regression, so I'd suggest to revert it.
+ Yes, it reverts the feature by waking up system from s2idle by paired BT
devices, but this feature introduces regression, so I'd suggest to revert it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1844247
Title:
BT advertising packet wakes up the system from S3 and suspend-to-idle
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux-oem source package in Bionic:
New
Status in linux source package in Disco:
In Progress
Status in linux-oem source package in Disco:
New
Status in linux source package in Eoan:
In Progress
Status in linux-oem source package in Eoan:
New
Status in linux source package in FF-Series:
In Progress
Status in linux-oem source package in FF-Series:
New
Bug description:
[Impact]
The new feature added by below commit let BT device to wake the system from
S3 and/or s2idle.
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
But this feature also wakes up the system randomly from an unpaired BLE
device by its advertising packets.
[Fix]
There is no easy way to fix this and may requires firmware update, so current
solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
Yes, it reverts the feature by waking up system from s2idle by paired BT
devices, but this feature introduces regression, so I'd suggest to revert it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844247/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842545] Re: bionic/linux-azure: -proposed tracker
** Tags removed: kernel-sru-cycle-2019.09.02-1 -- 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/1842545 Title: bionic/linux-azure: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lrm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842835 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Wednesday, 04. September 2019 03:56 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-azure-edge: bug 1842544 bionic/linux-azure/azure-kernel: bug 1842543 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842549] Re: bionic/linux-gcp: -proposed tracker
** Tags removed: kernel-sru-backport-of-1842841 ** Tags added: kernel-sru-backport-of-1842841 ** Tags removed: kernel-sru-backport-of-1842841 ** Tags added: kernel-sru-backport-of-1842841 ** Tags removed: kernel-sru-backport-of-1842841 ** Tags added: kernel-sru-backport-of-1842841 ** Tags removed: kernel-sru-backport-of-1842841 ** Tags added: kernel-sru-backport-of-1842841 ** Tags removed: kernel-sru-cycle-2019.09.02-1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1842549 Title: bionic/linux-gcp: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lrm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842841 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Wednesday, 04. September 2019 03:56 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-gcp-edge: bug 1842548 bionic/linux-gcp/gcp-kernel: bug 1842547 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844247] Re: BT advertising packet wakes up the system from S3 and suspend-to-idle
** Description changed:
[Impact]
- The new feature added by below commit let BT device to wake the system from
S3 and/or s2idle.
+ The new feature added by below commit let BT device to wake up the system
from S3 and/or s2idle.
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
But this feature also wakes up the system randomly from an unpaired BLE
device by its advertising packets.
[Fix]
There is no easy way to fix this and may requires firmware update, so current
solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
Yes, it reverts the feature by waking up system from s2idle by paired BT
devices, but this feature introduces regression, so I'd suggest to revert it.
** Description changed:
[Impact]
- The new feature added by below commit let BT device to wake up the system
from S3 and/or s2idle.
+ The new feature added by below commit let BT device to wake up the system
from S3 or s2idle.
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
But this feature also wakes up the system randomly from an unpaired BLE
device by its advertising packets.
[Fix]
There is no easy way to fix this and may requires firmware update, so current
solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
Yes, it reverts the feature by waking up system from s2idle by paired BT
devices, but this feature introduces regression, so I'd suggest to revert it.
** Description changed:
[Impact]
The new feature added by below commit let BT device to wake up the system
from S3 or s2idle.
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
But this feature also wakes up the system randomly from an unpaired BLE
device by its advertising packets.
[Fix]
- There is no easy way to fix this and may requires firmware update, so current
solution for this is to revert it.
+ There is no easy way to fix this and require firmware update, so current
solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
Yes, it reverts the feature by waking up system from s2idle by paired BT
devices, but this feature introduces regression, so I'd suggest to revert it.
** Description changed:
[Impact]
The new feature added by below commit let BT device to wake up the system
from S3 or s2idle.
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
But this feature also wakes up the system randomly from an unpaired BLE
device by its advertising packets.
[Fix]
- There is no easy way to fix this and require firmware update, so current
solution for this is to revert it.
+ There is no easy way to fix this and requires firmware update, so current
solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
Yes, it reverts the feature by waking up system from s2idle by paired BT
devices, but this feature introduces regression, so I'd suggest to revert it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1844247
Title:
BT advertising packet wakes up the system from S3 and suspend-to-idle
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux-oem source package in Bionic:
New
Status in linux source package in Disco:
In Progress
Status in linux-oem source package in Disco:
New
Status in linux source package in Eoan:
In Progress
Status in linux-oem source package in Eoan:
New
Status in linux source package in FF-Series:
In Progress
Status in linux-oem source package in FF-Series:
New
Bug description:
[Impact]
The new feature added by below commit let BT device to wake up the system
from S3 or s2idle.
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
But this feature also wakes up the system randomly from an unpaired BLE
device by its advertising packets.
[Fix]
There is no easy way to fix this and requires firmware update, so current
solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable
[Kernel-packages] [Bug 1833905] Re: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels
** Tags added: bionic -- 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/1833905 Title: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Issue found on C-KVM, from the test case content, these two tests are: * Call settimeofday and verify the time was changed. * Call settimeofday with invalid Args and verify that the call fails. <<>> tag=settimeofday01 stime=1561358482 cmdline="settimeofday01" contacts="" analysis=exit <<>> settimeofday011 TFAIL : settimeofday01.c:124: Test condition 1 failed settimeofday012 TPASS : Test condition 2 successful <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15 ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20 Uname: Linux 4.18.0-1015-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 Date: Mon Jun 24 06:41:26 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/1833905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833905] Re: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels
Spotted on kvm-4.15.0-1028 as well. -- 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/1833905 Title: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Issue found on C-KVM, from the test case content, these two tests are: * Call settimeofday and verify the time was changed. * Call settimeofday with invalid Args and verify that the call fails. <<>> tag=settimeofday01 stime=1561358482 cmdline="settimeofday01" contacts="" analysis=exit <<>> settimeofday011 TFAIL : settimeofday01.c:124: Test condition 1 failed settimeofday012 TPASS : Test condition 2 successful <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15 ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20 Uname: Linux 4.18.0-1015-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 Date: Mon Jun 24 06:41:26 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/1833905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833905] Re: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1833905 Title: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Issue found on C-KVM, from the test case content, these two tests are: * Call settimeofday and verify the time was changed. * Call settimeofday with invalid Args and verify that the call fails. <<>> tag=settimeofday01 stime=1561358482 cmdline="settimeofday01" contacts="" analysis=exit <<>> settimeofday011 TFAIL : settimeofday01.c:124: Test condition 1 failed settimeofday012 TPASS : Test condition 2 successful <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15 ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20 Uname: Linux 4.18.0-1015-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 Date: Mon Jun 24 06:41:26 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/1833905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842555] Re: bionic/linux-oracle-edge: -proposed tracker
** Tags removed: kernel-sru-backport-of-1842844 ** Tags added: kernel-sru-backport-of-1842844 ** Tags removed: kernel-sru-backport-of-1842844 ** Tags added: kernel-sru-backport-of-1842844 ** Tags removed: kernel-sru-cycle-2019.09.02-1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842555 Title: bionic/linux-oracle-edge: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842844 packages: main: linux-oracle-edge meta: linux-meta-oracle-edge signed: linux-signed-oracle-edge phase: Holding before Packaging phase-changed: Wednesday, 04. September 2019 03:57 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Jason Bassett, Sorry you are having a problem, but your laptop I believe has a different processor family in it, and the issue you are facing is likely not related to this issue. Please open a new bug report for your issue. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1
[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools
I understand, I just don't see how we can achieve this. You can have multiple linux-tools packages installed and you'll get different versions of libcpupower. We don't guarantee ABI stability so your running app needs to be linked to the version of the running kernel or it might no longer work. I just checked Debian and there you can have 2 different versions of libcpupower installed as well and depending on which is installed, the generic link points to a different (kernel) version of libcpupower. How is this expected to work if the ABI is different between the two versions? $ dpkg -l libcpupower-dev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===-===--= ii libcpupower-dev 5.2.9-2~bpo10+1 amd64CPU frequency and voltage scaling tools for Linux (development files) $ ls -l /usr/lib/x86_64-linux-gnu/libcpupower.so* lrwxrwxrwx 1 root root20 Aug 25 17:28 /usr/lib/x86_64-linux-gnu/libcpupower.so -> libcpupower.so.2.0.1 -rw-r--r-- 1 root root 26840 Aug 28 04:20 /usr/lib/x86_64-linux-gnu/libcpupower.so.0.0.1 lrwxrwxrwx 1 root root20 Aug 28 04:20 /usr/lib/x86_64-linux-gnu/libcpupower.so.1 -> libcpupower.so.0.0.1 lrwxrwxrwx 1 root root20 Aug 25 17:28 /usr/lib/x86_64-linux-gnu/libcpupower.so.2 -> libcpupower.so.2.0.1 -rw-r--r-- 1 root root 26840 Aug 25 17:28 /usr/lib/x86_64-linux-gnu/libcpupower.so.2.0.1 -- You 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 1833905] Re: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels
Not seeing this issue on Bionic guest w/ 4.15-kvm inside Bionic host w/ v4.15-generic host.: $ sudo ./testcases/kernel/syscalls/settimeofday/settimeofday01 -i 1000 | grep FAIL | wc -l 0 Maybe the host in question is also flaky? ** Changed in: ubuntu-kernel-tests Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- 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/1833905 Title: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Issue found on C-KVM, from the test case content, these two tests are: * Call settimeofday and verify the time was changed. * Call settimeofday with invalid Args and verify that the call fails. <<>> tag=settimeofday01 stime=1561358482 cmdline="settimeofday01" contacts="" analysis=exit <<>> settimeofday011 TFAIL : settimeofday01.c:124: Test condition 1 failed settimeofday012 TPASS : Test condition 2 successful <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15 ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20 Uname: Linux 4.18.0-1015-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 Date: Mon Jun 24 06:41:26 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/1833905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations
Olivier, Did this fix make it to Thunderbird? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801383 Title: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations Status in apport package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Fix Committed Bug description: When I apport-bug certain packages such as firefox for example, it uploads the WifiSyslog.txt file. The WifiSyslog may contain a list of all system connections enumerated in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has ever connected to that are found in the system-connections. This is a serious privacy risk and completely unnecessary information for most bug reports. Should either remove WifiSyslog as a requirement for packages that don't need it (should I report this to https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact information that may contain usernames and SSIDs from the log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 -0400:2018-11-01 19:17:30.982295751 -0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 11:24:20 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (50 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations
Hi Brian, Is this bug on your radar? Thanks! ** Changed in: apport (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801383 Title: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations Status in apport package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Fix Committed Bug description: When I apport-bug certain packages such as firefox for example, it uploads the WifiSyslog.txt file. The WifiSyslog may contain a list of all system connections enumerated in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has ever connected to that are found in the system-connections. This is a serious privacy risk and completely unnecessary information for most bug reports. Should either remove WifiSyslog as a requirement for packages that don't need it (should I report this to https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact information that may contain usernames and SSIDs from the log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 -0400:2018-11-01 19:17:30.982295751 -0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 11:24:20 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (50 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785687] Re: btrfs send can bypass DAC check with certain capability set
** Package changed: linux-signed (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/1785687 Title: btrfs send can bypass DAC check with certain capability set Status in linux package in Ubuntu: Incomplete Bug description: Expected: For btrfs tool with certain capabilities set(cap_fowner, cap_sys_admin), DAC check should not be by-passed when operating on subvol snapshot What happened instead: btrfs tool with certain capability(cap_fowner,cap_sys_admin) set can be used to by-pass DAC check on a snapshot, and gain read access to all files in a snapshot steps to reproduce: as root # dd if=/dev/zero of=/tmp/test.disk bs=1M count=128 # mkfs.btrfs /tmp/test.disk # mkdir -p /mnt/test # mount /tmp/test.disk /mnt/test/ # cd /mnt/test # btrfs subvol create snapshot # echo "this is a secret" > snapshot/1.secret # chmod 600 snapshot/1.secret # btrfs subvol snapshot -r snapshot snapshot-ro # setcap cap_fowner,cap_sys_admin+eip /bin/btrfs as non-root $ cd /mnt/test $ cat snapshot-ro/1.secret cat: snapshot-ro/1.secret: Permission denied $ btrfs send snapshot-ro > /tmp/snap $ strings /tmp/snap this is a secret ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 11:18:18 2018 InstallationDate: Installed on 2018-05-17 (80 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785687] Re: btrfs send can bypass DAC check with certain capability set
Hi, Have you reported this issue to the upstream developers? Thanks! ** Changed in: linux-signed (Ubuntu) Status: New => Incomplete -- 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/1785687 Title: btrfs send can bypass DAC check with certain capability set Status in linux package in Ubuntu: Incomplete Bug description: Expected: For btrfs tool with certain capabilities set(cap_fowner, cap_sys_admin), DAC check should not be by-passed when operating on subvol snapshot What happened instead: btrfs tool with certain capability(cap_fowner,cap_sys_admin) set can be used to by-pass DAC check on a snapshot, and gain read access to all files in a snapshot steps to reproduce: as root # dd if=/dev/zero of=/tmp/test.disk bs=1M count=128 # mkfs.btrfs /tmp/test.disk # mkdir -p /mnt/test # mount /tmp/test.disk /mnt/test/ # cd /mnt/test # btrfs subvol create snapshot # echo "this is a secret" > snapshot/1.secret # chmod 600 snapshot/1.secret # btrfs subvol snapshot -r snapshot snapshot-ro # setcap cap_fowner,cap_sys_admin+eip /bin/btrfs as non-root $ cd /mnt/test $ cat snapshot-ro/1.secret cat: snapshot-ro/1.secret: Permission denied $ btrfs send snapshot-ro > /tmp/snap $ strings /tmp/snap this is a secret ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 11:18:18 2018 InstallationDate: Installed on 2018-05-17 (80 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836873] Re: exec_stack from ubuntu_qrt_apparmor failed with T-4.4
Confirmed passed with 4.4.0-161.189~14.04.1 Thanks ** 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/1836873 Title: exec_stack from ubuntu_qrt_apparmor failed with T-4.4 Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: This issue cannot be reproduce on Xenial 4.4, probably related to Trusty. It looks like this is not a regression, at least it can be reproduced with 4.4.0-154-generic #181~14.04.1 Failure could be found across all architectures: running exec_stack /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11431 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (2 stacked - file)' was expected to 'fail'. Reason for failure expect errno 13 != 139 /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11433 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (2 stacked - otherfile)' was expected to 'fail'. Reason for failure expect errno 13 != 139 /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11435 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (2 stacked - thirdfile)' was expected to 'fail'. Reason for failure expect errno 13 != 139 /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11436 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (2 stacked - sharedfile)' was expected to 'pass'. Reason for failure 'killed by signal 11' /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11442 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (2 stacked - okcon)' was expected to 'pass'. Reason for failure 'killed by signal 11' /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11448 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (2 stacked - bad label)' was expected to 'fail'. Reason for failure 'killed by signal 11' /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11454 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (2 stacked - bad mode)' was expected to 'fail'. Reason for failure 'killed by signal 11' /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11549 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (3 stacked - file)' was expected to 'fail'. Reason for failure expect errno 13 != 139 /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11551 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (3 stacked - otherfile)' was expected to 'fail'. Reason for failure expect errno 13 != 139 /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11553 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (3 stacked - thirdfile)' was expected to 'fail'. Reason for failure expect errno 13 != 139 /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11554 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (3 stacked - sharedfile)' was expected to 'pass'. Reason for failure 'killed by signal 11' /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11560 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (3 stacked - okcon)' was expected to 'pass'. Reason for failure 'killed by signal 11' /tmp/testlibie9Zaq/source/trusty/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 11652 Segmentation fault $testexec "$@" > $outfile 2>&1 Error: transition failed. Test 'EXEC_STACK (3 stacked - old AA WARN)' was expected to 'pass'. Reason for failure 'killed by signal 11' Complete test report could be found here: https://pastebin.ubuntu.com/p/YH5cYVkC5p/ To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1836873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~ker
[Kernel-packages] [Bug 1841736] Re: Intel Killer(R) Wi-Fi 6 AX1650i/AX1650s 160MHz Wireless Network Adapter (201NGW) [8086:34f0] subsystem [1a56:1651] not supported
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841736 Title: Intel Killer(R) Wi-Fi 6 AX1650i/AX1650s 160MHz Wireless Network Adapter (201NGW) [8086:34f0] subsystem [1a56:1651] not supported Status in HWE Next: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Confirmed Status in linux-oem-osp1 source package in Disco: New Status in linux source package in Eoan: Confirmed Status in linux-oem-osp1 source package in Eoan: New Bug description: [SRU Justification] [Impact] These cards are currently not recognized correctly and trying to load non-existent firmware blob iwlwifi-QuQnj-b0-hr-b0-.ucode, so the device probing process fails and WiFi is therefore not functional. [Fix] Three new patches are required to bring up this device, and one of them, "handle switching killer Qu B0 NICs to C0", is still under review in iwlwifi-fixes tree. One previously SRU'ed patch, "add support for qu c-step devices", was replaced with the one in the mainline kernel tree due to a mandatory preprocessor symbol definition introduced in the differences. [Test Case] Tested on AX1650s/AX1650i, as well as 9462/9560. [Regression Risk] Low. These patches are mostly around adding support to new devices. == original description = iwlwifi cannot initialize this device and leave following error messages in dmesg: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-50.ucode failed with error -2 ... iwlwifi :00:14.3: no suitable firmware found! iwlwifi :00:14.3: minimum version required: iwlwifi-QuQnj-b0-hr-b0-39 iwlwifi :00:14.3: maximum version supported: iwlwifi-QuQnj-b0-hr-b0-50 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem-osp1 5.0.0.1017.18 ProcVersionSignature: Ubuntu 5.0.0-1017.19-oem-osp1 5.0.18 Uname: Linux 5.0.0-1017-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 15:53:18 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X16 InstallationDate: Installed on 2019-08-14 (14 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 SourcePackage: linux-meta-oem-osp1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1841736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838751] Re: Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas adapters(SAS3.5 onwards)
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838751
Title:
Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas
adapters(SAS3.5 onwards)
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
New
Status in linux source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
Fix Committed
Status in linux source package in Disco:
New
Status in linux-oem-osp1 source package in Disco:
New
Bug description:
[Impact]
Latest megaraid_sas and mpt3sas adapters which support Resizable BAR
with 1 MB BAR size fails to initialize during system resume from S3
sleep.
As per our findings the issue is caused by the below upstream commit:
d3252ace0bc652a1a24446b6a549f969bf99 ("PCI: Restore resized BAR
state on resume")
We see that the same commit has been ported to UBUNTU18.X - PCI:
Restore resized BAR state on resume (bsc#1105355).
the fix has been submitted to upstream
https://patchwork.kernel.org/patch/11058689/
please include this patch in the upcoming releases.please let me know
if additional information required.
https://bugzilla.kernel.org/show_bug.cgi?id=203939
[Test case]
See that suspend/resume works correctly after applying the patch
[Regression potential]
slim, itself fixes a regression
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838751/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840236] Re: Horizontal corrupted line at top of screen caused by framebuffer compression
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840236 Title: Horizontal corrupted line at top of screen caused by framebuffer compression Status in HWE Next: New Status in Linux: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: New Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: New Bug description: SRU Justification: [Impact] On IceLake platforms there might be a thin, horizon strap of corruption image at the top of screen randomly after some series of window operations and disappears within a second or so. This is found on multiple platforms and is quite annonying that results in bad user experience. [Fix] The upstream bug has been filed for previous platforms, e.g. GeminiLake for an year or so, still working in progress, and so far this only known work-around is to turn off framebuffer compression on affected platforms. [Test Case] The most easy way is to observe if such corruption appears during the transition from GDM to gnome-shell. [Regression Risk] Low. The work-around for GeminiLake was landed to Linux stable 4.14.125 and has been backported to B/D. === Original Description == This is an follow-up for https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on IceLake platforms. Right after GDM is login screen is rendered, there might be a thin strap of corrupted image at top of the display for a short while. Like f-d-o bug 108085, sometimes it can also be reproduced by clicking the date/time repeatedly to open and close the calendar several times. Etc. Known work-around so far is to append kernel boot param "i915.enable_fbc=0". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20 ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18 Uname: Linux 5.0.0-1018-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 15 16:41:01 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14 InstallationDate: Installed on 2019-08-12 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 SourcePackage: linux-signed-oem-osp1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1840236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
For the xenial/linux-hwe kernel, 4.15.0-62.69~16.04.1 with this fix has been published. Are you seeing this issue in xenial's 4.4 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/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Bug description: [Impact] Some fragmentation+NAT workloads will cause kernel BUG/Ooops. [Test case] sudo iptables -t nat -I POSTROUTING -j MASQUERADE sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6 [Regression potential] This could make fragmented packets stop flowing. So, make sure fragmented pings still work. ping 192.168.122.1 -s 6 still works, even with the above nat rule. Hello, there are multiple inquries in the mailcow GitHub issues over at https://github.com/mailcow/mailcow-dockerized/issues/2904 that the latest kernel linux-image-4.15.0-60-generic causes kernel panics when "- dns" setting is used within the docker-compose.yml file, for yet some unclear reasons. Multiple users on different systems (e.g. virtualized ones on VMware ESXi and KVM) were able to reproduce the same issue. I was also able to reproduce this constantly on a completely new deployed Ubuntu 18.04 VM (KVM) with a fresh mailcow installation. Steps to reproduce: 1. Install a clean Ubuntu 18.04(.03) machine 2. Upgrade the installation to linux-image-4.15.0-60-generic 3. Setup mailcow as instructed at https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes less than a minute, easy to reproduce) 4. Start mailcow with "dns"-settings specified in docker-compose file (Make sure using the older docker-compose version with dns settings: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml) 5. Wait a few minutes, then kernel crash appears Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow- dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2 I've attached the apport file to this bug. Please let me know if you need any kind of further information. (As this is my first bug report here, I hope I have included all required information helping you finding the cause.) Kind regards, Patrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu
** Changed in: linux-meta (Ubuntu Precise)
Status: New => Won't Fix
** Changed in: linux-meta-hwe (Ubuntu)
Status: New => Fix Released
** Changed in: linux-meta-hwe-edge (Ubuntu)
Status: New => Fix Released
** Changed in: linux-meta-lts-xenial (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1738259
Title:
need to ensure microcode updates are available to all bare-metal
installs of Ubuntu
Status in linux-meta package in Ubuntu:
Fix Released
Status in linux-meta-hwe package in Ubuntu:
Fix Released
Status in linux-meta-hwe-edge package in Ubuntu:
Fix Released
Status in linux-meta-lts-xenial package in Ubuntu:
Fix Released
Status in linux-meta-oem package in Ubuntu:
Fix Released
Status in linux-meta source package in Precise:
Won't Fix
Status in linux-meta source package in Trusty:
Fix Released
Status in linux-meta source package in Xenial:
Fix Released
Status in linux-meta-hwe source package in Xenial:
Fix Released
Status in linux-meta-hwe-edge source package in Xenial:
Fix Released
Status in linux-meta-lts-xenial source package in Xenial:
Fix Released
Status in linux-meta-oem source package in Xenial:
Fix Released
Status in linux-meta source package in Zesty:
Invalid
Status in linux-meta source package in Artful:
Fix Released
Status in linux-meta source package in Bionic:
Fix Released
Bug description:
From time to time, CPU vendors release updates to microcode that can
be loaded into the CPU from the OS. For x86, we have these updates
available in the archive as amd64-microcode and intel-microcode.
Sometimes, these microcode updates have addressed security issues with
the CPU. They almost certainly will again in the future.
We should ensure that all users of Ubuntu on baremetal x86 receive
these security updates, and have them applied to the CPU in early boot
where at all feasible.
Because these are hardware-dependent packages which we don't want to
install except on baremetal (so: not in VMs or containers), the
logical place to pull them into the system is via the kernel, so that
only the kernel baremetal flavors pull them in. This is analogous to
linux-firmware, which is already a dependency of the linux-
image-{lowlatency,generic} metapackages, and whose contents are
applied to the hardware by the kernel similar to microcode.
So, please update the linux-image-{lowlatency,generic} metapackages to
add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
and the corresponding hwe metapackages also.
Please time this change to coincide with the next updates of the
microcode packages in the archive.
I believe we will also need to promote the *-microcode packages to
main from restricted as part of this (again, by analogy with linux-
firmware).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1738259/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764618] Re: python-API test in ubuntu_lxc will fail on X-kvm kernel
Confirmed with 4.4.0-1056-kvm kernel. Failed program:
## Python3 testsuite
STRING="python3: API"
if [ ! -f /usr/share/doc/python3-lxc/examples/api_test.py.gz ]; then
ignore "$STRING"
else
OUT=$(mktemp)
PYTEST=$(mktemp)
cat /usr/share/doc/python3-lxc/examples/api_test.py.gz | gzip -d > $PYTEST
python3 $PYTEST >$OUT 2>&1 && pass "$STRING" || \
fail "$STRING" "python3" "$OUT"
rm $PYTEST
rm $OUT
fi
--
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 1833905] Re: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels
* Tested with the 4.15 generic kernel on the KVM node, test failed * Tested with the 4.4 generic kernel on the KVM host, test passed with 1000 iterations. -- 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/1833905 Title: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Issue found on C-KVM, from the test case content, these two tests are: * Call settimeofday and verify the time was changed. * Call settimeofday with invalid Args and verify that the call fails. <<>> tag=settimeofday01 stime=1561358482 cmdline="settimeofday01" contacts="" analysis=exit <<>> settimeofday011 TFAIL : settimeofday01.c:124: Test condition 1 failed settimeofday012 TPASS : Test condition 2 successful <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15 ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20 Uname: Linux 4.18.0-1015-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 Date: Mon Jun 24 06:41:26 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/1833905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844072] Re: nouveau core notifier timeout
A moment ago again in the logs: Sep 15 11:55:30 if kernel: [34041.145493] nouveau :07:00.0: DRM: core notifier timeout Sep 15 11:55:32 if kernel: [34043.145460] nouveau :07:00.0: DRM: wndw-0: timeout Sep 15 11:55:34 if kernel: [34045.142000] usb 5-1: new high-speed USB device number 3 using xhci_hcd Sep 15 11:55:34 if kernel: [34045.308976] usb 5-1: New USB device found, idVendor=0bda, idProduct=5412, bcdDevice= 1.13 and mouse and keyboard were dead. Reboot. So, this modifies the information: there is no relation with screen blanking, this happened while I was working. The USB device mentioned is $ lsusb ... Bus 005 Device 002: ID 0bda:5412 Realtek Semiconductor Corp. ... Will try the latest mainline 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/1844072 Title: nouveau core notifier timeout Status in linux package in Ubuntu: Incomplete Bug description: Newly installed Ubuntu 19.04 system. AMD Ryzen 3700X. NVIDIA GeForce RTX 2060. When the system is left for a while and the screen goes to sleep, then sometimes but not always, upon return there is no reaction to keyboard and mouse. Most likely the system is still running fine, but the only thing one can do is reboot. Afterwards, /var/log/kern.log shows lines like Sep 15 21:50:50 if kernel: [35590.756691] nouveau :07:00.0: DRM: core notifier timeout Sep 15 21:50:52 if kernel: [35592.756660] nouveau :07:00.0: DRM: wndw-0: timeout Ubuntu 5.0.0-27.28-generic 5.0.21 $ sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838278] Re: zfs-initramfs wont mount rpool
The issue seems to be related to a change in ZFS 0.8 initramfs script. The initramfs script for ZFS does a normal ZFS import. ZFS import now forces to export a pool before importing it back again on a different system. This is a security feature to ensure the same pool isn't imported on two different systems on the same time. I guess what happens is that the way you are installing the pool doesn't export it before the reboot, then you reboot to the new installed system (which has different ID), and so zfs import fails in the initramfs. We were wondering if we should import -f in the initramfs to force importing, that's a question for Colin K. I think? At least, we should ensure you find what didn't export the pool properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1838278 Title: zfs-initramfs wont mount rpool Status in zfs-linux package in Ubuntu: New Bug description: 1. Eoan 2. http://archive.ubuntu.com/ubuntu eoan/main amd64 zfs-initramfs amd64 0.8.1-1ubuntu7 [23.1 kB] 3. ZFS rootfs rpool is mounted at boot 4. Booting an image with a rootfs rpool: [0.00] Linux version 5.2.0-8-generic (buildd@lgw01-amd64-015) (gcc version 9.1.0 (Ubuntu 9.1.0-6ubuntu2)) #9-Ubuntu SMP Mon Jul 8 13:07:27 UTC 2019 (Ubuntu 5.2.0-8.9-generic 5.2.0) [0.00] Command line: BOOT_IMAGE=/ROOT/zfsroot@/boot/vmlinuz-5.2.0-8-generic root=ZFS=rpool/ROOT/zfsroot ro console=ttyS0 Command: /sbin/zpool import -N 'rpool' Message: cannot import 'rpool': pool was previously in use from another system. Last accessed by ubuntu (hostid=d24775ba) at Mon Jul 29 05:21:19 2019 The pool can be imported, use 'zpool import -f' to import the pool. Error: 1 Failed to import pool 'rpool'. Manually import the pool and exit. Note, this works fine under Disco, http://archive.ubuntu.com/ubuntu disco/main amd64 zfs-initramfs amd64 0.7.12-1ubuntu5 [22.2 kB] [4.773077] spl: loading out-of-tree module taints kernel. [4.777256] SPL: Loaded module v0.7.12-1ubuntu3 [4.779433] znvpair: module license 'CDDL' taints kernel. [4.780333] Disabling lock debugging due to kernel taint [5.713830] ZFS: Loaded module v0.7.12-1ubuntu5, ZFS pool version 5000, ZFS filesystem version 5 Begin: Sleeping for ... done. Begin: Importing ZFS root pool 'rpool' ... Begin: Importing pool 'rpool' using defaults ... done. Begin: Mounting 'rpool/ROOT/zfsroot' on '/root//' ... done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1838278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844072] Re: nouveau core notifier timeout
(Concerning the USB connection: my monitor is plugged into this NVIDIA card. On the left hand side of the monitor there are USB ports. The device 0bda:5412 that is mentioned immediately after the nouveau timeout is that USB port. Apparently the monitor is reprobed after that timeout.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844072 Title: nouveau core notifier timeout Status in linux package in Ubuntu: Incomplete Bug description: Newly installed Ubuntu 19.04 system. AMD Ryzen 3700X. NVIDIA GeForce RTX 2060. When the system is left for a while and the screen goes to sleep, then sometimes but not always, upon return there is no reaction to keyboard and mouse. Most likely the system is still running fine, but the only thing one can do is reboot. Afterwards, /var/log/kern.log shows lines like Sep 15 21:50:50 if kernel: [35590.756691] nouveau :07:00.0: DRM: core notifier timeout Sep 15 21:50:52 if kernel: [35592.756660] nouveau :07:00.0: DRM: wndw-0: timeout Ubuntu 5.0.0-27.28-generic 5.0.21 $ sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844245] Re: Integrate Intel SGX driver into linux-azure
Patches are already for review in the Ubuntu Kernel mailing list: https://lists.ubuntu.com/archives/kernel-team/2019-September/103746.html https://lists.ubuntu.com/archives/kernel-team/2019-September/103747.html https://lists.ubuntu.com/archives/kernel-team/2019-September/103748.html https://lists.ubuntu.com/archives/kernel-team/2019-September/103749.html ** Changed in: linux-azure (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Disco) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Xenial) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Disco) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- 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/1844245 Title: Integrate Intel SGX driver into linux-azure Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Xenial: In Progress Status in linux-azure source package in Disco: In Progress Bug description: Intel is still trying to upstream the SGX driver, but in the meantime it would be desirable to have it available on the linux-azure kernel. The following version relies only on Kbuild: https://github.com/haimc-intel/SGXDataCenterAttestationPrimitives inker-ph1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1844245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842838] Re: bionic/linux-gcp: 5.0.0-1016.16~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842553 packages: - lrm: linux-restricted-modules-gcp - main: linux-gcp - meta: linux-meta-gcp - signed: linux-signed-gcp + lrm: linux-restricted-modules-gcp + main: linux-gcp + meta: linux-meta-gcp + signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Friday, 13. September 2019 15:01 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- ready for review replaces: bug 1842549 trackers: - bionic/linux-gcp-edge: bug 1842837 - bionic/linux-gcp/gcp-kernel: bug 1842836 + bionic/linux-gcp-edge: bug 1842837 + bionic/linux-gcp/gcp-kernel: bug 1842836 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1842838 Title: bionic/linux-gcp: 5.0.0-1016.16~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842553 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Friday, 13. September 2019 15:01 UTC reason: promote-to-proposed: Stalled -- ready for review replaces: bug 1842549 trackers: bionic/linux-gcp-edge: bug 1842837 bionic/linux-gcp/gcp-kernel: bug 1842836 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842838] Re: bionic/linux-gcp: 5.0.0-1016.16~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: - https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1842590 + kernel-stable-master-bug: 1842553 packages: - lrm: linux-restricted-modules-gcp - main: linux-gcp - meta: linux-meta-gcp - signed: linux-signed-gcp + lrm: linux-restricted-modules-gcp + main: linux-gcp + meta: linux-meta-gcp + signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Friday, 13. September 2019 15:01 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- ready for review replaces: bug 1842549 trackers: - bionic/linux-gcp-edge: bug 1842837 - bionic/linux-gcp/gcp-kernel: bug 1842836 + bionic/linux-gcp-edge: bug 1842837 + bionic/linux-gcp/gcp-kernel: bug 1842836 variant: debs ** Tags removed: kernel-sru-backport-of-1842590 ** Tags added: kernel-sru-backport-of-1842553 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1842838 Title: bionic/linux-gcp: 5.0.0-1016.16~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842553 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Friday, 13. September 2019 15:01 UTC reason: promote-to-proposed: Stalled -- ready for review replaces: bug 1842549 trackers: bionic/linux-gcp-edge: bug 1842837 bionic/linux-gcp/gcp-kernel: bug 1842836 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842553] Re: disco/linux-gcp: 5.0.0-1016.16 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842561 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Thursday, 12. September 2019 21:56 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: - bionic/linux-gcp: bug 1842549 + bionic/linux-gcp: bug 1842838 bionic/linux-gke-5.0: bug 1842840 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1842553 Title: disco/linux-gcp: 5.0.0-1016.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842561 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Thursday, 12. September 2019 21:56 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-gcp: bug 1842838 bionic/linux-gke-5.0: bug 1842840 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833905] Re: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels
I'll find a system to test both 4.4 and 4.15 to make sure it's not hardware related. ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1833905 Title: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Issue found on C-KVM, from the test case content, these two tests are: * Call settimeofday and verify the time was changed. * Call settimeofday with invalid Args and verify that the call fails. <<>> tag=settimeofday01 stime=1561358482 cmdline="settimeofday01" contacts="" analysis=exit <<>> settimeofday011 TFAIL : settimeofday01.c:124: Test condition 1 failed settimeofday012 TPASS : Test condition 2 successful <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15 ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20 Uname: Linux 4.18.0-1015-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 Date: Mon Jun 24 06:41:26 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/1833905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in kernel virtual address space
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: In Progress => 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/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: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released 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 ?<
[Kernel-packages] [Bug 1829982] Re: ltp_acpi from kernel_misc test suite in LTP failed
[ 504.084541] ltp_acpi_test: get register: 11 val: [ 504.084944] ltp_acpi_test: get register: 12 val: [ 504.085318] ACPI Exception: AE_BAD_ADDRESS, acpi_read_bit_register the fail is on read ID 0x13, which is on PM2 control bit 0(ARB_DIS). this failure is caused by the PM2 aren't supported by firmeare. >From FADT table. [038h 0056 4] PM1A Event Block Address : B000 [03Ch 0060 4] PM1B Event Block Address : [040h 0064 4] PM1A Control Block Address : B004 [044h 0068 4] PM1B Control Block Address : [048h 0072 4]PM2 Control Block Address : [04Ch 0076 4] PM Timer Block Address : B008 [050h 0080 4] GPE0 Block Address : AFE0 [054h 0084 4] GPE1 Block Address : [058h 0088 1] PM1 Event Block Length : 04 [059h 0089 1] PM1 Control Block Length : 02 [05Ah 0090 1] PM2 Control Block Length : 00 [05Bh 0091 1]PM Timer Block Length : 04 So got AE_BAD_ADDRESS when the test reads from the register is expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829982 Title: ltp_acpi from kernel_misc test suite in LTP failed 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: New Bug description: startup='Wed May 22 07:02:13 2019' ltp_acpi1 TPASS : Test-case '0' ltp_acpi2 TPASS : Test-case '1' ltp_acpi3 TPASS : Test-case '2' ltp_acpi4 TPASS : Test-case '3' ltp_acpi5 TPASS : Test-case '4' ltp_acpi6 TPASS : Test-case '5' ltp_acpi7 TPASS : Test-case '6' ltp_acpi8 TPASS : Test-case '7' ltp_acpi9 TFAIL : ltp_acpi.c:139: Test-case '8' ltp_acpi 10 TPASS : Test-case '9' tag=ltp_acpi stime=1558508533 dur=0 exit=exited stat=1 core=no cu=0 cs=3 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:15:46 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/1829982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844138] Re: eoan/linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1844144 packages: main: linux-aws meta: linux-meta-aws - phase: Holding before Packaging - phase-changed: Monday, 16. September 2019 13:45 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 17. September 2019 11:43 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- 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/1844138 Title: eoan/linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1844144 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Packaging phase-changed: Tuesday, 17. September 2019 11:43 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844139] Re: eoan/linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1844144 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Packaging - phase-changed: Monday, 16. September 2019 13:45 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 17. September 2019 11:43 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- 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/1844139 Title: eoan/linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1844144 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Tuesday, 17. September 2019 11:43 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844139/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844141] Re: eoan/linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1844144 packages: main: linux-kvm meta: linux-meta-kvm - phase: Holding before Packaging - phase-changed: Monday, 16. September 2019 13:46 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 17. September 2019 11:43 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- 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/1844141 Title: eoan/linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1844144 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Packaging phase-changed: Tuesday, 17. September 2019 11:43 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844144] Re: eoan/linux: 5.3.0-11.12 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Packaging - phase-changed: Monday, 16. September 2019 13:51 UTC + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 17. September 2019 11:41 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:failed,meta:depwait,signed:depwait trackers: bionic/linux-hwe-edge: bug 1844142 eoan/linux-aws: bug 1844138 eoan/linux-azure: bug 1844139 eoan/linux-gcp: bug 1844140 eoan/linux-kvm: bug 1844141 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844144 Title: eoan/linux: 5.3.0-11.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Tuesday, 17. September 2019 11:41 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:failed,meta:depwait,signed:depwait trackers: bionic/linux-hwe-edge: bug 1844142 eoan/linux-aws: bug 1844138 eoan/linux-azure: bug 1844139 eoan/linux-gcp: bug 1844140 eoan/linux-kvm: bug 1844141 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844140] Re: eoan/linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1844144 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Packaging - phase-changed: Monday, 16. September 2019 13:46 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 17. September 2019 11:43 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1844140 Title: eoan/linux-gcp: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1844144 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Packaging phase-changed: Tuesday, 17. September 2019 11:43 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844072] Re: nouveau core notifier timeout
Can you please attach full dmesg? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844072 Title: nouveau core notifier timeout Status in linux package in Ubuntu: Incomplete Bug description: Newly installed Ubuntu 19.04 system. AMD Ryzen 3700X. NVIDIA GeForce RTX 2060. When the system is left for a while and the screen goes to sleep, then sometimes but not always, upon return there is no reaction to keyboard and mouse. Most likely the system is still running fine, but the only thing one can do is reboot. Afterwards, /var/log/kern.log shows lines like Sep 15 21:50:50 if kernel: [35590.756691] nouveau :07:00.0: DRM: core notifier timeout Sep 15 21:50:52 if kernel: [35592.756660] nouveau :07:00.0: DRM: wndw-0: timeout Ubuntu 5.0.0-27.28-generic 5.0.21 $ sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 kernel
The issue tested by LTP testcase inotify07 has been fixed by commit: 31747eda41ef "ovl: hash directory inodes for fsnotify" >From this upstream commit: "The reported issue dates back to initial version of overlayfs, but this patch depends on ovl_inode code that was introduced in kernel v4.13." Our Xenial 4.4 kernel doesn't have the ovl_inode code, so the solution is to blacklist this testcase for kernels older than 4.13. -- You 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: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix 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 1831899] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-09-17 07:40 EDT--- IBM Bugzilla status-> closed, Fix Released with 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/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: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released 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 1842820] Re: xenial/linux-azure: -proposed tracker
*** This bug is a duplicate of bug 1842587 *** https://bugs.launchpad.net/bugs/1842587 ** Tags removed: kernel-sru-backport-of-1842828 ** Tags added: kernel-sru-backport-of-1842828 ** Tags removed: kernel-sru-backport-of-1842828 ** Tags added: kernel-sru-backport-of-1842828 ** Tags removed: kernel-sru-cycle-2019.09.02-2 -- 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/1842820 Title: xenial/linux-azure: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Thursday, 05. September 2019 04:34 UTC reason: prepare-package: Holding -- waiting for master bug replaces: bug 1842587 trackers: trusty/linux-azure: bug 1842819, bug 1842585 xenial/linux-azure-edge: bug 1842818, bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583, bug 1842816 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842813] Re: xenial/linux-oracle: -proposed tracker
** Tags removed: kernel-sru-backport-of-1842814 ** Tags added: kernel-sru-backport-of-1842814 ** Tags removed: kernel-sru-backport-of-1842814 ** Tags added: kernel-sru-backport-of-1842814 ** Tags removed: kernel-sru-backport-of-1842814 ** Tags added: kernel-sru-backport-of-1842814 ** Tags removed: kernel-sru-cycle-2019.09.02-2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1842813 Title: xenial/linux-oracle: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842814 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Packaging phase-changed: Thursday, 05. September 2019 04:33 UTC reason: prepare-package: Holding -- waiting for master bug replaces: bug 1842580 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You 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) TES
[Kernel-packages] [Bug 1842585] Re: trusty/linux-azure: -proposed tracker
*** This bug is a duplicate of bug 1842819 *** https://bugs.launchpad.net/bugs/1842819 ** Tags removed: kernel-sru-cycle-2019.09.02-1 -- 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/1842585 Title: trusty/linux-azure: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842587 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Friday, 06. September 2019 05:47 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842823] Re: xenial/linux-gcp: -proposed tracker
*** This bug is a duplicate of bug 1842590 *** https://bugs.launchpad.net/bugs/1842590 ** Tags removed: kernel-sru-backport-of-1842828 ** Tags added: kernel-sru-backport-of-1842828 ** Tags removed: kernel-sru-cycle-2019.09.02-2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1842823 Title: xenial/linux-gcp: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842828 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Thursday, 05. September 2019 04:34 UTC reason: prepare-package: Holding -- waiting for master bug replaces: bug 1842590 trackers: xenial/linux-gcp/gcp-kernel: bug 1842821, bug 1842588 xenial/linux-gcp/gke-kernel: bug 1842589, bug 1842822 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842590] Re: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: - https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842828 packages: - main: linux-gcp - meta: linux-meta-gcp - signed: linux-signed-gcp + main: linux-gcp + meta: linux-meta-gcp + signed: linux-signed-gcp phase: Signoff phase-changed: Thursday, 12. September 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress - security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Stalled -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: - bionic/linux-gcp: bug 1842838 - bionic/linux-gke-5.0: bug 1842840 - xenial/linux-gcp/gcp-kernel: bug 1842588 - xenial/linux-gcp/gke-kernel: bug 1842589 + xenial/linux-gcp/gcp-kernel: bug 1842588 + xenial/linux-gcp/gke-kernel: bug 1842589 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1842590 Title: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842828 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Thursday, 12. September 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1842588 xenial/linux-gcp/gke-kernel: bug 1842589 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774394] Re: fcntl35 / fcntl35_64 in LTP syscall test failed with T/X/X-LTS kernel
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-lts-xenial (Ubuntu Xenial) 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/1774394 Title: fcntl35 / fcntl35_64 in LTP syscall test failed with T/T-LTS/X kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-lts-xenial package in Ubuntu: New Status in linux source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux source package in Xenial: New Status in linux-lts-xenial source package in Xenial: New Bug description: The "fcntl35" and "fcntl35_64" from the LTP syscall tests have failed on a testing node with T-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <>> tag=fcntl35 stime=1527764565 cmdline="fcntl35" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> <<>> tag=fcntl35_64 stime=1527764565 cmdline="fcntl35_64" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154~14.04.1 ProcVersionSignature: User Name 4.4.0-128.154~14.04.1-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: i386 Date: Thu May 31 11:05:58 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/1774394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653597] Re: libhugetlbfs test suite failed with brk_near_huge test
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Connor Kuehl (connork) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1653597 Title: libhugetlbfs test suite failed with brk_near_huge test Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Bug description: Kernel: 4.8.0-34.36 The libhugetlbfs failed with the brk_near_huge test on x86_64(gce) 12/24 04:59:42 DEBUG| utils:0153| [stdout] truncate_above_4GB (2M: 64): PASS 12/24 04:59:42 ERROR| utils:0153| [stderr] brk_near_huge: malloc.c:2403: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed. 12/24 04:59:42 DEBUG| utils:0153| [stdout] brk_near_huge (2M: 64): 12/24 04:59:42 DEBUG| utils:0153| [stdout] task-size-overrun (2M: 64): PASS Full log: http://pastebin.ubuntu.com/23732201/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1653597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 kernel
Fix sent to kernel-team mailing-list: https://lists.ubuntu.com/archives/kernel-team/2019-September/103750.html ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium -- You 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: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix 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 1842826] Re: xenial/linux-deeplens: -proposed tracker
** Tags removed: kernel-sru-cycle-2019.09.02-2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842826 Title: xenial/linux-deeplens: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842827 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Holding before Packaging phase-changed: Thursday, 05. September 2019 04:35 UTC reason: prepare-package: Holding -- waiting for master bug replaces: bug 1842592 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842590] Re: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842828 packages: - main: linux-gcp - meta: linux-meta-gcp - signed: linux-signed-gcp + main: linux-gcp + meta: linux-meta-gcp + signed: linux-signed-gcp phase: Signoff phase-changed: Thursday, 12. September 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress - security-signoff: Stalled -- waiting for signoff - verification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Stalled -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: - xenial/linux-gcp/gcp-kernel: bug 1842588 - xenial/linux-gcp/gke-kernel: bug 1842589 + xenial/linux-gcp/gcp-kernel: bug 1842588 + xenial/linux-gcp/gke-kernel: bug 1842589 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1842590 Title: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842828 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Thursday, 12. September 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1842588 xenial/linux-gcp/gke-kernel: bug 1842589 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774394] Re: fcntl35 / fcntl35_64 in LTP syscall test failed with T/T-LTS/X kernel
** Summary changed: - fcntl35 / fcntl35_64 in LTP syscall test failed with T/X/X-LTS kernel + fcntl35 / fcntl35_64 in LTP syscall test failed with T/T-LTS/X kernel ** Description changed: The "fcntl35" and "fcntl35_64" from the LTP syscall tests have failed on - a testing node with X-LTS i386 kernel installed (they were not tested on + a testing node with T-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <>> tag=fcntl35 stime=1527764565 cmdline="fcntl35" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> - <<>> tag=fcntl35_64 stime=1527764565 cmdline="fcntl35_64" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154~14.04.1 ProcVersionSignature: User Name 4.4.0-128.154~14.04.1-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: i386 Date: Thu May 31 11:05:58 2018 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + 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) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774394 Title: fcntl35 / fcntl35_64 in LTP syscall test failed with T/T-LTS/X kernel Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-lts-xenial package in Ubuntu: New Status in linux source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux source package in Xenial: New Status in linux-lts-xenial source package in Xenial: New Bug description: The "fcntl35" and "fcntl35_64" from the LTP syscall tests have failed on a testing node with T-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <>> tag=fcntl35 stime=1527764565 cmdline="fcntl35" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> <<>> tag=fcntl35_64 stime=1527764565 cmdline="fcntl35_64" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154~14.04.1 ProcVersionSignature: User Name 4.4.0-128.154~14.04.1-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: i386 Date: Thu May 31 11:05:58 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/1774394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help
[Kernel-packages] [Bug 1774394] Re: fcntl35 / fcntl35_64 in LTP syscall test failed with T/T-LTS/X kernel
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774394 Title: fcntl35 / fcntl35_64 in LTP syscall test failed with T/T-LTS/X kernel Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-lts-xenial package in Ubuntu: New Status in linux source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux source package in Xenial: New Status in linux-lts-xenial source package in Xenial: New Bug description: The "fcntl35" and "fcntl35_64" from the LTP syscall tests have failed on a testing node with T-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <>> tag=fcntl35 stime=1527764565 cmdline="fcntl35" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> <<>> tag=fcntl35_64 stime=1527764565 cmdline="fcntl35_64" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154~14.04.1 ProcVersionSignature: User Name 4.4.0-128.154~14.04.1-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: i386 Date: Thu May 31 11:05:58 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/1774394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations
Marc, the version currently in eoan-proposed has the fix. I'm working on addressing autopkgtest issues in related packages that prevent thunderbird from migrating to the release pocket. Once sorted out in eoan, I'll proceed to preparing updates for all stable releases, including this fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801383 Title: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations Status in apport package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Fix Committed Bug description: When I apport-bug certain packages such as firefox for example, it uploads the WifiSyslog.txt file. The WifiSyslog may contain a list of all system connections enumerated in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has ever connected to that are found in the system-connections. This is a serious privacy risk and completely unnecessary information for most bug reports. Should either remove WifiSyslog as a requirement for packages that don't need it (should I report this to https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact information that may contain usernames and SSIDs from the log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 -0400:2018-11-01 19:17:30.982295751 -0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 11:24:20 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (50 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784535] Re: ubuntu_quota_smoke_test failed with KVM kernel
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1784535 Title: ubuntu_quota_smoke_test failed with KVM kernel Status in ubuntu-kernel-tests: Confirmed 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 Status in linux-kvm source package in Cosmic: New Bug description: According to Kamal's comment: CONFIG_QUOTA (and various other quota-related-looking configs) appear to be enabled already in the linux-kvm kernels -- but the required modules just end up in the regular linux-modules package (e.g. linux-modules-x.y.z-a.b-kvm) However even with the linux-modules-x.y.z-a.b-kvm package installed, this test will still fail with KVM kernel. $ sudo /home/ubuntu/autotest/client/tests/ubuntu_quota_smoke_test/ubuntu_quota_smoke_test.sh Using block device /dev/loop0 for path /home/ubuntu/mnt PASSED (quotacheck -vucmg) quotaon: using /home/ubuntu/mnt/aquota.group on /dev/loop0 [/home/ubuntu/mnt]: No such process quotaon: Quota format not supported in kernel. quotaon: using /home/ubuntu/mnt/aquota.user on /dev/loop0 [/home/ubuntu/mnt]: No such process quotaon: Quota format not supported in kernel. FAILED (quotaon -v) Summary: 1 passed, 1 failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1016-kvm 4.15.0-1016.16 ProcVersionSignature: User Name 4.15.0-1016.16-kvm 4.15.18 Uname: Linux 4.15.0-1016-kvm x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 31 03:59:45 2018 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/1784535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
The syscall is not implemented on FUSE which ntfs uses. LTP sync_file_range02 testcase skip FUSE on purpose. No failure reported by testcase, just error in log. So let's ignore this issue. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842266 Title: Operation against ntfs in ubuntu_ltp_syscalls test will fail with EROFS Status in ubuntu-kernel-tests: Won't Fix 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 1841956] Re: ubuntu_sysdig fails on kvm kernels
When trying to load sysdig-probe in linux-kvm, I get the following errors: [ 1566.950603] sysdig_probe: Unknown symbol tracepoint_probe_unregister (err 0) [ 1566.950810] sysdig_probe: Unknown symbol for_each_kernel_tracepoint (err 0) [ 1566.950816] sysdig_probe: Unknown symbol tracepoint_probe_register (err 0) That seems to be caused by the lack of CONFIG_TRACING and CONFIG_FTRACE in the linux-kvm config. ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-kvm (Ubuntu) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => In Progress -- 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/1841956 Title: ubuntu_sysdig fails on kvm kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Bionic: In Progress Bug description: Bionic, Linux-Kvm: 4.15.0-1043.43 The module appears to load, however it may be that the service itself still does not start, there are no errors in the logs, just the following: 08/29 11:20:26 DEBUG| utils:0153| [stdout] == sysdig smmoke test to trace dd, cat, read and writes == 08/29 11:20:26 DEBUG| utils:0153| [stdout] Limiting raw capture file to 16384 blocks 08/29 11:20:26 DEBUG| utils:0153| [stdout] Try 1 of 10 08/29 11:21:13 DEBUG| utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start? 08/29 11:21:21 ERROR| utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory 08/29 11:21:21 DEBUG| utils:0153| [stdout] Raw capture file is 0 Mbytes 08/29 11:21:21 DEBUG| utils:0153| [stdout] Converted events file is 0 Mbytes 08/29 11:21:21 DEBUG| utils:0153| [stdout] Try 2 of 10 08/29 11:22:08 DEBUG| utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start? 08/29 11:22:16 ERROR| utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory 08/29 11:22:16 DEBUG| utils:0153| [stdout] Raw capture file is 0 Mbytes 08/29 11:22:16 DEBUG| utils:0153| [stdout] Converted events file is 0 Mbytes 08/29 11:22:16 DEBUG| utils:0153| [stdout] Try 3 of 10 08/29 11:23:03 DEBUG| utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start? Will require some additional triage. Summary: 0 passed, 3 failed stderr: stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1841956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Touchpad again stopped working, "disappeared" from the xinput list on kernel upgrade to 5.0.0-27. Works again when reverted to 5.0.0-25. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774394] Re: fcntl35 / fcntl35_64 in LTP syscall test failed with T/T-LTS/X kernel
This testcase is now passing on 4.4 kernels. ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Released ** No longer affects: linux-lts-xenial (Ubuntu Xenial) ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux-lts-xenial (Ubuntu) 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/1774394 Title: fcntl35 / fcntl35_64 in LTP syscall test failed with T/T-LTS/X kernel Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-lts-xenial package in Ubuntu: Fix Released Status in linux source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux source package in Xenial: Fix Released Bug description: The "fcntl35" and "fcntl35_64" from the LTP syscall tests have failed on a testing node with T-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <>> tag=fcntl35 stime=1527764565 cmdline="fcntl35" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> <<>> tag=fcntl35_64 stime=1527764565 cmdline="fcntl35_64" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154~14.04.1 ProcVersionSignature: User Name 4.4.0-128.154~14.04.1-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: i386 Date: Thu May 31 11:05:58 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/1774394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829982] Re: ltp_acpi from kernel_misc test suite in LTP failed
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Ivan Hu (ivan.hu) ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829982 Title: ltp_acpi from kernel_misc test suite in LTP failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: New Bug description: startup='Wed May 22 07:02:13 2019' ltp_acpi1 TPASS : Test-case '0' ltp_acpi2 TPASS : Test-case '1' ltp_acpi3 TPASS : Test-case '2' ltp_acpi4 TPASS : Test-case '3' ltp_acpi5 TPASS : Test-case '4' ltp_acpi6 TPASS : Test-case '5' ltp_acpi7 TPASS : Test-case '6' ltp_acpi8 TPASS : Test-case '7' ltp_acpi9 TFAIL : ltp_acpi.c:139: Test-case '8' ltp_acpi 10 TPASS : Test-case '9' tag=ltp_acpi stime=1558508533 dur=0 exit=exited stat=1 core=no cu=0 cs=3 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:15:46 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/1829982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844144] Re: eoan/linux: 5.3.0-11.12 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Tuesday, 17. September 2019 11:41 UTC - reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:failed,meta:depwait,signed:depwait trackers: bionic/linux-hwe-edge: bug 1844142 eoan/linux-aws: bug 1844138 eoan/linux-azure: bug 1844139 eoan/linux-gcp: bug 1844140 eoan/linux-kvm: bug 1844141 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844144 Title: eoan/linux: 5.3.0-11.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Tuesday, 17. September 2019 11:41 UTC trackers: bionic/linux-hwe-edge: bug 1844142 eoan/linux-aws: bug 1844138 eoan/linux-azure: bug 1844139 eoan/linux-gcp: bug 1844140 eoan/linux-kvm: bug 1844141 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774394] Re: fcntl35 / fcntl35_64 in LTP syscall test failed with T/T-LTS/X kernel
** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: New => Fix Released ** Changed in: linux (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774394 Title: fcntl35 / fcntl35_64 in LTP syscall test failed with T/T-LTS/X kernel Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Fix Released Status in linux-lts-xenial package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Bug description: The "fcntl35" and "fcntl35_64" from the LTP syscall tests have failed on a testing node with T-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <>> tag=fcntl35 stime=1527764565 cmdline="fcntl35" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> <<>> tag=fcntl35_64 stime=1527764565 cmdline="fcntl35_64" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154~14.04.1 ProcVersionSignature: User Name 4.4.0-128.154~14.04.1-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: i386 Date: Thu May 31 11:05:58 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/1774394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774394] Re: fcntl35 / fcntl35_64 in LTP syscall test failed with T/T-LTS/X kernel
Setting priority to low as Trusty is now ESM. ** Changed in: ubuntu-kernel-tests Status: In Progress => Triaged ** Changed in: ubuntu-kernel-tests Importance: Medium => Low ** Changed in: ubuntu-kernel-tests Assignee: Kleber Sacilotto de Souza (kleber-souza) => (unassigned) ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774394 Title: fcntl35 / fcntl35_64 in LTP syscall test failed with T/T-LTS/X kernel Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Fix Released Status in linux-lts-xenial package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Bug description: The "fcntl35" and "fcntl35_64" from the LTP syscall tests have failed on a testing node with T-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <>> tag=fcntl35 stime=1527764565 cmdline="fcntl35" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> <<>> tag=fcntl35_64 stime=1527764565 cmdline="fcntl35_64" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154~14.04.1 ProcVersionSignature: User Name 4.4.0-128.154~14.04.1-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: i386 Date: Thu May 31 11:05:58 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/1774394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Debian has package names that follow upstream SONAME, e.g. libcpupower0, libcpupower2. The -dev package is used only for building, the resulting binary packages get dependency on library package. When there is ABI break, upstream changes SONAME, so the library package changes too and all reverse dependencies need rebuild. Can you do the same in 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/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 1804594] Re: fanotify09 test case 1 in LTP failed with first group got more than 2 events
** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804594 Title: fanotify09 test case 1 in LTP failed with first group got more than 2 events Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Bug description: There is a new test cases added into fanotify09: 457e13c (fanotify09: check merging of events on child subdir) tag=fanotify09 stime=1542775332 cmdline="fanotify09" contacts="" analysis=exit <<>> tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s fanotify09.c:161: INFO: Test #0: Events on children with both inode and mount marks fanotify09.c:150: PASS: group 0 got event: mask 2 pid=19769 fd=23 path=/tmp/ltp-2Jj8lWaBTL/UT3GCK/mntpoint/tfile_19769 fanotify09.c:234: PASS: group 1 got no event fanotify09.c:234: PASS: group 2 got no event fanotify09.c:161: INFO: Test #1: Events on children and subdirs with both inode and mount marks fanotify09.c:150: PASS: group 0 got event: mask 2 pid=19769 fd=23 path=/tmp/ltp-2Jj8lWaBTL/UT3GCK/mntpoint/tfile_19769 fanotify09.c:150: PASS: group 0 got event: mask 10 pid=19769 fd=24 path=/tmp/ltp-2Jj8lWaBTL/UT3GCK/mntpoint/testdir fanotify09.c:202: FAIL: first group got more than 2 events (72 > 48) fanotify09.c:234: PASS: group 1 got no event fanotify09.c:234: PASS: group 2 got no event Summary: passed 7 failed 1 skipped 0 warnings 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 22 06:27 seq crw-rw 1 root audio 116, 33 Nov 22 06:27 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 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: Date: Thu Nov 22 06:45:22 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R320 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=7e417b15-9c42-401c-b706-06eb693e6d19 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0DY523 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R320 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1804594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 kernel
https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=f835ec7b5fd099a108d1d3deada19936d96b8037 ** Changed in: ubuntu-kernel-tests Status: In Progress => 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/1774387 Title: inotify07 in LTP syscall test failed with X kernel Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix 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 1775153] Re: fanotify09 test case 0 in LTP syscall test failed with T kernel
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775153 Title: fanotify09 test case 0 in LTP syscall test failed with T kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: New Bug description: The "fanotify09" from the LTP syscall tests has failed on a testing node with A/T kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. cd /opt/ltp 8. echo "fanotify09" > /tmp/jobs 9. ./runltp -f /tmp/jobs <<>> tag=fanotify09 stime=1528192114 cmdline="fanotify09" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9 fanotify09.c:182: FAIL: group 1 got event fanotify09.c:182: FAIL: group 2 got event Summary: passed 1 failed 2 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: User Name 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 5 08:30 seq crw-rw 1 root audio 116, 33 Jun 5 08:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.9 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: Date: Tue Jun 5 09:14:07 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Cavium ThunderX CRB PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.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: 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.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/1775153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841956] Re: ubuntu_sysdig fails on kvm kernels
xenial:linux-kvm already has the necessary config options but Disco and Bionic need to be updated. ** Also affects: linux-kvm (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Disco) Status: New => In Progress -- 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/1841956 Title: ubuntu_sysdig fails on kvm kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Bionic: In Progress Status in linux-kvm source package in Disco: In Progress Bug description: Bionic, Linux-Kvm: 4.15.0-1043.43 The module appears to load, however it may be that the service itself still does not start, there are no errors in the logs, just the following: 08/29 11:20:26 DEBUG| utils:0153| [stdout] == sysdig smmoke test to trace dd, cat, read and writes == 08/29 11:20:26 DEBUG| utils:0153| [stdout] Limiting raw capture file to 16384 blocks 08/29 11:20:26 DEBUG| utils:0153| [stdout] Try 1 of 10 08/29 11:21:13 DEBUG| utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start? 08/29 11:21:21 ERROR| utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory 08/29 11:21:21 DEBUG| utils:0153| [stdout] Raw capture file is 0 Mbytes 08/29 11:21:21 DEBUG| utils:0153| [stdout] Converted events file is 0 Mbytes 08/29 11:21:21 DEBUG| utils:0153| [stdout] Try 2 of 10 08/29 11:22:08 DEBUG| utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start? 08/29 11:22:16 ERROR| utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory 08/29 11:22:16 DEBUG| utils:0153| [stdout] Raw capture file is 0 Mbytes 08/29 11:22:16 DEBUG| utils:0153| [stdout] Converted events file is 0 Mbytes 08/29 11:22:16 DEBUG| utils:0153| [stdout] Try 3 of 10 08/29 11:23:03 DEBUG| utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start? Will require some additional triage. Summary: 0 passed, 3 failed stderr: stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1841956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes
Confirmed that this is fixed in 4.15 as of (at least) 4.15.0-62-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/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 1838278] Re: zfs-initramfs wont mount rpool
Curtin hasn't ever run zfs export on the pools; so either something else did this previously, or it wasn't a requirement. I can see if adding a zfs export on the pool works around the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1838278 Title: zfs-initramfs wont mount rpool Status in zfs-linux package in Ubuntu: New Bug description: 1. Eoan 2. http://archive.ubuntu.com/ubuntu eoan/main amd64 zfs-initramfs amd64 0.8.1-1ubuntu7 [23.1 kB] 3. ZFS rootfs rpool is mounted at boot 4. Booting an image with a rootfs rpool: [0.00] Linux version 5.2.0-8-generic (buildd@lgw01-amd64-015) (gcc version 9.1.0 (Ubuntu 9.1.0-6ubuntu2)) #9-Ubuntu SMP Mon Jul 8 13:07:27 UTC 2019 (Ubuntu 5.2.0-8.9-generic 5.2.0) [0.00] Command line: BOOT_IMAGE=/ROOT/zfsroot@/boot/vmlinuz-5.2.0-8-generic root=ZFS=rpool/ROOT/zfsroot ro console=ttyS0 Command: /sbin/zpool import -N 'rpool' Message: cannot import 'rpool': pool was previously in use from another system. Last accessed by ubuntu (hostid=d24775ba) at Mon Jul 29 05:21:19 2019 The pool can be imported, use 'zpool import -f' to import the pool. Error: 1 Failed to import pool 'rpool'. Manually import the pool and exit. Note, this works fine under Disco, http://archive.ubuntu.com/ubuntu disco/main amd64 zfs-initramfs amd64 0.7.12-1ubuntu5 [22.2 kB] [4.773077] spl: loading out-of-tree module taints kernel. [4.777256] SPL: Loaded module v0.7.12-1ubuntu3 [4.779433] znvpair: module license 'CDDL' taints kernel. [4.780333] Disabling lock debugging due to kernel taint [5.713830] ZFS: Loaded module v0.7.12-1ubuntu5, ZFS pool version 5000, ZFS filesystem version 5 Begin: Sleeping for ... done. Begin: Importing ZFS root pool 'rpool' ... Begin: Importing pool 'rpool' using defaults ... done. Begin: Mounting 'rpool/ROOT/zfsroot' on '/root//' ... done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1838278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841288] Re: does not create compressed dump on 5.0 or later kernels
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. ** Tags removed: verification-needed-bionic ** Changed in: makedumpfile (Ubuntu Bionic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1841288 Title: does not create compressed dump on 5.0 or later kernels Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Bug description: [Impact] On ppc64el, makedumpfile won't create compressed dumps, causing them to be very large. This affects any kernel later than 4.19 actually. [Test case] Crash a system with kdump-tools installed and enabled, by using the following sequence. Verify the created dumps are compressed by using file. This is the same test as the autopkgtest for makedumpfile. echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Regression potential] This is a small fix and should only impact ppc64el. Older kernels should still work, and should be tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1841288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. ** Changed in: makedumpfile (Ubuntu Bionic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: New Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830756] Re: tuntap: correctly set SOCKWQ_ASYNC_NOSPACE
** 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/1830756
Title:
tuntap: correctly set SOCKWQ_ASYNC_NOSPACE
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
[SRU Justification]
== Impact ==
1bd4978a88ac2 ("tun: honor IFF_UP in tun_get_user()") which is part of
kernel v4.5 introduced an issue where userspace processes might not
get notified if a link comes up after initially being down. This was
fixed in the requested backport (from 4.17).
== Fix ==
Backport the requested patch to Bionic (4.15). Xenial (4.4) is not
affected and Disco and later already contain that fix.
== Risk of Regregression ==
The change only slightly modifies a very specific protocol function.
Risk should be low and limited to tuntap.
---
The upstream commit 2f3ab6221e4c ("tuntap: correctly set
SOCKWQ_ASYNC_NOSPACE") is missing.
Without this patch, userspace apps that use tuntap may be blocked.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f3ab6221e4c
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830756/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: New Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841288] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1841288 Title: does not create compressed dump on 5.0 or later kernels Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Bug description: [Impact] On ppc64el, makedumpfile won't create compressed dumps, causing them to be very large. This affects any kernel later than 4.19 actually. [Test case] Crash a system with kdump-tools installed and enabled, by using the following sequence. Verify the created dumps are compressed by using file. This is the same test as the autopkgtest for makedumpfile. echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Regression potential] This is a small fix and should only impact ppc64el. Older kernels should still work, and should be tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1841288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: New Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: New Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: New Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841288] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1841288 Title: does not create compressed dump on 5.0 or later kernels Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Bug description: [Impact] On ppc64el, makedumpfile won't create compressed dumps, causing them to be very large. This affects any kernel later than 4.19 actually. [Test case] Crash a system with kdump-tools installed and enabled, by using the following sequence. Verify the created dumps are compressed by using file. This is the same test as the autopkgtest for makedumpfile. echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Regression potential] This is a small fix and should only impact ppc64el. Older kernels should still work, and should be tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1841288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: New Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741860] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1741860 Title: Use the kernel default for crashkernel offset Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] * The value chosen for ppc64el of 128MB aligns with that of the kernel default. That may change some day, so it would be best to let the kernel decide what value it should use. If the value does change and the kernel is not allowed to choose a value, this may stop the kernel from booting on a production system. [Test Case] Run `cat /etc/default/grub.d/kdump-tools.cfg` * Expected result: there is no offset specified at the end of the line (.e.g, @128M). * Actual result: For Xenial, Bionic, Disco, and Eoan there are offsets specified. [Regression Potential] * Right now, the offset described in the kdump-tools.cfg aligns with that of what the kernel would select, so since they are the same we would expect no change in operation. Original bug description follows: - == Comment: #0 - Hari Krishna Bathini - 2018-01-08 01:06:41 == ---Problem Description--- A default offset of 128MB is enforced for crashkernel by kdump-tools utility overriding the kernel default. While the kernel default offset for crashkernel is also 128MB, that may change and the right thing to do would be to let the kernel decide on the offset of crashkernel in the default scenario.. Get rid of "@128M" in kdump-tools.cfg file Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- # cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M" --- The offset is specified via kdump-tools where as the kernel may be the right place to set an offset by default.. Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #3 - MAMATHA INAMDAR - 2018-01-08 03:05:05 == This bug is opened to follow-up other bug based on the comment 19 https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical Launchpad1676884 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741860] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1741860 Title: Use the kernel default for crashkernel offset Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] * The value chosen for ppc64el of 128MB aligns with that of the kernel default. That may change some day, so it would be best to let the kernel decide what value it should use. If the value does change and the kernel is not allowed to choose a value, this may stop the kernel from booting on a production system. [Test Case] Run `cat /etc/default/grub.d/kdump-tools.cfg` * Expected result: there is no offset specified at the end of the line (.e.g, @128M). * Actual result: For Xenial, Bionic, Disco, and Eoan there are offsets specified. [Regression Potential] * Right now, the offset described in the kdump-tools.cfg aligns with that of what the kernel would select, so since they are the same we would expect no change in operation. Original bug description follows: - == Comment: #0 - Hari Krishna Bathini - 2018-01-08 01:06:41 == ---Problem Description--- A default offset of 128MB is enforced for crashkernel by kdump-tools utility overriding the kernel default. While the kernel default offset for crashkernel is also 128MB, that may change and the right thing to do would be to let the kernel decide on the offset of crashkernel in the default scenario.. Get rid of "@128M" in kdump-tools.cfg file Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- # cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M" --- The offset is specified via kdump-tools where as the kernel may be the right place to set an offset by default.. Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #3 - MAMATHA INAMDAR - 2018-01-08 03:05:05 == This bug is opened to follow-up other bug based on the comment 19 https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical Launchpad1676884 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741860] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1741860 Title: Use the kernel default for crashkernel offset Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] * The value chosen for ppc64el of 128MB aligns with that of the kernel default. That may change some day, so it would be best to let the kernel decide what value it should use. If the value does change and the kernel is not allowed to choose a value, this may stop the kernel from booting on a production system. [Test Case] Run `cat /etc/default/grub.d/kdump-tools.cfg` * Expected result: there is no offset specified at the end of the line (.e.g, @128M). * Actual result: For Xenial, Bionic, Disco, and Eoan there are offsets specified. [Regression Potential] * Right now, the offset described in the kdump-tools.cfg aligns with that of what the kernel would select, so since they are the same we would expect no change in operation. Original bug description follows: - == Comment: #0 - Hari Krishna Bathini - 2018-01-08 01:06:41 == ---Problem Description--- A default offset of 128MB is enforced for crashkernel by kdump-tools utility overriding the kernel default. While the kernel default offset for crashkernel is also 128MB, that may change and the right thing to do would be to let the kernel decide on the offset of crashkernel in the default scenario.. Get rid of "@128M" in kdump-tools.cfg file Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- # cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M" --- The offset is specified via kdump-tools where as the kernel may be the right place to set an offset by default.. Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #3 - MAMATHA INAMDAR - 2018-01-08 03:05:05 == This bug is opened to follow-up other bug based on the comment 19 https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical Launchpad1676884 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741860] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1741860 Title: Use the kernel default for crashkernel offset Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] * The value chosen for ppc64el of 128MB aligns with that of the kernel default. That may change some day, so it would be best to let the kernel decide what value it should use. If the value does change and the kernel is not allowed to choose a value, this may stop the kernel from booting on a production system. [Test Case] Run `cat /etc/default/grub.d/kdump-tools.cfg` * Expected result: there is no offset specified at the end of the line (.e.g, @128M). * Actual result: For Xenial, Bionic, Disco, and Eoan there are offsets specified. [Regression Potential] * Right now, the offset described in the kdump-tools.cfg aligns with that of what the kernel would select, so since they are the same we would expect no change in operation. Original bug description follows: - == Comment: #0 - Hari Krishna Bathini - 2018-01-08 01:06:41 == ---Problem Description--- A default offset of 128MB is enforced for crashkernel by kdump-tools utility overriding the kernel default. While the kernel default offset for crashkernel is also 128MB, that may change and the right thing to do would be to let the kernel decide on the offset of crashkernel in the default scenario.. Get rid of "@128M" in kdump-tools.cfg file Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- # cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M" --- The offset is specified via kdump-tools where as the kernel may be the right place to set an offset by default.. Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #3 - MAMATHA INAMDAR - 2018-01-08 03:05:05 == This bug is opened to follow-up other bug based on the comment 19 https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical Launchpad1676884 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741860] Proposed package removed from archive
The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. ** Changed in: makedumpfile (Ubuntu Bionic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1741860 Title: Use the kernel default for crashkernel offset Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] * The value chosen for ppc64el of 128MB aligns with that of the kernel default. That may change some day, so it would be best to let the kernel decide what value it should use. If the value does change and the kernel is not allowed to choose a value, this may stop the kernel from booting on a production system. [Test Case] Run `cat /etc/default/grub.d/kdump-tools.cfg` * Expected result: there is no offset specified at the end of the line (.e.g, @128M). * Actual result: For Xenial, Bionic, Disco, and Eoan there are offsets specified. [Regression Potential] * Right now, the offset described in the kdump-tools.cfg aligns with that of what the kernel would select, so since they are the same we would expect no change in operation. Original bug description follows: - == Comment: #0 - Hari Krishna Bathini - 2018-01-08 01:06:41 == ---Problem Description--- A default offset of 128MB is enforced for crashkernel by kdump-tools utility overriding the kernel default. While the kernel default offset for crashkernel is also 128MB, that may change and the right thing to do would be to let the kernel decide on the offset of crashkernel in the default scenario.. Get rid of "@128M" in kdump-tools.cfg file Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- # cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M" --- The offset is specified via kdump-tools where as the kernel may be the right place to set an offset by default.. Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #3 - MAMATHA INAMDAR - 2018-01-08 03:05:05 == This bug is opened to follow-up other bug based on the comment 19 https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical Launchpad1676884 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797325] Re: quotactl01 / 02 / 03 in ubuntu_ltp_syscalls test failed with KVM kernel
** Changed in: linux-kvm (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1797325 Title: quotactl01 / 02 / 03 in ubuntu_ltp_syscalls test failed with KVM kernel Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: New Bug description: I think this issue has something to do with the quota related failure reported in bug 1784535 For quotactl01: startup='Wed Nov 28 23:16:08 2018' tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts='' mke2fs 1.44.4 (18-Aug-2018) tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s quotactl01.c:195: FAIL: quotactl failed to turn on quota for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get disk quota limit for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get quota format for user: ESRCH quotactl01.c:206: PASS: quotactl succeeded to update quota usages for user quotactl01.c:206: PASS: quotactl succeeded to turn off quota for user quotactl01.c:195: FAIL: quotactl failed to turn on quota for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to get quota format for group: ESRCH quotactl01.c:206: PASS: quotactl succeeded to update quota usages for group quotactl01.c:206: PASS: quotactl succeeded to turn off quota for group Summary: passed 4 failed 12 skipped 0 warnings 0 For quotactl02 / quotactl03, they both failed with xfs mounting: tst_mkfs.c:90: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' safe_macros.c:757: BROK: tst_test.c:759: mount(/dev/loop0, mnt_point, xfs, 0, 0x40fbbd) failed: EINVAL <<>> tag=quotactl02 stime=1539242831 cmdline="quotactl02" contacts="" analysis=exit <<>> incrementing stop tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:90: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' safe_macros.c:757: BROK: tst_test.c:759: mount(/dev/loop0, mnt_point, xfs, 0, 0x40fbbd) failed: EINVAL Summary: passed 0 failed 0 skipped 0 warnings 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1036-kvm 4.4.0-1036.42 ProcVersionSignature: User Name 4.4.0-1036.42-kvm 4.4.155 Uname: Linux 4.4.0-1036-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Oct 11 07:27:17 2018 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/1797325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784535] Re: ubuntu_quota_smoke_test failed with KVM kernel
** Changed in: linux-kvm (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: ubuntu-kernel-tests Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- 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/1784535 Title: ubuntu_quota_smoke_test failed with KVM kernel Status in ubuntu-kernel-tests: Confirmed 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 Status in linux-kvm source package in Cosmic: New Bug description: According to Kamal's comment: CONFIG_QUOTA (and various other quota-related-looking configs) appear to be enabled already in the linux-kvm kernels -- but the required modules just end up in the regular linux-modules package (e.g. linux-modules-x.y.z-a.b-kvm) However even with the linux-modules-x.y.z-a.b-kvm package installed, this test will still fail with KVM kernel. $ sudo /home/ubuntu/autotest/client/tests/ubuntu_quota_smoke_test/ubuntu_quota_smoke_test.sh Using block device /dev/loop0 for path /home/ubuntu/mnt PASSED (quotacheck -vucmg) quotaon: using /home/ubuntu/mnt/aquota.group on /dev/loop0 [/home/ubuntu/mnt]: No such process quotaon: Quota format not supported in kernel. quotaon: using /home/ubuntu/mnt/aquota.user on /dev/loop0 [/home/ubuntu/mnt]: No such process quotaon: Quota format not supported in kernel. FAILED (quotaon -v) Summary: 1 passed, 1 failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1016-kvm 4.15.0-1016.16 ProcVersionSignature: User Name 4.15.0-1016.16-kvm 4.15.18 Uname: Linux 4.15.0-1016-kvm x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 31 03:59:45 2018 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/1784535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
