[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812845 Title: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: [ 494.357824] [ cut here ] [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! [ 494.365079] invalid opcode: [#1] SMP [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] [ 494.453657] EIP: kunmap_high+0xaa/0xb0 [ 494.457571] EFLAGS: 00010246 CPU: 2 [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 [ 494.486353] Call Trace: [ 494.488967] kunmap+0x3e/0x50 [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] [ 494.497226] ? update_load_avg+0x64f/0x830 [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] [ 494.513058] bio_endio+0xb9/0x110 [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] [ 494.536621] process_one_work+0x1b9/0x3d0 [ 494.540799] worker_thread+0x37/0x420 [ 494.544628] kthread+0xf0/0x110 [ 494.547931] ? process_one_work+0x3d0/0x3d0 [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.562701] ret_from_fork+0x2e/0x38 [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- Follow up with CPU soft lockup. Please find the attachment for the complete log. 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 i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 11:54 seq crw-rw 1 root audio 116, 33 Jan 22 11:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 11:54:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=6aaa11f6-d386-4c0c-b4b8-38e6c408980a ro
[Kernel-packages] [Bug 1746971] Re: Please enable PAGE_POISONING
*** This bug is a duplicate of bug 1783651 *** https://bugs.launchpad.net/bugs/1783651 Enabled in 4.18 and newer. ** This bug has been marked a duplicate of bug 1783651 Please enable CONFIG_PAGE_POISONING -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746971 Title: Please enable PAGE_POISONING Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Hi, page poising is currently disabled in Ubuntu kernels: $ grep PAGE_POISON /boot/config-4.13.0-32-generic # CONFIG_PAGE_POISONING is not set It is also disabled in mainline kernels: $ grep PAGE_POISON /boot/config-4.14.16-041416-generic # CONFIG_PAGE_POISONING is not set On the contrary, it is enabled in Debian stretch and buster/sid kernels: # grep PAGE_POISON /boot/config-* /boot/config-4.9.0-5-amd64:CONFIG_PAGE_POISONING=y /boot/config-4.9.0-5-amd64:CONFIG_PAGE_POISONING_NO_SANITY=y /boot/config-4.9.0-5-amd64:# CONFIG_PAGE_POISONING_ZERO is not set $ grep PAGE_POISON /boot/config-* /boot/config-4.14.0-3-amd64:CONFIG_PAGE_POISONING=y /boot/config-4.14.0-3-amd64:CONFIG_PAGE_POISONING_NO_SANITY=y /boot/config-4.14.0-3-amd64:# CONFIG_PAGE_POISONING_ZERO is not set It is an interesting kernel hardening feature, so could you please enable those options in Ubuntu and mainline kernels? Some background information is here: https://outflux.net/blog/archives/2016/09/30/security-things-in- linux-v4-6/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 3167 F pulseaudio CurrentDesktop: KDE Date: Fri Feb 2 09:47:37 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26 MachineType: Dell Inc. Latitude E6520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none ecurity=apparmor enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic
ok, so can someone who's experiencing this bug run the requested command so we can collect more information? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1818134 Title: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic Status in bcmwl package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in shim-signed package in Ubuntu: Incomplete Bug description: when installing bcmwl-kernel-source to build wl.ko package version: 6.30.223.248+bdcom-0ubuntu0.2 Expected behavior: kernel module wl.ko loads. What happened: finit_module returns ENOPKG My device is: BCM4352 [14e4:43b1] (rev 03) Happened after latest OS update, downgrading kernel to 164 did not fix, downgrading package did not work. secure boot mode is off. A few others are having this issue https://ubuntuforums.org/showthread.php?t=2413303 There is a possibility it is a modaliases problem -- 2015 chagelog states that there was a capitalization problem, but I don't know how to check this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818134] 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 1818134 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 bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1818134 Title: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic Status in bcmwl package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in shim-signed package in Ubuntu: Incomplete Bug description: when installing bcmwl-kernel-source to build wl.ko package version: 6.30.223.248+bdcom-0ubuntu0.2 Expected behavior: kernel module wl.ko loads. What happened: finit_module returns ENOPKG My device is: BCM4352 [14e4:43b1] (rev 03) Happened after latest OS update, downgrading kernel to 164 did not fix, downgrading package did not work. secure boot mode is off. A few others are having this issue https://ubuntuforums.org/showthread.php?t=2413303 There is a possibility it is a modaliases problem -- 2015 chagelog states that there was a capitalization problem, but I don't know how to check this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic
There's a reasonable chance this is an issue with the lockdown kernel patches in Ubuntu 14.04, so opening a task on linux also. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1818134 Title: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic Status in bcmwl package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in shim-signed package in Ubuntu: Incomplete Bug description: when installing bcmwl-kernel-source to build wl.ko package version: 6.30.223.248+bdcom-0ubuntu0.2 Expected behavior: kernel module wl.ko loads. What happened: finit_module returns ENOPKG My device is: BCM4352 [14e4:43b1] (rev 03) Happened after latest OS update, downgrading kernel to 164 did not fix, downgrading package did not work. secure boot mode is off. A few others are having this issue https://ubuntuforums.org/showthread.php?t=2413303 There is a possibility it is a modaliases problem -- 2015 chagelog states that there was a capitalization problem, but I don't know how to check this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"
Christoper, thanks for your help. But I think this should be mailed to the following recipients instead: To: Bjørn Mork Cc: linux-...@vger.kernel.org Cc: net...@vger.kernel.org Cc: linux-ker...@vger.kernel.org And please also Cc me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819362 Title: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers" Status in linux package in Ubuntu: Triaged Bug description: I have a HUAWEI E3531 HSPA+ USB Stick When I plug it in, journalctl shows me Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 12d1:14dc on 1/9 Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind list file: No such file or directory Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 12d1:14dc to driver option Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the device ID to the Linux USB developers! Mär 10 19:21:22 pshp ModemManager[860]: Couldn't check support for device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any plugin And the modem does not work (no ttyUSBX appears) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 10 19:17:23 2019 EcryptfsInUse: Yes SourcePackage: linux-signed-hwe UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ps 1825 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93 MachineType: HP HP EliteBook 820 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.08 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.3C dmi.chassis.asset.tag: 5CG7453N9P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 820 G4 dmi.product.sku: X3T22AV dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ps 1825 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93 MachineType: HP HP EliteBook 820 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.08 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.3C dmi.chassis.asset.tag: 5CG7453N9P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias:
[Kernel-packages] [Bug 1819968] Re: Colour banding in Lenovo G50-80 laptop display (i915)
Please send a patch to upstream. Also, 18514 should change to a hex value. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819968 Title: Colour banding in Lenovo G50-80 laptop display (i915) Status in linux package in Ubuntu: Incomplete Bug description: Colour bandind is visible everywhere in the system. I believe it's not a hardware problem, since booting with 'nomodeset' works as expected and the previously installed Ubuntu 14.04 also worked. I tried installing kernel 4.18.0-16.17 from ppa:canonical-kernel- team/ppa but the problem remained. There were already similar bugs, https://bugs.launchpad.net/bugs/1749420 , https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794387 and https://bugs.launchpad.net/bugs/1788308, but the fixes provided for those bugs did not work for my specific monitor. cat /proc/version_signature Ubuntu 4.15.0-46.49-generic 4.15.18 sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 0b) Subsystem: Lenovo Haswell-ULT DRAM Controller [17aa:390b] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: hsw_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:390b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
Please test this kernel: https://people.canonical.com/~khfeng/lp1814069-2/ Cherry-picked additional two commits: 916c5e1413be058d1c1f6e502db350df890730ce b19b46346f483ae055fa027cb2d5c2ca91484b91 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu stuck on booting on HyperV Server 2008R2. I saw kernel messages, seems to load ram image the boot is stuck. Seems to be a problem with hyperv drivers propably harddrive. Reverted back to the previous kernel. Description:Ubuntu 18.04.1 LTS Release:18.04Description:Ubuntu 18.04.1 LTS Release:18.04 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 08:52 seq crw-rw 1 root audio 116, 33 Jan 31 08:52 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: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 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 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090004 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819881] Re: [CONFIG] please enable highdpi font FONT_TER16x32
Patch available in Disco. Porting to T/X/B/C ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) 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/1819881 Title: [CONFIG] please enable highdpi font FONT_TER16x32 Status in linux package in Ubuntu: Fix Released 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: In Progress Status in linux source package in Cosmic: In Progress Bug description: [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813820] Re: Waking from Suspend causes screen to appear with grey static (like a TV with no signal)
Please file an upstream bug at https://bugs.freedesktop.org/ Product: DRI Component: DRM/amdgpu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813820 Title: Waking from Suspend causes screen to appear with grey static (like a TV with no signal) Status in linux package in Ubuntu: Confirmed Bug description: I am running Kubuntu 18.10. This is the PH517-61 Acer Predator Helios 500 with the Ryzen processor. My first issue I need to deal with is Suspend. I have temporarily disabled suspend in the kcmshell5 configuration. If I do let the laptop suspend and then hit the keyboard I get what appears to be a 1950s TV with no signal. At this point I manually power down and then power up again and am able to view things on screen. Running these commands I get this information: $ journalctl -b -g suspend Compiled without pattern matching support $ journalctl -b -p3 -- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54 CST. -- Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xdf775000-0xdf778fff] Jan 28 20:40:42 craig-Predator-PH517-61 spice-vdagent[2100]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 $ uname -a Linux craig-Predator-PH517-61 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This is a Vega 56 card but Kubuntu seems to think it is a Vega 64: $ lspci -k | grep -EA3 'VGA|3D|Display' 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c7) Subsystem: Acer Incorporated [ALI] Vega 10 XT [Radeon RX Vega 64] Kernel driver in use: amdgpu Kernel modules: amdgpu $ glxinfo | grep "OpenGL version" OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.2 I will attempt to flesh this out more when I get home. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: craig 2094 F pulseaudio /dev/snd/controlC0: craig 2094 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2019-01-28 (1 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Acer Predator PH517-61 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=5f69d6c1-716a-41ac-a88c-b271a71ce5a0 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 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 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/12/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Cayman_PRS dmi.board.vendor: PRS dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd10/12/2018:svnAcer:pnPredatorPH517-61:pvrV1.07:rvnPRS:rnCayman_PRS:rvrV1.07:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Predator Helios 500 dmi.product.name: Predator PH517-61 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813820] Re: Waking from Suspend causes screen to appear with grey static (like a TV with no signal)
Also please attach `journalctl -b -1 -k`. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813820 Title: Waking from Suspend causes screen to appear with grey static (like a TV with no signal) Status in linux package in Ubuntu: Confirmed Bug description: I am running Kubuntu 18.10. This is the PH517-61 Acer Predator Helios 500 with the Ryzen processor. My first issue I need to deal with is Suspend. I have temporarily disabled suspend in the kcmshell5 configuration. If I do let the laptop suspend and then hit the keyboard I get what appears to be a 1950s TV with no signal. At this point I manually power down and then power up again and am able to view things on screen. Running these commands I get this information: $ journalctl -b -g suspend Compiled without pattern matching support $ journalctl -b -p3 -- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54 CST. -- Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xdf775000-0xdf778fff] Jan 28 20:40:42 craig-Predator-PH517-61 spice-vdagent[2100]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 $ uname -a Linux craig-Predator-PH517-61 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This is a Vega 56 card but Kubuntu seems to think it is a Vega 64: $ lspci -k | grep -EA3 'VGA|3D|Display' 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c7) Subsystem: Acer Incorporated [ALI] Vega 10 XT [Radeon RX Vega 64] Kernel driver in use: amdgpu Kernel modules: amdgpu $ glxinfo | grep "OpenGL version" OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.2 I will attempt to flesh this out more when I get home. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: craig 2094 F pulseaudio /dev/snd/controlC0: craig 2094 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2019-01-28 (1 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Acer Predator PH517-61 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=5f69d6c1-716a-41ac-a88c-b271a71ce5a0 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 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 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/12/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Cayman_PRS dmi.board.vendor: PRS dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd10/12/2018:svnAcer:pnPredatorPH517-61:pvrV1.07:rvnPRS:rnCayman_PRS:rvrV1.07:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Predator Helios 500 dmi.product.name: Predator PH517-61 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819192] Re: rtl8723bs slow wifi (after kernel 4.18)
Please find the first -rc kernel between v4.16-rc* and v4.18-rc* that causes this regression in [1]. [1] https://kernel.ubuntu.com/~kernel-ppa/mainline/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819192 Title: rtl8723bs slow wifi (after kernel 4.18) Status in linux package in Ubuntu: Confirmed Bug description: wifi slowed down after kernel 4.18 (https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be) it does not work. thanks --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.394 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive Bus 001 Device 002: ID 6080:8060 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: I-Life Digital Technologies LLC ZED AIR TES Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: r8723bs Tags: bionic staging Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818645] Re: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm)
** Tags removed: severity-high ** Tags added: severity-critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818645 Title: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm) Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Invalid Bug description: == Comment: #0 - Satheesh Rajendran - 2019-02-28 04:38:22 == ---Problem Description--- Power8 Compat guest(RHEL 7.6) crashes during guest boot with > 256G of memory (kernel/kvm) Contact Information = sathe...@in.ibm.com ---uname output--- Host Kernel: 4.15.0-1016-ibm-gt ii qemu-system-ppc1:2.11+dfsg- 1ubuntu7.8-1ibm3 ppc64el QEMU full system emulation binaries (ppc) ii libvirt-bin4.0.0-1ubuntu8.6 ppc64el programs for the libvirt library Guest kernel: 3.10.0-957.5.1.el7.ppc64le (rhel7.6 zstream) Machine Type = power9 ppc64le ---Steps to Reproduce--- 1. Boot a power8 compat guest with memory >256G virsh define avocado-vt-vm1;virsh start --console avocado-vt-vm1 (guest xml sosreport attached) Guest crashes while booting 2019-02-28 10:36:44.752+: starting up libvirt version: 4.0.0, package: 1ubuntu8.6 (Christian Ehrhardt Fri, 09 Nov 2018 07:42:01 +0100), qemu version: 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.8-1ibm3), hostname: cs-host-f37-ac922-3.pok.ibm.com LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-system-ppc64 -name guest=avocado-vt-vm1,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/master-key.aes -machine pseries-2.11,accel=kvm,usb=off,dump-guest-core=off -m 264192 -realtime mlock=off -smp 256,sockets=256,cores=1,threads=1 -uuid f4e14f88-bf1b-4cc3-b6d6-958d514d6c18 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device qemu-xhci,id=usb,bus=pci.0,addr=0x3 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/home/sath/avocado-fvt-wrapper/data/avocado-vt/images/rhel76-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:fc:fd:fe,bus=pci.0,addr=0x1 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-15-avocado-vt-vm1/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on 2019-02-28 10:36:44.759+: 19598: info : libvirt version: 4.0.0, package: 1ubuntu8.6 (Christian Ehrhardt Fri, 09 Nov 2018 07:42:01 +0100) 2019-02-28 10:36:44.759+: 19598: info : hostname: cs-host-f37-ac922-3 2019-02-28 10:36:44.759+: 19598: info : virObjectUnref:350 : OBJECT_UNREF: obj=0x76d594111710 2019-02-28T10:36:44.781703Z qemu-system-ppc64: -chardev pty,id=charserial0: char device redirected to /dev/pts/3 (label charserial0) 2019-02-28T10:36:44.781945Z qemu-system-ppc64: warning: Number of SMP cpus requested (256) exceeds the recommended cpus supported by KVM (128) 2019-02-28T10:36:44.781953Z qemu-system-ppc64: warning: Number of hotpluggable cpus requested (256) exceeds the recommended cpus supported by KVM (128) 2019-02-28 10:37:18.060+: shutting down, reason=crashed 2019-02-28T10:37:18.071969Z qemu-system-ppc64: terminating on signal 15 from pid 14056 (/usr/sbin/libvirtd) *Additional Instructions for sathe...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #3 - Satheesh Rajendran - 2019-02-28 04:51:45 == Possible Upstream fix: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=46dec40fb741f00f1864580130779aeeaf24fb3d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Dell M5530 1.8.1 w/TB16 1.0.2. TB16 firmware flashed in Win10 fails on MST2 firmware. Seeing the same on Fedora 29 w/ 5.0.1-300.fc30.x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=1600126 WorkARound for me is booting Win10 before booting Linux. Then I can hotplug as much as I want. If I boot linux twice, it fails after minutes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
i am now using 5.0.x with your patches and it is working great! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB 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:
[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
Attached is the dmesg output from a modprobe using the ordinary kernel 4.15.0-46 ** Attachment added: "dmesg_4.15.0-46.49" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+attachment/5245801/+files/dmesg_4.15.0-46.49 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu stuck on booting on HyperV Server 2008R2. I saw kernel messages, seems to load ram image the boot is stuck. Seems to be a problem with hyperv drivers propably harddrive. Reverted back to the previous kernel. Description:Ubuntu 18.04.1 LTS Release:18.04Description:Ubuntu 18.04.1 LTS Release:18.04 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 08:52 seq crw-rw 1 root audio 116, 33 Jan 31 08:52 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: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 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 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090004 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
Please see if this kernel helps: https://people.canonical.com/~khfeng/lp1773897/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
** Attachment added: "Flasing TB16 fails on MST2 firmware" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/+attachment/5245802/+files/Capture-thunderbird-flash-fails-MST2-no-serial.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber:
[Kernel-packages] [Bug 1819869] Re: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin
This is a packaging issue, so logs should be irrelevant. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819869 Title: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin Status in linux package in Ubuntu: Confirmed Bug description: Version 3.13.0-165.215 of linux-cloud-tools-common has the following contents /. /usr /usr/sbin /usr/sbin/hv_vss_daemon /usr/sbin/hv_kvp_daemon /usr/sbin/hv_fcopy_daemon /usr/sbin/hv_get_dhcp_info /usr/sbin/hv_set_ifconfig /usr/sbin/hv_get_dns_info /usr/share /usr/share/man /usr/share/man/man8 /usr/share/man/man8/hv_kvp_daemon.8.gz /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /usr/share/doc/linux-cloud-tools-common/copyright /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-fcopy-daemon.conf /etc/init/hv-kvp-daemon.conf whereas version 3.13.0-166.216 only contains /. /usr /usr/share /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/copyright /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-kvp-daemon.conf /etc/init/hv-fcopy-daemon.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819698] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819695 (xenial/linux-gcp) -- swm properties -- kernel-stable-master-bug: 1819716 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 18:12 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 11:02 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified -- 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/1819698 Title: linux-gcp: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819695 (xenial/linux-gcp) -- swm properties -- kernel-stable-master-bug: 1819716 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 11:02 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819699] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819716 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 18:14 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 11:05 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified -- 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/1819699 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819716 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 11:05 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819692] Re: linux-oem: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819716 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 18:08 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 11:05 UTC reason: - prepare-package: Stalled -- waiting for master bug + 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/1819692 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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819716 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 11:05 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819713] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819711 (trusty/linux-azure) derivatives: bug 1819710 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1819716 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 18:10 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 11:04 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified -- 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/1819713 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819711 (trusty/linux-azure) derivatives: bug 1819710 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1819716 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 11:04 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819694] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819693 (xenial/linux-aws-hwe) -- swm properties -- kernel-stable-master-bug: 1819716 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 18:09 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 11:02 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified -- 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/1819694 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819693 (xenial/linux-aws-hwe) -- swm properties -- kernel-stable-master-bug: 1819716 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 11:02 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819701] Re: linux-ibm-gt: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819716 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 18:11 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 11:03 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819701 Title: linux-ibm-gt: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819716 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 11:03 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819704] Re: linux-oracle: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819703 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1819716 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 18:07 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 11:01 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1819704 Title: linux-oracle: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819703 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1819716 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 11:01 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819869] Re: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** 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/1819869 Title: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: Version 3.13.0-165.215 of linux-cloud-tools-common has the following contents /. /usr /usr/sbin /usr/sbin/hv_vss_daemon /usr/sbin/hv_kvp_daemon /usr/sbin/hv_fcopy_daemon /usr/sbin/hv_get_dhcp_info /usr/sbin/hv_set_ifconfig /usr/sbin/hv_get_dns_info /usr/share /usr/share/man /usr/share/man/man8 /usr/share/man/man8/hv_kvp_daemon.8.gz /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /usr/share/doc/linux-cloud-tools-common/copyright /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-fcopy-daemon.conf /etc/init/hv-kvp-daemon.conf whereas version 3.13.0-166.216 only contains /. /usr /usr/share /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/copyright /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-kvp-daemon.conf /etc/init/hv-fcopy-daemon.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Cosmic) 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/1812845 Title: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: [ 494.357824] [ cut here ] [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! [ 494.365079] invalid opcode: [#1] SMP [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] [ 494.453657] EIP: kunmap_high+0xaa/0xb0 [ 494.457571] EFLAGS: 00010246 CPU: 2 [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 [ 494.486353] Call Trace: [ 494.488967] kunmap+0x3e/0x50 [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] [ 494.497226] ? update_load_avg+0x64f/0x830 [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] [ 494.513058] bio_endio+0xb9/0x110 [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] [ 494.536621] process_one_work+0x1b9/0x3d0 [ 494.540799] worker_thread+0x37/0x420 [ 494.544628] kthread+0xf0/0x110 [ 494.547931] ? process_one_work+0x3d0/0x3d0 [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.562701] ret_from_fork+0x2e/0x38 [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- Follow up with CPU soft lockup. Please find the attachment for the complete log. 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 i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 11:54 seq crw-rw 1 root audio 116, 33 Jan 22 11:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 11:54:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1814646] Re: linux-lts-trusty: 3.13.0-166.216~precise1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814645 - phase: Ready for Release - phase-changed: Wednesday, 13. March 2019 10:06 UTC + phase: Release + phase-changed: Wednesday, 13. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Pending -- ready to copy - promote-to-updates: Pending -- ready to copy + promote-to-security: Ongoing -- packages not yet published + promote-to-updates: Ongoing -- packages not yet published -- 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/1814646 Title: linux-lts-trusty: 3.13.0-166.216~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: Fix Committed Status in Kernel SRU Workflow promote-to-updates series: Fix Committed 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-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: 1814645 phase: Release phase-changed: Wednesday, 13. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Ongoing -- packages not yet published promote-to-updates: Ongoing -- packages not yet published To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) 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/1812845 Title: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: [ 494.357824] [ cut here ] [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! [ 494.365079] invalid opcode: [#1] SMP [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] [ 494.453657] EIP: kunmap_high+0xaa/0xb0 [ 494.457571] EFLAGS: 00010246 CPU: 2 [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 [ 494.486353] Call Trace: [ 494.488967] kunmap+0x3e/0x50 [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] [ 494.497226] ? update_load_avg+0x64f/0x830 [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] [ 494.513058] bio_endio+0xb9/0x110 [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] [ 494.536621] process_one_work+0x1b9/0x3d0 [ 494.540799] worker_thread+0x37/0x420 [ 494.544628] kthread+0xf0/0x110 [ 494.547931] ? process_one_work+0x3d0/0x3d0 [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.562701] ret_from_fork+0x2e/0x38 [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- Follow up with CPU soft lockup. Please find the attachment for the complete log. 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 i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 11:54 seq crw-rw 1 root audio 116, 33 Jan 22 11:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 11:54:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Xenial) 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/1812845 Title: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: [ 494.357824] [ cut here ] [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! [ 494.365079] invalid opcode: [#1] SMP [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] [ 494.453657] EIP: kunmap_high+0xaa/0xb0 [ 494.457571] EFLAGS: 00010246 CPU: 2 [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 [ 494.486353] Call Trace: [ 494.488967] kunmap+0x3e/0x50 [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] [ 494.497226] ? update_load_avg+0x64f/0x830 [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] [ 494.513058] bio_endio+0xb9/0x110 [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] [ 494.536621] process_one_work+0x1b9/0x3d0 [ 494.540799] worker_thread+0x37/0x420 [ 494.544628] kthread+0xf0/0x110 [ 494.547931] ? process_one_work+0x3d0/0x3d0 [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.562701] ret_from_fork+0x2e/0x38 [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- Follow up with CPU soft lockup. Please find the attachment for the complete log. 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 i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 11:54 seq crw-rw 1 root audio 116, 33 Jan 22 11:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 11:54:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1819612] Re: linux-raspi2: 4.18.0-1011.13 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819624 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 10:31 UTC + phase: Packaging + phase-changed: Wednesday, 13. March 2019 12:34 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- 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/1819612 Title: linux-raspi2: 4.18.0-1011.13 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819624 phase: Packaging phase-changed: Wednesday, 13. March 2019 12:34 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814646] Re: linux-lts-trusty: 3.13.0-166.216~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1814646 Title: linux-lts-trusty: 3.13.0-166.216~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: Fix Committed Status in Kernel SRU Workflow promote-to-updates series: Fix Committed 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-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: 1814645 phase: Release phase-changed: Wednesday, 13. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Ongoing -- packages not yet published promote-to-updates: Ongoing -- packages not yet published To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819869] [NEW] linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin
Public bug reported: Version 3.13.0-165.215 of linux-cloud-tools-common has the following contents /. /usr /usr/sbin /usr/sbin/hv_vss_daemon /usr/sbin/hv_kvp_daemon /usr/sbin/hv_fcopy_daemon /usr/sbin/hv_get_dhcp_info /usr/sbin/hv_set_ifconfig /usr/sbin/hv_get_dns_info /usr/share /usr/share/man /usr/share/man/man8 /usr/share/man/man8/hv_kvp_daemon.8.gz /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /usr/share/doc/linux-cloud-tools-common/copyright /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-fcopy-daemon.conf /etc/init/hv-kvp-daemon.conf whereas version 3.13.0-166.216 only contains /. /usr /usr/share /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/copyright /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-kvp-daemon.conf /etc/init/hv-fcopy-daemon.conf ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819869 Title: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin Status in linux package in Ubuntu: New Bug description: Version 3.13.0-165.215 of linux-cloud-tools-common has the following contents /. /usr /usr/sbin /usr/sbin/hv_vss_daemon /usr/sbin/hv_kvp_daemon /usr/sbin/hv_fcopy_daemon /usr/sbin/hv_get_dhcp_info /usr/sbin/hv_set_ifconfig /usr/sbin/hv_get_dns_info /usr/share /usr/share/man /usr/share/man/man8 /usr/share/man/man8/hv_kvp_daemon.8.gz /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /usr/share/doc/linux-cloud-tools-common/copyright /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-fcopy-daemon.conf /etc/init/hv-kvp-daemon.conf whereas version 3.13.0-166.216 only contains /. /usr /usr/share /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/copyright /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-kvp-daemon.conf /etc/init/hv-fcopy-daemon.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817060] Re: EXT4: Mainstream fix for regression caused by fix CVE-2018-10876 is missing from Ubuntu Bionic Kernel
This patch was already applied to the Bionic kernel as part of our upstream stable update (bug 1815234) and will be available on the next kernel SRU udpate. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817060 Title: EXT4: Mainstream fix for regression caused by fix CVE-2018-10876 is missing from Ubuntu Bionic Kernel Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: Bionic kernels including the current 4.15.0-45 (and 4.15.0-46 from the latest in git) contain the following commit https://git.launchpad.net /~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/commit/?id=70b9ab218a71b56b6a8c1f4c0daf0219a5238597 from June 2018 which was an (incorrect) attempt to fix CVE-2018-10876. Given that this problem involves changes to code relating to a CVE I have marked this bug as being security related Unfortunately this fix introduces a new bug whereby the kernel will detect corruption and take evasive action if a filesystem is remounted before the lazy background initialisation has zeroed block group zero's inode table. There was an upstream commit made in July 2018, which claims to fix the above regression but this one has not been adopted into Ubuntu's kernel: (https://github.com/torvalds/linux/commit/5012284700775a4e6e3fbe7eac4c543c4874b559) Contrary to the example in the upstream fix, it doesn't really matter whether the first mount is ro or rw although if the initial mount is read-only then the kernel will not initialise in the background and a subsequent remount as rw is guaranteed to hit this problem, whereas after an initial rw mount there is a small window of time where a remount will encounter this problem. We are hitting this issue during automated builds because Puppet is likely to issue one or more remounts against a filesystem it has only just created and mounted. This seems like inefficient behaviour by Puppet, however remounting should be a safe operation and it currently is not. SUGGESTED FIX: -- Please could the above upstream commit (874b559) to be patched into Ubuntu's kernel to alleviate this? STEPS TO REPRODUCE: --- You either need a spare disk/volume to reformat, or a 'loop' device backed to a large file - e.g.: # fallocate -l 25G /bigfile && losetup --find --show /bigfile Format the device, mount and remount e.g.: # mkfs.ext4 /dev/loop2 # mount /dev/loop7 /mnt && mount -o remount /mnt NOTE: Contrary to the similar example in the upstream fix I am mounting rw not ro see my earlier comments on this. The filesystem will immediately be remounted read-only with the following in /var/log/syslog: --- Feb 21 12:25:04 host kernel: [123.278265] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: errors=remount-ro Feb 21 12:25:04 host kernel: [123.284921] EXT4-fs error (device loop2): ext4_has_uninit_itable:3135: comm mount: Inode table for bg 0 marked as needing zeroing Feb 21 12:25:04 host kernel: [123.341356] Aborting journal on device loop2-8. Feb 21 12:25:05 host kernel: [123.634358] EXT4-fs (loop2): Remounting filesystem read-only By running dump2efs in a loop after first mount I was able to observe that the output for Group 0 shows in my case that it takes about 4-5 seconds after the first mount before the kernel's ext4lazyinit process zeroes Group 0's inode table. WORKAROUND: --- For the benefit of anyone else hitting this issue prior to a kernel fix, it is possible to avoid this problem by forcing mkfs to zero the inode tables immediately - e.g. # mkfs.ext4 -E lazy_itable_init=0 This will cause mkfs to take a little longer creating the filesystem. With the workaround all block groups on the new filesystem (as shown by dumpe2fs) will look like this until some time after the filesystem was first mounted: Group 0: (Blocks 0-32767) csum 0x7b1a Once initialised (either by the ext4lazyinit or by using lazy_itable_init=0 ) they acquire the ITABLE_ZEROED flag and can then be safely remounted without hitting this bug: Group 0: (Blocks 0-32767) csum 0x7b1a [ITABLE_ZEROED] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-signed-image-generic 4.15.0.45.47 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop:
[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
This patch seems to fix the problem for me. See also: https://lkml.org/lkml/2019/3/13/181 ** Patch added: "btrfs-raid56-properly-unmap-parity-page-in-finish_pa.patch" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812845/+attachment/5245817/+files/btrfs-raid56-properly-unmap-parity-page-in-finish_pa.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812845 Title: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Confirmed Bug description: This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: [ 494.357824] [ cut here ] [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! [ 494.365079] invalid opcode: [#1] SMP [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] [ 494.453657] EIP: kunmap_high+0xaa/0xb0 [ 494.457571] EFLAGS: 00010246 CPU: 2 [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 [ 494.486353] Call Trace: [ 494.488967] kunmap+0x3e/0x50 [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] [ 494.497226] ? update_load_avg+0x64f/0x830 [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] [ 494.513058] bio_endio+0xb9/0x110 [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] [ 494.536621] process_one_work+0x1b9/0x3d0 [ 494.540799] worker_thread+0x37/0x420 [ 494.544628] kthread+0xf0/0x110 [ 494.547931] ? process_one_work+0x3d0/0x3d0 [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.562701] ret_from_fork+0x2e/0x38 [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- Follow up with CPU soft lockup. Please find the attachment for the complete log. 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 i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 11:54 seq crw-rw 1 root audio 116, 33 Jan 22 11:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 11:54:49 2019 IwConfig: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 1819881] 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 1819881 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/1819881 Title: [CONFIG] please enable highdpi font FONT_TER16x32 Status in linux package in Ubuntu: Incomplete Bug description: [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819882] 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 1819882 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/1819882 Title: [CONFIG] please enable highdpi font FONT_TER16x32 Status in linux package in Ubuntu: Incomplete Bug description: [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819716] Re: linux: 4.15.0-47.50 -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 will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819713 (xenial/linux-azure), bug 1819715 (xenial/linux-hwe) derivatives: bug 1819691 (linux-raspi2), bug 1819692 (linux-oem), bug 1819694 (linux-aws), bug 1819698 (linux-gcp), bug 1819699 (linux-kvm), bug 1819701 (linux-ibm-gt), bug 1819704 (linux-oracle), bug 1819707 (linux-fips) -- swm properties -- - phase: Packaging - phase-changed: Wednesday, 13. March 2019 04:32 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 13. March 2019 11:00 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 in Ubuntu. https://bugs.launchpad.net/bugs/1819716 Title: linux: 4.15.0-47.50 -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 snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819713 (xenial/linux-azure), bug 1819715 (xenial/linux-hwe) derivatives: bug 1819691 (linux-raspi2), bug 1819692 (linux-oem), bug 1819694 (linux-aws), bug 1819698 (linux-gcp), bug 1819699 (linux-kvm), bug 1819701 (linux-ibm-gt), bug 1819704 (linux-oracle), bug 1819707 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 13. March 2019 11:00 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/1819716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819707] Re: linux-fips: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819716 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 18:13 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 11:04 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819707 Title: linux-fips: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819716 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 11:04 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819707/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818430] Re: Please update aufs driver
As of right now there is no non-rc version of aufs with support for Linux 5.0. We will update it as soon as one is available. However, the regex isn't going to work even when we have a non-rc version since it is looking for a 4.x version, and the version will undoubtedly be 5.0 (looks like it would even be broken for 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/1818430 Title: Please update aufs driver Status in linux package in Ubuntu: Confirmed Bug description: The latest Debian package of aufs-tools fails to build on Ubuntu 19.04 because it is looking for a non-RC version of aufs. Currently, Ubuntu's aufs reports as "4.x-rcN-20180917" References -- https://sources.debian.org/src/aufs-tools/unstable/ver.c https://launchpad.net/ubuntu/+source/aufs-tools/1:4.14+20190211-1 https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=82ab94a2db To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
What testing did you perform? ** Tags removed: verification-done verification-done-cosmic ** Tags added: verification-needed verification-needed-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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819612] Re: linux-raspi2: 4.18.0-1011.13 -proposed tracker
** Summary changed: - linux-raspi2: -proposed tracker + linux-raspi2: 4.18.0-1011.13 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1819612 Title: linux-raspi2: 4.18.0-1011.13 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819624 phase: Holding before Packaging phase-changed: Tuesday, 12. March 2019 10:31 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819869] Re: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin
** Changed in: linux (Ubuntu) Status: Invalid => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819869 Title: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: Version 3.13.0-165.215 of linux-cloud-tools-common has the following contents /. /usr /usr/sbin /usr/sbin/hv_vss_daemon /usr/sbin/hv_kvp_daemon /usr/sbin/hv_fcopy_daemon /usr/sbin/hv_get_dhcp_info /usr/sbin/hv_set_ifconfig /usr/sbin/hv_get_dns_info /usr/share /usr/share/man /usr/share/man/man8 /usr/share/man/man8/hv_kvp_daemon.8.gz /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /usr/share/doc/linux-cloud-tools-common/copyright /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-fcopy-daemon.conf /etc/init/hv-kvp-daemon.conf whereas version 3.13.0-166.216 only contains /. /usr /usr/share /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/copyright /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-kvp-daemon.conf /etc/init/hv-fcopy-daemon.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819624] Re: linux: 4.18.0-17.18 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.18.0-17.18 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819624 Title: linux: 4.18.0-17.18 -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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819623 (bionic/linux-hwe) derivatives: bug 1819612 (linux-raspi2), bug 1819614 (linux-aws), bug 1819618 (linux-azure), bug 1819620 (linux-gcp), bug 1819621 (linux-kvm) -- swm properties -- phase: Packaging phase-changed: Wednesday, 13. March 2019 11:36 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/1819624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763975] Re: DP1.2 daisy-chain flickering
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (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/1763975 Title: DP1.2 daisy-chain flickering Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Hi all, I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04 (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2 disabled on the second monitor as per Dell instructions). I am getting flickering whereby randomly display1 or display2 turn black and then back on again. When I disable DP1.2 on the display1, and therefore get a duplicate display (as opposed to extended) on display2, I get no flickering at all. The same setup yields no flickering when running from a Windows 10 box, so don't think it is the monitors. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 12:52:24 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2068] InstallationDate: Installed on 2018-04-01 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401) MachineType: Intel Corporation NUC7i7BNH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-307 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-308 dmi.sys.vendor: Intel Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812845 Title: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Confirmed Bug description: This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: [ 494.357824] [ cut here ] [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! [ 494.365079] invalid opcode: [#1] SMP [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] [ 494.453657] EIP: kunmap_high+0xaa/0xb0 [ 494.457571] EFLAGS: 00010246 CPU: 2 [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 [ 494.486353] Call Trace: [ 494.488967] kunmap+0x3e/0x50 [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] [ 494.497226] ? update_load_avg+0x64f/0x830 [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] [ 494.513058] bio_endio+0xb9/0x110 [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] [ 494.536621] process_one_work+0x1b9/0x3d0 [ 494.540799] worker_thread+0x37/0x420 [ 494.544628] kthread+0xf0/0x110 [ 494.547931] ? process_one_work+0x3d0/0x3d0 [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.562701] ret_from_fork+0x2e/0x38 [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- Follow up with CPU soft lockup. Please find the attachment for the complete log. 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 i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 11:54 seq crw-rw 1 root audio 116, 33 Jan 22 11:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 11:54:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=6aaa11f6-d386-4c0c-b4b8-38e6c408980a ro console=ttyS0,115200n8 RelatedPackageVersions:
[Kernel-packages] [Bug 1819869] Re: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin
** Tags added: id-5c88b2cecc73e1431fae0041 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819869 Title: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: Version 3.13.0-165.215 of linux-cloud-tools-common has the following contents /. /usr /usr/sbin /usr/sbin/hv_vss_daemon /usr/sbin/hv_kvp_daemon /usr/sbin/hv_fcopy_daemon /usr/sbin/hv_get_dhcp_info /usr/sbin/hv_set_ifconfig /usr/sbin/hv_get_dns_info /usr/share /usr/share/man /usr/share/man/man8 /usr/share/man/man8/hv_kvp_daemon.8.gz /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /usr/share/doc/linux-cloud-tools-common/copyright /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-fcopy-daemon.conf /etc/init/hv-kvp-daemon.conf whereas version 3.13.0-166.216 only contains /. /usr /usr/share /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/copyright /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-kvp-daemon.conf /etc/init/hv-fcopy-daemon.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817097] Re: pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices
Decreasing importance from critical to medium, because the bug is known to the community, it is already discussed in RH Bug 1669751, and here https://www.redhat.com/archives/linux-lvm/2019-February/msg00018.html / https://www.redhat.com/archives/linux-lvm/2019-March/msg0.html, and not platform specific, nor specific to a certain Ubuntu release. On top there are actions possible to easily avoid this situation, like explicitly setting / forcing the sector size to be 4096 bytes or using a bigger image size (>512 MB - which is not uncommon), so that the sector size default changes to 4k anyway. A patch was already suggested upstream: https://sourceware.org/git/?p=lvm2.git;a=commit;h=dd6ff9e3a75801fc5c6166aa0983fa8df098e91a Once that patch got upstream accepted and became picked-up in a new lvm2 version, it will eventually land in Ubuntu, too. ** Changed in: ubuntu-z-systems Importance: Critical => 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/1817097 Title: pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices Status in lvm2: Confirmed Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Incomplete Bug description: Problem Description--- Summary === Environment: IBM Z13 LPAR and z/VM Guest IBM Type: 2964 Model: 701 NC9 OS: Ubuntu 18.10 (GNU/Linux 4.18.0-13-generic s390x) Package: lvm2 version 2.02.176-4.1ubuntu3 LVM: pvmove operation corrupts file system when using 4096 (4k) logical block size and default block size being 512 bytes in the underlying devices The problem is immediately reproducible. We see a real usability issue with data destruction as consequence - which is not acceptable. We expect 'pvmove' to fail with error in such situations to prevent fs destruction, which might possibly be overridden by a force flag. Details === After a 'pvmove' operation is run to move a physical volume onto an ecrypted device with 4096 bytes logical block size we experience a file system corruption. There is no need for the file system to be mounted, but the problem surfaces differently if so. Either, the 'pvs' command after the pvmove shows /dev/LOOP_VG/LV: read failed after 0 of 1024 at 0: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 314507264: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 314564608: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 4096: Invalid argument or a subsequent mount shows (after umount if the fs had previously been mounted as in our setup) mount: /mnt: wrong fs type, bad option, bad superblock on /dev/mapper/LOOP_VG-LV, missing codepage or helper program, or other error. A minimal setup of LVM using one volume group with one logical volume defined, based on one physical volume is sufficient to raise the problem. One more physical volume of the same size is needed to run the pvmove operation to. LV | VG: LOOP_VG [ ] | PV: /dev/loop0 --> /dev/mapper/enc-loop ( backed by /dev/mapper/enc-loop ) The physical volumes are backed by loopback devices (losetup) to base the problem report on, but we have seen the error on real SCSI multipath volumes also, with and without cryptsetup mapper devices in use. Further discussion == https://www.saout.de/pipermail/dm-crypt/2019-February/006078.html The problem does not occur on block devices with native size of 4k. E.g. DASDs, or file systems with mkfs -b 4096 option. Terminal output === See attached file pvmove-error.txt Debug data == pvmove was run with -dd (maximum debug level) See attached journal file. Contact Information = christian.r...@de.ibm.com ---uname output--- Linux system 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:00:35 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM Type: 2964 Model: 701 NC9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1.) Create two image files of 500MB in size and set up two loopback devices with 'losetup -fP FILE' 2.) Create one physical volume and one volume group 'LOOP_VG', and one logical volume 'VG' Run: pvcreate /dev/loop0 vgcreate LOOP_VG /dev/loop0 lvcreate -L 300MB LOOP_VG -n LV /dev/loop0 3.) Create a file system on the logical volume device: mkfs.ext4 /dev/mapper/LOOP_VG-LV 4.) mount the file system created in the previous step to some empty available directory: mount /dev/mapper/LOOP_VG-LV /mnt 5.) Set up a second physical volume, this time encrypted with LUKS2, and open the
[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812845 Title: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Confirmed Bug description: This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: [ 494.357824] [ cut here ] [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! [ 494.365079] invalid opcode: [#1] SMP [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] [ 494.453657] EIP: kunmap_high+0xaa/0xb0 [ 494.457571] EFLAGS: 00010246 CPU: 2 [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 [ 494.486353] Call Trace: [ 494.488967] kunmap+0x3e/0x50 [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] [ 494.497226] ? update_load_avg+0x64f/0x830 [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] [ 494.513058] bio_endio+0xb9/0x110 [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] [ 494.536621] process_one_work+0x1b9/0x3d0 [ 494.540799] worker_thread+0x37/0x420 [ 494.544628] kthread+0xf0/0x110 [ 494.547931] ? process_one_work+0x3d0/0x3d0 [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.562701] ret_from_fork+0x2e/0x38 [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- Follow up with CPU soft lockup. Please find the attachment for the complete log. 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 i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 11:54 seq crw-rw 1 root audio 116, 33 Jan 22 11:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 11:54:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=6aaa11f6-d386-4c0c-b4b8-38e6c408980a ro
[Kernel-packages] [Bug 1814646] Re: linux-lts-trusty: 3.13.0-166.216~precise1 -proposed tracker
3.13.0-166.216~precise1 - generic Regression test CMPL, RTB. 35 / 36 tests were run, missing: ubuntu_boot Issue to note in amd64: ubuntu_qrt_kernel_security - CONFIG_RETPOLINE=y in kernel (bug 1786894) ubuntu_ftrace_smoke - timeouted on amd64 (bug 1819850) 33 / 34 tests were run, missing: ubuntu_boot Issue to note in i386: ubuntu_qrt_kernel_security - CONFIG_RETPOLINE=y in kernel (bug 1786894) ** 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) -- 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/1814646 Title: linux-lts-trusty: 3.13.0-166.216~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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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-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: 1814645 phase: Ready for Release phase-changed: Wednesday, 13. March 2019 10:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779848] Re: Cleanup Meltdown/Spectre implementation
Xenial's implementation has been update via updates to newer 4.4 upstream stable versions. ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) 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/1779848 Title: Cleanup Meltdown/Spectre implementation Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Released Status in linux source package in Xenial: Invalid Bug description: == SRU Justification == Ubuntu kernels contain Meltdown and Spectre mitigations that are largely based on embargoed patches but what eventually landed in upstream is different in some places. We should clean up the different kernels to bring them closer in line with upstream. == Fix == Add missing upstream patches. == Regression Potential == Medium. The patches have been in upstream for quite a while now and are baked in but some of the backporting is not completely trivial and without risk. == Test Case == TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814646] Re: linux-lts-trusty: 3.13.0-166.216~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Tags removed: block-proposed-precise ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814645 - phase: Ready for Testing - phase-changed: Monday, 11. March 2019 13:31 UTC + phase: Ready for Release + phase-changed: Wednesday, 13. March 2019 10:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1814646 Title: linux-lts-trusty: 3.13.0-166.216~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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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-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: 1814645 phase: Ready for Release phase-changed: Wednesday, 13. March 2019 10:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817060] Re: EXT4: Mainstream fix for regression caused by fix CVE-2018-10876 is missing from Ubuntu Bionic Kernel
Hi Jonathan, Since this patch has been applied to the tree with a link to a different bug, this bug report won't get any notification about when the fix is published to -updates. Please follow the updates on bug 1815234. Thank you. ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817060 Title: EXT4: Mainstream fix for regression caused by fix CVE-2018-10876 is missing from Ubuntu Bionic Kernel Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: Bionic kernels including the current 4.15.0-45 (and 4.15.0-46 from the latest in git) contain the following commit https://git.launchpad.net /~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/commit/?id=70b9ab218a71b56b6a8c1f4c0daf0219a5238597 from June 2018 which was an (incorrect) attempt to fix CVE-2018-10876. Given that this problem involves changes to code relating to a CVE I have marked this bug as being security related Unfortunately this fix introduces a new bug whereby the kernel will detect corruption and take evasive action if a filesystem is remounted before the lazy background initialisation has zeroed block group zero's inode table. There was an upstream commit made in July 2018, which claims to fix the above regression but this one has not been adopted into Ubuntu's kernel: (https://github.com/torvalds/linux/commit/5012284700775a4e6e3fbe7eac4c543c4874b559) Contrary to the example in the upstream fix, it doesn't really matter whether the first mount is ro or rw although if the initial mount is read-only then the kernel will not initialise in the background and a subsequent remount as rw is guaranteed to hit this problem, whereas after an initial rw mount there is a small window of time where a remount will encounter this problem. We are hitting this issue during automated builds because Puppet is likely to issue one or more remounts against a filesystem it has only just created and mounted. This seems like inefficient behaviour by Puppet, however remounting should be a safe operation and it currently is not. SUGGESTED FIX: -- Please could the above upstream commit (874b559) to be patched into Ubuntu's kernel to alleviate this? STEPS TO REPRODUCE: --- You either need a spare disk/volume to reformat, or a 'loop' device backed to a large file - e.g.: # fallocate -l 25G /bigfile && losetup --find --show /bigfile Format the device, mount and remount e.g.: # mkfs.ext4 /dev/loop2 # mount /dev/loop7 /mnt && mount -o remount /mnt NOTE: Contrary to the similar example in the upstream fix I am mounting rw not ro see my earlier comments on this. The filesystem will immediately be remounted read-only with the following in /var/log/syslog: --- Feb 21 12:25:04 host kernel: [123.278265] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: errors=remount-ro Feb 21 12:25:04 host kernel: [123.284921] EXT4-fs error (device loop2): ext4_has_uninit_itable:3135: comm mount: Inode table for bg 0 marked as needing zeroing Feb 21 12:25:04 host kernel: [123.341356] Aborting journal on device loop2-8. Feb 21 12:25:05 host kernel: [123.634358] EXT4-fs (loop2): Remounting filesystem read-only By running dump2efs in a loop after first mount I was able to observe that the output for Group 0 shows in my case that it takes about 4-5 seconds after the first mount before the kernel's ext4lazyinit process zeroes Group 0's inode table. WORKAROUND: --- For the benefit of anyone else hitting this issue prior to a kernel fix, it is possible to avoid this problem by forcing mkfs to zero the inode tables immediately - e.g. # mkfs.ext4 -E lazy_itable_init=0 This will cause mkfs to take a little longer creating the filesystem. With the workaround all block groups on the new filesystem (as shown by dumpe2fs) will look like this until some time after the filesystem was first mounted: Group 0: (Blocks 0-32767) csum 0x7b1a Once initialised (either by the ext4lazyinit or by using lazy_itable_init=0 ) they acquire the ITABLE_ZEROED flag and can then be safely remounted without hitting this bug: Group 0: (Blocks 0-32767) csum 0x7b1a [ITABLE_ZEROED] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-signed-image-generic 4.15.0.45.47 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c',
[Kernel-packages] [Bug 1814646] Re: linux-lts-trusty: 3.13.0-166.216~precise1 -proposed tracker
** Tags added: regression-testing-passed -- 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/1814646 Title: linux-lts-trusty: 3.13.0-166.216~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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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-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: 1814645 phase: Ready for Release phase-changed: Wednesday, 13. March 2019 10:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819624] Re: linux: 4.18.0-17.18 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819623 (bionic/linux-hwe) derivatives: bug 1819612 (linux-raspi2), bug 1819614 (linux-aws), bug 1819618 (linux-azure), bug 1819620 (linux-gcp), bug 1819621 (linux-kvm) -- swm properties -- - phase: Ready for Packaging - phase-changed: Tuesday, 12. March 2019 10:58 UTC + phase: Packaging + phase-changed: Wednesday, 13. March 2019 11:36 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 in Ubuntu. https://bugs.launchpad.net/bugs/1819624 Title: linux: 4.18.0-17.18 -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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819623 (bionic/linux-hwe) derivatives: bug 1819612 (linux-raspi2), bug 1819614 (linux-aws), bug 1819618 (linux-azure), bug 1819620 (linux-gcp), bug 1819621 (linux-kvm) -- swm properties -- phase: Packaging phase-changed: Wednesday, 13. March 2019 11:36 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/1819624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817060] Re: EXT4: Mainstream fix for regression caused by fix CVE-2018-10876 is missing from Ubuntu Bionic Kernel
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Bionic) 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/1817060 Title: EXT4: Mainstream fix for regression caused by fix CVE-2018-10876 is missing from Ubuntu Bionic Kernel Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: Bionic kernels including the current 4.15.0-45 (and 4.15.0-46 from the latest in git) contain the following commit https://git.launchpad.net /~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/commit/?id=70b9ab218a71b56b6a8c1f4c0daf0219a5238597 from June 2018 which was an (incorrect) attempt to fix CVE-2018-10876. Given that this problem involves changes to code relating to a CVE I have marked this bug as being security related Unfortunately this fix introduces a new bug whereby the kernel will detect corruption and take evasive action if a filesystem is remounted before the lazy background initialisation has zeroed block group zero's inode table. There was an upstream commit made in July 2018, which claims to fix the above regression but this one has not been adopted into Ubuntu's kernel: (https://github.com/torvalds/linux/commit/5012284700775a4e6e3fbe7eac4c543c4874b559) Contrary to the example in the upstream fix, it doesn't really matter whether the first mount is ro or rw although if the initial mount is read-only then the kernel will not initialise in the background and a subsequent remount as rw is guaranteed to hit this problem, whereas after an initial rw mount there is a small window of time where a remount will encounter this problem. We are hitting this issue during automated builds because Puppet is likely to issue one or more remounts against a filesystem it has only just created and mounted. This seems like inefficient behaviour by Puppet, however remounting should be a safe operation and it currently is not. SUGGESTED FIX: -- Please could the above upstream commit (874b559) to be patched into Ubuntu's kernel to alleviate this? STEPS TO REPRODUCE: --- You either need a spare disk/volume to reformat, or a 'loop' device backed to a large file - e.g.: # fallocate -l 25G /bigfile && losetup --find --show /bigfile Format the device, mount and remount e.g.: # mkfs.ext4 /dev/loop2 # mount /dev/loop7 /mnt && mount -o remount /mnt NOTE: Contrary to the similar example in the upstream fix I am mounting rw not ro see my earlier comments on this. The filesystem will immediately be remounted read-only with the following in /var/log/syslog: --- Feb 21 12:25:04 host kernel: [123.278265] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: errors=remount-ro Feb 21 12:25:04 host kernel: [123.284921] EXT4-fs error (device loop2): ext4_has_uninit_itable:3135: comm mount: Inode table for bg 0 marked as needing zeroing Feb 21 12:25:04 host kernel: [123.341356] Aborting journal on device loop2-8. Feb 21 12:25:05 host kernel: [123.634358] EXT4-fs (loop2): Remounting filesystem read-only By running dump2efs in a loop after first mount I was able to observe that the output for Group 0 shows in my case that it takes about 4-5 seconds after the first mount before the kernel's ext4lazyinit process zeroes Group 0's inode table. WORKAROUND: --- For the benefit of anyone else hitting this issue prior to a kernel fix, it is possible to avoid this problem by forcing mkfs to zero the inode tables immediately - e.g. # mkfs.ext4 -E lazy_itable_init=0 This will cause mkfs to take a little longer creating the filesystem. With the workaround all block groups on the new filesystem (as shown by dumpe2fs) will look like this until some time after the filesystem was first mounted: Group 0: (Blocks 0-32767) csum 0x7b1a Once initialised (either by the ext4lazyinit or by using lazy_itable_init=0 ) they acquire the ITABLE_ZEROED flag and can then be safely remounted without hitting this bug: Group 0: (Blocks 0-32767) csum 0x7b1a [ITABLE_ZEROED] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-signed-image-generic 4.15.0.45.47 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq',
[Kernel-packages] [Bug 1819869] 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 1819869 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: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819869 Title: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin Status in linux package in Ubuntu: Incomplete Bug description: Version 3.13.0-165.215 of linux-cloud-tools-common has the following contents /. /usr /usr/sbin /usr/sbin/hv_vss_daemon /usr/sbin/hv_kvp_daemon /usr/sbin/hv_fcopy_daemon /usr/sbin/hv_get_dhcp_info /usr/sbin/hv_set_ifconfig /usr/sbin/hv_get_dns_info /usr/share /usr/share/man /usr/share/man/man8 /usr/share/man/man8/hv_kvp_daemon.8.gz /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /usr/share/doc/linux-cloud-tools-common/copyright /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-fcopy-daemon.conf /etc/init/hv-kvp-daemon.conf whereas version 3.13.0-166.216 only contains /. /usr /usr/share /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/copyright /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-kvp-daemon.conf /etc/init/hv-fcopy-daemon.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819881] [NEW] [CONFIG] please enable highdpi font FONT_TER16x32
Public bug reported: [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-stop-nagging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819881 Title: [CONFIG] please enable highdpi font FONT_TER16x32 Status in linux package in Ubuntu: Incomplete Bug description: [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819882] [NEW] [CONFIG] please enable highdpi font FONT_TER16x32
Public bug reported: [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-stop-nagging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819882 Title: [CONFIG] please enable highdpi font FONT_TER16x32 Status in linux package in Ubuntu: Incomplete Bug description: [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819696] Re: Cinnamon highly loads my CPU after installing this driver
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Assignee: (unassigned) => Nikolay Nechaev (kolay.ne) -- 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/1819696 Title: Cinnamon highly loads my CPU after installing this driver Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: ``` * Cinnamon 4.0.9 * Distro: Linux Mint 19.1 Tessa, base: Ubuntu 18.04 bionic; Kernel: 4.15.0-46-generic x86_64 * Device-2: NVIDIA GM108M [GeForce 940MX] * 64 bit ``` After installing nvidia driver for my graphic card, cinnamon strongly loads my cpu. It loads much more while playing videos, opening windows and even just typing text! (issue to cinnamon, containing screenshots and logs: https://github.com/linuxmint/cinnamon/issues/8457) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1819696/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819921] [NEW] [SRU] [B/OEM] Fix ACPI bug that causes boot failure
Public bug reported: [Impact] Some systems boot failed at a very early stage, only blackscreen shown. [Fix] Some system BIOS set definition in if statement, it would be deferred to be loaded. Some devices would not work properly and cause a system lockup. execute all acpi tables to make system work properly. [Test] Tested on several laptops, the laptop that failed to boot boots well. Other laptops still works fine. [Regression Potential] Upstream fix. Low risk. Backported changes is one line of debug ouput sentence in nsparse.c: s/Start table execution pass/Start load pass/ Verified on several laptops. Fix boot failure and no regression found. ** Affects: hwe-next Importance: Critical Assignee: AaronMa (mapengyu) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: originate-from-1819416 sutton ** Tags added: originate-from-1819416 sutton ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: hwe-next Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819921 Title: [SRU] [B/OEM] Fix ACPI bug that causes boot failure Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] Some systems boot failed at a very early stage, only blackscreen shown. [Fix] Some system BIOS set definition in if statement, it would be deferred to be loaded. Some devices would not work properly and cause a system lockup. execute all acpi tables to make system work properly. [Test] Tested on several laptops, the laptop that failed to boot boots well. Other laptops still works fine. [Regression Potential] Upstream fix. Low risk. Backported changes is one line of debug ouput sentence in nsparse.c: s/Start table execution pass/Start load pass/ Verified on several laptops. Fix boot failure and no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1819921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818140] Re: [Dell DW1560 / BCM20702A1] kobject_add_internal failed for hci0:11 with --EEXIST, don't try to register things with the same name in the same directory
Ubuntu 18.10 Bluez Version: 5.50-0ubuntu1 After changing batteries in my bluetooth mouse, it is connected but doesn't work (no movement or clicking). Fix is to re-pair it. ~$ dmesg | tail -40 [12650.520061] sysfs_warn_dup.cold.4+0x17/0x32 [12650.520064] sysfs_create_dir_ns+0xa9/0xd0 [12650.520067] kobject_add_internal+0xac/0x260 [12650.520071] ? kvasprintf+0x7f/0xd0 [12650.520073] kobject_add+0x7d/0xb0 [12650.520076] device_add+0x128/0x650 [12650.520092] hci_conn_add_sysfs+0x4b/0xc0 [bluetooth] [12650.520106] hci_conn_complete_evt.isra.47+0xc7/0x400 [bluetooth] [12650.520109] ? __switch_to_asm+0x34/0x70 [12650.520123] hci_event_packet+0x1670/0x27d0 [bluetooth] [12650.520124] ? __switch_to_asm+0x40/0x70 [12650.520126] ? __switch_to_asm+0x34/0x70 [12650.520127] ? __switch_to_asm+0x40/0x70 [12650.520129] ? __switch_to_asm+0x34/0x70 [12650.520130] ? __switch_to_asm+0x40/0x70 [12650.520132] ? __switch_to_asm+0x40/0x70 [12650.520144] hci_rx_work+0x190/0x380 [bluetooth] [12650.520148] ? __schedule+0x2a6/0x840 [12650.520153] process_one_work+0x20f/0x410 [12650.520156] worker_thread+0x34/0x400 [12650.520159] kthread+0x120/0x140 [12650.520162] ? pwq_unbound_release_workfn+0xd0/0xd0 [12650.520164] ? kthread_bind+0x40/0x40 [12650.520165] ret_from_fork+0x35/0x40 [12650.520168] kobject_add_internal failed for hci0:11 with -EEXIST, don't try to register things with the same name in the same directory. [12650.520172] Bluetooth: hci0: failed to register connection device [12650.582899] kobject_add_internal failed for 0005:05AC:030D.0008 (error: -2 parent: hci0:11) [12651.761999] Bluetooth: hci0: last event is not cmd complete (0x0f) [12667.896097] Bluetooth: hci0: last event is not cmd complete (0x0f) [12684.202210] Bluetooth: hci0: last event is not cmd complete (0x0f) [12688.792774] audit: type=1107 audit(1552483496.482:112): pid=1858 uid=105 auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="GetDevices" mask="send" name="org.freedesktop.NetworkManager" pid=4519 label="snap.chromium.chromium" peer_pid=2026 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' [12699.892349] Bluetooth: hci0: last event is not cmd complete (0x0f) [12716.204418] Bluetooth: hci0: last event is not cmd complete (0x0f) [12732.080523] Bluetooth: hci0: last event is not cmd complete (0x0f) [12747.954625] Bluetooth: hci0: last event is not cmd complete (0x0f) [12764.078740] Bluetooth: hci0: last event is not cmd complete (0x0f) [12779.952841] Bluetooth: hci0: last event is not cmd complete (0x0f) [12796.084949] Bluetooth: hci0: last event is not cmd complete (0x0f) [12812.215051] Bluetooth: hci0: last event is not cmd complete (0x0f) ~$ dpkg --status bluez | grep '^Version:' Version: 5.50-0ubuntu1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818140 Title: [Dell DW1560 / BCM20702A1] kobject_add_internal failed for hci0:11 with --EEXIST, don't try to register things with the same name in the same directory Status in linux package in Ubuntu: Confirmed Bug description: kobject_add_internal_failed for hci0:11 with --EEXIST, don't try to register things with the same name in the same directory This issue is about kernel - it shouldn't rely on state of unrealiable propertary drivers. Sometimes rmmod all bluetooth modules helps, sometimes restart is just faster. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 21:13:21 2019 InstallationDate: Installed on 2015-05-08 (1392 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: btusb rfcomm bnep bluetooth MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash log_buf_len=1M crashkernel=384M-:128M SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-08-26 (185 days ago) dmi.bios.date: 09/27/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09K8G1 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd09/27/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc.
[Kernel-packages] [Bug 1819699] Re: linux-kvm: 4.15.0-1031.31 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819716 - phase: Ready for Packaging - phase-changed: Wednesday, 13. March 2019 11:05 UTC + phase: Packaging + phase-changed: Wednesday, 13. March 2019 14:05 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- 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/1819699 Title: linux-kvm: 4.15.0-1031.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819716 phase: Packaging phase-changed: Wednesday, 13. March 2019 14:05 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819917] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + -- swm properties -- + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 14:29 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 in Ubuntu. https://bugs.launchpad.net/bugs/1819917 Title: linux: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 14:29 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
Hi, do you install vanilla/stock Ubuntu Xenial, or the preloaded OEM Xenial? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: Hello Team, I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower over UEFI installation. I'm using Display port monitor, inorder to get proper display I need to download nvidia driver from ppa:graphics- drivers/ppa After install nvidia-384 and did a reboot, still no display, but can able to see the PCI modules conflicted #lspci -v lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory There is no issue with Ubuntu 18.04 , which is works perfectly on the same machine. Ubuntu 16.04 having issue. Please let me know id there is some issue with the running kernel or any package? Below is the environment details. = Ubuntu 16.04.4 LTS Xenial Kernel - 4.15.0-46-generic NVIDIA Quadro P4000 $lshw -C Display WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:29 memory:d700-d7ff memory:c000-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 #dpkg -l | grep xserver-xorg-core-hwe-16.04 ii xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 $dpkg -l | grep nvid ii nvidia-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA binary driver - version 384.130 ii nvidia-opencl-icd-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.8.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 415.27-0ubuntu0~gpu16.04.1 amd64Tool for configuring the NVIDIA graphics driver #startx xauth: file /root/.Xauthority does not exist X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7 Build Date: 24 November 2017 09:44:25AM xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 15:14:19 2019 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a968970e1e] (EE) 1: /usr/lib/xorg/Xorg (0x55a9687bf000+0x1b5b89) [0x55a968974b89] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe81648b000+0x11390) [0x7fe81649c390] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_next+0x118) [0x7fe817ae4a38] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_find_by_slot+0x3b) [0x7fe817ae4abb] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_init+0xaf) [0x7fe817ae67af] (EE) 6: /usr/lib/xorg/Xorg (0x55a9687bf000+0xb17a9) [0x55a9688707a9] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55a968849e62] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xa13) [0x55a968857f83] (EE) 9: /usr/lib/xorg/Xorg (0x55a9687bf000+0x581a6) [0x55a9688171a6] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fe8160e1830] (EE) 11: /usr/lib/xorg/Xorg (_start+0x29) [0x55a968801329] (EE) (EE) Segmentation fault at address 0x0 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also
[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
Exactly. I did the "verification-done-bionic" step for 18.2.2 in comment #12 above; and unfortunately I don't have an affected school nearby, where I could test 18.2.8 in cosmic, and installing cosmic in a remote school would be hard. Thanks a lot Timo! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819924] [NEW] System hangs when hot-plugging dual monitor dock
Public bug reported: When plugging in my Cable Matters USB-C Dual 4K DisplayPort Docking Station into my system, after it has already booted, the system hangs with a kernel OOPS. This is always repeatable. Steps to reproduce: 1. Ensure docking station is unplugged or shut-off. 2. Boot up computer. 3. Turn-on docking station and plug into to system. If the docking station is plugged in before the system boots, it works fine. It can even be unpluged and hot-plugged without issue at that point. This kernel Oops occurs when the system hangs: BUG: unable to handle kernel NULL pointer dereference at 0320 PGD 0 P4D 0 SMP NOPTI CPU: 3 PID: 84 Comm: kworker/3:1 Tainted: G DOE 4.18.0-16-generic #17-Ubuntu Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 Workqueue: events_long drm_dp_mst_link_probe_work [drm_kms_helper] RIP: 0010:mutex_lock+0x1d/0x30 Code: 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb e8 8e df ff ff 31 c0 65 48 8b 14 25 00 5c 01 00 48 0f b1 13 74 08 48 89 df e8 b4 ff ff ff 5b 5d c3 90 0f 1f 44 RSP: 0018:b6c0c1efbd78 EFLAGS: 00010246 RAX: RBX: 0320 RCX: 8ed7cfb5c800 RDX: 8ed7d383 RSI: 0202 RDI: 0320 RBP: b6c0c1efbd80 R08: 0201 R09: R10: R11: 8ed7df6e1ac8 R12: R13: 8ed7cfb5c468 R14: 8ed7d3b33f60 R15: FS: () GS:8ed7df6c() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0320 CR3: 0003b5d6e000 CR4: 003406a0 Call Trace: drm_dp_mst_wait_tx_reply+0x155/0x1f0 [drm_kms_helper] ? wait_woken+0x80/0x80 drm_dp_send_enum_path_resources.isra.24+0x69/0xf0 [drm_kms_helper] drm_dp_check_and_send_link_address+0xa1/0xd0 [drm_kms_helper] drm_dp_mst_link_probe_work+0x4f/0x80 [drm_kms_helper] process_one_work+0x20f/0x410 worker_thread+0x34/0x400 kthread+0x120/0x140 ? pwq_unbound_release_workfn+0xd0/0xd0 ? kthread_bind+0x40/0x40 ret_from_fork+0x22/0x40 Modules linked in: snd_usb_audio snd_usbmidi_lib usbhid cdc_ether uas usbnet usb_storage r8152 rfcomm binfmt_misc ccm cmac bnep btusb btrtl btbcm btintel bluetooth ecdh_generic uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media evdi(OE) nfc arc4 joydev nls_iso8859_1 snd_hda_codec_conexant snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec edac_mce_amd snd_hda_core snd_hwdep kvm_amd ccp kvm irqbypass snd_pcm crct10dif_pclmul iwlmvm crc32_pclmul ghash_clmulni_intel pcbc snd_seq_midi snd_seq_midi_event mac80211 snd_rawmidi snd_seq snd_seq_device snd_timer iwlwifi aesni_intel snd hp_wmi aes_x86_64 crypto_simd cryptd input_leds glue_helper wmi_bmof serio_raw sparse_keymap hid_multitouch k10temp soundcore cfg80211 ipmi_devintf ipmi_msghandler ucsi_acpi typec_ucsi typec mac_hid hp_wireless sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic amdkfd amd_iommu_v2 amdgpu chash gpu_sched i2c_algo_bit ttm nvme drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm ahci libahci r8169 nvme_core i2c_piix4 mii i2c_hid wmi hid video CR2: 0320 ---[ end trace 3aa69f7fb354f0c1 ]--- BUG: unable to handle kernel NULL pointer dereference at 0320 PGD 0 P4D 0 RIP: 0010:queue_work_on+0x1b/0x40 Code: SMP NOPTI CPU: 0 PID: 974 Comm: Xorg Tainted: G DOE 4.18.0-16-generic #17-Ubuntu Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 RIP: 0010:mutex_lock+0x1d/0x30 Code: 5d c3 58 66 66 2e 0f 01 01 e8 69 1f 84 00 27 fe ff 00 0f 0b e9 00 b5 fc ff 00 ff 0f 1f 00 44 00 00 0f 55 48 89 e5 1f 44 00 53 00 55 48 9c 89 e5 53 58 0f 1f 48 44 00 00 48 89 fb e8 89 c3 fa 8e 66 0f 1f df 44 00 00 ff 48 0f ba 2a ff 31 c0 00 65 48 8b 73 11 31 c9 14 25 00 48 89 df 57 5c 01 00 9d 0f 1f 44 00 00 89 48 0f b1 c8 RSP: 0018:b6c0c2063c98 EFLAGS: 00010002 13 RAX: 0202 RBX: 0202 RCX: 74 08 48 89 RDX: 03a8 RSI: 8ed7df019000 RDI: 2000 df e8 b4 RBP: b6c0c2063ca0 R08: 00027080 R09: a25d9e13 R10: fa628ed74840 R11: 0036 R12: 8ed7cfb5c5e6 R13: 8ed7801fa800 R14: 0001 R15: 8ed7d3b33f60 FS: () GS:8ed7df6c() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0320 CR3: 0003b5d6e000 CR4: 003406a0 ff ff ff 5b 5d c3 90 0f 1f 44 RSP: 0018:b6c0c2b3b858 EFLAGS: 00010246 RAX: RBX: 0320 RCX: 8ed7cfb5c800 RDX: 8ed7da888000 RSI: 0206 RDI: 0320 RBP: b6c0c2b3b860 R08: 0206 R09: R10: R11: 8ed7df621ac8 R12: R13: 8ed7cfb5c468 R14: 8ed7d3b33f60 R15:
[Kernel-packages] [Bug 1819924] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819924 Title: System hangs when hot-plugging dual monitor dock Status in linux package in Ubuntu: Confirmed Bug description: When plugging in my Cable Matters USB-C Dual 4K DisplayPort Docking Station into my system, after it has already booted, the system hangs with a kernel OOPS. This is always repeatable. Steps to reproduce: 1. Ensure docking station is unplugged or shut-off. 2. Boot up computer. 3. Turn-on docking station and plug into to system. If the docking station is plugged in before the system boots, it works fine. It can even be unpluged and hot-plugged without issue at that point. This kernel Oops occurs when the system hangs: BUG: unable to handle kernel NULL pointer dereference at 0320 PGD 0 P4D 0 SMP NOPTI CPU: 3 PID: 84 Comm: kworker/3:1 Tainted: G DOE 4.18.0-16-generic #17-Ubuntu Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 Workqueue: events_long drm_dp_mst_link_probe_work [drm_kms_helper] RIP: 0010:mutex_lock+0x1d/0x30 Code: 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb e8 8e df ff ff 31 c0 65 48 8b 14 25 00 5c 01 00 48 0f b1 13 74 08 48 89 df e8 b4 ff ff ff 5b 5d c3 90 0f 1f 44 RSP: 0018:b6c0c1efbd78 EFLAGS: 00010246 RAX: RBX: 0320 RCX: 8ed7cfb5c800 RDX: 8ed7d383 RSI: 0202 RDI: 0320 RBP: b6c0c1efbd80 R08: 0201 R09: R10: R11: 8ed7df6e1ac8 R12: R13: 8ed7cfb5c468 R14: 8ed7d3b33f60 R15: FS: () GS:8ed7df6c() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0320 CR3: 0003b5d6e000 CR4: 003406a0 Call Trace: drm_dp_mst_wait_tx_reply+0x155/0x1f0 [drm_kms_helper] ? wait_woken+0x80/0x80 drm_dp_send_enum_path_resources.isra.24+0x69/0xf0 [drm_kms_helper] drm_dp_check_and_send_link_address+0xa1/0xd0 [drm_kms_helper] drm_dp_mst_link_probe_work+0x4f/0x80 [drm_kms_helper] process_one_work+0x20f/0x410 worker_thread+0x34/0x400 kthread+0x120/0x140 ? pwq_unbound_release_workfn+0xd0/0xd0 ? kthread_bind+0x40/0x40 ret_from_fork+0x22/0x40 Modules linked in: snd_usb_audio snd_usbmidi_lib usbhid cdc_ether uas usbnet usb_storage r8152 rfcomm binfmt_misc ccm cmac bnep btusb btrtl btbcm btintel bluetooth ecdh_generic uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media evdi(OE) nfc arc4 joydev nls_iso8859_1 snd_hda_codec_conexant snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec edac_mce_amd snd_hda_core snd_hwdep kvm_amd ccp kvm irqbypass snd_pcm crct10dif_pclmul iwlmvm crc32_pclmul ghash_clmulni_intel pcbc snd_seq_midi snd_seq_midi_event mac80211 snd_rawmidi snd_seq snd_seq_device snd_timer iwlwifi aesni_intel snd hp_wmi aes_x86_64 crypto_simd cryptd input_leds glue_helper wmi_bmof serio_raw sparse_keymap hid_multitouch k10temp soundcore cfg80211 ipmi_devintf ipmi_msghandler ucsi_acpi typec_ucsi typec mac_hid hp_wireless sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic amdkfd amd_iommu_v2 amdgpu chash gpu_sched i2c_algo_bit ttm nvme drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm ahci libahci r8169 nvme_core i2c_piix4 mii i2c_hid wmi hid video CR2: 0320 ---[ end trace 3aa69f7fb354f0c1 ]--- BUG: unable to handle kernel NULL pointer dereference at 0320 PGD 0 P4D 0 RIP: 0010:queue_work_on+0x1b/0x40 Code: SMP NOPTI CPU: 0 PID: 974 Comm: Xorg Tainted: G DOE 4.18.0-16-generic #17-Ubuntu Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 RIP: 0010:mutex_lock+0x1d/0x30 Code: 5d c3 58 66 66 2e 0f 01 01 e8 69 1f 84 00 27 fe ff 00 0f 0b e9 00 b5 fc ff 00 ff 0f 1f 00 44 00 00 0f 55 48 89 e5 1f 44 00 53 00 55 48 9c 89 e5 53 58 0f 1f 48 44 00 00 48 89 fb e8 89 c3 fa 8e 66 0f 1f df 44 00 00 ff 48 0f ba 2a ff 31 c0 00 65 48 8b 73 11 31 c9 14 25 00 48 89 df 57 5c 01 00 9d 0f 1f 44 00 00 89 48 0f b1 c8 RSP: 0018:b6c0c2063c98 EFLAGS: 00010002 13 RAX: 0202 RBX: 0202 RCX: 74 08 48 89 RDX: 03a8 RSI: 8ed7df019000 RDI: 2000 df e8 b4 RBP: b6c0c2063ca0 R08: 00027080 R09: a25d9e13 R10: fa628ed74840 R11: 0036 R12: 8ed7cfb5c5e6 R13: 8ed7801fa800 R14: 0001 R15: 8ed7d3b33f60 FS:
[Kernel-packages] [Bug 1819624] Re: linux: 4.18.0-17.18 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819623 (bionic/linux-hwe) derivatives: bug 1819612 (linux-raspi2), bug 1819614 (linux-aws), bug 1819618 (linux-azure), bug 1819620 (linux-gcp), bug 1819621 (linux-kvm) -- swm properties -- phase: Packaging phase-changed: Wednesday, 13. March 2019 11:36 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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819624 Title: linux: 4.18.0-17.18 -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: 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819623 (bionic/linux-hwe) derivatives: bug 1819612 (linux-raspi2), bug 1819614 (linux-aws), bug 1819618 (linux-azure), bug 1819620 (linux-gcp), bug 1819621 (linux-kvm) -- swm properties -- phase: Packaging phase-changed: Wednesday, 13. March 2019 11:36 UTC reason: 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/1819624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819917] Re: linux: 3.13.0-167.217 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - phase: Ready for Packaging - phase-changed: Wednesday, 13. March 2019 14:29 UTC + phase: Packaging + phase-changed: Wednesday, 13. March 2019 15:02 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 in Ubuntu. https://bugs.launchpad.net/bugs/1819917 Title: linux: 3.13.0-167.217 -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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Packaging phase-changed: Wednesday, 13. March 2019 15:02 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/1819917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819921] 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 1819921 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/1819921 Title: [SRU] [B/OEM] Fix ACPI bug that causes boot failure Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Some systems boot failed at a very early stage, only blackscreen shown. [Fix] Some system BIOS set definition in if statement, it would be deferred to be loaded. Some devices would not work properly and cause a system lockup. execute all acpi tables to make system work properly. [Test] Tested on several laptops, the laptop that failed to boot boots well. Other laptops still works fine. [Regression Potential] Upstream fix. Low risk. Backported changes is one line of debug ouput sentence in nsparse.c: s/Start table execution pass/Start load pass/ Verified on several laptops. Fix boot failure and no regression found. This patch is from 4.17-rc1, so only Bionic/OEM 4.15 kernels need it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1819921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
** Description changed: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] - Check that the user session uses the proper driver on these systems. + Check that the user session uses the proper driver on these systems, if possible. Adding new pci-id's is a trivial change which can't regress existing hw. [Regression potential] none, these just add pci-id's and platform definitions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems, if possible. Adding new pci-id's is a trivial change which can't regress existing hw. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814646] Re: linux-lts-trusty: 3.13.0-166.216~precise1 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814645 phase: Release phase-changed: Wednesday, 13. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-security: Ongoing -- packages not yet published - promote-to-updates: Ongoing -- packages not yet published ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1814646 Title: linux-lts-trusty: 3.13.0-166.216~precise1 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: 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-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: 1814645 phase: Release phase-changed: Wednesday, 13. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
bionic was already fixed earlier by 18.2.2-0ubuntu1~18.04.2 in time for 18.04.2 release cosmic got the exact same oneliner in 18.2.8-0ubuntu0~blah, and then that was backported to bionic which reopened this bug. Requiring Alkis to test this on cosmic is too much IMO, as it would involve first to set up a school to use cosmic, then test remotely or ask folks over there to report back... all for a oneliner. Alkis, please correct me if I'm wrong.. ** Description changed: - Several schools reported black screens after normally updating their - Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. + [Impact] + Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: - * systemctl --failed says "gpu-manager" and "lightdm" have failed - * Xorg.log is clean: https://termbin.com/6l2b - * dmesg too: https://termbin.com/ip4e - * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. - * If one runs `xinit` from ssh, it fails with: + * systemctl --failed says "gpu-manager" and "lightdm" have failed + * Xorg.log is clean: https://termbin.com/6l2b + * dmesg too: https://termbin.com/ip4e + * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. + * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument + + This is caused by mesa assuming that soft-pinning on GEN8+ is working + since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a + proper fix would be to backport commits from 4.19.3/4.20 to fix GTT + sizes/pin flags, but that's left for future. + + [Test case] + install fixed mesa or kernel, check that the regression is fixed + + [Regression potential] + mesa: shouldn't be any, it just reverts the change to always soft-pin + (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781533] Re: SATA device is not going to DEVSLP
** Changed in: oem-priority Status: Triaged => Fix Released -- 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/1781533 Title: SATA device is not going to DEVSLP Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-oem source package in Cosmic: Fix Released Bug description: [Impact] Any of the platforms we’ve been seeing SATA problems not going to deepest state leads to other devices not getting there during long idle or s2idle. And it also prevents the system from entering deeper PC state other than PC3. [Fix] Suggested from Intel and Dell to contains the following 4 commits, and all of 4 commits are in v4.19-rc1 https://patchwork.kernel.org/patch/10502285/ https://patchwork.kernel.org/patch/10502287/ https://patchwork.kernel.org/patch/10535781/ https://patchwork.kernel.org/patch/10535783/ [Test] Verified the power consumption on some new platforms, it improves the SATA HDD power consumption around 0.5w during long idle. [Regression Potential] Low, the DEVSLP function is already validated when shipped with SLP_S0 support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1781533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
I am sorry, but what is going on? The authors of some posts in this thread say that they are using a patched kernel. Yet, the developer, Aaron, seems to say one does not need patches . However, that same developer seems to say that his work has *not yet* become incorporated into the kernel. (Meanwhile I continue to try various combinations to get my touchpad to work after deep sleep and it still does not.) If the patches *are* now incorporated into a version of the Linux kernel, then *which kernel version(s)* is/are at issue? If the patches are *not* yet incorporated into a version of the Linux kernel, then - as I asked previously - how does one apply the patches? Can one do so without compiling the kernel oneself? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
[Kernel-packages] [Bug 1819921] Re: [SRU] [B/OEM] Fix ACPI bug that causes boot failure
** Description changed: [Impact] Some systems boot failed at a very early stage, only blackscreen shown. [Fix] Some system BIOS set definition in if statement, it would be deferred to be loaded. Some devices would not work properly and cause a system lockup. execute all acpi tables to make system work properly. [Test] Tested on several laptops, the laptop that failed to boot boots well. Other laptops still works fine. [Regression Potential] Upstream fix. Low risk. Backported changes is one line of debug ouput sentence in nsparse.c: s/Start table execution pass/Start load pass/ Verified on several laptops. Fix boot failure and no regression found. + + This patch is from 4.17-rc1, so only Bionic/OEM 4.15 kernels need it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819921 Title: [SRU] [B/OEM] Fix ACPI bug that causes boot failure Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Some systems boot failed at a very early stage, only blackscreen shown. [Fix] Some system BIOS set definition in if statement, it would be deferred to be loaded. Some devices would not work properly and cause a system lockup. execute all acpi tables to make system work properly. [Test] Tested on several laptops, the laptop that failed to boot boots well. Other laptops still works fine. [Regression Potential] Upstream fix. Low risk. Backported changes is one line of debug ouput sentence in nsparse.c: s/Start table execution pass/Start load pass/ Verified on several laptops. Fix boot failure and no regression found. This patch is from 4.17-rc1, so only Bionic/OEM 4.15 kernels need it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1819921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker
Still did not get further update from our customer. Please feel free to invalid certification-testing to move forward by following the original release schedule. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814647 Title: linux: 4.4.0-143.169 -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: In Progress 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 1814648 (linux-aws), bug 1814649 (linux-lts-xenial) derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 (linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Tuesday, 26. February 2019 14:24 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/1814647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819917] [NEW] linux: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** 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/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.02.04-6 trusty ** 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/verification-testing Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) 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-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided
[Kernel-packages] [Bug 1816564] Re: java breaks on this kernel
Hello there I'm seeing this issue too on Ubuntu 16.04.6 with kernel 4.4.0-142. We had to revert back to kernel 4.4.0-141 for java to work again. I think, I have identified this commit https://kernel.ubuntu.com/git/ubuntu/ubuntu- xenial.git/commit/?id=1096e1455d67b0c804c8936947a82971ebab0644 as the root cause of the issue. Best regards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816564 Title: java breaks on this kernel Status in linux package in Ubuntu: Confirmed Bug description: I reverted back to 4.15.0-20-generic for proper java operations gge@jasperserver:~$ java -version java version "1.8.0_191" Java(TM) SE Runtime Environment (build 1.8.0_191-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode) with kernel 4.15.0-45-generic java processes just get terminated: root@jasperserver:/opt# java -jar jboss-eap-6.4.0-installer.jar Exception in thread "Thread-1" java.lang.RuntimeException: broken pipe at org.jboss.aesh.console.reader.ConsoleInputSession$2.run(ConsoleInputSession.java:95) Select language : 0: eng 1: chn 2: deu 3: fra 4: jpn 5: por 6: spa Please choose [0] : Invalid file. Please specify the correct XML file. root@jasperserver:/opt# root@jasperserver:/opt/EAP-6.4/bin# ./jboss-cli.sh Exception in thread "Thread-2" java.lang.RuntimeException: broken pipe at org.jboss.aesh.console.reader.ConsoleInputSession$2.run(ConsoleInputSession.java:95) You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. [disconnected /] root@jasperserver:/opt/EAP-6.4/bin# ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. 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/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Tue Feb 19 13:34:12 2019 HibernationDevice: RESUME=/dev/mapper/jasperserver--vg-swap_1 InstallationDate: Installed on 2019-02-15 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm PATH=(custom, no user) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
This was already fixed in bionic by 18.2.2-0ubuntu1~18.04.1, now the same is included upstream in 18.2.8 which was upload to cosmic too as well as to bionic via a new backport. Again, I don't have the hardware (AML, WHL is broken atm), adding pci- id's just allow the X driver to load the DRI driver, there is no regression potential on other hw etc etc. So in a way this bug should've been marked 'invalid' for cosmic and just let it be part of 18.2.8 upstream version which is handled separately in bug 1811225.. My bad for including it in the changelog. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems, if possible. Adding new pci-id's is a trivial change which can't regress existing hw. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819918] [NEW] Nouveau deadlocks system
Public bug reported: Ubuntu 18.04 w/ kernel 4.18.0-15 or 4.19.28 w/ nouveau driver on top of Xen 4.11.1 regularly deadlocks system. It's reachable via network for a bit, then becomes completely unresponsive. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kerneloops 0.12+git20140509-6ubuntu2 Uname: Linux 4.19.28-041928-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 13 09:13:27 2019 InstallationDate: Installed on 2019-02-08 (32 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kerneloops UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kerneloops (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/1819918 Title: Nouveau deadlocks system Status in kerneloops package in Ubuntu: New Bug description: Ubuntu 18.04 w/ kernel 4.18.0-15 or 4.19.28 w/ nouveau driver on top of Xen 4.11.1 regularly deadlocks system. It's reachable via network for a bit, then becomes completely unresponsive. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kerneloops 0.12+git20140509-6ubuntu2 Uname: Linux 4.19.28-041928-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 13 09:13:27 2019 InstallationDate: Installed on 2019-02-08 (32 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kerneloops UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1819918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819918] Re: Nouveau deadlocks system
I reported this incorrectly, since the actual traces aren't included. Here's the kernel log. ** Attachment added: "kern.log-20190313" https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1819918/+attachment/5245858/+files/kern.log-20190313 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/1819918 Title: Nouveau deadlocks system Status in kerneloops package in Ubuntu: New Bug description: Ubuntu 18.04 w/ kernel 4.18.0-15 or 4.19.28 w/ nouveau driver on top of Xen 4.11.1 regularly deadlocks system. It's reachable via network for a bit, then becomes completely unresponsive. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kerneloops 0.12+git20140509-6ubuntu2 Uname: Linux 4.19.28-041928-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 13 09:13:27 2019 InstallationDate: Installed on 2019-02-08 (32 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kerneloops UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1819918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814755] Re: linux-raspi2: 4.18.0-1010.12 -proposed tracker
This bug was fixed in the package linux-raspi2 - 4.18.0-1010.12 --- linux-raspi2 (4.18.0-1010.12) cosmic; urgency=medium * linux-raspi2: 4.18.0-1010.12 -proposed tracker (LP: #1814755) * bluetooth controller not detected with 4.15 kernel (LP: #1810797) - [Config] Disable BT_QCOMSMD_HACK * rpi-cm3 dtb is not present in the arm64 variant (LP: #1813133) - devicetree: add RPi CM3 dts to arm64; mimic the RPi 3B arm64 dts implementation, by referring to the actual dts file in the arm directory [ Ubuntu: 4.18.0-16.17 ] * linux: 4.18.0-16.17 -proposed tracker (LP: #1814749) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2018-16880 - vhost: fix OOB in get_rx_bufs() * RTL8822BE WiFi Disabled in Kernel 4.18.0-12 (LP: #1806472) - SAUCE: staging: rtlwifi: allow RTLWIFI_DEBUG_ST to be disabled - [Config] CONFIG_RTLWIFI_DEBUG_ST=n - SAUCE: Add r8822be to signature inclusion list * kernel oops in bcache module (LP: #1793901) - SAUCE: bcache: never writeback a discard operation * CVE-2018-18397 - userfaultfd: use ENOENT instead of EFAULT if the atomic copy user fails - userfaultfd: shmem: allocate anonymous memory for MAP_PRIVATE shmem - userfaultfd: shmem/hugetlbfs: only allow to register VM_MAYWRITE vmas - userfaultfd: shmem: add i_size checks - userfaultfd: shmem: UFFDIO_COPY: set the page dirty if VM_WRITE is not set * Ignore "incomplete report" from Elan touchpanels (LP: #1813733) - HID: i2c-hid: Ignore input report if there's no data present on Elan touchpanels * Vsock connect fails with ENODEV for large CID (LP: #1813934) - vhost/vsock: fix vhost vsock cid hashing inconsistent * Fix non-working pinctrl-intel (LP: #1811777) - pinctrl: intel: Do pin translation in other GPIO operations as well * ip6_gre: fix tunnel list corruption for x-netns (LP: #1812875) - ip6_gre: fix tunnel list corruption for x-netns * Backported commit breaks audio (fixed upstream) (LP: #1811566) - ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards using pmc_plt_clk_0 - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Clapper - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty * kvm_stat : missing python dependency (LP: #1798776) - tools/kvm_stat: switch to python3 * [SRU] Fix Xorg crash with nomodeset when BIOS enable 64-bit fb addr (LP: #1812797) - vgaarb: Add support for 64-bit frame buffer address - vgaarb: Keep adding VGA device in queue * Fix non-working QCA Rome Bluetooth after S3 (LP: #1812812) - USB: Add new USB LPM helpers - USB: Consolidate LPM checks to avoid enabling LPM twice * [SRU] IO's are issued with incorrect Scatter Gather Buffer (LP: #1795453) - scsi: megaraid_sas: Use 63-bit DMA addressing * x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a (LP: #1813532) - x86/mm: Do not warn about PCI BIOS W+X mappings * CVE-2019-6133 - fork: record start_time late * Fix not working Goodix touchpad (LP: #1811929) - HID: i2c-hid: Disable runtime PM on Goodix touchpad * bluetooth controller not detected with 4.15 kernel (LP: #1810797) - SAUCE: btqcomsmd: introduce BT_QCOMSMD_HACK - [Config] arm64: snapdragon: BT_QCOMSMD_HACK=y * X1 Extreme: only one of the two SSDs is loaded (LP: #1811755) - nvme-core: rework a NQN copying operation - nvme: pad fake subsys NQN vid and ssvid with zeros - nvme: introduce NVME_QUIRK_IGNORE_DEV_SUBNQN * Crash on "ip link add foo type ipip" (LP: #1811803) - SAUCE: fan: Fix NULL pointer dereference [ Ubuntu: 4.18.0-15.16 ] * Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) (LP: #1814555) - Revert "drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5" * Userspace break as a result of missing patch backport (LP: #1813873) - tty: Don't hold ldisc lock in tty_reopen() if ldisc present -- Khalid Elmously Mon, 11 Feb 2019 06:00:26 + ** Changed in: linux-raspi2 (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1814755 Title: linux-raspi2: 4.18.0-1010.12 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid
[Kernel-packages] [Bug 1813133] Re: rpi-cm3 dtb is not present in the arm64 variant
This bug was fixed in the package linux-raspi2 - 4.18.0-1010.12 --- linux-raspi2 (4.18.0-1010.12) cosmic; urgency=medium * linux-raspi2: 4.18.0-1010.12 -proposed tracker (LP: #1814755) * bluetooth controller not detected with 4.15 kernel (LP: #1810797) - [Config] Disable BT_QCOMSMD_HACK * rpi-cm3 dtb is not present in the arm64 variant (LP: #1813133) - devicetree: add RPi CM3 dts to arm64; mimic the RPi 3B arm64 dts implementation, by referring to the actual dts file in the arm directory [ Ubuntu: 4.18.0-16.17 ] * linux: 4.18.0-16.17 -proposed tracker (LP: #1814749) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2018-16880 - vhost: fix OOB in get_rx_bufs() * RTL8822BE WiFi Disabled in Kernel 4.18.0-12 (LP: #1806472) - SAUCE: staging: rtlwifi: allow RTLWIFI_DEBUG_ST to be disabled - [Config] CONFIG_RTLWIFI_DEBUG_ST=n - SAUCE: Add r8822be to signature inclusion list * kernel oops in bcache module (LP: #1793901) - SAUCE: bcache: never writeback a discard operation * CVE-2018-18397 - userfaultfd: use ENOENT instead of EFAULT if the atomic copy user fails - userfaultfd: shmem: allocate anonymous memory for MAP_PRIVATE shmem - userfaultfd: shmem/hugetlbfs: only allow to register VM_MAYWRITE vmas - userfaultfd: shmem: add i_size checks - userfaultfd: shmem: UFFDIO_COPY: set the page dirty if VM_WRITE is not set * Ignore "incomplete report" from Elan touchpanels (LP: #1813733) - HID: i2c-hid: Ignore input report if there's no data present on Elan touchpanels * Vsock connect fails with ENODEV for large CID (LP: #1813934) - vhost/vsock: fix vhost vsock cid hashing inconsistent * Fix non-working pinctrl-intel (LP: #1811777) - pinctrl: intel: Do pin translation in other GPIO operations as well * ip6_gre: fix tunnel list corruption for x-netns (LP: #1812875) - ip6_gre: fix tunnel list corruption for x-netns * Backported commit breaks audio (fixed upstream) (LP: #1811566) - ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards using pmc_plt_clk_0 - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Clapper - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty * kvm_stat : missing python dependency (LP: #1798776) - tools/kvm_stat: switch to python3 * [SRU] Fix Xorg crash with nomodeset when BIOS enable 64-bit fb addr (LP: #1812797) - vgaarb: Add support for 64-bit frame buffer address - vgaarb: Keep adding VGA device in queue * Fix non-working QCA Rome Bluetooth after S3 (LP: #1812812) - USB: Add new USB LPM helpers - USB: Consolidate LPM checks to avoid enabling LPM twice * [SRU] IO's are issued with incorrect Scatter Gather Buffer (LP: #1795453) - scsi: megaraid_sas: Use 63-bit DMA addressing * x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a (LP: #1813532) - x86/mm: Do not warn about PCI BIOS W+X mappings * CVE-2019-6133 - fork: record start_time late * Fix not working Goodix touchpad (LP: #1811929) - HID: i2c-hid: Disable runtime PM on Goodix touchpad * bluetooth controller not detected with 4.15 kernel (LP: #1810797) - SAUCE: btqcomsmd: introduce BT_QCOMSMD_HACK - [Config] arm64: snapdragon: BT_QCOMSMD_HACK=y * X1 Extreme: only one of the two SSDs is loaded (LP: #1811755) - nvme-core: rework a NQN copying operation - nvme: pad fake subsys NQN vid and ssvid with zeros - nvme: introduce NVME_QUIRK_IGNORE_DEV_SUBNQN * Crash on "ip link add foo type ipip" (LP: #1811803) - SAUCE: fan: Fix NULL pointer dereference [ Ubuntu: 4.18.0-15.16 ] * Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) (LP: #1814555) - Revert "drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5" * Userspace break as a result of missing patch backport (LP: #1813873) - tty: Don't hold ldisc lock in tty_reopen() if ldisc present -- Khalid Elmously Mon, 11 Feb 2019 06:00:26 + ** Changed in: linux-raspi2 (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1813133 Title: rpi-cm3 dtb is not present in the arm64 variant Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Bionic: Fix Released Status in linux-raspi2 source package in Cosmic: Fix Released Bug description: Impact: The dtb for the Raspberry CM3 board is not shipped in the Bionic -raspi2 kernel arm64 variant. Fix: The dtb for the cm3 board was not compiled at all, in the arm64 arch - apply the attached patch and recompile. How to test: The linux-modules-*-raspi2_arm64.deb should contain the bcm2710-rpi- cm3 dtb now: $ dpkg -x linux-modules-4.15.0-1031-raspi2_4.15.0-1031.33_arm64.deb
[Kernel-packages] [Bug 1814759] Re: linux-gcp: 4.18.0-1007.8 -proposed tracker
This bug was fixed in the package linux-gcp - 4.18.0-1007.8 --- linux-gcp (4.18.0-1007.8) cosmic; urgency=medium * linux-gcp: 4.18.0-1007.8 -proposed tracker (LP: #1814759) * bluetooth controller not detected with 4.15 kernel (LP: #1810797) - [Config] Disable BT_QCOMSMD_HACK [ Ubuntu: 4.18.0-16.17 ] * linux: 4.18.0-16.17 -proposed tracker (LP: #1814749) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2018-16880 - vhost: fix OOB in get_rx_bufs() * RTL8822BE WiFi Disabled in Kernel 4.18.0-12 (LP: #1806472) - SAUCE: staging: rtlwifi: allow RTLWIFI_DEBUG_ST to be disabled - [Config] CONFIG_RTLWIFI_DEBUG_ST=n - SAUCE: Add r8822be to signature inclusion list * kernel oops in bcache module (LP: #1793901) - SAUCE: bcache: never writeback a discard operation * CVE-2018-18397 - userfaultfd: use ENOENT instead of EFAULT if the atomic copy user fails - userfaultfd: shmem: allocate anonymous memory for MAP_PRIVATE shmem - userfaultfd: shmem/hugetlbfs: only allow to register VM_MAYWRITE vmas - userfaultfd: shmem: add i_size checks - userfaultfd: shmem: UFFDIO_COPY: set the page dirty if VM_WRITE is not set * Ignore "incomplete report" from Elan touchpanels (LP: #1813733) - HID: i2c-hid: Ignore input report if there's no data present on Elan touchpanels * Vsock connect fails with ENODEV for large CID (LP: #1813934) - vhost/vsock: fix vhost vsock cid hashing inconsistent * Fix non-working pinctrl-intel (LP: #1811777) - pinctrl: intel: Do pin translation in other GPIO operations as well * ip6_gre: fix tunnel list corruption for x-netns (LP: #1812875) - ip6_gre: fix tunnel list corruption for x-netns * Backported commit breaks audio (fixed upstream) (LP: #1811566) - ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards using pmc_plt_clk_0 - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Clapper - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty * kvm_stat : missing python dependency (LP: #1798776) - tools/kvm_stat: switch to python3 * [SRU] Fix Xorg crash with nomodeset when BIOS enable 64-bit fb addr (LP: #1812797) - vgaarb: Add support for 64-bit frame buffer address - vgaarb: Keep adding VGA device in queue * Fix non-working QCA Rome Bluetooth after S3 (LP: #1812812) - USB: Add new USB LPM helpers - USB: Consolidate LPM checks to avoid enabling LPM twice * [SRU] IO's are issued with incorrect Scatter Gather Buffer (LP: #1795453) - scsi: megaraid_sas: Use 63-bit DMA addressing * x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a (LP: #1813532) - x86/mm: Do not warn about PCI BIOS W+X mappings * CVE-2019-6133 - fork: record start_time late * Fix not working Goodix touchpad (LP: #1811929) - HID: i2c-hid: Disable runtime PM on Goodix touchpad * bluetooth controller not detected with 4.15 kernel (LP: #1810797) - SAUCE: btqcomsmd: introduce BT_QCOMSMD_HACK - [Config] arm64: snapdragon: BT_QCOMSMD_HACK=y * X1 Extreme: only one of the two SSDs is loaded (LP: #1811755) - nvme-core: rework a NQN copying operation - nvme: pad fake subsys NQN vid and ssvid with zeros - nvme: introduce NVME_QUIRK_IGNORE_DEV_SUBNQN * Crash on "ip link add foo type ipip" (LP: #1811803) - SAUCE: fan: Fix NULL pointer dereference [ Ubuntu: 4.18.0-15.16 ] * Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) (LP: #1814555) - Revert "drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5" * Userspace break as a result of missing patch backport (LP: #1813873) - tty: Don't hold ldisc lock in tty_reopen() if ldisc present -- Khalid Elmously Tue, 12 Feb 2019 01:13:50 + ** Changed in: linux-gcp (Ubuntu) Status: Invalid => Fix Released -- 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/1814759 Title: linux-gcp: 4.18.0-1007.8 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU
[Kernel-packages] [Bug 1814760] Re: linux-kvm: 4.18.0-1008.8 -proposed tracker
This bug was fixed in the package linux-kvm - 4.18.0-1008.8 --- linux-kvm (4.18.0-1008.8) cosmic; urgency=medium * linux-kvm: 4.18.0-1008.8 -proposed tracker (LP: #1814760) [ Ubuntu: 4.18.0-16.17 ] * linux: 4.18.0-16.17 -proposed tracker (LP: #1814749) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2018-16880 - vhost: fix OOB in get_rx_bufs() * RTL8822BE WiFi Disabled in Kernel 4.18.0-12 (LP: #1806472) - SAUCE: staging: rtlwifi: allow RTLWIFI_DEBUG_ST to be disabled - [Config] CONFIG_RTLWIFI_DEBUG_ST=n - SAUCE: Add r8822be to signature inclusion list * kernel oops in bcache module (LP: #1793901) - SAUCE: bcache: never writeback a discard operation * CVE-2018-18397 - userfaultfd: use ENOENT instead of EFAULT if the atomic copy user fails - userfaultfd: shmem: allocate anonymous memory for MAP_PRIVATE shmem - userfaultfd: shmem/hugetlbfs: only allow to register VM_MAYWRITE vmas - userfaultfd: shmem: add i_size checks - userfaultfd: shmem: UFFDIO_COPY: set the page dirty if VM_WRITE is not set * Ignore "incomplete report" from Elan touchpanels (LP: #1813733) - HID: i2c-hid: Ignore input report if there's no data present on Elan touchpanels * Vsock connect fails with ENODEV for large CID (LP: #1813934) - vhost/vsock: fix vhost vsock cid hashing inconsistent * Fix non-working pinctrl-intel (LP: #1811777) - pinctrl: intel: Do pin translation in other GPIO operations as well * ip6_gre: fix tunnel list corruption for x-netns (LP: #1812875) - ip6_gre: fix tunnel list corruption for x-netns * Backported commit breaks audio (fixed upstream) (LP: #1811566) - ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards using pmc_plt_clk_0 - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Clapper - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty * kvm_stat : missing python dependency (LP: #1798776) - tools/kvm_stat: switch to python3 * [SRU] Fix Xorg crash with nomodeset when BIOS enable 64-bit fb addr (LP: #1812797) - vgaarb: Add support for 64-bit frame buffer address - vgaarb: Keep adding VGA device in queue * Fix non-working QCA Rome Bluetooth after S3 (LP: #1812812) - USB: Add new USB LPM helpers - USB: Consolidate LPM checks to avoid enabling LPM twice * [SRU] IO's are issued with incorrect Scatter Gather Buffer (LP: #1795453) - scsi: megaraid_sas: Use 63-bit DMA addressing * x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a (LP: #1813532) - x86/mm: Do not warn about PCI BIOS W+X mappings * CVE-2019-6133 - fork: record start_time late * Fix not working Goodix touchpad (LP: #1811929) - HID: i2c-hid: Disable runtime PM on Goodix touchpad * bluetooth controller not detected with 4.15 kernel (LP: #1810797) - SAUCE: btqcomsmd: introduce BT_QCOMSMD_HACK - [Config] arm64: snapdragon: BT_QCOMSMD_HACK=y * X1 Extreme: only one of the two SSDs is loaded (LP: #1811755) - nvme-core: rework a NQN copying operation - nvme: pad fake subsys NQN vid and ssvid with zeros - nvme: introduce NVME_QUIRK_IGNORE_DEV_SUBNQN * Crash on "ip link add foo type ipip" (LP: #1811803) - SAUCE: fan: Fix NULL pointer dereference [ Ubuntu: 4.18.0-15.16 ] * Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) (LP: #1814555) - Revert "drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5" * Userspace break as a result of missing patch backport (LP: #1813873) - tty: Don't hold ldisc lock in tty_reopen() if ldisc present -- Khalid Elmously Mon, 11 Feb 2019 06:20:24 + ** Changed in: linux-kvm (Ubuntu) Status: Invalid => Fix Released -- 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/1814760 Title: linux-kvm: 4.18.0-1008.8 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: 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-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Cosmic: Fix Released Bug description:
[Kernel-packages] [Bug 1819759] Re: linux: 5.0.0-8.9 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-disco ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - phase: Ready for Packaging - phase-changed: Tuesday, 12. March 2019 19:14 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 13. March 2019 13:36 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 -- packages copied but not yet published to -proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819759 Title: linux: 5.0.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: 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 -- phase: Promote to Proposed phase-changed: Wednesday, 13. March 2019 13:36 UTC reason: promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819699] Re: linux-kvm: 4.15.0-1031.31 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.15.0-1031.31 -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) => Andrea Righi (arighi) ** 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) => Andrea Righi (arighi) -- 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/1819699 Title: linux-kvm: 4.15.0-1031.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819716 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 11:05 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819917] Re: linux: 3.13.0-167.217 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 3.13.0-167.217 -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 in Ubuntu. https://bugs.launchpad.net/bugs/1819917 Title: linux: 3.13.0-167.217 -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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 14:29 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819620] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819619 (bionic/linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1819624 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 10:30 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 15:30 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified -- 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/1819620 Title: linux-gcp: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819619 (bionic/linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1819624 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 15:30 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819621] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819624 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 10:52 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 15:36 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified -- 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/1819621 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819624 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 15:36 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819924] Re: System hangs when hot-plugging dual monitor dock
Would it be possible to try kernel < 4.18.0-16? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819924 Title: System hangs when hot-plugging dual monitor dock Status in linux package in Ubuntu: Confirmed Bug description: When plugging in my Cable Matters USB-C Dual 4K DisplayPort Docking Station into my system, after it has already booted, the system hangs with a kernel OOPS. This is always repeatable. Steps to reproduce: 1. Ensure docking station is unplugged or shut-off. 2. Boot up computer. 3. Turn-on docking station and plug into to system. If the docking station is plugged in before the system boots, it works fine. It can even be unpluged and hot-plugged without issue at that point. This kernel Oops occurs when the system hangs: BUG: unable to handle kernel NULL pointer dereference at 0320 PGD 0 P4D 0 SMP NOPTI CPU: 3 PID: 84 Comm: kworker/3:1 Tainted: G DOE 4.18.0-16-generic #17-Ubuntu Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 Workqueue: events_long drm_dp_mst_link_probe_work [drm_kms_helper] RIP: 0010:mutex_lock+0x1d/0x30 Code: 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb e8 8e df ff ff 31 c0 65 48 8b 14 25 00 5c 01 00 48 0f b1 13 74 08 48 89 df e8 b4 ff ff ff 5b 5d c3 90 0f 1f 44 RSP: 0018:b6c0c1efbd78 EFLAGS: 00010246 RAX: RBX: 0320 RCX: 8ed7cfb5c800 RDX: 8ed7d383 RSI: 0202 RDI: 0320 RBP: b6c0c1efbd80 R08: 0201 R09: R10: R11: 8ed7df6e1ac8 R12: R13: 8ed7cfb5c468 R14: 8ed7d3b33f60 R15: FS: () GS:8ed7df6c() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0320 CR3: 0003b5d6e000 CR4: 003406a0 Call Trace: drm_dp_mst_wait_tx_reply+0x155/0x1f0 [drm_kms_helper] ? wait_woken+0x80/0x80 drm_dp_send_enum_path_resources.isra.24+0x69/0xf0 [drm_kms_helper] drm_dp_check_and_send_link_address+0xa1/0xd0 [drm_kms_helper] drm_dp_mst_link_probe_work+0x4f/0x80 [drm_kms_helper] process_one_work+0x20f/0x410 worker_thread+0x34/0x400 kthread+0x120/0x140 ? pwq_unbound_release_workfn+0xd0/0xd0 ? kthread_bind+0x40/0x40 ret_from_fork+0x22/0x40 Modules linked in: snd_usb_audio snd_usbmidi_lib usbhid cdc_ether uas usbnet usb_storage r8152 rfcomm binfmt_misc ccm cmac bnep btusb btrtl btbcm btintel bluetooth ecdh_generic uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media evdi(OE) nfc arc4 joydev nls_iso8859_1 snd_hda_codec_conexant snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec edac_mce_amd snd_hda_core snd_hwdep kvm_amd ccp kvm irqbypass snd_pcm crct10dif_pclmul iwlmvm crc32_pclmul ghash_clmulni_intel pcbc snd_seq_midi snd_seq_midi_event mac80211 snd_rawmidi snd_seq snd_seq_device snd_timer iwlwifi aesni_intel snd hp_wmi aes_x86_64 crypto_simd cryptd input_leds glue_helper wmi_bmof serio_raw sparse_keymap hid_multitouch k10temp soundcore cfg80211 ipmi_devintf ipmi_msghandler ucsi_acpi typec_ucsi typec mac_hid hp_wireless sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic amdkfd amd_iommu_v2 amdgpu chash gpu_sched i2c_algo_bit ttm nvme drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm ahci libahci r8169 nvme_core i2c_piix4 mii i2c_hid wmi hid video CR2: 0320 ---[ end trace 3aa69f7fb354f0c1 ]--- BUG: unable to handle kernel NULL pointer dereference at 0320 PGD 0 P4D 0 RIP: 0010:queue_work_on+0x1b/0x40 Code: SMP NOPTI CPU: 0 PID: 974 Comm: Xorg Tainted: G DOE 4.18.0-16-generic #17-Ubuntu Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 RIP: 0010:mutex_lock+0x1d/0x30 Code: 5d c3 58 66 66 2e 0f 01 01 e8 69 1f 84 00 27 fe ff 00 0f 0b e9 00 b5 fc ff 00 ff 0f 1f 00 44 00 00 0f 55 48 89 e5 1f 44 00 53 00 55 48 9c 89 e5 53 58 0f 1f 48 44 00 00 48 89 fb e8 89 c3 fa 8e 66 0f 1f df 44 00 00 ff 48 0f ba 2a ff 31 c0 00 65 48 8b 73 11 31 c9 14 25 00 48 89 df 57 5c 01 00 9d 0f 1f 44 00 00 89 48 0f b1 c8 RSP: 0018:b6c0c2063c98 EFLAGS: 00010002 13 RAX: 0202 RBX: 0202 RCX: 74 08 48 89 RDX: 03a8 RSI: 8ed7df019000 RDI: 2000 df e8 b4 RBP: b6c0c2063ca0 R08: 00027080 R09: a25d9e13 R10: fa628ed74840 R11: 0036 R12: 8ed7cfb5c5e6 R13: 8ed7801fa800 R14: 0001 R15: 8ed7d3b33f60 FS: () GS:8ed7df6c()
[Kernel-packages] [Bug 1819612] Re: linux-raspi2: 4.18.0-1011.13 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819624 - phase: Packaging - phase-changed: Wednesday, 13. March 2019 12:34 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 13. March 2019 17:07 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: 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-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1819612 Title: linux-raspi2: 4.18.0-1011.13 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819624 phase: Holding before Promote to Proposed phase-changed: Wednesday, 13. March 2019 17:07 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/1819612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819614] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819613 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1819624 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 11:02 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 15:32 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified -- 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/1819614 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819613 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1819624 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 15:32 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
@ALinuxUser: the patches are not yet upstream and thus one has to build a patched kernel yourself. You can follow the upstream process in the links posted from aaronma. For some people it is working because they have a different touchpad. But according to the above discussion even the patches probably wont work for you :/ at your own risk!!! For building a kernel you first have to install all dependencies, should be the following: apt-get install build-essential git wget kernel-package fakeroot dpkg-dev \ libncurses5-dev libssl-dev ccache flex bison libelf-dev tzdata then you need to git clone the kernel source: git clone --depth 1 --branch v5.0.1 git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git get the patches wget -O first.patch https://lkml.org/lkml/diff/2019/2/20/700/1 wget -O second.patch https://lkml.org/lkml/diff/2019/2/20/701/1 apply the patches cd linux git apply ../first.patch git apply ../second.patch clean the repo (just in case) make clean && make mrproper copy the config of your current kernel sudo cp /boot/config-`uname -r` . adjust the config yes '' | make oldconfig and now compile it, can take a while make deb-pkg at your own risk! you can then install the generated deb files -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21
[Kernel-packages] [Bug 1819618] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819617 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1819624 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 11:01 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 13. March 2019 15:36 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified -- 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/1819618 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819617 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1819624 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 15:36 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819869] Re: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin
** Changed in: linux (Ubuntu Trusty) 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/1819869 Title: linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents of /usr/sbin Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Bug description: Version 3.13.0-165.215 of linux-cloud-tools-common has the following contents /. /usr /usr/sbin /usr/sbin/hv_vss_daemon /usr/sbin/hv_kvp_daemon /usr/sbin/hv_fcopy_daemon /usr/sbin/hv_get_dhcp_info /usr/sbin/hv_set_ifconfig /usr/sbin/hv_get_dns_info /usr/share /usr/share/man /usr/share/man/man8 /usr/share/man/man8/hv_kvp_daemon.8.gz /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /usr/share/doc/linux-cloud-tools-common/copyright /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-fcopy-daemon.conf /etc/init/hv-kvp-daemon.conf whereas version 3.13.0-166.216 only contains /. /usr /usr/share /usr/share/doc /usr/share/doc/linux-cloud-tools-common /usr/share/doc/linux-cloud-tools-common/copyright /usr/share/doc/linux-cloud-tools-common/changelog.Debian.gz /etc /etc/init /etc/init/hv-vss-daemon.conf /etc/init/hv-kvp-daemon.conf /etc/init/hv-fcopy-daemon.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
