[Kernel-packages] [Bug 1808056] Re: vmlinuz is very large in arm64 -raspi2
The needed flash-kernel changes landed in 3.98ubuntu2, setting to Fix Released. Should we start looking into building compressed linux-raspi2 kernels for eoan? ** Changed in: flash-kernel (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1808056 Title: vmlinuz is very large in arm64 -raspi2 Status in flash-kernel package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Triaged Bug description: The debs are close to the same size: mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw-rw-r-- 1 mwhudson mwhudson 5398652 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw-rw-r-- 1 mwhudson mwhudson 6640960 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb But the vmlinuz on arm64 is several times larger: $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw--- root/root 6633048 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw--- root/root 23914504 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 This forced us to make the boot partition larger for the raspi3 b+ arm64 image we made. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1808056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834505] Re: Random kernel panics in QEMU instances when running on EPYC architecture
** Changed in: linux (Ubuntu) Status: Incomplete => Opinion ** Changed in: linux (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834505 Title: Random kernel panics in QEMU instances when running on EPYC architecture Status in linux package in Ubuntu: Confirmed Bug description: We have been seeing many kernel panic in QEMU instances on newly deployed servers all running on the EPYC architecture. Many of the KP occur early after the start of the QEMU process or within a few hours. All the servers are running an up to date Bionic. After the first few panics on 4.15 kernels, we upgraded to 4.18 and still had panics. The only thing running on the underlying server is QEMU processes. Here is a typical backtrace of a kernel panic : [58034.598930] BUG: unable to handle kernel paging request at 943276c49f64 [58034.612039] PGD 8363067 P4D 8363067 PUD 8367067 PMD 759ac063 PTE 800076c49163 [58034.612992] Oops: [#1] SMP NOPTI [58034.613462] CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 4.18.0-20-generic #21~18.04.1-Ubuntu [58034.614685] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [58034.615803] RIP: 0010:sched_ttwu_pending+0x6b/0xe0 [58034.616385] Code: 4b a1 93 00 41 83 a4 24 98 09 00 00 03 4c 89 e7 48 89 45 d8 c7 45 e0 00 00 00 00 e8 ef ca ff ff 48 8d 73 d0 48 83 fe d0 74 2c <0f> b6 96 64 08 00 00 48 8b 46 30 48 8d 4d d8 4c 89 e7 48 8d 5> [58034.618537] RSP: 0018:94327f803f90 EFLAGS: 00010087 [58034.619134] RAX: 34c83ba48a83 RBX: 943276c49730 RCX: [58034.619992] RDX: 2a12 RSI: 943276c49700 RDI: 94327fe3e000 [58034.620913] RBP: 94327f803fb8 R08: 3753c7b87c93 R09: [58034.621835] R10: R11: R12: 94327f822c00 [58034.622723] R13: R14: R15: [58034.623539] FS: () GS:94327f80() knlGS: [58034.624513] CS: 0010 DS: ES: CR0: 80050033 [58034.625214] CR2: 943276c49f64 CR3: 76544000 CR4: 003406f0 [58034.626268] Call Trace: [58034.626605] [58034.626924] scheduler_ipi+0xa9/0x130 [58034.627400] smp_reschedule_interrupt+0x39/0xe0 [58034.627925] reschedule_interrupt+0xf/0x20 [58034.628398] [58034.628659] RIP: 0010:rcu_idle_exit+0x40/0x70 [58034.629181] Code: fa 66 0f 1f 44 00 00 48 c7 c3 80 a6 01 00 65 48 03 1d ec 4b 50 4e 48 8b 03 48 85 c0 74 16 48 83 c0 01 48 89 03 4c 89 e7 57 9d <0f> 1f 44 00 00 5b 41 5c 5d c3 e8 a1 c6 ff ff 48 b8 00 00 00 0> [58034.631577] RSP: 0018:b2e03e48 EFLAGS: 0202 ORIG_RAX: ff02 [58034.632566] RAX: 4000 RBX: 94327f81a680 RCX: 94327f81a680 [58034.633557] RDX: RSI: 94327f81a680 RDI: 0202 [58034.634416] RBP: b2e03e58 R08: 0001cc00 R09: 0001 [58034.635292] R10: b2e03d98 R11: R12: 0202 [58034.636107] R13: R14: R15: 7e369c93 [58034.637052] do_idle+0x13f/0x280 [58034.637453] cpu_startup_entry+0x73/0x80 [58034.638067] rest_init+0xae/0xb0 [58034.638506] start_kernel+0x539/0x55a [58034.638938] x86_64_start_reservations+0x24/0x26 [58034.639470] x86_64_start_kernel+0x74/0x77 [58034.639958] secondary_startup_64+0xa5/0xb0 [58034.640441] Modules linked in: cfg80211 veth xt_nat xt_tcpudp ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_fi> None of the server has experienced any kernel panic itself. After analysing many of the crashes and seeing many of them handling interrupts, we decided to reboot the instances with the noapic parameter. No kernel panic has been seen since but this is just a workaround until a solution is found. AMD has been informed of the issue. TIA, ...Louis (aka Caribou) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834578] [NEW] Mouse stop working
You have been subscribed to a public bug: USB mouse stop working randomly ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18 Uname: Linux 4.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 28 10:24:54 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-52-generic, x86_64: installed nvidia, 390.116, 4.15.0-53-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-52-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-53-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d3] InstallationDate: Installed on 2018-09-21 (280 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 0518:5111 EzKEY Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-53-generic root=UUID=8e5738ba-3515-4603-abfb-a837482ef7ba ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0809 dmi.board.asset.tag: Default string dmi.board.name: PRIME B250M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0809:bd07/07/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- Mouse stop working https://bugs.launchpad.net/bugs/1834578 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833935] Re: Handle overflow in proc_get_long of sysctl
** Description changed: + == SRU Justification == + With the upper / lower boundary confined in bug 1834310, the file-max + is still suffering with overflow issue. + + This is because the simple_strtoul() used in proc_get_long() to parse + user input explicitly ignores overflows. So when you tried to put 2^64 + into file-max, it will: + # echo 18446744073709551616 > /proc/sys/fs/file-max + # cat /proc/sys/fs/file-max + 0 + + Which will cause your system to silently die behind your back. + + This issue was reported by the case 1 of the sysctl02 test in LTP: + sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0 + + + == Fix == + * 7f2923c4 (sysctl: handle overflow in proc_get_long) + + A new strtoul_lenient() was introduced here to solve this issue, with + extra check to notify userspace with -EINVAL. + + This patch can be cherry-picked into B/C/D/E, it needs some content + adjustment for X. + + == Test == + Test kernels could be found here: + https://people.canonical.com/~phlin/kernel/lp-1833935-proc_get_long/ + + The attempt to set file-max to 2^64 will be rejected: + $ sudo sysctl -w -q fs.file-max=18446744073709551616 + sysctl: setting key "fs.file-max": Invalid argument + + Tested and passed with these kernels on AMD64 KVM nodes. + + == Regression Potential == + Low, the newly introduced function strtoul_lenient() is just for + proc_get_long here. + + + == Original bug report == Test complains about apparmor enabled. As it's enabled by default, I think we might need to disable this test. Furthermore, this test will need kallsyms to be enabled, which is not for KVM kernels. <<>> tag=sysctl02_sh stime=1561360893 cmdline="sysctl02.sh" contacts="" analysis=exit <<>> incrementing stop sysctl02 1 TINFO: timeout per run is 0h 5m 0s sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0 sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 18446744073709551615 sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 9223372036854775808 sysctl02 4 TCONF: /proc/kallsyms not enabled sysctl02 4 TINFO: AppArmor enabled, this may affect test results sysctl02 4 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 (requires super/root) sysctl02 4 TINFO: loaded AppArmor profiles: none Summary: passed 0 failed 3 skipped 1 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=33 corefile=no cutime=2 cstime=1 <<>> 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 07:21:41 2019 SourcePackage: linux-kvm 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1833935 Title: Handle overflow in proc_get_long of sysctl Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: == SRU Justification == With the upper / lower boundary confined in bug 1834310, the file-max is still suffering with overflow issue. This is because the simple_strtoul() used in proc_get_long() to parse user input explicitly ignores overflows. So when you tried to put 2^64 into file-max, it will: # echo 18446744073709551616 > /proc/sys/fs/file-max # cat /proc/sys/fs/file-max 0 Which will cause your system to silently die behind your back. This issue was reported by the case 1 of the sysctl02 test in LTP: sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0 == Fix == * 7f2923c4 (sysctl: handle overflow in proc_get_long) A new strtoul_lenient() was introduced here to solve this issue, with extra check to notify userspace with -EINVAL. This patch can be cherry-picked into B/C/D/E, it needs some content adjustment for X. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1833935-proc_get_long/ The attempt to set file-max to 2^64 will be rejected: $ sudo sysctl -w -q fs.file-max=18446744073709551616 sysctl: setting key "fs.file-max": Invalid argument Tested and passed with these kernels on AMD64 KVM nodes. == Regression Potential == Low, the newly introduced function strtoul_lenient() is just for proc_get_long here. == Original bug report == Test complains about apparmor enabled. As it's enabled by default, I think we might ne
[Kernel-packages] [Bug 1834578] Re: Mouse stop working
Your kernel log shows it is having trouble with the mouse. This might be a fault with the mouse or the USB port. It might also be a kernel bug, but that's less likely... [ 551.252894] usb 1-6: reset low-speed USB device number 3 using xhci_hcd [ 551.520701] usb 1-6: device descriptor read/64, error -71 [ 556.957250] usb 1-6: reset low-speed USB device number 3 using xhci_hcd [ 557.733478] usb 1-6: USB disconnect, device number 3 [ 558.061164] usb 1-6: new low-speed USB device number 4 using xhci_hcd [ 558.212826] usb 1-6: New USB device found, idVendor=046d, idProduct=c05a [ 558.212832] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 558.212837] usb 1-6: Product: USB Optical Mouse [ 558.212841] usb 1-6: Manufacturer: Logitech [ 558.215745] input: Logitech USB Optical Mouse as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:046D:C05A.0005/input/input15 [ 558.216101] hid-generic 0003:046D:C05A.0005: input,hidraw3: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-:00:14.0-6/input0 [ 687.645465] usb 1-6: reset low-speed USB device number 4 using xhci_hcd [ 777.148862] usb 1-6: reset low-speed USB device number 4 using xhci_hcd [ 777.417072] usb 1-6: Device not responding to setup address. [ 777.625107] usb 1-6: Device not responding to setup address. [ 777.832620] usb 1-6: device not accepting address 4, error -71 [ 778.100621] usb 1-6: reset low-speed USB device number 4 using xhci_hcd [ 1095.999728] usb 1-6: reset low-speed USB device number 4 using xhci_hcd [ 1096.267472] usb 1-6: device descriptor read/64, error -71 [ 1096.643504] usb 1-6: device descriptor read/64, error -71 [ 1097.019526] usb 1-6: reset low-speed USB device number 4 using xhci_hcd [ 1097.287539] usb 1-6: device descriptor read/64, error -71 [ 1097.663495] usb 1-6: device descriptor read/64, error -71 [ 1098.039490] usb 1-6: reset low-speed USB device number 4 using xhci_hcd [ 1098.039923] usb 1-6: Device not responding to setup address. [ 1098.247947] usb 1-6: Device not responding to setup address. [ 1098.455509] usb 1-6: device not accepting address 4, error -71 [ 1098.723506] usb 1-6: reset low-speed USB device number 4 using xhci_hcd [ 1098.723945] usb 1-6: Device not responding to setup address. [ 1098.931938] usb 1-6: Device not responding to setup address. [ 1099.139470] usb 1-6: device not accepting address 4, error -71 [ 1099.139617] usb 1-6: USB disconnect, device number 4 [ 1099.327521] usb 1-6: new low-speed USB device number 5 using xhci_hcd [ 1099.455500] usb 1-6: device descriptor read/64, error -71 [ 1099.691465] usb 1-6: device descriptor read/64, error -71 [ 1099.927528] usb 1-6: new low-speed USB device number 6 using xhci_hcd [ 1100.055542] usb 1-6: device descriptor read/64, error -71 [ 1100.291539] usb 1-6: device descriptor read/64, error -71 [ 1100.399599] usb usb1-port6: attempt power cycle [ 1101.055512] usb 1-6: new low-speed USB device number 7 using xhci_hcd [ 1101.055908] usb 1-6: Device not responding to setup address. [ 1101.263962] usb 1-6: Device not responding to setup address. [ 1101.471513] usb 1-6: device not accepting address 7, error -71 [ 1101.599512] usb 1-6: new low-speed USB device number 8 using xhci_hcd [ 1101.599924] usb 1-6: Device not responding to setup address. [ 1101.807962] usb 1-6: Device not responding to setup address. [ 1102.015541] usb 1-6: device not accepting address 8, error -71 [ 1102.015632] usb usb1-port6: unable to enumerate USB device [ 1143.931796] usb 1-6: new low-speed USB device number 9 using xhci_hcd [ 1144.083477] usb 1-6: New USB device found, idVendor=046d, idProduct=c05a [ 1144.083483] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1144.083487] usb 1-6: Product: USB Optical Mouse ** Package changed: xorg (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/1834578 Title: Mouse stop working Status in linux package in Ubuntu: Confirmed Bug description: USB mouse stop working randomly ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18 Uname: Linux 4.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 28 10:24:54 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatu
[Kernel-packages] [Bug 1833935] Re: Handle overflow in proc_get_long of sysctl
https://lists.ubuntu.com/archives/kernel-team/2019-June/101710.html ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: Incomplete ** Also affects: linux-kvm (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux-kvm (Ubuntu) ** No longer affects: linux-kvm (Ubuntu Xenial) ** No longer affects: linux-kvm (Ubuntu Cosmic) ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** No longer affects: linux-kvm (Ubuntu Bionic) ** No longer affects: linux-kvm (Ubuntu Disco) ** No longer affects: linux-kvm (Ubuntu Eoan) ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => 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/1833935 Title: Handle overflow in proc_get_long of sysctl Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: == SRU Justification == With the upper / lower boundary confined in bug 1834310, the file-max is still suffering with overflow issue. This is because the simple_strtoul() used in proc_get_long() to parse user input explicitly ignores overflows. So when you tried to put 2^64 into file-max, it will: # echo 18446744073709551616 > /proc/sys/fs/file-max # cat /proc/sys/fs/file-max 0 Which will cause your system to silently die behind your back. This issue was reported by the case 1 of the sysctl02 test in LTP: sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0 == Fix == * 7f2923c4 (sysctl: handle overflow in proc_get_long) A new strtoul_lenient() was introduced here to solve this issue, with extra check to notify userspace with -EINVAL. This patch can be cherry-picked into B/C/D/E, it needs some content adjustment for X. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1833935-proc_get_long/ The attempt to set file-max to 2^64 will be rejected: $ sudo sysctl -w -q fs.file-max=18446744073709551616 sysctl: setting key "fs.file-max": Invalid argument Tested and passed with these kernels on AMD64 KVM nodes. == Regression Potential == Low, the newly introduced function strtoul_lenient() is just for proc_get_long here. == Original bug report == Test complains about apparmor enabled. As it's enabled by default, I think we might need to disable this test. Furthermore, this test will need kallsyms to be enabled, which is not for KVM kernels. <<>> tag=sysctl02_sh stime=1561360893 cmdline="sysctl02.sh" contacts="" analysis=exit <<>> incrementing stop sysctl02 1 TINFO: timeout per run is 0h 5m 0s sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0 sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 18446744073709551615 sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 9223372036854775808 sysctl02 4 TCONF: /proc/kallsyms not enabled sysctl02 4 TINFO: AppArmor enabled, this may affect test results sysctl02 4 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 (requires super/root) sysctl02 4 TINFO: loaded AppArmor profiles: none Summary: passed 0 failed 3 skipped 1 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=33 corefile=no cutime=2 cstime=1 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.10 P
[Kernel-packages] [Bug 1834588] Re: ICX: Add PMU support for adaptive and enhanced PEBS
c22497f5838c237e3094a4dfb99d1c5de6353239 5.2-rc1 ** Description changed: Description: Add support for new ICX PMU features: Adaptive PEBS, and Enhanced PEBS. Target Release: 19.10 - Target Kernel: 5.3 + Target Kernel: 5.2 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834588 Title: ICX: Add PMU support for adaptive and enhanced PEBS Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: Add support for new ICX PMU features: Adaptive PEBS, and Enhanced PEBS. Target Release: 19.10 Target Kernel: 5.2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834588] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1834588 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834588 Title: ICX: Add PMU support for adaptive and enhanced PEBS Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: Add support for new ICX PMU features: Adaptive PEBS, and Enhanced PEBS. Target Release: 19.10 Target Kernel: 5.2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834315] Re: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan
Seth - the reason this is targeted against xenial is that the launchpad builders are running the 4.4 xenial kernel - and so glibc *from eoan- proposed* FTBFS when building on launchpad - and it would appear to be as a result of this change. Oddly, I cannot reproduce the same failure locally using a xenial VM containing an eoan schroot. One data point - for me glibc from eoan-proposed builds fine in an eoan schroot running on a bionic host with the hwe-edge kernel - so it is not clear this needs to be reverted for disco/eoan. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834315 Title: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Incomplete Bug description: [Impact] As reported in #1833067 and https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/comments/7 some glibc testcases are still regressing on i386 after applying both the following commits: commit 379d98ddf41344273d9718556f761420f4dc80b3 Author: Alistair Strachan Date: Fri Aug 3 10:39:31 2018 -0700 x86: vdso: Use $LD instead of $CC to link commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 Author: Alistair Strachan Date: Fri Dec 14 14:36:37 2018 -0800 x86/vdso: Pass --eh-frame-hdr to the linker [Fix] Revert both these patches to restore the original behaviour. [Test] ADT tests for glibc. [Regression Potential] Low. This restores the status quo before the original change to vdso/x86/Makefile to restore the original linker behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834578] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834578 Title: Mouse stop working Status in linux package in Ubuntu: Confirmed Bug description: USB mouse stop working randomly ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18 Uname: Linux 4.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 28 10:24:54 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-52-generic, x86_64: installed nvidia, 390.116, 4.15.0-53-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-52-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-53-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d3] InstallationDate: Installed on 2018-09-21 (280 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 0518:5111 EzKEY Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-53-generic root=UUID=8e5738ba-3515-4603-abfb-a837482ef7ba ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0809 dmi.board.asset.tag: Default string dmi.board.name: PRIME B250M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0809:bd07/07/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834310] Re: Handle overflow for file-max
** Description changed: == SRU Justification == - Currently, when writing + Currently, when writing 2^64-1 or 2^63 into file-max: echo 18446744073709551616 > /proc/sys/fs/file-max - /proc/sys/fs/file-max will overflow and be set to 0 and make the system - stuck with "Too many open files in system" error within seconds. + Will make the system stuck with "Too many open files in system" error + within seconds. The upper and lower limit need to be defined properly to avoid this. + (The case for passing 2^64 will be addressed in bug 1833935) This failure was reported by the case 2 and 3 of the sysctl02 test in LTP: sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 18446744073709551615 sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 9223372036854775808 == Fix == * 32a5ad9c sysctl: handle overflow for file-max * 9002b214 kernel/sysctl.c: fix out-of-bounds access when setting file-max These patches can be cherry-picked into B/C. They have already been applied in X/D from stable update process. == Test == Test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1834310-file-max/ Tested OK on KVM nodes with the following command (extracted from the sysctl02 test case in LTP): $ cat /proc/sys/fs/file-max $ sudo sysctl -w -q fs.file-max=18446744073709551615 $ cat /proc/sys/fs/file-max $ sudo sysctl -w -q fs.file-max=9223372036854775808 $ cat /proc/sys/fs/file-max All three file-max output should be identical with the patched kernel. This is because the file-max value is parsed via __do_proc_doulongvec_minmax(), which does not report error when min or max are exceeded but it will just keep the old value instead. == Regression Potential == Low, just adding boundaries to the file-max. And it's been applied in some of our kernels for a while. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-52-generic 4.15.0-52.56 ProcVersionSignature: User Name 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 25 11:03 seq crw-rw 1 root audio 116, 33 Jun 25 11:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jun 25 11:04:55 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=6f08d1c2-d443-47ee-97ca-2aeb1bf53f35 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-52-generic N/A linux-backports-modules-4.15.0-52-generic N/A linux-firmware 1.173.6 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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834310 Title: Handle overflow for file-max Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == SRU Justification == Currently, when writing 2^64-1 or 2^63 into file-max: echo 18446744073709551616 > /proc/sys/fs/file-max Will make the system stuck with "Too many open files in system" error within seconds. The upper and lower limit need to be defined properly to avoid this. (The case for passing 2^64 will be addressed in bug 1833935) This failure was reported by the case 2 and 3 of the sysctl02 test in LTP: sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 18446744073709551615 sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 9223372036854775808 == Fix == * 32a5ad9c sysctl: handle overflow for file-max * 9002b214 kernel/sysctl.c: fix out-of-bounds access when setting file-max These patches can be cherry-picked into B/C. They have already been applied in
[Kernel-packages] [Bug 1782728] Re: crypto AF_ALG protocol not enabled on KVM - is this intentional?
As per Kamal's comment, marking this as "Won't Fix" until any customer asks for this. ** Changed in: linux-kvm (Ubuntu) Status: New => Won't Fix -- 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/1782728 Title: crypto AF_ALG protocol not enabled on KVM - is this intentional? Status in linux-kvm package in Ubuntu: Won't Fix Bug description: The 4.15.0 KVM kernels do not enable AF_ALG crypto [1] by default. This userspace crypto can be useful - so is it intentional for this to be disabled? [1] https://en.wikipedia.org/wiki/Crypto_API_(Linux) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1782728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782727] Re: DCCP protocol not enabled on KVM kernel - is this intentional?
As per Kamal's comment, marking this as "Won't Fix" until any customer asks for this. ** Changed in: linux-kvm (Ubuntu) Status: New => Won't Fix -- 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/1782727 Title: DCCP protocol not enabled on KVM kernel - is this intentional? Status in linux-kvm package in Ubuntu: Won't Fix Bug description: kvm 4.15.0 kernels don't have DCCP [1] enabled by default unlike our generic kernel. Is this intentional? [1] https://en.wikipedia.org/wiki/Datagram_Congestion_Control_Protocol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1782727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834528] Re: linux-ibm-gt: 4.15.0-1026.28 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => 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 -- kernel-stable-master-bug: 1833987 - phase: Packaging - phase-changed: Friday, 28. June 2019 05:12 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 28. June 2019 08:42 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,main:building 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/1834528 Title: linux-ibm-gt: 4.15.0-1026.28 -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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1833987 phase: Holding before Promote to Proposed phase-changed: Friday, 28. June 2019 08:42 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828035] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2019-06-28 05:04 EDT--- Is there an outlook when this SRU will be available in proposed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828035 Title: StrongSwan with GCM and large packet sizes produces unstable behavior Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Confirmed Status in strongswan package in Ubuntu: Incomplete Bug description: StrongSwan with GCM and large packet sizes produces unstable behavior when used in Linux native environment. ---uname output--- Linux ubu01 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:29:11 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = 3906 / M04 (z14), LPAR (dedicated) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- On two separate machines (Linux native), install StrongSwan and on both machines, configure the encryption with aes128gcm8 for IPsec. Then run the following command from one of the machine: ``` $# ping -s 1024 ``` Small packet sizes are working as expected. However, anything large (around 1024 bytes or more) are sometimes returning wrong values, or the packets are getting lost. This problem does not occur for ciphers not involving GCM. Userspace tool common name: StrongSwan The userspace tool has the following bit modes: both Userspace package: StrongSwan Userspace tool obtained from project website: na -Attach ltrace and strace of userspace application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834528] Re: linux-ibm-gt: 4.15.0-1026.28 -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 -- kernel-stable-master-bug: 1833987 phase: Holding before Promote to Proposed phase-changed: Friday, 28. June 2019 08:42 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,main:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building 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/1834528 Title: linux-ibm-gt: 4.15.0-1026.28 -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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1833987 phase: Holding before Promote to Proposed phase-changed: Friday, 28. June 2019 08:42 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed -- 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/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 09:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833470] Re: ca0132 audio in Ubuntu 19.04 only after Windows 10 started
It's in alsa-firmware but not in upstream linux-firmware yet: https://git.alsa-project.org/?p=alsa-firmware.git;a=commit;h=57800c337aeca5743049493f489eb29f07a0d624 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833470 Title: ca0132 audio in Ubuntu 19.04 only after Windows 10 started Status in linux package in Ubuntu: Confirmed Bug description: Motherboard: Gigabyte GA-Z170X-Gaming GT (rev. 1.0) Description: Ubuntu 19.04 Release: 19.04 Expected behavior: Audio playback via headphones Actual behavior: No audio playback heard If I start Ubuntu 19.04 directly after booting my PC, there is no sound from the front or rear outputs. Everything seems configured correctly in Alsamixer, etc. If I boot into Windows 10, then restart and enter Ubuntu, the sound works as expected. I suspect something is being set properly by the Windows driver that is missed in the native Linux driver. The fact that it survives a (soft) reboot is interesting. I know this is at the ALSA level or below, because if I stop pulseaudio, `aplay music.wav` produces no output before starting Windows, and works after starting Windows. output of `lspci | grep -i audio` 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 02:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) output of `aplay -lL` default Playback/recording through the PulseAudio sound server null Discard all samples (playback) or generate zero samples (capture) jack JACK Audio Connection Kit pulse PulseAudio Sound Server sysdefault:CARD=PCH HDA Intel PCH, CA0132 Analog Default Audio Device front:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Front speakers surround21:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Digital IEC958 (S/PDIF) Digital Audio Output dmix:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Direct sample mixing device dmix:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Direct sample mixing device dsnoop:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Direct sample snooping device dsnoop:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Direct sample snooping device hw:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Direct hardware device without any conversions hw:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Direct hardware device without any conversions plughw:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Hardware device with all software conversions plughw:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Hardware device with all software conversions usbstream:CARD=PCH HDA Intel PCH USB Stream Output hdmi:CARD=NVidia,DEV=0 HDA NVidia, HDMI 0 HDMI Audio Output hdmi:CARD=NVidia,DEV=1 HDA NVidia, HDMI 1 HDMI Audio Output hdmi:CARD=NVidia,DEV=2 HDA NVidia, HDMI 2 HDMI Audio Output hdmi:CARD=NVidia,DEV=3 HDA NVidia, HDMI 3 HDMI Audio Output dmix:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Direct sample mixing device dmix:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Direct sample mixing device dmix:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Direct sample mixing device dmix:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3 Direct sample mixing device dsnoop:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Direct sample snooping device dsnoop:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Direct sample snooping device dsnoop:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Direct sample snooping device dsnoop:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3 Direct sample snooping device hw:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Direct hardware device without any conversions hw:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Direct hardware device without any conversions hw:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Direct hardware device without any conversions hw:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1834030 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 17:15 UTC + phase: Complete + phase-changed: Friday, 28. June 2019 09:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs ** Tags removed: kernel-release-tracking-bug-live -- 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/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 09:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834528] Re: linux-ibm-gt: 4.15.0-1026.28 -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 -- kernel-stable-master-bug: 1833987 phase: Holding before Promote to Proposed phase-changed: Friday, 28. June 2019 08:42 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,main:building 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/1834528 Title: linux-ibm-gt: 4.15.0-1026.28 -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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1833987 phase: Holding before Promote to Proposed phase-changed: Friday, 28. June 2019 08:42 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830682] Re: cve-2017-5754 from cve test suite in LTP failed with KVM kernel
http://lists.linux.it/pipermail/ltp/2019-June/012567.html ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: linux-kvm (Ubuntu) Status: New => Invalid -- 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/1830682 Title: cve-2017-5754 from cve test suite in LTP failed with KVM kernel Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: Invalid Bug description: It looks like this is cause by the absence of kallsyms: safe_file_ops.c:202: BROK: Failed to open FILE '/proc/kallsyms' for reading at meltdown.c:272: ENOENT <<>> tag=cve-2017-5754 stime=1559026443 cmdline="meltdown" contacts="" analysis=exit <<>> tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s meltdown.c:259: INFO: access time: cached = 49, uncached = 290, threshold = 119 safe_file_ops.c:202: BROK: Failed to open FILE '/proc/kallsyms' for reading at meltdown.c:272: ENOENT Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=2 corefile=no cutime=21 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1013-kvm 4.18.0-1013.13 ProcVersionSignature: User Name 4.18.0-1013.13-kvm 4.18.20 Uname: Linux 4.18.0-1013-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 Date: Tue May 28 06:54:14 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/1830682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830362] Re: runpwtests03 from power_management_tests test suite in LTP failed
** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830362 Title: runpwtests03 from power_management_tests test suite in LTP failed Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Invalid Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:57:20 2019' /opt/ltp/testcases/bin/runpwtests03.sh: 29: /opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found find: â/sys/devices/system/cpu/cpu40/cpufreq/â: No such file or directory /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Checking cpu freq sysfs files Power_Management03 1 TPASS: CPUFREQ sysfs tests /opt/ltp/testcases/bin/runpwtests03.sh: 55: /opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found /opt/ltp/testcases/bin/runpwtests03.sh: 62: /opt/ltp/testcases/bin/runpwtests03.sh: cannot create /sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- performance for cpu40 /opt/ltp/testcases/bin/runpwtests03.sh: 62: /opt/ltp/testcases/bin/runpwtests03.sh: cannot create /sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- powersave for cpu40 Power_Management03 2 TFAIL: Changing governors cat: '/sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies': No such file or directory /opt/ltp/testcases/bin/runpwtests03.sh: 83: /opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Changing cpu frequencies Power_Management03 3 TPASS: Changing frequncies modprobe: invalid option -- 'l' modprobe: invalid option -- 'l' Power_Management03 4 TPASS: Loading and Unloading of governor kernel modules tag=runpwtests03 stime=1558695440 dur=2 exit=exited stat=1 core=no cu=28 cs=7 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 07:49 seq crw-rw 1 root audio 116, 33 May 21 07:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri May 24 11:07:37 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 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/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831595] Re: block_dev test from kernel_misc in LTP is causing kernel traces
>From LTP upstream feedback, this seems to be an expected behaviour. http://lists.linux.it/pipermail/ltp/2019-June/012255.html Thus I'm closing this. ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** 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/1831595 Title: block_dev test from kernel_misc in LTP is causing kernel traces Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Bug description: Reproduce rate: 100% Steps: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools; ./configure; make; sudo make install 3. Run the block_dev test: cd /opt/ltp/testcases/bin sudo ./block_dev All 7 test cases will pass, but there will be a kernel warning trace in dmesg: $ sudo ./block_dev block_dev1 TPASS : Test-case '1' block_dev2 TPASS : Test-case '2' block_dev3 TPASS : Test-case '3' block_dev4 TPASS : Test-case '4' block_dev5 TPASS : Test-case '5' block_dev6 TPASS : Test-case '6' block_dev7 TPASS : Test-case '7' [ 182.564296] ltp_block_dev: loading out-of-tree module taints kernel. [ 182.564334] ltp_block_dev: module verification failed: signature and/or required key missing - tainting kernel [ 182.564547] ltp_block_dev: Starting module [ 182.564557] ltp_block_dev: device registered [ 182.564698] ltp_block_dev: Test Case 1: register_blkdev() with auto allocating major numbers (major=0) [ 182.564699] ltp_block_dev: Test Case Result: PASS [ 182.564746] ltp_block_dev: Test Case 2: stress test of register_blkdev() with auto allocating major numbers (major=0) [ 182.564776] register_blkdev: failed to get major for ltp_block_dev [ 182.564776] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564777] register_blkdev: failed to get major for ltp_block_dev [ 182.564777] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564777] register_blkdev: failed to get major for ltp_block_dev [ 182.564778] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564778] register_blkdev: failed to get major for ltp_block_dev [ 182.564778] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564779] register_blkdev: failed to get major for ltp_block_dev [ 182.564779] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564780] register_blkdev: failed to get major for ltp_block_dev [ 182.564780] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564780] register_blkdev: failed to get major for ltp_block_dev [ 182.564781] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564781] register_blkdev: failed to get major for ltp_block_dev [ 182.564781] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564782] register_blkdev: failed to get major for ltp_block_dev [ 182.564782] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564782] register_blkdev: failed to get major for ltp_block_dev [ 182.564783] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564783] register_blkdev: failed to get major for ltp_block_dev [ 182.564784] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564784] register_blkdev: failed to get major for ltp_block_dev [ 182.564784] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564785] register_blkdev: failed to get major for ltp_block_dev [ 182.564785] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564785] register_blkdev: failed to get major for ltp_block_dev [ 182.564786] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564786] register_blkdev: failed to get major for ltp_block_dev [ 182.564786] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564787] register_blkdev: failed to get major for ltp_block_dev [ 182.564787] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564788] register_blkdev: failed to get major for ltp_block_dev [ 182.564788] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564788] register_blkdev: failed to get major for ltp_block_dev [ 182.564789] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564789] register_blkdev: failed to get major for ltp_block_dev [ 182.564789] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564790] register_blkdev: failed to get major for ltp_block_dev [ 182.564790] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564790] register_blkdev: failed to get major for ltp_block_dev [ 182.564791] ltp_block_dev: device is busy, register_blkdev() ret -16 [ 182.564791] register_blkdev: failed to get major for ltp_bloc
[Kernel-packages] [Bug 1834528] Re: linux-ibm-gt: 4.15.0-1026.28 -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 -- kernel-stable-master-bug: 1833987 phase: Holding before Promote to Proposed phase-changed: Friday, 28. June 2019 08:42 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,main:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building 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/1834528 Title: linux-ibm-gt: 4.15.0-1026.28 -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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1833987 phase: Holding before Promote to Proposed phase-changed: Friday, 28. June 2019 08:42 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -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: 1834030 phase: Complete - phase-changed: Friday, 28. June 2019 09:28 UTC + phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs ** Changed in: kernel-sru-workflow Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released -- 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/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
** Changed in: kernel-sru-workflow Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
** Changed in: kernel-sru-workflow Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released -- 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/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released -- 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/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
** Changed in: kernel-sru-workflow Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released -- 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/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
** Changed in: kernel-sru-workflow Status: Fix Released => In Progress ** Tags added: kernel-release-tracking-bug-live -- 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/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
** Changed in: kernel-sru-workflow Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released -- 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/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834528] Re: linux-ibm-gt: 4.15.0-1026.28 -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 -- kernel-stable-master-bug: 1833987 phase: Holding before Promote to Proposed phase-changed: Friday, 28. June 2019 08:42 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building 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/1834528 Title: linux-ibm-gt: 4.15.0-1026.28 -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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1833987 phase: Holding before Promote to Proposed phase-changed: Friday, 28. June 2019 08:42 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833877] Re: Kernel couldn't recognize Touchpad and Trackpoint as different devices for Lenovo Thinkpad A275
Please boot with this kernel with more debug information: https://people.canonical.com/~khfeng/lp1833877/ And attach 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/1833877 Title: Kernel couldn't recognize Touchpad and Trackpoint as different devices for Lenovo Thinkpad A275 Status in linux package in Ubuntu: Confirmed Bug description: So, the problem described in header. xinput sees only one input device (PS/2 Synaptics TouchPad) instead of two (PS/2 Synaptics TouchPad and IBM TrackPoint). So I couldn't turn off TouchPad without of turning off Trackpoint, and so on and so on --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: misha 1411 F pulseaudio /dev/snd/controlC0: misha 1411 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-02 (21 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20KD0013US Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=7db192d2-3f73-4d63-9857-72249498145e ro i8042.debug=1 quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2017 dmi.bios.vendor: LENOVO dmi.bios.version: R0NET30W (1.08 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KD0013US dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0NET30W(1.08):bd09/19/2017:svnLENOVO:pn20KD0013US:pvrThinkPadA275:rvnLENOVO:rn20KD0013US:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad A275 dmi.product.name: 20KD0013US dmi.product.version: ThinkPad A275 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834528] Re: linux-ibm-gt: 4.15.0-1026.28 -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 -- kernel-stable-master-bug: 1833987 phase: Holding before Promote to Proposed phase-changed: Friday, 28. June 2019 08:42 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building + promote-to-proposed: Pending -- builds not complete in ppa meta:queued 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/1834528 Title: linux-ibm-gt: 4.15.0-1026.28 -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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1833987 phase: Holding before Promote to Proposed phase-changed: Friday, 28. June 2019 08:42 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826868] Re: Sound device not detected after resume from hibernate
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Disco) Status: New => Invalid -- 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/1826868 Title: Sound device not detected after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: New Status in linux-oem source package in Disco: Invalid Bug description: The patch is already in the v5.2-rc1, so don't send the patch to unstable. In the V2, I added 3 more patches. The 0001-xxx.patch is for fixing the issue of "audio doesn't work after s3/s4 on cln and glk machines", but it introduces a new issue of "screen flickering when CDCLK changes", So I added 0002/3/4-xxx.patch to fix the new issue. [Impact] After s3 or s4, the hdmi audio driver will re-probe the hw, if the hdmi monitor is not plugged before s3 or s4, the re-probe will fail on cnl and glk machines. [Fix] Keep the cdclk alive when re-probing [Test Case] I applied the patches to bionic kernel and disco kernel, and tested them on Whiskeylake, cannonlake, kabylake, skylake and geminilake machines, before s3, I verified analogue audio, hdmi audio and screen dispaly all worked well, then let the system enter s3 and resume, recheck the analogue audio, hdmi audio and screen display, all worked well too. And repeated the test 5 times. [Regression Risk] Low. I have tested the patched kernel on different Dell and Lenovo machines, they include Whiskeylake, cannonlake, kabylake, skylake and geminilake. dmesg -w shows the following: snd_hda_codec_realtek hdaudioC0D0: out of range cmd 0:20:400: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1551 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 21:22:18 2019 InstallationDate: Installed on 2019-04-24 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Stream x360 Convertible 11-ag1XX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8501 dmi.board.vendor: HP dmi.board.version: 05.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Stream x360 Convertible 11-ag1XX dmi.product.sku: 4RV86PA#ABG dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834528] Re: linux-ibm-gt: 4.15.0-1026.28 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** 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: 1833987 - phase: Holding before Promote to Proposed - phase-changed: Friday, 28. June 2019 08:42 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 28. June 2019 11:43 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:queued + promote-to-proposed: Pending -- ready for review 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/1834528 Title: linux-ibm-gt: 4.15.0-1026.28 -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 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 package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Promote to Proposed phase-changed: Friday, 28. June 2019 11:43 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834028] Re: linux-aws: 4.4.0-1048.52 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1834028 Title: linux-aws: 4.4.0-1048.52 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834030 phase: Complete phase-changed: Friday, 28. June 2019 10:28 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832775] Re: Disco update: 5.0.14 upstream stable release
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832775 Title: Disco update: 5.0.14 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.14 upstream stable release from git://git.kernel.org/ The following patches were applied: * selftests/seccomp: Prepare for exclusive seccomp flags * seccomp: Make NEW_LISTENER and TSYNC flags exclusive * ARC: memset: fix build with L1_CACHE_SHIFT != 6 * iwlwifi: fix driver operation for 5350 * mwifiex: Make resume actually do something useful again on SDIO cards * mtd: rawnand: marvell: Clean the controller state before each operation * mac80211: don't attempt to rename ERR_PTR() debugfs dirs * i2c: synquacer: fix enumeration of slave devices * i2c: imx: correct the method of getting private data in notifier_call * i2c: Prevent runtime suspend of adapter when Host Notify is required * ALSA: hda/realtek - Add new Dell platform for headset mode * ALSA: hda/realtek - Apply the fixup for ASUS Q325UAR * USB: yurex: Fix protection fault after device removal * USB: w1 ds2490: Fix bug caused by improper use of altsetting array * USB: dummy-hcd: Fix failure to give back unlinked URBs * usb: usbip: fix isoc packet num validation in get_pipe * USB: core: Fix unterminated string returned by usb_string() * USB: core: Fix bug caused by duplicate interface PM usage counter * KVM: lapic: Disable timer advancement if adaptive tuning goes haywire * KVM: x86: Consider LAPIC TSC-Deadline timer expired if deadline too short * KVM: lapic: Track lapic timer advance per vCPU * KVM: lapic: Allow user to disable adaptive tuning of timer advancement * KVM: lapic: Convert guest TSC to host time domain if necessary * arm64: dts: rockchip: fix rk3328-roc-cc gmac2io tx/rx_delay * HID: logitech: check the return value of create_singlethread_workqueue * HID: debug: fix race condition with between rdesc_show() and device removal * rtc: cros-ec: Fail suspend/resume if wake IRQ can't be configured * rtc: sh: Fix invalid alarm warning for non-enabled alarm * ARM: OMAP2+: add missing of_node_put after of_device_is_available * batman-adv: Reduce claim hash refcnt only for removed entry * batman-adv: Reduce tt_local hash refcnt only for removed entry * batman-adv: Reduce tt_global hash refcnt only for removed entry * batman-adv: fix warning in function batadv_v_elp_get_throughput * ARM: dts: rockchip: Fix gpu opp node names for rk3288 * reset: meson-audio-arb: Fix missing .owner setting of reset_controller_dev * ARM: dts: Fix dcan clkctrl clock for am3 * i40e: fix i40e_ptp_adjtime when given a negative delta * ixgbe: fix mdio bus registration * i40e: fix WoL support check * riscv: fix accessing 8-byte variable from RV32 * HID: quirks: Fix keyboard + touchpad on Lenovo Miix 630 * net: hns3: fix compile error * xdp: fix cpumap redirect SKB creation bug * net/mlx5: E-Switch, Protect from invalid memory access in offload fdb table * net/mlx5: E-Switch, Fix esw manager vport indication for more vport commands * bonding: show full hw address in sysfs for slave entries * net: stmmac: use correct DMA buffer size in the RX descriptor * net: stmmac: ratelimit RX error logs * net: stmmac: don't stop NAPI processing when dropping a packet * net: stmmac: don't overwrite discard_frame status * net: stmmac: fix dropping of multi-descriptor RX frames * net: stmmac: don't log oversized frames * jffs2: fix use-after-free on symlink traversal * debugfs: fix use-after-free on symlink traversal * mfd: twl-core: Disable IRQ while suspended * block: use blk_free_flush_queue() to free hctx->fq in blk_mq_init_hctx * rtc: da9063: set uie_unsupported when relevant * HID: input: add mapping for Assistant key * vfio/pci: use correct format characters * scsi: core: add new RDAC LENOVO/DE_Series device * scsi: storvsc: Fix calculation of sub-channel count * arm/mach-at91/pm : fix possible object reference leak * blk-mq: do not reset plug->rq_count before the list is sorted * arm64: fix wrong check of on_sdei_stack in nmi context * net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() * net: hns: Fix probabilistic memory overwrite when HNS driver i
[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
storage test passed for all archs ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: Fix Committed Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Released Status in linux source package in Disco: New Status in systemd source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Status in systemd package in Debian: Fix Committed Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826868] Re: Sound device not detected after resume from hibernate
** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Low -- 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/1826868 Title: Sound device not detected after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: New Status in linux-oem source package in Disco: Invalid Bug description: The patch is already in the v5.2-rc1, so don't send the patch to unstable. In the V2, I added 3 more patches. The 0001-xxx.patch is for fixing the issue of "audio doesn't work after s3/s4 on cln and glk machines", but it introduces a new issue of "screen flickering when CDCLK changes", So I added 0002/3/4-xxx.patch to fix the new issue. [Impact] After s3 or s4, the hdmi audio driver will re-probe the hw, if the hdmi monitor is not plugged before s3 or s4, the re-probe will fail on cnl and glk machines. [Fix] Keep the cdclk alive when re-probing [Test Case] I applied the patches to bionic kernel and disco kernel, and tested them on Whiskeylake, cannonlake, kabylake, skylake and geminilake machines, before s3, I verified analogue audio, hdmi audio and screen dispaly all worked well, then let the system enter s3 and resume, recheck the analogue audio, hdmi audio and screen display, all worked well too. And repeated the test 5 times. [Regression Risk] Low. I have tested the patched kernel on different Dell and Lenovo machines, they include Whiskeylake, cannonlake, kabylake, skylake and geminilake. dmesg -w shows the following: snd_hda_codec_realtek hdaudioC0D0: out of range cmd 0:20:400: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1551 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 21:22:18 2019 InstallationDate: Installed on 2019-04-24 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Stream x360 Convertible 11-ag1XX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8501 dmi.board.vendor: HP dmi.board.version: 05.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Stream x360 Convertible 11-ag1XX dmi.product.sku: 4RV86PA#ABG dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
re: autopkgtests, a few failed, but I re-ran them and they passed on the re-run. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: Fix Committed Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Released Status in linux source package in Disco: New Status in systemd source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Status in systemd package in Debian: Fix Committed Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834635] [NEW] x86/speculation: SPEC_CTRL MSR not properly set/restored on VMENTER/VMEXIT
Private bug reported:
Placeholder. Need to change Precise arch/x86/kernel/kvm/* from:
if (ibrs_enabled && (svm->spec_ctrl != SPEC_CTRL_IBRS))
wrmsrl(MSR_IA32_SPEC_CTRL, svm->spec_ctrl);
if (ibrs_enabled) {
rdmsrl(MSR_IA32_SPEC_CTRL, svm->spec_ctrl);
if (svm->spec_ctrl != SPEC_CTRL_IBRS)
wrmsrl(MSR_IA32_SPEC_CTRL, SPEC_CTRL_IBRS);
}
to:
x86_spec_ctrl_set_guest(svm->spec_ctrl, svm->virt_spec_ctrl);
x86_spec_ctrl_restore_host(svm->spec_ctrl, svm->virt_spec_ctrl);
to properly set and restore the MSR.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Information type changed from Public to Private
** Also affects: linux (Ubuntu Precise)
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/1834635
Title:
x86/speculation: SPEC_CTRL MSR not properly set/restored on
VMENTER/VMEXIT
Status in linux package in Ubuntu:
New
Status in linux source package in Precise:
New
Bug description:
Placeholder. Need to change Precise arch/x86/kernel/kvm/* from:
if (ibrs_enabled && (svm->spec_ctrl != SPEC_CTRL_IBRS))
wrmsrl(MSR_IA32_SPEC_CTRL, svm->spec_ctrl);
if (ibrs_enabled) {
rdmsrl(MSR_IA32_SPEC_CTRL, svm->spec_ctrl);
if (svm->spec_ctrl != SPEC_CTRL_IBRS)
wrmsrl(MSR_IA32_SPEC_CTRL, SPEC_CTRL_IBRS);
}
to:
x86_spec_ctrl_set_guest(svm->spec_ctrl, svm->virt_spec_ctrl);
x86_spec_ctrl_restore_host(svm->spec_ctrl, svm->virt_spec_ctrl);
to properly set and restore the MSR.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834635/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834529] Re: Disco update: 5.0.15 upstream stable release
Applied to disco/master-next branch, with the following exceptions: * "iommu/amd: Set exclusion range correctly" - already applied for LP: #1823037 ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834529 Title: Disco update: 5.0.15 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. 5.0.15 upstream stable release from git://git.kernel.org/ The following upstream stable patches should be included in the Ubuntu kernel: * net: stmmac: Use bfsize1 in ndesc_init_rx_desc * Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() * ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings * staging: greybus: power_supply: fix prop-descriptor request size * staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. * staging: most: cdev: fix chrdev_region leak in mod_exit * staging: most: sound: pass correct device when creating a sound card * ASoC: tlv320aic3x: fix reset gpio reference counting * ASoC: hdmi-codec: fix S/PDIF DAI * ASoC: stm32: sai: fix iec958 controls indexation * ASoC: stm32: sai: fix exposed capabilities in spdif mode * ASoC: stm32: sai: fix race condition in irq handler * ASoC:soc-pcm:fix a codec fixup issue in TDM case * ASoC:hdac_hda:use correct format to setup hda codec * ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform * ASoC: dpcm: prevent snd_soc_dpcm use after free * ASoC: nau8824: fix the issue of the widget with prefix name * ASoC: nau8810: fix the issue of widget with prefixed name * ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate * ASoC: rt5682: Check JD status when system resume * ASoC: rt5682: fix jack type detection issue * ASoC: rt5682: recording has no sound after booting * ASoC: wm_adsp: Add locking to wm_adsp2_bus_error * clk: meson-gxbb: round the vdec dividers to closest * ASoC: stm32: dfsdm: manage multiple prepare * ASoC: stm32: dfsdm: fix debugfs warnings on entry creation * ASoC: cs4270: Set auto-increment bit for register writes * ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol * drm/omap: hdmi4_cec: Fix CEC clock handling for PM * IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state * IB/hfi1: Eliminate opcode tests on mr deref * IB/hfi1: Fix the allocation of RSM table * MIPS: KGDB: fix kgdb support for SMP platforms. * ASoC: tlv320aic32x4: Fix Common Pins * drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() * perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS * perf/x86/intel: Initialize TFA MSR * linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() * iov_iter: Fix build error without CONFIG_CRYPTO * xtensa: fix initialization of pt_regs::syscall in start_thread * ASoC: rockchip: pdm: fix regmap_ops hang issue * drm/amdkfd: Add picasso pci id * drm/amdgpu: Adjust IB test timeout for XGMI configuration * drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list * drm/amd/display: fix cursor black issue * ASoC: cs35l35: Disable regulators on driver removal * objtool: Add rewind_stack_do_exit() to the noreturn list * slab: fix a crash by reading /proc/slab_allocators * drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind * virtio_pci: fix a NULL pointer reference in vp_del_vqs * RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove * RDMA/hns: Fix bug that caused srq creation to fail * KEYS: trusted: fix -Wvarags warning * scsi: csiostor: fix missing data copy in csio_scsi_err_handler() * drm/mediatek: fix possible object reference leak * drm/mediatek: fix the rate and divder of hdmi phy for MT2701 * drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy * drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy * drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy * drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy * ASoC: Intel: kbl: fix wrong number of channels * ASoC: stm32: sai: fix master clock management * ALSA: hda: Fix racy display power access * virtio-blk: limit number of hw queues by nr_cpu_ids * blk-mq: introduce blk_mq_complete_request_sync() * nvme: cancel request synchronou
[Kernel-packages] [Bug 1782177] Re: Screen sometimes jumps to full brightness on resume from suspend
Does this issue still happen? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782177 Title: Screen sometimes jumps to full brightness on resume from suspend Status in Linux: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: At night, I usually turn my brightness down as far as it will go using the brightness keys. This makes it dim, but visible and not off. When I walk away for a while, the screen goes to sleep, and when I come back and move the mouse, the screen jumps to full brightness, which is very unpleasant at night. Investigating, it seems that the brightness in intel_backlight is getting reset to 4437, but the one in acpi_video0 reads 0. $ for file in brightness max_brightness actual_brightness; > do > for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 4437 /sys/class/backlight/acpi_video0/brightness : 0 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 4437 /sys/class/backlight/acpi_video0/actual_brightness : 0 After I press the button to increase the brightness one notch, they are back in sync, and then I can turn it back down as well. $ for file in brightness max_brightness actual_brightness; > do >for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 53 /sys/class/backlight/acpi_video0/brightness : 1 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 53 /sys/class/backlight/acpi_video0/actual_brightness : 1 This is on a fresh install of xubuntu 18.04. Seems like a regression from 16.04, which I ran on the same laptop without this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1782177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4
Sorry for the late reply. The next step is to find out if we need to disable both ASPM L0s and ASPM L1, or just disable one of them can solve our issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834315] Re: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan
Okay, thanks for explaining. I'll remove the reverts from 5.2. ** Changed in: linux (Ubuntu) Assignee: Seth Forshee (sforshee) => (unassigned) ** Changed in: linux (Ubuntu) Status: Fix Committed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834315 Title: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: [Impact] As reported in #1833067 and https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/comments/7 some glibc testcases are still regressing on i386 after applying both the following commits: commit 379d98ddf41344273d9718556f761420f4dc80b3 Author: Alistair Strachan Date: Fri Aug 3 10:39:31 2018 -0700 x86: vdso: Use $LD instead of $CC to link commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 Author: Alistair Strachan Date: Fri Dec 14 14:36:37 2018 -0800 x86/vdso: Pass --eh-frame-hdr to the linker [Fix] Revert both these patches to restore the original behaviour. [Test] ADT tests for glibc. [Regression Potential] Low. This restores the status quo before the original change to vdso/x86/Makefile to restore the original linker behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793846] Re: Regression: gamepad Redragon Seymur 2 no longer works properly
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793846 Title: Regression: gamepad Redragon Seymur 2 no longer works properly Status in linux package in Ubuntu: Fix Released Bug description: The gamepad Redragon Seymur 2 right analog stick no longer works properly with kernel versions at least 4.18 and newer. On 4.17.19 they work properly. I already reported this regression on kernel bugzilla but it did not receive attention there and Ubuntu Cosmic release is going to be soon, so I think it's relevant it's reported here too. This is the link of the bugzilla report I wrote: https://bugzilla.kernel.org/show_bug.cgi?id=200995 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.396 CurrentDesktop: XFCE Date: Sat Sep 22 04:14:39 2018 IwConfig: lono wireless extensions. ens2 no wireless extensions. LiveMediaBuild: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180921) Lsusb: Bus 002 Device 002: ID 0480:0200 Toshiba America Inc External Disk Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0079:0006 DragonRise Inc. PC TWIN SHOCK Gamepad Bus 001 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcFB: 0 virtiodrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.0 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1564463] Re: Joystick Dragonrise Axes confused in Ubuntu 14.04
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1564463 Title: Joystick Dragonrise Axes confused in Ubuntu 14.04 Status in linux package in Ubuntu: Fix Released Status in linux package in Debian: Confirmed Bug description: In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly working. Its conflicting and superimposed by axis 0 (left-right of the left joystick) Axis 2 was allready behaving bad in eralier versions now its completly broken. Also jscal complains when applying stored settings from earlier ubuntu versions as the joystick now has 6 axes [0-5] and used to have 7, but this seems correct. The Dragonrise chip seems to be very widespread among different speedlink and LinQ models There is a related bugreport in Debian Bug-Tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606 that makes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834549] Re: Wifi won't load
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834549 Title: Wifi won't load Status in linux package in Ubuntu: New Bug description: To me this looks different from: 1. https://lkml.org/lkml/2019/4/11/861 2. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537183 version.log: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 00:14.3 Network controller: Intel Corporation Wireless-AC 9560 [Jefferson Peak] (rev 10) /var/log/kern.log: ... Jun 27 15:03:41 user-ThinkPad-P52 kernel: [274383.172489] CPU5: Package temperature/speed normal Jun 27 15:10:04 user-ThinkPad-P52 kernel: [274765.973921] thinkpad_acpi: unhandled HKEY event 0x6031 Jun 27 15:10:04 user-ThinkPad-P52 kernel: [274765.973924] thinkpad_acpi: please report the conditions when this event happened to ibm-acpi-de...@lists.sourceforge.net Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.439876] iwlwifi :00:14.3: Error sending STATISTICS_CMD: time out after 2000ms. Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.439892] iwlwifi :00:14.3: Current CMD queue read_ptr 10 write_ptr 11 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440076] iwlwifi :00:14.3: Start IWL Error Log Dump: Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440084] iwlwifi :00:14.3: Status: 0x0100, count: 6 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440090] iwlwifi :00:14.3: Loaded firmware version: 38.c0e03d94.0 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440096] iwlwifi :00:14.3: 0x0034 | NMI_INTERRUPT_WDG Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440102] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440107] iwlwifi :00:14.3: 0x | trm_hw_status1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440112] iwlwifi :00:14.3: 0x00454EAA | branchlink2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440118] iwlwifi :00:14.3: 0x0045E8C2 | interruptlink1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440123] iwlwifi :00:14.3: 0xE630 | interruptlink2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440128] iwlwifi :00:14.3: 0x | data1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440133] iwlwifi :00:14.3: 0x03FF | data2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440138] iwlwifi :00:14.3: 0x03FF | data3 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440144] iwlwifi :00:14.3: 0x6AC0A6B1 | beacon time Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440149] iwlwifi :00:14.3: 0xD15FB958 | tsf low Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440155] iwlwifi :00:14.3: 0x002C | tsf hi Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440160] iwlwifi :00:14.3: 0x | time gp1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440166] iwlwifi :00:14.3: 0xF36C18D6 | time gp2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440171] iwlwifi :00:14.3: 0x0001 | uCode revision type Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440176] iwlwifi :00:14.3: 0x0026 | uCode version major Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440181] iwlwifi :00:14.3: 0xC0E03D94 | uCode version minor Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440187] iwlwifi :00:14.3: 0x0312 | hw version Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440192] iwlwifi :00:14.3: 0x00489008 | board version Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440197] iwlwifi :00:14.3: 0x0A69001C | hcmd Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440203] iwlwifi :00:14.3: 0x22822002 | isr0 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440208] iwlwifi :00:14.3: 0x0080 | isr1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440213] iwlwifi :00:14.3: 0x08005802 | isr2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440218] iwlwifi :00:14.3: 0x4040BDC3 | isr3 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440223] iwlwifi :00:14.3: 0x | isr4 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440229] iwlwifi :00:14.3: 0x0A68001C | last cmd Id Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440235] iwlwifi :00:14.3: 0x | wait_event Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440240] iwlwifi :00:14
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Disco) Status: New => Invalid -- 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/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: New Status in linux-oem source package in Disco: Invalid Bug description: === SRU Justification === [Impact] Qualcomm WiFi/Bluetooth may disappear after boot. [Fix] Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM L1. Pull back the device to full power before shutdown imitates the behavior on Windows. [Test] The affected user confimed it fixes the issue. I can also confirm that a) The power drain in S5 is much lower, b) Both WiFi and Bluetooth are always present during reboot stress test. [Regression Potential] Low. Only a limited number of USB2 devices that support LPM. === Original Bug Report === Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUM
[Kernel-packages] [Bug 1832316] Re: shiftfs: allow changing ro/rw for subvolumes
** Changed in: linux (Ubuntu Disco) 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/1832316 Title: shiftfs: allow changing ro/rw for subvolumes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: New Bug description: SRU Justification Impact: Stéphane reported regression for btrfs workloads employing shiftfs. Unprivileged users can already toggle whether a subvolume will be ro or rw. This is broken on current shiftfs as we haven't whitelisted these ioctls(). Fix: To enable this with shiftfs we need to whitelist BTRFS_IOC_FS_INFO, BTRFS_IOC_SUBVOL_GETFLAGS, BTRFS_IOC_SUBVOL_SETFLAGS. All of them should be safe for unprivileged users. Regression Potential: Limited to shiftfs. Test Case: Tested with LXD running shiftfs on top of btrfs and verified btrfs subvolumes can be made ro or rw. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832909] Re: Cache line contention prevents scaling of 100Gbps performance
** Changed in: linux (Ubuntu Disco) 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/1832909 Title: Cache line contention prevents scaling of 100Gbps performance Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] 100Gbps network performance, as measured on an hns3 controller, doesn't scale as queue size goes up. [Test Case] Use a traffic generator instrument to generate load, using the SUT as an IP forwarder. 19.04 today: 8 queue 12 queue 16 queue 24 queue 37G 45G 38G 33G With the patch applied: 8 queue 12 queue 16 queue 24 queue 37G 50G 47G 47G [Fix] 14bd9a607f908 iommu/iova: Separate atomic variables to improve performance [Regression Risk] The patch makes no functional change, just reorders members of a structure. However, it is possible that this has unforeseen negative performance impacts on some platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
Hi Viktor,
These patches were not applied for the SRU cycle "03-Jun through
30-Jun", they are committed now for the cycle starting next week
("01-Jul through 21-Jul"). Please check https://kernel.ubuntu.com/ for
the current schedules.
Thank you.
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1825942
Title:
kernel crash : net_sched race condition in tcindex_destroy()
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
It is possible to trigger a NULL pointer dereference in
tcindex_delete() with a simple reproducer script, this is because in
tcindex_set_parms() when old_r doesn't exist we set the new exts to
cr.exts that can be uninitialized, triggering the NULL pointer
dereference.
In addition to that we may also hit a race condition in
tcindex_destroy() (as pointed out in the original bug report and also
here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542#10),
that is also fixed upstream, but it requires 4b79817f7add "net_sched:
switch to rcu_work".
However adding these changes introduces three memory leak problems in
cls_tcindex (that can be easily verified using the same test case).
These leaks are also fixed upstream by 711ff09f3330 "net_sched: fix a
memory leak in cls_tcindex" and 000d2aeda70c "net_sched: fix two more
memory leaks in cls_tcindex", so we need to backport also these two
additional fixes.
After all these fixes are applied the test case doesn't seem to
trigger any bug.
[Test Case]
#!/bin/sh -ex
modprobe ifb
while true; do
tc qdisc add dev ifb0 root handle 2:0 prio bands 5
tc qdisc add dev ifb0 parent 2:5 sfq
tc filter add dev ifb0 parent 2:0 protocol ip prio 5 handle 0 tcindex
mask 0 classid 2:5 pass_on
tc qdisc del dev ifb0 root || true
done
[Fix]
* Fixes required to solve this problem:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2df8bee5654bb2b7312662ca6810d4dc16b0b67f
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8015d93ebd27484418d4952284fd02172fa4b0b2
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=033b228e7f26b29ae37f8bfa1bc6b209a5365e9f
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1db817e75f5b9387b8db11e37d5f0624eb9223e0
[Regression Potential]
* All upstream fixes, tested on the affected platform, backport
changes are minimal.
[Original bug report]
I am running into a kernel crash issue using latest Ubuntu 4.15 kernel.
It does not appear to have been fixed in Ubuntu-4.15.0-48.51.
This crash has also been reported for debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542
The kernel crash issue was fixed in February in the Linux kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=056a17982adbd52b2a6c5ec6266cee4521cd931b
I did test one of the recent kernel-ppa/mainline kernels, more specifically:
linux-image-unsigned-4.19.34-041934-generic_4.19.34-041934.201904051741_amd64.deb
It seems to fix the problem, that is, no crashes experienced so far.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833809] Re: TouchPad and Mousepad not working
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833809 Title: TouchPad and Mousepad not working Status in linux package in Ubuntu: New Bug description: I am unable to use touchpad in lenovo ideapad 330 after installing Ubuntu 18.04 in my laptop, and touchpad is working fine in window 10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prateek1309 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 22 17:09:59 2019 InstallationDate: Installed on 2019-06-22 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81DE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=d2ff3cf0-aca3-4db0-9d5c-3c40789eca56 ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN46WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN46WW:bd07/26/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833474] Re: Radom & frequent total crashes since upgrade to 19.04
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833474 Title: Radom & frequent total crashes since upgrade to 19.04 Status in linux package in Ubuntu: New Bug description: Hi, I'm using an ASUS X751L laptop for several years with no (=a few manageable) problem(s). Two weeks ago, I switched to Xunbuntu 19.04, by: - changing the lines in the /etc/sources.list - running apt-get dist-upgrade Since then, the computer randomly totally freezes ~twice a day. Even after another dist-upgrade this morning... When I say "totally freezes", I mean: - Mouse is froozen, if there was sound playing (be it movie or music, played either with mplayer or vlc), then the last 1/2 second loops indefinitely - CTRL-ALT-Fn do not work - There's nothing in the logs: kern.log, syslog, dmesg... appart some garbage chars (like ^@^@^@...) that sometimes gets appended in syslog at crash time. - Even when activated Magic SysReq (ALT-SysReq-RSEIUB) do not work - Alt-SysReq 1 + Alt-SysReq t do not create anything in /var/crash (there are some files for qemu & xfce4-panel, that I already reported) - Following https://wiki.ubuntu.com/Kernel/CrashdumpRecipe , I installed linux-crashdump, and verified it correctly sets the boot line option, but nothing gets created in /var/crash when computer crashes (apart a kexec_cmd file that simply lists the boot line args). - Quick (2/3 sec) press on the power button does nothing - Long (10 sec) press on the power button is the only way to regain control... - I've tried to run Memtest86+ (even if I'm sure RAM is not the problem as it started occurring only after dist-upgrade to 19.04), but the system is UEFI, so option is not in the grub menu. I'll try to make a USB stick to test the RAM FYI, the internal wifi card (rtl8723) has always caused troubles: HD write slowdowns, audio device locks, etc (from what I guess, it overfills some internal bus...). So I deactivate it at boot by removing the module, and I use another external Wifi dongle (rt2800usb) $ uname -a Linux gmuller-X751LAB 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:52:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # Note: crashes occurred also with 5.0.0-15 Does anyone has any hints/tips on how I could get more info & target where the problem comes from? because as-is the computer is just unusable... In the attached log files, the crash occurred right before my manual reboot at 15:17:24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832625] Re: [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) 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/1832625 Title: [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: New Bug description: SRU Justification: == [Impact] * 'zkey validate' shows wrong information about master key registers * this might lead to unsuccessful usage of pkeys, although the master key and the derived keys are correct [Fix] * ebb7c695d3bc7a4986b92edc8d9ef43491be183e ebb7c69 "pkey: Indicate old mkvp only if old and current mkvp are different" [Test Case] * set a CCA master key * generate a pkey * 'change' (or better set) the current CCA master key to the exact same master key again which is currently in use * execute a 'zkey validate' [Regression Potential] * The regression potential can be considered as very low since this is purely s390x specific * changes are limited to a single file (drivers/s390/crypto/pkey_api.c) * patch changes only one line (actually expands an if stmt) * and all this happens only in a very specific situation (in case a new master key was set, using the same key as before) [Other Info] * Problem was found during tests at IBM and is a so called 'preventive fix' __ Description: pkey: Indicate old mkvp only if old and curr. mkvp are different Symptom: zkey validate shows wrong information about master key registers Problem: When the CCA master key is set twice with the same master key, then the old and the current master key are the same and thus the verification patterns are the same, too. The check to report if a secure key is currently wrapped by the old master key erroneously reports old mkvp in this case. Solution: Fix this by checking current and old mkvp and report OLD only if current and old mkvp are different. Reproduction: Change the CCA master key but set the exact same master key that is already used. Then do a 'zkey validate' command on a secure key Component: kernel 5.1 rc1 Upstream-ID: ebb7c695d3bc7a4986b92edc8d9ef43491be183e This fix will be provided with kernel >=5.1 , will be integrate in 19.10 by default. But should also be applied to 18.04 and 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1832625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium -- 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/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: New Status in linux-oem source package in Disco: Invalid Bug description: === SRU Justification === [Impact] Qualcomm WiFi/Bluetooth may disappear after boot. [Fix] Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM L1. Pull back the device to full power before shutdown imitates the behavior on Windows. [Test] The affected user confimed it fixes the issue. I can also confirm that a) The power drain in S5 is much lower, b) Both WiFi and Bluetooth are always present during reboot stress test. [Regression Potential] Low. Only a limited number of USB2 devices that support LPM. === Original Bug Report === Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/
[Kernel-packages] [Bug 1834549] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834549 Title: Wifi won't load Status in linux package in Ubuntu: Confirmed Bug description: To me this looks different from: 1. https://lkml.org/lkml/2019/4/11/861 2. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537183 version.log: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 00:14.3 Network controller: Intel Corporation Wireless-AC 9560 [Jefferson Peak] (rev 10) /var/log/kern.log: ... Jun 27 15:03:41 user-ThinkPad-P52 kernel: [274383.172489] CPU5: Package temperature/speed normal Jun 27 15:10:04 user-ThinkPad-P52 kernel: [274765.973921] thinkpad_acpi: unhandled HKEY event 0x6031 Jun 27 15:10:04 user-ThinkPad-P52 kernel: [274765.973924] thinkpad_acpi: please report the conditions when this event happened to ibm-acpi-de...@lists.sourceforge.net Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.439876] iwlwifi :00:14.3: Error sending STATISTICS_CMD: time out after 2000ms. Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.439892] iwlwifi :00:14.3: Current CMD queue read_ptr 10 write_ptr 11 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440076] iwlwifi :00:14.3: Start IWL Error Log Dump: Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440084] iwlwifi :00:14.3: Status: 0x0100, count: 6 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440090] iwlwifi :00:14.3: Loaded firmware version: 38.c0e03d94.0 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440096] iwlwifi :00:14.3: 0x0034 | NMI_INTERRUPT_WDG Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440102] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440107] iwlwifi :00:14.3: 0x | trm_hw_status1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440112] iwlwifi :00:14.3: 0x00454EAA | branchlink2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440118] iwlwifi :00:14.3: 0x0045E8C2 | interruptlink1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440123] iwlwifi :00:14.3: 0xE630 | interruptlink2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440128] iwlwifi :00:14.3: 0x | data1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440133] iwlwifi :00:14.3: 0x03FF | data2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440138] iwlwifi :00:14.3: 0x03FF | data3 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440144] iwlwifi :00:14.3: 0x6AC0A6B1 | beacon time Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440149] iwlwifi :00:14.3: 0xD15FB958 | tsf low Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440155] iwlwifi :00:14.3: 0x002C | tsf hi Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440160] iwlwifi :00:14.3: 0x | time gp1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440166] iwlwifi :00:14.3: 0xF36C18D6 | time gp2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440171] iwlwifi :00:14.3: 0x0001 | uCode revision type Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440176] iwlwifi :00:14.3: 0x0026 | uCode version major Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440181] iwlwifi :00:14.3: 0xC0E03D94 | uCode version minor Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440187] iwlwifi :00:14.3: 0x0312 | hw version Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440192] iwlwifi :00:14.3: 0x00489008 | board version Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440197] iwlwifi :00:14.3: 0x0A69001C | hcmd Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440203] iwlwifi :00:14.3: 0x22822002 | isr0 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440208] iwlwifi :00:14.3: 0x0080 | isr1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440213] iwlwifi :00:14.3: 0x08005802 | isr2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440218] iwlwifi :00:14.3: 0x4040BDC3 | isr3 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440223] iwlwifi :00:14.3: 0x | isr4 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440229] iwlwifi :00:14.3: 0x0A68001C | last cmd Id Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440235] iwlwifi :00:14.3: 0x | wait_event Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440240] iwlwifi :00:14.3: 0x | l2p_control Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440245] iwlwifi :00:14.3: 0x0020 | l2p_duration Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440250] iwlwifi :00:14.3: 0x | l2p_mhvalid Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440256] iwlwifi :00:14.3: 0x | l2p_ad
[Kernel-packages] [Bug 1827750] Re: Not boot with EFI
** Changed in: linux-raspi2 (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux-raspi2 (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux-raspi2 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1827750 Title: Not boot with EFI Status in linux-raspi2 package in Ubuntu: Incomplete Status in linux-raspi2 source package in Bionic: Fix Committed Status in linux-raspi2 source package in Cosmic: Fix Committed Status in linux-raspi2 source package in Disco: Fix Committed Bug description: Impact: The linux-raspi2 kernel doesn't have the necessary UEFI hooks to boot on a UEFI enabled system. Fix: Enable the relevant UEFI options (see the attached patch). How to test: On a patched kernel, UEFI presence will be check during boot: $ dmesg | grep -i eufi ... [0.00] efi: UEFI not found. ... Regression potential: Very low, some config option changes that have been enabled in generic for a long while. -- Hello. I can't boot with linux-raspi2 kernel, but linux-generic work fine. Please add support kernel option CONFIG_U(EFI)_STUB=y as default. Thanks. os: ubuntu 18.04 lts arm64 hw: raspberry pi 3b (+ tiano core uefi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1827750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833809] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833809 Title: TouchPad and Mousepad not working Status in linux package in Ubuntu: Confirmed Bug description: I am unable to use touchpad in lenovo ideapad 330 after installing Ubuntu 18.04 in my laptop, and touchpad is working fine in window 10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prateek1309 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 22 17:09:59 2019 InstallationDate: Installed on 2019-06-22 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81DE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=d2ff3cf0-aca3-4db0-9d5c-3c40789eca56 ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN46WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN46WW:bd07/26/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833474] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1833474 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833474 Title: Radom & frequent total crashes since upgrade to 19.04 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I'm using an ASUS X751L laptop for several years with no (=a few manageable) problem(s). Two weeks ago, I switched to Xunbuntu 19.04, by: - changing the lines in the /etc/sources.list - running apt-get dist-upgrade Since then, the computer randomly totally freezes ~twice a day. Even after another dist-upgrade this morning... When I say "totally freezes", I mean: - Mouse is froozen, if there was sound playing (be it movie or music, played either with mplayer or vlc), then the last 1/2 second loops indefinitely - CTRL-ALT-Fn do not work - There's nothing in the logs: kern.log, syslog, dmesg... appart some garbage chars (like ^@^@^@...) that sometimes gets appended in syslog at crash time. - Even when activated Magic SysReq (ALT-SysReq-RSEIUB) do not work - Alt-SysReq 1 + Alt-SysReq t do not create anything in /var/crash (there are some files for qemu & xfce4-panel, that I already reported) - Following https://wiki.ubuntu.com/Kernel/CrashdumpRecipe , I installed linux-crashdump, and verified it correctly sets the boot line option, but nothing gets created in /var/crash when computer crashes (apart a kexec_cmd file that simply lists the boot line args). - Quick (2/3 sec) press on the power button does nothing - Long (10 sec) press on the power button is the only way to regain control... - I've tried to run Memtest86+ (even if I'm sure RAM is not the problem as it started occurring only after dist-upgrade to 19.04), but the system is UEFI, so option is not in the grub menu. I'll try to make a USB stick to test the RAM FYI, the internal wifi card (rtl8723) has always caused troubles: HD write slowdowns, audio device locks, etc (from what I guess, it overfills some internal bus...). So I deactivate it at boot by removing the module, and I use another external Wifi dongle (rt2800usb) $ uname -a Linux gmuller-X751LAB 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:52:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # Note: crashes occurred also with 5.0.0-15 Does anyone has any hints/tips on how I could get more info & target where the problem comes from? because as-is the computer is just unusable... In the attached log files, the crash occurred right before my manual reboot at 15:17:24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832048] Re: hinic: fix oops due to race in set_rx_mode
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) 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/1832048 Title: hinic: fix oops due to race in set_rx_mode Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Fix Committed Bug description: [Impact] It is possible for the hinic driver to oops after the module is removed and reinserted. [Test Case] while :; do sudo modprobe -r hinic; modprobe hinic; done [Fix] From linux-next: 66350023d5756 hinic: fix a bug in set rx mode [Regression Risk] Patch is local to the hinic driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832623] Re: [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) 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/1832623 Title: [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: New Bug description: SRU Justification: == [Impact] * Wrong encryption/decryption with gcm-aes-s390 on z14. * gcm-aes-s390 does not process scatter-gather input and output lists correctly if list entries of sizes being not multiples of the blocksize (16 bytes) are used, which results in wrong calculations. [Fix] * bef9f0ba300a55d79a69aa172156072182176515 bef9f0b "s390/crypto: fix gcm-aes-s390 selftest failures" [Test Case] * z14 with kernel >= 5.1 needed * If disabled, enable the crypto self tests. * Monitor syslog during modprobe of the aes_s390 kernel module. As this module usually gets automatically inserted during system startup you may need to unload the aes_s390 kernel module before re-inserting it. * Without the fix a message like "kernel: alg: aead: gcm-aes-s390 encryption test failed (wrong result) on test vector 1,..." will show up. * With the fix, all selftests will pass and nothing is reported in syslog. [Regression Potential] * The regression potential can be considered as low since this is purely s390x specific * affects one mode of the hardware crypto facility CPACF * and happens only on z14 (since z14 is the only model that currently supports the gcm-aes-s390 mode). * Applications using aes-gcm via the AF_ALG interface are not affected since this API ensures scatter/gather list entries with chunk sizes in multiples of 16 bytes. * Changes are limited to a single s390x crypto file /arch/s390/crypto/aes_s390.c [Other Info] * Problem was found during tests at IBM and is a so called 'preventive fix' * Since this affects z14 only, final test need to be done by IBM. * Applied cleanly for me on bionic master-next. __ Description: kernel: Fix gcm-aes-s390 wrong scatter-gather list processing Symptom: gcm-aes-s390 wrong en/decryption processing Problem: The current gcm aes s390 implementation does not process scatter-gather input and output lists correct when list entries with sizes not multiples of the blocksize of 16 bytes are used. Result may be wrong calculated encrypted or decrypted data. This can only happen on z14 (this is the only machine which supports aes-gcm in hardware via CPACF). Please note that applications using aes-gcm via the AF_ALG interface are not affected as this API ensures scatter/gather list entries with chunk sizes in multiples of 16 bytes. However, all exploiters of aes-gcm within the kernel may be affected. Solution: Rework of the scatter/gather walk within the aes_s390 kernel module implementation with the goal to support any list entry size. Reproduction: With kernel 5.1 there has been an improvement on the crypto selftests. There are now tests run with fragmented scatter/gather lists. So: 1. You need at least a z14 and kernel >= 5.1. 2. If disabled, enable the crypto self tests. 3. Watch for syslog entries during modprobe of the aes_s390 kernel module. As this module usually gets automatically inserted during system startup you may need to unload the aes_s390 kernel module before re-inserting it. 4. Without the fix something like "kernel: alg: aead: gcm-aes-s390 encryption test failed (wrong result) on test vector 1,..." will show up. With the fix, all selftests will pass and nothing is reported in syslog. Component: kernel Upstream-ID: bef9f0ba300a55d79a69aa172156072182176515 This request is targeted for 19.10, but should also be applied to 18.04 and 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/u
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium -- 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/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: New Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
** Changed in: qemu (Ubuntu Disco) Status: Confirmed => In Progress ** Changed in: qemu (Ubuntu Cosmic) Status: Confirmed => In Progress ** Changed in: qemu (Ubuntu Eoan) Assignee: Rafael David Tinoco (rafaeldtinoco) => Christian Ehrhardt îż (paelzer) ** Changed in: qemu (Ubuntu Bionic) Status: Confirmed => 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/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: In Progress Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: In Progress Status in linux source package in Cosmic: Confirmed Status in qemu source package in Cosmic: In Progress Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: In Progress Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ïŒCPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704433] Re: [Feature] Crystal Ridge - Use FS DAX radix tree as a cache to service page faults
Intel upstream think it is not must for OSV, so close it as invalid. ** Changed in: intel Status: Triaged => 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/1704433 Title: [Feature] Crystal Ridge - Use FS DAX radix tree as a cache to service page faults Status in intel: Invalid Status in linux package in Ubuntu: Incomplete Bug description: Description We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches. Target Kernel:TBD Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1704433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Changed in: ubuntu-power-systems
Status: Fix Committed => 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/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
-- Firmware information on Baltar --
pnor: P9DSU20190404_IBM_prod_sign.pnor
bmc: SMT_P9_206.bin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831065] Re: does not detect headphone when there is no other output devices
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed -- 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/1831065 Title: does not detect headphone when there is no other output devices Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Bug description: These two patches are already in the kernel-v5.0, so only B and C need these two patches. [Impact] On a Dell machine, there is no other output devices but a headphone on it, when plugging headset, the headset-mic can't work. [Fix] The headphone detection method is buggy, the driver can't detect the headphone, then the driver will not initialize for headset-mic, after applying these patches, the problem is fixed. [Test Case] Plug headset and record the sound from headset-mic, it works well. [Regression Risk] Low. the patch just change the headphone detection function, and the function is already in the kernel from 5.0-rc, no bug is reported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772412] Re: zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343) that hangs the system completely
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772412
Title:
zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343)
that hangs the system completely
Status in linux package in Ubuntu:
Invalid
Status in zfs-linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in zfs-linux source package in Bionic:
New
Bug description:
SRU Bionic
== SRU Justification ==
Intensive I/O such as performed by ZFS send/receive can cause hangs because
of monopolization of the global system_taskq. The outcome is that z_zvol hung
tasks occur and I/O gets blocked.
== Fix ==
Upstream ZFS commit 77d8a0f1a4d0b2f59cee63088f7987cb38e66538 ("Fix
hung z_zvol tasks during 'zfs receive'") fixes this issue, it adds a
dedicated per-pool prefetch taskq that prevents the traverse code from
monopolizing the global (and limited) system_taskq by inappropriately
scheduling long running tasks on it. This fixes the z_zvol hung tasks.
A trivial backport is required for Bionic ZFS.
== Testcase ==
Perform large send/receives. Occasionally they lock up. With the fix,
this issue is addressed and no more lockups occur. Also must pass the
full ZFS ubuntu autotest tests to prove no regressions occur.
== Regression Potential ==
This fix adds more per-pool prefetch taskq's so we have more kernel
resources being used. There is therefore a very small risk that this
may impact ZFS running on memory and CPU constrained systems.
However, the fix is small, has been upstream for a while and is in
Cosmic+ releases and has not caused any regressions, so I think this
is a relatively safe fix.
--
I have experienced the problems fixed by this commit
https://github.com/zfsonlinux/zfs/pull/7343 a few times on my NAS. The
system hangs completely when it occurs. It looks like 0.7.9 brings
other interesting bug fixes that potentially freeze the system.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772412/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833716 Title: System crashes on hot adding a core with drmgr command (4.15.0-48-generic) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Bug description: [Impact] On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to crash. The patches identified to fix these issues disables changing the NUMA associations for CPUs and Memory at runtime by default. [Test] # drmgr -c cpu -r -q 1 # drmgr -c cpu -a -q 1 Test kernel available in ppa:ubuntu-power-triage/lp1833716 Please see comment #2 for before and after results with the patches applied. [Fix] 558f86493df0 powerpc/numa: document topology_updates_enabled, disable by default 2d4d9b308f8f powerpc/numa: improve control of topology updates [Regression Potential] The two patches relate to powerpc/numa and does not impact other architectures or platform code. Regression potential is low. [Other Information] == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530 TRAP: 0380 Not tainted (4.15.0-48-generic) [ 218.555776] MSR: 80009033 CR: 22824228 XER: 0004 [ 218.555789] CFAR: c0176920 SOFTE: 1 [ 218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 c001f7bfd200 [ 218.555789] GPR04: 0001 0008 0010 [ 218.555789] GPR08: 0018 c001f7bfd408 [ 218.555789] GPR12: 8000 c7a35800 0007 c001f549d900 [ 218.555789] GPR16: 0040 c1722494 c001f0f29400 0001 [ 218.555789] GPR20: c001ffb68580 0008 c11d8580 c171dd78 [ 218.555789] GPR24: e830 ec30 12af [ 218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 9332ae80f961139f [ 218.555859] NIP [c01768cc] free_sched_groups.part.2+0x4c/0xf0 [ 218.555866] LR [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555871] Call Trace: [ 218.555875] [c001f5f1f7b0] [ec30] 0xec30 (unreliable) [ 218.555884] [c001f5f1f7f0] [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555892] [c001f5f1f820] [c0176eb0] cpu_attach_domain+0xf0/0x870 [ 218.555900] [c001f5f1f960] [
[Kernel-packages] [Bug 1833952] Re: linux: 4.18.0-25.26 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 backports: bug 1833950 (bionic/linux-hwe) derivatives: bug 1833936 (linux-raspi2), bug 1833940 (linux-aws), bug 1833946 (linux-azure), bug 1833948 (linux-gcp), bug 1833949 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:32 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:34 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1833952 Title: linux: 4.18.0-25.26 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1833950 (bionic/linux-hwe) derivatives: bug 1833936 (linux-raspi2), bug 1833940 (linux-aws), bug 1833946 (linux-azure), bug 1833948 (linux-gcp), bug 1833949 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Security phase-changed: Friday, 28. June 2019 14:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828989] Re: ftrace in ubuntu_kernel_selftests complains "Illegal number" because of the absence of tput
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828989 Title: ftrace in ubuntu_kernel_selftests complains "Illegal number" because of the absence of tput Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Bug description: == Justification == Issue found in Disco, the ftrace test will complain about: ./ftracetest: 163: [: Illegal number: This is because the tput command failed and returns nothing for the shell script comparison. == Fix == * 0e27ded1 (selftests/ftrace: Handle the absence of tput) This patches can be cherry-picked into Disco after the patch for bug 1828995 has landed (4ce55a9c). == Test == Tested with a P8 box, problem can be solved with this patch. == Regression Potential == No regression is expected. It's just fixing the testing tool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833934] Re: linux: 5.0.0-20.21 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 backports: bug 1833930 (bionic/linux-hwe-edge), bug 1833932 (bionic/linux-oem-osp1) derivatives: bug 1833921 (linux-raspi2), bug 1833922 (linux-aws), bug 1833924 (linux-azure), bug 1833927 (linux-gcp), bug 1833928 (linux-kvm), bug 1833929 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:31 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:33 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1833934 Title: linux: 5.0.0-20.21 -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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1833930 (bionic/linux-hwe-edge), bug 1833932 (bionic/linux-oem-osp1) derivatives: bug 1833921 (linux-raspi2), bug 1833922 (linux-aws), bug 1833924 (linux-azure), bug 1833927 (linux-gcp), bug 1833928 (linux-kvm), bug 1833929 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Security phase-changed: Friday, 28. June 2019 14:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833987] Re: linux: 4.15.0-54.58 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 backports: bug 1833986 (xenial/linux-hwe), bug 1834091 (xenial/linux-azure) derivatives: bug 1833954 (pc-kernel), bug 1833955 (pc-lowlatency-kernel), bug 1833957 (linux-raspi2), bug 1833960 (linux-snapdragon), bug 1833962 (linux-oem), bug 1833967 (linux-aws), bug 1833973 (linux-gcp), bug 1833975 (linux-gke-4.15), bug 1833976 (linux-kvm), bug 1833979 (linux-oracle), bug 1833980 (linux-fips), bug 1834528 (linux-ibm-gt) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 15:03 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:35 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1833987 Title: linux: 4.15.0-54.58 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1833986 (xenial/linux-hwe), bug 1834091 (xenial/linux-azure) derivatives: bug 1833954 (pc-kernel), bug 1833955 (pc-lowlatency-kernel), bug 1833957 (linux-raspi2), bug 1833960 (linux-snapdragon), bug 1833962 (linux-oem), bug 1833967 (linux-aws), bug 1833973 (linux-gcp), bug 1833975 (linux-gke-4.15), bug 1833976 (linux-kvm), bug 1833979 (linux-oracle), bug 1833980 (linux-fips), bug 1834528 (linux-ibm-gt) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Security phase-changed: Friday, 28. June 2019 14:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833921] Re: linux-raspi2: 5.0.0-1012.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 -- boot-testing-requested: true kernel-stable-master-bug: 1833934 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:34 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:37 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1833921 Title: linux-raspi2: 5.0.0-1012.12 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Fix Released 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: 1833934 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833928] Re: linux-kvm: 5.0.0-1010.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 -- boot-testing-requested: true kernel-stable-master-bug: 1833934 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:36 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:38 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1833928 Title: linux-kvm: 5.0.0-1010.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Fix Released 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: 1833934 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833922] Re: linux-aws: 5.0.0-1010.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 -- boot-testing-requested: true kernel-stable-master-bug: 1833934 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:35 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:37 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1833922 Title: linux-aws: 5.0.0-1010.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Fix Released 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: 1833934 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833927] Re: linux-gcp: 5.0.0-1010.10 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 -- boot-testing-requested: true kernel-stable-master-bug: 1833934 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:35 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:38 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1833927 Title: linux-gcp: 5.0.0-1010.10 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Fix Released 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: 1833934 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833929] Re: linux-snapdragon: 5.0.0-1016.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 -- boot-testing-requested: true kernel-stable-master-bug: 1833934 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:24 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1833929 Title: linux-snapdragon: 5.0.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Fix Released 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: 1833934 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833929/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833973] Re: linux-gcp: 4.15.0-1036.38 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 backports: bug 1833971 (xenial/linux-gcp) derivatives: bug 1833968 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:10 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:44 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1833973 Title: linux-gcp: 4.15.0-1036.38 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1833971 (xenial/linux-gcp) derivatives: bug 1833968 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833948] Re: linux-gcp: 4.18.0-1015.16 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 backports: bug 1833947 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833952 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:38 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1833948 Title: linux-gcp: 4.18.0-1015.16 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1833947 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833952 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833967] Re: linux-aws: 4.15.0-1043.45 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 backports: bug 1833965 (xenial/linux-aws-hwe) derivatives: bug 1833964 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:09 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:44 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1833967 Title: linux-aws: 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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1833965 (xenial/linux-aws-hwe) derivatives: bug 1833964 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833949] Re: linux-kvm: 4.18.0-1016.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 -- boot-testing-requested: true kernel-stable-master-bug: 1833952 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:38 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1833949 Title: linux-kvm: 4.18.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: Fix Released 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: 1833952 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833936] Re: linux-raspi2: 4.18.0-1018.21 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 -- boot-testing-requested: true kernel-stable-master-bug: 1833952 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:37 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:40 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1833936 Title: linux-raspi2: 4.18.0-1018.21 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: Fix Released 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: 1833952 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833957] Re: linux-raspi2: 4.15.0-1040.43 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 derivatives: bug 1833956 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 15:09 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:43 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1833957 Title: linux-raspi2: 4.15.0-1040.43 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1833956 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833960] Re: linux-snapdragon: 4.15.0-1057.62 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 derivatives: bug 1833958 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 15:09 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:43 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1833960 Title: linux-snapdragon: 4.15.0-1057.62 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1833958 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834528] Re: linux-ibm-gt: 4.15.0-1026.28 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834528 Title: linux-ibm-gt: 4.15.0-1026.28 -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 promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Promote to Proposed phase-changed: Friday, 28. June 2019 11:43 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833976] Re: linux-kvm: 4.15.0-1038.38 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 -- boot-testing-requested: true kernel-stable-master-bug: 1833987 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 16:11 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:45 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1833976 Title: linux-kvm: 4.15.0-1038.38 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833979] Re: linux-oracle: 4.15.0-1017.19 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 backports: bug 1833978 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 - phase: Holding before Security - phase-changed: Thursday, 27. June 2019 15:12 UTC + phase: Ready for Security + phase-changed: Friday, 28. June 2019 14:45 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy variant: debs -- 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/1833979 Title: linux-oracle: 4.15.0-1017.19 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-oracle package in Ubuntu: Fix Released Status in linux-oracle source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1833978 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834528] Re: linux-ibm-gt: 4.15.0-1026.28 -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: 1833987 - phase: Ready for Promote to Proposed - phase-changed: Friday, 28. June 2019 11:43 UTC + phase: Promote to Proposed + phase-changed: Friday, 28. June 2019 15:07 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress variant: debs ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** 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: 1833987 phase: Promote to Proposed phase-changed: Friday, 28. June 2019 15:07 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync 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/1834528 Title: linux-ibm-gt: 4.15.0-1026.28 -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 promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Promote to Proposed phase-changed: Friday, 28. June 2019 15:07 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828868] Re: crashdump fails on HiSilicon D06
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828868 Title: crashdump fails on HiSilicon D06 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) Add "arm_smmu_v3.disable_bypass=1" to the kernel command line sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger (Note to self - the following is needed on our systems w/ Mellanox adapters: ubuntu@d06-3:~$ grep blacklist /etc/default/kdump-tools KDUMP_CMDLINE_APPEND="nr_cpus=1 systemd.unit=kdump-tools-dump.service module_blacklist=mlx5_core") [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] Restricted to SMMUv3 arm64-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833987] Re: linux: 4.15.0-54.58 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833987 Title: linux: 4.15.0-54.58 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: In Progress Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1833986 (xenial/linux-hwe), bug 1834091 (xenial/linux-azure) derivatives: bug 1833954 (pc-kernel), bug 1833955 (pc-lowlatency-kernel), bug 1833957 (linux-raspi2), bug 1833960 (linux-snapdragon), bug 1833962 (linux-oem), bug 1833967 (linux-aws), bug 1833973 (linux-gcp), bug 1833975 (linux-gke-4.15), bug 1833976 (linux-kvm), bug 1833979 (linux-oracle), bug 1833980 (linux-fips), bug 1834528 (linux-ibm-gt) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Security phase-changed: Friday, 28. June 2019 14:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828035] Re: StrongSwan with GCM and large packet sizes produces unstable behavior
A rough outlook is: in ~ less than 2 weeks - it's planned to come with the next proposed kernel. (If everything runs smoothly with the kernel SRU, but it looks good - there is already one Ack.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828035 Title: StrongSwan with GCM and large packet sizes produces unstable behavior Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Confirmed Status in strongswan package in Ubuntu: Incomplete Bug description: StrongSwan with GCM and large packet sizes produces unstable behavior when used in Linux native environment. ---uname output--- Linux ubu01 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:29:11 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = 3906 / M04 (z14), LPAR (dedicated) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- On two separate machines (Linux native), install StrongSwan and on both machines, configure the encryption with aes128gcm8 for IPsec. Then run the following command from one of the machine: ``` $# ping -s 1024 ``` Small packet sizes are working as expected. However, anything large (around 1024 bytes or more) are sometimes returning wrong values, or the packets are getting lost. This problem does not occur for ciphers not involving GCM. Userspace tool common name: StrongSwan The userspace tool has the following bit modes: both Userspace package: StrongSwan Userspace tool obtained from project website: na -Attach ltrace and strace of userspace application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833960] Re: linux-snapdragon: 4.15.0-1057.62 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1833960 Title: linux-snapdragon: 4.15.0-1057.62 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: In Progress Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1833958 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833957] Re: linux-raspi2: 4.15.0-1040.43 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1833957 Title: linux-raspi2: 4.15.0-1040.43 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: In Progress Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1833956 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Security phase-changed: Friday, 28. June 2019 14:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827555] Re: [ALSA] [PATCH] Headset fixup for System76 Gazelle (gaze14)
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827555 Title: [ALSA] [PATCH] Headset fixup for System76 Gazelle (gaze14) Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux-hwe source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Status in linux-hwe source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-hwe source package in Disco: Invalid Bug description: [Impact] * On the System76 Gazelle (gaze14), there is a headset microphone input attached to 0x1a that does not have a jack detect. In order to get it working, the pin configuration needs to be set correctly, and the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is identical to the patch already applied for the System76 Darter Pro (darp5). [Test Case] * With the affected hardware, attempt to use a headset with a microphone input. There will be no microphone input from the headset until applying this patch. [Regression Potential] * Extremely low, it specifically identifies the affected hardware. [Other Info] * I have attached the patch as it will be applied to upstream Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
