[Kernel-packages] [Bug 1800278] Re: kernel linux 4.18 crashes on xiaomi notebook pro
hello, this issue happens in both cases. when i start a clean install from a usb key AND when i try to update it from command lines. the only kernel series that works correctly on my laptop starts to the 4.9.0 (debian) and finish to 4.15.0-36-generic #39. i tried to test the 4.19 using ukuu and the problem is still here. the only option that i has to solve this was to do a fresh install from the usb key ubuntu 18.04 with 4.15 kernel. i´m at your disposal for every informations that you will need. cordially -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800278 Title: kernel linux 4.18 crashes on xiaomi notebook pro Status in linux package in Ubuntu: Confirmed Bug description: hello here´s my hardware profile ; 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1) 00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 3D controller: NVIDIA Corporation Device 1d12 (rev a1) 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a808 as xiaomi notebook pro late 2018 when i tried to use ubuntu 18.10(cosmic cuttlefish) with kernel 4.18 the system freeze and cause high processor activity (100%), high temperature, loud processor activity and the system crashes in one word all the system is static and i have to sutdown the system manually because there is no process respond to anything i can do... i tried every variant of this os and the bug repeat instantly after installation. i have to downgrade to ubuntu 18.04 to solve the probleme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800609] [NEW] dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR
Public bug reported: The dev test on a s390x node (Ubuntu on LPAR) will hang, kernel bug could be found in the syslog [54084.082277] [ cut here ] [54084.082279] kernel BUG at mm/usercopy.c:100! [54084.082294] illegal operation: 0001 ilc:1 [#256] SMP [54084.082297] Modules linked in: vhost_net vhost tap cuse dccp_ipv4 dccp algif_rng salsa20_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common lrw algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg aufs ip6t_MASQUERADE ip6table_nat ip6table_filter ip6_tables xt_comment xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat xt_tcpudp bridge iptable_filter bpfilter openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_conncount nf_nat nf_conntrack 8021q garp mrp stp llc binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) dm_service_time zcommon(PO) znvpair(PO) dm_multipath scsi_dh_rdac scsi_dh_emc spl(O) scsi_dh_alua ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 [54084.082354] sha1_s390 sha_common genwqe_card crc_itu_t chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd ib_iser rdma_cm auth_rpcgss nfs_acl iw_cm lockd grace ib_cm iscsi_tcp libiscsi_tcp sunrpc libiscsi scsi_transport_iscsi ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx4_en mlx4_ib qeth_l2 ib_core ptp pps_core crc32_vx_s390 mlx4_core devlink zfcp scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod [54084.082418] CPU: 3 PID: 217520 Comm: stress-ng-dev Tainted: P DO 4.18.0-11-generic #12-Ubuntu [54084.082420] Hardware name: IBM 2964 N63 400 (LPAR) [54084.082422] Krnl PSW : ed7ed85f 816ddc5c (usercopy_abort+0xb2/0xb8) [54084.082433]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [54084.082436] Krnl GPRS: 0320 0006 0056 0007 [54084.082438]0007 7fe0 00a96d3a [54084.082441]03ff 0006 0006 0002acb4ee00 [54084.082443]00a96d3a 00914430 00386606 00038f087a78 [54084.082449] Krnl Code: 003865fa: c02000390dc4larl %r2,aa8182 00386600: c0e5fff2b418brasl %r14,1dce30 #00386606: a7f40001brc 15,386608 >0038660a: 0707bcr 0,%r7 0038660c: 0707bcr 0,%r7 0038660e: 0707bcr 0,%r7 00386610: c004brcl0,386610 00386616: ebcff0780024stmg %r12,%r15,120(%r15) [54084.082484] Call Trace: [54084.082487] ([<00386606>] usercopy_abort+0xae/0xb8) [54084.082489] [<00386522>] __check_object_size+0x19a/0x1d0 [54084.082492] [<005c69d8>] sg_scsi_ioctl+0x120/0x3d8 [54084.082495] [<005c75b6>] scsi_cmd_ioctl+0x3ce/0x3d8 [54084.082497] [<005c87d0>] bsg_ioctl+0x118/0x250 [54084.082499] [<003a3c9c>] do_vfs_ioctl+0xac/0x650 [54084.082502] [<003a42cc>] ksys_ioctl+0x8c/0xb8 [54084.082504] [<003a432a>] sys_ioctl+0x32/0x40 [54084.082507] [<008f0dc0>] system_call+0xdc/0x2c8 [54084.082508] Last Breaking-Event-Address: [54084.082510] [<00386606>] usercopy_abort+0xae/0xb8 [54084.082512] [54084.082513] ---[ end trace 5009dd6293a23031 ]--- 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 s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 09:05:17 2018 HibernationDevice: RESUME=UUID=46fcf640-03e2-4fd5-b7d6-321d6a11ff8d IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=7ca41340-b34a-4b16-87e9-3ceb5b51767d crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-gene
[Kernel-packages] [Bug 1800278] Re: kernel linux 4.18 crashes on xiaomi notebook pro
bug confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800278 Title: kernel linux 4.18 crashes on xiaomi notebook pro Status in linux package in Ubuntu: Confirmed Bug description: hello here´s my hardware profile ; 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1) 00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 3D controller: NVIDIA Corporation Device 1d12 (rev a1) 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a808 as xiaomi notebook pro late 2018 when i tried to use ubuntu 18.10(cosmic cuttlefish) with kernel 4.18 the system freeze and cause high processor activity (100%), high temperature, loud processor activity and the system crashes in one word all the system is static and i have to sutdown the system manually because there is no process respond to anything i can do... i tried every variant of this os and the bug repeat instantly after installation. i have to downgrade to ubuntu 18.04 to solve the probleme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic
apt-side fix in https://salsa.debian.org/apt- team/apt/commit/a4b0ce5a4f5068f780b3aa94473230b5093a837d ** Changed in: apt (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Committed Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Bug description: On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux- image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800609] 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/1800609 Title: dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: The dev test on a s390x node (Ubuntu on LPAR) will hang, kernel bug could be found in the syslog [54084.082277] [ cut here ] [54084.082279] kernel BUG at mm/usercopy.c:100! [54084.082294] illegal operation: 0001 ilc:1 [#256] SMP [54084.082297] Modules linked in: vhost_net vhost tap cuse dccp_ipv4 dccp algif_rng salsa20_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common lrw algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg aufs ip6t_MASQUERADE ip6table_nat ip6table_filter ip6_tables xt_comment xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat xt_tcpudp bridge iptable_filter bpfilter openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_conncount nf_nat nf_conntrack 8021q garp mrp stp llc binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) dm_service_time zcommon(PO) znvpair(PO) dm_multipath scsi_dh_rdac scsi_dh_emc spl(O) scsi_dh_alua ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 [54084.082354] sha1_s390 sha_common genwqe_card crc_itu_t chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd ib_iser rdma_cm auth_rpcgss nfs_acl iw_cm lockd grace ib_cm iscsi_tcp libiscsi_tcp sunrpc libiscsi scsi_transport_iscsi ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx4_en mlx4_ib qeth_l2 ib_core ptp pps_core crc32_vx_s390 mlx4_core devlink zfcp scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod [54084.082418] CPU: 3 PID: 217520 Comm: stress-ng-dev Tainted: P DO 4.18.0-11-generic #12-Ubuntu [54084.082420] Hardware name: IBM 2964 N63 400 (LPAR) [54084.082422] Krnl PSW : ed7ed85f 816ddc5c (usercopy_abort+0xb2/0xb8) [54084.082433]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [54084.082436] Krnl GPRS: 0320 0006 0056 0007 [54084.082438]0007 7fe0 00a96d3a [54084.082441]03ff 0006 0006 0002acb4ee00 [54084.082443]00a96d3a 00914430 00386606 00038f087a78 [54084.082449] Krnl Code: 003865fa: c02000390dc4 larl %r2,aa8182 00386600: c0e5fff2b418 brasl %r14,1dce30 #00386606: a7f40001 brc 15,386608 >0038660a: 0707 bcr 0,%r7 0038660c: 0707 bcr 0,%r7 0038660e: 0707 bcr 0,%r7 00386610: c004 brcl0,386610 00386616: ebcff0780024 stmg %r12,%r15,120(%r15) [54084.082484] Call Trace: [54084.082487] ([<00386606>] usercopy_abort+0xae/0xb8) [54084.082489] [<00386522>] __check_object_size+0x19a/0x1d0 [54084.082492] [<005c69d8>] sg_scsi_ioctl+0x120/0x3d8 [54084.082495] [<005c75b6>] scsi_cmd_ioctl+0x3ce/0x3d8 [54084.082497] [<005c87d0>] bsg_ioctl+0x118/0x250 [54084.082499] [<003a3c9c>] do_vfs_ioctl+0xac/0x650 [54084.082502] [<003a42cc>] ksys_ioctl+0x8c/0xb8 [54084.082504] [<003a432a>] sys_ioctl+0x32/0x40 [54084.082507] [<008f0dc0>] system_call+0xdc/0x2c8 [54084.082508] Last Breaking-Event-Address: [54084.082510] [<00386606>] usercopy_abort+0xae/0xb8 [54084.082512] [54084.082513] ---[ end trace 5009dd6293a23031 ]--- 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 s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw',
[Kernel-packages] [Bug 1769937] Re: Error reported when creating ZFS pool with "-t" option, despite successful pool creation
Tested with linux 4.4.0-139-generic #165 and zfsutils 0.6.5.6-0ubuntu26
- marking as verified for xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1769937
Title:
Error reported when creating ZFS pool with "-t" option, despite
successful pool creation
Status in linux package in Ubuntu:
Fix Released
Status in zfs-linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in zfs-linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Released
Status in zfs-linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in zfs-linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification, Xenial, Bionic ==
Bug:
When creating a pool with the -t option on Ubuntu 18.04 LTS, it will
report an error and return a non-zero exit code, but the pool appears
to be successfully created.
For example:
# zpool create -O canmount=off -O mountpoint=none -R /mnt/rpool-25582 -t
rpool-25582 rpool /dev/mapper/loop2p1
cannot create 'rpool': no such pool or dataset
# zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH
ALTROOT
rpool-25582 69.5G 92.5K 69.5G - 0% 0% 1.00x ONLINE
/mnt/rpool-25582
# zpool export rpool-25582
# zpool import rpool
# zpool list
NAMESIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT
rpool 69.5G 134K 69.5G - 0% 0% 1.00x ONLINE -
I opened an upstream bug against ZFS on Linux, here:
https://github.com/zfsonlinux/zfs/issues/7502
And it has been recently fixed, here:
https://github.com/zfsonlinux/zfs/pull/7509
Can this upstream fix be pulled into the Ubuntu 18.04 LTS packages?
Thanks,
Prakash
== Fix ==
Upstream zfs commit 4ceb8dd6fdfd ("Fix 'zpool create -t '")
== Test ==
Without the fix, creating a pool with -t will show an error message
such as:
"cannot create 'rpool': no such pool or dataset" and will return an
error number even though it successfully created the pool. With the
fix, the error is not shown and it exits with 0.
E.g.
pool create -O canmount=off -O mountpoint=none -R /mnt/rpool-25582 -t
rpool-25582 rpool /dev/mapper/loop2p1
cannot create 'rpool': no such pool or dataset
== Regression Potential ==
Small. This is an upstream fix that is know to fix the error. There
are no known subsequent changes to the fix hence suggesting it is a
good fix. The change is very limited and testing shows it does not
break any of the kernel team's ZFS regression testing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769937/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799399] Re: linux: 3.13.0-162.212 -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) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799399 Title: linux: 3.13.0-162.212 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Uploaded reason: promote-to-proposed: Review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799452] Re: linux-gcp: 4.18.0-1003.4 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799445 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-beta: Snap not in beta channel - snap-release-to-edge: Snap not in edge channel + snap-release-to-beta: snap not in beta channel -- snapcraft release gcp-kernel beta + snap-release-to-edge: snap not in edge channel -- snapcraft release gcp-kernel edge verification-testing: Testing in progress -- 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/1799452 Title: linux-gcp: 4.18.0-1003.4 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799445 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff snap-release-to-beta: snap not in beta channel -- snapcraft release gcp-kernel beta snap-release-to-edge: snap not in edge channel -- snapcraft release gcp-kernel edge verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799399] Re: linux: 3.13.0-162.212 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Uploaded reason: - promote-to-proposed: Ready for review + promote-to-proposed: Review 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/1799399 Title: linux: 3.13.0-162.212 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Uploaded reason: promote-to-proposed: Review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798674] Re: linux-azure: 4.15.0-1028.29~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (Confirmed) - snap-release-to-candidate: Snap not in candidate channel + snap-release-to-candidate: snap not in candidate channel -- snapcraft release azure-kernel + candidate -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1798674 Title: linux-azure: 4.15.0-1028.29~16.04.1 -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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-candidate: snap not in candidate channel -- snapcraft release azure-kernel candidate To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1798674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799399] Re: linux: 3.13.0-162.212 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed 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/1799399 Title: linux: 3.13.0-162.212 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Uploaded reason: promote-to-proposed: Review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799411] Re: linux: 4.15.0-39.42 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1799413 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) kernel-stable-phase-changed:Tuesday, 23. October 2018 16:06 UTC kernel-stable-phase:Uploaded -- swm properties -- backports: null boot-testing-requested: true bugs-spammed: true derivatives: null phase: Uploaded reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-candidate: Snap not in 18/candidate channel + snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release + pc-kernel 18/candidate verification-testing: Testing 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/1799411 Title: linux: 4.15.0-39.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1799413 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) kernel-stable-phase-changed:Tuesday, 23. October 2018 16:06 UTC kernel-stable-phase:Uploaded -- swm properties -- backports: null boot-testing-requested: true bugs-spammed: true derivatives: null phase: Uploaded reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release pc-kernel 18/candidate verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799416] Re: linux-gcp: 4.15.0-1024.25 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-candidate: Snap not in 18/candidate channel + snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release + gcp-kernel 18/candidate verification-testing: Testing in progress -- 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/1799416 Title: linux-gcp: 4.15.0-1024.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release gcp-kernel 18/candidate verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799414] Re: linux-aws: 4.15.0-1026.26 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-candidate: Snap not in 18/candidate channel + snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release + aws-kernel 18/candidate verification-testing: Testing 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/1799414 Title: linux-aws: 4.15.0-1026.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release aws-kernel 18/candidate verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798658] Re: linux-azure: 4.15.0-1028.29 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1028.29 upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (Confirmed) - snap-release-to-candidate: Snap not in 18/candidate channel + snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release + azure-kernel 18/candidate -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1798658 Title: linux-azure: 4.15.0-1028.29 -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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Fix Released Bug description: This bug is for tracking the 4.15.0-1028.29 upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release azure-kernel 18/candidate To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1798658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799405] Re: linux-aws: 4.4.0-1071.81 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-beta: Snap not in beta channel - snap-release-to-edge: Snap not in edge channel + snap-release-to-beta: snap not in beta channel -- snapcraft release aws-kernel beta + snap-release-to-edge: snap not in edge channel -- snapcraft release aws-kernel edge verification-testing: Testing 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/1799405 Title: linux-aws: 4.4.0-1071.81 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff snap-release-to-beta: snap not in beta channel -- snapcraft release aws-kernel beta snap-release-to-edge: snap not in edge channel -- snapcraft release aws-kernel edge verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800306] Re: Computer hangs completely passed 15~25 days of usage
We have this problem for a long, long time now. I supposed a hardware fault but changed motherboard, graphics card, memtest my ram, etc. I send this bug report because I think that is a kernel/software problem. This must take in caution but I believe that I had this problem since 14.04. By the way, I installed a clean 16.04 release some months ago. Maybe an important point is that some days before system crash, I start to see problems with window manager, maybe compiz related. Windows isn't refreshing accordingly. ok. We will test v4.19 and I will try to record the windows problem and attach here. Regards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800306 Title: Computer hangs completely passed 15~25 days of usage Status in linux package in Ubuntu: Incomplete Bug description: Computer hangs every 3 weeks or so. It seems a graphics card problem but I changed by a new one, tried nvidia driver with the same behaviour too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-138-generic 4.4.0-138.164 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 27 16:20:18 2018 HibernationDevice: RESUME=/dev/mapper/LINUX--vg-swap_1 InstallationDate: Installed on 2017-11-02 (359 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: MSI MS-7885 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-138-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-138-generic N/A linux-backports-modules-4.4.0-138-generic N/A linux-firmware 1.157.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P.50 dmi.board.asset.tag: Default string dmi.board.name: X99A RAIDER (MS-7885) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP.50:bd07/19/2016:svnMSI:pnMS-7885:pvr5.0:rvnMSI:rnX99ARAIDER(MS-7885):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7885 dmi.product.version: 5.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799400] Re: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 phase: Uploaded reason: - promote-to-proposed: Ready for review + promote-to-proposed: Review in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1799400 Title: linux-lts-trusty: 3.13.0-162.212~precise1 -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 prepare-package-signed 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 phase: Uploaded reason: promote-to-proposed: Review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800609] Re: dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800609 Title: dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: The dev test on a s390x node (Ubuntu on LPAR) will hang, kernel bug could be found in the syslog [54084.082277] [ cut here ] [54084.082279] kernel BUG at mm/usercopy.c:100! [54084.082294] illegal operation: 0001 ilc:1 [#256] SMP [54084.082297] Modules linked in: vhost_net vhost tap cuse dccp_ipv4 dccp algif_rng salsa20_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common lrw algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg aufs ip6t_MASQUERADE ip6table_nat ip6table_filter ip6_tables xt_comment xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat xt_tcpudp bridge iptable_filter bpfilter openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_conncount nf_nat nf_conntrack 8021q garp mrp stp llc binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) dm_service_time zcommon(PO) znvpair(PO) dm_multipath scsi_dh_rdac scsi_dh_emc spl(O) scsi_dh_alua ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 [54084.082354] sha1_s390 sha_common genwqe_card crc_itu_t chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd ib_iser rdma_cm auth_rpcgss nfs_acl iw_cm lockd grace ib_cm iscsi_tcp libiscsi_tcp sunrpc libiscsi scsi_transport_iscsi ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx4_en mlx4_ib qeth_l2 ib_core ptp pps_core crc32_vx_s390 mlx4_core devlink zfcp scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod [54084.082418] CPU: 3 PID: 217520 Comm: stress-ng-dev Tainted: P DO 4.18.0-11-generic #12-Ubuntu [54084.082420] Hardware name: IBM 2964 N63 400 (LPAR) [54084.082422] Krnl PSW : ed7ed85f 816ddc5c (usercopy_abort+0xb2/0xb8) [54084.082433]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [54084.082436] Krnl GPRS: 0320 0006 0056 0007 [54084.082438]0007 7fe0 00a96d3a [54084.082441]03ff 0006 0006 0002acb4ee00 [54084.082443]00a96d3a 00914430 00386606 00038f087a78 [54084.082449] Krnl Code: 003865fa: c02000390dc4 larl %r2,aa8182 00386600: c0e5fff2b418 brasl %r14,1dce30 #00386606: a7f40001 brc 15,386608 >0038660a: 0707 bcr 0,%r7 0038660c: 0707 bcr 0,%r7 0038660e: 0707 bcr 0,%r7 00386610: c004 brcl0,386610 00386616: ebcff0780024 stmg %r12,%r15,120(%r15) [54084.082484] Call Trace: [54084.082487] ([<00386606>] usercopy_abort+0xae/0xb8) [54084.082489] [<00386522>] __check_object_size+0x19a/0x1d0 [54084.082492] [<005c69d8>] sg_scsi_ioctl+0x120/0x3d8 [54084.082495] [<005c75b6>] scsi_cmd_ioctl+0x3ce/0x3d8 [54084.082497] [<005c87d0>] bsg_ioctl+0x118/0x250 [54084.082499] [<003a3c9c>] do_vfs_ioctl+0xac/0x650 [54084.082502] [<003a42cc>] ksys_ioctl+0x8c/0xb8 [54084.082504] [<003a432a>] sys_ioctl+0x32/0x40 [54084.082507] [<008f0dc0>] system_call+0xdc/0x2c8 [54084.082508] Last Breaking-Event-Address: [54084.082510] [<00386606>] usercopy_abort+0xae/0xb8 [54084.082512] [54084.082513] ---[ end trace 5009dd6293a23031 ]--- ProblemT
[Kernel-packages] [Bug 1800609] Re: dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR
Occurs when performing the FIBMAP ioctl on /dev/bsg/rport-1:0-0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800609 Title: dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: The dev test on a s390x node (Ubuntu on LPAR) will hang, kernel bug could be found in the syslog [54084.082277] [ cut here ] [54084.082279] kernel BUG at mm/usercopy.c:100! [54084.082294] illegal operation: 0001 ilc:1 [#256] SMP [54084.082297] Modules linked in: vhost_net vhost tap cuse dccp_ipv4 dccp algif_rng salsa20_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common lrw algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg aufs ip6t_MASQUERADE ip6table_nat ip6table_filter ip6_tables xt_comment xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat xt_tcpudp bridge iptable_filter bpfilter openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_conncount nf_nat nf_conntrack 8021q garp mrp stp llc binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) dm_service_time zcommon(PO) znvpair(PO) dm_multipath scsi_dh_rdac scsi_dh_emc spl(O) scsi_dh_alua ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 [54084.082354] sha1_s390 sha_common genwqe_card crc_itu_t chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd ib_iser rdma_cm auth_rpcgss nfs_acl iw_cm lockd grace ib_cm iscsi_tcp libiscsi_tcp sunrpc libiscsi scsi_transport_iscsi ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx4_en mlx4_ib qeth_l2 ib_core ptp pps_core crc32_vx_s390 mlx4_core devlink zfcp scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod [54084.082418] CPU: 3 PID: 217520 Comm: stress-ng-dev Tainted: P DO 4.18.0-11-generic #12-Ubuntu [54084.082420] Hardware name: IBM 2964 N63 400 (LPAR) [54084.082422] Krnl PSW : ed7ed85f 816ddc5c (usercopy_abort+0xb2/0xb8) [54084.082433]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [54084.082436] Krnl GPRS: 0320 0006 0056 0007 [54084.082438]0007 7fe0 00a96d3a [54084.082441]03ff 0006 0006 0002acb4ee00 [54084.082443]00a96d3a 00914430 00386606 00038f087a78 [54084.082449] Krnl Code: 003865fa: c02000390dc4 larl %r2,aa8182 00386600: c0e5fff2b418 brasl %r14,1dce30 #00386606: a7f40001 brc 15,386608 >0038660a: 0707 bcr 0,%r7 0038660c: 0707 bcr 0,%r7 0038660e: 0707 bcr 0,%r7 00386610: c004 brcl0,386610 00386616: ebcff0780024 stmg %r12,%r15,120(%r15) [54084.082484] Call Trace: [54084.082487] ([<00386606>] usercopy_abort+0xae/0xb8) [54084.082489] [<00386522>] __check_object_size+0x19a/0x1d0 [54084.082492] [<005c69d8>] sg_scsi_ioctl+0x120/0x3d8 [54084.082495] [<005c75b6>] scsi_cmd_ioctl+0x3ce/0x3d8 [54084.082497] [<005c87d0>] bsg_ioctl+0x118/0x250 [54084.082499] [<003a3c9c>] do_vfs_ioctl+0xac/0x650 [54084.082502] [<003a42cc>] ksys_ioctl+0x8c/0xb8 [54084.082504] [<003a432a>] sys_ioctl+0x32/0x40 [54084.082507] [<008f0dc0>] system_call+0xdc/0x2c8 [54084.082508] Last Breaking-Event-Address: [54084.082510] [<00386606>] usercopy_abort+0xae/0xb8 [54084.082512] [54084.082513] ---[ end trace 5009dd6293a23031 ]--- 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 s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with ex
[Kernel-packages] [Bug 1799237] Re: mprotect fails on ext4 with dax
I have tested the following upstream kernels and mprotect works fine on all of
them:
4.15.17-041517-generic
4.15.18-041518-generic
4.19.0-041900-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Confirmed
Status in pmdk package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799399] Re: linux: 3.13.0-162.212 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Uploaded reason: - promote-to-proposed: Review in progress + promote-to-proposed: Packages copied but not yet published to -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/1799399 Title: linux: 3.13.0-162.212 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Uploaded reason: promote-to-proposed: Packages copied but not yet published to -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777010] Re: ip token set, results in: Invalid argument
Just tried "ip token set" in 18.10 (Cosmic Cuttlefish), fails with the same error: RTNETLINK answers: Invalid argument iproute2 Version: 4.18.0-1ubuntu2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1777010 Title: ip token set, results in: Invalid argument Status in iproute2 package in Ubuntu: Confirmed Bug description: Hi, I can't set any ipv6 token with ip command. It seems that it has a bug. Also it is not possible to set it with netplan (see bug #1737976) ~# ip token list token :: dev enp1s0 token :: dev enp2s0 token :: dev ovpn0 token :: dev br0 ~# ip token set ::2a:2a:2a:2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::beef dev br0 RTNETLINK answers: Invalid argument It seems, that this Bug is really old?! https://bbs.archlinux.org/viewtopic.php?id=202757 This is really fatal, because I cant set a static ip. My prefix get mixed from my provider every x days. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 15 01:26:04 2018 InstallationDate: Installed on 2018-06-12 (2 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1777010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799399] Re: linux: 3.13.0-162.212 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Uploaded reason: - promote-to-proposed: Packages copied but not yet published to -proposed + promote-to-proposed: Packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799399 Title: linux: 3.13.0-162.212 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Uploaded reason: promote-to-proposed: Packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800609] Re: dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1800609 Title: dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Bug description: The dev test on a s390x node (Ubuntu on LPAR) will hang, kernel bug could be found in the syslog [54084.082277] [ cut here ] [54084.082279] kernel BUG at mm/usercopy.c:100! [54084.082294] illegal operation: 0001 ilc:1 [#256] SMP [54084.082297] Modules linked in: vhost_net vhost tap cuse dccp_ipv4 dccp algif_rng salsa20_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common lrw algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg aufs ip6t_MASQUERADE ip6table_nat ip6table_filter ip6_tables xt_comment xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat xt_tcpudp bridge iptable_filter bpfilter openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_conncount nf_nat nf_conntrack 8021q garp mrp stp llc binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) dm_service_time zcommon(PO) znvpair(PO) dm_multipath scsi_dh_rdac scsi_dh_emc spl(O) scsi_dh_alua ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 [54084.082354] sha1_s390 sha_common genwqe_card crc_itu_t chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd ib_iser rdma_cm auth_rpcgss nfs_acl iw_cm lockd grace ib_cm iscsi_tcp libiscsi_tcp sunrpc libiscsi scsi_transport_iscsi ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx4_en mlx4_ib qeth_l2 ib_core ptp pps_core crc32_vx_s390 mlx4_core devlink zfcp scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod [54084.082418] CPU: 3 PID: 217520 Comm: stress-ng-dev Tainted: P DO 4.18.0-11-generic #12-Ubuntu [54084.082420] Hardware name: IBM 2964 N63 400 (LPAR) [54084.082422] Krnl PSW : ed7ed85f 816ddc5c (usercopy_abort+0xb2/0xb8) [54084.082433]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [54084.082436] Krnl GPRS: 0320 0006 0056 0007 [54084.082438]0007 7fe0 00a96d3a [54084.082441]03ff 0006 0006 0002acb4ee00 [54084.082443]00a96d3a 00914430 00386606 00038f087a78 [54084.082449] Krnl Code: 003865fa: c02000390dc4 larl %r2,aa8182 00386600: c0e5fff2b418 brasl %r14,1dce30 #00386606: a7f40001 brc 15,386608 >0038660a: 0707 bcr 0,%r7 0038660c: 0707 bcr 0,%r7 0038660e: 0707 bcr 0,%r7 00386610: c004 brcl0,386610 00386616: ebcff0780024 stmg %r12,%r15,120(%r15) [54084.082484] Call Trace: [54084.082487] ([<00386606>] usercopy_abort+0xae/0xb8) [54084.082489] [<00386522>] __check_object_size+0x19a/0x1d0 [54084.082492] [<005c69d8>] sg_scsi_ioctl+0x120/0x3d8 [54084.082495] [<005c75b6>] scsi_cmd_ioctl+0x3ce/0x3d8 [54084.082497] [<005c87d0>] bsg_ioctl+0x118/0x250 [54084.082499] [<003a3c9c>] do_vfs_ioctl+0xac/0x650 [54084.082502] [<003a42cc>] ksys_ioctl+0x8c/0xb8 [54084.082504] [<003a432a>] sys_ioctl+0x32/0x40 [54084.082507] [<008f0dc0>] system_call+0xdc/0x2c8 [54084.082508] Last Breaking-Event-Address: [54084.082510] [<00386606>] usercopy_abort+0xae/0xb8 [54084.082512] [54084.082513] ---[ end trace 5009dd6293a23031 ]--- 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 s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13
[Kernel-packages] [Bug 1799400] Re: linux-lts-trusty: 3.13.0-162.212~precise1 -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) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1799400 Title: linux-lts-trusty: 3.13.0-162.212~precise1 -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 prepare-package-signed 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 phase: Uploaded reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792501] Comment bridged from LTC Bugzilla
--- Comment From sathe...@in.ibm.com 2018-10-30 06:54 EDT---
Tested with the proposed kernel (4.15.0-39-generic) and found the issue fixed,
fix can be included in official release and bug can be closed.
Env: host kernel 4.15.0-39-generic
guest kernel 4.15.0-39-generic
Regards,
-Satheesh.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792501
Title:
[Ubuntu18.04][Power9][DD2.2]package installation segfaults inside
debian chroot env in P9 KVM guest with HTM enabled (kvm)
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
== SRU Justification ==
IBM is requesting this commit in Bionic. It fixes a regression
introduced by upstream commit 4bb3c7a020.
Without this patch, package installation segfaults inside debian chroot
env in P9 KVM guest with HTM enabled.
The fix has already landed in Cosmic master-next.
== Fix ==
f14040bca892 ("KVM: PPC: Book3S HV: Fix guest r11 corruption with POWER9 TM
workarounds")
== Regression Potential ==
Low. This commit fixes an existing regrssion and is specific to powerpc. It
has been cc'd to
upstream stable, so has had additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Satheesh Rajendran - 2018-09-11
04:10:09 ==
---Problem Description---
package installation segfaults inside debian chroot env in P9 KVM guest with
HTM enabled
---Additional Hardware Info---
FW with tm-suspend-mode enabled
#cd /sys/firmware/devicetree/base/ibm,opal/fw-features/
#ls -1 tm-suspend-mode
enabled
name
phandle
qemu-kvm 1:2.11+dfsg-1ubuntu7.4
Machine Type = Power9 DD2.2
---Steps to Reproduce---
1. Boot a P9 KVM guest Ubuntu 18.04 (with cap-htm=on, bydefault it is on)
tried with upstream kernel aswell(same results)
create tap device in host
# tunctl -t tap1 -u `whoami`;brctl addif virbr0 tap1;ifconfig tap1 up
#qemu-system-ppc64 -enable-kvm -M pseries -m 8192 -smp 4 -drive
file=/home/sath/ubuntu-18.04-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0
-device virtio-scsi-pci,id=drive-scsi0 -device scsi-hd,drive=drive-scsi0
-serial mon:stdio -enable-kvm -vga none -nographic -kernel
/home/sath/vmlinux_4.19 -append root=/dev/sda2 rw console=tty0
console=ttyS0,115200 init=/sbin/init initcall_debug -netdev
tap,id=mynet1,ifname=tap1,script=no,downscript=no -device
virtio-net,netdev=mynet1,mac=52:55:00:d1:55:42
run dhclient inside guest.
2. # mkdir -p stretch
# debootstrap stretch /stretch http://httpredir.debian.org/debian
# chroot /stretch
/# apt-get update && apt-get install -y make gcc ruby python
...
[ 32.029474] random: crng init done
[ 32.029477] random: 7 urandom warning(s) missed due to ratelimiting
[ 500.300835] dpkg-deb[8704]: segfault (11) at c00037fa nip
7fffac2d098c lr 7fffac2d08c4 code 1 in libc-2.24.so[7fffac17+19]
[ 500.300863] dpkg-deb[8704]: code: 4828 eb090010 2eb8 4096006c
419e0074 85270004 394a0001 794a0020
[ 500.300881] dpkg-deb[8704]: code: 71280001 408200a0 1d2a0018 7d2b4a14
2ea8 40960010 e9090008
---uname output---
4.15.0-34,4.19.0-rc3
---Debugger---
A debugger is not configured
Contact Information = sathe...@in.ibm.com
Userspace tool common name:
KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27,
Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version
2.24
Userspace rpm:
KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27,
Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version
2.24
The userspace tool has the following bit modes: both
Userspace tool obtained from project website: na
*Additional Instructions for sathe...@in.ibm.com:
-Post a private note with access information to the machine that the bug is
occuring on.
-Attach ltrace and strace of userspace application.
So latest update taken from https://github.ibm.com/powercloud/icp-
ppc64le/issues/470
was able to recreate segfault using TM test cases
/linux/tools/testing/selftests/powerpc/tm
# ./tm-vmxcopy
test: tm_vmxcopy
tags: git_version:v4.19-rc3-0-g11da3a7f84f1-dirty
!! child died by signal 11
failure: tm_vmxcopy
this particular test on being run gets a signal 11
[267132.434651] tm-vmxcopy[641]: unhandled signal 11 at 0001 nip
000104ba122c lr 000104ba11e4 code 30001
[267253.708795] tm-vmxcopy[7861]: unhandled signal 11 at 0001 nip
00012a31122c lr 00012a3111e4 code 30001
[267385.064533] tm-v
[Kernel-packages] [Bug 1792501] testcase
--- Comment on attachment From sathe...@in.ibm.com 2018-10-30 06:58
EDT---
alternate testcase
1. boot the guest as mentioned in bug description
2. copy the testcase inside guest
3. compile and run the testcase
cc -g -ggdb -O3 -static -I. -m64 ./htm_demo.c -lpthread
#./a.out
Starting 2 worker threads, 1000 loops
Thread 2 crossed zero
PASS -- shared values correct
Done! Bye!
Test passed.
Regards,
-Satheesh
** Attachment added: "testcase"
https://bugs.launchpad.net/bugs/1792501/+attachment/5207141/+files/htm_demo.c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792501
Title:
[Ubuntu18.04][Power9][DD2.2]package installation segfaults inside
debian chroot env in P9 KVM guest with HTM enabled (kvm)
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
== SRU Justification ==
IBM is requesting this commit in Bionic. It fixes a regression
introduced by upstream commit 4bb3c7a020.
Without this patch, package installation segfaults inside debian chroot
env in P9 KVM guest with HTM enabled.
The fix has already landed in Cosmic master-next.
== Fix ==
f14040bca892 ("KVM: PPC: Book3S HV: Fix guest r11 corruption with POWER9 TM
workarounds")
== Regression Potential ==
Low. This commit fixes an existing regrssion and is specific to powerpc. It
has been cc'd to
upstream stable, so has had additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Satheesh Rajendran - 2018-09-11
04:10:09 ==
---Problem Description---
package installation segfaults inside debian chroot env in P9 KVM guest with
HTM enabled
---Additional Hardware Info---
FW with tm-suspend-mode enabled
#cd /sys/firmware/devicetree/base/ibm,opal/fw-features/
#ls -1 tm-suspend-mode
enabled
name
phandle
qemu-kvm 1:2.11+dfsg-1ubuntu7.4
Machine Type = Power9 DD2.2
---Steps to Reproduce---
1. Boot a P9 KVM guest Ubuntu 18.04 (with cap-htm=on, bydefault it is on)
tried with upstream kernel aswell(same results)
create tap device in host
# tunctl -t tap1 -u `whoami`;brctl addif virbr0 tap1;ifconfig tap1 up
#qemu-system-ppc64 -enable-kvm -M pseries -m 8192 -smp 4 -drive
file=/home/sath/ubuntu-18.04-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0
-device virtio-scsi-pci,id=drive-scsi0 -device scsi-hd,drive=drive-scsi0
-serial mon:stdio -enable-kvm -vga none -nographic -kernel
/home/sath/vmlinux_4.19 -append root=/dev/sda2 rw console=tty0
console=ttyS0,115200 init=/sbin/init initcall_debug -netdev
tap,id=mynet1,ifname=tap1,script=no,downscript=no -device
virtio-net,netdev=mynet1,mac=52:55:00:d1:55:42
run dhclient inside guest.
2. # mkdir -p stretch
# debootstrap stretch /stretch http://httpredir.debian.org/debian
# chroot /stretch
/# apt-get update && apt-get install -y make gcc ruby python
...
[ 32.029474] random: crng init done
[ 32.029477] random: 7 urandom warning(s) missed due to ratelimiting
[ 500.300835] dpkg-deb[8704]: segfault (11) at c00037fa nip
7fffac2d098c lr 7fffac2d08c4 code 1 in libc-2.24.so[7fffac17+19]
[ 500.300863] dpkg-deb[8704]: code: 4828 eb090010 2eb8 4096006c
419e0074 85270004 394a0001 794a0020
[ 500.300881] dpkg-deb[8704]: code: 71280001 408200a0 1d2a0018 7d2b4a14
2ea8 40960010 e9090008
---uname output---
4.15.0-34,4.19.0-rc3
---Debugger---
A debugger is not configured
Contact Information = sathe...@in.ibm.com
Userspace tool common name:
KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27,
Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version
2.24
Userspace rpm:
KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27,
Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version
2.24
The userspace tool has the following bit modes: both
Userspace tool obtained from project website: na
*Additional Instructions for sathe...@in.ibm.com:
-Post a private note with access information to the machine that the bug is
occuring on.
-Attach ltrace and strace of userspace application.
So latest update taken from https://github.ibm.com/powercloud/icp-
ppc64le/issues/470
was able to recreate segfault using TM test cases
/linux/tools/testing/selftests/powerpc/tm
# ./tm-vmxcopy
test: tm_vmxcopy
tags: git_version:v4.19-rc3-0-g11da3a7f84f1-dirty
!! child died by signal 11
failure: tm_vmxcopy
this particular test on being run gets a signal 11
[267132.434651] tm-vmxcopy[641]: unhandled
[Kernel-packages] [Bug 1800509] Re: unable to handle kernel NULL pointer dereference at 0000000000000007
We don't know what triggered this bug. While the server was operational and hosting 5 virtual machines, we saw abnormal behavior to one of them and after a while the whole host became unresponsive due to high loads. We were unable to force shutdown guest vms due to device or resource busy error. We were only able to find a few more info from the quest vm that was first affected. Please find bellow. Oct 29 13:53:15 ws091 kernel: [201133.016407] INFO: rcu_sched detected stalls on CPUs/tasks: Oct 29 13:53:15 ws091 kernel: [201133.050472] 30-...0: (1 GPs behind) idle=83e/140/0 softirq=294262/294263 fqs=4910 Oct 29 13:53:15 ws091 kernel: [201133.053751] (detected by 7, t=15011 jiffies, g=3090541, c=3090540, q=8389) Oct 29 13:53:15 ws091 kernel: [201133.056359] Sending NMI from CPU 7 to CPUs 30: Oct 29 13:53:15 ws091 kernel: [201142.979012] rcu_sched kthread starved for 6707 jiffies! g3090541 c3090540 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=45 Oct 29 13:53:15 ws091 kernel: [201142.983752] rcu_sched I0 8 2 0x8000 Oct 29 13:53:15 ws091 kernel: [201142.983755] Call Trace: Oct 29 13:53:15 ws091 kernel: [201142.983763] __schedule+0x3d6/0x8b0 Oct 29 13:53:15 ws091 kernel: [201142.983765] schedule+0x36/0x80 Oct 29 13:53:15 ws091 kernel: [201142.983767] schedule_timeout+0x162/0x370 Oct 29 13:53:15 ws091 kernel: [201142.983770] ? __next_timer_interrupt+0xe0/0xe0 Oct 29 13:53:15 ws091 kernel: [201142.983774] rcu_gp_kthread+0x5b4/0x960 Oct 29 13:53:15 ws091 kernel: [201142.983779] kthread+0x105/0x140 Oct 29 13:53:15 ws091 kernel: [201142.983780] ? rcu_barrier_sched+0x10/0x10 Oct 29 13:53:15 ws091 kernel: [201142.983781] ? kthread_destroy_worker+0x50/0x50 Oct 29 13:53:15 ws091 kernel: [201142.983784] ret_from_fork+0x35/0x40 Oct 29 13:55:57 ws091 kernel: [201305.267245] INFO: task jbd2/vdc1-8:1412 blocked for more than 120 seconds. Oct 29 13:55:57 ws091 kernel: [201305.340061] Not tainted 4.15.0-38-generic #41~16.04.1-Ubuntu Oct 29 13:55:57 ws091 kernel: [201305.341300] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 29 13:55:57 ws091 kernel: [201305.342813] jbd2/vdc1-8 D0 1412 2 0x8000 Oct 29 13:55:57 ws091 kernel: [201305.342817] Call Trace: Oct 29 13:55:57 ws091 kernel: [201305.342831] __schedule+0x3d6/0x8b0 Oct 29 13:55:57 ws091 kernel: [201305.342834] schedule+0x36/0x80 Oct 29 13:55:57 ws091 kernel: [201305.342840] jbd2_journal_commit_transaction+0x241/0x1760 Oct 29 13:55:57 ws091 kernel: [201305.342846] ? __switch_to_asm+0x34/0x70 Oct 29 13:55:57 ws091 kernel: [201305.342848] ? __switch_to_asm+0x40/0x70 Oct 29 13:55:57 ws091 kernel: [201305.342849] ? __switch_to_asm+0x34/0x70 Oct 29 13:55:57 ws091 kernel: [201305.342851] ? __switch_to_asm+0x40/0x70 Oct 29 13:55:57 ws091 kernel: [201305.342853] ? __switch_to_asm+0x34/0x70 Oct 29 13:55:57 ws091 kernel: [201305.342855] ? __switch_to_asm+0x40/0x70 Oct 29 13:55:57 ws091 kernel: [201305.342857] ? __switch_to_asm+0x40/0x70 Oct 29 13:55:57 ws091 kernel: [201305.342859] ? __switch_to_asm+0x34/0x70 Oct 29 13:55:57 ws091 kernel: [201305.342860] ? __switch_to_asm+0x34/0x70 Oct 29 13:55:57 ws091 kernel: [201305.342862] ? __switch_to_asm+0x40/0x70 Oct 29 13:55:57 ws091 kernel: [201305.342873] ? __switch_to_asm+0x40/0x70 Oct 29 13:55:57 ws091 kernel: [201305.342879] ? wait_woken+0x80/0x80 Oct 29 13:55:57 ws091 kernel: [201305.342882] ? __switch_to_asm+0x40/0x70 Oct 29 13:55:57 ws091 kernel: [201305.342890] ? lock_timer_base+0x75/0xa0 Oct 29 13:55:57 ws091 kernel: [201305.342895] kjournald2+0xc8/0x250 Oct 29 13:55:57 ws091 kernel: [201305.342897] ? kjournald2+0xc8/0x250 Oct 29 13:55:57 ws091 kernel: [201305.342899] ? wait_woken+0x80/0x80 Oct 29 13:55:57 ws091 kernel: [201305.342905] kthread+0x105/0x140 Oct 29 13:55:57 ws091 kernel: [201305.342907] ? commit_timeout+0x20/0x20 Oct 29 13:55:57 ws091 kernel: [201305.342909] ? kthread_destroy_worker+0x50/0x50 Oct 29 13:55:57 ws091 kernel: [201305.342911] ret_from_fork+0x35/0x40 Oct 29 13:55:57 ws091 kernel: [201305.343058] INFO: task kworker/u112:1:45667 blocked for more than 120 seconds. Oct 29 13:55:57 ws091 kernel: [201305.344520] Not tainted 4.15.0-38-generic #41~16.04.1-Ubuntu Oct 29 13:55:58 ws091 kernel: [201305.362862] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 29 13:55:58 ws091 kernel: [201305.376988] kworker/u112:1 D0 45667 2 0x8000 Oct 29 13:55:58 ws091 kernel: [201305.377000] Workqueue: writeback wb_workfn (flush-252:32) Oct 29 13:55:58 ws091 kernel: [201305.377002] Call Trace: Oct 29 13:55:58 ws091 kernel: [201305.377007] __schedule+0x3d6/0x8b0 Oct 29 13:55:58 ws091 kernel: [201305.377016] ? blk_mq_sched_insert_requests+0x7a/0x80 Oct 29 13:55:58 ws091 kernel: [201305.377017] schedule+0x36/0x80 Oct 29 13:55:58 ws091 kernel: [201305.377026] wait_transaction_locked+0x8a/0xd0 Oct 29 13:55:58 ws091 kernel: [201305.377029] ?
[Kernel-packages] [Bug 1800639] [NEW] [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
You have been subscribed to a public bug: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-172698 severity-high targetmilestone-inin1810 -- [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport https://bugs.launchpad.net/bugs/1800639 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 1800639] [NEW] [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
Public bug reported: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! ** Affects: ubuntu-z-systems Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-172698 severity-high targetmilestone-inin1810 ** Tags added: architecture-s39064 bugnameltc-172698 severity-high targetmilestone-inin1810 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: 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/1800639 Title: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799424] Re: linux-gcp: 4.15.0-1024.25~16.04.2 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: + prepare-package: Package not yet uploaded promote-to-proposed: Review in progress -- 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/1799424 Title: linux-gcp: 4.15.0-1024.25~16.04.2 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: prepare-package: Package not yet uploaded promote-to-proposed: Review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799424] Re: linux-gcp: 4.15.0-1024.25~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => New -- 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/1799424 Title: linux-gcp: 4.15.0-1024.25~16.04.2 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: prepare-package: Package not yet uploaded promote-to-proposed: Review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799424] Re: linux-gcp: 4.15.0-1024.25~16.04.2 -proposed tracker
** Summary changed: - linux-gcp: 4.15.0-1024.25~16.04.1 -proposed tracker + linux-gcp: 4.15.0-1024.25~16.04.2 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1799424 Title: linux-gcp: 4.15.0-1024.25~16.04.2 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: prepare-package: Package not yet uploaded promote-to-proposed: Review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800641] [NEW] [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
You have been subscribed to a public bug: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-172700 severity-high targetmilestone-inin1810 -- [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup https://bugs.launchpad.net/bugs/1800641 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 1800641] [NEW] [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
Public bug reported: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-172700 severity-high targetmilestone-inin1810 ** Tags added: architecture-s39064 bugnameltc-172700 severity-high targetmilestone-inin1810 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: 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/1800641 Title: [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup Status in linux package in Ubuntu: New Bug description: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800639] Re: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800639 Title: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800509] Re: unable to handle kernel NULL pointer dereference at 0000000000000007
Please reproduce the problem, do a hard reset and then run this command: journalctl -b-1 > prev_boot.txt and send us the resulting file prev_boot.txt ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800509 Title: unable to handle kernel NULL pointer dereference at 0007 Status in linux package in Ubuntu: Incomplete Bug description: ```Oct 29 13:51:25 vs09 kernel: [201179.645520] BUG: unable to handle kernel NULL pointer dereference at 0007 Oct 29 13:51:25 vs09 kernel: [201179.645601] IP: split_swap_cluster+0x4f/0x70 Oct 29 13:51:25 vs09 kernel: [201179.645633] PGD 0 P4D 0 Oct 29 13:51:25 vs09 kernel: [201179.645660] Oops: 0002 [#1] SMP PTI Oct 29 13:51:25 vs09 kernel: [201179.645689] Modules linked in: vhost_net vhost tap xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp intel_cstate ipmi_ssif joydev input_leds intel_rapl_perf bridge stp llc mei_me lpc_ich mei ioatdma shpchp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid kvm_intel kvm irqbypass ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov Oct 29 13:51:25 vs09 kernel: [201179.646180] async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ast crct10dif_pclmul hid_generic crc32_pclmul ttm ghash_clmulni_intel pcbc drm_kms_helper usbhid syscopyarea igb sysfillrect aesni_intel sysimgblt dca aes_x86_64 crypto_simd fb_sys_fops glue_helper i2c_algo_bit ahci ptp drm mxm_wmi hid cryptd libahci pps_core wmi Oct 29 13:51:25 vs09 kernel: [201179.646418] CPU: 15 PID: 4321 Comm: qemu-system-x86 Not tainted 4.15.0-38-generic #41~16.04.1-Ubuntu Oct 29 13:51:25 vs09 kernel: [201179.646478] Hardware name: Supermicro SYS-6028R-TR/X10DRi, BIOS 2.1 09/13/2016 Oct 29 13:51:25 vs09 kernel: [201179.646531] RIP: 0010:split_swap_cluster+0x4f/0x70 Oct 29 13:51:25 vs09 kernel: [201179.646567] RSP: 0018:a9c9f77e3398 EFLAGS: 00010246 Oct 29 13:51:25 vs09 kernel: [201179.646606] RAX: RBX: 00064566 RCX: 00064566 Oct 29 13:51:25 vs09 kernel: [201179.646655] RDX: a9c9a0001000 RSI: 05cc5fff RDI: 00064566 Oct 29 13:51:25 vs09 kernel: [201179.646703] RBP: a9c9f77e33a0 R08: 0001 R09: 9140bffd4d00 Oct 29 13:51:25 vs09 kernel: [201179.646752] R10: 9140bffd4000 R11: 0001 R12: e5fdb3178000 Oct 29 13:51:25 vs09 kernel: [201179.646800] R13: e5fdb3178080 R14: e5fdb318 R15: e5fdb3178040 Oct 29 13:51:25 vs09 kernel: [201179.646850] FS: 7fb2a27fc700() GS:913fbee4() knlGS: Oct 29 13:51:25 vs09 kernel: [201179.646905] CS: 0010 DS: ES: CR0: 80050033 Oct 29 13:51:25 vs09 kernel: [201179.646946] CR2: 0007 CR3: 003f691b4006 CR4: 003626e0 Oct 29 13:51:25 vs09 kernel: [201179.646995] DR0: DR1: DR2: Oct 29 13:51:25 vs09 kernel: [201179.647043] DR3: DR6: fffe0ff0 DR7: 0400 Oct 29 13:51:25 vs09 kernel: [201179.647091] Call Trace: Oct 29 13:51:25 vs09 kernel: [201179.647119] split_huge_page_to_list+0x76e/0x7f0 Oct 29 13:51:25 vs09 kernel: [201179.647156] deferred_split_scan+0x177/0x2d0 Oct 29 13:51:25 vs09 kernel: [201179.647191] shrink_slab.part.50+0x20b/0x440 Oct 29 13:51:25 vs09 kernel: [201179.647226] shrink_node+0x2fc/0x310 Oct 29 13:51:25 vs09 kernel: [201179.647257] do_try_to_free_pages+0xee/0x360 Oct 29 13:51:25 vs09 kernel: [201179.647290] try_to_free_pages+0xf1/0x1c0 Oct 29 13:51:25 vs09 kernel: [201179.647324] __alloc_pages_slowpath+0x405/0xec0 Oct 29 13:51:25 vs09 kernel: [201179.647362] __alloc_pages_nodemask+0x265/0x280 Oct 29 13:51:25 vs09 kernel: [201179.647399] alloc_pages_vma+0x165/0x1e0 Oct 29 13:51:25 vs09 kernel: [201179.647431] do_huge_pmd_anonymous_page+0x167/0x710 Oct 29 13:51:25 vs09 kernel: [201179.647469] __handle_mm_fault+0xb1d/0x11e0 Oct 29 13:51:25 vs09 kernel: [201179.647504] handle_mm_fault+0xcc/0x1c0 Oct 29 13:51:25 vs09 kernel: [201179.647535] __get_user_pages+0x11d/0x6d0 Oct 29 13:51:25 vs09 kernel: [201179.647568] get_user_pages+0x42/0x50 Oct 29 13:51:25 vs09 kernel: [201179.647627] __gfn_to_pfn_memslot+0x18b/0x3b0 [kvm] Oct 29 13:51:25 vs09 kernel: [201179.6
[Kernel-packages] [Bug 1800254] Re: packet socket panic in Trusty 3.13.0-157 and later
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1800254
Title:
packet socket panic in Trusty 3.13.0-157 and later
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Fix Committed
Bug description:
SRU Justification:
Due to changes added as part of c108ac876c02 ("packet: hold bind lock when
rebinding to fanout hook"), it is possible for fanout_add to add a
packet_type handler via dev_add_pack and then kfree the memory backing the
packet_type. This corrupts the ptype_all list, causing the system to
panic when network packet processing next traverses ptype_all. The
erroneous path is taken when a PACKET_FANOUT setsockopt is performed on a
packet socket that is bound to an interface that is administratively down.
This is not due to any flaw of c108ac876c02, but rather than the packet
socket code base differs subtly in 3.13 as compared to 4.4.
This affects only the Trusty 3.13 kernel series, starting with
3.13.0-157.
Fix:
The remedy for this is to backport additional changes in the management of
the dev_add_pack calls from 4.4. This moves the dev_add_pack and
dev_remove_pack calls from fanout_add and _release into __fanout_link and
_unlink.
Testcase:
The issue can be reproduced reliably by (a) creating an AF_PACKET socket,
binding it to an interface that is administratively down, and then (c)
attempting to set the PACKET_FANOUT sockopt. The setsockopt call will
fail, but will corrupt ptype_all in the kernel. Subsequent network traffic
will induce a panic when evaulating the corrupted ptype_all entry. A
test program is attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800254/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779848] Re: Cleanup Meltdown/Spectre implementation
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed- trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779848 Title: Cleanup Meltdown/Spectre implementation Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Bug description: == SRU Justification == Ubuntu kernels contain Meltdown and Spectre mitigations that are largely based on embargoed patches but what eventually landed in upstream is different in some places. We should clean up the different kernels to bring them closer in line with upstream. == Fix == Add missing upstream patches. == Regression Potential == Medium. The patches have been in upstream for quite a while now and are baked in but some of the backporting is not completely trivial and without risk. == Test Case == TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798013] Re: xattr length returned by vfs_getxattr() is not correct in Trusty kernel
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798013
Title:
xattr length returned by vfs_getxattr() is not correct in Trusty
kernel
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Committed
Bug description:
== Justification ==
This issue has been addressed in bug 1789746 for other kernels
When the getxattr05 test in ubuntu_ltp_syscalls test suite, the test
will failed with:
tag=getxattr05 stime=1539663573
cmdline="getxattr05"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
getxattr05.c:85: PASS: Got same data when acquiring the value of
system.posix_acl_access twice
getxattr05.c:80: FAIL: Got different data(00 != ) at 16
getxattr05.c:85: PASS: Got same data when acquiring the value of
system.posix_acl_access twice
Summary:
passed 2
failed 1
skipped 0
warnings 0
This is caused by posix_acl_fix_xattr_to_user() being passed the total
buffer size and not the actual size of the xattr as returned by
vfs_getxattr().
== Fix ==
82c9a927bc5d ("getxattr: use correct xattr length")
A test kernel for Trusty could be found here:
http://people.canonical.com/~phlin/kernel/lp-1798013-getxattr05/
== Regression Potential ==
Low, this one-liner fix just passes the actual length of the xattr as
returned by vfs_getxattr() down.
== Test Case ==
Run the getxattr05 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-160-generic 3.13.0-160.210
ProcVersionSignature: User Name 3.13.0-160.210-generic 3.13.11-ckt39
Uname: Linux 3.13.0-160-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 16 03:39 seq
crw-rw 1 root audio 116, 33 Oct 16 03:39 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 16 04:19:43 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Intel Corporation S1200RP
PciMultimedia:
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-160-generic
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8
RelatedPackageVersions:
linux-restricted-modules-3.13.0-160-generic N/A
linux-backports-modules-3.13.0-160-generic N/A
linux-firmware 1.127.24
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
dmi.board.asset.tag:
dmi.board.name: S1200RP
dmi.board.vendor: Intel Corporation
dmi.board.version: G62254-407
dmi.chassis.asset.tag:
dmi.chassis.type: 17
dmi.chassis.vendor: ..
dmi.chassis.version: ..
dmi.modalias:
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
dmi.product.name: S1200RP
dmi.product.version:
dmi.sys.vendor: Intel Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798013/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799399] Re: linux: 3.13.0-162.212 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Uploaded reason: promote-to-proposed: Packages waiting in -proposed for mirror sync + kernel-stable-phase-changed:Tuesday, 30. October 2018 12:05 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true - phase: Uploaded + bugs-spammed: true + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Packages waiting in -proposed for mirror sync - kernel-stable-phase-changed:Tuesday, 30. October 2018 12:05 UTC - kernel-stable-phase:Promoted to proposed + automated-testing: Testing in progress + certification-testing: Testing in progress + regression-testing: Testing in progress + security-signoff: Waiting for signoff + verification-testing: Testing 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/1799399 Title: linux: 3.13.0-162.212 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing in progress certification-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799424] Re: linux-gcp: 4.15.0-1024.25~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously (kmously) ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: prepare-package: Package not yet uploaded promote-to-proposed: Review in progress + kernel-stable-phase-changed:Tuesday, 30. October 2018 12:01 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: prepare-package: Package not yet uploaded - promote-to-proposed: Review in progress - kernel-stable-phase-changed:Tuesday, 30. October 2018 12:01 UTC - kernel-stable-phase:Uploaded + prepare-package-signed: Package not yet uploaded -- 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/1799424 Title: linux-gcp: 4.15.0-1024.25~16.04.2 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: prepare-package: Package not yet uploaded prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800641] Re: [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800641 Title: [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799400] Re: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1799400 Title: linux-lts-trusty: 3.13.0-162.212~precise1 -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 prepare-package-signed 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 phase: Uploaded reason: promote-to-proposed: Review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799415] Re: linux-azure: 4.15.0-1029.30 -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 ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Packaging reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 30. October 2018 13:00 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 - phase: Packaging + phase: Uploaded reason: - prepare-package: Package not yet uploaded - prepare-package-meta: Package not yet uploaded - prepare-package-signed: Package not yet uploaded - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Tuesday, 30. October 2018 13:00 UTC + promote-to-proposed: Builds not complete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1799415 Title: linux-azure: 4.15.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: promote-to-proposed: Builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799400] Re: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 phase: Uploaded reason: - promote-to-proposed: Review in progress + promote-to-proposed: Packages copied but not yet published to -proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1799400 Title: linux-lts-trusty: 3.13.0-162.212~precise1 -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 prepare-package-signed 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 phase: Uploaded reason: promote-to-proposed: Packages copied but not yet published to -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800641] Re: [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Cosmic) 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/1800641 Title: [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."
I built a test kernel using the master-next repo. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1792100 Can you test that kernel and report back if it has the bug or not? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792100 Title: Boot hangs at "loading initial ramdisk..." Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I cannot load a kernel beyond 4.15.0-32-generic on my machine. Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial ramdisk...". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kms2233 F pulseaudio /dev/snd/controlC1: kms2233 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 10:52:00 2018 HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef InstallationDate: Installed on 2018-01-05 (249 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision Tower 7810 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago) dmi.bios.date: 06/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A27 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
Kai-Heng Feng Bluetooth missing issue started appearing again dmesg attached P.S. I use self-installed ubuntu 18.10 ** Attachment added: "dmesg.tbz2" https://bugs.launchpad.net/dell-sputnik/+bug/1766825/+attachment/5207165/+files/dmesg.tbz2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Triaged Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25
[Kernel-packages] [Bug 1800664] [NEW] Add checksum offload and TSO support for HiNIC adapters
Public bug reported: [Impact] Increases throughput by more than 2x, as measured by the iperf benchmark. [Test Case] iperf -c 192.168.122.10 -P5 [Fix] cc18a7543d2f6 net-next/hinic: add checksum offload and TSO support [Regression Risk] Clean cherry-pick restricted to a single driver that has been explicitly tested. A regression risk is that these bugs in these new features, which are enabled by default, could impact existing deployments. These features can, however, be disabled by ethtool which helps mitigate that risk. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800664 Title: Add checksum offload and TSO support for HiNIC adapters Status in linux package in Ubuntu: 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 Bug description: [Impact] Increases throughput by more than 2x, as measured by the iperf benchmark. [Test Case] iperf -c 192.168.122.10 -P5 [Fix] cc18a7543d2f6 net-next/hinic: add checksum offload and TSO support [Regression Risk] Clean cherry-pick restricted to a single driver that has been explicitly tested. A regression risk is that these bugs in these new features, which are enabled by default, could impact existing deployments. These features can, however, be disabled by ethtool which helps mitigate that risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799416] Re: linux-gcp: 4.15.0-1024.25 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release - gcp-kernel 18/candidate verification-testing: Testing in progress -- 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/1799416 Title: linux-gcp: 4.15.0-1024.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799411] Re: linux: 4.15.0-39.42 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1799413 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) kernel-stable-phase-changed:Tuesday, 23. October 2018 16:06 UTC kernel-stable-phase:Uploaded -- swm properties -- backports: null boot-testing-requested: true bugs-spammed: true derivatives: null phase: Uploaded reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release - pc-kernel 18/candidate verification-testing: Testing 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/1799411 Title: linux: 4.15.0-39.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1799413 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) kernel-stable-phase-changed:Tuesday, 23. October 2018 16:06 UTC kernel-stable-phase:Uploaded -- swm properties -- backports: null boot-testing-requested: true bugs-spammed: true derivatives: null phase: Uploaded reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799400] Re: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 phase: Uploaded reason: - promote-to-proposed: Packages copied but not yet published to -proposed + promote-to-proposed: Packages copies requested -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1799400 Title: linux-lts-trusty: 3.13.0-162.212~precise1 -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 prepare-package-signed 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 phase: Uploaded reason: promote-to-proposed: Packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800446] Re: kidle_inject constantly running
I reinstalled thermald and tried with the 4.15 kernel and still got intense throttling. I noticed that with either kernel the dmesg output still dumps this: [ 47.365544] CPU1: Core temperature above threshold, cpu clock throttled (total events = 1) [ 47.365568] CPU5: Core temperature above threshold, cpu clock throttled (total events = 1) [ 47.365570] CPU5: Package temperature above threshold, cpu clock throttled (total events = 1) [ 47.365573] CPU6: Package temperature above threshold, cpu clock throttled (total events = 1) [ 47.365574] CPU4: Package temperature above threshold, cpu clock throttled (total events = 1) [ 47.365575] CPU0: Package temperature above threshold, cpu clock throttled (total events = 1) [ 47.365576] CPU7: Package temperature above threshold, cpu clock throttled (total events = 1) [ 47.365577] CPU1: Package temperature above threshold, cpu clock throttled (total events = 1) [ 47.365577] CPU3: Package temperature above threshold, cpu clock throttled (total events = 1) [ 47.365578] CPU2: Package temperature above threshold, cpu clock throttled (total events = 1) But without thermald I don't get the throttling. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800446 Title: kidle_inject constantly running Status in linux package in Ubuntu: Incomplete Bug description: Computer boots up fine, but as soon as any process causes a single spike in CPU, `kidle_inject` starts and it just won't stop. Even after 1 hour of idling, with low temperatures, no fan, it’s still making this computer unresponsive. I disabled `kidle_inject` process by creating a file `/etc/modprobe.d /blacklist-power.conf` with the following content: ``` blacklist intel_powerclamp blacklist intel_rapl ``` Then I restarted computer. Since then, my computer is not unresponsive anymore, and I use it to work all the time. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: williamivanski 5974 F pulseaudio /dev/snd/controlC1: williamivanski 5974 F pulseaudio Date: Mon Oct 29 08:05:09 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1c6d4273-ae09-412d-9488-78ab7ba2fc4b InstallationDate: Installed on 2015-09-23 (1131 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LG Electronics 13Z940-G.BK71P1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=42b637c4-2da3-4c1a-a62d-b4beb93b8243 ro quiet splash 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-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-23 (5 days ago) dmi.bios.date: 09/04/2014 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 13Z940FF dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: White Tip Mountain dmi.board.vendor: LG Electronics dmi.board.version: FAB3 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr13Z940FF:bd09/04/2014:svnLGElectronics:pn13Z940-G.BK71P1:pvr0.1:rvnLGElectronics:rnWhiteTipMountain:rvrFAB3:cvnLGElectronics:ct9:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: 13Z940-G.BK71P1 dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799414] Re: linux-aws: 4.15.0-1026.26 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release - aws-kernel 18/candidate verification-testing: Testing 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/1799414 Title: linux-aws: 4.15.0-1026.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800639] Re: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Cosmic) 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/1800639 Title: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: In Progress Bug description: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800641] Re: [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
These are the same two commits requested in bug 1800639. Is that correct? If so, I'll mark this bug as a duplicate of that bug. ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800641 Title: [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800639] Re: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => 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/1800639 Title: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: In Progress Bug description: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799424] Re: linux-gcp: 4.15.0-1024.25~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: prepare-package: Package not yet uploaded prepare-package-signed: Package not yet uploaded + kernel-stable-phase-changed:Tuesday, 30. October 2018 14:32 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: - prepare-package: Package not yet uploaded - prepare-package-signed: Package not yet uploaded - kernel-stable-phase-changed:Tuesday, 30. October 2018 14:32 UTC - kernel-stable-phase:Uploaded + promote-to-proposed: Builds not complete -- 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/1799424 Title: linux-gcp: 4.15.0-1024.25~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: promote-to-proposed: Builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799400] Re: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 phase: Uploaded reason: - promote-to-proposed: Packages copies requested + promote-to-proposed: Packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1799400 Title: linux-lts-trusty: 3.13.0-162.212~precise1 -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 prepare-package-signed 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 phase: Uploaded reason: promote-to-proposed: Packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798658] Re: linux-azure: 4.15.0-1028.29 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.15.0-1028.29 upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release azure-kernel 18/candidate + kernel-stable-phase-changed:Tuesday, 30. October 2018 14:33 UTC + kernel-stable-phase:Released ** Description changed: This bug is for tracking the 4.15.0-1028.29 upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - phase: Promoted to updates + phase: Released proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (Confirmed) - snap-release-to-candidate: snap not in 18/candidate channel -- snapcraft release - azure-kernel 18/candidate - kernel-stable-phase-changed:Tuesday, 30. October 2018 14:33 UTC - kernel-stable-phase: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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1798658 Title: linux-azure: 4.15.0-1028.29 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Fix Released Bug description: This bug is for tracking the 4.15.0-1028.29 upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Released proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (Confirmed) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1798658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798674] Re: linux-azure: 4.15.0-1028.29~16.04.1 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-candidate: snap not in candidate channel -- snapcraft release azure-kernel candidate + kernel-stable-phase-changed:Tuesday, 30. October 2018 14:30 UTC + kernel-stable-phase:Released ** Description changed: This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - phase: Promoted to updates + phase: Released proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (Confirmed) - snap-release-to-candidate: snap not in candidate channel -- snapcraft release azure-kernel - candidate - kernel-stable-phase-changed:Tuesday, 30. October 2018 14:30 UTC - kernel-stable-phase: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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1798674 Title: linux-azure: 4.15.0-1028.29~16.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.15.0-1028.29~16.04.1 upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Released proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (Confirmed) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1798674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799401] Re: linux: 4.4.0-139.165 -proposed tracker
on the snap testing, it fails test_095_kernel_symbols_missing from the kernel security tests because it is unable to read /proc/self/stack as a normal user. Can you confirm if this is expected? == FAIL: test_095_kernel_symbols_missing (test_kernel_security.KernelSecurityTest) kernel addresses in kallsyms and modules are zeroed out -- Traceback (most recent call last): File "/home/ubuntu/snap/checkbox-snappy/1418/.cache/plainbox/sessions/smoke-test-2018-10-30T13.32.02.session/CHECKBOX_DATA/test_kernel_security.py", line 1499, in test_095_kernel_symbols_missing self._check_pK_files(expected) File "/home/ubuntu/snap/checkbox-snappy/1418/.cache/plainbox/sessions/smoke-test-2018-10-30T13.32.02.session/CHECKBOX_DATA/test_kernel_security.py", line 1474, in _check_pK_files expected, retry=True) File "/home/ubuntu/snap/checkbox-snappy/1418/.cache/plainbox/sessions/smoke-test-2018-10-30T13.32.02.session/CHECKBOX_DATA/test_kernel_security.py", line 1378, in _read_twice self.assertEqual(rc, 0, regular) AssertionError: 1 != 0 : cat: /proc/self/stack: Permission denied -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799401 Title: linux: 4.4.0-139.165 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799403 (linux-aws), bug 1799404 (linux-lts-xenial) derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 (linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff snap-certification-testing: Ready verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800446] Re: kidle_inject constantly running
Here is what I did: - Removed file /etc/modprobe.d/blacklist-power.conf to re-enable kidle_inject - Disabled thermald - Restarted the computer on kernel 4.18 I confirm I don't get the throttling. In Ubuntu 18.04, thermald version is 1.7.0-5ubuntu1, while on Ubuntu 18.10 it is 1.7.0-8. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800446 Title: kidle_inject constantly running Status in linux package in Ubuntu: Incomplete Bug description: Computer boots up fine, but as soon as any process causes a single spike in CPU, `kidle_inject` starts and it just won't stop. Even after 1 hour of idling, with low temperatures, no fan, it’s still making this computer unresponsive. I disabled `kidle_inject` process by creating a file `/etc/modprobe.d /blacklist-power.conf` with the following content: ``` blacklist intel_powerclamp blacklist intel_rapl ``` Then I restarted computer. Since then, my computer is not unresponsive anymore, and I use it to work all the time. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: williamivanski 5974 F pulseaudio /dev/snd/controlC1: williamivanski 5974 F pulseaudio Date: Mon Oct 29 08:05:09 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1c6d4273-ae09-412d-9488-78ab7ba2fc4b InstallationDate: Installed on 2015-09-23 (1131 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LG Electronics 13Z940-G.BK71P1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=42b637c4-2da3-4c1a-a62d-b4beb93b8243 ro quiet splash 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-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-23 (5 days ago) dmi.bios.date: 09/04/2014 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 13Z940FF dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: White Tip Mountain dmi.board.vendor: LG Electronics dmi.board.version: FAB3 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr13Z940FF:bd09/04/2014:svnLGElectronics:pn13Z940-G.BK71P1:pvr0.1:rvnLGElectronics:rnWhiteTipMountain:rvrFAB3:cvnLGElectronics:ct9:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: 13Z940-G.BK71P1 dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799400] Re: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 phase: Uploaded reason: promote-to-proposed: Packages waiting in -proposed for mirror sync + kernel-stable-phase-changed:Tuesday, 30. October 2018 15:02 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 - phase: Uploaded + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Packages waiting in -proposed for mirror sync - kernel-stable-phase-changed:Tuesday, 30. October 2018 15:02 UTC - kernel-stable-phase:Promoted to proposed + regression-testing: Testing in progress + security-signoff: Waiting for signoff + verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1799400 Title: linux-lts-trusty: 3.13.0-162.212~precise1 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799399 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1
Sometimes it finds the displays, and sometimes it does not. Uploading two Xorg.0 log files from /var/lib/gdm3/.local/share/xorg/ One from before stopping gdm, running Xorg as root, stopping Xorg as root and then restarting gdm. The first one finds no displays: +(II) NVIDIA(0): "NULL" +(II) NVIDIA(0): Virtual screen size determined to be 640 x 480 +(WW) NVIDIA(0): Unable to get display device for DPI computation. +(==) NVIDIA(0): DPI set to (75, 75); computed from built-in default Where as the second gets: -(--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0 -(--) NVIDIA(0): DFP-1.1 -(--) NVIDIA(0): DFP-1.2 -(--) NVIDIA(0): DFP-1.3 -(--) NVIDIA(0): DFP-0 -(--) NVIDIA(0): DFP-1 (boot) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/174 Title: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime- select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 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 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/174/+attachment/5207171/+files/Xorg.0.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/174 Title: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime- select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 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 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse
[Kernel-packages] [Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1
** Attachment added: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/174/+attachment/5207172/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/174 Title: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime- select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 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 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevi
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
I still have add ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 to even boot. Ubuntu 18.10 works great so long as I add those in GRUBs editor before boot or permanently add to grub.cfg after install. Also, hiding the AE_ALREADY_EXISTS errors doesn't mean they're gone. Fedora is experimenting with a cool feature that freezes an image in the framebuffer (similar to what windows 10 does during the loading screen and circling dots), this hides the flicker to console, then flicker to plymouth bootscreen. It goes straight from BIOS image to plymouth (very awesome). a journalctl -xe and possibly dmesg should still show those errors. As a side note, ACER has contacted me back again. They did a little research and noticed there was indeed a community of people who are experiencing this issue and the community did seem large enough to warrant being looked into and possibly fixed for Linux Users! Customer support has been pretty awesome about all this so far. I'm very impressed. They've asked that I pull together some info to better explain the issues so they can forward them up to the engineers for review. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799237] Re: mprotect fails on ext4 with dax
It turns out that this issue is only present for certain mapping lengths.
If I run the program, which I attached to the bug report, with size>=2M,
mprotect succeeds.
I have also tested this on device dax, and the results depend on alignment.
For 2M alignment, everything works fine, for 4k alignment mprotect fails for
all sizes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Confirmed
Status in pmdk package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799184] Re: [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding
** 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/1799184 Title: [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: With the introduction of KVM crypto virtualization the driver bound to an AP queue device is no longer unique determined. This feature provides a deterministic hot plugging semantics of AP queues that may be bound to multiple drivers. In particular it enables to configure an AP queue (APQN) as being bound to a particular driver even if the associate HW gets intermittently lost and reconnected. This function has to be applied to kernel 4.15 for Ubuntu 18.04, Git Commit information available here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784331 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1799184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800639] Re: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => 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/1800639 Title: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport Status in Ubuntu on IBM z Systems: Triaged 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 Bug description: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777600] Re: chzdev can't find modprobe
This bug was fixed in the package s390-tools - 2.3.0-0ubuntu3.1 --- s390-tools (2.3.0-0ubuntu3.1) bionic; urgency=medium * zdev: Adjust zdev modprobe path to be compatible with split-usr systems. (LP: #1777600) * zdev: Trigger generic_ccw devices on any kernel module loads. (LP: #1794308) -- Dimitri John Ledkov Mon, 22 Oct 2018 12:37:39 +0100 ** Changed in: s390-tools (Ubuntu Bionic) 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/1777600 Title: chzdev can't find modprobe Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: Fix Released Status in s390-tools source package in Bionic: Fix Released Status in s390-tools source package in Cosmic: Fix Released Bug description: [Impact] * chzdev fails to load additional kernel modules at runtime, resulting in failure to activate devices. [Test Case] $ chzdev zfcp --type datarouter=0 dbflevel=5 Should succeed, instead of erroring out / not able to find modprobe. [Regression Potential] * This corrects compiled-in path to /sbin/modprobe, thus making available previously a broken codepath of chzdev. [Other Info] * Original bug report Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787405] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2018-10-30 11:51 EDT--- the qemu patches are (in reverse order) 694a8d703b s390: doc: detailed specifications for AP virtualization 2fe2942cd6 s390x/vfio: ap: Introduce VFIO AP device a51b31535a s390x/ap: base Adjunct Processor (AP) object model 1d7db85b61 s390x/kvm: enable AP instruction interpretation for guest c5cd17afdd s390x/cpumodel: Set up CPU model for AP device support 8f3cd250a8 linux-headers: update There are some minor merge conflicts that are easy to solve when merging into 3.0,2.12 or older -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787405 Title: [19.04 FEAT] Guest-dedicated Crypto Adapters Status in Ubuntu on IBM z Systems: Triaged Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Description: Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to a KVM guest such that the hypervisor cannot observe the communication of the guest with the device. This functionality will be contribute to following packages. --kernel, qemu and libvirt. Currently these functions are not finalized and therefore no git-commit are avalable, - kernel > 4.19 - libvirt > 4.6.0 - qemu > 3.0 We will provide these as soon as possible. This request is launched against Ubuntu 18.10 to fulllfil the feature integration process of Canonical. But the main intention is, to get this integrated into 18.04 LTS !! Thererfore, the backports will be required for both distros.! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1787405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787405] Re: [19.04 FEAT] Guest-dedicated Crypto Adapters
** 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/1787405 Title: [19.04 FEAT] Guest-dedicated Crypto Adapters Status in Ubuntu on IBM z Systems: Triaged Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Description: Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to a KVM guest such that the hypervisor cannot observe the communication of the guest with the device. This functionality will be contribute to following packages. --kernel, qemu and libvirt. Currently these functions are not finalized and therefore no git-commit are avalable, - kernel > 4.19 - libvirt > 4.6.0 - qemu > 3.0 We will provide these as soon as possible. This request is launched against Ubuntu 18.10 to fulllfil the feature integration process of Canonical. But the main intention is, to get this integrated into 18.04 LTS !! Thererfore, the backports will be required for both distros.! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1787405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777600] Update Released
The verification of the Stable Release Update for s390-tools has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777600 Title: chzdev can't find modprobe Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: Fix Committed Status in s390-tools source package in Bionic: Fix Released Status in s390-tools source package in Cosmic: Fix Released Bug description: [Impact] * chzdev fails to load additional kernel modules at runtime, resulting in failure to activate devices. [Test Case] $ chzdev zfcp --type datarouter=0 dbflevel=5 Should succeed, instead of erroring out / not able to find modprobe. [Regression Potential] * This corrects compiled-in path to /sbin/modprobe, thus making available previously a broken codepath of chzdev. [Other Info] * Original bug report Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799415] Re: linux-azure: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded - reason: - promote-to-proposed: Builds not complete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1799415 Title: linux-azure: 4.15.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777600] Re: chzdev can't find modprobe
This bug was fixed in the package s390-tools - 1.34.0-0ubuntu8.8 --- s390-tools (1.34.0-0ubuntu8.8) xenial; urgency=medium * zdev: Adjust zdev modprobe path to be compatible with split-usr systems. (LP: #1777600) * zdev: Trigger generic_ccw devices on any kernel module loads. (LP: #1794308) -- Dimitri John Ledkov Mon, 22 Oct 2018 12:51:12 +0100 ** Changed in: s390-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777600 Title: chzdev can't find modprobe Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: Fix Released Status in s390-tools source package in Bionic: Fix Released Status in s390-tools source package in Cosmic: Fix Released Bug description: [Impact] * chzdev fails to load additional kernel modules at runtime, resulting in failure to activate devices. [Test Case] $ chzdev zfcp --type datarouter=0 dbflevel=5 Should succeed, instead of erroring out / not able to find modprobe. [Regression Potential] * This corrects compiled-in path to /sbin/modprobe, thus making available previously a broken codepath of chzdev. [Other Info] * Original bug report Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787405] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2018-10-30 12:04 EDT--- the libvirt patches have landed as well a017bae1ae news: Update news for vfio-ap support 1170864198 qemu: vfio-ap device support dc788d2540 qemu: add vfio-ap capability -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787405 Title: [19.04 FEAT] Guest-dedicated Crypto Adapters Status in Ubuntu on IBM z Systems: Triaged Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in qemu package in Ubuntu: Incomplete Bug description: Description: Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to a KVM guest such that the hypervisor cannot observe the communication of the guest with the device. This functionality will be contribute to following packages. --kernel, qemu and libvirt. Currently these functions are not finalized and therefore no git-commit are avalable, - kernel > 4.19 - libvirt > 4.6.0 - qemu > 3.0 We will provide these as soon as possible. This request is launched against Ubuntu 18.10 to fulllfil the feature integration process of Canonical. But the main intention is, to get this integrated into 18.04 LTS !! Thererfore, the backports will be required for both distros.! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1787405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787405] Re: [19.04 FEAT] Guest-dedicated Crypto Adapters
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787405 Title: [19.04 FEAT] Guest-dedicated Crypto Adapters Status in Ubuntu on IBM z Systems: Triaged Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in qemu package in Ubuntu: Incomplete Bug description: Description: Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to a KVM guest such that the hypervisor cannot observe the communication of the guest with the device. This functionality will be contribute to following packages. --kernel, qemu and libvirt. Currently these functions are not finalized and therefore no git-commit are avalable, - kernel > 4.19 - libvirt > 4.6.0 - qemu > 3.0 We will provide these as soon as possible. This request is launched against Ubuntu 18.10 to fulllfil the feature integration process of Canonical. But the main intention is, to get this integrated into 18.04 LTS !! Thererfore, the backports will be required for both distros.! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1787405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799184] Re: [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding
** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799184 Title: [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: With the introduction of KVM crypto virtualization the driver bound to an AP queue device is no longer unique determined. This feature provides a deterministic hot plugging semantics of AP queues that may be bound to multiple drivers. In particular it enables to configure an AP queue (APQN) as being bound to a particular driver even if the associate HW gets intermittently lost and reconnected. This function has to be applied to kernel 4.15 for Ubuntu 18.04, Git Commit information available here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784331 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1799184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787405] Re: [19.04 FEAT] Guest-dedicated Crypto Adapters
** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787405 Title: [19.04 FEAT] Guest-dedicated Crypto Adapters Status in Ubuntu on IBM z Systems: Triaged Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in qemu package in Ubuntu: Incomplete Bug description: Description: Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to a KVM guest such that the hypervisor cannot observe the communication of the guest with the device. This functionality will be contribute to following packages. --kernel, qemu and libvirt. Currently these functions are not finalized and therefore no git-commit are avalable, - kernel > 4.19 - libvirt > 4.6.0 - qemu > 3.0 We will provide these as soon as possible. This request is launched against Ubuntu 18.10 to fulllfil the feature integration process of Canonical. But the main intention is, to get this integrated into 18.04 LTS !! Thererfore, the backports will be required for both distros.! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1787405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787405] Re: [19.04 FEAT] Guest-dedicated Crypto Adapters
** Tags added: libvirt-19.04 qemu-19.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787405 Title: [19.04 FEAT] Guest-dedicated Crypto Adapters Status in Ubuntu on IBM z Systems: Triaged Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in qemu package in Ubuntu: Incomplete Bug description: Description: Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to a KVM guest such that the hypervisor cannot observe the communication of the guest with the device. This functionality will be contribute to following packages. --kernel, qemu and libvirt. Currently these functions are not finalized and therefore no git-commit are avalable, - kernel > 4.19 - libvirt > 4.6.0 - qemu > 3.0 We will provide these as soon as possible. This request is launched against Ubuntu 18.10 to fulllfil the feature integration process of Canonical. But the main intention is, to get this integrated into 18.04 LTS !! Thererfore, the backports will be required for both distros.! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1787405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777600] Re: chzdev can't find modprobe
** Changed in: ubuntu-z-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/1777600 Title: chzdev can't find modprobe Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: Fix Released Status in s390-tools source package in Bionic: Fix Released Status in s390-tools source package in Cosmic: Fix Released Bug description: [Impact] * chzdev fails to load additional kernel modules at runtime, resulting in failure to activate devices. [Test Case] $ chzdev zfcp --type datarouter=0 dbflevel=5 Should succeed, instead of erroring out / not able to find modprobe. [Regression Potential] * This corrects compiled-in path to /sbin/modprobe, thus making available previously a broken codepath of chzdev. [Other Info] * Original bug report Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800639] Re: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
** Changed in: ubuntu-z-systems Status: Triaged => 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/1800639 Title: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport Status in Ubuntu on IBM z Systems: 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 Bug description: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800639] Re: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
I built a test kernel with commits 065a2cdcbd and 048a7f8b4. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1800639 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800639 Title: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport Status in Ubuntu on IBM z Systems: 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 Bug description: Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom: Infinite loop when processing a received cmd. Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build human-readable messages for received cmd data. They store the to-be translated value in the last entry of a global array, and then iterate over each entry until they found the queried value (and the corresponding message string). If there is no prior match, the lookup is intended to stop at the final entry (which was previously prepared). If two qeth devices are concurrently processing a received cmd, one lookup can over-write the last entry of the global array while a second lookup is in process. This second lookup will then never hit its stop-condition, and loop. Solution: Remove the modification of the global array, and limit the number of iterations to the size of the array. Upstream-ID: kernel 4.19 - 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b - 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9 Should also be applied, to all other Ubuntu Releases in the field ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799398] Re: linux: 3.2.0-137.183 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- reason: - prepare-package: Version not specified + prepare-package: Package not yet uploaded + prepare-package-lbm: Package not yet uploaded + prepare-package-meta: Package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799398 Title: linux: 3.2.0-137.183 -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: In Progress Status in Kernel SRU Workflow prepare-package-lbm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- reason: prepare-package: Package not yet uploaded prepare-package-lbm: Package not yet uploaded prepare-package-meta: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799422] Re: linux-azure: 4.15.0-1029.30~16.04.1 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 4.15.0-1029.30~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1799422 Title: linux-azure: 4.15.0-1029.30~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Packaging reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799398] Re: linux: 3.2.0-137.183 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 3.2.0-137.183 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799398 Title: linux: 3.2.0-137.183 -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: In Progress Status in Kernel SRU Workflow prepare-package-lbm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- reason: prepare-package: Package not yet uploaded prepare-package-lbm: Package not yet uploaded prepare-package-meta: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799422] Re: linux-azure: 4.15.0-1029.30~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Packaging reason: - prepare-package: Version not specified + prepare-package: Package not yet uploaded + prepare-package-meta: Package not yet uploaded + prepare-package-signed: Package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1799422 Title: linux-azure: 4.15.0-1029.30~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Packaging reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
I'll run a test tonight and see if I can get power draw differences at the wall between windows and Linux. Hopefully when Acer drills this down, we'll see something that compares pretty well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799424] Re: linux-gcp: 4.15.0-1024.25~16.04.2 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded - reason: - promote-to-proposed: Builds not complete -- 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/1799424 Title: linux-gcp: 4.15.0-1024.25~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799415] Re: linux-azure: 4.15.0-1029.30 -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 is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded + reason: + promote-to-proposed: Ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1799415 Title: linux-azure: 4.15.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799422] Re: linux-azure: 4.15.0-1029.30~16.04.1 -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 ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Packaging reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 30. October 2018 17:35 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 - phase: Packaging + phase: Uploaded reason: - prepare-package: Package not yet uploaded - prepare-package-meta: Package not yet uploaded - prepare-package-signed: Package not yet uploaded - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Tuesday, 30. October 2018 17:35 UTC + promote-to-proposed: Builds not complete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1799422 Title: linux-azure: 4.15.0-1029.30~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: promote-to-proposed: Builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799424] Re: linux-gcp: 4.15.0-1024.25~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded + reason: + promote-to-proposed: Ready for review -- 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/1799424 Title: linux-gcp: 4.15.0-1024.25~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799415] Re: linux-azure: 4.15.0-1029.30 -proposed tracker
Watching for a test build. ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1799415 Title: linux-azure: 4.15.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: promote-to-proposed: Ready for review stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799415] Re: linux-azure: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: promote-to-proposed: Ready for review + stakeholder-signoff: Waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1799415 Title: linux-azure: 4.15.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1799411 phase: Uploaded reason: promote-to-proposed: Ready for review stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
Some feedback for Cosmic: FWIW, I can confirm that the update did NOT break the keyboard backlight key on Dell XPS 15 9575, where it had already worked flawlessly out-of- the-box with Cosmic since installation in early September (contrary to the bug description above stating that "keyboard backlight control keys don't work in cosmic") At the time also submitted the similar bug #1791372, "Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image". I can test this update on the Asus as well but cannot report result before Sunday, Oct 4. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Committed Status in upower source package in Cosmic: Fix Committed Bug description: * Impact keyboard backlight control keys don't work in cosmic * Test case On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level * Regression potential The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working --- https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800465] Re: Vulkan error when using NVIDIA-Prime
This ONLY happens on Ubuntu 18.10, no issue in 18.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1800465 Title: Vulkan error when using NVIDIA-Prime Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: New Bug description: After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils, switching to NVIDIA and then running vulkaninfo or vulkan-cube works perfectly. But when you reboot and update, then switch to Intel, then back to Nvidia, all Vulkan programs give an "Assertion `!err' failed." Vulkaninfo: === Presentable Surfaces: = GPU id : 0 (GeForce GTX 960M) Surface type : VK_KHR_xcb_surface vulkaninfo: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253: AppDumpSurfaceFormats: Assertion `!err' failed. Annullato (core dump creato) Vulkancube: vulkan-cube: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: demo_init_vk_swapchain: Assertion `!err' failed. Annullato (core dump creato) I still have not found a workaround for that, the only way to get it working again is to reinstall everything. - Install Ubuntu 18.10 - Install proprietary 390 NVIDIA drivers - Switch NVIDIA-Prime to NVIDIA - Testing the vulkan capabilities works - Updating the system then switching to intel - Reboot - Switch to nvida - Now all Vulkan programs when using NVIDIA give that error To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
