[Kernel-packages] [Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
Is there an easy way to disable the sensor until a kernel arrives that fixes the problem? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: === SRU Justification === [Impact] [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) [Fix] Let HID core allow longer input report length. [Test] User confirmed the fix works. [Regression Potential] Low. Longer input report length is now considered valid, shorter input report length doesn't get touched. === Original Bug Report === Dmesg is a constant barrage of the same error: ``` [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) ``` This does not occur in 4.19 but does occur in all mainline 4.20 releases including 4.20.13 (linux-image-unsigned-4.20.13-042013). Tested with both Ubuntu's included libinput 1.10 and an updated libinput 1.12. Hardware (from lspci) includes a synaptic touchpad. Having the xorg synaptic driver installed makes no difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822085] Re: Often the VGA screen stops working after screen saver was on
excellent, thanks ** Changed in: linux-oem (Ubuntu) Status: Incomplete => 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/1822085 Title: Often the VGA screen stops working after screen saver was on Status in linux-oem package in Ubuntu: Fix Released Bug description: I have two connected external monitors. They are connected through a Dell Dock W15. One is connected with VGA, the other with DP. Sometimes the VGA monitor complains about the resolution and will not work after the screen saver has been active (and putting the monitors to sleep). When shutting down the system, it then hangs and I have to force a shutdown with the power button. There seems to be a kernel crash before as seen in the dmesg log. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-1034.39-oem 4.15.18 Uname: Linux 4.15.0-1034-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 12:04:07 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-1034-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08af] InstallationDate: Installed on 2019-02-12 (44 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 ProcEnviron: LANG=sv_SE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1034-oem root=UUID=0b807479-b451-4f56-b9cc-307300b68200 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTDY6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTDY6:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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-oem/+bug/1822085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823859] [NEW] NULL pointer dereference in split_swap_cluster
Public bug reported: We have encountered the following oops on one of our VMs: Apr 7 14:02:19 rancher1 kernel: [2089793.273674] BUG: unable to handle kernel NULL pointer dereference at 0007 Apr 7 14:02:19 rancher1 kernel: [2089793.282782] IP: split_swap_cluster+0x4f/0x70 Apr 7 14:02:19 rancher1 kernel: [2089793.330631] PGD 0 P4D 0 Apr 7 14:02:19 rancher1 kernel: [2089793.338279] Oops: 0002 [#1] SMP PTI Apr 7 14:02:19 rancher1 kernel: [2089793.350774] Modules linked in: ufs msdos xfs cmac arc4 md4 nls_utf8 cifs ccm fscache xt_tcpudp xt_set ip_set_hash_net ip_set iptable_raw vxlan ip6_udp_tunnel udp_tunnel xt_nat xt_mark xfrm6_mode_tunnel xfrm4_mode_tunnel esp4 ansi_cprng veth ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter nf_nat br_netfilter bridge stp llc nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_security ip_tables x_tables aufs overlay mlx4_en pci_hyperv hv_balloon serio_raw joydev ib_iser iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 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 crct10dif_pclmul Apr 7 14:02:19 rancher1 kernel: [2089793.618910] crc32_pclmul ghash_clmulni_intel pcbc hid_generic aesni_intel aes_x86_64 crypto_simd glue_helper cryptd hid_hyperv pata_acpi hyperv_fb cfbfillrect hyperv_keyboard cfbimgblt hid cfbcopyarea hv_netvsc hv_utils Apr 7 14:02:19 rancher1 kernel: [2089793.692250] CPU: 0 PID: 47 Comm: kswapd0 Not tainted 4.15.0-1040-azure #44-Ubuntu Apr 7 14:02:19 rancher1 kernel: [2089793.725316] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 Apr 7 14:02:19 rancher1 kernel: [2089793.762206] RIP: 0010:split_swap_cluster+0x4f/0x70 Apr 7 14:02:19 rancher1 kernel: [2089793.781768] RSP: 0018:aaf900fbfbe0 EFLAGS: 00010246 Apr 7 14:02:19 rancher1 kernel: [2089793.800432] RAX: RBX: 007290de RCX: 007290de Apr 7 14:02:19 rancher1 kernel: [2089793.824572] RDX: aaf905001000 RSI: 00118df9 RDI: 007290de Apr 7 14:02:19 rancher1 kernel: [2089793.854139] RBP: aaf900fbfbe8 R08: 0001 R09: 9c647ffd4d00 Apr 7 14:02:19 rancher1 kernel: [2089793.882588] R10: 9c647ffd4000 R11: 0001 R12: f61ac463 Apr 7 14:02:19 rancher1 kernel: [2089793.909530] R13: f61ac4630080 R14: f61ac4638000 R15: f61ac4630040 Apr 7 14:02:19 rancher1 kernel: [2089793.935871] FS: () GS:9c647fc0() knlGS: Apr 7 14:02:19 rancher1 kernel: [2089793.966483] CS: 0010 DS: ES: CR0: 80050033 Apr 7 14:02:19 rancher1 kernel: [2089793.987904] CR2: 0007 CR3: 3240a005 CR4: 001606f0 Apr 7 14:02:19 rancher1 kernel: [2089794.017641] Call Trace: Apr 7 14:02:19 rancher1 kernel: [2089794.028683] split_huge_page_to_list+0x76e/0x7f0 Apr 7 14:02:19 rancher1 kernel: [2089794.051250] deferred_split_scan+0x177/0x2d0 Apr 7 14:02:19 rancher1 kernel: [2089794.065213] shrink_slab.part.50+0x20b/0x440 Apr 7 14:02:19 rancher1 kernel: [2089794.083856] shrink_node+0x2fc/0x310 Apr 7 14:02:19 rancher1 kernel: [2089794.097963] kswapd+0x32a/0x770 Apr 7 14:02:19 rancher1 kernel: [2089794.110523] kthread+0x105/0x140 Apr 7 14:02:19 rancher1 kernel: [2089794.122680] ? mem_cgroup_shrink_node+0x190/0x190 Apr 7 14:02:19 rancher1 kernel: [2089794.139139] ? kthread_destroy_worker+0x50/0x50 Apr 7 14:02:19 rancher1 kernel: [2089794.155543] ret_from_fork+0x35/0x40 Apr 7 14:02:19 rancher1 kernel: [2089794.167841] Code: c1 e3 07 48 c1 eb 10 48 8d 1c d8 48 89 df e8 49 9f 79 00 80 63 07 fb 48 85 db 74 17 48 89 df c6 07 00 0f 1f 40 00 31 c0 5b 5d c3 <80> 24 25 07 00 00 00 fb 31 c0 5b 5d c3 b8 f0 ff ff ff eb e9 0f Apr 7 14:02:19 rancher1 kernel: [2089794.237196] RIP: split_swap_cluster+0x4f/0x70 RSP: aaf900fbfbe0 Apr 7 14:02:19 rancher1 kernel: [2089794.259910] CR2: 0007 Apr 7 14:02:19 rancher1 kernel: [2089794.270891] ---[ end trace 5b797d89aee7fc1b ]--- The machine become unstable after this until reboot, like reading some namespaced process' command arguments hung, so it is possible that there was some kernel data structure corruption. The machine was under large memory pressure, when this happened. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1823859 Title: NULL pointer dereference in split_swap_cluster Status in linux-azure package in Ubuntu: New Bug description: We have encountered the following oops on one of our VMs: Apr 7 14:02:19 rancher1 kernel: [2089793.273674] BUG: unable to handle
[Kernel-packages] [Bug 1766565] Re: Unable to insert sysdig_probe module on KVM kernel
** Summary changed: - Unable to insert sysdig_probe module on B-KVM kernel + Unable to insert sysdig_probe module on KVM kernel ** Tags added: cosmic -- 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/1766565 Title: Unable to insert sysdig_probe module on KVM kernel Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in sysdig package in Ubuntu: New Bug description: The sysdig-dkms module cannot be installed on the B-KVM kernel once before (bug 1764693), but now the installation works since 4.15.0-1007 However, when you try to insert the module, it will complain about: $ sudo modprobe sysdig-probe modprobe: ERROR: could not insert 'sysdig_probe': Unknown symbol in module, or unknown parameter (see dmesg) Log in dmesg: [ 1989.967807] sysdig_probe: loading out-of-tree module taints kernel. [ 1989.967924] sysdig_probe: module verification failed: signature and/or required key missing - tainting kernel [ 1989.967986] sysdig_probe: Unknown symbol tracepoint_probe_unregister (err 0) [ 1989.968090] sysdig_probe: Unknown symbol for_each_kernel_tracepoint (err 0) [ 1989.968094] sysdig_probe: Unknown symbol tracepoint_probe_register (err 0) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1007-kvm 4.15.0-1007.7 ProcVersionSignature: User Name 4.15.0-1007.7-kvm 4.15.17 Uname: Linux 4.15.0-1007-kvm x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 11:31:08 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1766565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575334] Re: Docking thinkpad laptop causes a complete system freeze
> Incomplete → Expired Are you serious? It is happening everyday without the work around. What information are you missing, dear Janitor? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575334 Title: Docking thinkpad laptop causes a complete system freeze Status in linux package in Ubuntu: Expired Bug description: Since upgrading to Xenial, about 80% of the time when I dock my thinkpad laptop I get a complete system freeze. The symptoms of the freeze are: * The two external monitors connected to the dock seem to be in a half-configured state - they're powered on, and display some graphics from my desktop, but do not yet show the correct contents. * I can't get to a console with Ctrl+Alt+F1. * I can't kill X with Ctrl+Alt+Backspace * I can't get the mouse cursor to appear or move, either with the trackpad or the external mouse. * Undocking the laptop doesn't help. The only thing I *can* do at this point is to hold down the power button. I seem to recall similar issues in the past (perhaps in Vivid?), where the fix ended up being in the graphics driver. The laptop is a T540p. The docking station is an "ultra dock pro" - not a USB dock, but rather one of those ones where the laoptop clicks into a base. This bug makes the docking station rather useless, and makes me sad :( ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomi 3196 F pulseaudio /dev/snd/controlC0: thomi 3196 F pulseaudio /dev/snd/controlC1: thomi 3196 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 27 07:35:58 2016 HibernationDevice: RESUME=UUID=d27c9b15-955a-4bff-b4a7-e6116a8b30bb InstallationDate: Installed on 2015-10-12 (197 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20BECTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (5 days ago) dmi.bios.date: 09/01/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GMET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BECTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGMET72WW(2.20):bd09/01/2015:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20BECTO1WW dmi.product.version: ThinkPad T540p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822987] Re: nouveau timeout on Disco with nvidia GTX 1060
This issue might leads to the boot time increase in bug 1821027 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822987 Title: nouveau timeout on Disco with nvidia GTX 1060 Status in linux package in Ubuntu: Confirmed Bug description: The following error message could be found while booting this Dell G7 with Disco LiveUSB (20190403) Despite there is a such error message, the graphic looks OK. [ 15.714767] [ cut here ] [ 15.714768] nouveau :01:00.0: timeout [ 15.714818] WARNING: CPU: 7 PID: 2038 at drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ls_ucode_msgqueue.c:183 acr_ls_sec2_post_run+0x192/0x240 [nouveau] [ 15.714819] Modules linked in: arc4 cmac bnep intel_rapl snd_soc_skl x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp snd_soc_hdac_hda coretemp snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp kvm_intel snd_soc_acpi_intel_match snd_soc_acpi ath10k_pci snd_soc_core snd_hda_codec_realtek ath10k_core snd_hda_codec_generic snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec crct10dif_pclmul joydev crc32_pclmul ghash_clmulni_intel snd_hda_core ath uvcvideo btusb aesni_intel mac80211 snd_hwdep btrtl snd_pcm videobuf2_vmalloc btbcm videobuf2_memops snd_seq_midi videobuf2_v4l2 snd_seq_midi_event btintel aes_x86_64 videobuf2_common bluetooth crypto_simd snd_rawmidi cryptd videodev glue_helper intel_cstate snd_seq mei_me media cdc_acm dell_laptop processor_thermal_device snd_seq_device cfg80211 snd_timer input_leds ucsi_acpi idma64 ecdh_generic ledtrig_audio mei serio_raw hid_multitouch intel_rapl_perf typec_ucsi snd intel_soc_dts_iosf dell_wmi int3403_thermal [ 15.714833] virt_dma intel_hid wmi_bmof sparse_keymap intel_wmi_thunderbolt dell_smbios soundcore dcdbas int3400_thermal intel_pch_thermal int340x_thermal_zone acpi_thermal_rel dell_wmi_descriptor typec mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 overlay nls_utf8 isofs nls_iso8859_1 jfs xfs libcrc32c reiserfs dm_mirror dm_region_hash dm_log uas usb_storage hid_generic usbhid i915 nouveau kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass ttm i2c_algo_bit drm_kms_helper syscopyarea nvme sysfillrect sysimgblt fb_sys_fops mxm_wmi drm psmouse alx ahci nvme_core intel_lpss_pci mdio libahci i2c_hid intel_lpss hid pinctrl_cannonlake wmi video pinctrl_intel [ 15.714848] CPU: 7 PID: 2038 Comm: Xorg Not tainted 5.0.0-8-generic #9-Ubuntu [ 15.714849] Hardware name: Dell Inc. G7 7588/, BIOS 1.0.1 03/14/2018 [ 15.714867] RIP: 0010:acr_ls_sec2_post_run+0x192/0x240 [nouveau] [ 15.714868] Code: 45 a8 48 8b 40 10 48 8b 78 10 4c 8b 7f 50 4d 85 ff 74 1e e8 40 ac 37 f7 4c 89 fa 48 c7 c7 15 56 62 c0 48 89 c6 e8 80 98 d7 f6 <0f> 0b e9 25 ff ff ff 4c 8b 7f 10 eb dc 8b 43 20 48 c7 c6 08 c7 61 [ 15.714869] RSP: 0018:ac7305a079b8 EFLAGS: 00010286 [ 15.714869] RAX: RBX: 9b950cdde300 RCX: 0006 [ 15.714870] RDX: 0007 RSI: 0096 RDI: 9b951f3d6440 [ 15.714870] RBP: ac7305a07a10 R08: 0001 R09: 03e2 [ 15.714870] R10: 0004 R11: R12: [ 15.714871] R13: 9b951921a800 R14: 0040 R15: 9b951ab96940 [ 15.714872] FS: 7f14f3629a80() GS:9b951f3c() knlGS: [ 15.714872] CS: 0010 DS: ES: CR0: 80050033 [ 15.714873] CR2: 7f14f00ef000 CR3: 000856790003 CR4: 003606e0 [ 15.714873] DR0: DR1: DR2: [ 15.714874] DR3: DR6: fffe0ff0 DR7: 0400 [ 15.714874] Call Trace: [ 15.714893] acr_r352_bootstrap+0x1a9/0x2b0 [nouveau] [ 15.714910] acr_r352_reset+0x39/0x230 [nouveau] [ 15.714926] nvkm_secboot_reset+0x35/0x70 [nouveau] [ 15.714944] gf100_gr_init_ctxctl_ext+0x72/0x7e0 [nouveau] [ 15.714962] ? gf100_gr_zbc_init+0x15f/0x2a0 [nouveau] [ 15.714979] gf100_gr_init_ctxctl+0x32/0x2b0 [nouveau] [ 15.714997] gf100_gr_init+0x563/0x590 [nouveau] [ 15.715015] gf100_gr_init_+0x5b/0x60 [nouveau] [ 15.715032] nvkm_gr_init+0x1d/0x20 [nouveau] [ 15.715041] nvkm_engine_init+0xb9/0x1f0 [nouveau] [ 15.715052] nvkm_subdev_init+0xbc/0x210 [nouveau] [ 15.715061] nvkm_engine_ref.part.0+0x4a/0x70 [nouveau] [ 15.715071] nvkm_engine_ref+0x13/0x20 [nouveau] [ 15.715081] nvkm_ioctl_new+0x129/0x220 [nouveau] [ 15.715098] ? nvkm_fifo_chan_child_del+0xa0/0xa0 [nouveau] [ 15.715115] ? gf100_gr_dtor+0xd0/0xd0 [nouveau] [ 15.715125] nvkm_ioctl+0xe2/0x180 [nouveau] [ 15.715143] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 15.715152] nvif_client_ioctl+0x2c/0x30 [nouveau] [ 15.715169] usif_ioctl+0
[Kernel-packages] [Bug 1813001] Re: test_095_kernel_symbols_missing_proc_self_stack failed on P-LTS
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813001
Title:
test_095_kernel_symbols_missing_proc_self_stack failed on P-LTS
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Fix Released
Bug description:
[Impact]
The testcase test_095_kernel_symbols_missing_proc_self_stack from
ubuntu_qrt_kernel_security testsuite started to fail with Trusty
kernel (3.13) after the fix for CVE-2018-17972 ("proc: restrict kernel
stack dumps to root"), which prevents a regular user to read from
/proc/self/stack.
Kernel: 3.13.0-165.215~precise1
The test failed with:
AssertionError: cat: /proc/self/stack: Permission denied
FAIL: test_095_kernel_symbols_missing_proc_self_stack
(__main__.KernelSecurityTest)
kernel addresses in /proc/self/stack are zeroed out
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1364, in
test_095_kernel_symbols_missing_proc_self_stack
self._check_pK_files(self._095_kernel_symbols_missing_proc_self_stack,
expected=expected)
File "./test-kernel-security.py", line 1209, in _check_pK_files
test_function(expected_restricted)
File "./test-kernel-security.py", line 1320, in
_095_kernel_symbols_missing_proc_self_stack
expected, retry=True)
File "./test-kernel-security.py", line 1146, in _read_twice
self.assertEqual(rc, 0, regular)
AssertionError: cat: /proc/self/stack: Permission denied
The testcase checks the file permission before trying to read it, and
for kernel 3.13 the permissions became inconsistent with what the user
can actually do:
$ cat /proc/self/stack
cat: /proc/self/stack: Permission denied
$ ls -l /proc/self/stack
-r--r--r-- 1 ubuntu ubuntu 0 Jan 24 04:06 /proc/self/stack
[Test Case]
Run 'cat' and 'ls' on the file as stated above, or run the
ubuntu_qrt_kernel_security testsuite and check for the results of the
test_095_kernel_symbols_missing_proc_self_stack testcase.
[Fix]
Upstream commit 35a35046e4f9 ("procfs: make
/proc/*/{stack,syscall,personality} 0400") applied for v3.15-rc1 fixes the
issue.
[Regression Potential]
The upstream fix changes the permissions of the files
/proc/*/{stack,syscall,personality}, so userspace which relies on reading these
files as regular users might fail. However, this fixes a security issue and is
already applied on our later series.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813001/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817028] [NEW] Add arm64 CONFIG_ARCH_MESON=y and related configs
You have been subscribed to a public bug: Hi, Could CONFIG_ARCH_MESON=y and related configs be enabled like the armhf counterpart ? This will follow the debian kernel config. Here is the list of config that should be enabled to have optimal platform support: CONFIG_ARCH_MESON=y CONFIG_MESON_SM=y CONFIG_DWMAC_MESON=m CONFIG_MESON_GXL_PHY=m CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y CONFIG_HW_RANDOM_MESON=m CONFIG_I2C_MESON=m CONFIG_SPI_MESON_SPICC=m CONFIG_SPI_MESON_SPIFC=m CONFIG_PINCTRL_MESON=y CONFIG_PINCTRL_MESON_GXBB=y CONFIG_PINCTRL_MESON_GXL=y CONFIG_PINCTRL_MESON_AXG=y CONFIG_PINCTRL_MESON_AXG_PMX=y CONFIG_PINCTRL_MESON_G12A=y CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_IR_MESON=m CONFIG_VIDEO_MESON_AO_CEC=m CONFIG_DRM_MESON=m CONFIG_DRM_MESON_DW_HDMI=m CONFIG_MMC_MESON_GX=m CONFIG_MESON_CANVAS=m CONFIG_MESON_GX_SOCINFO=y CONFIG_MESON_GX_PM_DOMAINS=y CONFIG_MESON_SARADC=m CONFIG_PWM_MESON=m CONFIG_MESON_IRQ_GPIO=y CONFIG_RESET_MESON=m CONFIG_PHY_MESON_GXL_USB2=m CONFIG_PHY_MESON_GXL_USB3=m ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Add arm64 CONFIG_ARCH_MESON=y and related configs https://bugs.launchpad.net/bugs/1817028 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817848] Re: i915: Backport watermark fixes for gen9+
This bug was fixed in the package linux-oem - 4.15.0-1035.40
---
linux-oem (4.15.0-1035.40) bionic; urgency=medium
* linux-oem: 4.15.0-1035.40 -proposed tracker (LP: #1819692)
* [amdgpu] screen corruption when using touchpad (LP: #1818617)
- drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3)
- drm/amdgpu: Free VGA stolen memory as soon as possible.
* r8169 doesn't get woken up by ethernet cable plugging, no PME generated
(LP: #1817676)
- Revert "PCI/PME: Implement runtime PM callbacks"
- PCI: pciehp: Disable Data Link Layer State Changed event on suspend
* Fix I219 doesn't get woken up after plugging ethernet cable (LP: #1817058)
- e1000e: Disable runtime PM on CNP+
* i915: Backport watermark fixes for gen9+ (LP: #1817848)
- drm/i915: Backport gen9+ watermark fixes from 5.0
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 4.15.0-47.50 ]
* linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
* C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
* arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
* Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
* CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
* CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
* amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Don't use dc_link in link_encoder
- drm/amd/display: Move wait for hpd ready out from edp power control.
- drm/amd/display: eDP sequence BL off first then DP blank.
- drm/amd/display: Fix unused variable compilation error
- drm/amd/display: Fix warning about misaligned code
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
* tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
* CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
* raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
(LP: #1811194)
- selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock
adjustments are in progress
* [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
* CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
paths
- bpf: add various test cases to selftests
* CVE-2017-5753
- bpf: properly enforce index mask to prevent out-of-bounds speculation
- bpf: fix inner map masking to prevent oob under speculation
* BPF: kernel pointer leak to unprivileged userspace (LP: #1815259)
- bpf/verifier: disallow pointer subtraction
* squashfs hardening (LP: #1816756)
- squashfs: more metadata hardening
- squashfs metadata 2: electric boogaloo
- squashfs: more metadata hardening
- Squashfs: Compute expected length from inode size rather than block length
* efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
* ipset kernel error: 4.15.0-43-generic (LP: #1811394)
- netfilter: ipset: Fix wraparound in hash:*net* types
* Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
* CVE-2018-18021
- arm64: KVM: Tighten guest core register access from userspace
- KVM: arm/arm64: Introduce vcpu_el1_is_32bit
- arm64: KVM: Sanitize PSTATE.M when being set from userspace
* CVE-2018-14678
- x86/entry/64: Remove %ebx handling from error_entry/exit
* CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in
card.c
* CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
* Bionic
[Kernel-packages] [Bug 1819692] Re: linux-oem: 4.15.0-1035.40 -proposed tracker
This bug was fixed in the package linux-oem - 4.15.0-1035.40
---
linux-oem (4.15.0-1035.40) bionic; urgency=medium
* linux-oem: 4.15.0-1035.40 -proposed tracker (LP: #1819692)
* [amdgpu] screen corruption when using touchpad (LP: #1818617)
- drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3)
- drm/amdgpu: Free VGA stolen memory as soon as possible.
* r8169 doesn't get woken up by ethernet cable plugging, no PME generated
(LP: #1817676)
- Revert "PCI/PME: Implement runtime PM callbacks"
- PCI: pciehp: Disable Data Link Layer State Changed event on suspend
* Fix I219 doesn't get woken up after plugging ethernet cable (LP: #1817058)
- e1000e: Disable runtime PM on CNP+
* i915: Backport watermark fixes for gen9+ (LP: #1817848)
- drm/i915: Backport gen9+ watermark fixes from 5.0
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 4.15.0-47.50 ]
* linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
* C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
* arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
* Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
* CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
* CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
* amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Don't use dc_link in link_encoder
- drm/amd/display: Move wait for hpd ready out from edp power control.
- drm/amd/display: eDP sequence BL off first then DP blank.
- drm/amd/display: Fix unused variable compilation error
- drm/amd/display: Fix warning about misaligned code
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
* tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
* CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
* raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
(LP: #1811194)
- selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock
adjustments are in progress
* [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
* CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
paths
- bpf: add various test cases to selftests
* CVE-2017-5753
- bpf: properly enforce index mask to prevent out-of-bounds speculation
- bpf: fix inner map masking to prevent oob under speculation
* BPF: kernel pointer leak to unprivileged userspace (LP: #1815259)
- bpf/verifier: disallow pointer subtraction
* squashfs hardening (LP: #1816756)
- squashfs: more metadata hardening
- squashfs metadata 2: electric boogaloo
- squashfs: more metadata hardening
- Squashfs: Compute expected length from inode size rather than block length
* efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
* ipset kernel error: 4.15.0-43-generic (LP: #1811394)
- netfilter: ipset: Fix wraparound in hash:*net* types
* Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
* CVE-2018-18021
- arm64: KVM: Tighten guest core register access from userspace
- KVM: arm/arm64: Introduce vcpu_el1_is_32bit
- arm64: KVM: Sanitize PSTATE.M when being set from userspace
* CVE-2018-14678
- x86/entry/64: Remove %ebx handling from error_entry/exit
* CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in
card.c
* CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
* Bionic
[Kernel-packages] [Bug 1817058] Re: Fix I219 doesn't get woken up after plugging ethernet cable
This bug was fixed in the package linux-oem - 4.15.0-1035.40
---
linux-oem (4.15.0-1035.40) bionic; urgency=medium
* linux-oem: 4.15.0-1035.40 -proposed tracker (LP: #1819692)
* [amdgpu] screen corruption when using touchpad (LP: #1818617)
- drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3)
- drm/amdgpu: Free VGA stolen memory as soon as possible.
* r8169 doesn't get woken up by ethernet cable plugging, no PME generated
(LP: #1817676)
- Revert "PCI/PME: Implement runtime PM callbacks"
- PCI: pciehp: Disable Data Link Layer State Changed event on suspend
* Fix I219 doesn't get woken up after plugging ethernet cable (LP: #1817058)
- e1000e: Disable runtime PM on CNP+
* i915: Backport watermark fixes for gen9+ (LP: #1817848)
- drm/i915: Backport gen9+ watermark fixes from 5.0
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 4.15.0-47.50 ]
* linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
* C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
* arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
* Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
* CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
* CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
* amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Don't use dc_link in link_encoder
- drm/amd/display: Move wait for hpd ready out from edp power control.
- drm/amd/display: eDP sequence BL off first then DP blank.
- drm/amd/display: Fix unused variable compilation error
- drm/amd/display: Fix warning about misaligned code
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
* tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
* CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
* raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
(LP: #1811194)
- selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock
adjustments are in progress
* [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
* CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
paths
- bpf: add various test cases to selftests
* CVE-2017-5753
- bpf: properly enforce index mask to prevent out-of-bounds speculation
- bpf: fix inner map masking to prevent oob under speculation
* BPF: kernel pointer leak to unprivileged userspace (LP: #1815259)
- bpf/verifier: disallow pointer subtraction
* squashfs hardening (LP: #1816756)
- squashfs: more metadata hardening
- squashfs metadata 2: electric boogaloo
- squashfs: more metadata hardening
- Squashfs: Compute expected length from inode size rather than block length
* efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
* ipset kernel error: 4.15.0-43-generic (LP: #1811394)
- netfilter: ipset: Fix wraparound in hash:*net* types
* Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
* CVE-2018-18021
- arm64: KVM: Tighten guest core register access from userspace
- KVM: arm/arm64: Introduce vcpu_el1_is_32bit
- arm64: KVM: Sanitize PSTATE.M when being set from userspace
* CVE-2018-14678
- x86/entry/64: Remove %ebx handling from error_entry/exit
* CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in
card.c
* CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
* Bionic
[Kernel-packages] [Bug 1818617] Re: [amdgpu] screen corruption when using touchpad
This bug was fixed in the package linux-oem - 4.15.0-1035.40
---
linux-oem (4.15.0-1035.40) bionic; urgency=medium
* linux-oem: 4.15.0-1035.40 -proposed tracker (LP: #1819692)
* [amdgpu] screen corruption when using touchpad (LP: #1818617)
- drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3)
- drm/amdgpu: Free VGA stolen memory as soon as possible.
* r8169 doesn't get woken up by ethernet cable plugging, no PME generated
(LP: #1817676)
- Revert "PCI/PME: Implement runtime PM callbacks"
- PCI: pciehp: Disable Data Link Layer State Changed event on suspend
* Fix I219 doesn't get woken up after plugging ethernet cable (LP: #1817058)
- e1000e: Disable runtime PM on CNP+
* i915: Backport watermark fixes for gen9+ (LP: #1817848)
- drm/i915: Backport gen9+ watermark fixes from 5.0
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 4.15.0-47.50 ]
* linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
* C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
* arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
* Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
* CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
* CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
* amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Don't use dc_link in link_encoder
- drm/amd/display: Move wait for hpd ready out from edp power control.
- drm/amd/display: eDP sequence BL off first then DP blank.
- drm/amd/display: Fix unused variable compilation error
- drm/amd/display: Fix warning about misaligned code
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
* tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
* CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
* raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
(LP: #1811194)
- selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock
adjustments are in progress
* [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
* CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
paths
- bpf: add various test cases to selftests
* CVE-2017-5753
- bpf: properly enforce index mask to prevent out-of-bounds speculation
- bpf: fix inner map masking to prevent oob under speculation
* BPF: kernel pointer leak to unprivileged userspace (LP: #1815259)
- bpf/verifier: disallow pointer subtraction
* squashfs hardening (LP: #1816756)
- squashfs: more metadata hardening
- squashfs metadata 2: electric boogaloo
- squashfs: more metadata hardening
- Squashfs: Compute expected length from inode size rather than block length
* efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
* ipset kernel error: 4.15.0-43-generic (LP: #1811394)
- netfilter: ipset: Fix wraparound in hash:*net* types
* Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
* CVE-2018-18021
- arm64: KVM: Tighten guest core register access from userspace
- KVM: arm/arm64: Introduce vcpu_el1_is_32bit
- arm64: KVM: Sanitize PSTATE.M when being set from userspace
* CVE-2018-14678
- x86/entry/64: Remove %ebx handling from error_entry/exit
* CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in
card.c
* CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
* Bionic
[Kernel-packages] [Bug 1817058] Re: Fix I219 doesn't get woken up after plugging ethernet cable
This bug was fixed in the package linux-oem - 4.15.0-1035.40
---
linux-oem (4.15.0-1035.40) bionic; urgency=medium
* linux-oem: 4.15.0-1035.40 -proposed tracker (LP: #1819692)
* [amdgpu] screen corruption when using touchpad (LP: #1818617)
- drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3)
- drm/amdgpu: Free VGA stolen memory as soon as possible.
* r8169 doesn't get woken up by ethernet cable plugging, no PME generated
(LP: #1817676)
- Revert "PCI/PME: Implement runtime PM callbacks"
- PCI: pciehp: Disable Data Link Layer State Changed event on suspend
* Fix I219 doesn't get woken up after plugging ethernet cable (LP: #1817058)
- e1000e: Disable runtime PM on CNP+
* i915: Backport watermark fixes for gen9+ (LP: #1817848)
- drm/i915: Backport gen9+ watermark fixes from 5.0
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 4.15.0-47.50 ]
* linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
* C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
* arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
* Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
* CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
* CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
* amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Don't use dc_link in link_encoder
- drm/amd/display: Move wait for hpd ready out from edp power control.
- drm/amd/display: eDP sequence BL off first then DP blank.
- drm/amd/display: Fix unused variable compilation error
- drm/amd/display: Fix warning about misaligned code
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
* tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
* CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
* raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
(LP: #1811194)
- selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock
adjustments are in progress
* [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
* CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
paths
- bpf: add various test cases to selftests
* CVE-2017-5753
- bpf: properly enforce index mask to prevent out-of-bounds speculation
- bpf: fix inner map masking to prevent oob under speculation
* BPF: kernel pointer leak to unprivileged userspace (LP: #1815259)
- bpf/verifier: disallow pointer subtraction
* squashfs hardening (LP: #1816756)
- squashfs: more metadata hardening
- squashfs metadata 2: electric boogaloo
- squashfs: more metadata hardening
- Squashfs: Compute expected length from inode size rather than block length
* efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
* ipset kernel error: 4.15.0-43-generic (LP: #1811394)
- netfilter: ipset: Fix wraparound in hash:*net* types
* Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
* CVE-2018-18021
- arm64: KVM: Tighten guest core register access from userspace
- KVM: arm/arm64: Introduce vcpu_el1_is_32bit
- arm64: KVM: Sanitize PSTATE.M when being set from userspace
* CVE-2018-14678
- x86/entry/64: Remove %ebx handling from error_entry/exit
* CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in
card.c
* CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
* Bionic
[Kernel-packages] [Bug 1423672] Re: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y
Unfortunately the symptom still persists on bionic (Ubuntu 18.04.1 LTS) with kernel 4.15.0-43-generic. This issue may be a symptom that's caused by lice and fleas. I updated https://bugzilla.kernel.org/show_bug.cgi?id=104571 by adding a comment with additional information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1423672 Title: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux package in Debian: Fix Released Bug description: SRU Justification: Impact: Users of VMs running 3.13/3.16 and ext4 can experience data corruption in the guest. Fix: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?h=7dec5603b6b8dc4c3e1c65d318bd2a5a8c62a424 Testcase: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818502#22 -- I noticed that one of my VM had this "dmesg -T" output: [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204 [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor inconsistent: 16446 vs 16445 free clusters [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8. [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only [Thu Feb 19 06:25:09 2015] [ cut here ] [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0() [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 3.13.0-45-generic #74-Ubuntu [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [Thu Feb 19 06:25:09 2015] 0009 880003a11aa0 81720eb6 [Thu Feb 19 06:25:09 2015] 880003a11ad8 810677cd 88c41340 [Thu Feb 19 06:25:09 2015] 88000a58e000 81835280 1302 880003a11ae8 [Thu Feb 19 06:25:09 2015] Call Trace: [Thu Feb 19 06:25:09 2015] [] dump_stack+0x45/0x56 [Thu Feb 19 06:25:09 2015] [] warn_slowpath_common+0x7d/0xa0 [Thu Feb 19 06:25:09 2015] [] warn_slowpath_null+0x1a/0x20 [Thu Feb 19 06:25:09 2015] [] __ext4_handle_dirty_metadata+0x1a2/0x1c0 [Thu Feb 19 06:25:09 2015] [] ? ext4_dirty_inode+0x2a/0x60 [Thu Feb 19 06:25:09 2015] [] ext4_free_blocks+0x646/0xbf0 [Thu Feb 19 06:25:09 2015] [] ? wake_up_bit+0x25/0x30 [Thu Feb 19 06:25:09 2015] [] ext4_ext_rm_leaf+0x505/0x8f0 [Thu Feb 19 06:25:09 2015] [] ? __ext4_ext_check+0x197/0x370 [Thu Feb 19 06:25:09 2015] [] ? ext4_ext_remove_space+0xc0/0x7e0 [Thu Feb 19 06:25:09 2015] [] ext4_ext_remove_space+0x31c/0x7e0 [Thu Feb 19 06:25:09 2015] [] ext4_ext_truncate+0xb0/0xe0 [Thu Feb 19 06:25:09 2015] [] ext4_truncate+0x379/0x3c0 [Thu Feb 19 06:25:09 2015] [] ext4_evict_inode+0x408/0x4d0 [Thu Feb 19 06:25:09 2015] [] evict+0xb0/0x1b0 [Thu Feb 19 06:25:09 2015] [] iput+0xf5/0x180 [Thu Feb 19 06:25:09 2015] [] __dentry_kill+0x1a8/0x200 [Thu Feb 19 06:25:09 2015] [] dput+0xa5/0x180 [Thu Feb 19 06:25:09 2015] [] __fput+0x176/0x260 [Thu Feb 19 06:25:09 2015] [] fput+0xe/0x10 [Thu Feb 19 06:25:09 2015] [] task_work_run+0xa7/0xe0 [Thu Feb 19 06:25:09 2015] [] do_notify_resume+0x97/0xb0 [Thu Feb 19 06:25:09 2015] [] int_signal+0x12/0x17 [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]--- [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer dereference at 0028 [Thu Feb 19 06:25:09 2015] IP: [] __ext4_error_inode+0x31/0x160 [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0 [Thu Feb 19 06:25:09 2015] Oops: [#1] SMP [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Tainted: G W 3.13.0-45-generic #74-Ubuntu [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [Thu Feb 19 06:25:09 2015] task: 880009ac4800 ti: 880003a1 task.ti: 880003a1 [Thu Feb 19 06:25:09 2015] RIP: 0010:[] [] __ext4_
[Kernel-packages] [Bug 1823428] Re: linux-oem ftbfs in disco
1035 seems to have built fine on disco & cosmic ** Changed in: linux-oem (Ubuntu) Status: New => 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/1823428 Title: linux-oem ftbfs in disco Status in linux-oem package in Ubuntu: Fix Released Bug description: https://launchpadlibrarian.net/417924465/buildlog_ubuntu-disco-amd64 .linux-oem_4.15.0-1034.39_BUILDING.txt.gz HOSTLD scripts/mod/modpost HOSTCC scripts/selinux/genheaders/genheaders In file included from /<>/scripts/selinux/genheaders/genheaders.c:19: /<>/security/selinux/include/classmap.h:247:2: error: #error New address family defined, please update secclass_map. #error New address family defined, please update secclass_map. ^ make[6]: *** [scripts/Makefile.host:90: scripts/selinux/genheaders/genheaders] Error 1 make[5]: *** [/<>/scripts/Makefile.build:606: scripts/selinux/genheaders] Error 2 make[4]: *** [/<>/scripts/Makefile.build:606: scripts/selinux] Error 2 make[3]: *** [/<>/Makefile:589: scripts] Error 2 make[2]: *** [/<>/Makefile:278: __build_one_by_one] Error 2 make[2]: Leaving directory '/<>/debian/build/build-oem' make[1]: *** [Makefile:146: sub-make] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules.d/2-binary-arch.mk:31: /<>/debian/stamps/stamp-prepare-tree-oem] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1823428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817028] Re: Add arm64 CONFIG_ARCH_MESON=y and related configs
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817028 Title: Add arm64 CONFIG_ARCH_MESON=y and related configs Status in linux package in Ubuntu: New Bug description: Hi, Could CONFIG_ARCH_MESON=y and related configs be enabled like the armhf counterpart ? This will follow the debian kernel config. Here is the list of config that should be enabled to have optimal platform support: CONFIG_ARCH_MESON=y CONFIG_MESON_SM=y CONFIG_DWMAC_MESON=m CONFIG_MESON_GXL_PHY=m CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y CONFIG_HW_RANDOM_MESON=m CONFIG_I2C_MESON=m CONFIG_SPI_MESON_SPICC=m CONFIG_SPI_MESON_SPIFC=m CONFIG_PINCTRL_MESON=y CONFIG_PINCTRL_MESON_GXBB=y CONFIG_PINCTRL_MESON_GXL=y CONFIG_PINCTRL_MESON_AXG=y CONFIG_PINCTRL_MESON_AXG_PMX=y CONFIG_PINCTRL_MESON_G12A=y CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_IR_MESON=m CONFIG_VIDEO_MESON_AO_CEC=m CONFIG_DRM_MESON=m CONFIG_DRM_MESON_DW_HDMI=m CONFIG_MMC_MESON_GX=m CONFIG_MESON_CANVAS=m CONFIG_MESON_GX_SOCINFO=y CONFIG_MESON_GX_PM_DOMAINS=y CONFIG_MESON_SARADC=m CONFIG_PWM_MESON=m CONFIG_MESON_IRQ_GPIO=y CONFIG_RESET_MESON=m CONFIG_PHY_MESON_GXL_USB2=m CONFIG_PHY_MESON_GXL_USB3=m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793004] Re: package linux-modules-4.15.0-1018-oem (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-1018-oem/kernel/drivers/media/dvb-frontends/drx
sounds like your disk was full ** Changed in: linux-oem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1793004 Title: package linux-modules-4.15.0-1018-oem (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-1018-oem/kernel/drivers/media/dvb- frontends/drxd.ko.dpkg-new': Operation not permitted Status in linux-oem package in Ubuntu: Invalid Bug description: N/A ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-modules-4.15.0-1018-oem (not installed) ProcVersionSignature: Ubuntu 4.15.0-1017.20-oem 4.15.18 Uname: Linux 4.15.0-1017-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Mon Sep 17 06:40:58 2018 DuplicateSignature: package:linux-modules-4.15.0-1018-oem:(not installed) Unpacking linux-modules-4.15.0-1018-oem (4.15.0-1018.21) ... dpkg: error processing archive /tmp/apt-dpkg-install-U05ilT/2-linux-modules-4.15.0-1018-oem_4.15.0-1018.21_amd64.deb (--unpack): unable to open '/lib/modules/4.15.0-1018-oem/kernel/drivers/media/dvb-frontends/drxd.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.15.0-1018-oem/kernel/drivers/media/dvb-frontends/drxd.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-08-30 (18 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: linux-oem Title: package linux-modules-4.15.0-1018-oem (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-1018-oem/kernel/drivers/media/dvb-frontends/drxd.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1793004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814874] Re: NULL pointer dereference when using z3fold and zswap
Thanks for the feedback, I will see if I can reproduce this and SRU this patch. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) 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/1814874 Title: NULL pointer dereference when using z3fold and zswap Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Bug description: Under memory pressure, my VM locks up. This has been reported upstream though I don't know how far any solution has progressed. https://bugzilla.kernel.org/show_bug.cgi?id=201603 Feb 6 07:15:42 vps632258 kernel: [151336.450064] z3fold: unknown buddy id 0 Feb 6 07:15:42 vps632258 kernel: [151336.454450] BUG: unable to handle kernel NULL pointer dereference at 0008 The little bit of log I managed to salvage is attached. This has happened to two identical VMs. Unusually it has not occurred on a third VM which is configured the same but has less RAM (fingers crossed it won't). Irrelevant information: I thought the lock-ups were due to me using a BTRFS filesystem, however I swapped over to NILFS2 and this still occurs. The only difference seems to be that I am now able to grab some of the kernel output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-14-generic 4.18.0-14.15~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Feb 6 10:55:05 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1814874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick
This looks like the change which blacklists the motion device. https://github.com/torvalds/linux/commit/20ac95d52a28f55472a54cc751eeec49fd445cb1#diff-34c8d0c14a101d038ef2d2e7a1957559 Not sure why we would want to by default disable the gyro/accelerometer device which IMHO makes the DS3 far more useful and valuable than a cheap USB or BT gamepad. It probably just took six months to make it into stable Ubuntu. quoting the Oct 9, 2017 submit: Input: joydev - blacklist ds3/ds4/udraw motion sensors Introduce a device table used for blacklisting devices. We currently blacklist the motion sensor subdevice of THQ Udraw and Sony ds3/ds4. Signed-off-by: Roderick Colenbrander [dtor: siwtched to blacklist built on input_device_id and using input_match_device_id()] Signed-off-by: Dmitry Torokhov -- 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/1800839 Title: Dualshock3 hid_sony accelerometer not registering as joystick Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25 [12649.015925] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24 [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux perhaps this is only a config issue as when the new split gyro & analog sticks/buttons/triggers both appeared as joysticks while you can now see only Sony PLAYSTATION(R)3 Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 Controller Motion Sensors (input25) does not. Any questions I am happy to respond, I have every reason to believe this is actually not a bluez issue but google gives me no returns other than general compatibility issues over the new hid_sony driver splitting the gyro from the pad. I use this to stay current on instrument flying while working out of town using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator that fis in my laptop bag. thanks dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Wed Oct 31 15:06:00 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. GL503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash modprobe.blacklist=nouveau vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL503VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 60:F6:77:DD:DB:90 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:624605 acl:10743 sco:0 events:125 errors:0 TX bytes:5814 acl:12 sco:0 commands:106 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1800839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823684] Re: Right click does not work as expected on Dell G7 7588
** Changed in: linux-signed (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1823684 Title: Right click does not work as expected on Dell G7 7588 Status in linux-signed package in Ubuntu: Confirmed Bug description: The right button on the touchpad of this system does not work as expected, the click event will get treated as a regular left click. $ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ DELL0825:00 06CB:7E92 Touchpad id=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=11 [slave keyboard (3)] ↳ Intel HID 5 button arrayid=13 [slave keyboard (3)] ↳ Intel HID eventsid=14 [slave keyboard (3)] ↳ Dell WMI hotkeysid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] xev for left click and right click: ButtonPress event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 304106, (167,148), root:(357,319), state 0x10, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 304146, (167,148), root:(357,319), state 0x110, button 1, same_screen YES ButtonPress event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 309562, (167,148), root:(357,319), state 0x10, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 309563, (167,148), root:(357,319), state 0x110, button 1, same_screen YES ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 17:50:24 2019 InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1823684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick
Kai-Heng Feng, I replied to you several months ago via email but for completeness I want to leave a reply here too. Yes, when the new sony_hid first came out there were two devices an analog sticks/triggers and buttons device and a second accelerometer/gyro device. Splitting into two joysticks simply required remapping in the applications I was using. Later (around last april-june)the gyro/accelerometer device is detected but is not registered as a joystick device. this answer which I asked when I first reported this bug is at Ask Ubuntu, maybe it might help, I didn't get it to work and after loosing use of a second computer I prefer to leave hand repairs out of my everyday machine. https://askubuntu.com/questions/1088925/ubuntu-18-04-no-longer-adds-second-joystick-device-for-sony-dualshock3s-gyro-ac -- 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/1800839 Title: Dualshock3 hid_sony accelerometer not registering as joystick Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25 [12649.015925] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24 [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux perhaps this is only a config issue as when the new split gyro & analog sticks/buttons/triggers both appeared as joysticks while you can now see only Sony PLAYSTATION(R)3 Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 Controller Motion Sensors (input25) does not. Any questions I am happy to respond, I have every reason to believe this is actually not a bluez issue but google gives me no returns other than general compatibility issues over the new hid_sony driver splitting the gyro from the pad. I use this to stay current on instrument flying while working out of town using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator that fis in my laptop bag. thanks dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Wed Oct 31 15:06:00 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. GL503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash modprobe.blacklist=nouveau vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL503VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 60:F6:77:DD:DB:90 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:624605 acl:10743 sco:0 events:125 errors:0 TX bytes:5814 acl:12 sco:0 commands:106 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1800839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1534162] Re: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs
It seems that we're hitting this issue again with the subiquity installer. The installer fails at the "installing kernel" stage, when zipl is called. These are the last lines of the installer log (retrieving the full log is not trivial because of LP: #1823797): Setting up linux-image-5.0.0-8-generic (5.0.0-8.9) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.0.0-8-generic I: /initrd.img.old is now a symlink to boot/initrd.img-5.0.0-8-generic I: /vmlinuz is now a symlink to boot/vmlinuz-5.0.0-8-generic I: /initrd.img is now a symlink to boot/initrd.img-5.0.0-8-generic Not invoking zipl: initrd doesn't exist yet /etc/kernel/postinst.d/zz-zipl: Not invoking zipl: initrd doesn't exist yet Setting up linux-generic (5.0.0.8.9) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.0.0-8-generic Not invoking zipl: initrd doesn't exist yet /etc/kernel/postinst.d/zz-zipl: Not invoking zipl: initrd doesn't exist yet Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'zipl'] Error: Image file '/boot/vmlinuz' in section 'ubuntu': No such file or directory The qcow2 disk image can be mounted like this: $ sudo modprobe nbd max_part=8 $ sudo qemu-nbd --connect=/dev/nbd0 /path/to/CE-install-test.qcow2 $ sudo mount /dev/nbd0p1 /mnt/guest and it contains the expected target filesystem, but the vmlinuz and initrd.img symlink are in / instead of being in /boot, where zipl expects them: lrwxrwxrwx 1 root root31 Apr 9 08:11 initrd.img -> boot/initrd.img-5.0.0-8-generic lrwxrwxrwx 1 root root28 Apr 9 08:11 vmlinuz -> boot/vmlinuz-5.0.0-8-generic Moving the symlinks in /boot and chrooting in the target partition makes zipl work: $ for i in sys dev proc; do sudo mount -o bind /$i /mnt/guest/$i; done $ sudo chroot /mnt/guest/ groups: cannot find name for group ID 129 root@s1lp04:/# rm initrd.img* vmlinuz* root@s1lp04:/# cd /boot/ root@s1lp04:/boot# ln -s vmlinuz-5.0.0-8-generic vmlinuz root@s1lp04:/boot# ln -s initrd.img-5.0.0-8-generic initrd.img root@s1lp04:/boot# cd .. root@s1lp04:/# zipl -V Using config file '/etc/zipl.conf' Warning: Could not remove temporary file : No such file or directoryfree(): double free detected in tcache 2 Aborted (It still errors, but we go past the "No such file or directory" error, and this error is probably related to the chroot.) It seems that the location of the vmlinuz and initrd symlinks can be configured with the /etc/kernel-img.conf file. On the host system we have: $ cat /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = yes do_initrd = yes link_in_boot = yes and the symlinks are indeed created in /boot. In the (subiquity installed, non functional) guest system the /etc/kernel-img.conf is missing. The package responsible of installing kernel-img.conf is kernel-common, but it is *not* installed in the host system, so the file is probably (supposed to be) copied from the installer system. My supposition is that this step is missing in the subiquity installer. I am reopening this and setting it as Confirmed as it was verified together by me and cpaelzer. Dimitri: do you remember how this was fixed with the debian-installer? ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed ** Changed in: zipl-installer (Ubuntu) Status: Invalid => Confirmed ** Changed in: livecd-rootfs (Ubuntu) Status: Invalid => 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/1534162 Title: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs Status in subiquity: New Status in linux package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: New Status in zipl-installer package in Ubuntu: Confirmed Bug description: Symlinks are not managed correctly. Last installed and configured kernel, prior to purging -5- was -6-, yet symlinks were not updated to -6- when that happened. root@devac03:~# apt-get remove --purge linux-headers-4.3.0-5 linux-headers-4.3.0-5-generic linux-image-4.3.0-5-generic linux-image-extra-4.3.0-5-generic Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.3.0-5* linux-headers-4.3.0-5-generic* linux-image-4.3.0-5-generic* lin
[Kernel-packages] [Bug 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1822811 Title: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822812 phase: Ready for Promote to Proposed phase-changed: Tuesday, 09. April 2019 01:42 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817028] 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 1817028 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/1817028 Title: Add arm64 CONFIG_ARCH_MESON=y and related configs Status in linux package in Ubuntu: Incomplete Bug description: Hi, Could CONFIG_ARCH_MESON=y and related configs be enabled like the armhf counterpart ? This will follow the debian kernel config. Here is the list of config that should be enabled to have optimal platform support: CONFIG_ARCH_MESON=y CONFIG_MESON_SM=y CONFIG_DWMAC_MESON=m CONFIG_MESON_GXL_PHY=m CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y CONFIG_HW_RANDOM_MESON=m CONFIG_I2C_MESON=m CONFIG_SPI_MESON_SPICC=m CONFIG_SPI_MESON_SPIFC=m CONFIG_PINCTRL_MESON=y CONFIG_PINCTRL_MESON_GXBB=y CONFIG_PINCTRL_MESON_GXL=y CONFIG_PINCTRL_MESON_AXG=y CONFIG_PINCTRL_MESON_AXG_PMX=y CONFIG_PINCTRL_MESON_G12A=y CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_IR_MESON=m CONFIG_VIDEO_MESON_AO_CEC=m CONFIG_DRM_MESON=m CONFIG_DRM_MESON_DW_HDMI=m CONFIG_MMC_MESON_GX=m CONFIG_MESON_CANVAS=m CONFIG_MESON_GX_SOCINFO=y CONFIG_MESON_GX_PM_DOMAINS=y CONFIG_MESON_SARADC=m CONFIG_PWM_MESON=m CONFIG_MESON_IRQ_GPIO=y CONFIG_RESET_MESON=m CONFIG_PHY_MESON_GXL_USB2=m CONFIG_PHY_MESON_GXL_USB3=m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1534162] Re: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs
** Also affects: subiquity Importance: Undecided Status: New ** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1534162 Title: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs Status in subiquity: New Status in linux package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: New Status in zipl-installer package in Ubuntu: Confirmed Bug description: Symlinks are not managed correctly. Last installed and configured kernel, prior to purging -5- was -6-, yet symlinks were not updated to -6- when that happened. root@devac03:~# apt-get remove --purge linux-headers-4.3.0-5 linux-headers-4.3.0-5-generic linux-image-4.3.0-5-generic linux-image-extra-4.3.0-5-generic Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.3.0-5* linux-headers-4.3.0-5-generic* linux-image-4.3.0-5-generic* linux-image-extra-4.3.0-5-generic* 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded. After this operation, 131 MB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 92073 files and directories currently installed.) Removing linux-headers-4.3.0-5-generic (4.3.0-5.16) ... Removing linux-headers-4.3.0-5 (4.3.0-5.16) ... Removing linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic update-initramfs: Generating /boot/initrd.img-4.3.0-5-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot/' Building menu 'zipl-automatic-menu' Adding #1: IPL section 'ubuntu' (default) Preparing boot device: dasda (0200). Done. run-parts: executing /etc/kernel/postinst.d/pm-utils 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic run-parts: executing /etc/kernel/postinst.d/zz-zipl 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot/' Building menu 'zipl-automatic-menu' Adding #1: IPL section 'ubuntu' (default) Preparing boot device: dasda (0200). Done. Purging configuration files for linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ... Removing linux-image-4.3.0-5-generic (4.3.0-5.16) ... WARN: Proceeding with removing running kernel image. Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic update-initramfs: Deleting /boot/initrd.img-4.3.0-5-generic run-parts: executing /etc/kernel/postrm.d/zz-zipl 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic Using config file '/etc/zipl.conf' Error: Image file '/boot/vmlinuz' in section 'ubuntu': No such file or directory run-parts: /etc/kernel/postrm.d/zz-zipl exited with return code 1 Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/linux-image-4.3.0-5-generic.postrm line 328. dpkg: error processing package linux-image-4.3.0-5-generic (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-4.3.0-5-generic E: Sub-process /usr/bin/dpkg returned an error code (1) root@devac03:~# ls -latr /boot total 24208 drwx-- 2 root root16384 Dec 9 16:38 lost+found lrwxrwxrwx 1 root root 26 Jan 6 16:23 initrd.img -> initrd.img-4.3.0-5-generic lrwxrwxrwx 1 root root 23 Jan 6 16:24 vmlinuz -> vmlinuz-4.3.0-5-generic -rw--- 1 root root 13026048 Jan 11 21:36 vmlinuz-4.3.0-6-generic -rw--- 1 root root 2446124 Jan 11 21:36 System.map-4.3.0-6-generic -rw-r--r-- 1 root root63422 Jan 11 21:36 config-4.3.0-6-generic -rw-r--r-- 1 root root 517933 Jan 11 21:36 abi-4.3.0-6-generic drwxr-xr-x 22 root root 4096 Jan 14 13:03 .. -rw-r--r-- 1 root root 8574889 Jan 14 13:03 initrd.img-4.3.0-6-generic -rw--- 1 root root69632 Jan 14 13:41 bootmap drwxr-xr-x 3 root root 4096 Jan 14 13:41 . root@devac03:~# dpkg -l | grep 4.3.0 ii iproute 1:4.3.0-1ubuntu1 all transitional dummy package for iproute2 ii iproute2 4.3.0-1ubuntu1 s390xnetworking and traffic control tools ii linux-generic4.3.0.6.7 s390xComplete Generic Linux kernel and headers ii linux-headers-4.3.0-64.3.0-6.17 all Header files related to Linux kernel version 4.3.0 ii linux-headers-4.3.0-6-generic4.3.0-6.17 s390xLinux k
[Kernel-packages] [Bug 1823653] Re: Wireless key does not work on Dell G7 7588 with Bionic
The output from "libinput debug-events" looks okay: event4 KEYBOARD_KEY +6.48s KEY_UNKNOWN (240) pressed -event8 KEYBOARD_KEY +6.49s KEY_RFKILL (247) pressed event8 KEYBOARD_KEY +6.49s KEY_RFKILL (247) released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1823653 Title: Wireless key does not work on Dell G7 7588 with Bionic Status in linux-signed package in Ubuntu: New Bug description: The wireless key (fn + PrtScn) does not work on this system. "sudo showkey -s" does not return anything But it will generate some noise in dmesg: [ 1863.388925] keyboard: can't emulate rawmode for keycode 240 [ 1863.408641] keyboard: can't emulate rawmode for keycode 247 [ 1863.408667] keyboard: can't emulate rawmode for keycode 247 "sudo showkey -k" will show: keycode 240 press keycode 247 press keycode 247 release xev returns: KeyPress event, serial 37, synthetic NO, window 0x281, root 0x263, subw 0x0, time 1542623, (357,334), root:(547,505), state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x281, root 0x263, subw 0x0, time 1542623, (357,334), root:(547,505), state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 15:58:37 2019 InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1823653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822812 - phase: Ready for Promote to Proposed - phase-changed: Tuesday, 09. April 2019 01:42 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 09. April 2019 10:11 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- 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/1822811 Title: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822812 phase: Promote to Proposed phase-changed: Tuesday, 09. April 2019 10:11 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1822811 Title: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822812 phase: Promote to Proposed phase-changed: Tuesday, 09. April 2019 10:11 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X
I have also had this problem - MSI Tomahawk Arctic B350, ryzen 1700, vega 56 gpu ubuntu 19.04 - ignores bios setting, attempts to boot, kernel panic with lots of AMD-Vi: Completion-Wait loop timed out Reboot to find grub in rescue mode, and all ext4 partitions wiped. Can't boot live disc either, unless swap to an nvidia graphics card Only work around is to add the kernel parameters, but booting ubuntu shouldn't wipe my OS? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747463 Title: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu. There are lots of AMD-Vi logged events and I get irq crashes or acpi hangups with a 'normal' boot. I got it to boot by disabling IOMMU in the BIOS and adding "iommu=soft" to the kernel booting options in grub. linux can then detect everything properly (all cores) and I've had zero crashes. The only issue is that it's using software IOMMU which could have a performance penalty because it has to copy all the data of some PCI devices to sub 4G regions. Alternatively it boots with the kernel option "acpi=off" but only detects a single core/thread. I attached a kernel log. I believe(d) this might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085 --- ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fixme 1487 F pulseaudio /dev/snd/controlC0: fixme 1487 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece InstallationDate: Installed on 2018-01-31 (4 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group B350GT5 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 RfKill: Tags: bionic Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.asset.tag: None dmi.board.name: B350GT5 dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: None dmi.product.name: B350GT5 dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1747463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817058] Re: Fix I219 doesn't get woken up after plugging ethernet cable
This bug was fixed in the package linux-oem - 4.15.0-1035.40
---
linux-oem (4.15.0-1035.40) bionic; urgency=medium
* linux-oem: 4.15.0-1035.40 -proposed tracker (LP: #1819692)
* [amdgpu] screen corruption when using touchpad (LP: #1818617)
- drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3)
- drm/amdgpu: Free VGA stolen memory as soon as possible.
* r8169 doesn't get woken up by ethernet cable plugging, no PME generated
(LP: #1817676)
- Revert "PCI/PME: Implement runtime PM callbacks"
- PCI: pciehp: Disable Data Link Layer State Changed event on suspend
* Fix I219 doesn't get woken up after plugging ethernet cable (LP: #1817058)
- e1000e: Disable runtime PM on CNP+
* i915: Backport watermark fixes for gen9+ (LP: #1817848)
- drm/i915: Backport gen9+ watermark fixes from 5.0
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 4.15.0-47.50 ]
* linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
* C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
* arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
* Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
* CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
* CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
* amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Don't use dc_link in link_encoder
- drm/amd/display: Move wait for hpd ready out from edp power control.
- drm/amd/display: eDP sequence BL off first then DP blank.
- drm/amd/display: Fix unused variable compilation error
- drm/amd/display: Fix warning about misaligned code
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
* tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
* CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
* raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
(LP: #1811194)
- selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock
adjustments are in progress
* [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
* CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
paths
- bpf: add various test cases to selftests
* CVE-2017-5753
- bpf: properly enforce index mask to prevent out-of-bounds speculation
- bpf: fix inner map masking to prevent oob under speculation
* BPF: kernel pointer leak to unprivileged userspace (LP: #1815259)
- bpf/verifier: disallow pointer subtraction
* squashfs hardening (LP: #1816756)
- squashfs: more metadata hardening
- squashfs metadata 2: electric boogaloo
- squashfs: more metadata hardening
- Squashfs: Compute expected length from inode size rather than block length
* efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
* ipset kernel error: 4.15.0-43-generic (LP: #1811394)
- netfilter: ipset: Fix wraparound in hash:*net* types
* Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
* CVE-2018-18021
- arm64: KVM: Tighten guest core register access from userspace
- KVM: arm/arm64: Introduce vcpu_el1_is_32bit
- arm64: KVM: Sanitize PSTATE.M when being set from userspace
* CVE-2018-14678
- x86/entry/64: Remove %ebx handling from error_entry/exit
* CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in
card.c
* CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
* Bionic
[Kernel-packages] [Bug 1817676] Re: r8169 doesn't get woken up by ethernet cable plugging, no PME generated
This bug was fixed in the package linux-oem - 4.15.0-1035.40
---
linux-oem (4.15.0-1035.40) bionic; urgency=medium
* linux-oem: 4.15.0-1035.40 -proposed tracker (LP: #1819692)
* [amdgpu] screen corruption when using touchpad (LP: #1818617)
- drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3)
- drm/amdgpu: Free VGA stolen memory as soon as possible.
* r8169 doesn't get woken up by ethernet cable plugging, no PME generated
(LP: #1817676)
- Revert "PCI/PME: Implement runtime PM callbacks"
- PCI: pciehp: Disable Data Link Layer State Changed event on suspend
* Fix I219 doesn't get woken up after plugging ethernet cable (LP: #1817058)
- e1000e: Disable runtime PM on CNP+
* i915: Backport watermark fixes for gen9+ (LP: #1817848)
- drm/i915: Backport gen9+ watermark fixes from 5.0
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 4.15.0-47.50 ]
* linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
* C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
* arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
* Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
* CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
* CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
* amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Don't use dc_link in link_encoder
- drm/amd/display: Move wait for hpd ready out from edp power control.
- drm/amd/display: eDP sequence BL off first then DP blank.
- drm/amd/display: Fix unused variable compilation error
- drm/amd/display: Fix warning about misaligned code
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
* tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
* CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
* raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
(LP: #1811194)
- selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock
adjustments are in progress
* [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
* CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
paths
- bpf: add various test cases to selftests
* CVE-2017-5753
- bpf: properly enforce index mask to prevent out-of-bounds speculation
- bpf: fix inner map masking to prevent oob under speculation
* BPF: kernel pointer leak to unprivileged userspace (LP: #1815259)
- bpf/verifier: disallow pointer subtraction
* squashfs hardening (LP: #1816756)
- squashfs: more metadata hardening
- squashfs metadata 2: electric boogaloo
- squashfs: more metadata hardening
- Squashfs: Compute expected length from inode size rather than block length
* efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
* ipset kernel error: 4.15.0-43-generic (LP: #1811394)
- netfilter: ipset: Fix wraparound in hash:*net* types
* Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
* CVE-2018-18021
- arm64: KVM: Tighten guest core register access from userspace
- KVM: arm/arm64: Introduce vcpu_el1_is_32bit
- arm64: KVM: Sanitize PSTATE.M when being set from userspace
* CVE-2018-14678
- x86/entry/64: Remove %ebx handling from error_entry/exit
* CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in
card.c
* CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
* Bionic
[Kernel-packages] [Bug 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822812 phase: Promote to Proposed phase-changed: Tuesday, 09. April 2019 10:11 UTC reason: - promote-to-proposed: Ongoing -- review in progress + 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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1822811 Title: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822812 phase: Promote to Proposed phase-changed: Tuesday, 09. April 2019 10:11 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/1822811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1534162] Re: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs
I think last time it was fixed by fixing base-installer. http://launchpadlibrarian.net/235185956/base-installer_1.158ubuntu1_1.158ubuntu2.diff.gz but this time around, we need to decide who/what/where should write out kernel-img.conf. because we do not have kernel-common by default. ** Also affects: base-installer (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: zipl-installer (Ubuntu) Status: Confirmed => Fix Released ** Changed in: subiquity Status: New => Confirmed ** Changed in: base-installer (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1534162 Title: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs Status in subiquity: Confirmed Status in base-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: New Status in zipl-installer package in Ubuntu: Fix Released Bug description: Symlinks are not managed correctly. Last installed and configured kernel, prior to purging -5- was -6-, yet symlinks were not updated to -6- when that happened. root@devac03:~# apt-get remove --purge linux-headers-4.3.0-5 linux-headers-4.3.0-5-generic linux-image-4.3.0-5-generic linux-image-extra-4.3.0-5-generic Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.3.0-5* linux-headers-4.3.0-5-generic* linux-image-4.3.0-5-generic* linux-image-extra-4.3.0-5-generic* 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded. After this operation, 131 MB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 92073 files and directories currently installed.) Removing linux-headers-4.3.0-5-generic (4.3.0-5.16) ... Removing linux-headers-4.3.0-5 (4.3.0-5.16) ... Removing linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic update-initramfs: Generating /boot/initrd.img-4.3.0-5-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot/' Building menu 'zipl-automatic-menu' Adding #1: IPL section 'ubuntu' (default) Preparing boot device: dasda (0200). Done. run-parts: executing /etc/kernel/postinst.d/pm-utils 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic run-parts: executing /etc/kernel/postinst.d/zz-zipl 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot/' Building menu 'zipl-automatic-menu' Adding #1: IPL section 'ubuntu' (default) Preparing boot device: dasda (0200). Done. Purging configuration files for linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ... Removing linux-image-4.3.0-5-generic (4.3.0-5.16) ... WARN: Proceeding with removing running kernel image. Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic update-initramfs: Deleting /boot/initrd.img-4.3.0-5-generic run-parts: executing /etc/kernel/postrm.d/zz-zipl 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic Using config file '/etc/zipl.conf' Error: Image file '/boot/vmlinuz' in section 'ubuntu': No such file or directory run-parts: /etc/kernel/postrm.d/zz-zipl exited with return code 1 Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/linux-image-4.3.0-5-generic.postrm line 328. dpkg: error processing package linux-image-4.3.0-5-generic (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-4.3.0-5-generic E: Sub-process /usr/bin/dpkg returned an error code (1) root@devac03:~# ls -latr /boot total 24208 drwx-- 2 root root16384 Dec 9 16:38 lost+found lrwxrwxrwx 1 root root 26 Jan 6 16:23 initrd.img -> initrd.img-4.3.0-5-generic lrwxrwxrwx 1 root root 23 Jan 6 16:24 vmlinuz -> vmlinuz-4.3.0-5-generic -rw--- 1 root root 13026048 Jan 11 21:36 vmlinuz-4.3.0-6-generic -rw--- 1 root root 2446124 Jan 11 21:36 System.map-4.3.0-6-generic -rw-r--r-- 1 root root63422 Jan 11 21:36 config-4.3.0-6-generic -rw-r--r-- 1 root root 517933 Jan 11 21:36 abi-4.3.0-6-generic drwxr-xr-x 22 root root 4096 Jan 14 13:03 .. -rw-r--r-- 1 root root 8574889 Jan 14 13:03 initrd.img-4.3.0-6-generic -rw--- 1 root root69632 Jan 14 13:41 bootmap drwxr-xr-x 3 root root 4096 Jan 14 13:41 . root@devac03:~# dpkg -l | grep 4.3.0 ii iproute
[Kernel-packages] [Bug 1822812] Re: linux-oracle: 4.15.0-1011.13 -proposed tracker
This bug was fixed in the package linux-oracle - 4.15.0-1011.13 --- linux-oracle (4.15.0-1011.13) bionic; urgency=medium * linux-oracle: 4.15.0-1011.13 -proposed tracker (LP: #1822812) * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log [ Ubuntu: 4.15.0-48.51 ] * linux: 4.15.0-48.51 -proposed tracker (LP: #1822820) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - [Packaging] resync retpoline extraction * 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386 (LP: #1812845) - btrfs: raid56: properly unmap parity page in finish_parity_scrub() * [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats (LP: #1719545) - cpupower : Fix header name to read idle state name * [amdgpu] screen corruption when using touchpad (LP: #1818617) - drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3) - drm/amdgpu: Free VGA stolen memory as soon as possible. * [SRU][B/C/OEM]IOMMU: add kernel dma protection (LP: #1820153) - ACPICA: AML parser: attempt to continue loading table after error - ACPI / property: Allow multiple property compatible _DSD entries - PCI / ACPI: Identify untrusted PCI devices - iommu/vt-d: Force IOMMU on for platform opt in hint - iommu/vt-d: Do not enable ATS for untrusted devices - thunderbolt: Export IOMMU based DMA protection support to userspace - iommu/vt-d: Disable ATS support on untrusted devices * Add basic support to NVLink2 passthrough (LP: #1819989) - powerpc/powernv/npu: Do not try invalidating 32bit table when 64bit table is enabled - powerpc/powernv: call OPAL_QUIESCE before OPAL_SIGNAL_SYSTEM_RESET - powerpc/powernv: Export opal_check_token symbol - powerpc/powernv: Make possible for user to force a full ipl cec reboot - powerpc/powernv/idoa: Remove unnecessary pcidev from pci_dn - powerpc/powernv: Move npu struct from pnv_phb to pci_controller - powerpc/powernv/npu: Move OPAL calls away from context manipulation - powerpc/pseries/iommu: Use memory@ nodes in max RAM address calculation - powerpc/pseries/npu: Enable platform support - powerpc/pseries: Remove IOMMU API support for non-LPAR systems - powerpc/powernv/npu: Check mmio_atsd array bounds when populating - powerpc/powernv/npu: Fault user page into the hypervisor's pagetable * Huawei Hi1822 NIC has poor performance (LP: #1820187) - net-next: hinic: fix a problem in free_tx_poll() - hinic: remove ndo_poll_controller - net-next/hinic: add checksum offload and TSO support - hinic: Fix l4_type parameter in hinic_task_set_tunnel_l4 - net-next/hinic:replace multiply and division operators - net-next/hinic:add rx checksum offload for HiNIC - net-next/hinic:fix a bug in set mac address - net-next/hinic: fix a bug in rx data flow - net: hinic: fix null pointer dereference on pointer hwdev - hinic: optmize rx refill buffer mechanism - net-next/hinic:add shutdown callback - net-next/hinic: replace disable_irq_nosync/enable_irq * [CONFIG] please enable highdpi font FONT_TER16x32 (LP: #1819881) - Fonts: New Terminus large console font - [Config]: enable highdpi Terminus 16x32 font support * [19.04 FEAT] qeth: Enhanced link speed - kernel part (LP: #1814892) - s390/qeth: report 25Gbit link speed * CVE-2017-5754 - x86/nmi: Fix NMI uaccess race against CR3 switching - x86/mm: Fix documentation of module mapping range with 4-level paging - x86/pti: Enable global pages for shared areas - x86/pti: Never implicitly clear _PAGE_GLOBAL for kernel image - x86/pti: Leave kernel text global for !PCID - x86/pti: Fix boot problems from Global-bit setting - x86/pti: Fix boot warning from Global-bit setting - x86/pti: Reduce amount of kernel text allowed to be Global - x86/pti: Disallow global kernel text with RANDSTRUCT - x86/entry/32: Add explicit 'l' instruction suffix - x86/asm-offsets: Move TSS_sp0 and TSS_sp1 to asm-offsets.c - x86/entry/32: Rename TSS_sysenter_sp0 to TSS_entry2task_stack - x86/entry/32: Load task stack from x86_tss.sp1 in SYSENTER handler - x86/entry/32: Put ESPFIX code into a macro - x86/entry/32: Unshare NMI return path - x86/entry/32: Split off return-to-kernel path - x86/entry/32: Enter the kernel via trampoline stack - x86/entry/32: Leave the kernel via trampoline stack - x86/entry/32: Introduce SAVE_ALL_NMI and RESTORE_ALL_NMI - x86/entry/32: Handle Entry from Kernel-Mode on Entry-Stack - x86/entry/32: Simplify debug entry point - x86/entry/32: Add PTI cr3 switch to non-NMI entry/exit points - x86/entry/32: Add PTI CR3 switches to NMI handler code - x86/entry: Rename update_sp0 to update_task_stack - x86/pgtable: Rename pti_set_user_pgd() to pti_set_user_pgtbl() - x86/pgtable/pae: Unsha
[Kernel-packages] [Bug 1823227] Re: linux-oem-osp1: 5.0.0-1001.2 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: - https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + WAS: kernel-stable-master-bug: 1823228 -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1823228 phase: Holding before Promote to Proposed phase-changed: Friday, 05. April 2019 12:09 UTC reason: - promote-to-proposed: Holding -- master bug not ready for proposed + promote-to-proposed: Holding -- master bug not ready for proposed ** Tags added: kernel-block-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/1823227 Title: linux-oem-osp1: 5.0.0-1001.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 WAS: kernel-stable-master-bug: 1823228 -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Tuesday, 09. April 2019 11:33 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823227] Re: linux-oem-osp1: 5.0.0-1001.2 -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 WAS: kernel-stable-master-bug: 1823228 -- swm properties -- boot-testing-requested: true phase: Holding before Promote to Proposed phase-changed: Friday, 05. April 2019 12:09 UTC reason: - promote-to-proposed: Holding -- master bug not ready for proposed + promote-to-proposed: Holding -- cycle on hold ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow WAS: kernel-stable-master-bug: 1823228 -- swm properties -- boot-testing-requested: true - phase: Holding before Promote to Proposed - phase-changed: Friday, 05. April 2019 12:09 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 09. April 2019 11:33 UTC reason: - promote-to-proposed: Holding -- cycle on hold + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823227 Title: linux-oem-osp1: 5.0.0-1001.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 WAS: kernel-stable-master-bug: 1823228 -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Tuesday, 09. April 2019 11:33 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick
Thanks for pointing out the regression commit. The patch author is from Sony, so it's better to ask the patch author directly the justification behind blacklisting. -- 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/1800839 Title: Dualshock3 hid_sony accelerometer not registering as joystick Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25 [12649.015925] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24 [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux perhaps this is only a config issue as when the new split gyro & analog sticks/buttons/triggers both appeared as joysticks while you can now see only Sony PLAYSTATION(R)3 Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 Controller Motion Sensors (input25) does not. Any questions I am happy to respond, I have every reason to believe this is actually not a bluez issue but google gives me no returns other than general compatibility issues over the new hid_sony driver splitting the gyro from the pad. I use this to stay current on instrument flying while working out of town using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator that fis in my laptop bag. thanks dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Wed Oct 31 15:06:00 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. GL503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash modprobe.blacklist=nouveau vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL503VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 60:F6:77:DD:DB:90 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:624605 acl:10743 sco:0 events:125 errors:0 TX bytes:5814 acl:12 sco:0 commands:106 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1800839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822812 phase: Promote to Proposed phase-changed: Tuesday, 09. April 2019 10:11 UTC reason: - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1822811 Title: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822812 phase: Promote to Proposed phase-changed: Tuesday, 09. April 2019 10:11 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1534162] Re: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs
** Also affects: curtin Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Invalid ** Changed in: curtin 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/1534162 Title: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs Status in curtin: Confirmed Status in subiquity: Confirmed Status in base-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Invalid Status in zipl-installer package in Ubuntu: Fix Released Bug description: On Ubuntu/Debian like systems /etc/kernel-img.conf should be created by the "installer". It is currently done by base-installer/live-installer/ubiquity but not curtin, but it should be. At the moment we require kernel-img.conf and we do not have the correct per-arch built-in defaults for its settings in all of our kernels. It is not a config file, nor is it created by livecd-rootfs (after all our squashfs might be containers, and never live to install kernels and bootloaders). One day we might fix our kernels to not require kernel-img.conf, but until then curtin should be generating the right one. Making a merge proposal to fix this in curtin by mimicking what base-installer did. == Symlinks are not managed correctly. Last installed and configured kernel, prior to purging -5- was -6-, yet symlinks were not updated to -6- when that happened. root@devac03:~# apt-get remove --purge linux-headers-4.3.0-5 linux-headers-4.3.0-5-generic linux-image-4.3.0-5-generic linux-image-extra-4.3.0-5-generic Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.3.0-5* linux-headers-4.3.0-5-generic* linux-image-4.3.0-5-generic* linux-image-extra-4.3.0-5-generic* 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded. After this operation, 131 MB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 92073 files and directories currently installed.) Removing linux-headers-4.3.0-5-generic (4.3.0-5.16) ... Removing linux-headers-4.3.0-5 (4.3.0-5.16) ... Removing linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic update-initramfs: Generating /boot/initrd.img-4.3.0-5-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot/' Building menu 'zipl-automatic-menu' Adding #1: IPL section 'ubuntu' (default) Preparing boot device: dasda (0200). Done. run-parts: executing /etc/kernel/postinst.d/pm-utils 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic run-parts: executing /etc/kernel/postinst.d/zz-zipl 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot/' Building menu 'zipl-automatic-menu' Adding #1: IPL section 'ubuntu' (default) Preparing boot device: dasda (0200). Done. Purging configuration files for linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ... Removing linux-image-4.3.0-5-generic (4.3.0-5.16) ... WARN: Proceeding with removing running kernel image. Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic update-initramfs: Deleting /boot/initrd.img-4.3.0-5-generic run-parts: executing /etc/kernel/postrm.d/zz-zipl 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic Using config file '/etc/zipl.conf' Error: Image file '/boot/vmlinuz' in section 'ubuntu': No such file or directory run-parts: /etc/kernel/postrm.d/zz-zipl exited with return code 1 Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/linux-image-4.3.0-5-generic.postrm line 328. dpkg: error processing package linux-image-4.3.0-5-generic (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-4.3.0-5-generic E: Sub-process /usr/bin/dpkg returned an error code (1) root@devac03:~# ls -latr /boot total 24208 drwx-- 2 root root16384 Dec 9 16:38 lost+found lrwxrwxrwx 1 root root 26 Jan 6 16:23 initrd.img -> initrd.img-4.3.0-5-generic lrwxrwxrwx 1 root root 23 Jan 6 16:24 vmlinuz -> vmlinuz-4.3.0-5-generic -rw--- 1 root root 13026048 Jan 11 21:36 vmlinuz-4.3.0-6-generic -rw--- 1 root root 2446124 Jan 11 21:36 System.map-4.3.0-6-generic -rw-r--r-- 1 root root63422 Jan 11 21:36 config-4.3.0-6-generic -rw-r--r-- 1 root root 517933 Jan 11 21:36 abi-4.3.0-6-generic drwxr-xr-x 22 r
[Kernel-packages] [Bug 1534162] Re: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs
** Description changed: + + On Ubuntu/Debian like systems /etc/kernel-img.conf should be created by the "installer". It is currently done by base-installer/live-installer/ubiquity but not curtin, but it should be. At the moment we require kernel-img.conf and we do not have the correct per-arch built-in defaults for its settings in all of our kernels. It is not a config file, nor is it created by livecd-rootfs (after all our squashfs might be containers, and never live to install kernels and bootloaders). + + One day we might fix our kernels to not require kernel-img.conf, but + until then curtin should be generating the right one. Making a merge + proposal to fix this in curtin by mimicking what base-installer did. + + == + Symlinks are not managed correctly. Last installed and configured kernel, prior to purging -5- was -6-, yet symlinks were not updated to -6- when that happened. root@devac03:~# apt-get remove --purge linux-headers-4.3.0-5 linux-headers-4.3.0-5-generic linux-image-4.3.0-5-generic linux-image-extra-4.3.0-5-generic Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following packages will be REMOVED: - linux-headers-4.3.0-5* linux-headers-4.3.0-5-generic* linux-image-4.3.0-5-generic* - linux-image-extra-4.3.0-5-generic* + linux-headers-4.3.0-5* linux-headers-4.3.0-5-generic* linux-image-4.3.0-5-generic* + linux-image-extra-4.3.0-5-generic* 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded. After this operation, 131 MB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 92073 files and directories currently installed.) Removing linux-headers-4.3.0-5-generic (4.3.0-5.16) ... Removing linux-headers-4.3.0-5 (4.3.0-5.16) ... Removing linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic update-initramfs: Generating /boot/initrd.img-4.3.0-5-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot/' Building menu 'zipl-automatic-menu' Adding #1: IPL section 'ubuntu' (default) Preparing boot device: dasda (0200). Done. run-parts: executing /etc/kernel/postinst.d/pm-utils 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic run-parts: executing /etc/kernel/postinst.d/zz-zipl 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot/' Building menu 'zipl-automatic-menu' Adding #1: IPL section 'ubuntu' (default) Preparing boot device: dasda (0200). Done. Purging configuration files for linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ... Removing linux-image-4.3.0-5-generic (4.3.0-5.16) ... WARN: Proceeding with removing running kernel image. Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic update-initramfs: Deleting /boot/initrd.img-4.3.0-5-generic run-parts: executing /etc/kernel/postrm.d/zz-zipl 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic Using config file '/etc/zipl.conf' Error: Image file '/boot/vmlinuz' in section 'ubuntu': No such file or directory run-parts: /etc/kernel/postrm.d/zz-zipl exited with return code 1 Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/linux-image-4.3.0-5-generic.postrm line 328. dpkg: error processing package linux-image-4.3.0-5-generic (--purge): - subprocess installed post-removal script returned error exit status 1 + subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: - linux-image-4.3.0-5-generic + linux-image-4.3.0-5-generic E: Sub-process /usr/bin/dpkg returned an error code (1) root@devac03:~# ls -latr /boot total 24208 drwx-- 2 root root16384 Dec 9 16:38 lost+found lrwxrwxrwx 1 root root 26 Jan 6 16:23 initrd.img -> initrd.img-4.3.0-5-generic lrwxrwxrwx 1 root root 23 Jan 6 16:24 vmlinuz -> vmlinuz-4.3.0-5-generic -rw--- 1 root root 13026048 Jan 11 21:36 vmlinuz-4.3.0-6-generic -rw--- 1 root root 2446124 Jan 11 21:36 System.map-4.3.0-6-generic -rw-r--r-- 1 root root63422 Jan 11 21:36 config-4.3.0-6-generic -rw-r--r-- 1 root root 517933 Jan 11 21:36 abi-4.3.0-6-generic drwxr-xr-x 22 root root 4096 Jan 14 13:03 .. -rw-r--r-- 1 root root 8574889 Jan 14 13:03 initrd.img-4.3.0-6-generic -rw--- 1 root root69632 Jan 14 13:41 bootmap drwxr-xr-x 3 root root 4096 Jan 14 13:41 . root@devac03:~# dpkg -l | grep 4.3.0 ii iproute 1:4.3.0-1ubuntu1 all transitional dummy package for iproute2 ii iproute2 4.3.0-1ubuntu1
[Kernel-packages] [Bug 1534162] Re: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs
** Merge proposal linked: https://code.launchpad.net/~xnox/curtin/+git/curtin/+merge/346539 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1534162 Title: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs Status in curtin: Confirmed Status in subiquity: Confirmed Status in base-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Invalid Status in zipl-installer package in Ubuntu: Fix Released Bug description: On Ubuntu/Debian like systems /etc/kernel-img.conf should be created by the "installer". It is currently done by base-installer/live-installer/ubiquity but not curtin, but it should be. At the moment we require kernel-img.conf and we do not have the correct per-arch built-in defaults for its settings in all of our kernels. It is not a config file, nor is it created by livecd-rootfs (after all our squashfs might be containers, and never live to install kernels and bootloaders). One day we might fix our kernels to not require kernel-img.conf, but until then curtin should be generating the right one. Making a merge proposal to fix this in curtin by mimicking what base-installer did. == Symlinks are not managed correctly. Last installed and configured kernel, prior to purging -5- was -6-, yet symlinks were not updated to -6- when that happened. root@devac03:~# apt-get remove --purge linux-headers-4.3.0-5 linux-headers-4.3.0-5-generic linux-image-4.3.0-5-generic linux-image-extra-4.3.0-5-generic Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.3.0-5* linux-headers-4.3.0-5-generic* linux-image-4.3.0-5-generic* linux-image-extra-4.3.0-5-generic* 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded. After this operation, 131 MB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 92073 files and directories currently installed.) Removing linux-headers-4.3.0-5-generic (4.3.0-5.16) ... Removing linux-headers-4.3.0-5 (4.3.0-5.16) ... Removing linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic update-initramfs: Generating /boot/initrd.img-4.3.0-5-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot/' Building menu 'zipl-automatic-menu' Adding #1: IPL section 'ubuntu' (default) Preparing boot device: dasda (0200). Done. run-parts: executing /etc/kernel/postinst.d/pm-utils 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic run-parts: executing /etc/kernel/postinst.d/zz-zipl 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot/' Building menu 'zipl-automatic-menu' Adding #1: IPL section 'ubuntu' (default) Preparing boot device: dasda (0200). Done. Purging configuration files for linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ... Removing linux-image-4.3.0-5-generic (4.3.0-5.16) ... WARN: Proceeding with removing running kernel image. Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic update-initramfs: Deleting /boot/initrd.img-4.3.0-5-generic run-parts: executing /etc/kernel/postrm.d/zz-zipl 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic Using config file '/etc/zipl.conf' Error: Image file '/boot/vmlinuz' in section 'ubuntu': No such file or directory run-parts: /etc/kernel/postrm.d/zz-zipl exited with return code 1 Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/linux-image-4.3.0-5-generic.postrm line 328. dpkg: error processing package linux-image-4.3.0-5-generic (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-4.3.0-5-generic E: Sub-process /usr/bin/dpkg returned an error code (1) root@devac03:~# ls -latr /boot total 24208 drwx-- 2 root root16384 Dec 9 16:38 lost+found lrwxrwxrwx 1 root root 26 Jan 6 16:23 initrd.img -> initrd.img-4.3.0-5-generic lrwxrwxrwx 1 root root 23 Jan 6 16:24 vmlinuz -> vmlinuz-4.3.0-5-generic -rw--- 1 root root 13026048 Jan 11 21:36 vmlinuz-4.3.0-6-generic -rw--- 1 root root 2446124 Jan 11 21:36 System.map-4.3.0-6-generic -rw-r--r-- 1 root root63422 Jan 11 21:36 config-4.3.0-6-generic -rw-r--r-- 1 root root 517933 Jan 11 21:36 abi-4.3.0-6-generic drwxr-xr-x 22 root root 4096 Jan 14 13:03 .. -rw-r--r-- 1 root root 8574889 Jan 14 13:03 initrd.img-4.3.
[Kernel-packages] [Bug 1805304] Re: [Hyper-V] Additional patches for Lv2 storage performance
** Also affects: linux-azure (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Cosmic) Status: New => In Progress -- 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/1805304 Title: [Hyper-V] Additional patches for Lv2 storage performance Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure source package in Cosmic: In Progress Bug description: After analysis of the first 4.15 kernel for Lv2 performance, and while we are delayed getting to 4.18, we have identified and backported the following patches for the 4.15 linux-azure kernel: commit 1268ed0c474a5c8f165ef386f3310521b5e00e27 Author: K. Y. Srinivasan Date: Tue Jul 3 16:01:55 2018 -0700 x86/hyper-v: Fix the circular dependency in IPI enlightenment linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=1268ed0c474a5c8f165ef386f3310521b5e00e27 commit 366f03b0cf90ef55f063d4a54cf62b0ac9b6da9d Author: K. Y. Srinivasan Date: Wed May 16 14:53:32 2018 -0700 X86/Hyper-V: Enhanced IPI enlightenment https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=366f03b0cf90ef55f063d4a54cf62b0ac9b6da9d commit 68bb7bfb7985df2bd15c2dc975cb68b7a901488a Author: K. Y. Srinivasan Date: Wed May 16 14:53:31 2018 -0700 X86/Hyper-V: Enable IPI enlightenments https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=68bb7bfb7985df2bd15c2dc975cb68b7a901488a commit 6b48cb5f8347bc0153ff1d7b075db92e6723ffdb Author: K. Y. Srinivasan Date: Wed May 16 14:53:30 2018 -0700 X86/Hyper-V: Enlighten APIC access https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=6b48cb5f8347bc0153ff1d7b075db92e6723ffdb commit 68d1eb72ee99e26576913aa6824f7a703ca06b90 Author: Vitaly Kuznetsov Date: Tue Mar 20 15:02:09 2018 +0100 x86/hyper-v: define struct hv_enlightened_vmcs and clean field bits https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=68d1eb72ee99e26576913aa6824f7a703ca06b90 commit a46d15cc1ae5af905afac2af4cc0c188c2eb59b0 Author: Vitaly Kuznetsov Date: Tue Mar 20 15:02:08 2018 +0100 x86/hyper-v: allocate and use Virtual Processor Assist Pages https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=a46d15cc1ae5af905afac2af4cc0c188c2eb59b0 commit 415bd1cd3a42897f61a92cda0a9f9d7b04c28fb7 Author: Vitaly Kuznetsov Date: Tue Mar 20 15:02:06 2018 +0100 x86/hyper-v: move definitions from TLFS to hyperv-tlfs.h https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=415bd1cd3a42897f61a92cda0a9f9d7b04c28fb7 commit 5a485803221777013944cbd1a7cd5c62efba3ffa Author: Vitaly Kuznetsov Date: Tue Mar 20 15:02:05 2018 +0100 x86/hyper-v: move hyperv.h out of uapi https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=5a485803221777013944cbd1a7cd5c62efba3ffa commit e7c4e36c447daca2b7df49024f6bf230871cb155 Author: Vitaly Kuznetsov Date: Wed Jan 24 14:23:34 2018 +0100 x86/hyperv: Redirect reenlightment notifications on CPU offlining https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=e7c4e36c447daca2b7df49024f6bf230871cb155 commit 93286261de1b46339aa27cd4c639b21778f6cade Author: Vitaly Kuznetsov Date: Wed Jan 24 14:23:33 2018 +0100 x86/hyperv: Reenlightenment notifications support https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=93286261de1b46339aa27cd4c639b21778f6cade commit e2768eaa1ca4fbb7b778da5615cce3dd310352e6 Author: Vitaly Kuznetsov Date: Wed Jan 24 14:23:32 2018 +0100 x86/hyperv: Add a function to read both TSC and TSC page value simulateneously https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=e2768eaa1ca4fbb7b778da5615cce3dd310352e6 commit 4a5f3cde4d51c7afce859aed9d74d197751896d5 Author: Michael Kelley Date: Fri Dec 22 11:19:02 2017 -0700 Drivers: hv: vmbus: Remove x86-isms from arch independent drivers https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/hv?h=next-20181126&id=4a5f3cde4d51c7afce859aed9d74d197751896d5 From: Dexuan Cui We can concurrently try to open the same sub-channel from 2 paths: path #1: vmbus_onoffer() -> vmbus_process_offer() -> handle_sc_creation(). path #2: storvsc_probe() -> storvsc_connect_to_vsp() -> -> storvsc_channel_init() -> handle_multichannel_storage() -> -> vmbus_are_subchannels_pr
[Kernel-packages] [Bug 1534162] Re: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs
** Merge proposal linked: https://code.launchpad.net/~xnox/curtin/+git/curtin/+merge/365739 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1534162 Title: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs Status in curtin: Confirmed Status in subiquity: Confirmed Status in base-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Invalid Status in zipl-installer package in Ubuntu: Fix Released Bug description: On Ubuntu/Debian like systems /etc/kernel-img.conf should be created by the "installer". It is currently done by base-installer/live-installer/ubiquity but not curtin, but it should be. At the moment we require kernel-img.conf and we do not have the correct per-arch built-in defaults for its settings in all of our kernels. It is not a config file, nor is it created by livecd-rootfs (after all our squashfs might be containers, and never live to install kernels and bootloaders). One day we might fix our kernels to not require kernel-img.conf, but until then curtin should be generating the right one. Making a merge proposal to fix this in curtin by mimicking what base-installer did. == Symlinks are not managed correctly. Last installed and configured kernel, prior to purging -5- was -6-, yet symlinks were not updated to -6- when that happened. root@devac03:~# apt-get remove --purge linux-headers-4.3.0-5 linux-headers-4.3.0-5-generic linux-image-4.3.0-5-generic linux-image-extra-4.3.0-5-generic Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.3.0-5* linux-headers-4.3.0-5-generic* linux-image-4.3.0-5-generic* linux-image-extra-4.3.0-5-generic* 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded. After this operation, 131 MB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 92073 files and directories currently installed.) Removing linux-headers-4.3.0-5-generic (4.3.0-5.16) ... Removing linux-headers-4.3.0-5 (4.3.0-5.16) ... Removing linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic update-initramfs: Generating /boot/initrd.img-4.3.0-5-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot/' Building menu 'zipl-automatic-menu' Adding #1: IPL section 'ubuntu' (default) Preparing boot device: dasda (0200). Done. run-parts: executing /etc/kernel/postinst.d/pm-utils 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic run-parts: executing /etc/kernel/postinst.d/zz-zipl 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot/' Building menu 'zipl-automatic-menu' Adding #1: IPL section 'ubuntu' (default) Preparing boot device: dasda (0200). Done. Purging configuration files for linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ... Removing linux-image-4.3.0-5-generic (4.3.0-5.16) ... WARN: Proceeding with removing running kernel image. Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic update-initramfs: Deleting /boot/initrd.img-4.3.0-5-generic run-parts: executing /etc/kernel/postrm.d/zz-zipl 4.3.0-5-generic /boot/vmlinuz-4.3.0-5-generic Using config file '/etc/zipl.conf' Error: Image file '/boot/vmlinuz' in section 'ubuntu': No such file or directory run-parts: /etc/kernel/postrm.d/zz-zipl exited with return code 1 Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/linux-image-4.3.0-5-generic.postrm line 328. dpkg: error processing package linux-image-4.3.0-5-generic (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-4.3.0-5-generic E: Sub-process /usr/bin/dpkg returned an error code (1) root@devac03:~# ls -latr /boot total 24208 drwx-- 2 root root16384 Dec 9 16:38 lost+found lrwxrwxrwx 1 root root 26 Jan 6 16:23 initrd.img -> initrd.img-4.3.0-5-generic lrwxrwxrwx 1 root root 23 Jan 6 16:24 vmlinuz -> vmlinuz-4.3.0-5-generic -rw--- 1 root root 13026048 Jan 11 21:36 vmlinuz-4.3.0-6-generic -rw--- 1 root root 2446124 Jan 11 21:36 System.map-4.3.0-6-generic -rw-r--r-- 1 root root63422 Jan 11 21:36 config-4.3.0-6-generic -rw-r--r-- 1 root root 517933 Jan 11 21:36 abi-4.3.0-6-generic drwxr-xr-x 22 root root 4096 Jan 14 13:03 .. -rw-r--r-- 1 root root 8574889 Jan 14 13:03 initrd.img-4.3.
[Kernel-packages] [Bug 1823379] Re: Apparmor enforcement failure in lxc selftests
** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Assignee: (unassigned) => John Johansen (jjohansen) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Description changed: + SRU Justification + + Impact: The LSM stacking patches for disco changed the values read from + /sys/module/apparmor/parameters/enabled from Y/N to 0/1. This has caused + regressions in applications which expect Y/N, as demonstrated by this + failing lxc dep8 test. + + Fix: Change the values read back from + /sys/module/apparmor/parameters/enabled to Y/N. + + Regression Potential: Minimal, the change is straightforward and fixes a + regression. + + Test Case: Can be confirmed with 'cat + /sys/module/apparmor/parameters/enabled' and by running the lxc dep8 + tests and confirming that lxc-test-apparmor passes. + + --- + The lxc apparmor tests are failing with linux 5.0.0-9.10. The test expects an open of /sys/kernel/uevent_helper to fail, but it succeeds: FAIL: lxc-tests: lxc-test-apparmor (2s) --- failed - opened /sys/kernel/uevent_helper --- Full test log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco-canonical-kernel-team- bootstrap/disco/amd64/l/lxc/20190405_07_d0e52@/log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823379 Title: Apparmor enforcement failure in lxc selftests Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: The LSM stacking patches for disco changed the values read from /sys/module/apparmor/parameters/enabled from Y/N to 0/1. This has caused regressions in applications which expect Y/N, as demonstrated by this failing lxc dep8 test. Fix: Change the values read back from /sys/module/apparmor/parameters/enabled to Y/N. Regression Potential: Minimal, the change is straightforward and fixes a regression. Test Case: Can be confirmed with 'cat /sys/module/apparmor/parameters/enabled' and by running the lxc dep8 tests and confirming that lxc-test-apparmor passes. --- The lxc apparmor tests are failing with linux 5.0.0-9.10. The test expects an open of /sys/kernel/uevent_helper to fail, but it succeeds: FAIL: lxc-tests: lxc-test-apparmor (2s) --- failed - opened /sys/kernel/uevent_helper --- Full test log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco-canonical-kernel-team- bootstrap/disco/amd64/l/lxc/20190405_07_d0e52@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823379] Re: Apparmor enforcement failure in lxc selftests
** Changed in: linux (Ubuntu) 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/1823379 Title: Apparmor enforcement failure in lxc selftests Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: The LSM stacking patches for disco changed the values read from /sys/module/apparmor/parameters/enabled from Y/N to 0/1. This has caused regressions in applications which expect Y/N, as demonstrated by this failing lxc dep8 test. Fix: Change the values read back from /sys/module/apparmor/parameters/enabled to Y/N. Regression Potential: Minimal, the change is straightforward and fixes a regression. Test Case: Can be confirmed with 'cat /sys/module/apparmor/parameters/enabled' and by running the lxc dep8 tests and confirming that lxc-test-apparmor passes. --- The lxc apparmor tests are failing with linux 5.0.0-9.10. The test expects an open of /sys/kernel/uevent_helper to fail, but it succeeds: FAIL: lxc-tests: lxc-test-apparmor (2s) --- failed - opened /sys/kernel/uevent_helper --- Full test log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco-canonical-kernel-team- bootstrap/disco/amd64/l/lxc/20190405_07_d0e52@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822812 - phase: Promote to Proposed - phase-changed: Tuesday, 09. April 2019 10:11 UTC + phase: Testing + phase-changed: Tuesday, 09. April 2019 13:13 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- 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/1822811 Title: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822812 phase: Testing phase-changed: Tuesday, 09. April 2019 13:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823936] [NEW] linux: 5.0.0-10.11 -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 backports: bug 1823224 (bionic/linux-hwe-edge), bug 1823227 (bionic/linux-oem-osp1) derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 (linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 (linux-snapdragon) -- swm properties -- ** 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/prepare-package Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Disco) Importance: Medium Status: New ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.04.04-2 ** Also affects: kernel-sru-workflow/automated-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-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) 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/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) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: disco ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: kernel-sru-cycle-d2019.04.04-2 ** 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 1823224 (bionic/linux-hwe-edge) + + -- swm properties -- ** Description changed: This bug will contain status and test results related to a kernel source (or snap)
[Kernel-packages] [Bug 1823227] Re: linux-oem-osp1: 5.0.0-1001.2 -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 - - WAS: kernel-stable-master-bug: 1823228 + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true + kernel-stable-master-bug: 1823936 phase: Ready for Promote to Proposed phase-changed: Tuesday, 09. April 2019 11:33 UTC reason: promote-to-proposed: Pending -- ready for review ** Tags removed: kernel-sru-backport-of-1823228 ** Tags added: kernel-sru-backport-of-1823936 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823227 Title: linux-oem-osp1: 5.0.0-1001.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: 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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1823936 phase: Promote to Proposed phase-changed: Tuesday, 09. April 2019 13:32 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823227] Re: linux-oem-osp1: 5.0.0-1001.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823227 Title: linux-oem-osp1: 5.0.0-1001.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: 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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1823936 phase: Promote to Proposed phase-changed: Tuesday, 09. April 2019 13:32 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823228] Re: linux: 5.0.0-9.10 -proposed tracker
*** This bug is a duplicate of bug 1823936 *** https://bugs.launchpad.net/bugs/1823936 ** 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 1823224 (bionic/linux-hwe-edge), bug 1823227 (bionic/linux-oem-osp1) - derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 (linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823223 (linux-snapdragon) + derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 (linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm) -- swm properties -- phase: Packaging phase-changed: Thursday, 04. April 2019 20:10 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 ** This bug has been marked a duplicate of bug 1823936 linux: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823228 Title: linux: 5.0.0-9.10 -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: 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-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Disco: 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 1823224 (bionic/linux-hwe-edge), bug 1823227 (bionic/linux-oem-osp1) derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 (linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm) -- swm properties -- phase: Packaging phase-changed: Thursday, 04. April 2019 20:10 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/1823228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823221] Re: linux-gcp: -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: 1823228 + kernel-stable-master-bug: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug ** Tags removed: kernel-sru-derivative-of-1823228 ** Tags added: kernel-sru-derivative-of-1823936 -- 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/1823221 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 prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Disco: 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 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/1823221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823219] Re: linux-aws: -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: 1823228 + kernel-stable-master-bug: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug ** Tags removed: kernel-sru-derivative-of-1823228 ** Tags added: kernel-sru-derivative-of-1823936 -- 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/1823219 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 prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Disco: 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 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/1823219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823220] Re: linux-azure: -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: 1823228 + kernel-stable-master-bug: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug ** Tags removed: kernel-sru-derivative-of-1823228 ** Tags added: kernel-sru-derivative-of-1823936 -- 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/1823220 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 prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Disco: 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 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/1823220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823218] Re: linux-raspi2: -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: 1823228 + kernel-stable-master-bug: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug ** Tags removed: kernel-sru-derivative-of-1823228 ** Tags added: kernel-sru-derivative-of-1823936 -- 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/1823218 Title: linux-raspi2: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Disco: 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 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/1823218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823222] Re: linux-kvm: -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: 1823228 + kernel-stable-master-bug: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug ** Tags removed: kernel-sru-derivative-of-1823228 ** Tags added: kernel-sru-derivative-of-1823936 -- 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/1823222 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 prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 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/1823222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823227] Re: linux-oem-osp1: 5.0.0-1001.2 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1823936 - phase: Ready for Promote to Proposed - phase-changed: Tuesday, 09. April 2019 11:33 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 09. April 2019 13:32 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823227 Title: linux-oem-osp1: 5.0.0-1001.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: 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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1823936 phase: Promote to Proposed phase-changed: Tuesday, 09. April 2019 13:32 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick
kaihengfeng, emailed Roderick Colenbrander the commit at Sony and we will see. -- 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/1800839 Title: Dualshock3 hid_sony accelerometer not registering as joystick Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25 [12649.015925] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24 [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux perhaps this is only a config issue as when the new split gyro & analog sticks/buttons/triggers both appeared as joysticks while you can now see only Sony PLAYSTATION(R)3 Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 Controller Motion Sensors (input25) does not. Any questions I am happy to respond, I have every reason to believe this is actually not a bluez issue but google gives me no returns other than general compatibility issues over the new hid_sony driver splitting the gyro from the pad. I use this to stay current on instrument flying while working out of town using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator that fis in my laptop bag. thanks dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Wed Oct 31 15:06:00 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. GL503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash modprobe.blacklist=nouveau vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL503VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 60:F6:77:DD:DB:90 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:624605 acl:10743 sco:0 events:125 errors:0 TX bytes:5814 acl:12 sco:0 commands:106 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1800839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823936] Re: linux: 5.0.0-10.11 -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 1823224 (bionic/linux-hwe-edge), bug 1823227 (bionic/linux-oem-osp1) derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 (linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 (linux-snapdragon) -- swm properties -- + phase: Packaging + phase-changed: Tuesday, 09. April 2019 13:42 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/1823936 Title: linux: 5.0.0-10.11 -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: 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-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Disco: 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 1823224 (bionic/linux-hwe-edge), bug 1823227 (bionic/linux-oem-osp1) derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 (linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 (linux-snapdragon) -- swm properties -- phase: Packaging phase-changed: Tuesday, 09. April 2019 13:42 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/1823936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823805] Re: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit
https://lists.ubuntu.com/archives/kernel-team/2019-April/099939.html ** Also affects: linux-azure (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Cosmic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1823805 Title: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Cosmic: In Progress Bug description: The following commit is being requested in the 18.04 4.18 based Bionic kernel for Azure: c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause panic This commit was included when it was requested in bug 1805304. However, the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel at that time. The patch was applied to the 4.15 based kernel as an Ubuntu SAUCE patch. The 18.04 Bionic kernel for Azure has since been re-based to the 4.18 kernel. This requested commit was applied to mainline as of v4.20-rc6. The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that point. Due to this, the patch never made it into any 4.18 kernels, which is why it is now missing from 18.04, it was rebased to 4.18. This is a critical issue. The 4.18.0-1015 kernel immediately panics on boot without this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1823805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9757] Occasionally fails to suspend and locks up instead
Yes, I've seen it on both bionic and cosmic kernels in addition to disco's ** Summary changed: - [Dell XPS 15 9757] Occasionally fails to suspend and locks up instead + [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[979
[Kernel-packages] [Bug 1805304] Re: [Hyper-V] Additional patches for Lv2 storage performance
** Changed in: linux-azure (Ubuntu Cosmic) Status: In Progress => Invalid -- 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/1805304 Title: [Hyper-V] Additional patches for Lv2 storage performance Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure source package in Cosmic: Invalid Bug description: After analysis of the first 4.15 kernel for Lv2 performance, and while we are delayed getting to 4.18, we have identified and backported the following patches for the 4.15 linux-azure kernel: commit 1268ed0c474a5c8f165ef386f3310521b5e00e27 Author: K. Y. Srinivasan Date: Tue Jul 3 16:01:55 2018 -0700 x86/hyper-v: Fix the circular dependency in IPI enlightenment linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=1268ed0c474a5c8f165ef386f3310521b5e00e27 commit 366f03b0cf90ef55f063d4a54cf62b0ac9b6da9d Author: K. Y. Srinivasan Date: Wed May 16 14:53:32 2018 -0700 X86/Hyper-V: Enhanced IPI enlightenment https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=366f03b0cf90ef55f063d4a54cf62b0ac9b6da9d commit 68bb7bfb7985df2bd15c2dc975cb68b7a901488a Author: K. Y. Srinivasan Date: Wed May 16 14:53:31 2018 -0700 X86/Hyper-V: Enable IPI enlightenments https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=68bb7bfb7985df2bd15c2dc975cb68b7a901488a commit 6b48cb5f8347bc0153ff1d7b075db92e6723ffdb Author: K. Y. Srinivasan Date: Wed May 16 14:53:30 2018 -0700 X86/Hyper-V: Enlighten APIC access https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=6b48cb5f8347bc0153ff1d7b075db92e6723ffdb commit 68d1eb72ee99e26576913aa6824f7a703ca06b90 Author: Vitaly Kuznetsov Date: Tue Mar 20 15:02:09 2018 +0100 x86/hyper-v: define struct hv_enlightened_vmcs and clean field bits https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=68d1eb72ee99e26576913aa6824f7a703ca06b90 commit a46d15cc1ae5af905afac2af4cc0c188c2eb59b0 Author: Vitaly Kuznetsov Date: Tue Mar 20 15:02:08 2018 +0100 x86/hyper-v: allocate and use Virtual Processor Assist Pages https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=a46d15cc1ae5af905afac2af4cc0c188c2eb59b0 commit 415bd1cd3a42897f61a92cda0a9f9d7b04c28fb7 Author: Vitaly Kuznetsov Date: Tue Mar 20 15:02:06 2018 +0100 x86/hyper-v: move definitions from TLFS to hyperv-tlfs.h https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=415bd1cd3a42897f61a92cda0a9f9d7b04c28fb7 commit 5a485803221777013944cbd1a7cd5c62efba3ffa Author: Vitaly Kuznetsov Date: Tue Mar 20 15:02:05 2018 +0100 x86/hyper-v: move hyperv.h out of uapi https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=5a485803221777013944cbd1a7cd5c62efba3ffa commit e7c4e36c447daca2b7df49024f6bf230871cb155 Author: Vitaly Kuznetsov Date: Wed Jan 24 14:23:34 2018 +0100 x86/hyperv: Redirect reenlightment notifications on CPU offlining https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=e7c4e36c447daca2b7df49024f6bf230871cb155 commit 93286261de1b46339aa27cd4c639b21778f6cade Author: Vitaly Kuznetsov Date: Wed Jan 24 14:23:33 2018 +0100 x86/hyperv: Reenlightenment notifications support https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=93286261de1b46339aa27cd4c639b21778f6cade commit e2768eaa1ca4fbb7b778da5615cce3dd310352e6 Author: Vitaly Kuznetsov Date: Wed Jan 24 14:23:32 2018 +0100 x86/hyperv: Add a function to read both TSC and TSC page value simulateneously https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=e2768eaa1ca4fbb7b778da5615cce3dd310352e6 commit 4a5f3cde4d51c7afce859aed9d74d197751896d5 Author: Michael Kelley Date: Fri Dec 22 11:19:02 2017 -0700 Drivers: hv: vmbus: Remove x86-isms from arch independent drivers https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/hv?h=next-20181126&id=4a5f3cde4d51c7afce859aed9d74d197751896d5 From: Dexuan Cui We can concurrently try to open the same sub-channel from 2 paths: path #1: vmbus_onoffer() -> vmbus_process_offer() -> handle_sc_creation(). path #2: storvsc_probe() -> storvsc_connect_to_vsp() -> -> storvsc_channel_init() -> handle_multichannel_storage() -> -> vmbus_are_subchannels_present() -> handle_sc_creation(). They conflict with each other, but it was not an issue
[Kernel-packages] [Bug 1823972] [NEW] bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch
Public bug reported: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.14..stable/linux-4.14.y -- fs/fuse/ 266a69895b89 fuse: handle zero sized retrieve correctly b928e93d864c fuse: decrement NR_WRITEBACK_TEMP on the right page 65f222bb370e fuse: call pipe_buf_release() under pipe lock c1149b873482 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS 6ceec07cc84a fuse: fix leaked notify reply a42d933dc281 fuse: fix use-after-free in fuse_direct_IO() 78da72ee42d8 fuse: set FR_SENT while locked f6f21a2b70c6 fuse: fix blocked_waitq wakeup ab962e91008a fuse: Fix use-after-free in fuse_dev_do_write() d94b3a2375cb fuse: Fix use-afte
[Kernel-packages] [Bug 1822794] Re: linux-kvm: 4.18.0-1010.10 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Thursday, 04. April 2019 00:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1822794 Title: linux-kvm: 4.18.0-1010.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-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 -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Thursday, 04. April 2019 00:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822793] Re: linux-gcp: 4.18.0-1009.10 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** 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 1822792 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Thursday, 04. April 2019 01:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1822793 Title: linux-gcp: 4.18.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in 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 1822792 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Thursday, 04. April 2019 01:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822870] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2019-04-09 10:04 EDT--- There's a couple extra patches we need to add to have all the mitigations (some that are from earlier than these DD 2.3 changes) from here: https://github.com/linuxppc/wiki/wiki/Spectre-and-Meltdown-Related-Commits I'll attach that later today. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822870 Title: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: For the different kernels: The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears to have all patches. Disco appears to be missing only this patch: 92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting Cosmic (which is supported until July) is missing a number of patches: cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation barrier from the command line 6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier PPC_BOOK3S_64 specific. 179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call setup_barrier_nospec() from setup_arch() 406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting Book3S 64 specific 06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & helpers for patching instructions dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security feature flags for count cache flush ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for software count cache flush ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor for count cache flush settings 99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for count cache flush settings 7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 mitigations reporting 92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting This appears to already be in -next. For the bionic 18.04.1 (4.15) kernel only this patch is already part of master-next: a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec The others are ported, there were only 3 that were not clean. Those are: 2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori barrier_nospec patching This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is missing, but it does not look like that is required here. cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec based on firmware settings This failed because debugfs was already included, I can see that previously added, I didn't see where it was previously removed. 06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & helpers for patching instructions This failed because 8183d99f4a22c is not included - but doesn't seem necessary. All other patches applied with, at most, some fuzz. Has had a little testing - boots, check debugfs, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1822870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1545330] Re: [wily][regression] systemtap script compilation broken by new kernels
By the way, a simple diagnostic for whether any particular version of
systemtap has been ported to a kernel is to run
% stap -V
Systemtap translator/driver (version 4.1/0.174, rpm
4.1-0.20190327git2ede4cecb20c.fc28)
Copyright (C) 2005-2019 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.18 ... 5.0-rc3
enabled features: AVAHI BOOST_STRING_REF DYNINST BPF JAVA PYTHON2 PYTHON3
LIBRPM LIBSQLITE3 LIBVIRT LIBXML2 NLS NSS READLINE
Note the "tested kernel versions" line. If your kernel is newer than
that, you'll need to switch to a fresher upstream systemtap version.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1545330
Title:
[wily][regression] systemtap script compilation broken by new kernels
Status in linux package in Ubuntu:
Fix Released
Status in systemtap package in Ubuntu:
Fix Released
Status in linux source package in Wily:
Fix Released
Status in systemtap source package in Wily:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in systemtap source package in Xenial:
Fix Released
Status in systemtap package in Fedora:
Fix Released
Bug description:
The following errors appear when compiling any systemtap script:
In file included from include/linux/mutex.h:15:0,
from
/tmp/stapbdpxn3/stap_a0ec17f995e8f89d672d8c2eb7fe7c24_1693_src.c:25:
include/linux/spinlock_types.h:55:14: error: ‘__ARCH_SPIN_LOCK_UNLOCKED’
undeclared here (not in a function)
.raw_lock = __ARCH_SPIN_LOCK_UNLOCKED, \
^
include/linux/spinlock_types.h:79:15: note: in expansion of macro
‘__RAW_SPIN_LOCK_INITIALIZER’
{ { .rlock = __RAW_SPIN_LOCK_INITIALIZER(lockname) } }
^
include/linux/spinlock_types.h:82:16: note: in expansion of macro
‘__SPIN_LOCK_INITIALIZER’
(spinlock_t ) __SPIN_LOCK_INITIALIZER(lockname)
^
include/linux/mutex.h:111:18: note: in expansion of macro
‘__SPIN_LOCK_UNLOCKED’
, .wait_lock = __SPIN_LOCK_UNLOCKED(lockname.wait_lock) \
^
include/linux/mutex.h:117:27: note: in expansion of macro
‘__MUTEX_INITIALIZER’
struct mutex mutexname = __MUTEX_INITIALIZER(mutexname)
Upstream fix:
https://www.sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=320e1ecb16427b5769f0f5a097d80823ee1fb765
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1545330/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823972] 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 1823972 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: 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/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Incomplete Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451
[Kernel-packages] [Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_scr
This bug was fixed in the package mutter - 3.32.0-1ubuntu2 --- mutter (3.32.0-1ubuntu2) disco; urgency=medium * debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: - Don't invert the screen size when rotation is enabled (LP: #1822513) - Remove unneeded cleanup changes - Use xcb checked function to set scaling to catch errors - Update screen size only after monitors modes have been derived (LP: #1822616) - Trigger a monitors rebuild only if scale has changed (LP: #1823485) - Only update UI scaling when output scaling is enabled (LP: #1822478) -- Marco Trevisan (Treviño) Wed, 03 Apr 2019 19:19:59 -0400 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- 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/1822616 Title: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size Status in budgie-desktop package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Bug description: https://errors.ubuntu.com/problem/de2c123796506b10cd9d03070c91b581d7c6ae0c WORKAROUNDS Don't use kernel parameter nvidia-drm.modeset=1 - or - Before trying to log in: 1. Ctrl+Alt+F4, log in to VT4 and run: sudo Xorg :4 vt4 2. Ctrl+Alt+F1, wait for the log screen to reappear, then log in normally. ORIGINAL DESCRIPTION I am unable to use the NVIDIA drivers Ubuntu Budgie installed with 3 vertical displays. I changed to the X.org driver and rebooted. This error popped up on reboot. And now only one display is working. This one display is only working in landscape instead of portrait mode. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: budgie-core 10.5-0ubuntu1 Uname: Linux 5.0.2-050002-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Apr 1 09:16:50 2019 ExecutablePath: /usr/bin/budgie-wm InstallationDate: Installed on 2019-01-10 (80 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) ProcCmdline: budgie-wm ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: budgie-desktop StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 Title: budgie-wm crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2019-03-25 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822788] Re: linux-aws: 4.18.0-1013.15 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** 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 1822787 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Wednesday, 03. April 2019 23:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1822788 Title: linux-aws: 4.18.0-1013.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-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 1822787 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Wednesday, 03. April 2019 23:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822791] Re: linux-azure: 4.18.0-1015.15 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** 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 1822790 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Thursday, 04. April 2019 17:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- 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/1822791 Title: linux-azure: 4.18.0-1015.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed 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 1822790 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Thursday, 04. April 2019 17:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch
apport information ** Tags added: apport-collected ** Description changed: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.14..stable/linux-4.14.y -- fs/fuse/ 266a69895b89 fuse: handle zero sized retrieve correctly b928e93d864c fuse: decrement NR_WRITEBACK_TEMP on the right page 65f222bb370e fuse: call pipe_buf_release() under pipe lock c1149b873482 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS 6ceec07cc84a fuse: fix leaked notify
[Kernel-packages] [Bug 1823972] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1823972/+attachment/5254446/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.14..stable/linux-4.14
[Kernel-packages] [Bug 1823972] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1823972/+attachment/5254449/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.14..st
[Kernel-packages] [Bug 1823972] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1823972/+attachment/5254447/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.14..
[Kernel-packages] [Bug 1823972] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1823972/+attachment/5254448/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.14..stable/linux-4.
[Kernel-packages] [Bug 1823972] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1823972/+attachment/5254450/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --one
[Kernel-packages] [Bug 1823972] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1823972/+attachment/5254453/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.14..st
[Kernel-packages] [Bug 1823972] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1823972/+attachment/5254456/+files/WifiSyslog.txt ** 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/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y h
[Kernel-packages] [Bug 1823972] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1823972/+attachment/5254455/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.14..stable/linux-
[Kernel-packages] [Bug 1822813] Re: linux-fips: 4.15.0-1003.4 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Holding before Promote to Proposed phase-changed: Friday, 05. April 2019 14:06 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822813 Title: linux-fips: 4.15.0-1003.4 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Holding before Promote to Proposed phase-changed: Friday, 05. April 2019 14:06 UTC reason: promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823972] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1823972/+attachment/5254451/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.14..st
[Kernel-packages] [Bug 1823972] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1823972/+attachment/5254452/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.
[Kernel-packages] [Bug 1823972] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1823972/+attachment/5254454/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.14..stable
[Kernel-packages] [Bug 1823219] Re: linux-aws: 5.0.0-1002.2 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 5.0.0-1002.2 -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) => Seth Forshee (sforshee) ** 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) => Seth Forshee (sforshee) -- 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/1823219 Title: linux-aws: 5.0.0-1002.2 -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: 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-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Disco: 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 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/1823219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch
** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns which suggests that other FUSE fixes should be cherry-picked too. Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.14..stable/linux-4.14.y -- fs/fuse/ 266a69895b89 fuse: handle zero sized retrieve correctly b928e93d864c fuse: decrement NR_W
[Kernel-packages] [Bug 1823346] Re: SD card stays locked even when unlocked
Tested with latest mainline build: v5.1-rc4 generic AMD64 kernel. Bug still exists. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823346 Title: SD card stays locked even when unlocked Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.2 LTS Release:18.04 After card reader device is used with write-protected SD card, write- protection incorrectly persists to future SD cards, even non-protected ones. To reproduce: 1) Insert non-protected SD card in card reader (confirm system normal): $ sudo hdparm -r /dev/sdd /dev/sdd: readonly = 0 (off) [result is correct] 2) Eject card, set physical lock on side of card, reinsert: $ sudo hdparm -r /dev/sdd /dev/sdd: readonly = 1 (on) [result is correct - card read-only] 3) Eject card again, unlock card, reinsert $ sudo hdparm -r /dev/sdd /dev/sdd: readonly = 1 (on) [result is **incorrect** (card still locked)] Because the lock is still set, the device always appears read-only. (For example, I cannot "dd" to /dev/sdd) Workaround: after removing the locked card, issue "sudo hdparm -r0" to turn off the lock. Then insert the unlocked card and the device will appear read/write. (I don't know if this is the right package to report against.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-3ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE CustomUdevRuleFiles: 69-basler-cameras.rules 99-realsense-libusb.rules Date: Fri Apr 5 14:50:32 2019 InstallationDate: Installed on 2016-09-28 (919 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Z620 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=1a9272d2-8838-4bb4-8f63-ce571641c48c ro quiet splash vt.handoff=1 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: Upgraded to bionic on 2019-01-14 (81 days ago) dmi.bios.date: 05/27/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.88 dmi.board.asset.tag: CZC4086C7Q dmi.board.name: 158A dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: CZC4086C7Q dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z620 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823346/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823346] Re: SD card stays locked even when unlocked
Sorry, trying to follow your instructions, but some competency problems here: I did install and test with v5.1-rc4 kernel. Behaviour is exactly the same. (oddly, this was the easy bit.) Finally worked out how to add a tag. But now: 1) my dmesg appears to be broken with this kernel. Just hundreds of lines all saying the same, eg: [ 693.835558] cma: cma_alloc: alloc failed, req-size: 1 pages, ret: -12 and 3) bug already says "confirmed" I'm confused. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823346 Title: SD card stays locked even when unlocked Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.2 LTS Release:18.04 After card reader device is used with write-protected SD card, write- protection incorrectly persists to future SD cards, even non-protected ones. To reproduce: 1) Insert non-protected SD card in card reader (confirm system normal): $ sudo hdparm -r /dev/sdd /dev/sdd: readonly = 0 (off) [result is correct] 2) Eject card, set physical lock on side of card, reinsert: $ sudo hdparm -r /dev/sdd /dev/sdd: readonly = 1 (on) [result is correct - card read-only] 3) Eject card again, unlock card, reinsert $ sudo hdparm -r /dev/sdd /dev/sdd: readonly = 1 (on) [result is **incorrect** (card still locked)] Because the lock is still set, the device always appears read-only. (For example, I cannot "dd" to /dev/sdd) Workaround: after removing the locked card, issue "sudo hdparm -r0" to turn off the lock. Then insert the unlocked card and the device will appear read/write. (I don't know if this is the right package to report against.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-3ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE CustomUdevRuleFiles: 69-basler-cameras.rules 99-realsense-libusb.rules Date: Fri Apr 5 14:50:32 2019 InstallationDate: Installed on 2016-09-28 (919 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Z620 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=1a9272d2-8838-4bb4-8f63-ce571641c48c ro quiet splash vt.handoff=1 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: Upgraded to bionic on 2019-01-14 (81 days ago) dmi.bios.date: 05/27/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.88 dmi.board.asset.tag: CZC4086C7Q dmi.board.name: 158A dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: CZC4086C7Q dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z620 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823346/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823219] Re: linux-aws: 5.0.0-1002.2 -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: 1823936 - phase: Holding before Packaging - phase-changed: Thursday, 04. April 2019 19:39 UTC + phase: Packaging + phase-changed: Tuesday, 09. April 2019 16:10 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1823219 Title: linux-aws: 5.0.0-1002.2 -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: 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-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Disco: 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: 1823936 phase: Packaging phase-changed: Tuesday, 09. April 2019 16:10 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/1823219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822832] Re: linux-aws: 4.4.0-1041.44 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1041.44 -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) => Connor Kuehl (connork) ** 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) => Connor Kuehl (connork) -- 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/1822832 Title: linux-aws: 4.4.0-1041.44 -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-signing-to-proposed 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 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 -- kernel-stable-master-bug: 1822834 phase: Ready for Packaging phase-changed: Wednesday, 03. April 2019 09:34 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick
Got this back from the Sony dev Roderick Colenbrander, "Unfortunately reverting the joydev patch is not an option. Let me explain why. Joydev is an old legacy for using joysticks. It is very limited and can only deal with buttons and sticks. It doesn't support new features like force feedback / rumble (though already added 15+ years ago), multitouch, motion sensors and other features. When we started offering motion sensors, this broke existing applications which were never designed with motion sensor support. Applications which would never get updated. Nor does joydev have a way to distinguish motion sensor axes from regular joystick axes. The recommended way for over a decade is to not use joydev, but use evdev, which is also what is used for keyboard, mouse and other devices. It offers all the features needed and it is supported fine for ds3 and ds4." I am playing with a hack that cam be found here: https://askubuntu.com/questions/1088925/ubuntu-18-04-no-longer-adds-second-joystick-device-for-sony-dualshock3s-gyro-ac which I have not gotten to fully work creating a joydev as I write this but I do now see both evdevs. Unfortunately joydev is still pretty standard for things like Flightgear. https://askubuntu.com/questions/1088925/ubuntu-18-04-no-longer-adds- second-joystick-device-for-sony-dualshock3s-gyro-ac -- 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/1800839 Title: Dualshock3 hid_sony accelerometer not registering as joystick Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25 [12649.015925] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24 [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux perhaps this is only a config issue as when the new split gyro & analog sticks/buttons/triggers both appeared as joysticks while you can now see only Sony PLAYSTATION(R)3 Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 Controller Motion Sensors (input25) does not. Any questions I am happy to respond, I have every reason to believe this is actually not a bluez issue but google gives me no returns other than general compatibility issues over the new hid_sony driver splitting the gyro from the pad. I use this to stay current on instrument flying while working out of town using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator that fis in my laptop bag. thanks dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Wed Oct 31 15:06:00 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. GL503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash modprobe.blacklist=nouveau vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL503VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 60:F6:77:DD:DB:90 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:624605 acl:10743 sco:0 events:125 errors:0 TX bytes:5814 acl:12 sco:0 commands:106 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1800839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823994] [NEW] arm64: not able to install linux-generic-hwe-18.04-edge/bionic-proposed
Public bug reported: 1. linux-generic-hwe-18.04-edge from bionic-updates is installed: `linux-generic-hwe-18.04-edge/bionic-updates,bionic-security,now 4.18.0.16.65 arm64 [installed]` ``` $ dpkg -l |grep linux-generic ii linux-generic-hwe-18.04-edge 4.18.0.16.65 arm64Complete Generic Linux kernel and headers ``` 2. enable -proposed archive and update: ``` $ sudo add-apt-repository "deb http://ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main restricted" $ sudo apt update ``` 3. shows it is upgradable: ``` $ apt search --names-only linux-generic linux-generic-hwe-18.04-edge/bionic-proposed 5.0.0.8.66 arm64 [upgradable from: 4.18.0.16.65] Complete Generic Linux kernel and headers ``` 4. try to install it, but: ``` $ sudo apt install linux-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge (= 5.0.0.8.66) but 4.18.0.16.65 is to be installed E: Unable to correct problems, you have held broken packages. ``` 5. same happens trying to install `linux-image-generic-hwe-18.04-edge`: ``` $ sudo apt install linux-image-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic-hwe-18.04-edge : Depends: linux-image-5.0.0-8-generic but it is not installable E: Unable to correct problems, you have held broken packages. ``` 6. also not able to install `linux-image-5.0.0-8-generic`: ``` $ sudo apt install linux-image-5.0.0-8-generic Reading package lists... Done Building dependency tree Reading state information... Done Package linux-image-5.0.0-8-generic is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-image-5.0.0-8-generic' has no installation candidate ``` more info: ~$ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 ~$ apt-cache policy linux-generic-hwe-18.04-edge linux-generic-hwe-18.04-edge: Installed: 4.18.0.16.65 Candidate: 5.0.0.8.66 Version table: 5.0.0.8.66 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 Packages *** 4.18.0.16.65 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages 100 /var/lib/dpkg/status ** 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-meta in Ubuntu. https://bugs.launchpad.net/bugs/1823994 Title: arm64: not able to install linux-generic-hwe-18.04-edge/bionic- proposed Status in linux package in Ubuntu: New Bug description: 1. linux-generic-hwe-18.04-edge from bionic-updates is installed: `linux-generic-hwe-18.04-edge/bionic-updates,bionic-security,now 4.18.0.16.65 arm64 [installed]` ``` $ dpkg -l |grep linux-generic ii linux-generic-hwe-18.04-edge 4.18.0.16.65 arm64Complete Generic Linux kernel and headers ``` 2. enable -proposed archive and update: ``` $ sudo add-apt-repository "deb http://ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main restricted" $ sudo apt update ``` 3. shows it is upgradable: ``` $ apt search --names-only linux-generic linux-generic-hwe-18.04-edge/bionic-proposed 5.0.0.8.66 arm64 [upgradable from: 4.18.0.16.65] Complete Generic Linux kernel and headers ``` 4. try to install it, but: ``` $ sudo apt install linux-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-18.04-edge : Depe
[Kernel-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work
Now dist-upgrade found that kernel. I can confirm, with this kernel rfkill reports the device unblocked. ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan unblocked unblocked 1 bluetooth ideapad_bluetooth unblocked unblocked 3 wlan phy0 unblocked unblocked 4 bluetooth hci0 unblocked unblocked -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818204 Title: Qualcomm Atheros QCA9377 wireless does not work Status in linux package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in network-manager source package in Bionic: Invalid Status in linux source package in Cosmic: Fix Committed Status in network-manager source package in Cosmic: Invalid Bug description: === SRU Justification === [Impact] Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked [Fix] The platform in question doesn't have hardware RF switch, so quirk it off. [Test] User confirm it fixes the issue. [Regression Potential] Minimal. This fix is limited to one specific platform. === Original Bug Report === I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). The menu shows that wireless is off. Turning on the wireless from the menu does not do anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.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: ubuntu:GNOME Date: Fri Mar 1 11:42:34 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 ada277fe-966d-33ff-aba2-8ba32d6ce5a9 ethernet 155143 pe 1. maaliskuuta 2019 11.42.13 yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enx00e04c704f68 activated /org/freedesktop/NetworkManager/ActiveConnection/11 -- virbr0 dc46fe89-5b22-438a-85d5-37be48a077ea bridge 155143 pe 1. maaliskuuta 2019 11.42.13 no 0 no/org/freedesktop/NetworkManager/Settings/2 yes virbr0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled disabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sami 1315 F pulseaudio /dev/snd/controlC0: sami 1315 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown MachineType: LENOVO 81H1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet splash vt.handoff=1
[Kernel-packages] [Bug 1823994] Re: not able to install linux-generic-hwe-18.04-edge/bionic-proposed
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823994 Title: arm64: not able to install linux-generic-hwe-18.04-edge/bionic- proposed Status in linux package in Ubuntu: New Bug description: 1. linux-generic-hwe-18.04-edge from bionic-updates is installed: `linux-generic-hwe-18.04-edge/bionic-updates,bionic-security,now 4.18.0.16.65 arm64 [installed]` ``` $ dpkg -l |grep linux-generic ii linux-generic-hwe-18.04-edge 4.18.0.16.65 arm64Complete Generic Linux kernel and headers ``` 2. enable -proposed archive and update: ``` $ sudo add-apt-repository "deb http://ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main restricted" $ sudo apt update ``` 3. shows it is upgradable: ``` $ apt search --names-only linux-generic linux-generic-hwe-18.04-edge/bionic-proposed 5.0.0.8.66 arm64 [upgradable from: 4.18.0.16.65] Complete Generic Linux kernel and headers ``` 4. try to install it, but: ``` $ sudo apt install linux-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge (= 5.0.0.8.66) but 4.18.0.16.65 is to be installed E: Unable to correct problems, you have held broken packages. ``` 5. same happens trying to install `linux-image-generic-hwe-18.04-edge`: ``` $ sudo apt install linux-image-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic-hwe-18.04-edge : Depends: linux-image-5.0.0-8-generic but it is not installable E: Unable to correct problems, you have held broken packages. ``` 6. also not able to install `linux-image-5.0.0-8-generic`: ``` $ sudo apt install linux-image-5.0.0-8-generic Reading package lists... Done Building dependency tree Reading state information... Done Package linux-image-5.0.0-8-generic is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-image-5.0.0-8-generic' has no installation candidate ``` more info: ~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 ~$ apt-cache policy linux-generic-hwe-18.04-edge linux-generic-hwe-18.04-edge: Installed: 4.18.0.16.65 Candidate: 5.0.0.8.66 Version table: 5.0.0.8.66 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 Packages *** 4.18.0.16.65 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823994] Re: not able to install linux-generic-hwe-18.04-edge/bionic-proposed
It appears that linux-signed-hwe-edge does not yet have the arm64 support we added to linux-signed. ** Summary changed: - not able to install linux-generic-hwe-18.04-edge/bionic-proposed + arm64: not able to install linux-generic-hwe-18.04-edge/bionic-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/1823994 Title: arm64: not able to install linux-generic-hwe-18.04-edge/bionic- proposed Status in linux package in Ubuntu: New Bug description: 1. linux-generic-hwe-18.04-edge from bionic-updates is installed: `linux-generic-hwe-18.04-edge/bionic-updates,bionic-security,now 4.18.0.16.65 arm64 [installed]` ``` $ dpkg -l |grep linux-generic ii linux-generic-hwe-18.04-edge 4.18.0.16.65 arm64Complete Generic Linux kernel and headers ``` 2. enable -proposed archive and update: ``` $ sudo add-apt-repository "deb http://ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main restricted" $ sudo apt update ``` 3. shows it is upgradable: ``` $ apt search --names-only linux-generic linux-generic-hwe-18.04-edge/bionic-proposed 5.0.0.8.66 arm64 [upgradable from: 4.18.0.16.65] Complete Generic Linux kernel and headers ``` 4. try to install it, but: ``` $ sudo apt install linux-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge (= 5.0.0.8.66) but 4.18.0.16.65 is to be installed E: Unable to correct problems, you have held broken packages. ``` 5. same happens trying to install `linux-image-generic-hwe-18.04-edge`: ``` $ sudo apt install linux-image-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic-hwe-18.04-edge : Depends: linux-image-5.0.0-8-generic but it is not installable E: Unable to correct problems, you have held broken packages. ``` 6. also not able to install `linux-image-5.0.0-8-generic`: ``` $ sudo apt install linux-image-5.0.0-8-generic Reading package lists... Done Building dependency tree Reading state information... Done Package linux-image-5.0.0-8-generic is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-image-5.0.0-8-generic' has no installation candidate ``` more info: ~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 ~$ apt-cache policy linux-generic-hwe-18.04-edge linux-generic-hwe-18.04-edge: Installed: 4.18.0.16.65 Candidate: 5.0.0.8.66 Version table: 5.0.0.8.66 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 Packages *** 4.18.0.16.65 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818204 Title: Qualcomm Atheros QCA9377 wireless does not work Status in linux package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in network-manager source package in Bionic: Invalid Status in linux source package in Cosmic: Fix Committed Status in network-manager source package in Cosmic: Invalid Bug description: === SRU Justification === [Impact] Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked [Fix] The platform in question doesn't have hardware RF switch, so quirk it off. [Test] User confirm it fixes the issue. [Regression Potential] Minimal. This fix is limited to one specific platform. === Original Bug Report === I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). The menu shows that wireless is off. Turning on the wireless from the menu does not do anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.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: ubuntu:GNOME Date: Fri Mar 1 11:42:34 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 ada277fe-966d-33ff-aba2-8ba32d6ce5a9 ethernet 155143 pe 1. maaliskuuta 2019 11.42.13 yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enx00e04c704f68 activated /org/freedesktop/NetworkManager/ActiveConnection/11 -- virbr0 dc46fe89-5b22-438a-85d5-37be48a077ea bridge 155143 pe 1. maaliskuuta 2019 11.42.13 no 0 no/org/freedesktop/NetworkManager/Settings/2 yes virbr0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled disabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sami 1315 F pulseaudio /dev/snd/controlC0: sami 1315 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown MachineType: LENOVO 81H1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ 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-sessi
[Kernel-packages] [Bug 1822832] Re: linux-aws: 4.4.0-1041.44 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid ** 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: 1822834 - phase: Ready for Packaging - phase-changed: Wednesday, 03. April 2019 09:34 UTC + phase: Packaging + phase-changed: Tuesday, 09. April 2019 17:10 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1822832 Title: linux-aws: 4.4.0-1041.44 -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-signing-to-proposed series: Invalid 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 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 -- kernel-stable-master-bug: 1822834 phase: Packaging phase-changed: Tuesday, 09. April 2019 17:10 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/1822832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803960] Re: 4.18.0 kernels hang system randomly
Continuing issues up to and including 5.0.0-8. Experienced three lock- ups today. I strongly suspect the iwlwifi device but as the lock up is total and silent there are zero clues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803960 Title: 4.18.0 kernels hang system randomly Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: I've been using 18.04 on an Asus T300CHI without issue until I decided to switch to the v4.18 kernels from 18.10 via linux-image-lowlatency- hwe-18.04-edge. Since then the system randomly but regularly completely hangs. Only a hard power-off resolves it. Frustratingly there are never any clues in the kernel logs so it is very difficult to point to anything that might cause it; there is never any obvious pattern in the workload, the user interaction, or state of the PC when the hang occurs. A week ago I switched to the Ubuntu mainline v4.19 builds and that resolved the issue. I was reminded of it again today when it hung a few minutes ago. After the reboot I checked the previous boot log and realised the PC had accidentally been booted with the default v4.18 kernel rather than v4.19. I don't think this report can be debugged but it is worth having a tracking bug in case other people experience the same issue with v4.18. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823994] 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 1823994 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823994 Title: arm64: not able to install linux-generic-hwe-18.04-edge/bionic- proposed Status in linux package in Ubuntu: Incomplete Bug description: 1. linux-generic-hwe-18.04-edge from bionic-updates is installed: `linux-generic-hwe-18.04-edge/bionic-updates,bionic-security,now 4.18.0.16.65 arm64 [installed]` ``` $ dpkg -l |grep linux-generic ii linux-generic-hwe-18.04-edge 4.18.0.16.65 arm64Complete Generic Linux kernel and headers ``` 2. enable -proposed archive and update: ``` $ sudo add-apt-repository "deb http://ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main restricted" $ sudo apt update ``` 3. shows it is upgradable: ``` $ apt search --names-only linux-generic linux-generic-hwe-18.04-edge/bionic-proposed 5.0.0.8.66 arm64 [upgradable from: 4.18.0.16.65] Complete Generic Linux kernel and headers ``` 4. try to install it, but: ``` $ sudo apt install linux-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge (= 5.0.0.8.66) but 4.18.0.16.65 is to be installed E: Unable to correct problems, you have held broken packages. ``` 5. same happens trying to install `linux-image-generic-hwe-18.04-edge`: ``` $ sudo apt install linux-image-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic-hwe-18.04-edge : Depends: linux-image-5.0.0-8-generic but it is not installable E: Unable to correct problems, you have held broken packages. ``` 6. also not able to install `linux-image-5.0.0-8-generic`: ``` $ sudo apt install linux-image-5.0.0-8-generic Reading package lists... Done Building dependency tree Reading state information... Done Package linux-image-5.0.0-8-generic is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-image-5.0.0-8-generic' has no installation candidate ``` more info: ~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 ~$ apt-cache policy linux-generic-hwe-18.04-edge linux-generic-hwe-18.04-edge: Installed: 4.18.0.16.65 Candidate: 5.0.0.8.66 Version table: 5.0.0.8.66 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 Packages *** 4.18.0.16.65 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822871] Re: enabling ftrace on Hi1620 CS causes an Oops
Does this fix the issue? https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?h =for-next/fixes&id=5a3ae7b314a2259b1188b22b392f5eba01e443ee -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822871 Title: enabling ftrace on Hi1620 CS causes an Oops Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Attempting to enable the function tracer causes an Oops. This impacts the current disco kernel, as well as latest upstream (@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539). This is 100% reproducible on D06 CS systems, but not reproducible on D06 ES systems (the previous silicon rev). [Test Case] $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325! [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure marvell aes_ce_blk aes_ce_cipher hibmc_drm hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce sha2_ce syscopyarea sha256_arm64 sysfillrect ixgbe igb sha1_ce hns3 sysimgblt usbhid fb_sys_fops hisi_sas_v3_hw hclge i2c_algo_bit xfrm_algo hisi_sas_main mdio hid drm hnae3 libsas ahci scsi_transport_sas hinic gpio_dwapb aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 3125.736544] CPU: 124 PID: 3306 Comm: tee Not tainted 5.0.0-rc4+ #12 [ 3125.742802] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS 2280-A CS V2.16.01 03/16/2019 [ 3125.752099] pstate: 0049 (nzcv daif +PAN -UAO) [ 3125.756893] pc : aarch64_insn_adrp_get_offset+0x34/0x38 [ 3125.762111] lr : plt_entries_equal.part.3+0x40/0x80 [ 3125.766979] sp : 2837b9f0 [ 3125.770286] x29: 2837b9f0 x28: bef4fd20d880 [ 3125.775591] x27: x26: [ 3125.780896] x25: dea2a7e8 x24: 3dceb8413000 [ 3125.786200] x23: 0002 x22: 3dce9d2289a4 [ 3125.791504] x21: 2837ba8c x20: 2837b000 [ 3125.796808] x19: 3dce9d228000 x18: [ 3125.802112] x17: x16: 3dceb7742780 [ 3125.807416] x15: 3dceb7ce7c38 x14: 0001 [ 3125.812720] x13: bef50bb9e188 x12: [ 3125.818023] x11: 7efba3e79608 x10: 0a70 [ 3125.823327] x9 : 3dceb6deeacc x8 : [ 3125.828631] x7 : 0005 x6 : 3dceb8413f10 [ 3125.833935] x5 : 002b3000 x4 : 3dceb6f4f4b8 [ 3125.839239] x3 : x2 : 9000 [ 3125.844543] x1 : x0 : [ 3125.849850] Process tee (pid: 3306, stack limit = 0x262bb476) [ 3125.856281] Call trace: [ 3125.858723] aarch64_insn_adrp_get_offset+0x34/0x38 [ 3125.863593] plt_entries_equal.part.3+0x40/0x80 [ 3125.868115] plt_entries_equal+0x5c/0x70 [ 3125.872031] ftrace_make_call+0xf0/0x150 [ 3125.875950] __ftrace_replace_code+0xe8/0xf8 [ 3125.880212] ftrace_replace_code+0x64/0xc0 [ 3125.884301] ftrace_modify_all_code+0xb0/0x148 [ 3125.888738] arch_ftrace_update_code+0x10/0x18 [ 3125.893174] ftrace_run_update_code+0x20/0x70 [ 3125.897524] ftrace_startup_enable+0x4c/0x58 [ 3125.901788] ftrace_startup+0xa4/0x140 [ 3125.905531] register_ftrace_function+0x64/0x80 [ 3125.910059] function_trace_init+0x50/0x98 [ 3125.914149] tracing_set_tracer+0xf4/0x1c0 [ 3125.918238] tracing_set_trace_write+0x10c/0x168 [ 3125.922852] __vfs_write+0x60/0x1a8 [ 3125.926333] vfs_write+0xac/0x1b8 [ 3125.929641] ksys_write+0x6c/0xd8 [ 3125.932949] __arm64_sys_write+0x24/0x30 [ 3125.936866] el0_svc_common+0x78/0x120 [ 3125.940608] el0_svc_handler+0x38/0x78 [ 3125.944349] el0_svc+0x8/0xc [ 3125.947224] Code: 97fffb33 53144c00 a8c17bfd d65f03c0 (d421) [ 3125.953312] ---[ end trace 0872d3e5933385e2 ]--- [Fix] TBD [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily
The HP Elitebook 840 G1 is a regular laptop, so the accelerometer is not frequently used. Even when it's functioning properly like in 18.04, it can accidentally rotate 90 degrees when you tilt it slightly. You would never use this unit tilted 90 degrees or upside down, so if it's possible to entirely disable screen rotation on this model it would be preferable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821641 Title: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily Status in linux package in Ubuntu: Confirmed Bug description: On the 19.04 daily image (2019-03-24), the screen on my laptop is completely upside down, from the moment the GUI loads. This does not happen on 18.04 and 18.10. It appears to be an accelerometer issue since holding the laptop upside down flips the image to its correct orientation - basically the functionality of the accelerometer is suddenly inverted. Please contact me if you want me to help testing the issue on my hardware. Thanks! --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sharper1380 F pulseaudio /dev/snd/controlC1: sharper1380 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-30 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190330) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=1e4bdc5f-0616-42f3-8da2-4ec27df3fc55 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.44 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: 5CG4430MGN dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.44:bd04/12/2018:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.sku: D1F44AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
