[Kernel-packages] [Bug 1813423] Re: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-modesetting (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/1813423 Title: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A" Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-modesetting package in Ubuntu: Confirmed Bug description: My system keeps freezing on a brand new install of Kubuntu 18.10, always with the kern.log error "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235) time 486 us, min 763, max 767, scanline start 760, end 783" I think it's probably a duplicate of these bugs which were closed unresolved: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was on an older version of Ubuntu) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because it was a duplicate of the first bug) It happens far more frequently if I have desktop effects turned on, and far less frequently when using a live USB key (at always happens eventually though. Usually once every few hours.) Please advise how I can help triage / test. My system is a new install now, so I'm perfectly willing to modify / reinstall to help testing (I've reinstalled 5 times to test things, but never managed to find a solution) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 26 14:19:52 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227a] InstallationDate: Installed on 2019-01-18 (8 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227A dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 14 Notebook PC dmi.product.sku: J9L01UA#ABL dmi.product.version: 096C110800405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814092] Re: ADT test failure: quota and zram smoke tests don't install modules-extra pkg
Seems to be working as expected. https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=d0d453a008537ada7d52135ceb03c82ee057a2d8 Running 'apt-get install --yes --force-yes linux-modules-extra-gcp*' Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: linux-modules-extra-4.15.0-1027-gcp The following NEW packages will be installed: linux-modules-extra-4.15.0-1027-gcp linux-modules-extra-gcp 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 32.4 MB of archives. After this operation, 171 MB of additional disk space will be used. Get:1 http://ftpmaster.internal/ubuntu xenial-proposed/main amd64 linux-modules-extra-4.15.0-1027-gcp amd64 4.15.0-1027.28~16.04.1 [32.4 MB] Get:2 http://ftpmaster.internal/ubuntu xenial-proposed/main amd64 linux-modules-extra-gcp amd64 4.15.0.1027.41 [2382 B] Fetched 32.4 MB in 1s (17.3 MB/s) Selecting previously unselected package linux-modules-extra-4.15.0-1027-gcp. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 143922 files and directories currently installed.) Preparing to unpack .../linux-modules-extra-4.15.0-1027-gcp_4.15.0-1027.28~16.04.1_amd64.deb ... Unpacking linux-modules-extra-4.15.0-1027-gcp (4.15.0-1027.28~16.04.1) ... Selecting previously unselected package linux-modules-extra-gcp. Preparing to unpack .../linux-modules-extra-gcp_4.15.0.1027.41_amd64.deb ... Unpacking linux-modules-extra-gcp (4.15.0.1027.41) ... Setting up linux-modules-extra-4.15.0-1027-gcp (4.15.0-1027.28~16.04.1) ... Setting up linux-modules-extra-gcp (4.15.0.1027.41) ... Processing triggers for linux-image-4.15.0-1027-gcp (4.15.0-1027.28~16.04.1) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-1027-gcp /etc/kernel/postinst.d/x-grub-legacy-ec2: Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-4.15.0-1027-gcp Found kernel: /boot/vmlinuz-4.4.0-142-generic Found kernel: /boot/vmlinuz-4.4.0-141-generic Found kernel: /boot/vmlinuz-4.15.0-1027-gcp Found kernel: /boot/vmlinuz-4.4.0-142-generic Found kernel: /boot/vmlinuz-4.4.0-141-generic Updating /boot/grub/menu.lst ... done /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.15.0-1027-gcp Found initrd image: /boot/initrd.img-4.15.0-1027-gcp Found linux image: /boot/vmlinuz-4.4.0-142-generic Found initrd image: /boot/initrd.img-4.4.0-142-generic Found linux image: /boot/vmlinuz-4.4.0-141-generic Found initrd image: /boot/initrd.img-4.4.0-141-generic done 07:31:04 ERROR| [stderr] W: --force-yes is deprecated, use one of the options starting with --allow instead. Running '/tmp/autopkgtest.ZyECro/build.HDO/src/autotest/client/tests/ubuntu_zram_smoke_test/ubuntu_zram_smoke_test.sh' PASSED: zram module loaded PASSED: got 1 compression streams PASSED: got lzo lz4 lz4hc 842 compression algorithmns Total of 420 MB free memory Making zram disk of 140 MB PASSED: mkfs.ext4 on ZRAM successful PASSED: ext4 on ZRAM (lzo), memory used: 8391187 4236, file size: 8 MB Total of 420 MB free memory Making zram disk of 140 MB PASSED: mkfs.ext4 on ZRAM successful PASSED: ext4 on ZRAM (lz4), memory used: 8390709 3506, file size: 8 MB Total of 420 MB free memory Making zram disk of 140 MB PASSED: mkfs.ext4 on ZRAM successful PASSED: ext4 on ZRAM (lz4hc), memory used: 8390538 3204, file size: 8 MB Total of 420 MB free memory Making zram disk of 140 MB PASSED: mkfs.ext4 on ZRAM successful PASSED: ext4 on ZRAM (842), memory used: 8390528 3168, file size: 8 MB PASSED: zram module unloaded PASSED: ALL TESTS PASSED: zram module loaded PASSED: got 1 compression streams PASSED: got lzo lz4 lz4hc 842 compression algorithmns Total of 420 MB free memory Making zram disk of 140 MB PASSED: mkfs.ext4 on ZRAM successful PASSED: ext4 on ZRAM (lzo), memory used: 8391187 4236, file size: 8 MB Total of 420 MB free memory Making zram disk of 140 MB PASSED: mkfs.ext4 on ZRAM successful PASSED: ext4 on ZRAM (lz4), memory used: 8390709 3506, file size: 8 MB Total of 420 MB
[Kernel-packages] [Bug 1812822] Re: Guest crashed when detaching the ovs interface device
** Package changed: qemu-kvm (Ubuntu) => qemu (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/1812822 Title: Guest crashed when detaching the ovs interface device Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Bug description: When detaching one openvswitch interface device with virsh detach-device, if the port has been deleted from the ovs and the interface device has been deleted. The virsh detach-device will fail with "error: Unable to read from monitor: Connection reset by peer", the qemu is terminated and the log shows " UNSETVNETLE ioctl() failed, File descriptor in bad state". [Background] This error is originally found from the openstack KVM CI tempest test. By investigating I found it's introduced by one ovs-vif patch, which deletes the ovs port and delete the interface before detaching the device. You can find the commit from https://bugs.launchpad.net/os-vif/+bug/1801072 Reproduced: root@:~# ovs-vsctl del-port br0 tap9273235a-dd root@:~# ip link del tap9273235a-dd The interface device tap9273235a-dd has been removed from the host(ifconfg, ovs-vsctl show) and can be found in the guest.(logon the guest, ip a it's in down state) root@:~# virsh detach-device kvm net.xml error: Failed to detach device from net.xml error: Unable to read from monitor: Connection reset by peer The qemu has terminated and the log in /var/log/libvirt/qemu/kvm.log TUNSETVNETLE ioctl() failed: File descriptor in bad state. 2019-01-18 08:16:11.304+: shutting down, reason=crashed It seems the qemu tried to handle this interface, but in fact it has been deleted. qemu couldn't read the file and give the error. But I don't think the guest should be crashed directly for the file descriptor error. Environment: Ubuntu 16.04.5 LTS Linux (EC12) 4.4.0-141-generic QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5~cloud0) libvirtd (libvirt) 4.0.0 net.xml kvm.xml kvm 59f71b47-16e4-401d-9d33-30bc1605a84a 524288 524288 1 /machine hvm destroy restart destroy /usr/bin/qemu-system-s390x libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a +0:+0 +0:+0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1812822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813663] Re: External monitors does not work anymore 4.15.0-44
I confirm that the newly proposed kernel (4.15.0-45-generic) solves the problem for me too (Dell latitude 5480+WD15 Dock). This closes the bug 1814117, marked as duplicate of this one. That new kernel is now released in the standard ubuntu repository. Thanks a lot! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813663 Title: External monitors does not work anymore 4.15.0-44 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: I am using a docking station for my laptop. After install the 4.15.0-44 update my external monitors goes undetected after logging in or having the laptop closed. I am on 18.04.1 LTS with Intel® HD Graphics 620 (Kaby Lake GT2) Graphics. Going back to the 4.15.0-43 version makes it all work fine again. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonas 2407 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=80397b76-2ded-4f7d-adbf-dfdface8e2d4 InstallationDate: Installed on 2018-10-17 (103 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20HF004MMX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=64cf1582-d574-4e2f-a40a-7942c40caf5d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF004MMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HF004MMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF004MMX dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813881] Re: Kworker process stuck in uninterruptible sleep
** Package changed: linux (Ubuntu) => linux-hwe (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/1813881 Title: Kworker process stuck in uninterruptible sleep Status in linux-hwe package in Ubuntu: Confirmed Bug description: 2019-01-22T09:03:34.968028+00:00 localhost kernel: [80233.315906] INFO: task kworker/u30:3:5705 blocked for more than 120 seconds. 2019-01-22T09:03:34.968049+00:00 localhost kernel: [80233.321444] Tainted: P O 4.15.0-43-generic #46~16.04.1-Ubuntu 2019-01-22T09:03:34.980485+00:00 localhost kernel: [80233.327648] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2019-01-22T09:03:34.980519+00:00 localhost kernel: [80233.333902] kworker/u30:3 D0 5705 2 0x8000 2019-01-22T09:03:34.980521+00:00 localhost kernel: [80233.333909] Workqueue: events_unbound fsnotify_mark_destroy_workfn 2019-01-22T09:03:34.980522+00:00 localhost kernel: [80233.333910] Call Trace: 2019-01-22T09:03:34.980526+00:00 localhost kernel: [80233.333914] __schedule+0x3d6/0x8b0 2019-01-22T09:03:34.980527+00:00 localhost kernel: [80233.333918] schedule+0x36/0x80 2019-01-22T09:03:34.980528+00:00 localhost kernel: [80233.333920] schedule_timeout+0x1db/0x370 2019-01-22T09:03:34.980530+00:00 localhost kernel: [80233.333927] ? __enqueue_entity+0x5c/0x60 2019-01-22T09:03:34.980531+00:00 localhost kernel: [80233.333932] ? enqueue_entity+0x112/0x670 2019-01-22T09:03:34.980547+00:00 localhost kernel: [80233.333937] wait_for_completion+0xb4/0x140 2019-01-22T09:03:34.980554+00:00 localhost kernel: [80233.333939] ? wake_up_q+0x70/0x70 2019-01-22T09:03:34.980556+00:00 localhost kernel: [80233.333944] __synchronize_srcu.part.13+0x85/0xb0 2019-01-22T09:03:34.980557+00:00 localhost kernel: [80233.333947] ? trace_raw_output_rcu_utilization+0x50/0x50 2019-01-22T09:03:34.980558+00:00 localhost kernel: [80233.333950] synchronize_srcu+0xd3/0xe0 2019-01-22T09:03:34.980559+00:00 localhost kernel: [80233.333956] ? synchronize_srcu+0xd3/0xe0 2019-01-22T09:03:34.980560+00:00 localhost kernel: [80233.333962] fsnotify_mark_destroy_workfn+0x7c/0xe0 2019-01-22T09:03:34.980568+00:00 localhost kernel: [80233.333966] process_one_work+0x14d/0x410 2019-01-22T09:03:34.980570+00:00 localhost kernel: [80233.333968] worker_thread+0x22b/0x460 2019-01-22T09:03:34.980571+00:00 localhost kernel: [80233.333971] kthread+0x105/0x140 2019-01-22T09:03:34.980572+00:00 localhost kernel: [80233.333974] ? process_one_work+0x410/0x410 2019-01-22T09:03:34.980573+00:00 localhost kernel: [80233.333976] ? kthread_destroy_worker+0x50/0x50 2019-01-22T09:03:34.980574+00:00 localhost kernel: [80233.333979] ret_from_fork+0x35/0x40 The taint on the kernel is from zfs module. Also there are other processes that reach the same state (D) like dockerd, systemd(init) ... 2019-01-22T09:03:34.949861+00:00 localhost kernel: [80233.299475] INFO: task dockerd:2809 blocked for more than 120 seconds. 2019-01-22T09:03:34.949863+00:00 localhost kernel: [80233.303136] Tainted: P O 4.15.0-43-generic #46~16.04.1-Ubuntu 2019-01-22T09:03:34.962084+00:00 localhost kernel: [80233.309016] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2019-01-22T09:03:34.962114+00:00 localhost kernel: [80233.315513] dockerd D0 2809 1 0x 2019-01-22T09:03:34.962118+00:00 localhost kernel: [80233.315516] Call Trace: 2019-01-22T09:03:34.962120+00:00 localhost kernel: [80233.315521] __schedule+0x3d6/0x8b0 2019-01-22T09:03:34.962122+00:00 localhost kernel: [80233.315528] ? xen_smp_send_reschedule+0x10/0x20 2019-01-22T09:03:34.962137+00:00 localhost kernel: [80233.315532] schedule+0x36/0x80 2019-01-22T09:03:34.962139+00:00 localhost kernel: [80233.315535] schedule_timeout+0x1db/0x370 2019-01-22T09:03:34.962140+00:00 localhost kernel: [80233.315537] ? try_to_wake_up+0x59/0x4a0 2019-01-22T09:03:34.962164+00:00 localhost kernel: [80233.315539] wait_for_completion+0xb4/0x140 2019-01-22T09:03:34.962168+00:00 localhost kernel: [80233.315541] ? wake_up_q+0x70/0x70 2019-01-22T09:03:34.962170+00:00 localhost kernel: [80233.315547] flush_work+0x129/0x1e0 2019-01-22T09:03:34.962171+00:00 localhost kernel: [80233.315552] ? worker_detach_from_pool+0xb0/0xb0 2019-01-22T09:03:34.962186+00:00 localhost kernel: [80233.31] flush_delayed_work+0x3f/0x50 2019-01-22T09:03:34.962194+00:00 localhost kernel: [80233.315559] fsnotify_wait_marks_destroyed+0x15/0x20 2019-01-22T09:03:34.962195+00:00 localhost kernel: [80233.315561] fsnotify_destroy_group+0x48/0xd0 2019-01-22T09:03:34.962196+00:00 localhost kernel: [80233.315563] inotify_release+0x1e/0x50 2019-01-22T09:03:34.962197+00:00 localhost kernel: [80233.315565] __fput+0xea/0x220
[Kernel-packages] [Bug 1813957] Re: T480: closed lid and touchpad
I have just tried with 4.15.0-45-generic and the problem is still there. ** This bug is no longer a duplicate of bug 1813663 External monitors does not work anymore 4.15.0-44 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813957 Title: T480: closed lid and touchpad Status in linux package in Ubuntu: Confirmed Bug description: After closing the lid and working with externals screens and mouse and keyboard, the mouse cursor jumps. The effect is caused by touchpad: the workaround is to completely disable it in settings. This bug is 4.15.0-44 kernel specific. With the previous version 4.15.0-43 the problem was not observed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afiergol 9976 F pulseaudio /dev/snd/pcmC0D0p: afiergol 9976 F...m pulseaudio /dev/snd/controlC0: afiergol 9976 F pulseaudio CurrentDesktop: GNOME Date: Wed Jan 30 17:29:35 2019 HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c InstallationDate: Installed on 2018-04-05 (300 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: LENOVO 20L6S04200 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-22 (161 days ago) dmi.bios.date: 11/07/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET44W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S04200 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S04200 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813713] Re: ubuntu_nbd_smoke_test failed with kernel warning on X-4.15 i386
This is also affecting xenial/linux (only i386 as well): https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190201_082722_4cb3e@/log.gz ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813713 Title: ubuntu_nbd_smoke_test failed with kernel warning on X-4.15 i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux-hwe source package in Xenial: New Status in linux source package in Bionic: New Status in linux-hwe source package in Bionic: Invalid Bug description: Issue found on a i386 SUT with X-4.15 generic / low-latency kernel: creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-12309 Date: Tue Jan 29 06:30:51 UTC 2019 Host: pepe Kernel:4.15.0-43-lowlatency #46~16.04.1-Ubuntu SMP PREEMPT Fri Dec 7 16:13:34 UTC 2018 Machine: pepe i686 i686 CPUs online: 8 CPUs total:8 Page size: 4096 Pages avail: 1824175 Pages total: 2069973 Free space: Filesystem Size Used Avail Use% Mounted on udev4.0G 0 4.0G 0% /dev tmpfs 809M 8.8M 800M 2% /run /dev/sda1 275G 5.8G 255G 3% / tmpfs 4.0G 0 4.0G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 4.0G 0 4.0G 0% /sys/fs/cgroup tmpfs 809M 0 809M 0% /run/user/1000 NBD device /dev/nbd0 created found nbd export NBD exports found: test starting client with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 succeeded after 0 attempt(s) checking ext4 on /dev/nbd0 fsck from util-linux 2.27.1 /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks mount: /dev/nbd0 on /mnt/nbd-test-12309 type ext4 (rw,relatime,data=ordered) mounted on /dev/nbd0 free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 1550112111 2% /mnt/nbd-test-12309 creating large file /mnt/nbd-test-12309/largefile -rw-r--r-- 1 root root 100M Jan 29 06:30 /mnt/nbd-test-12309/largefile free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-12309 removing file /mnt/nbd-test-12309/largefile unmounting /mnt/nbd-test-12309 stopping client disconnect, sock, done Found kernel warning, IO error and/or call trace echo [ 144.498338] creating backing nbd image /tmp/nbd_image.img [ 145.668377] NBD device /dev/nbd0 created [ 145.716876] found nbd export [ 146.760018] starting client with NBD device /dev/nbd0 [ 146.761655] creating ext4 on /dev/nbd0 [ 147.007051] mkfs on /dev/nbd0 succeeded after 0 attempt(s) [ 147.171873] checking ext4 on /dev/nbd0 [ 147.222034] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ 147.226224] mounted on /dev/nbd0 [ 147.227449] creating large file /mnt/nbd-test-12309/largefile [ 147.940687] removing file /mnt/nbd-test-12309/largefile [ 148.007125] unmounting /mnt/nbd-test-12309 [ 149.048638] stopping client [ 149.049176] block nbd0: NBD_DISCONNECT [ 149.049200] block nbd0: shutting down sockets [ 149.049320] nbd0: detected capacity change from 0 to 134217728 [ 149.049346] print_req_error: I/O error, dev nbd0, sector 0 [ 149.055116] Buffer I/O error on dev nbd0, logical block 0, async page read [ 149.062402] print_req_error: I/O error, dev nbd0, sector 0 [ 149.068078] Buffer I/O error on dev nbd0, logical block 0, async page read [ 149.075363] print_req_error: I/O error, dev nbd0, sector 0 [ 149.080923] Buffer I/O error on dev nbd0, logical block 0, async page read [ 149.087847] ldm_validate_partition_table(): Disk read failed. [ 149.087861]
[Kernel-packages] [Bug 1811252] Re: Xenial update: 4.4.169 upstream stable release
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811252
Title:
Xenial update: 4.4.169 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.4.169 upstream stable release
from git://git.kernel.org/
Linux 4.4.169
ALSA: isa/wavefront: prevent some out of bound writes
rtc: snvs: Add timeouts to avoid kernel lockups
rtc: snvs: add a missing write sync
i2c: scmi: Fix probe error on devices with an empty SMB0001 ACPI device node
i2c: axxia: properly handle master timeout
cifs: In Kconfig CONFIG_CIFS_POSIX needs depends on legacy (insecure cifs)
ARM: 8814/1: mm: improve/fix ARM v7_dma_inv_range() unaligned address handling
mv88e6060: disable hardware level MAC learning
libata: whitelist all SAMSUNG MZ7KM* solid-state disks
Input: omap-keypad - fix keyboard debounce configuration
clk: mmp: Off by one in mmp_clk_add()
ide: pmac: add of_node_put()
drivers/tty: add missing of_node_put()
drivers/sbus/char: add of_node_put()
sbus: char: add of_node_put()
SUNRPC: Fix a potential race in xprt_connect()
bonding: fix 802.3ad state sent to partner when unbinding slave
ARC: io.h: Implement reads{x}()/writes{x}()
drm/msm: Grab a vblank reference when waiting for commit_done
x86/earlyprintk/efi: Fix infinite loop on some screen widths
scsi: vmw_pscsi: Rearrange code to avoid multiple calls to free_irq during
unload
scsi: libiscsi: Fix NULL pointer dereference in iscsi_eh_session_reset
mac80211_hwsim: fix module init error paths for netlink
mac80211: Fix condition validating WMM IE
mac80211: don't WARN on bad WMM parameters from buggy APs
f2fs: fix a panic caused by NULL flush_cmd_control
Revert "drm/rockchip: Allow driver to be shutdown on reboot/kexec"
powerpc/msi: Fix NULL pointer access in teardown code
tracing: Fix memory leak of instance function hash filters
tracing: Fix memory leak in set_trigger_filter()
MMC: OMAP: fix broken MMC on OMAP15XX/OMAP5910/OMAP310
aio: fix spectre gadget in lookup_ioctx
pinctrl: sunxi: a83t: Fix IRQ offset typo for PH11
powerpc/boot: Fix random libfdt related build errors
timer/debug: Change /proc/timer_list from 0444 to 0400
lib/interval_tree_test.c: allow users to limit scope of endpoint
lib/rbtree-test: lower default params
lib/rbtree_test.c: make input module parameters
lib/interval_tree_test.c: allow full tree search
lib/interval_tree_test.c: make test options module parameters
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811252/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813663] Re: External monitors does not work anymore 4.15.0-44
I just got the 4.15.0-45 kernel through normal updates. Am I the only one who sees it as problematic that when updating to 4.15.0-45, it marks both 4.15.0-43 and 4.15.0-44 for auto removal? Of course 44 should go, because it's problematic, but what if someone ends up without a prior kernel to boot in case of trouble with 45? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813663 Title: External monitors does not work anymore 4.15.0-44 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: I am using a docking station for my laptop. After install the 4.15.0-44 update my external monitors goes undetected after logging in or having the laptop closed. I am on 18.04.1 LTS with Intel® HD Graphics 620 (Kaby Lake GT2) Graphics. Going back to the 4.15.0-43 version makes it all work fine again. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonas 2407 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=80397b76-2ded-4f7d-adbf-dfdface8e2d4 InstallationDate: Installed on 2018-10-17 (103 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20HF004MMX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=64cf1582-d574-4e2f-a40a-7942c40caf5d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF004MMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HF004MMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF004MMX dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814240] [NEW] ubuntu_zfs_xfs_generic 129 timeouted on node gonzo with X-4.15
Public bug reported: Kernel: 4.15.0-45.48~16.04.1 Test 129 timeouted (20 min) on node gonzo, and all the following 30 tests have failed too. 1. 01/31 15:53:20 INFO |ubuntu_zfs:0134| Running: /home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh 129 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src 2. 01/31 15:53:20 DEBUG| utils:0116| Running '/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh 129 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src' 3. 01/31 15:53:20 DEBUG| utils:0153| [stdout] Creating zfs pool testpool.. 4. 01/31 15:53:23 DEBUG| utils:0153| [stdout] Creating zfs file systems test and scratch in testpool.. 5. 01/31 15:53:25 DEBUG| utils:0153| [stdout] VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src 6. 01/31 15:53:25 DEBUG| utils:0153| [stdout] FSTYP -- zfs 7. 01/31 15:53:25 DEBUG| utils:0153| [stdout] PLATFORM -- Linux/x86_64 gonzo 4.15.0-45-generic 8. 01/31 15:53:25 DEBUG| utils:0153| [stdout] MKFS_OPTIONS -- testpool/scratch 9. 01/31 15:53:25 DEBUG| utils:0153| [stdout] MOUNT_OPTIONS -- testpool/scratch /mnt/scratch 10. 01/31 15:53:25 DEBUG| utils:0153| [stdout] I didn't see this issue in 4.15.0-44.47~16.04.1, but this test was not run with gonzo back then ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814240 Title: ubuntu_zfs_xfs_generic 129 timeouted on node gonzo with X-4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: Kernel: 4.15.0-45.48~16.04.1 Test 129 timeouted (20 min) on node gonzo, and all the following 30 tests have failed too. 1.01/31 15:53:20 INFO |ubuntu_zfs:0134| Running: /home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh 129 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src 2.01/31 15:53:20 DEBUG| utils:0116| Running '/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh 129 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src' 3.01/31 15:53:20 DEBUG| utils:0153| [stdout] Creating zfs pool testpool.. 4.01/31 15:53:23 DEBUG| utils:0153| [stdout] Creating zfs file systems test and scratch in testpool.. 5.01/31 15:53:25 DEBUG| utils:0153| [stdout] VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src 6.01/31 15:53:25 DEBUG| utils:0153| [stdout] FSTYP -- zfs 7.01/31 15:53:25 DEBUG| utils:0153| [stdout] PLATFORM -- Linux/x86_64 gonzo 4.15.0-45-generic 8.01/31 15:53:25 DEBUG| utils:0153| [stdout] MKFS_OPTIONS -- testpool/scratch 9.01/31 15:53:25 DEBUG| utils:0153| [stdout] MOUNT_OPTIONS -- testpool/scratch /mnt/scratch 10. 01/31 15:53:25 DEBUG| utils:0153| [stdout] I didn't see this issue in 4.15.0-44.47~16.04.1, but this test was not run with gonzo back then To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814237] Re: ubuntu_nbd_smoke_test failed with I/O error on X-4.15
Can we re-run this to see if it's 100% reproduceable? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814237 Title: ubuntu_nbd_smoke_test failed with I/O error on X-4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: Kernel: 4.15.0-45.48~16.04.1 creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-25789 Date: Thu Jan 31 14:42:42 UTC 2019 Host: onibi Kernel:4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 Machine: onibi x86_64 x86_64 CPUs online: 4 CPUs total:4 Page size: 4096 Pages avail: 1351388 Pages total: 2038431 Free space: Filesystem Size Used Avail Use% Mounted on udev3.9G 0 3.9G 0% /dev tmpfs 797M 17M 780M 3% /run /dev/sda1 917G 9.1G 861G 2% / tmpfs 3.9G 4.0K 3.9G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 797M 0 797M 0% /run/user/1000 tmpfs 100K 0 100K 0% /var/lib/lxd/shmounts tmpfs 100K 0 100K 0% /var/lib/lxd/devlxd cgmfs 100K 0 100K 0% /run/cgmanager/fs NBD device /dev/nbd0 created found nbd export NBD exports found: test starting client with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 succeeded after 0 attempt(s) checking ext4 on /dev/nbd0 fsck from util-linux 2.27.1 /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks mount: /dev/nbd0 on /mnt/nbd-test-25789 type ext4 (rw,relatime,data=ordered) mounted on /dev/nbd0 free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 1550112111 2% /mnt/nbd-test-25789 creating large file /mnt/nbd-test-25789/largefile -rw-r--r-- 1 root root 100M Jan 31 14:42 /mnt/nbd-test-25789/largefile free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-25789 removing file /mnt/nbd-test-25789/largefile unmounting /mnt/nbd-test-25789 stopping client disconnect, sock, done Found kernel warning, IO error and/or call trace echo [ 4593.254552] creating backing nbd image /tmp/nbd_image.img [ 4595.506134] NBD device /dev/nbd0 created [ 4595.557990] found nbd export [ 4596.604855] starting client with NBD device /dev/nbd0 [ 4596.606795] creating ext4 on /dev/nbd0 [ 4597.013721] mkfs on /dev/nbd0 succeeded after 0 attempt(s) [ 4597.390241] checking ext4 on /dev/nbd0 [ 4597.455371] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ 4597.460552] mounted on /dev/nbd0 [ 4597.461810] creating large file /mnt/nbd-test-25789/largefile [ 4599.056704] removing file /mnt/nbd-test-25789/largefile [ 4599.276298] unmounting /mnt/nbd-test-25789 [ 4600.319460] stopping client [ 4600.320083] block nbd0: NBD_DISCONNECT [ 4600.320127] block nbd0: shutting down sockets [ 4600.320267] nbd0: detected capacity change from 0 to 134217728 [ 4600.320306] print_req_error: 7 callbacks suppressed [ 4600.320308] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.325890] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.333002] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.338653] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.345687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.351253] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.358279] ldm_validate_partition_table(): Disk read failed. [ 4600.358305] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.363892] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.371075] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.376645] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.383687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.389230] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.396307] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.401819] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.408826] Dev nbd0: unable to read RDB block 0 [ 4600.413467] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.418955] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.425858] print_req_error: I/O error, dev nbd0, sector 24 [ 4600.431433] Buffer I/O error on dev nbd0, logical block 3, async page read [ 4600.438422] print_req_error: I/O error,
[Kernel-packages] [Bug 1814241] [NEW] linux-oem: -proposed tracker
Public bug reported: 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: 1814239 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.01.14-2 kernel-sru-derivative-of-1813779 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in:
[Kernel-packages] [Bug 1811421] Re: linux-oem: 4.15.0-1032.37 -proposed tracker
*** This bug is a duplicate of bug 1814241 *** https://bugs.launchpad.net/bugs/1814241 ** This bug has been marked a duplicate of bug 1814241 linux-oem: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1811421 Title: linux-oem: 4.15.0-1032.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1813779 phase: Testing phase-changed: Monday, 28. January 2019 12:58 UTC reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814239] [NEW] linux: -proposed tracker
Public bug reported: 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: bug 1814241 (linux-oem) ** Affects: kernel-sru-workflow Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: Invalid ** Affects: kernel-sru-workflow/snap-certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-sru-cycle-2019.01.04-2 kernel-sru-master-kernel ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status:
[Kernel-packages] [Bug 1814237] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1814237 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814237 Title: ubuntu_nbd_smoke_test failed with I/O error on X-4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Kernel: 4.15.0-45.48~16.04.1 creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-25789 Date: Thu Jan 31 14:42:42 UTC 2019 Host: onibi Kernel:4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 Machine: onibi x86_64 x86_64 CPUs online: 4 CPUs total:4 Page size: 4096 Pages avail: 1351388 Pages total: 2038431 Free space: Filesystem Size Used Avail Use% Mounted on udev3.9G 0 3.9G 0% /dev tmpfs 797M 17M 780M 3% /run /dev/sda1 917G 9.1G 861G 2% / tmpfs 3.9G 4.0K 3.9G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 797M 0 797M 0% /run/user/1000 tmpfs 100K 0 100K 0% /var/lib/lxd/shmounts tmpfs 100K 0 100K 0% /var/lib/lxd/devlxd cgmfs 100K 0 100K 0% /run/cgmanager/fs NBD device /dev/nbd0 created found nbd export NBD exports found: test starting client with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 succeeded after 0 attempt(s) checking ext4 on /dev/nbd0 fsck from util-linux 2.27.1 /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks mount: /dev/nbd0 on /mnt/nbd-test-25789 type ext4 (rw,relatime,data=ordered) mounted on /dev/nbd0 free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 1550112111 2% /mnt/nbd-test-25789 creating large file /mnt/nbd-test-25789/largefile -rw-r--r-- 1 root root 100M Jan 31 14:42 /mnt/nbd-test-25789/largefile free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-25789 removing file /mnt/nbd-test-25789/largefile unmounting /mnt/nbd-test-25789 stopping client disconnect, sock, done Found kernel warning, IO error and/or call trace echo [ 4593.254552] creating backing nbd image /tmp/nbd_image.img [ 4595.506134] NBD device /dev/nbd0 created [ 4595.557990] found nbd export [ 4596.604855] starting client with NBD device /dev/nbd0 [ 4596.606795] creating ext4 on /dev/nbd0 [ 4597.013721] mkfs on /dev/nbd0 succeeded after 0 attempt(s) [ 4597.390241] checking ext4 on /dev/nbd0 [ 4597.455371] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ 4597.460552] mounted on /dev/nbd0 [ 4597.461810] creating large file /mnt/nbd-test-25789/largefile [ 4599.056704] removing file /mnt/nbd-test-25789/largefile [ 4599.276298] unmounting /mnt/nbd-test-25789 [ 4600.319460] stopping client [ 4600.320083] block nbd0: NBD_DISCONNECT [ 4600.320127] block nbd0: shutting down sockets [ 4600.320267] nbd0: detected capacity change from 0 to 134217728 [ 4600.320306] print_req_error: 7 callbacks suppressed [ 4600.320308] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.325890] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.333002] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.338653] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.345687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.351253] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.358279] ldm_validate_partition_table(): Disk read failed. [ 4600.358305] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.363892] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.371075] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.376645] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.383687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.389230] Buffer I/O
[Kernel-packages] [Bug 1814240] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1814240 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814240 Title: ubuntu_zfs_xfs_generic 129 timeouted on node gonzo with X-4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Kernel: 4.15.0-45.48~16.04.1 Test 129 timeouted (20 min) on node gonzo, and all the following 30 tests have failed too. 1.01/31 15:53:20 INFO |ubuntu_zfs:0134| Running: /home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh 129 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src 2.01/31 15:53:20 DEBUG| utils:0116| Running '/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh 129 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src' 3.01/31 15:53:20 DEBUG| utils:0153| [stdout] Creating zfs pool testpool.. 4.01/31 15:53:23 DEBUG| utils:0153| [stdout] Creating zfs file systems test and scratch in testpool.. 5.01/31 15:53:25 DEBUG| utils:0153| [stdout] VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src 6.01/31 15:53:25 DEBUG| utils:0153| [stdout] FSTYP -- zfs 7.01/31 15:53:25 DEBUG| utils:0153| [stdout] PLATFORM -- Linux/x86_64 gonzo 4.15.0-45-generic 8.01/31 15:53:25 DEBUG| utils:0153| [stdout] MKFS_OPTIONS -- testpool/scratch 9.01/31 15:53:25 DEBUG| utils:0153| [stdout] MOUNT_OPTIONS -- testpool/scratch /mnt/scratch 10. 01/31 15:53:25 DEBUG| utils:0153| [stdout] I didn't see this issue in 4.15.0-44.47~16.04.1, but this test was not run with gonzo back then To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814241] Re: linux-oem: -proposed tracker
** Tags removed: kernel-sru-derivative-of-1814239 ** Tags added: kernel-sru-derivative-of-1813779 ** 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: 1814239 + kernel-stable-master-bug: 1813779 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1814241 Title: linux-oem: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-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-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1813779 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker
*** This bug is a duplicate of bug 1814241 *** https://bugs.launchpad.net/bugs/1814241 ** This bug is no longer a duplicate of bug 1811421 linux-oem: 4.15.0-1032.37 -proposed tracker ** This bug has been marked a duplicate of bug 1814241 linux-oem: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1810370 Title: linux-oem: 4.15.0-1031.36 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1806659 phase: Testing -- automated-testing FAILED phase-changed: Wednesday, 09. January 2019 14:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1810370/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device
I see that the verification-done-cosmic tag has been set, I'll also set the verification-done tag too ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1803360 Title: Fanless systems with DPTF shutdown before using any passive cooling device Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Xenial: Won't Fix Status in thermald source package in Bionic: Fix Released Status in thermald source package in Cosmic: Fix Committed Status in thermald source package in Disco: Fix Released Bug description: == SRU Justification, Cosmic, Bionic, Xenial == There are some new fanless platforms use DPTF's virtual sensor instead of INT340X devices. Because of that, the _PSV is no longer in use, at least not directly, hence its value may set higher then _CRT. To a fanless system that means no cooling device gets activated before _CRT, so the system will be considered overheated by Linux kernel, and gets shutdown by the kernel. == Fix == Upstream fix https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9 == Testing == Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and try and reach the trip point. Without the fix thermal overrun occurs and this trips CPU shutdown. With the fix, thermald will start to throttle the system and get it out of the thermal overrun zone. == Regression Potential == This modifies the behavior for just INT340X devices with ACPI _CRT objects, specifically, now to honor this setting. This is a small subset of devices with these objects and the change will in face make thermald catch systems before they hit thermal overrun, so the risk of regression is small. This fix also has been reviewed by the thermal experts at Intel, so it seems like a very reasonable workaround for these specific use cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811080] Re: Xenial update: 4.4.168 upstream stable release
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811080
Title:
Xenial update: 4.4.168 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.4.168 upstream stable release
from git://git.kernel.org/
Linux 4.4.168
selftests: Move networking/timestamping from Documentation
rocker: fix rocker_tlv_put_* functions for KASAN
staging: speakup: Replace strncpy with memcpy
matroxfb: fix size of memcpy
media: dvb-frontends: fix i2c access helpers for KASAN
proc: do not access cmdline nor environ from file-backed areas
proc: don't use FOLL_FORCE for reading cmdline and environment
mm: replace access_remote_vm() write parameter with gup_flags
mm: replace __access_remote_vm() write parameter with gup_flags
mm: replace get_user_pages() write/force parameters with gup_flags
mm: replace get_vaddr_frames() write/force parameters with gup_flags
mm: replace get_user_pages_locked() write/force parameters with gup_flags
mm: replace get_user_pages_unlocked() write/force parameters with gup_flags
mm/nommu.c: Switch __get_user_pages_unlocked() to use __get_user_pages()
mm: remove write/force parameters from __get_user_pages_unlocked()
mm: remove write/force parameters from __get_user_pages_locked()
sr: pass down correctly sized SCSI sense buffer
swiotlb: clean up reporting
hugetlbfs: fix bug in pgoff overflow checking
hugetlbfs: check for pgoff value overflow
hugetlbfs: fix offset overflow in hugetlbfs mmap
mm/hugetlb.c: don't call region_abort if region_chg fails
posix-timers: Sanitize overrun handling
wil6210: missing length check in wmi_set_ie
bpf: Prevent memory disambiguation attack
bpf/verifier: Pass instruction index to check_mem_access() and check_xadd()
bpf/verifier: Add spi variable to check_stack_write()
bpf: support 8-byte metafield access
KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
KVM: SVM: Move spec control call after restore of GS
x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest
x86/bugs, KVM: Support the combination of guest and host IBRS
x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
x86: fix SMAP in 32-bit environments
x86: reorganize SMAP handling in user space accesses
KVM/x86: Remove indirect MSR op calls from SPEC_CTRL
KVM/SVM: Allow direct access to MSR_IA32_SPEC_CTRL
KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL
KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES
KVM/x86: Add IBPB support
KVM: VMX: make MSR bitmaps per-VCPU
KVM: VMX: introduce alloc_loaded_vmcs
KVM: nVMX: Eliminate vmcs02 pool
KVM: nVMX: mark vmcs12 pages dirty on L2 exit
KVM: nVMX: fix msr bitmaps to prevent L2 from accessing L0 x2APIC
ALSA: pcm: remove SNDRV_PCM_IOCTL1_INFO internal command
pstore: Convert console write to use ->write_buf
ocfs2: fix potential use after free
debugobjects: avoid recursive calls with kmemleak
hfsplus: do not free node before using
hfs: do not free node before using
ocfs2: fix deadlock caused by ocfs2_defrag_extent()
fscache, cachefiles: remove redundant variable 'cache'
fscache: fix race between enablement and dropping of object
xen: xlate_mmu: add missing header to fix 'W=1' warning
drm/ast: fixed reading monitor EDID not stable issue
net: hisilicon: remove unexpected free_netdev
ixgbe: recognize 1000BaseLX SFP modules as 1Gbps
net: thunderx: fix NULL pointer dereference in nic_remove
KVM: x86: fix empty-body warnings
USB: omap_udc: fix USB gadget functionality on Palm Tungsten E
USB: omap_udc: fix omap_udc_start() on 15xx machines
USB: omap_udc: fix crashes on probe error and module removal
USB: omap_udc: use devm_request_irq()
bpf: fix check of allowed specifiers in bpf_trace_printk
exportfs: do not read dentry after free
ASoC: omap-dmic: Add pm_qos handling to avoid overruns with CPU_IDLE
ASoC: omap-mcpdm: Add pm_qos handling to avoid under/overruns with CPU_IDLE
Btrfs: send, fix infinite loop due to directory rename
[Kernel-packages] [Bug 1799139] Re: linux 4.15.0-38.41 ADT test failure (ubuntu_nbd_smoke_test)
*** This bug is a duplicate of bug 1813713 *** https://bugs.launchpad.net/bugs/1813713 ** This bug has been marked a duplicate of bug 1813713 ubuntu_nbd_smoke_test failed with kernel warning on X-4.15 i386 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799139 Title: linux 4.15.0-38.41 ADT test failure (ubuntu_nbd_smoke_test) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20181019_194651_d42a8@/log.gz The ubuntu_nbd_smoke_test testcase is hitting the following kernel bug: 16:02:03 DEBUG| [stdout] [ 6587.920070] [ cut here ] 16:02:03 DEBUG| [stdout] [ 6587.975274] kernel BUG at /build/linux-aTHL1U/linux-4.15.0/fs/buffer.c:3064! 16:02:03 DEBUG| [stdout] [ 6587.976968] invalid opcode: [#2] SMP 16:02:03 DEBUG| [stdout] [ 6587.977880] Modules linked in: nbd 842 842_decompress 842_compress lz4hc lz4hc_compress lz4 lz4_compress unix_diag binfmt_misc cuse uhid hid vfio_iommu_type1 vfio hci_vhci bluetooth ecdh_generic vhost_net tap vhost_vsock vmw_vsock_virtio_transport_common vhost vsock snd_seq snd_seq_device snd_timer snd soundcore userio dccp_ipv4 algif_rng salsa20_generic salsa20_i586 camellia_generic cast6_generic cast_common serpent_sse2_i586 serpent_generic glue_helper ablk_helper twofish_generic twofish_i586 twofish_common lrw algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg aufs macsec vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip_gre ip_tunnel gre cls_u32 sch_htb dummy af_packet_diag sctp_diag sctp libcrc32c dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag 16:02:03 DEBUG| [stdout] [ 6587.994265] xt_TCPMSS xt_tcpudp iptable_mangle kvm_intel kvm irqbypass crc32_pclmul pcbc aesni_intel aes_i586 crypto_simd cryptd joydev input_leds mac_hid qemu_fw_cfg serio_raw sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq psmouse i2c_piix4 virtio_net virtio_blk pata_acpi floppy [last unloaded: zram] 16:02:03 DEBUG| [stdout] [ 6588.000720] CPU: 3 PID: 3794 Comm: kworker/u8:1 Tainted: G D W OE4.15.0-38-generic #41-Ubuntu 16:02:03 DEBUG| [stdout] [ 6588.002806] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 16:02:03 DEBUG| [stdout] [ 6588.004941] Workqueue: writeback wb_workfn (flush-43:0) 16:02:03 DEBUG| [stdout] [ 6588.006119] EIP: submit_bh_wbc+0x168/0x190 16:02:03 DEBUG| [stdout] [ 6588.007052] EFLAGS: 00010246 CPU: 3 16:02:03 DEBUG| [stdout] [ 6588.007846] EAX: 00620005 EBX: ce002cb0 ECX: ce002cb0 EDX: 00020800 16:02:03 DEBUG| [stdout] [ 6588.009251] ESI: 00020800 EDI: db34e400 EBP: d054bc3c ESP: d054bc2c 16:02:03 DEBUG| [stdout] [ 6588.010656] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 16:02:03 DEBUG| [stdout] [ 6588.011876] CR0: 80050033 CR2: b7f29e44 CR3: 1de14000 CR4: 001406f0 16:02:03 DEBUG| [stdout] [ 6588.013286] Call Trace: 16:02:03 DEBUG| [stdout] [ 6588.013886] __sync_dirty_buffer+0x4d/0xf0 16:02:03 DEBUG| [stdout] [ 6588.014824] ext4_commit_super+0x1e2/0x290 16:02:03 DEBUG| [stdout] [ 6588.015767] __ext4_abort+0x4a/0x120 16:02:03 DEBUG| [stdout] [ 6588.016588] ext4_journal_check_start+0x81/0x90 16:02:03 DEBUG| [stdout] [ 6588.017611] __ext4_journal_start_sb+0x28/0xd0 16:02:03 DEBUG| [stdout] [ 6588.018622] ? ext4_writepages+0x4d4/0x880 16:02:03 DEBUG| [stdout] [ 6588.045547] ext4_writepages+0x4d4/0x880 16:02:03 DEBUG| [stdout] [ 6588.046460] ? blk_mq_dispatch_rq_list+0x74/0x440 16:02:03 DEBUG| [stdout] [ 6588.047552] do_writepages+0x39/0xc0 16:02:03 DEBUG| [stdout] [ 6588.048367] ? blk_mq_sched_dispatch_requests+0x184/0x190 16:02:03 DEBUG| [stdout] [ 6588.049579] __writeback_single_inode+0x3a/0x310 16:02:03 DEBUG| [stdout] [ 6588.050623] writeback_sb_inodes+0x167/0x3a0 16:02:03 DEBUG| [stdout] [ 6588.051601] __writeback_inodes_wb+0x55/0xa0 16:02:03 DEBUG| [stdout] [ 6588.052568] wb_writeback+0x20a/0x2a0 16:02:03 DEBUG| [stdout] [ 6588.053411] ? find_next_bit+0xa/0x10 16:02:03 DEBUG| [stdout] [ 6588.054246] wb_workfn+0x313/0x430 16:02:03 DEBUG| [stdout] [ 6588.055051] ? __switch_to_asm+0x27/0x4c 16:02:03 DEBUG| [stdout] [ 6588.055961] ? __switch_to+0xae/0x360 16:02:03 DEBUG| [stdout] [ 6588.056795] ? __switch_to_asm+0x33/0x4c 16:02:03 DEBUG| [stdout] [ 6588.057685] ? __switch_to_asm+0x27/0x4c 16:02:03 DEBUG| [stdout] [ 6588.058597] process_one_work+0x1b9/0x3d0 16:02:03 DEBUG| [stdout] [ 6588.059514] worker_thread+0x37/0x420 16:02:03 DEBUG| [stdout] [ 6588.060345] kthread+0xf0/0x110 16:02:03 DEBUG| [stdout] [ 6588.061064] ?
[Kernel-packages] [Bug 1814237] [NEW] ubuntu_nbd_smoke_test failed with I/O error on X-4.15
Public bug reported: Kernel: 4.15.0-45.48~16.04.1 creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-25789 Date: Thu Jan 31 14:42:42 UTC 2019 Host: onibi Kernel:4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 Machine: onibi x86_64 x86_64 CPUs online: 4 CPUs total:4 Page size: 4096 Pages avail: 1351388 Pages total: 2038431 Free space: Filesystem Size Used Avail Use% Mounted on udev3.9G 0 3.9G 0% /dev tmpfs 797M 17M 780M 3% /run /dev/sda1 917G 9.1G 861G 2% / tmpfs 3.9G 4.0K 3.9G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 797M 0 797M 0% /run/user/1000 tmpfs 100K 0 100K 0% /var/lib/lxd/shmounts tmpfs 100K 0 100K 0% /var/lib/lxd/devlxd cgmfs 100K 0 100K 0% /run/cgmanager/fs NBD device /dev/nbd0 created found nbd export NBD exports found: test starting client with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 succeeded after 0 attempt(s) checking ext4 on /dev/nbd0 fsck from util-linux 2.27.1 /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks mount: /dev/nbd0 on /mnt/nbd-test-25789 type ext4 (rw,relatime,data=ordered) mounted on /dev/nbd0 free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 1550112111 2% /mnt/nbd-test-25789 creating large file /mnt/nbd-test-25789/largefile -rw-r--r-- 1 root root 100M Jan 31 14:42 /mnt/nbd-test-25789/largefile free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-25789 removing file /mnt/nbd-test-25789/largefile unmounting /mnt/nbd-test-25789 stopping client disconnect, sock, done Found kernel warning, IO error and/or call trace echo [ 4593.254552] creating backing nbd image /tmp/nbd_image.img [ 4595.506134] NBD device /dev/nbd0 created [ 4595.557990] found nbd export [ 4596.604855] starting client with NBD device /dev/nbd0 [ 4596.606795] creating ext4 on /dev/nbd0 [ 4597.013721] mkfs on /dev/nbd0 succeeded after 0 attempt(s) [ 4597.390241] checking ext4 on /dev/nbd0 [ 4597.455371] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ 4597.460552] mounted on /dev/nbd0 [ 4597.461810] creating large file /mnt/nbd-test-25789/largefile [ 4599.056704] removing file /mnt/nbd-test-25789/largefile [ 4599.276298] unmounting /mnt/nbd-test-25789 [ 4600.319460] stopping client [ 4600.320083] block nbd0: NBD_DISCONNECT [ 4600.320127] block nbd0: shutting down sockets [ 4600.320267] nbd0: detected capacity change from 0 to 134217728 [ 4600.320306] print_req_error: 7 callbacks suppressed [ 4600.320308] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.325890] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.333002] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.338653] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.345687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.351253] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.358279] ldm_validate_partition_table(): Disk read failed. [ 4600.358305] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.363892] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.371075] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.376645] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.383687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.389230] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.396307] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.401819] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.408826] Dev nbd0: unable to read RDB block 0 [ 4600.413467] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.418955] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.425858] print_req_error: I/O error, dev nbd0, sector 24 [ 4600.431433] Buffer I/O error on dev nbd0, logical block 3, async page read [ 4600.438422] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.443995] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.451003] nbd0: unable to read partition table [ 4600.584152] Found kernel warning, IO error and/or call trace [ 4600.584201] echo killing server Completed Kernel issues: Found kernel warning, IO error and/or call trace: TEST: [ 4593.254552] creating backing nbd image /tmp/nbd_image.img [ 4595.506134] NBD device /dev/nbd0 created [ 4595.557990] found nbd
[Kernel-packages] [Bug 1814237] Re: ubuntu_nbd_smoke_test failed with I/O error on X-4.15
I can see this test has passed with 4.15.0-44.47~16.04.1, so this might be a regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814237 Title: ubuntu_nbd_smoke_test failed with I/O error on X-4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: Kernel: 4.15.0-45.48~16.04.1 creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-25789 Date: Thu Jan 31 14:42:42 UTC 2019 Host: onibi Kernel:4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 Machine: onibi x86_64 x86_64 CPUs online: 4 CPUs total:4 Page size: 4096 Pages avail: 1351388 Pages total: 2038431 Free space: Filesystem Size Used Avail Use% Mounted on udev3.9G 0 3.9G 0% /dev tmpfs 797M 17M 780M 3% /run /dev/sda1 917G 9.1G 861G 2% / tmpfs 3.9G 4.0K 3.9G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 797M 0 797M 0% /run/user/1000 tmpfs 100K 0 100K 0% /var/lib/lxd/shmounts tmpfs 100K 0 100K 0% /var/lib/lxd/devlxd cgmfs 100K 0 100K 0% /run/cgmanager/fs NBD device /dev/nbd0 created found nbd export NBD exports found: test starting client with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 succeeded after 0 attempt(s) checking ext4 on /dev/nbd0 fsck from util-linux 2.27.1 /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks mount: /dev/nbd0 on /mnt/nbd-test-25789 type ext4 (rw,relatime,data=ordered) mounted on /dev/nbd0 free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 1550112111 2% /mnt/nbd-test-25789 creating large file /mnt/nbd-test-25789/largefile -rw-r--r-- 1 root root 100M Jan 31 14:42 /mnt/nbd-test-25789/largefile free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-25789 removing file /mnt/nbd-test-25789/largefile unmounting /mnt/nbd-test-25789 stopping client disconnect, sock, done Found kernel warning, IO error and/or call trace echo [ 4593.254552] creating backing nbd image /tmp/nbd_image.img [ 4595.506134] NBD device /dev/nbd0 created [ 4595.557990] found nbd export [ 4596.604855] starting client with NBD device /dev/nbd0 [ 4596.606795] creating ext4 on /dev/nbd0 [ 4597.013721] mkfs on /dev/nbd0 succeeded after 0 attempt(s) [ 4597.390241] checking ext4 on /dev/nbd0 [ 4597.455371] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ 4597.460552] mounted on /dev/nbd0 [ 4597.461810] creating large file /mnt/nbd-test-25789/largefile [ 4599.056704] removing file /mnt/nbd-test-25789/largefile [ 4599.276298] unmounting /mnt/nbd-test-25789 [ 4600.319460] stopping client [ 4600.320083] block nbd0: NBD_DISCONNECT [ 4600.320127] block nbd0: shutting down sockets [ 4600.320267] nbd0: detected capacity change from 0 to 134217728 [ 4600.320306] print_req_error: 7 callbacks suppressed [ 4600.320308] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.325890] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.333002] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.338653] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.345687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.351253] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.358279] ldm_validate_partition_table(): Disk read failed. [ 4600.358305] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.363892] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.371075] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.376645] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.383687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.389230] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.396307] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.401819] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.408826] Dev nbd0: unable to read RDB block 0 [ 4600.413467] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.418955] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.425858] print_req_error: I/O error, dev nbd0, sector 24 [ 4600.431433] Buffer I/O error on dev nbd0, logical block 3, async page read [
[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed
Thanks again Christopher! I could not send the email though, the email address "linux-...@vger.linux.org" seems invalid. Any ideas? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812561 Title: [MacBookPro11,5] wakes up and suspends in a loop while closed Status in linux package in Ubuntu: Triaged Bug description: Similar bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/ The first time suspending works great but after that suspending causes the laptop to wake up regardless of the method used to suspend. WORKAROUND: Disable XHC1 prior to sleeping via: # echo XHC1 > /proc/acpi/wakeup Sidenote: thanks to penalvch for explaining how to report this! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: siilwyn1852 F pulseaudio /dev/snd/controlC1: siilwyn1852 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 13:40:14 2019 InstallationDate: Installed on 2019-01-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814241] Re: linux-oem: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1813779 + phase: Packaging + phase-changed: Friday, 01. February 2019 10:39 UTC + reason: + prepare-package: Pending -- version not specified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1814241 Title: linux-oem: 4.15.0-1033.38 -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: 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 upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1813779 phase: Packaging phase-changed: Friday, 01. February 2019 10:39 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811429] Re: linux-azure: 4.15.0-1037.39~14.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: 1813779 - phase: Testing - phase-changed: Monday, 28. January 2019 11:52 UTC + phase: Release Holding + phase-changed: Friday, 01. February 2019 10:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811429 Title: linux-azure: 4.15.0-1037.39~14.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu 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 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Release Holding phase-changed: Friday, 01. February 2019 10:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811420] Re: linux-raspi2: 4.15.0-1031.33 -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: 1813779 - phase: Testing - phase-changed: Monday, 28. January 2019 12:00 UTC + phase: Release Holding + phase-changed: Friday, 01. February 2019 10:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1811420 Title: linux-raspi2: 4.15.0-1031.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released 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-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1813779 phase: Release Holding phase-changed: Friday, 01. February 2019 10:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811856] Re: linux: 3.13.0-165.215 -proposed tracker
3.13.0-165.215 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_btrfs_kernel_fixes - 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22 hang (bug 1809879) ubuntu_kvm_smoke_test - Unable to start KVM, timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - 46 failed on onibi, 39 failed on KVM nodes ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fremovexattr01, fremovexattr02, fsync01, msync04, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) fcntl35 / fcntl35_64 (bug 1774394) fanotify06 (bug 1775378) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 (bug 1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107) keyctl02 (bug 1798022) keyctl06 (bug 1798025) openat03 (bug 1798027) request_key03 (bug 1798052) ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack (bug 1813001) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) libhugetlbfs - noresv-preserve-resv-page failed (bug 1747823) chunk-overcommit failed (bug 1747828) ubuntu_btrfs_kernel_fixes - 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22 hang (bug 1809879) ubuntu_kvm_smoke_test - Inappropriate ioctl for device ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fremovexattr01, fremovexattr02, fsync01, msync04, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) fcntl35 / fcntl35_64 (bug 1774394) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 (bug 1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107) keyctl02 (bug 1798022) keyctl06 (bug 1798025) open14 (bug 1798061) openat03 (bug 1798027) request_key03 (bug 1798052) ubuntu_qrt_apparmor - test_old_trusty_regression_testsuite failed to build (bug 1699987) ubuntu_qrt_kernel_security - test_130_config_debug_rodata (bug 1747850) test 021, 022 (bug 1747847) test 050 (bug 1684776) test_095_kernel_symbols_missing_proc_self_stack (bug 1813001) Issue to note in i386: ubuntu_btrfs_kernel_fixes - 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22 hang (bug 1809879) ubuntu_kvm_smoke_test - uvt-kvm wait issue on Trusty(bug 1732883) ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007) ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fremovexattr01, fremovexattr02, fsync01, msync04, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) fcntl35 / fcntl35_64 (bug 1774394) fanotify06 (bug 1775378) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 (bug 1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107) keyctl02 (bug 1798022) keyctl06 (bug 1798025) openat03 (bug 1798027) request_key03 (bug 1798052) ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack (bug 1813001) Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_kvm_smoke_test - no supported architecture for 'hvm' (bug 1752550) ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fremovexattr01, fremovexattr02, fsync01, msync04, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) fanotify06 (bug 1775378) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 failed with T/X/A/B kernel (bug 1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107) keyctl02 (bug 1798022) keyctl06 (bug 1798025) open14 (bug 1798061) openat03 (bug 1798027) request_key03 (bug 1798052) ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack (bug 1813001) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811856 Title: linux: 3.13.0-165.215 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series:
[Kernel-packages] [Bug 1811414] Re: linux-aws: 4.18.0-1008.10 -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: 1811406 - phase: Testing - phase-changed: Monday, 28. January 2019 13:03 UTC + phase: Release Holding + phase-changed: Friday, 01. February 2019 10:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811414 Title: linux-aws: 4.18.0-1008.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1811406 phase: Release Holding phase-changed: Friday, 01. February 2019 10:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814241] Re: linux-oem: 4.15.0-1033.38 -proposed tracker
** Summary changed: - linux-oem: -proposed tracker + linux-oem: 4.15.0-1033.38 -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) => Stefan Bader (smb) ** 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) => Stefan Bader (smb) ** 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) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1814241 Title: linux-oem: 4.15.0-1033.38 -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: 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 upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1813779 phase: Packaging phase-changed: Friday, 01. February 2019 10:39 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811420] Re: linux-raspi2: 4.15.0-1031.33 -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: 1813779 - phase: Release Holding - phase-changed: Friday, 01. February 2019 10:36 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 11:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1811420 Title: linux-raspi2: 4.15.0-1031.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released 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-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811429] Re: linux-azure: 4.15.0-1037.39~14.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: 1813779 - phase: Release Holding - phase-changed: Friday, 01. February 2019 10:35 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 11:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811429 Title: linux-azure: 4.15.0-1037.39~14.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu 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 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811080] Re: Xenial update: 4.4.168 upstream stable release
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811080
Title:
Xenial update: 4.4.168 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.4.168 upstream stable release
from git://git.kernel.org/
Linux 4.4.168
selftests: Move networking/timestamping from Documentation
rocker: fix rocker_tlv_put_* functions for KASAN
staging: speakup: Replace strncpy with memcpy
matroxfb: fix size of memcpy
media: dvb-frontends: fix i2c access helpers for KASAN
proc: do not access cmdline nor environ from file-backed areas
proc: don't use FOLL_FORCE for reading cmdline and environment
mm: replace access_remote_vm() write parameter with gup_flags
mm: replace __access_remote_vm() write parameter with gup_flags
mm: replace get_user_pages() write/force parameters with gup_flags
mm: replace get_vaddr_frames() write/force parameters with gup_flags
mm: replace get_user_pages_locked() write/force parameters with gup_flags
mm: replace get_user_pages_unlocked() write/force parameters with gup_flags
mm/nommu.c: Switch __get_user_pages_unlocked() to use __get_user_pages()
mm: remove write/force parameters from __get_user_pages_unlocked()
mm: remove write/force parameters from __get_user_pages_locked()
sr: pass down correctly sized SCSI sense buffer
swiotlb: clean up reporting
hugetlbfs: fix bug in pgoff overflow checking
hugetlbfs: check for pgoff value overflow
hugetlbfs: fix offset overflow in hugetlbfs mmap
mm/hugetlb.c: don't call region_abort if region_chg fails
posix-timers: Sanitize overrun handling
wil6210: missing length check in wmi_set_ie
bpf: Prevent memory disambiguation attack
bpf/verifier: Pass instruction index to check_mem_access() and check_xadd()
bpf/verifier: Add spi variable to check_stack_write()
bpf: support 8-byte metafield access
KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
KVM: SVM: Move spec control call after restore of GS
x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest
x86/bugs, KVM: Support the combination of guest and host IBRS
x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
x86: fix SMAP in 32-bit environments
x86: reorganize SMAP handling in user space accesses
KVM/x86: Remove indirect MSR op calls from SPEC_CTRL
KVM/SVM: Allow direct access to MSR_IA32_SPEC_CTRL
KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL
KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES
KVM/x86: Add IBPB support
KVM: VMX: make MSR bitmaps per-VCPU
KVM: VMX: introduce alloc_loaded_vmcs
KVM: nVMX: Eliminate vmcs02 pool
KVM: nVMX: mark vmcs12 pages dirty on L2 exit
KVM: nVMX: fix msr bitmaps to prevent L2 from accessing L0 x2APIC
ALSA: pcm: remove SNDRV_PCM_IOCTL1_INFO internal command
pstore: Convert console write to use ->write_buf
ocfs2: fix potential use after free
debugobjects: avoid recursive calls with kmemleak
hfsplus: do not free node before using
hfs: do not free node before using
ocfs2: fix deadlock caused by ocfs2_defrag_extent()
fscache, cachefiles: remove redundant variable 'cache'
fscache: fix race between enablement and dropping of object
xen: xlate_mmu: add missing header to fix 'W=1' warning
drm/ast: fixed reading monitor EDID not stable issue
net: hisilicon: remove unexpected free_netdev
ixgbe: recognize 1000BaseLX SFP modules as 1Gbps
net: thunderx: fix NULL pointer dereference in nic_remove
KVM: x86: fix empty-body warnings
USB: omap_udc: fix USB gadget functionality on Palm Tungsten E
USB: omap_udc: fix omap_udc_start() on 15xx machines
USB: omap_udc: fix crashes on probe error and module removal
USB: omap_udc: use devm_request_irq()
bpf: fix check of allowed specifiers in bpf_trace_printk
exportfs: do not read dentry after free
ASoC: omap-dmic: Add pm_qos handling to avoid overruns with CPU_IDLE
ASoC: omap-mcpdm: Add pm_qos handling to avoid
[Kernel-packages] [Bug 1795408] Re: linux 4.15.0-36.39 ADT test failure with linux 4.15.0-36.39
This testcase is successful now since Bionic linux-meta/4.15.0.42.44 (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/amd64/l/linux/20181123_072634_fbf99@/log.gz). Based on that I'm closing this bug report. ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795408 Title: linux 4.15.0-36.39 ADT test failure with linux 4.15.0-36.39 Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux/20181001_121205_392da@/log.gz ubuntu_nbd_smoke_test is failing with the following error: 11:56:25 DEBUG| Running '/tmp/autopkgtest.eG1goL/build.4rM/src/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke_test.sh' 11:56:26 DEBUG| [stdout] done 11:56:26 DEBUG| [stdout] 11:56:26 DEBUG| [stdout] 11:56:26 DEBUG| [stdout] Image path:/tmp/nbd_image.img 11:56:26 DEBUG| [stdout] Mount point: /mnt/nbd-test-19291 11:56:26 DEBUG| [stdout] Date: Mon Oct 1 11:56:26 UTC 2018 11:56:26 DEBUG| [stdout] Host: autopkgtest 11:56:26 DEBUG| [stdout] Kernel:4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 11:56:26 DEBUG| [stdout] Machine: autopkgtest x86_64 x86_64 11:56:26 DEBUG| [stdout] CPUs online: 4 11:56:26 DEBUG| [stdout] CPUs total:4 11:56:26 DEBUG| [stdout] Page size: 4096 11:56:26 DEBUG| [stdout] Pages avail: 1730621 11:56:26 DEBUG| [stdout] Pages total: 2041971 11:56:26 DEBUG| [stdout] 11:56:26 DEBUG| [stdout] 11:56:27 DEBUG| [stdout] tcp6 0 0 ::: :::* LISTEN 19362/nbd-server 11:56:37 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:38 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:39 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:40 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:41 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:42 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:43 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:44 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:45 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:46 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:47 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:48 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:49 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:50 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:51 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other error. 11:56:52 ERROR| [stderr] mount: /mnt/nbd-test-19291: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program, or other
[Kernel-packages] [Bug 1799139] Re: linux 4.15.0-38.41 ADT test failure (ubuntu_nbd_smoke_test)
*** This bug is a duplicate of bug 1813713 *** https://bugs.launchpad.net/bugs/1813713 Testcase still failing with bionic/linux 4.15.0-45.48 (only on i386): https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20190201_035319_9ea9e@/log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799139 Title: linux 4.15.0-38.41 ADT test failure (ubuntu_nbd_smoke_test) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20181019_194651_d42a8@/log.gz The ubuntu_nbd_smoke_test testcase is hitting the following kernel bug: 16:02:03 DEBUG| [stdout] [ 6587.920070] [ cut here ] 16:02:03 DEBUG| [stdout] [ 6587.975274] kernel BUG at /build/linux-aTHL1U/linux-4.15.0/fs/buffer.c:3064! 16:02:03 DEBUG| [stdout] [ 6587.976968] invalid opcode: [#2] SMP 16:02:03 DEBUG| [stdout] [ 6587.977880] Modules linked in: nbd 842 842_decompress 842_compress lz4hc lz4hc_compress lz4 lz4_compress unix_diag binfmt_misc cuse uhid hid vfio_iommu_type1 vfio hci_vhci bluetooth ecdh_generic vhost_net tap vhost_vsock vmw_vsock_virtio_transport_common vhost vsock snd_seq snd_seq_device snd_timer snd soundcore userio dccp_ipv4 algif_rng salsa20_generic salsa20_i586 camellia_generic cast6_generic cast_common serpent_sse2_i586 serpent_generic glue_helper ablk_helper twofish_generic twofish_i586 twofish_common lrw algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg aufs macsec vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip_gre ip_tunnel gre cls_u32 sch_htb dummy af_packet_diag sctp_diag sctp libcrc32c dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag 16:02:03 DEBUG| [stdout] [ 6587.994265] xt_TCPMSS xt_tcpudp iptable_mangle kvm_intel kvm irqbypass crc32_pclmul pcbc aesni_intel aes_i586 crypto_simd cryptd joydev input_leds mac_hid qemu_fw_cfg serio_raw sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq psmouse i2c_piix4 virtio_net virtio_blk pata_acpi floppy [last unloaded: zram] 16:02:03 DEBUG| [stdout] [ 6588.000720] CPU: 3 PID: 3794 Comm: kworker/u8:1 Tainted: G D W OE4.15.0-38-generic #41-Ubuntu 16:02:03 DEBUG| [stdout] [ 6588.002806] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 16:02:03 DEBUG| [stdout] [ 6588.004941] Workqueue: writeback wb_workfn (flush-43:0) 16:02:03 DEBUG| [stdout] [ 6588.006119] EIP: submit_bh_wbc+0x168/0x190 16:02:03 DEBUG| [stdout] [ 6588.007052] EFLAGS: 00010246 CPU: 3 16:02:03 DEBUG| [stdout] [ 6588.007846] EAX: 00620005 EBX: ce002cb0 ECX: ce002cb0 EDX: 00020800 16:02:03 DEBUG| [stdout] [ 6588.009251] ESI: 00020800 EDI: db34e400 EBP: d054bc3c ESP: d054bc2c 16:02:03 DEBUG| [stdout] [ 6588.010656] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 16:02:03 DEBUG| [stdout] [ 6588.011876] CR0: 80050033 CR2: b7f29e44 CR3: 1de14000 CR4: 001406f0 16:02:03 DEBUG| [stdout] [ 6588.013286] Call Trace: 16:02:03 DEBUG| [stdout] [ 6588.013886] __sync_dirty_buffer+0x4d/0xf0 16:02:03 DEBUG| [stdout] [ 6588.014824] ext4_commit_super+0x1e2/0x290 16:02:03 DEBUG| [stdout] [ 6588.015767] __ext4_abort+0x4a/0x120 16:02:03 DEBUG| [stdout] [ 6588.016588] ext4_journal_check_start+0x81/0x90 16:02:03 DEBUG| [stdout] [ 6588.017611] __ext4_journal_start_sb+0x28/0xd0 16:02:03 DEBUG| [stdout] [ 6588.018622] ? ext4_writepages+0x4d4/0x880 16:02:03 DEBUG| [stdout] [ 6588.045547] ext4_writepages+0x4d4/0x880 16:02:03 DEBUG| [stdout] [ 6588.046460] ? blk_mq_dispatch_rq_list+0x74/0x440 16:02:03 DEBUG| [stdout] [ 6588.047552] do_writepages+0x39/0xc0 16:02:03 DEBUG| [stdout] [ 6588.048367] ? blk_mq_sched_dispatch_requests+0x184/0x190 16:02:03 DEBUG| [stdout] [ 6588.049579] __writeback_single_inode+0x3a/0x310 16:02:03 DEBUG| [stdout] [ 6588.050623] writeback_sb_inodes+0x167/0x3a0 16:02:03 DEBUG| [stdout] [ 6588.051601] __writeback_inodes_wb+0x55/0xa0 16:02:03 DEBUG| [stdout] [ 6588.052568] wb_writeback+0x20a/0x2a0 16:02:03 DEBUG| [stdout] [ 6588.053411] ? find_next_bit+0xa/0x10 16:02:03 DEBUG| [stdout] [ 6588.054246] wb_workfn+0x313/0x430 16:02:03 DEBUG| [stdout] [ 6588.055051] ? __switch_to_asm+0x27/0x4c 16:02:03 DEBUG| [stdout] [ 6588.055961] ? __switch_to+0xae/0x360 16:02:03 DEBUG| [stdout] [ 6588.056795] ? __switch_to_asm+0x33/0x4c 16:02:03 DEBUG| [stdout] [ 6588.057685] ? __switch_to_asm+0x27/0x4c 16:02:03 DEBUG| [stdout] [ 6588.058597] process_one_work+0x1b9/0x3d0 16:02:03 DEBUG| [stdout] [ 6588.059514] worker_thread+0x37/0x420
[Kernel-packages] [Bug 1814232] [NEW] cpu_hotplug test failed due to Permission denied
Public bug reported: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 TAP version 13 selftests: cpu-hotplug: cpu-on-off-test.sh pid 9047's current affinity mask: 3 pid 9047's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-1 present_max = 1 Cpus in online state: 0-1 Cpus in offline state: 2-127 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 19. 01/30 19:57:02 ERROR| utils:0153| [stderr] ./cpu-on-off-test.sh: line 96: /sys/devices/system/cpu/cpu1/online: Permission denied 20. 01/30 19:57:02 ERROR| utils:0153| [stderr] offline_cpu_expect_success 1: unexpected fail not ok 1..1 selftests: cpu-hotplug: cpu-on-off-test.sh [FAIL] ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-azure-edge (Ubuntu) Importance: Undecided Status: New ** Package changed: linux-azure (Ubuntu) => linux-azure-edge (Ubuntu) ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Summary changed: - cpu_hot_plug test failed due to Permission denied + cpu_hotplug test failed due to Permission denied -- 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/1814232 Title: cpu_hotplug test failed due to Permission denied Status in ubuntu-kernel-tests: New Status in linux-azure-edge package in Ubuntu: New Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 TAP version 13 selftests: cpu-hotplug: cpu-on-off-test.sh pid 9047's current affinity mask: 3 pid 9047's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-1 present_max = 1 Cpus in online state: 0-1 Cpus in offline state: 2-127 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 19. 01/30 19:57:02 ERROR| utils:0153| [stderr] ./cpu-on-off-test.sh: line 96: /sys/devices/system/cpu/cpu1/online: Permission denied 20. 01/30 19:57:02 ERROR| utils:0153| [stderr] offline_cpu_expect_success 1: unexpected fail not ok 1..1 selftests: cpu-hotplug: cpu-on-off-test.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812822] Re: Guest crashed when detaching the ovs interface device
To some extend this feels a bit like: - https://bugzilla.redhat.com/show_bug.cgi?id=1242383 - https://bugzilla.redhat.com/show_bug.cgi?id=1151306 All those got closed as "invalid host config -> won't fix" so we can't find the fix there. But something happened to let it work fine in my case, we need to find that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812822 Title: Guest crashed when detaching the ovs interface device Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Incomplete Bug description: When detaching one openvswitch interface device with virsh detach-device, if the port has been deleted from the ovs and the interface device has been deleted. The virsh detach-device will fail with "error: Unable to read from monitor: Connection reset by peer", the qemu is terminated and the log shows " UNSETVNETLE ioctl() failed, File descriptor in bad state". [Background] This error is originally found from the openstack KVM CI tempest test. By investigating I found it's introduced by one ovs-vif patch, which deletes the ovs port and delete the interface before detaching the device. You can find the commit from https://bugs.launchpad.net/os-vif/+bug/1801072 Reproduced: root@:~# ovs-vsctl del-port br0 tap9273235a-dd root@:~# ip link del tap9273235a-dd The interface device tap9273235a-dd has been removed from the host(ifconfg, ovs-vsctl show) and can be found in the guest.(logon the guest, ip a it's in down state) root@:~# virsh detach-device kvm net.xml error: Failed to detach device from net.xml error: Unable to read from monitor: Connection reset by peer The qemu has terminated and the log in /var/log/libvirt/qemu/kvm.log TUNSETVNETLE ioctl() failed: File descriptor in bad state. 2019-01-18 08:16:11.304+: shutting down, reason=crashed It seems the qemu tried to handle this interface, but in fact it has been deleted. qemu couldn't read the file and give the error. But I don't think the guest should be crashed directly for the file descriptor error. Environment: Ubuntu 16.04.5 LTS Linux (EC12) 4.4.0-141-generic QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5~cloud0) libvirtd (libvirt) 4.0.0 net.xml kvm.xml kvm 59f71b47-16e4-401d-9d33-30bc1605a84a 524288 524288 1 /machine hvm destroy restart destroy /usr/bin/qemu-system-s390x libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a +0:+0 +0:+0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1812822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812822] Re: Guest crashed when detaching the ovs interface device
I used a recent version of the softwrae stack from Disco - qemu 3.1 - libvirt 5.0 - openvswitch 2.11 With that I had a guest with an OVS device like that: Not too different to your's I'd think. The OVS is trivial just having this interface atm. $ sudo ovs-vsctl show 596674ef-e4cd-471f-9708-9caa5737961c Bridge "ovsbr0" Port "eno49" Interface "eno49" Port "ovsbr0" Interface "ovsbr0" type: internal Port "vnet1" Interface "vnet1" ovs_version: "2.11.0" $ ip link show dev vnet1 93: vnet1: mtu 1500 qdisc mq master ovs-system state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:54:00:22:57:fd brd ff:ff:ff:ff:ff:ff I have a started a second guest on the same vswitch (to check traffic from the first guest later on). Now lets delete that port: $ sudo ovs-vsctl del-port ovsbr0 vnet1 $ sudo ovs-vsctl show 596674ef-e4cd-471f-9708-9caa5737961c Bridge "ovsbr0" Port "vnet3" Interface "vnet3" Port "eno49" Interface "eno49" Port "ovsbr0" Interface "ovsbr0" type: internal ovs_version: "2.11.0" Ok the OVS device is gone. Obviously traffic on that interface is dead now, but the guest is still alive and happy. The host dev is still there: $ ip link show dev vnet1 93: vnet1: mtu 1500 qdisc mq state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:54:00:22:57:fd brd ff:ff:ff:ff:ff:ff Removing that as well as suggested $ sudo ip link del vnet1 $ ip link show dev vnet1 Device "vnet1" does not exist. The guest still is up and running, while traffic still won't work for obvious reasons. Now lets trigger the hot-unplug of the device. $ virsh detach-device guest-openvswitch-1 net.xml Device detached successfully The guest is still happy and alive. It lost the device (since we detached it) but that is ok and intentional. ** Bug watch added: Red Hat Bugzilla #1242383 https://bugzilla.redhat.com/show_bug.cgi?id=1242383 ** Bug watch added: Red Hat Bugzilla #1151306 https://bugzilla.redhat.com/show_bug.cgi?id=1151306 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812822 Title: Guest crashed when detaching the ovs interface device Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Incomplete Bug description: When detaching one openvswitch interface device with virsh detach-device, if the port has been deleted from the ovs and the interface device has been deleted. The virsh detach-device will fail with "error: Unable to read from monitor: Connection reset by peer", the qemu is terminated and the log shows " UNSETVNETLE ioctl() failed, File descriptor in bad state". [Background] This error is originally found from the openstack KVM CI tempest test. By investigating I found it's introduced by one ovs-vif patch, which deletes the ovs port and delete the interface before detaching the device. You can find the commit from https://bugs.launchpad.net/os-vif/+bug/1801072 Reproduced: root@:~# ovs-vsctl del-port br0 tap9273235a-dd root@:~# ip link del tap9273235a-dd The interface device tap9273235a-dd has been removed from the host(ifconfg, ovs-vsctl show) and can be found in the guest.(logon the guest, ip a it's in down state) root@:~# virsh detach-device kvm net.xml error: Failed to detach device from net.xml error: Unable to read from monitor: Connection reset by peer The qemu has terminated and the log in /var/log/libvirt/qemu/kvm.log TUNSETVNETLE ioctl() failed: File descriptor in bad state. 2019-01-18 08:16:11.304+: shutting down, reason=crashed It seems the qemu tried to handle this interface, but in fact it has been deleted. qemu couldn't read the file and give the error. But I don't think the guest should be crashed directly for the file descriptor error. Environment: Ubuntu 16.04.5 LTS Linux (EC12) 4.4.0-141-generic QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5~cloud0) libvirtd (libvirt) 4.0.0 net.xml kvm.xml kvm 59f71b47-16e4-401d-9d33-30bc1605a84a 524288 524288 1 /machine hvm destroy restart destroy /usr/bin/qemu-system-s390x libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a +0:+0
[Kernel-packages] [Bug 1813796] Re: kernel bug null pointer dereference
*** This bug is a duplicate of bug 1813663 *** https://bugs.launchpad.net/bugs/1813663 I had similar problem with my Thinkpad X1 and Thinkpad Thunderbolt dock. Updating to the newest release of kernel (4.15.0-45-generic) today morning fixed the issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813796 Title: kernel bug null pointer dereference Status in linux package in Ubuntu: Incomplete Bug description: After upgrading to linux-image-4.15.0-44-generic via the update manager today, I can't log in anymore. The login screen appears, but as soon as I've entered my password and hit enter, the desktop locks up, keyboard stops working and display goes black. Network is still working, so I could login remotely and see the crash live via journalctl. I attached the full output of journalctl -k -b -1 In short it says BUG: unable to handle kernel NULL pointer dereference at 0245 IP: intel_ddi_post_disable+0x54/0x170 [i915] PGD 0 P4D 0 Oops: [#1] SMP PTI Infos about my hardware: lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy linux-image-4.15.0-44-generic linux-image-4.15.0-44-generic: Installiert: 4.15.0-44.47 Installationskandidat: 4.15.0-44.47 Versionstabelle: *** 4.15.0-44.47 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status Rebooting to the previous kernel 4.15.0-43 doesn't have this issue and I can login without issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812822] Re: Guest crashed when detaching the ovs interface device
** Changed in: ubuntu-z-systems Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812822 Title: Guest crashed when detaching the ovs interface device Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Incomplete Bug description: When detaching one openvswitch interface device with virsh detach-device, if the port has been deleted from the ovs and the interface device has been deleted. The virsh detach-device will fail with "error: Unable to read from monitor: Connection reset by peer", the qemu is terminated and the log shows " UNSETVNETLE ioctl() failed, File descriptor in bad state". [Background] This error is originally found from the openstack KVM CI tempest test. By investigating I found it's introduced by one ovs-vif patch, which deletes the ovs port and delete the interface before detaching the device. You can find the commit from https://bugs.launchpad.net/os-vif/+bug/1801072 Reproduced: root@:~# ovs-vsctl del-port br0 tap9273235a-dd root@:~# ip link del tap9273235a-dd The interface device tap9273235a-dd has been removed from the host(ifconfg, ovs-vsctl show) and can be found in the guest.(logon the guest, ip a it's in down state) root@:~# virsh detach-device kvm net.xml error: Failed to detach device from net.xml error: Unable to read from monitor: Connection reset by peer The qemu has terminated and the log in /var/log/libvirt/qemu/kvm.log TUNSETVNETLE ioctl() failed: File descriptor in bad state. 2019-01-18 08:16:11.304+: shutting down, reason=crashed It seems the qemu tried to handle this interface, but in fact it has been deleted. qemu couldn't read the file and give the error. But I don't think the guest should be crashed directly for the file descriptor error. Environment: Ubuntu 16.04.5 LTS Linux (EC12) 4.4.0-141-generic QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5~cloud0) libvirtd (libvirt) 4.0.0 net.xml kvm.xml kvm 59f71b47-16e4-401d-9d33-30bc1605a84a 524288 524288 1 /machine hvm destroy restart destroy /usr/bin/qemu-system-s390x libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a +0:+0 +0:+0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1812822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811415] Re: linux-azure: 4.18.0-1008.8 -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: 1811406 - phase: Testing - phase-changed: Monday, 28. January 2019 13:03 UTC + phase: Release Holding + phase-changed: Friday, 01. February 2019 10:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811415 Title: linux-azure: 4.18.0-1008.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu 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 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: 1811406 phase: Release Holding phase-changed: Friday, 01. February 2019 10:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811412] Re: linux-raspi2: 4.18.0-1009.11 -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: 1811406 - phase: Testing - phase-changed: Monday, 28. January 2019 11:50 UTC + phase: Release Holding + phase-changed: Friday, 01. February 2019 10:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1811412 Title: linux-raspi2: 4.18.0-1009.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1811406 phase: Release Holding phase-changed: Friday, 01. February 2019 10:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811846] Re: linux: 4.4.0-142.168 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Monday, 28. January 2019 13:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED verification-testing: Ongoing -- 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/1811846 Title: linux: 4.4.0-142.168 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released 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: New Status in Kernel SRU Workflow upload-to-ppa-dnu 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 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Monday, 28. January 2019 13:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -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: 1813779 - phase: Testing - phase-changed: Monday, 28. January 2019 11:54 UTC + phase: Release Holding + phase-changed: Friday, 01. February 2019 10:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811431 Title: linux-azure: 4.15.0-1037.39~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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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-dnu 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: 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: 1813779 phase: Release Holding phase-changed: Friday, 01. February 2019 10:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811416] Re: linux-gcp: 4.18.0-1006.7 -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: 1811406 - phase: Testing - phase-changed: Monday, 28. January 2019 11:53 UTC + phase: Release Holding + phase-changed: Friday, 01. February 2019 10:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811416 Title: linux-gcp: 4.18.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid 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: 1811406 phase: Release Holding phase-changed: Friday, 01. February 2019 10:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811406] Re: linux: 4.18.0-14.15 -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 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Testing - phase-changed: Monday, 28. January 2019 13:02 UTC + phase: Release Holding + phase-changed: Friday, 01. February 2019 10:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811406 Title: linux: 4.18.0-14.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Friday, 01. February 2019 10:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811856] Re: linux: 3.13.0-165.215 -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 1811857 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Monday, 28. January 2019 11:49 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- 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/1811856 Title: linux: 3.13.0-165.215 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu 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 1811857 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Monday, 28. January 2019 11:49 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811432] Re: linux-gcp: 4.15.0-1027.28~16.04.1 -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: 1813779 - phase: Testing - phase-changed: Monday, 28. January 2019 11:53 UTC + phase: Release Holding + phase-changed: Friday, 01. February 2019 10:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811432 Title: linux-gcp: 4.15.0-1027.28~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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1813779 phase: Release Holding phase-changed: Friday, 01. February 2019 10:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on Bionic with PowerPC
Didn't see this for ppc64el on the latest 4.15 bionic kernel (4.15.0-45)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811981
Title:
test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
on Bionic with PowerPC
Status in QA Regression Testing:
New
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-kvm package in Ubuntu:
New
Status in linux source package in Bionic:
New
Status in linux-kvm source package in Bionic:
New
Status in linux source package in Cosmic:
New
Status in linux-kvm source package in Cosmic:
New
Bug description:
Kernel Version: 4.15.0-44.47
This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
Power8 and Power9
FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
Ensure kernel efi lockdown is enabled
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2668, in
test_410_config_lock_down_kernel
self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel
config
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1811981/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811424] Re: linux-gcp: 4.15.0-1027.28 -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: 1813779 - phase: Release Holding - phase-changed: Monday, 28. January 2019 12:19 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 10:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811424 Title: linux-gcp: 4.15.0-1027.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 10:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -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: 1813779 - phase: Release Holding - phase-changed: Friday, 01. February 2019 10:44 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 10:57 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811431 Title: linux-azure: 4.15.0-1037.39~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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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-dnu 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: 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: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 10:57 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814237] Re: ubuntu_nbd_smoke_test failed with I/O error on X-4.15
Some more useful info: * This issue started to be caught by the testcase after the following test script change: https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke_test.sh?id=92ffd0ff14715392730943a898a95920b243ebef * I have traced back these I/O errors on released from a couple of months ago. Checked xenial/linux-hwe and bionic/linux-azure. * This doesn't seem to affect the master kernel, bionic/linux. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814237 Title: ubuntu_nbd_smoke_test failed with I/O error on X-4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Kernel: 4.15.0-45.48~16.04.1 creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-25789 Date: Thu Jan 31 14:42:42 UTC 2019 Host: onibi Kernel:4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 Machine: onibi x86_64 x86_64 CPUs online: 4 CPUs total:4 Page size: 4096 Pages avail: 1351388 Pages total: 2038431 Free space: Filesystem Size Used Avail Use% Mounted on udev3.9G 0 3.9G 0% /dev tmpfs 797M 17M 780M 3% /run /dev/sda1 917G 9.1G 861G 2% / tmpfs 3.9G 4.0K 3.9G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 797M 0 797M 0% /run/user/1000 tmpfs 100K 0 100K 0% /var/lib/lxd/shmounts tmpfs 100K 0 100K 0% /var/lib/lxd/devlxd cgmfs 100K 0 100K 0% /run/cgmanager/fs NBD device /dev/nbd0 created found nbd export NBD exports found: test starting client with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 succeeded after 0 attempt(s) checking ext4 on /dev/nbd0 fsck from util-linux 2.27.1 /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks mount: /dev/nbd0 on /mnt/nbd-test-25789 type ext4 (rw,relatime,data=ordered) mounted on /dev/nbd0 free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 1550112111 2% /mnt/nbd-test-25789 creating large file /mnt/nbd-test-25789/largefile -rw-r--r-- 1 root root 100M Jan 31 14:42 /mnt/nbd-test-25789/largefile free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-25789 removing file /mnt/nbd-test-25789/largefile unmounting /mnt/nbd-test-25789 stopping client disconnect, sock, done Found kernel warning, IO error and/or call trace echo [ 4593.254552] creating backing nbd image /tmp/nbd_image.img [ 4595.506134] NBD device /dev/nbd0 created [ 4595.557990] found nbd export [ 4596.604855] starting client with NBD device /dev/nbd0 [ 4596.606795] creating ext4 on /dev/nbd0 [ 4597.013721] mkfs on /dev/nbd0 succeeded after 0 attempt(s) [ 4597.390241] checking ext4 on /dev/nbd0 [ 4597.455371] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ 4597.460552] mounted on /dev/nbd0 [ 4597.461810] creating large file /mnt/nbd-test-25789/largefile [ 4599.056704] removing file /mnt/nbd-test-25789/largefile [ 4599.276298] unmounting /mnt/nbd-test-25789 [ 4600.319460] stopping client [ 4600.320083] block nbd0: NBD_DISCONNECT [ 4600.320127] block nbd0: shutting down sockets [ 4600.320267] nbd0: detected capacity change from 0 to 134217728 [ 4600.320306] print_req_error: 7 callbacks suppressed [ 4600.320308] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.325890] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.333002] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.338653] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.345687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.351253] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.358279] ldm_validate_partition_table(): Disk read failed. [ 4600.358305] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.363892] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.371075] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.376645] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.383687] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.389230] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4600.396307] print_req_error: I/O error, dev nbd0, sector 0 [ 4600.401819] Buffer I/O error on dev nbd0,
[Kernel-packages] [Bug 1811425] Re: linux-kvm: 4.15.0-1029.29 -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: 1813779 - phase: Release Holding - phase-changed: Monday, 28. January 2019 12:20 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 10:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1811425 Title: linux-kvm: 4.15.0-1029.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 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 10:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814241] Re: linux-oem: 4.15.0-1033.38 -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: 1813779 phase: Packaging phase-changed: Friday, 01. February 2019 10:39 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1814241 Title: linux-oem: 4.15.0-1033.38 -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: 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 upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1813779 phase: Packaging phase-changed: Friday, 01. February 2019 10:39 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811417] Re: linux-kvm: 4.18.0-1007.7 -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: 1811406 - phase: Release Holding - phase-changed: Monday, 28. January 2019 12:28 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 11:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1811417 Title: linux-kvm: 4.18.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1811406 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811414] Re: linux-aws: 4.18.0-1008.10 -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: 1811406 - phase: Release Holding - phase-changed: Friday, 01. February 2019 10:38 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 11:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811414 Title: linux-aws: 4.18.0-1008.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1811406 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811432] Re: linux-gcp: 4.15.0-1027.28~16.04.1 -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: 1813779 - phase: Release Holding - phase-changed: Friday, 01. February 2019 10:46 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 11:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811432 Title: linux-gcp: 4.15.0-1027.28~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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811080] Re: Xenial update: 4.4.168 upstream stable release
** Changed in: linux (Ubuntu Xenial)
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/1811080
Title:
Xenial update: 4.4.168 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.4.168 upstream stable release
from git://git.kernel.org/
Linux 4.4.168
selftests: Move networking/timestamping from Documentation
rocker: fix rocker_tlv_put_* functions for KASAN
staging: speakup: Replace strncpy with memcpy
matroxfb: fix size of memcpy
media: dvb-frontends: fix i2c access helpers for KASAN
proc: do not access cmdline nor environ from file-backed areas
proc: don't use FOLL_FORCE for reading cmdline and environment
mm: replace access_remote_vm() write parameter with gup_flags
mm: replace __access_remote_vm() write parameter with gup_flags
mm: replace get_user_pages() write/force parameters with gup_flags
mm: replace get_vaddr_frames() write/force parameters with gup_flags
mm: replace get_user_pages_locked() write/force parameters with gup_flags
mm: replace get_user_pages_unlocked() write/force parameters with gup_flags
mm/nommu.c: Switch __get_user_pages_unlocked() to use __get_user_pages()
mm: remove write/force parameters from __get_user_pages_unlocked()
mm: remove write/force parameters from __get_user_pages_locked()
sr: pass down correctly sized SCSI sense buffer
swiotlb: clean up reporting
hugetlbfs: fix bug in pgoff overflow checking
hugetlbfs: check for pgoff value overflow
hugetlbfs: fix offset overflow in hugetlbfs mmap
mm/hugetlb.c: don't call region_abort if region_chg fails
posix-timers: Sanitize overrun handling
wil6210: missing length check in wmi_set_ie
bpf: Prevent memory disambiguation attack
bpf/verifier: Pass instruction index to check_mem_access() and check_xadd()
bpf/verifier: Add spi variable to check_stack_write()
bpf: support 8-byte metafield access
KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
KVM: SVM: Move spec control call after restore of GS
x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest
x86/bugs, KVM: Support the combination of guest and host IBRS
x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
x86: fix SMAP in 32-bit environments
x86: reorganize SMAP handling in user space accesses
KVM/x86: Remove indirect MSR op calls from SPEC_CTRL
KVM/SVM: Allow direct access to MSR_IA32_SPEC_CTRL
KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL
KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES
KVM/x86: Add IBPB support
KVM: VMX: make MSR bitmaps per-VCPU
KVM: VMX: introduce alloc_loaded_vmcs
KVM: nVMX: Eliminate vmcs02 pool
KVM: nVMX: mark vmcs12 pages dirty on L2 exit
KVM: nVMX: fix msr bitmaps to prevent L2 from accessing L0 x2APIC
ALSA: pcm: remove SNDRV_PCM_IOCTL1_INFO internal command
pstore: Convert console write to use ->write_buf
ocfs2: fix potential use after free
debugobjects: avoid recursive calls with kmemleak
hfsplus: do not free node before using
hfs: do not free node before using
ocfs2: fix deadlock caused by ocfs2_defrag_extent()
fscache, cachefiles: remove redundant variable 'cache'
fscache: fix race between enablement and dropping of object
xen: xlate_mmu: add missing header to fix 'W=1' warning
drm/ast: fixed reading monitor EDID not stable issue
net: hisilicon: remove unexpected free_netdev
ixgbe: recognize 1000BaseLX SFP modules as 1Gbps
net: thunderx: fix NULL pointer dereference in nic_remove
KVM: x86: fix empty-body warnings
USB: omap_udc: fix USB gadget functionality on Palm Tungsten E
USB: omap_udc: fix omap_udc_start() on 15xx machines
USB: omap_udc: fix crashes on probe error and module removal
USB: omap_udc: use devm_request_irq()
bpf: fix check of allowed specifiers in bpf_trace_printk
exportfs: do not read dentry after free
ASoC: omap-dmic: Add pm_qos handling to avoid overruns with CPU_IDLE
ASoC: omap-mcpdm: Add pm_qos handling to avoid under/overruns with CPU_IDLE
Btrfs: send, fix infinite loop due to directory
[Kernel-packages] [Bug 1811647] Re: Xenial update: 4.4.170 upstream stable release
When pulling, skipped "fork: record start_time late" since it was already applied for CVE-2019-6133. ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-6133 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811647 Title: Xenial update: 4.4.170 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.170 upstream stable release from git://git.kernel.org/ Linux 4.4.170 power: supply: olpc_battery: correct the temperature units intel_th: msu: Fix an off-by-one in attribute store genwqe: Fix size check ceph: don't update importing cap's mseq when handing cap export iommu/vt-d: Handle domain agaw being less than iommu agaw 9p/net: put a lower bound on msize b43: Fix error in cordic routine gfs2: Fix loop in gfs2_rbm_find dlm: memory leaks on error path in dlm_user_request() dlm: lost put_lkb on error path in receive_convert() and receive_unlock() dlm: possible memory leak on error path in create_lkb() dlm: fixed memory leaks after failed ls_remove_names allocation ALSA: usb-audio: Fix an out-of-bound read in create_composite_quirks ALSA: usb-audio: Avoid access before bLength check in build_audio_procunit() ALSA: cs46xx: Potential NULL dereference in probe crypto: x86/chacha20 - avoid sleeping with preemption disabled sunrpc: use SVC_NET() in svcauth_gss_* functions sunrpc: fix cache_head leak due to queued request mm, devm_memremap_pages: kill mapping "System RAM" support mm, devm_memremap_pages: mark devm_memremap_pages() EXPORT_SYMBOL_GPL hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined fork: record start_time late scsi: zfcp: fix posting too many status read buffers leading to adapter shutdown Input: omap-keypad - fix idle configuration to not block SoC idle states scsi: bnx2fc: Fix NULL dereference in error handling xfrm: Fix bucket count reported to userspace checkstack.pl: fix for aarch64 Input: restore EV_ABS ABS_RESERVED ARM: imx: update the cpu power up timing setting on i.mx6sx powerpc: Fix COFF zImage booting on old powermacs spi: bcm2835: Unbreak the build of esoteric configs x86/kvm/vmx: do not use vm-exit instruction length for fast MMIO when running nested CIFS: Fix error mapping for SMB2_LOCK command which caused OFD lock problem MIPS: Align kernel load address to 64KB MIPS: Ensure pmd_present() returns false after pmd_mknotpresent() media: vivid: free bitmap_cap when updating std/timings/etc. cdc-acm: fix abnormal DATA RX issue for Mediatek Preloader. spi: bcm2835: Avoid finishing transfer prematurely in IRQ mode spi: bcm2835: Fix book-keeping of DMA termination spi: bcm2835: Fix race on DMA termination ext4: force inode writes when nfsd calls commit_metadata() ext4: fix EXT4_IOC_GROUP_ADD ioctl ext4: missing unlock/put_page() in ext4_try_to_write_inline_data() ext4: fix possible use after free in ext4_quota_enable perf pmu: Suppress potential format-truncation warning KVM: x86: Use jmp to invoke kvm_spurious_fault() from .fixup Input: elan_i2c - add ACPI ID for touchpad in ASUS Aspire F5-573G usb: r8a66597: Fix a possible concurrency use-after-free bug in r8a66597_endpoint_disable() USB: serial: option: add Fibocom NL678 series USB: serial: pl2303: add ids for Hewlett-Packard HP POS pole displays ALSA: hda/tegra: clear pending irq handlers ALSA: hda: add mute LED support for HP EliteBook 840 G4 ALSA: emux: Fix potential Spectre v1 vulnerabilities ALSA: pcm: Fix potential Spectre v1 vulnerability ALSA: emu10k1: Fix potential Spectre v1 vulnerabilities ALSA: rme9652: Fix potential Spectre v1 vulnerability sock: Make sock->sk_stamp thread-safe gro_cell: add napi_disable in gro_cells_destroy xen/netfront: tolerate frags with no data VSOCK: Send reset control packet when socket is partially bound vhost: make sure used idx is seen before log in vhost_add_used_n() sctp: initialize sin6_flowinfo for ipv6 addrs in sctp_inet6addr_event packet: validate address length if non-zero
[Kernel-packages] [Bug 1812822] Re: Guest crashed when detaching the ovs interface device
We now need to find out what the difference is: a) your test case is slightly different and you can trigger it on the same SW levels it works for me, then we need to report that to upstream as those are the very latest versions b) your test is good once you use the more recent SW levels, in that case we need to drill down into your crash and identify the fix (that must be in between qemu 2.11 and 3.1 somewhere) to consider backporting it. c) This would be arch dependent (I tested x86), but we would find that further down the road as you'd report (a) to happen. After all TUNSETVNETLE is for setting big/little endian operations for linux tap/macvtap so it could be s390x only after all. I can't re-deploy the system to use Bionic level components that you use at the moment and that also would only answer (b) but not (a). Therefore to differentiate between the above I'd want to ask you if you could re-run your test on Ubuntu 19.04 with Proposed enabled [1] as the new openvswitch still is in proposed for now. Report back if you can still trigger the issue, but then I'll most likely encourage you to report it upstream and I'd then participate in the discussion there - probably building test PPAs for you as needed. Also report back if this SW stack works for you as well, in that case I'd wonder if you get an actual crash in /var/crash that would help where in the qemu code we would look for TUNSETVNETLE ioctl() failed: File descriptor in bad state. I'd assume net/tap-linux.c in tap_fd_set_vnet_le, but let's be sure. [1]: https://wiki.ubuntu.com/Testing/EnableProposed ** Changed in: qemu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812822 Title: Guest crashed when detaching the ovs interface device Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Incomplete Bug description: When detaching one openvswitch interface device with virsh detach-device, if the port has been deleted from the ovs and the interface device has been deleted. The virsh detach-device will fail with "error: Unable to read from monitor: Connection reset by peer", the qemu is terminated and the log shows " UNSETVNETLE ioctl() failed, File descriptor in bad state". [Background] This error is originally found from the openstack KVM CI tempest test. By investigating I found it's introduced by one ovs-vif patch, which deletes the ovs port and delete the interface before detaching the device. You can find the commit from https://bugs.launchpad.net/os-vif/+bug/1801072 Reproduced: root@:~# ovs-vsctl del-port br0 tap9273235a-dd root@:~# ip link del tap9273235a-dd The interface device tap9273235a-dd has been removed from the host(ifconfg, ovs-vsctl show) and can be found in the guest.(logon the guest, ip a it's in down state) root@:~# virsh detach-device kvm net.xml error: Failed to detach device from net.xml error: Unable to read from monitor: Connection reset by peer The qemu has terminated and the log in /var/log/libvirt/qemu/kvm.log TUNSETVNETLE ioctl() failed: File descriptor in bad state. 2019-01-18 08:16:11.304+: shutting down, reason=crashed It seems the qemu tried to handle this interface, but in fact it has been deleted. qemu couldn't read the file and give the error. But I don't think the guest should be crashed directly for the file descriptor error. Environment: Ubuntu 16.04.5 LTS Linux (EC12) 4.4.0-141-generic QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5~cloud0) libvirtd (libvirt) 4.0.0 net.xml kvm.xml kvm 59f71b47-16e4-401d-9d33-30bc1605a84a 524288 524288 1 /machine hvm destroy restart destroy /usr/bin/qemu-system-s390x libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a +0:+0 +0:+0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1812822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814231] [NEW] linux 4.4.0-142.168 ADT test failure (ubuntu_vfat_stress): hung task on i386
Public bug reported: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190201_082722_4cb3e@/log.gz ubuntu_vfat_stress is causing a kernel hung task on xenial/linux i386: Started, PID 23212 Timed out waiting for stress-ng to finish Forcefully killing, PID 23212 (after 121 seconds) Found kernel warning and/or call trace: [ 3998.807995] Testing: --verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M --fallocate-bytes 2M --chdir 2 --rename 2 --hdd-write-size 512 [ 3998.832802] Created loop image vfat-test-23176/vfat-image-23176.img on /dev/loop0 [ 3999.936713] ubuntu_vfat_str (23176): drop_caches: 1 [ 3999.944908] ubuntu_vfat_str (23176): drop_caches: 2 [ 3999.949450] ubuntu_vfat_str (23176): drop_caches: 3 [ 3999.967248] VFAT options: allow_utime=20 [ 3999.967299] Stress test: /tmp/autopkgtest.ytglRN/build.6Ql/src/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng --verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M --fallocate-bytes 2M --chdir 2 --rename 2 --hdd-write-size 512 [ 3999.967318] Mount point: /mnt/vfat-test-23176 [ 3999.967994] Started, PID 23212 [ 4121.902337] Timed out waiting for stress-ng to finish [ 4121.902488] Forcefully killing, PID 23212 (after 121 seconds) [ 4200.180102] INFO: task stress-ng:23229 blocked for more than 120 seconds. [ 4200.18] Tainted: G OE 4.4.0-142-generic #168-Ubuntu [ 4200.185438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4200.186581] stress-ng D c1214654 0 23229 1 0x0004 [ 4200.186587] c5bc9ebc 0086 c5bc9ea4 c1214654 ce0a5b00 64d56897 03a3 [ 4200.186591] 6497d7cf 03a3 d8185dc0 d239a800 c5bca000 d00ce5e0 c5bc9f08 c5bc9ec8 [ 4200.186595] c17e194d c5bc9f08 c5bc9ef0 c12146ad d239a800 c10b5340 d00ce5e4 [ 4200.186598] Call Trace: [ 4200.186608] [] ? wb_queue_work+0xe4/0xf0 [ 4200.186613] [] schedule+0x2d/0x80 [ 4200.186616] [] wb_wait_for_completion+0x4d/0x90 [ 4200.186620] [] ? wake_atomic_t_function+0x70/0x70 [ 4200.186622] [] sync_inodes_sb+0x7d/0x1a0 [ 4200.186624] [] sync_inodes_one_sb+0x15/0x20 [ 4200.186628] [] iterate_supers+0xcd/0xd0 [ 4200.186630] [] ? SyS_tee+0x2a0/0x2a0 [ 4200.186632] [] sys_sync+0x3a/0xa0 [ 4200.186636] [] do_fast_syscall_32+0x9f/0x160 [ 4200.186639] [] sysenter_past_esp+0x3d/0x61 [ 4200.186641] INFO: task stress-ng:23242 blocked for more than 120 seconds. [ 4200.187628] Tainted: G OE 4.4.0-142-generic #168-Ubuntu [ 4200.188667] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4200.189947] stress-ng D c1214654 0 23242 1 0x0004 [ 4200.189952] c011bebc 0086 c011bea4 c1214654 dd922680 65d2d986 03a3 [ 4200.189955] 65bb3d70 03a3 d8185dc0 cef0b200 c011c000 d00ce5e0 c011bf08 c011bec8 [ 4200.189958] c17e194d c011bf08 c011bef0 c12146ad cef0b200 c10b5340 c5bc9edc [ 4200.189962] Call Trace: [ 4200.189965] [] ? wb_queue_work+0xe4/0xf0 [ 4200.189968] [] schedule+0x2d/0x80 [ 4200.189971] [] wb_wait_for_completion+0x4d/0x90 [ 4200.189973] [] ? wake_atomic_t_function+0x70/0x70 [ 4200.189975] [] sync_inodes_sb+0x7d/0x1a0 [ 4200.189978] [] sync_inodes_one_sb+0x15/0x20 [ 4200.189980] [] iterate_supers+0xcd/0xd0 [ 4200.189983] [] ? SyS_tee+0x2a0/0x2a0 [ 4200.189985] [] sys_sync+0x3a/0xa0 [ 4200.189987] [] do_fast_syscall_32+0x9f/0x160 [ 4200.189989] [] sysenter_past_esp+0x3d/0x61 This is not a regression, different call traces or errors have been reported by older versions. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: Confirmed ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - linux 4.4.0-142.168 ADT test failure with linux 4.4.0-142.168 + linux 4.4.0-142.168 ADT test failure (ubuntu_vfat_stress): hung task on i386 ** Description changed: Testing failed on: - i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190201_082722_4cb3e@/log.gz + i386:
[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
I tried the glamor / tearfree - advice, but: with NO success; still flickering. And, btw.: I don't think the flickering is an Xorg-issue; it starts in "textmode" (!!) as soon as the radeon-kernel-driver loads. I think the kernel-driver does NOT read Xorg-configurations. Just for fun, I've tested different systems: System kernel radeon.ko result UBUNTU-14.04.5 3.13.0-164 2.36.0 O.K puppy_slacko-6.3.2 3.14.55 2.37.0 O.K. UBCD3.16.0 2.39.0 FLICKER UBUNTU 14.04.5 4.4.0-133 2.43.0 FLICKER UBUNTU 18.04.1 4.15.0-42 2.50.0 FLICKER So, I think the problem starts with a modification made in radeon.ko version 2.37.0 --> 2.39.0 Additionally I found a "kind of work-around": switch the mode several times! thus: - ignore flickering; start grafic mode - xrandr --output LVDS --mode 1440x900; sleep 2; xrandr --output LVDS --mode 1680x1050; - try that 2 ... 5 times until flickering stops! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 Status in linux package in Ubuntu: Confirmed Bug description: my laptop: HP Compaq nx9420 my grafic card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller]) attachment: the bug-apport-file Description: I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode; -> as soon as the kernel-module radeon.ko is loaded the screen starts flickering when starting the grafic-mode the flickering continues; so the screen is unusable. when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the screen does not flicker but the resolution is limited to 1400x1050 (instead of natural 1680x1050) so I can not use this as work-around when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157) the screen is o.k. NO flickering in textmode, nice grafic, NO flickering xrandr tells: 1680x1050 60.1 so I must stay on old ubuntu 14.04.05 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
It turns out that the installation without nvidia drivers and the secureboot option also causes errors. After some time using the laptop, the screen freezes and only holding down the power button allows you to turn off. Unfortunately, after switching on again, there was a problem with the grub welcome screen. I could not even enter the bios settings. There was only a black screen. I had to press the power button several times until I was able to do it after an hour. I have been using ubuntu for several years and this has never happened to me. The problem appeared a week ago on January 23. Previously, everything was fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. 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/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811406] Re: linux: 4.18.0-14.15 -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 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Release Holding - phase-changed: Friday, 01. February 2019 10:47 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 10:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811406 Title: linux: 4.18.0-14.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Friday, 01. February 2019 10:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811416] Re: linux-gcp: 4.18.0-1006.7 -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: 1811406 - phase: Release Holding - phase-changed: Friday, 01. February 2019 10:45 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 10:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811416 Title: linux-gcp: 4.18.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid 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: 1811406 phase: Holding before Release phase-changed: Friday, 01. February 2019 10:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811412] Re: linux-raspi2: 4.18.0-1009.11 -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: 1811406 - phase: Release Holding - phase-changed: Friday, 01. February 2019 10:37 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 10:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1811412 Title: linux-raspi2: 4.18.0-1009.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1811406 phase: Holding before Release phase-changed: Friday, 01. February 2019 10:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811415] Re: linux-azure: 4.18.0-1008.8 -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: 1811406 - phase: Release Holding - phase-changed: Friday, 01. February 2019 10:38 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 10:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811415 Title: linux-azure: 4.18.0-1008.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu 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 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: 1811406 phase: Holding before Release phase-changed: Friday, 01. February 2019 10:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811422] Re: linux-aws: 4.15.0-1032.34 -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: 1813779 - phase: Release Holding - phase-changed: Monday, 28. January 2019 12:20 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 10:58 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811422 Title: linux-aws: 4.15.0-1032.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 10:58 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
$ apt-cache policy linux-image-generic upower gnome-control-center gnome-shell linux-image-generic: Installed: 4.18.0.14.15 Candidate: 4.18.0.14.15 Version table: *** 4.18.0.14.15 500 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.18.0.13.14 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu cosmic-security/main amd64 Packages 4.18.0.10.11 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages upower: Installed: 0.99.8-2ubuntu0.2 Candidate: 0.99.8-2ubuntu0.2 Version table: *** 0.99.8-2ubuntu0.2 500 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.99.8-2ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 0.99.8-2 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages gnome-control-center: Installed: 1:3.30.2-1ubuntu0.18.10.2 Candidate: 1:3.30.2-1ubuntu0.18.10.2 Version table: *** 1:3.30.2-1ubuntu0.18.10.2 500 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:3.30.2-1ubuntu0.18.10.1 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 1:3.30.1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages gnome-shell: Installed: 3.30.2-0ubuntu1.18.10.1 Candidate: 3.30.2-0ubuntu1.18.10.1 Version table: *** 3.30.2-0ubuntu1.18.10.1 500 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.30.1-2ubuntu1.18.10.2 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 3.30.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Triaged Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1811252] Re: Xenial update: 4.4.169 upstream stable release
** Changed in: linux (Ubuntu Xenial)
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/1811252
Title:
Xenial update: 4.4.169 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.4.169 upstream stable release
from git://git.kernel.org/
Linux 4.4.169
ALSA: isa/wavefront: prevent some out of bound writes
rtc: snvs: Add timeouts to avoid kernel lockups
rtc: snvs: add a missing write sync
i2c: scmi: Fix probe error on devices with an empty SMB0001 ACPI device node
i2c: axxia: properly handle master timeout
cifs: In Kconfig CONFIG_CIFS_POSIX needs depends on legacy (insecure cifs)
ARM: 8814/1: mm: improve/fix ARM v7_dma_inv_range() unaligned address handling
mv88e6060: disable hardware level MAC learning
libata: whitelist all SAMSUNG MZ7KM* solid-state disks
Input: omap-keypad - fix keyboard debounce configuration
clk: mmp: Off by one in mmp_clk_add()
ide: pmac: add of_node_put()
drivers/tty: add missing of_node_put()
drivers/sbus/char: add of_node_put()
sbus: char: add of_node_put()
SUNRPC: Fix a potential race in xprt_connect()
bonding: fix 802.3ad state sent to partner when unbinding slave
ARC: io.h: Implement reads{x}()/writes{x}()
drm/msm: Grab a vblank reference when waiting for commit_done
x86/earlyprintk/efi: Fix infinite loop on some screen widths
scsi: vmw_pscsi: Rearrange code to avoid multiple calls to free_irq during
unload
scsi: libiscsi: Fix NULL pointer dereference in iscsi_eh_session_reset
mac80211_hwsim: fix module init error paths for netlink
mac80211: Fix condition validating WMM IE
mac80211: don't WARN on bad WMM parameters from buggy APs
f2fs: fix a panic caused by NULL flush_cmd_control
Revert "drm/rockchip: Allow driver to be shutdown on reboot/kexec"
powerpc/msi: Fix NULL pointer access in teardown code
tracing: Fix memory leak of instance function hash filters
tracing: Fix memory leak in set_trigger_filter()
MMC: OMAP: fix broken MMC on OMAP15XX/OMAP5910/OMAP310
aio: fix spectre gadget in lookup_ioctx
pinctrl: sunxi: a83t: Fix IRQ offset typo for PH11
powerpc/boot: Fix random libfdt related build errors
timer/debug: Change /proc/timer_list from 0444 to 0400
lib/interval_tree_test.c: allow users to limit scope of endpoint
lib/rbtree-test: lower default params
lib/rbtree_test.c: make input module parameters
lib/interval_tree_test.c: allow full tree search
lib/interval_tree_test.c: make test options module parameters
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811252/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811194] Re: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
I believe this is fixed (worked around, by skipping the test when ADJ_OFFSET is detected) by upstream commit 1416270f4a1ae83ea84156ceba19a66a8f88be1f: commit 1416270f4a1ae83ea84156ceba19a66a8f88be1f Author: John Stultz Date: Tue May 29 19:12:18 2018 -0700 selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock adjustments are in progress This commit is included upstream in v4.19, already included in cosmic (and disco) via bug 1794597, already included in xenial via bug 1798587. Does not appear that it's in bionic yet. ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811194 Title: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: This issue cannot be reproduced across all of our SUTs, issue found on node secchi (3 out of 3). And sometimes on node amaura (2 out of 4) selftests: raw_skew WARNING: ADJ_OFFSET in progress, this will cause inaccurate results Estimating clock drift: 29.255(est) 30.529(act) [FAILED] Bail out! Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 1..0 not ok 1..7 selftests: raw_skew [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 03:58 seq crw-rw 1 root audio 116, 33 Jan 10 03:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 10 06:25:41 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. Bus 001 Device 002: ID :0001 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S2600WFT PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9210e07a-fd34-474c-b77e-f7508f27e234 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C620.86B.01.00.0294.101220161543 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S2600WFT dmi.board.vendor: Intel Corporation dmi.board.version: H48104-410 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrSE5C620.86B.01.00.0294.101220161543:bd10/12/2016:svnIntelCorporation:pnS2600WFT:pvr:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S2600WFT dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1811194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1811846] Re: linux: 4.4.0-142.168 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811846 Title: linux: 4.4.0-142.168 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released 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: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released 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 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Friday, 01. February 2019 14:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811854] Re: linux-raspi2: 4.4.0-1103.111 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing 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: 1811846 - phase: Testing - phase-changed: Monday, 28. January 2019 12:59 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1811854 Title: linux-raspi2: 4.4.0-1103.111 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released 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: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811854/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811851] Re: linux-aws: 4.4.0-1075.85 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing 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: 1811846 - phase: Testing - phase-changed: Monday, 28. January 2019 11:55 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- 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/1811851 Title: linux-aws: 4.4.0-1075.85 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811851/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811846] Re: linux: 4.4.0-142.168 -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 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Testing - phase-changed: Monday, 28. January 2019 13:01 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 14:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811846 Title: linux: 4.4.0-142.168 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released 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: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released 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 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Friday, 01. February 2019 14:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811847] Re: linux-aws: 4.4.0-1038.41 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing 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: 1811846 - phase: Testing - phase-changed: Monday, 28. January 2019 11:51 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- 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/1811847 Title: linux-aws: 4.4.0-1038.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
** Package changed: linux-hwe (Ubuntu) => linux-meta-hwe (Ubuntu) -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux-azure package in Ubuntu: Confirmed Status in linux-meta-hwe package in Ubuntu: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux-meta-hwe source package in Bionic: Confirmed Status in linux-azure source package in Cosmic: Confirmed Status in linux-meta-hwe source package in Cosmic: Confirmed Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-hwe (Ubuntu Bionic) 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux-azure package in Ubuntu: Confirmed Status in linux-meta-hwe package in Ubuntu: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux-meta-hwe source package in Bionic: Confirmed Status in linux-azure source package in Cosmic: Confirmed Status in linux-meta-hwe source package in Cosmic: Confirmed Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806380] Re: linux-buildinfo: pull out ABI information into its own package
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806380 Title: linux-buildinfo: pull out ABI information into its own package Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Bug description: We have an increasing amount of ABI information which is currently exposed via the primary binary packages. Little to none of this is relevant to the end-user and does not deserve to use up space on their system. Also the kernel developer who needs to update this data does not want to downloads 10s of Megabytes of binary packages to extract this information. Pull it all out and generate all data that would require the actual binaries at kernel build time, package all of this information into a new linux-buildinfo package for consumption. This package is not installed by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-hwe (Ubuntu Cosmic) 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux-azure package in Ubuntu: Confirmed Status in linux-meta-hwe package in Ubuntu: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux-meta-hwe source package in Bionic: Confirmed Status in linux-azure source package in Cosmic: Confirmed Status in linux-meta-hwe source package in Cosmic: Confirmed Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system
Please please please, pretty please xD On Fri, Feb 1, 2019 at 4:41 PM risafov <1721...@bugs.launchpad.net> wrote: > Same for me: > ASUS UX370UA > Linux 18.10 > Kernel 4.20 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1721909 > > Title: > Goodix GF3208 (fingerprint reader) not being recognised by > kernel/system > > Status in Linux: > New > Status in linux package in Ubuntu: > Confirmed > > Bug description: > The Goodix GF3208 is not being recognised by the system (Dell Inspiron > 15 7577). What's worse is that it isn't even showing the manufacturer > vendor id information when doing: > > $ lsusb > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 004: ID 27c6:5301 > Bus 001 Device 003: ID 8087:0a2b Intel Corp. > Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver > Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Note that the vendor id 27c6 should at least say "Shenzhen Huiding > Technology Co., Ltd." as per > > https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings > /vendor-prefixes.txt > > Will/has support been made for the Goodix GF3208 Fingerprint > reader/scanner? > > Thanks in advance, > Haz > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1 > ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 > Uname: Linux 4.10.0-35-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.10 > Architecture: amd64 > CurrentDesktop: Unity > Date: Sat Oct 7 04:03:25 2017 > InstallationDate: Installed on 2017-10-01 (5 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > SourcePackage: linux-hwe > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/linux/+bug/1721909/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: The Goodix GF3208 is not being recognised by the system (Dell Inspiron 15 7577). What's worse is that it isn't even showing the manufacturer vendor id information when doing: $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5301 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Note that the vendor id 27c6 should at least say "Shenzhen Huiding Technology Co., Ltd." as per https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings /vendor-prefixes.txt Will/has support been made for the Goodix GF3208 Fingerprint reader/scanner? Thanks in advance, Haz ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 7 04:03:25 2017 InstallationDate: Installed on 2017-10-01 (5 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811853] Re: linux-kvm: 4.4.0-1040.46 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing 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: 1811846 - phase: Testing - phase-changed: Monday, 28. January 2019 11:58 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1811853 Title: linux-kvm: 4.4.0-1040.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system
Same for me: ASUS UX370UA Linux 18.10 Kernel 4.20 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: The Goodix GF3208 is not being recognised by the system (Dell Inspiron 15 7577). What's worse is that it isn't even showing the manufacturer vendor id information when doing: $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5301 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Note that the vendor id 27c6 should at least say "Shenzhen Huiding Technology Co., Ltd." as per https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings /vendor-prefixes.txt Will/has support been made for the Goodix GF3208 Fingerprint reader/scanner? Thanks in advance, Haz ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 7 04:03:25 2017 InstallationDate: Installed on 2017-10-01 (5 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed
The delivery status gives: : Host or domain name not found. Name service error for name=vger.linux.org type=A: Host not found -- message/delivery-status -- Reporting-MTA: dns; mail1.protonmail.ch X-Postfix-Queue-ID: A70A02008274 X-Postfix-Sender: rfc822; t...@selwyn.cc Arrival-Date: Fri, 1 Feb 2019 10:37:45 + (UTC) Final-Recipient: rfc822; linux-...@vger.linux.org Original- Recipient: rfc822;linux-...@vger.linux.org Action: failed Status: 5.4.4 Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error for name=vger.linux.org type=A: Host not found -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812561 Title: [MacBookPro11,5] wakes up and suspends in a loop while closed Status in linux package in Ubuntu: Triaged Bug description: Similar bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/ The first time suspending works great but after that suspending causes the laptop to wake up regardless of the method used to suspend. WORKAROUND: Disable XHC1 prior to sleeping via: # echo XHC1 > /proc/acpi/wakeup Sidenote: thanks to penalvch for explaining how to report this! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: siilwyn1852 F pulseaudio /dev/snd/controlC1: siilwyn1852 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 13:40:14 2019 InstallationDate: Installed on 2019-01-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
Thanks for trying the tearfree option! (ok, it don't work) By reading: https://wiki.ubuntu.com/Kernel/MainlineBuilds I discovered: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D which would allow to download prebuild .deb for old mwainline kernels. I am a bit sceptical if new versions of ubuntu would boot with so old versions. But it could help someone pinpoint the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 Status in linux package in Ubuntu: Confirmed Bug description: my laptop: HP Compaq nx9420 my grafic card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller]) attachment: the bug-apport-file Description: I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode; -> as soon as the kernel-module radeon.ko is loaded the screen starts flickering when starting the grafic-mode the flickering continues; so the screen is unusable. when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the screen does not flicker but the resolution is limited to 1400x1050 (instead of natural 1680x1050) so I can not use this as work-around when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157) the screen is o.k. NO flickering in textmode, nice grafic, NO flickering xrandr tells: 1680x1050 60.1 so I must stay on old ubuntu 14.04.05 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764956] Re: Guests using IBRS incur a large performance penalty
** Changed in: linux (Ubuntu Xenial)
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/1764956
Title:
Guests using IBRS incur a large performance penalty
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
In Progress
Status in linux source package in Xenial:
Fix Committed
Bug description:
[Impact]
the IBRS would be mistakenly enabled in the host when the switching
from an IBRS-enabled VM and that causes the performance overhead in
the host. The other condition could also mistakenly disables the IBRS
in VM when context-switching from the host. And this could be
considered a CVE host.
[Fix]
The patch fixes the logic inside the x86_virt_spec_ctrl that it checks
the ibrs_enabled and _or_ the hostval with the SPEC_CTRL_IBRS as the
x86_spec_ctrl_base by default is zero. Because the upstream
implementation is not equal to the Xenial's implementation. Upstream
doesn't use the IBRS as the formal fix. So, by default, it's zero.
On the other hand, after the VM exit, the SPEC_CTRL register also
needs to be saved manually by reading the SPEC_CTRL MSR as the MSR
intercept is disabled by default in the hardware_setup(v4.4) and
vmx_init(v3.13). The access to SPEC_CTRL MSR in VM is direct and
doesn't trigger a trap. So, the vmx_set_msr() function isn't called.
The v3.13 kernel hasn't been tested. However, the patch can be viewed
at:
http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=sf00191076-sru
The v4.4 patch:
http://kernel.ubuntu.com/git/gavinguo/ubuntu-xenial.git/log/?h=sf00191076-spectre-v2-regres-backport-juerg
[Test]
The patch has been tested on the 4.4.0-140.166 and works fine.
The reproducing environment:
Guest kernel version: 4.4.0-138.164
Host kernel version: 4.4.0-140.166
(host IBRS, guest IBRS)
- 1). (0, 1).
The case can be reproduced by the following instructions:
guest$ echo 1 | sudo tee /proc/sys/kernel/ibrs_enabled
1
host$ cat /proc/sys/kernel/ibrs_enabled
0
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
110001001010
Some of the IBRS bit inside the SPEC_CTRL MSR are mistakenly
enabled.
host$ taskset -c 5 stress-ng -c 1 --cpu-ops 2500
stress-ng: info: [11264] defaulting to a 86400 second run per stressor
stress-ng: info: [11264] dispatching hogs: 1 cpu
stress-ng: info: [11264] cache allocate: default cache size: 35840K
stress-ng: info: [11264] successful run completed in 33.48s
The host kernel didn't notice the IBRS bit is enabled. So, the situation
is the same as "echo 2 > /proc/sys/kernel/ibrs_enabled" in the host.
And running the stress-ng is a pure userspace CPU capability
calculation. So, the performance downgrades to about 1/3. Without the
IBRS enabled, it needs about 10s.
- 2). (1, 1) disables IBRS in host -> (0, 1) actually it becomes (0, 0).
The guest IBRS has been mistakenly disabled.
guest$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
host$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
host$ echo 0 | sudo tee /proc/sys/kernel/ibrs_enabled
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764956/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed
Selwyn: "! I could not send the email though, the email address "linux- u...@vger.linux.org" seems invalid." If you post the email source of the message sent, and what you may have received in a response, then this may be assessed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812561 Title: [MacBookPro11,5] wakes up and suspends in a loop while closed Status in linux package in Ubuntu: Triaged Bug description: Similar bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/ The first time suspending works great but after that suspending causes the laptop to wake up regardless of the method used to suspend. WORKAROUND: Disable XHC1 prior to sleeping via: # echo XHC1 > /proc/acpi/wakeup Sidenote: thanks to penalvch for explaining how to report this! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: siilwyn1852 F pulseaudio /dev/snd/controlC1: siilwyn1852 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 13:40:14 2019 InstallationDate: Installed on 2019-01-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811856] Re: linux: 3.13.0-165.215 -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 1811857 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Testing - phase-changed: Monday, 28. January 2019 11:49 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 12:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811856 Title: linux: 3.13.0-165.215 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released 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 1811857 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Friday, 01. February 2019 12:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814241] Re: linux-oem: 4.15.0-1033.38 -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: 1813779 - phase: Packaging - phase-changed: Friday, 01. February 2019 10:39 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 01. February 2019 13:38 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1814241 Title: linux-oem: 4.15.0-1033.38 -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: 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-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1813779 phase: Holding before Promote to Proposed phase-changed: Friday, 01. February 2019 13:38 UTC reason: promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813423] Re: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A"
there is no separate modesetting driver anymore, it's folded in the server that said, the bug is most likely in the kernel ** Package changed: xserver-xorg-video-modesetting (Ubuntu) => xorg- server (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/1813423 Title: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A" Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: My system keeps freezing on a brand new install of Kubuntu 18.10, always with the kern.log error "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235) time 486 us, min 763, max 767, scanline start 760, end 783" I think it's probably a duplicate of these bugs which were closed unresolved: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was on an older version of Ubuntu) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because it was a duplicate of the first bug) It happens far more frequently if I have desktop effects turned on, and far less frequently when using a live USB key (at always happens eventually though. Usually once every few hours.) Please advise how I can help triage / test. My system is a new install now, so I'm perfectly willing to modify / reinstall to help testing (I've reinstalled 5 times to test things, but never managed to find a solution) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 26 14:19:52 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227a] InstallationDate: Installed on 2019-01-18 (8 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227A dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 14 Notebook PC dmi.product.sku: J9L01UA#ABL dmi.product.version: 096C110800405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811856] Re: linux: 3.13.0-165.215 -proposed tracker
Verification tests completed successfully. ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811856 Title: linux: 3.13.0-165.215 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released 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 1811857 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Monday, 28. January 2019 11:49 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804604] Re: SRU: Fix thinkpad 11e 3rd boot hang
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1804604 Title: SRU: Fix thinkpad 11e 3rd boot hang Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Bug description: [Impact] ThinkPad 11e 3rd boot hang in systemd loading. [Fix] When boot case acpi_lpss_resume() get called without a corresponding acpi_lpss_suspend() having been called. Thus force setting the flag during boot. [Test Case] Tested on Thinkpad 11e 3rd. Booting successfully. [Regression Potential] Low, upstream fix cherry-picked. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1804604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811860] Re: Display ports on Lenovo docking station stopped working after upgrade of linux-firmware 1.173.2 -> 1.173.3
Can you provide the output of lsmod and dmesg with the laptop attached to the dock and 1.173.3 installed? I still can't see how any of the updates between those versions are to files which would be used by your laptop. For reference, here is is the list of files added or updated between 1.173.2 and 1.173.3. The amdgpu files won't be used at all by the bionic 4.15 kernel, but you have Intel graphics hardware anyway. You do have an Intel wireless card, but not one which uses the wireless firmware which was updated. The others are not for devices which would be found in a laptop. amdgpu/vegam_ce.bin amdgpu/vegam_me.bin amdgpu/vegam_mec.bin amdgpu/vegam_mec2.bin amdgpu/vegam_pfp.bin amdgpu/vegam_rlc.bin amdgpu/vegam_sdma.bin amdgpu/vegam_sdma1.bin amdgpu/vegam_smc.bin amdgpu/vegam_uvd.bin amdgpu/vegam_vce.bin iwlwifi-9000-pu-b0-jf-b0-34.ucode iwlwifi-9260-th-b0-jf-b0-34.ucode mellanox/mlxsw_spectrum-13.1620.192.mfa2 qed/qed_init_values_zipped-8.37.2.0.bin -- 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/1811860 Title: Display ports on Lenovo docking station stopped working after upgrade of linux-firmware 1.173.2 -> 1.173.3 Status in linux-firmware package in Ubuntu: Incomplete Bug description: Lenovo Carbon X1 running on Lenovo Thinkpad Ultra Dock I have only been able to attach a single monitor to the docking station before the upgrade of linux-firmware. After todays upgrade from 1.173.2 to 1.173.3, none of the outputs work anymore. The Ultra Dock has two DP, an HDMI, and a VGA output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 16:31:39 2019 Dependencies: InstallationDate: Installed on 2018-12-03 (42 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1811860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811647] Re: Xenial update: 4.4.170 upstream stable release
** Changed in: linux (Ubuntu Xenial) 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/1811647 Title: Xenial update: 4.4.170 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.170 upstream stable release from git://git.kernel.org/ Linux 4.4.170 power: supply: olpc_battery: correct the temperature units intel_th: msu: Fix an off-by-one in attribute store genwqe: Fix size check ceph: don't update importing cap's mseq when handing cap export iommu/vt-d: Handle domain agaw being less than iommu agaw 9p/net: put a lower bound on msize b43: Fix error in cordic routine gfs2: Fix loop in gfs2_rbm_find dlm: memory leaks on error path in dlm_user_request() dlm: lost put_lkb on error path in receive_convert() and receive_unlock() dlm: possible memory leak on error path in create_lkb() dlm: fixed memory leaks after failed ls_remove_names allocation ALSA: usb-audio: Fix an out-of-bound read in create_composite_quirks ALSA: usb-audio: Avoid access before bLength check in build_audio_procunit() ALSA: cs46xx: Potential NULL dereference in probe crypto: x86/chacha20 - avoid sleeping with preemption disabled sunrpc: use SVC_NET() in svcauth_gss_* functions sunrpc: fix cache_head leak due to queued request mm, devm_memremap_pages: kill mapping "System RAM" support mm, devm_memremap_pages: mark devm_memremap_pages() EXPORT_SYMBOL_GPL hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined fork: record start_time late scsi: zfcp: fix posting too many status read buffers leading to adapter shutdown Input: omap-keypad - fix idle configuration to not block SoC idle states scsi: bnx2fc: Fix NULL dereference in error handling xfrm: Fix bucket count reported to userspace checkstack.pl: fix for aarch64 Input: restore EV_ABS ABS_RESERVED ARM: imx: update the cpu power up timing setting on i.mx6sx powerpc: Fix COFF zImage booting on old powermacs spi: bcm2835: Unbreak the build of esoteric configs x86/kvm/vmx: do not use vm-exit instruction length for fast MMIO when running nested CIFS: Fix error mapping for SMB2_LOCK command which caused OFD lock problem MIPS: Align kernel load address to 64KB MIPS: Ensure pmd_present() returns false after pmd_mknotpresent() media: vivid: free bitmap_cap when updating std/timings/etc. cdc-acm: fix abnormal DATA RX issue for Mediatek Preloader. spi: bcm2835: Avoid finishing transfer prematurely in IRQ mode spi: bcm2835: Fix book-keeping of DMA termination spi: bcm2835: Fix race on DMA termination ext4: force inode writes when nfsd calls commit_metadata() ext4: fix EXT4_IOC_GROUP_ADD ioctl ext4: missing unlock/put_page() in ext4_try_to_write_inline_data() ext4: fix possible use after free in ext4_quota_enable perf pmu: Suppress potential format-truncation warning KVM: x86: Use jmp to invoke kvm_spurious_fault() from .fixup Input: elan_i2c - add ACPI ID for touchpad in ASUS Aspire F5-573G usb: r8a66597: Fix a possible concurrency use-after-free bug in r8a66597_endpoint_disable() USB: serial: option: add Fibocom NL678 series USB: serial: pl2303: add ids for Hewlett-Packard HP POS pole displays ALSA: hda/tegra: clear pending irq handlers ALSA: hda: add mute LED support for HP EliteBook 840 G4 ALSA: emux: Fix potential Spectre v1 vulnerabilities ALSA: pcm: Fix potential Spectre v1 vulnerability ALSA: emu10k1: Fix potential Spectre v1 vulnerabilities ALSA: rme9652: Fix potential Spectre v1 vulnerability sock: Make sock->sk_stamp thread-safe gro_cell: add napi_disable in gro_cells_destroy xen/netfront: tolerate frags with no data VSOCK: Send reset control packet when socket is partially bound vhost: make sure used idx is seen before log in vhost_add_used_n() sctp: initialize sin6_flowinfo for ipv6 addrs in sctp_inet6addr_event packet: validate address length if non-zero packet: validate address length netrom: fix locking in nr_find_socket() isdn: fix kernel-infoleak in capi_unlocked_ioctl ipv6: explicitly initialize udp6_addr in udp_sock_create6() ieee802154: lowpan_header_create check must check daddr ibmveth: fix DMA unmap error in ibmveth_xmit_start error path ax25: fix a use-after-free in ax25_fillin_cb() ipv4: Fix potential
[Kernel-packages] [Bug 1811423] Re: linux-azure: 4.15.0-1037.39 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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: 1813779 - phase: Testing - phase-changed: Monday, 28. January 2019 11:51 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 11:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- 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/1811423 Title: linux-azure: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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-dnu 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: 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: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
I'm also getting a Segmentation Fault with Gimp:
```
GNU Image Manipulation Program version 2.10.6
git-describe: GIMP_2_10_4-278-g0a8173ffde
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
8.2.0-4ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-4ubuntu1)
using GEGL version 0.4.8 (compiled against version 0.4.8)
using GLib version 2.58.1 (compiled against version 2.57.2)
using GdkPixbuf version 2.38.0 (compiled against version 2.36.12)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.0 (compiled against version 2.13.0)
using Cairo version 1.15.12 (compiled against version 1.15.12)
```
> fatal error: Segmentation fault
Stack trace:
```
# Stack traces obtained from PID 9501 - Thread 9501 #
[New LWP 9502]
[New LWP 9503]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (fd=12, buf=0x7ffd389644d0, nbytes=256) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target IdFrame
* 1Thread 0x7fc9dee16e00 (LWP 9501) "gimp-2.10" __libc_read (fd=12,
buf=0x7ffd389644d0, nbytes=256) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7fc9dcf25700 (LWP 9502) "gmain" 0x7fc9e1c9c6d9 in
__GI___poll (fds=0x558c28f8feb0, nfds=1, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
3Thread 0x7fc9dc724700 (LWP 9503) "gdbus" 0x7fc9e1c9c6d9 in
__GI___poll (fds=0x558c28fa9890, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
Thread 3 (Thread 0x7fc9dc724700 (LWP 9503)):
#0 0x7fc9e1c9c6d9 in __GI___poll (fds=0x558c28fa9890, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
sc_ret =
#1 0x7fc9e1f73e46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7fc9e1f741d2 in g_main_loop_run () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7fc9e28ef7b6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
No symbol table info available.
#4 0x7fc9e1f9c135 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7fc9e1d80164 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140504963630848,
8221769982414159155, 140725552829518, 140725552829519, 140725552829648,
140504963627264, -8247743653170905805, -8247679106546401997}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call =
#6 0x7fc9e1ca8def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 2 (Thread 0x7fc9dcf25700 (LWP 9502)):
#0 0x7fc9e1c9c6d9 in __GI___poll (fds=0x558c28f8feb0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
sc_ret =
#1 0x7fc9e1f73e46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7fc9e1f73f6c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7fc9e1f73fb1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7fc9e1f9c135 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7fc9e1d80164 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf =
[Kernel-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
frederick@graphMetrix-1:~$ sudo dpkg -P libnvidia-gl-390:i386 libgl1-mesa-dri:i386 [sudo] password for frederick: dpkg: dependency problems prevent removal of libnvidia-gl-390:i386: libnvidia-ifr1-390:i386 depends on libnvidia-gl-390. dpkg: error processing package libnvidia-gl-390:i386 (--purge): dependency problems - not removing dpkg: dependency problems prevent removal of libgl1-mesa-dri:i386: libglx-mesa0:i386 depends on libgl1-mesa-dri. dpkg: error processing package libgl1-mesa-dri:i386 (--purge): dependency problems - not removing Errors were encountered while processing: libnvidia-gl-390:i386 libgl1-mesa-dri:i386 -- 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/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Triaged Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812229] Re: Bionic update: upstream stable patchset 2019-01-17
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812229 Title: Bionic update: upstream stable patchset 2019-01-17 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-01-17 (ported from v4.14.58 and v4.17.10) from git://git.kernel.org/ scsi: sd_zbc: Fix variable type and bogus comment KVM/Eventfd: Avoid crash when assign and deassign specific eventfd in parallel. x86/apm: Don't access __preempt_count with zeroed fs x86/events/intel/ds: Fix bts_interrupt_threshold alignment x86/MCE: Remove min interval polling limitation fat: fix memory allocation failure handling of match_strdup() ALSA: hda/realtek - Add Panasonic CF-SZ6 headset jack quirk ARCv2: [plat-hsdk]: Save accl reg pair by default ARC: Fix CONFIG_SWAP ARC: configs: Remove CONFIG_INITRAMFS_SOURCE from defconfigs ARC: mm: allow mprotect to make stack mappings executable mm: memcg: fix use after free in mem_cgroup_iter() mm/huge_memory.c: fix data loss when splitting a file pmd cpufreq: intel_pstate: Register when ACPI PCCH is present vfio/pci: Fix potential Spectre v1 stop_machine: Disable preemption when waking two stopper threads drm/i915: Fix hotplug irq ack on i965/g4x drm/nouveau: Use drm_connector_list_iter_* for iterating connectors drm/nouveau: Avoid looping through fake MST connectors gen_stats: Fix netlink stats dumping in the presence of padding ipv4: Return EINVAL when ping_group_range sysctl doesn't map to user ns ipv6: fix useless rol32 call on hash ipv6: ila: select CONFIG_DST_CACHE lib/rhashtable: consider param->min_size when setting initial table size net: diag: Don't double-free TCP_NEW_SYN_RECV sockets in tcp_abort net: Don't copy pfmemalloc flag in __copy_skb_header() skbuff: Unconditionally copy pfmemalloc in __skb_clone() net/ipv4: Set oif in fib_compute_spec_dst net: phy: fix flag masking in __set_phy_supported ptp: fix missing break in switch qmi_wwan: add support for Quectel EG91 tg3: Add higher cpu clock for 5762. hv_netvsc: Fix napi reschedule while receive completion is busy net/mlx4_en: Don't reuse RX page when XDP is set net: systemport: Fix CRC forwarding check for SYSTEMPORT Lite ipv6: make DAD fail with enhanced DAD when nonce length differs net: usb: asix: replace mii_nway_restart in resume path alpha: fix osf_wait4() breakage cxl_getfile(): fix double-iput() on alloc_file() failures powerpc/powernv: Fix save/restore of SPRG3 on entry/exit from stop (idle) xhci: Fix perceived dead host due to runtime suspend race with event handler KVM: irqfd: fix race between EPOLLHUP and irq_bypass_register_consumer x86/kvmclock: set pvti_cpu0_va after enabling kvmclock ALSA: hda/realtek - Yet another Clevo P950 quirk entry drm/amdgpu: Reserve VM root shared fence slot for command submission (v3) rhashtable: add restart routine in rhashtable_free_and_destroy() sch_fq_codel: zero q->flows_cnt when fq_codel_init fails sctp: introduce sctp_dst_mtu sctp: fix the issue that pathmtu may be set lower than MINSEGMENT net: aquantia: vlan unicast address list correct handling drm_mode_create_lease_ioctl(): fix open-coded filp_clone_open() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811857] Re: linux-lts-trusty: 3.13.0-165.215~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing 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: 1811856 - phase: Testing - phase-changed: Monday, 28. January 2019 11:58 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 12:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- 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/1811857 Title: linux-lts-trusty: 3.13.0-165.215~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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1811856 phase: Holding before Release phase-changed: Friday, 01. February 2019 12:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
