[Kernel-packages] [Bug 1745927] Comment bridged from LTC Bugzilla
--- Comment From hasri...@in.ibm.com 2018-03-16 02:47 EDT--- With the proposed installer, the Chelsio card can be seen in the installer. ? Primary network interface: ? ? ? ? enP1p3s0f4: Chelsio Communications Inc T422-CR Unified Wire Ether ? ? enP1p3s0f4d1: Chelsio Communications Inc T422-CR Unified Wire Eth ? ? enP1p3s0f4d2: Chelsio Communications Inc T422-CR Unified Wire Eth ? ? enP1p3s0f4d3: Chelsio Communications Inc T422-CR Unified Wire Eth ? Once the patches are in mainline, this bug can be marked as resolved. Thanks, Harish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745927 Title: Driver not found in Ubuntu kernel does not detect interface Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Bug description: == Comment: #0 - Harish Sriram --Problem Description--- kernel does not detect interface in Ubuntu, driver missing in kernel Contact Information = hasri...@in.ibm.com ---Issue observed--- While installing Ubuntu on a machine with Chelsio card, ubuntu-installer fails to show the interface name - probable cause would be due to missing driver in Ubuntu kernel. Machine Type = Tuleta/Power 8 BML Additional Info- Installer Shell --- BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ # ip a 1: lo: mtu 65536 qdisc noop qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enP5p9s0f0: mtu 1500 qdisc mq qlen 1000 link/ether 98:be:94:02:09:7c brd ff:ff:ff:ff:ff:ff 3: enP5p9s0f1: mtu 1500 qdisc mq qlen 1000 link/ether 98:be:94:02:09:7d brd ff:ff:ff:ff:ff:ff 4: enP5p9s0f2: mtu 1500 qdisc mq qlen 1000 link/ether 98:be:94:02:09:7e brd ff:ff:ff:ff:ff:ff 5: enP5p9s0f3: mtu 1500 qdisc mq qlen 1000 link/ether 98:be:94:02:09:7f brd ff:ff:ff:ff:ff:ff ~ # lspci -k :00:00.0 PCI bridge: IBM Device 03dc 0001:00:00.0 PCI bridge: IBM Device 03dc 0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:03:00.0 Ethernet controller: Chelsio Communications Inc T422-CR Unified Wire Ethernet Controller Subsystem: IBM Device 03e5 0001:03:00.1 Ethernet controller: Chelsio Communications Inc T422-CR Unified Wire Ethernet Controller Subsystem: IBM Device 03e5 0001:03:00.2 Ethernet controller: Chelsio Communications Inc Device 4102 Subsystem: IBM Device 03e5 0001:03:00.3 Ethernet controller: Chelsio Communications Inc Device 4102 Subsystem: IBM Device 03e5 0001:03:00.4 Ethernet controller: Chelsio Communications Inc T422-CR Unified Wire Ethernet Controller Subsystem: IBM Device 03e5 0001:03:00.5 SCSI storage controller: Chelsio Communications Inc T422-CR Unified Wire Storage Controller Subsystem: IBM Device 03e5 0001:03:00.6 Fibre Channel: Chelsio Communications Inc T422-CR Unified Wire Storage Controller Subsystem: IBM Device 03e5 0001:03:00.7 Ethernet controller: Chelsio Communications Inc Device Subsystem: IBM Device 03e5 0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 02) Subsystem: IBM Device 03ff 0004:00:00.0 PCI bridge: IBM Device 03dc 0004:01:00.0 PCI bridge: Integrated Device Technology, Inc. [IDT] PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02) 0004:02:02.0 PCI bridge: Integrated Device Technology, Inc. [IDT] PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02) 0004:02:03.0 PCI bridge: Integrated Device Technology, Inc. [IDT] PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02) 0004:03:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: IBM Device 041e 0004:03:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: IBM Device 041e 0004:04:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: IBM Device 041e 0004:04:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: IBM Device 041e 0005:00:00.0 PCI bridge: IBM Device 03dc 0005:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12
[Kernel-packages] [Bug 1756254] Re: Ubuntu18.04[P9 DD2.2 Boston]:Unable to boot power8 compat mode guests(ubuntu14.04.5) (kvm)
** Changed in: ubuntu-power-systems Importance: High => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756254 Title: Ubuntu18.04[P9 DD2.2 Boston]:Unable to boot power8 compat mode guests(ubuntu14.04.5) (kvm) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Praveen K. Pandey - 2018-03-15 03:18:46 == Problem Description : As Ubuntu18.04 as KVM Host installation of ubuntu ubuntu14.04.5 kvm guest is hung to so not able to install using virt-install command Reproducible Step: 1- Install ubuntu18.04 on Boston DD2.2 2- Configure system as KVM host 3- get ubuntu-14.04.5-server-ppc64el iso 4- start installation using virt-install using ubuntu-14.04.5 iso LOG: OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-007) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #50~14.04.1-Ubuntu SMP Wed Jul 13 01:03:56 UTC 2016 (Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13) Detected machine type: 0101 Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... - it hung here -- root@system :/var/lib/libvirt/images/praveen# uname -a Linux system4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:37:03 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@lsystem:/var/lib/libvirt/images/praveen# root@system:/var/lib/libvirt/images/praveen# qemu-img create -f qcow2 pra-ubuntu14.qcow2 30G Formatting 'pra-ubuntu14.qcow2', fmt=qcow2 size=32212254720 cluster_size=65536 lazy_refcounts=off refcount_bits=16 root@system:/var/lib/libvirt/images/praveen# virt-install --name PRA-1404.5_vm1 --ram 2048 --disk path=/var/lib/libvirt/images/praveen/pra-ubuntu14.qcow2 --vcpus 4 --os-type linux --os-variant generic --network bridge=virbr0 --graphics none --console pty,target_type=serial --cdrom /var/lib/libvirt/images/isos/ubuntu-14.04.5-server-ppc64el.iso WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. See the man page for examples of using --location with CDROM media Starting install... Connected to domain PRA-1404.5_vm1 Escape character is ^] Populating /vdevice methods Populating /vdevice/vty@3000 Populating /vdevice/nvram@7100 Populating /pci@8002000 00 0800 (D) : 1af4 1000virtio [ net ] 00 1000 (D) : 1af4 1004virtio [ scsi ] Populating /pci@8002000/scsi@2 SCSI: Looking for devices 100 CD-ROM : "QEMU QEMU CD-ROM 2.5+" 00 1800 (D) : 1b36 000dserial bus [ usb-xhci ] 00 2000 (D) : 1af4 1001virtio [ block ] 00 2800 (D) : 1af4 1002unknown-legacy-device* No NVRAM common partition, re-initializing... Scanning USB XHCI: Initializing Using default console: /vdevice/vty@3000 Welcome to Open Firmware Copyright (c) 2004, 2017 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@2/disk@100 ... Successfully loaded GNU GRUB version 2.02~beta2-9ubuntu1.11 |*Install | Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-007) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #50~14.04.1-Ubuntu SMP Wed Jul 13 01:03:56 UTC 2016 (Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13) Detected machine type: 0101 Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... Regards Praveen == Comment: #1 - Harish Sriram - 2018-03
[Kernel-packages] [Bug 1745927] Re: Driver not found in Ubuntu kernel does not detect interface
** Changed in: ubuntu-power-systems Assignee: Canonical Kernel Team (canonical-kernel-team) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745927 Title: Driver not found in Ubuntu kernel does not detect interface Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Bug description: == Comment: #0 - Harish Sriram --Problem Description--- kernel does not detect interface in Ubuntu, driver missing in kernel Contact Information = hasri...@in.ibm.com ---Issue observed--- While installing Ubuntu on a machine with Chelsio card, ubuntu-installer fails to show the interface name - probable cause would be due to missing driver in Ubuntu kernel. Machine Type = Tuleta/Power 8 BML Additional Info- Installer Shell --- BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ # ip a 1: lo: mtu 65536 qdisc noop qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enP5p9s0f0: mtu 1500 qdisc mq qlen 1000 link/ether 98:be:94:02:09:7c brd ff:ff:ff:ff:ff:ff 3: enP5p9s0f1: mtu 1500 qdisc mq qlen 1000 link/ether 98:be:94:02:09:7d brd ff:ff:ff:ff:ff:ff 4: enP5p9s0f2: mtu 1500 qdisc mq qlen 1000 link/ether 98:be:94:02:09:7e brd ff:ff:ff:ff:ff:ff 5: enP5p9s0f3: mtu 1500 qdisc mq qlen 1000 link/ether 98:be:94:02:09:7f brd ff:ff:ff:ff:ff:ff ~ # lspci -k :00:00.0 PCI bridge: IBM Device 03dc 0001:00:00.0 PCI bridge: IBM Device 03dc 0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:03:00.0 Ethernet controller: Chelsio Communications Inc T422-CR Unified Wire Ethernet Controller Subsystem: IBM Device 03e5 0001:03:00.1 Ethernet controller: Chelsio Communications Inc T422-CR Unified Wire Ethernet Controller Subsystem: IBM Device 03e5 0001:03:00.2 Ethernet controller: Chelsio Communications Inc Device 4102 Subsystem: IBM Device 03e5 0001:03:00.3 Ethernet controller: Chelsio Communications Inc Device 4102 Subsystem: IBM Device 03e5 0001:03:00.4 Ethernet controller: Chelsio Communications Inc T422-CR Unified Wire Ethernet Controller Subsystem: IBM Device 03e5 0001:03:00.5 SCSI storage controller: Chelsio Communications Inc T422-CR Unified Wire Storage Controller Subsystem: IBM Device 03e5 0001:03:00.6 Fibre Channel: Chelsio Communications Inc T422-CR Unified Wire Storage Controller Subsystem: IBM Device 03e5 0001:03:00.7 Ethernet controller: Chelsio Communications Inc Device Subsystem: IBM Device 03e5 0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 02) Subsystem: IBM Device 03ff 0004:00:00.0 PCI bridge: IBM Device 03dc 0004:01:00.0 PCI bridge: Integrated Device Technology, Inc. [IDT] PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02) 0004:02:02.0 PCI bridge: Integrated Device Technology, Inc. [IDT] PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02) 0004:02:03.0 PCI bridge: Integrated Device Technology, Inc. [IDT] PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02) 0004:03:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: IBM Device 041e 0004:03:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: IBM Device 041e 0004:04:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: IBM Device 041e 0004:04:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: IBM Device 041e 0005:00:00.0 PCI bridge: IBM Device 03dc 0005:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca) 0005:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca) 0005:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca) 0005:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca) 0005:02:10.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane,
[Kernel-packages] [Bug 1755509] Re: Xenial update to 4.4.115 stable release
Skipped the following patches (previously applied already): * bpf: fix branch pruning logic * loop: fix concurrent lo_open/lo_release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755509 Title: Xenial update to 4.4.115 stable release Status in linux package in Ubuntu: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.115 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.115 stable release shall be applied: * loop: fix concurrent lo_open/lo_release * bpf: fix branch pruning logic * x86: bpf_jit: small optimization in emit_bpf_tail_call() * bpf: fix bpf_tail_call() x64 JIT * bpf: introduce BPF_JIT_ALWAYS_ON config * bpf: arsh is not supported in 32 bit alu thus reject it * bpf: avoid false sharing of map refcount with max_entries * bpf: fix divides by zero * bpf: fix 32-bit divide by zero * bpf: reject stores into ctx via st and xadd * x86/pti: Make unpoison of pgd for trusted boot work for real * kaiser: fix intel_bts perf crashes * ALSA: seq: Make ioctls race-free * crypto: aesni - handle zero length dst buffer * crypto: af_alg - whitelist mask and type * power: reset: zx-reboot: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE * gpio: iop: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE * gpio: ath79: add missing MODULE_DESCRIPTION/LICENSE * mtd: nand: denali_pci: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE * igb: Free IRQs when device is hotplugged * KVM: x86: emulator: Return to user-mode on L1 CPL=0 emulation failure * KVM: x86: Don't re-execute instruction when not passing CR2 value * KVM: X86: Fix operand/address-size during instruction decoding * KVM: x86: ioapic: Fix level-triggered EOI and IOAPIC reconfigure race * KVM: x86: ioapic: Clear Remote IRR when entry is switched to edge-triggered * KVM: x86: ioapic: Preserve read-only values in the redirection table * ACPI / bus: Leave modalias empty for devices which are not present * cpufreq: Add Loongson machine dependencies * bcache: check return value of register_shrinker * drm/amdgpu: Fix SDMA load/unload sequence on HWS disabled mode * drm/amdkfd: Fix SDMA ring buffer size calculation * drm/amdkfd: Fix SDMA oversubsription handling * openvswitch: fix the incorrect flow action alloc size * mac80211: fix the update of path metric for RANN frame * btrfs: fix deadlock when writing out space cache * KVM: VMX: Fix rflags cache during vCPU reset * xen-netfront: remove warning when unloading module * nfsd: CLOSE SHOULD return the invalid special stateid for NFSv4.x (x>0) * nfsd: Ensure we check stateid validity in the seqid operation checks * grace: replace BUG_ON by WARN_ONCE in exit_net hook * nfsd: check for use of the closed special stateid * lockd: fix "list_add double add" caused by legacy signal interface * hwmon: (pmbus) Use 64bit math for DIRECT format values * net: ethernet: xilinx: Mark XILINX_LL_TEMAC broken on 64-bit * quota: Check for register_shrinker() failure. * SUNRPC: Allow connect to return EHOSTUNREACH * kmemleak: add scheduling point to kmemleak_scan() * drm/omap: Fix error handling path in 'omap_dmm_probe()' * xfs: ubsan fixes * scsi: aacraid: Prevent crash in case of free interrupt during scsi EH path * scsi: ufs: ufshcd: fix potential NULL pointer dereference in ufshcd_config_vreg * media: usbtv: add a new usbid * usb: gadget: don't dereference g until after it has been null checked * staging: rtl8188eu: Fix incorrect response to SIOCGIWESSID * usb: option: Add support for FS040U modem * USB: serial: pl2303: new device id for Chilitag * USB: cdc-acm: Do not log urb submission errors on disconnect * CDC-ACM: apply quirk for card reader * USB: serial: io_edgeport: fix possible sleep-in-atomic * usbip: prevent bind loops on devices attached to vhci_hcd * usbip: list: don't list devices attached to vhci_hcd * USB: serial: simple: add Motorola Tetra driver * usb: f_fs: Prevent gadget unbind if it is already unbound * usb: uas: unconditionally bring back host after reset * selinux: general protection fault in sock_has_perm * serial: imx: Only wakeup via RTSDEN bit if the system has RTS/CTS * spi: imx: do n
[Kernel-packages] [Bug 1755228] Re: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker
** Summary changed: - linux-lts-trusty: -proposed tracker + linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1755228 Title: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755227 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 997605] Re: Disabling IPv6 autoconfiguration in sysctl.conf doesn't affect boot process
Still affect Xenial here too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/997605 Title: Disabling IPv6 autoconfiguration in sysctl.conf doesn't affect boot process Status in linux package in Ubuntu: Confirmed Bug description: When you put the following lines in sysctl.conf net.ipv6.conf.all.autoconf = 0 net.ipv6.conf.all.accept_ra = 0 the expeced result is to disable IPv6 autoconfiguration at bootup, but, actually, it does nothing, because sysctl.conf network settings are applied after network has been started. So what happens: 1. Network interfaces are started by /etc/init.d/networking 1a. IPv6 uses autocnfiguratin, because it is enabled at this point 2. Sysctl.conf settings are applied by /etc/init/procps.conf I don't know if there is an easy solution, because inverting order things are called could break something else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/997605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755228] Re: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755227 phase: Packaging + kernel-stable-phase-changed:Friday, 16. March 2018 09:32 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755227 - phase: Packaging - kernel-stable-phase-changed:Friday, 16. March 2018 09:32 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1755228 Title: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755227 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
The new build of v4.12-rc3 is a good build (2 of 151). 4.12.0-041200rc3-generic #201803151851 v4.12-rc3 - bad (24 of 90 - 26.6%) http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc3/ v4.12-rc3 - relatively good (2 of 151 - 1.3%) http://kernel.ubuntu.com/~jsalisbury/lp1753662/v4.12-rc3/ So what is the difference between those two? build config? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
** Attachment added: "bond_check_xenial_4.12.0-041200rc3-generic_201803151851.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5081137/+files/bond_check_xenial_4.12.0-041200rc3-generic_201803151851.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756311] [NEW] fstrim and discard operations take too long to complete
Public bug reported: 1-) Ubuntu Release : Ubuntu 14.04.5 LTS 2-) linux-image-3.13.0-143-generic and linux-image-4.4.0-1014-aws 3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should not take more than some seconds to complete. 4-) Formating the raid0 array with xfs took around 2 hours. Running fstrim -v on the mount point mounted on top of the raid array took around 2 hours. How to reproduce the issue: - Launch an i3.4xlarge instance on Amazon AWS using an Ubuntu 14.04.5 AMI ( ami-78d2be01 on EU-WEST-1 ), this will generate an instance with one 8Gb EBS root volume and two 1.9T SSD drives that are presented to the instance using the nvme driver. - Compose a raid0 array with the following command : # mdadm --create --verbose --level=0 /dev/md0 --raid-devices=2 /dev/nvme0n1 /dev/nvme1n1 - When trying to format the raid0 array ( /dev/md0 ) using xfs it takes around 2 hours to complete. I tried other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. root@ip-172-31-30-133:~# time mkfs.xfs /dev/md0 real120m45.725s user0m0.000s sys 0m18.248s - Running fstrim -v on a filesystem mounted on top of /dev/md0 can take around 2 hours to complete. With other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. - When I try the same with any of the nvme SSD devices alone, let's say /dev/nvme0n1, the issue doesn't happen. - I tried to replicate this issue using LVM and striping, fstrim and mkfs.xfs, the tasks complete without taking hours : root@ip-172-31-27-69:~# pvcreate /dev/nvme0n1 Physical volume "/dev/nvme0n1" successfully created root@ip-172-31-27-69:~# pvcreate /dev/nvme1n1 Physical volume "/dev/nvme1n1" successfully created root@ip-172-31-27-69:~# vgcreate raid0 /dev/nvme0n1 /dev/nvme1n1 Volume group "raid0" successfully created root@ip-172-31-27-69:~# lvcreate --type striped --stripes 2 --extents 100%FREE raid0 /dev/nvme0n1 /dev/nvme1n1 Using default stripesize 64.00 KiB. Logical volume "lvol0" created. root@ip-172-31-27-69:~# vgchange -ay 1 logical volume(s) in volume group "raid0" now active root@ip-172-31-27-69:~# lvchange -ay /dev/raid0/lvol0 root@ip-172-31-27-69:~# lvs -a /dev/raid0/lvol0 LVVGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol0 raid0 -wi-a- 3.46t htop root@ip-172-31-27-69:~# time mkfs.xfs /dev/raid0/lvol0 meta-data=/dev/raid0/lvol0 isize=512agcount=32, agsize=28991664 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0 data = bsize=4096 blocks=927733248, imaxpct=5 = sunit=16 swidth=32 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=453008, version=2 = sectsz=512 sunit=16 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 real0m2.926s user0m0.180s sys 0m0.000s root@ip-172-31-27-69:~# mount /dev/raid0/lvol0 /mnt root@ip-172-31-27-69:~# time fstrim -v /mnt /mnt: 3.5 TiB (3798138650624 bytes) trimmed real0m1.794s user0m0.000s sys 0m0.000s So the issue only happens when using nvme and md to compose the raid0 array. Bellow follows some information that may be useful: started formating the md array with mkfs.xfs. Process looks hanged. root@ip-172-31-24-66:~# ps aux | grep -i mkfs.xfs root 1693 12.0 0.0 12728 968 pts/1D+ 07:54 0:03 mkfs.xfs /dev/md0 PID 1693 is in uninterruptible sleep ( D ) Looking at /proc/7965/stack root@ip-172-31-24-66:~# cat /proc/1693/stack [] blkdev_issue_discard+0x232/0x2a0 [] blkdev_ioctl+0x61d/0x7d0 [] block_ioctl+0x41/0x50 [] do_vfs_ioctl+0x2e3/0x4d0 [] SyS_ioctl+0x81/0xa0 [] system_call_fastpath+0x1a/0x1f [] 0x Looking at the stack, looks like it's hanged on a discard operation root@ip-172-31-24-66:~# ps -flp 1693 F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 D root 1693 1682 2 80 0 - 3182 blkdev 07:54 pts/100:00:03 mkfs.xfs /dev/md0 root@ip-172-31-24-66:~# cat /proc/1693/wchan blkdev_issue_discard Process stuck with function --> blkdev_issue_discard ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- 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/1756311 Title: fstrim and discard operations take too long to complete Status in linux-aws package in Ubuntu: New Bug description: 1-) Ubuntu Release : Ubuntu 14.04.5 LTS 2-) linux-image-3.13.0-143-generic and linux-image-4.4.0-1014-aws 3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should not take more than some seconds to complete. 4-) Formating the raid0 array w
[Kernel-packages] [Bug 1755268] [NEW] Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled)
You have been subscribed to a public bug: # System information # # uname -a Linux m5c37 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.4 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.4 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial # ethtool -i eno1 driver: mlx4_en version: 4.3-1.0.1 firmware-version: 2.42.5004 expansion-rom-version: bus-info: :11:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes # ethtool -i bond0 driver: bonding version: 3.7.1 firmware-version: 2 expansion-rom-version: bus-info: supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no # ethtool -i vmbr0 driver: bridge version: 2.3 firmware-version: N/A expansion-rom-version: bus-info: N/A supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no Mellanox driver was installed from http://content.mellanox.com/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_LINUX-4.3-1.0.1.0-ubuntu16.04-x86_64.tgz ./mlnxofedinstall --kernel 4.13.0-36-generic --without-dkms --add- kernel-support # Steps for reproduce # This is my /etc/network/interfaces file: auto lo iface lo inet loopback auto openibd iface openibd inet manual pre-up /etc/init.d/openibd start pre-down /etc/init.d/openibd force-stop auto bond0 iface bond0 inet manual pre-up ip link add bond0 type bond || true pre-up ip link set bond0 down pre-up ip link set bond0 type bond mode active-backup arp_interval 2000 arp_ip_target 10.36.0.1 arp_validate 3 primary eno1 pre-up ip link set eno1 down pre-up ip link set eno1d1 down pre-up ip link set eno1 master bond0 pre-up ip link set eno1d1 master bond0 pre-up ip link set bond0 up pre-down ip link del bond0 auto vmbr0 iface vmbr0 inet static address 10.36.128.217 netmask 255.255.0.0 gateway 10.36.0.1 bridge_ports bond0 bridge_stp off bridge_fd 0 I execute these commands: wget http://dl-cdn.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-virt-3.7.0-x86_64.iso -O alpine.iso qemu-system-x86_64 -boot d -cdrom alpine.iso -m 512 -nographic -device e1000,netdev=net0 -netdev tap,id=net0 And after few moments I have hang kernel, and theese messages in console: [74390.187908] mlx4_core :11:00.0: bond for multifunction failed [74390.486476] mlx4_en: eno1d1: Fail to bond device [74390.750758] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 [74391.152326] general protection fault: [#1] SMP PTI [74391.410424] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 kernel trace log in attachment ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Mar 12 19:59:16 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) https://bugs.launchpad.net/bugs/1755268 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 1755268] Re: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled)
** Attachment added: "Dmesg output (before kernel panic)" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1755268/+attachment/5081272/+files/dmesg.txt ** 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/1755268 Title: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) Status in linux package in Ubuntu: Confirmed Bug description: # System information # # uname -a Linux m5c37 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.4 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.4 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial # ethtool -i eno1 driver: mlx4_en version: 4.3-1.0.1 firmware-version: 2.42.5004 expansion-rom-version: bus-info: :11:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes # ethtool -i bond0 driver: bonding version: 3.7.1 firmware-version: 2 expansion-rom-version: bus-info: supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no # ethtool -i vmbr0 driver: bridge version: 2.3 firmware-version: N/A expansion-rom-version: bus-info: N/A supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no Mellanox driver was installed from http://content.mellanox.com/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_LINUX-4.3-1.0.1.0-ubuntu16.04-x86_64.tgz ./mlnxofedinstall --kernel 4.13.0-36-generic --without-dkms --add- kernel-support # Steps for reproduce # This is my /etc/network/interfaces file: auto lo iface lo inet loopback auto openibd iface openibd inet manual pre-up /etc/init.d/openibd start pre-down /etc/init.d/openibd force-stop auto bond0 iface bond0 inet manual pre-up ip link add bond0 type bond || true pre-up ip link set bond0 down pre-up ip link set bond0 type bond mode active-backup arp_interval 2000 arp_ip_target 10.36.0.1 arp_validate 3 primary eno1 pre-up ip link set eno1 down pre-up ip link set eno1d1 down pre-up ip link set eno1 master bond0 pre-up ip link set eno1d1 master bond0 pre-up ip link set bond0 up pre-down ip link del bond0 auto vmbr0 iface vmbr0 inet static address 10.36.128.217 netmask 255.255.0.0 gateway 10.36.0.1 bridge_ports bond0 bridge_stp off bridge_fd 0 I execute these commands: wget http://dl-cdn.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-virt-3.7.0-x86_64.iso -O alpine.iso qemu-system-x86_64 -boot d -cdrom alpine.iso -m 512 -nographic -device e1000,netdev=net0 -netdev tap,id=net0 And after few moments I have hang kernel, and theese messages in console: [74390.187908] mlx4_core :11:00.0: bond for multifunction failed [74390.486476] mlx4_en: eno1d1: Fail to bond device [74390.750758] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 [74391.152326] general protection fault: [#1] SMP PTI [74391.410424] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 kernel trace log in attachment ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Mar 12 19:59:16 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756315] [NEW] fstrim and discard operations take too long to complete - Ubuntu 16.04
Public bug reported: 1-) Ubuntu Release : Ubuntu 16.04 LTS 2-) linux-image-4.4.0.1052.54-aws 3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should not take more than some seconds to complete. 4-) Formating the raid0 array with xfs took around 2 hours. Running fstrim -v on the mount point mounted on top of the raid array took around 2 hours. How to reproduce the issue: - Launch an i3.4xlarge instance on Amazon AWS using an Ubuntu 16.04 AMI ( ami-78d2be01 on EU-WEST-1 ), this will generate an instance with one 8Gb EBS root volume and two 1.9T SSD drives that are presented to the instance using the nvme driver. - Compose a raid0 array with the following command : # mdadm --create --verbose --level=0 /dev/md0 --raid-devices=2 /dev/nvme0n1 /dev/nvme1n1 - When trying to format the raid0 array ( /dev/md0 ) using xfs it takes around 2 hours to complete. I tried other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. root@ip-172-31-30-133:~# time mkfs.xfs /dev/md0 real120m45.725s user0m0.000s sys 0m18.248s - Running fstrim -v on a filesystem mounted on top of /dev/md0 can take around 2 hours to complete. With other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. - When I try the same with any of the nvme SSD devices alone, let's say /dev/nvme0n1, the issue doesn't happen. - I tried to replicate this issue using LVM and striping, fstrim and mkfs.xfs, the tasks complete without taking hours : root@ip-172-31-27-69:~# pvcreate /dev/nvme0n1 Physical volume "/dev/nvme0n1" successfully created root@ip-172-31-27-69:~# pvcreate /dev/nvme1n1 Physical volume "/dev/nvme1n1" successfully created root@ip-172-31-27-69:~# vgcreate raid0 /dev/nvme0n1 /dev/nvme1n1 Volume group "raid0" successfully created root@ip-172-31-27-69:~# lvcreate --type striped --stripes 2 --extents 100%FREE raid0 /dev/nvme0n1 /dev/nvme1n1 Using default stripesize 64.00 KiB. Logical volume "lvol0" created. root@ip-172-31-27-69:~# vgchange -ay 1 logical volume(s) in volume group "raid0" now active root@ip-172-31-27-69:~# lvchange -ay /dev/raid0/lvol0 root@ip-172-31-27-69:~# lvs -a /dev/raid0/lvol0 LVVGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol0 raid0 -wi-a- 3.46t htop root@ip-172-31-27-69:~# time mkfs.xfs /dev/raid0/lvol0 meta-data=/dev/raid0/lvol0 isize=512agcount=32, agsize=28991664 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0 data = bsize=4096 blocks=927733248, imaxpct=5 = sunit=16 swidth=32 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=453008, version=2 = sectsz=512 sunit=16 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 real0m2.926s user0m0.180s sys 0m0.000s root@ip-172-31-27-69:~# mount /dev/raid0/lvol0 /mnt root@ip-172-31-27-69:~# time fstrim -v /mnt /mnt: 3.5 TiB (3798138650624 bytes) trimmed real0m1.794s user0m0.000s sys 0m0.000s So the issue only happens when using nvme and md to compose the raid0 array. Bellow follows some information that may be useful: started formating the md array with mkfs.xfs. Process looks hanged. root@ip-172-31-24-66:~# ps aux | grep -i mkfs.xfs root 1693 12.0 0.0 12728 968 pts/1D+ 07:54 0:03 mkfs.xfs /dev/md0 PID 1693 is in uninterruptible sleep ( D ) Looking at /proc/7965/stack root@ip-172-31-24-66:~# cat /proc/1693/stack [] blkdev_issue_discard+0x232/0x2a0 [] blkdev_ioctl+0x61d/0x7d0 [] block_ioctl+0x41/0x50 [] do_vfs_ioctl+0x2e3/0x4d0 [] SyS_ioctl+0x81/0xa0 [] system_call_fastpath+0x1a/0x1f [] 0x Looking at the stack, looks like it's hanged on a discard operation root@ip-172-31-24-66:~# ps -flp 1693 F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 D root 1693 1682 2 80 0 - 3182 blkdev 07:54 pts/100:00:03 mkfs.xfs /dev/md0 root@ip-172-31-24-66:~# cat /proc/1693/wchan blkdev_issue_discard Process stuck with function --> blkdev_issue_discard ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Tags: aws discard fstrim mkfs.xfs trim -- 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/1756315 Title: fstrim and discard operations take too long to complete - Ubuntu 16.04 Status in linux-aws package in Ubuntu: New Bug description: 1-) Ubuntu Release : Ubuntu 16.04 LTS 2-) linux-image-4.4.0.1052.54-aws 3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should not take more than some seconds to complete. 4-) Formating the raid0 array with xfs too
[Kernel-packages] [Bug 1755268] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755268 Title: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) Status in linux package in Ubuntu: Confirmed Bug description: # System information # # uname -a Linux m5c37 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.4 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.4 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial # ethtool -i eno1 driver: mlx4_en version: 4.3-1.0.1 firmware-version: 2.42.5004 expansion-rom-version: bus-info: :11:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes # ethtool -i bond0 driver: bonding version: 3.7.1 firmware-version: 2 expansion-rom-version: bus-info: supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no # ethtool -i vmbr0 driver: bridge version: 2.3 firmware-version: N/A expansion-rom-version: bus-info: N/A supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no Mellanox driver was installed from http://content.mellanox.com/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_LINUX-4.3-1.0.1.0-ubuntu16.04-x86_64.tgz ./mlnxofedinstall --kernel 4.13.0-36-generic --without-dkms --add- kernel-support # Steps for reproduce # This is my /etc/network/interfaces file: auto lo iface lo inet loopback auto openibd iface openibd inet manual pre-up /etc/init.d/openibd start pre-down /etc/init.d/openibd force-stop auto bond0 iface bond0 inet manual pre-up ip link add bond0 type bond || true pre-up ip link set bond0 down pre-up ip link set bond0 type bond mode active-backup arp_interval 2000 arp_ip_target 10.36.0.1 arp_validate 3 primary eno1 pre-up ip link set eno1 down pre-up ip link set eno1d1 down pre-up ip link set eno1 master bond0 pre-up ip link set eno1d1 master bond0 pre-up ip link set bond0 up pre-down ip link del bond0 auto vmbr0 iface vmbr0 inet static address 10.36.128.217 netmask 255.255.0.0 gateway 10.36.0.1 bridge_ports bond0 bridge_stp off bridge_fd 0 I execute these commands: wget http://dl-cdn.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-virt-3.7.0-x86_64.iso -O alpine.iso qemu-system-x86_64 -boot d -cdrom alpine.iso -m 512 -nographic -device e1000,netdev=net0 -netdev tap,id=net0 And after few moments I have hang kernel, and theese messages in console: [74390.187908] mlx4_core :11:00.0: bond for multifunction failed [74390.486476] mlx4_en: eno1d1: Fail to bond device [74390.750758] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 [74391.152326] general protection fault: [#1] SMP PTI [74391.410424] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 kernel trace log in attachment ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Mar 12 19:59:16 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1755941] Re: No HDMI audio after suspend
It did start happening directly after the upgrade to Kernel 4.13.0-37. Thanks, Isaac On Thu, Mar 15, 2018 at 3:05 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.16 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4 > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1755941 > > Title: > No HDMI audio after suspend > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > HDMI audio out is available after suspend/sleep, but I am using a > Radeon video card with Audio/Video through HDMI. I have video, but no > audio. > > Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 > > lspci > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. > [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] > 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI > Audio [Radeon HD 5400/6300 Series] > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1755941/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755941 Title: No HDMI audio after suspend Status in linux package in Ubuntu: Incomplete Bug description: HDMI audio out is available after suspend/sleep, but I am using a Radeon video card with Audio/Video through HDMI. I have video, but no audio. Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 lspci 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755808] Re: CONFIG_VIRTIO_BLK=y in bionic
** Tags added: id-5a7e120dfbf0d5c41d3522ad -- 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/1755808 Title: CONFIG_VIRTIO_BLK=y in bionic Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Bionic: Fix Released Bug description: Using v4.15 linux-kvm, it fails to boot in a virtio only virtual machine. Inspecting the configs, it seems like CONFIG_VIRTIO_BLK is module, but should be included: $ grep CONFIG_VIRTIO_BLK= -r linux-kvm-4.*/debian.*/config/config* linux-kvm-4.15.0/debian.kvm/config/config.common.ubuntu: CONFIG_VIRTIO_BLK=m linux-kvm-4.15.0/debian.master/config/config.common.ubuntu: CONFIG_VIRTIO_BLK=m linux-kvm-4.4.0/debian.kvm/config/config.common.ubuntu: CONFIG_VIRTIO_BLK=y linux-kvm-4.4.0/debian.master/config/config.common.ubuntu: CONFIG_VIRTIO_BLK=y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1755808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755227] Re: linux: 3.13.0-144.193 -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/1755227 Title: linux: 3.13.0-144.193 -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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1755228 (linux-lts-trusty) derivatives: kernel-stable-phase-changed:Thursday, 15. March 2018 17:32 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752182] Re: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes
I'm working on this, and I've found that we need an additional commit from linux-next to fix a build error on 32-bit architectures. 4c06619fc4da scsi: lpfc: use __raw_writeX on DPP copies There are several other fixes there, I haven't looked at each of them in detail but this one at least looks pretty important: 917d59ac5e26 scsi: lpfc: Add missing unlock in WQ full logic I've added these two to my list; can you please let us know if there are any additional fixes we should get from linux-next? Thanks! ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) 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 in Ubuntu. https://bugs.launchpad.net/bugs/1752182 Title: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: This is a placeholder bugzilla that will list all commit ids needed for Broadcom Emulex FC 32/64GB new hardware support and all bug fixes available upstream. Note the lpfc FC driver commit list will include NVMe patches for ease of maintainability vs. upstream but we ask that you not build NVMe FC since we do not intend to support NVMe FC on 18.04 (4.15 kernel) at this time due to all of the unmet upper layer dependencies. Laurie Barry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756337] Re: kernel bug at fscache/operation.c
Hi There, The MAAS images use the kernels that are available in the archive. Since this is a kernel issue, I'm retargetting to the linux package in Ubuntu. If this is already fixed, MAAS will automatically update new images once the packages are available in the archive, otherwise, please feel free to use a different kernel (e.g. hwe-16.04) and see if that fixes your issue. Just make sure your images are latest. ** Changed in: maas Status: New => Invalid ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756337 Title: kernel bug at fscache/operation.c Status in MAAS: Invalid Status in linux package in Ubuntu: Incomplete Bug description: MAAS deployed Ubuntu 16.04 LTS hosts began suffering from either [577275.774627] FS-Cache: [577275.777530] FS-Cache: Assertion failed [577275.781945] FS-Cache: 6 == 5 is false [577275.786304] [ cut here ] [577275.791662] kernel BUG at /build/linux-Fk60NP/linux-4.10.0/fs/fscache/operation.c:494! [577275.800740] invalid opcode: [#1] SMP [577275.805415] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache $ [577275.885578] ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipa$ [577275.925771] CPU: 52 PID: 39395 Comm: kworker/u161:1 Not tainted 4.10.0-19-generic #21-Ubuntu [577275.940896] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.6.0 10/31/2017 or [126530.552030] FS-Cache: [126530.554868] FS-Cache: Assertion failed [126530.559250] FS-Cache: 1 > 0 is false [126530.563472] [ cut here ] [126530.568822] kernel BUG at /build/linux-Fk60NP/linux-4.10.0/fs/fscache/operation.c:68! [126530.577792] invalid opcode: [#1] SMP [126530.582464] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache $ [126530.662615] libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul $ [126530.700165] CPU: 6 PID: 13971 Comm: CPU 1/KVM Not tainted 4.10.0-19-generic #21-Ubuntu [126530.709227] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 01/26/2018 Possible solution here: https://patchwork.kernel.org/patch/10234815/ Using MAAS: MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1756337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756337] 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 1756337 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: zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756337 Title: kernel bug at fscache/operation.c Status in MAAS: Invalid Status in linux package in Ubuntu: Incomplete Bug description: MAAS deployed Ubuntu 16.04 LTS hosts began suffering from either [577275.774627] FS-Cache: [577275.777530] FS-Cache: Assertion failed [577275.781945] FS-Cache: 6 == 5 is false [577275.786304] [ cut here ] [577275.791662] kernel BUG at /build/linux-Fk60NP/linux-4.10.0/fs/fscache/operation.c:494! [577275.800740] invalid opcode: [#1] SMP [577275.805415] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache $ [577275.885578] ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipa$ [577275.925771] CPU: 52 PID: 39395 Comm: kworker/u161:1 Not tainted 4.10.0-19-generic #21-Ubuntu [577275.940896] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.6.0 10/31/2017 or [126530.552030] FS-Cache: [126530.554868] FS-Cache: Assertion failed [126530.559250] FS-Cache: 1 > 0 is false [126530.563472] [ cut here ] [126530.568822] kernel BUG at /build/linux-Fk60NP/linux-4.10.0/fs/fscache/operation.c:68! [126530.577792] invalid opcode: [#1] SMP [126530.582464] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache $ [126530.662615] libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul $ [126530.700165] CPU: 6 PID: 13971 Comm: CPU 1/KVM Not tainted 4.10.0-19-generic #21-Ubuntu [126530.709227] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 01/26/2018 Possible solution here: https://patchwork.kernel.org/patch/10234815/ Using MAAS: MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1756337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755228] Re: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1755227 phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1755228 Title: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755227 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755839] Re: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Killing the main plymouth server process allowed the installation to proceed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755839 Title: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Incomplete Bug description: Ran software update, which hung on DKMS processing for linux kernel upgrade ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1410 F pulseaudio mgann 1799 F pulseaudio Date: Wed Mar 14 10:16:22 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2018-03-09 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: ASUSTeK COMPUTER INC. GL703VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=4214ac83-5fc5-473a-a9ea-0f7b7c7a9291 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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.:bvrGL703VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755624] Re: With intel-microcode 3.20180312, kernel reports as broken spectre v2 microcode
>From the 4.15.0.12-13 still get the error oem@ubuntu:~$ journalctl -b | grep microcode kernel: microcode: microcode updated early to revision 0xc2, date = 2017-11-16 kernel: Intel Spectre v2 broken microcode detected; disabling Speculation Control kernel: microcode: sig=0x506e3, pf=0x2, revision=0xc2 kernel: microcode: Microcode Update Driver: v2.2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755624 Title: With intel-microcode 3.20180312, kernel reports as broken spectre v2 microcode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: With an intel-microcode package based off of https://downloadcenter.intel.com/download/27591/Linux-Processor- Microcode-Data-File, when booting, the kernel 4.15.0-10.11-generic reports the following in dmesg: [0.00] microcode: microcode updated early to revision 0x84, date = 2018-01-21 [0.00] Intel Spectre v2 broken microcode detected; disabling Speculation Control And indeed, none of ibrs, ibpb, or stibp show up in /proc/cpuinfo. Other testers of the updated microcode report seeing the same thing. The processor this is being tested on is: cpu family : 6 model : 142 model name : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz stepping: 9 microcode : 0x84 The test for the microcode is in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/tree/arch/x86/kernel/cpu/intel.c#n178 ; specifically, it looks like bad_spectre_microcode(c) is returning true. It seems https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d37fc6d360a404b208547ba112e7dabb6533c7fc has not been pulled in yet (though it's staged as 3e442a86b70eea274d01569244584d91e2f287e7 in bionic/master-next and is in 4.15.0-12.13 in bionic-proposed), which addresses things for Kaby Lake processors, but other processers may need to be verified for correctness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755624] Re: With intel-microcode 3.20180312, kernel reports as broken spectre v2 microcode
Something abnormal: - installed: intel-microcode (3.20180312.0~ubuntu18.04.1) bionic - but log shows: microcode: microcode updated early to revision 0xc2, date = 2017-11-16 Looks like the latest upgrade is not use by the kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755624 Title: With intel-microcode 3.20180312, kernel reports as broken spectre v2 microcode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: With an intel-microcode package based off of https://downloadcenter.intel.com/download/27591/Linux-Processor- Microcode-Data-File, when booting, the kernel 4.15.0-10.11-generic reports the following in dmesg: [0.00] microcode: microcode updated early to revision 0x84, date = 2018-01-21 [0.00] Intel Spectre v2 broken microcode detected; disabling Speculation Control And indeed, none of ibrs, ibpb, or stibp show up in /proc/cpuinfo. Other testers of the updated microcode report seeing the same thing. The processor this is being tested on is: cpu family : 6 model : 142 model name : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz stepping: 9 microcode : 0x84 The test for the microcode is in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/tree/arch/x86/kernel/cpu/intel.c#n178 ; specifically, it looks like bad_spectre_microcode(c) is returning true. It seems https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d37fc6d360a404b208547ba112e7dabb6533c7fc has not been pulled in yet (though it's staged as 3e442a86b70eea274d01569244584d91e2f287e7 in bionic/master-next and is in 4.15.0-12.13 in bionic-proposed), which addresses things for Kaby Lake processors, but other processers may need to be verified for correctness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756342] [NEW] Ubtun 17.10 Grub menu corrupt
Public bug reported: When Ubuntu boots Grub shows the purple small characters based screen is drawn very slowly from top to bottom almost line by line. After that the Grub menu writes over it in black and white characters. This started to happen just recently. Keyboard selection of which item to boot is sluggish. After boot, everything is fine. Also, Ubuntu does lock up often. Sometimes at the boot screen or when idle after login. and sometimes after several hours using lots of applications. Integrated IGP, (intel on board grpahics disabled) so it's not using Wayland suppose. Everything updated with apt-get install upgrade/update. Ubuntu 4.13.0-36.40-lowlatency 4.13.13 0:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0100] (rev 09) Subsystem: Super Micro Computer Inc 2nd Generation Core Processor Family DRAM Controller [15d9:0623] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snb_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Super Micro Computer Inc Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [15d9:0623] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 4181 Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM not supported, Exit Latency L0s <256ns, L1 <4us ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #7, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Not Supported ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [140 v1] Root Complex Link Desc: PortNumber=02 ComponentID=01 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=M
[Kernel-packages] [Bug 1752182] Re: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes
Seth, Thank you for you note, this patch was updated by the upstream SCSI maintainer after we submitted it. We are agree with this modification, please pull it in. thank you Laurie -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752182 Title: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: This is a placeholder bugzilla that will list all commit ids needed for Broadcom Emulex FC 32/64GB new hardware support and all bug fixes available upstream. Note the lpfc FC driver commit list will include NVMe patches for ease of maintainability vs. upstream but we ask that you not build NVMe FC since we do not intend to support NVMe FC on 18.04 (4.15 kernel) at this time due to all of the unmet upper layer dependencies. Laurie Barry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756342] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756342 Title: Ubtun 17.10 Grub menu corrupt Status in linux package in Ubuntu: Confirmed Bug description: When Ubuntu boots Grub shows the purple small characters based screen is drawn very slowly from top to bottom almost line by line. After that the Grub menu writes over it in black and white characters. This started to happen just recently. Keyboard selection of which item to boot is sluggish. After boot, everything is fine. Also, Ubuntu does lock up often. Sometimes at the boot screen or when idle after login. and sometimes after several hours using lots of applications. Integrated IGP, (intel on board grpahics disabled) so it's not using Wayland suppose. Everything updated with apt-get install upgrade/update. Ubuntu 4.13.0-36.40-lowlatency 4.13.13 0:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0100] (rev 09) Subsystem: Super Micro Computer Inc 2nd Generation Core Processor Family DRAM Controller [15d9:0623] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snb_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Super Micro Computer Inc Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [15d9:0623] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 4181 Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM not supported, Exit Latency L0s <256ns, L1 <4us ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #7, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Not Supported ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed+ WRR3
[Kernel-packages] [Bug 1755624] Re: With intel-microcode 3.20180312, kernel reports as broken spectre v2 microcode
So i have reinstalled both intel-microcode & iucode-tool and then rebooted. Still get the latest microcode version with the error; even if the reinstall has not displayed warning/error and the kernel rebuilt as expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755624 Title: With intel-microcode 3.20180312, kernel reports as broken spectre v2 microcode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: With an intel-microcode package based off of https://downloadcenter.intel.com/download/27591/Linux-Processor- Microcode-Data-File, when booting, the kernel 4.15.0-10.11-generic reports the following in dmesg: [0.00] microcode: microcode updated early to revision 0x84, date = 2018-01-21 [0.00] Intel Spectre v2 broken microcode detected; disabling Speculation Control And indeed, none of ibrs, ibpb, or stibp show up in /proc/cpuinfo. Other testers of the updated microcode report seeing the same thing. The processor this is being tested on is: cpu family : 6 model : 142 model name : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz stepping: 9 microcode : 0x84 The test for the microcode is in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/tree/arch/x86/kernel/cpu/intel.c#n178 ; specifically, it looks like bad_spectre_microcode(c) is returning true. It seems https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d37fc6d360a404b208547ba112e7dabb6533c7fc has not been pulled in yet (though it's staged as 3e442a86b70eea274d01569244584d91e2f287e7 in bionic/master-next and is in 4.15.0-12.13 in bionic-proposed), which addresses things for Kaby Lake processors, but other processers may need to be verified for correctness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752182] Re: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes
Yes those patches are needed. They are good. You should include them -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752182 Title: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: This is a placeholder bugzilla that will list all commit ids needed for Broadcom Emulex FC 32/64GB new hardware support and all bug fixes available upstream. Note the lpfc FC driver commit list will include NVMe patches for ease of maintainability vs. upstream but we ask that you not build NVMe FC since we do not intend to support NVMe FC on 18.04 (4.15 kernel) at this time due to all of the unmet upper layer dependencies. Laurie Barry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752182] Re: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752182 Title: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: This is a placeholder bugzilla that will list all commit ids needed for Broadcom Emulex FC 32/64GB new hardware support and all bug fixes available upstream. Note the lpfc FC driver commit list will include NVMe patches for ease of maintainability vs. upstream but we ask that you not build NVMe FC since we do not intend to support NVMe FC on 18.04 (4.15 kernel) at this time due to all of the unmet upper layer dependencies. Laurie Barry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753424] Re: s390/crypto: Fix kernel crash on aes_s390 module remove
** Changed in: linux (Ubuntu Bionic) Status: Triaged => 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/1753424 Title: s390/crypto: Fix kernel crash on aes_s390 module remove Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Upstream patch to fix the aes_s390 kernel module remove crash, introduced with kernel 4.15 rc1. Here is the patch to fix the kernel crash on aes_s390 kernel module removal. Please note that this patch is as of now not upstream available but in the s390 pipe for the next merge window (and so may be visible upstream with the start of the 4.17 development kernels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1753424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755227] Re: linux: 3.13.0-144.193 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755227 Title: linux: 3.13.0-144.193 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1755228 (linux-lts-trusty) derivatives: kernel-stable-phase-changed:Thursday, 15. March 2018 17:32 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755839] Re: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
@jsalisbury sudo apt-get install -f hangs in the same way, so the other commands are impossible to execute. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755839 Title: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Incomplete Bug description: Ran software update, which hung on DKMS processing for linux kernel upgrade ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1410 F pulseaudio mgann 1799 F pulseaudio Date: Wed Mar 14 10:16:22 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2018-03-09 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: ASUSTeK COMPUTER INC. GL703VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=4214ac83-5fc5-473a-a9ea-0f7b7c7a9291 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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.:bvrGL703VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753424] Re: s390/crypto: Fix kernel crash on aes_s390 module remove
** Changed in: ubuntu-z-systems Status: Triaged => 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/1753424 Title: s390/crypto: Fix kernel crash on aes_s390 module remove Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Upstream patch to fix the aes_s390 kernel module remove crash, introduced with kernel 4.15 rc1. Here is the patch to fix the kernel crash on aes_s390 kernel module removal. Please note that this patch is as of now not upstream available but in the s390 pipe for the next merge window (and so may be visible upstream with the start of the 4.17 development kernels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1753424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755624] Re: With intel-microcode 3.20180312, kernel reports as broken spectre v2 microcode
More tests: - purging intel-microcode & iucode-tool, then rebooting, i get: kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb2 (or later) - reinstalling the 2 packages above (3.20180312.0~ubuntu18.04.1) and rebooting, i get: kernel: microcode: microcode updated early to revision 0xc2, date = 2017-11-16 As previously, purging then reinstalling still show that old version. Is it an initrd path issue ? - running: (cpio -t; zcat | cpio -t) < /boot/initrd.img-4.15.0-12-generic kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/.enuineIntel.align.0123456789abc kernel/x86/microcode/GenuineIntel.bin 196 blocks ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755624 Title: With intel-microcode 3.20180312, kernel reports as broken spectre v2 microcode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: With an intel-microcode package based off of https://downloadcenter.intel.com/download/27591/Linux-Processor- Microcode-Data-File, when booting, the kernel 4.15.0-10.11-generic reports the following in dmesg: [0.00] microcode: microcode updated early to revision 0x84, date = 2018-01-21 [0.00] Intel Spectre v2 broken microcode detected; disabling Speculation Control And indeed, none of ibrs, ibpb, or stibp show up in /proc/cpuinfo. Other testers of the updated microcode report seeing the same thing. The processor this is being tested on is: cpu family : 6 model : 142 model name : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz stepping: 9 microcode : 0x84 The test for the microcode is in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/tree/arch/x86/kernel/cpu/intel.c#n178 ; specifically, it looks like bad_spectre_microcode(c) is returning true. It seems https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d37fc6d360a404b208547ba112e7dabb6533c7fc has not been pulled in yet (though it's staged as 3e442a86b70eea274d01569244584d91e2f287e7 in bionic/master-next and is in 4.15.0-12.13 in bionic-proposed), which addresses things for Kaby Lake processors, but other processers may need to be verified for correctness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754580] Re: [CVE] Spectre: System Z {kernel} UBUNTU18.04
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754580 Title: [CVE] Spectre: System Z {kernel} UBUNTU18.04 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Comment will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1754580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
I built another v4.12-rc3 test kernel. This time with Xenial configs instead of Artful configs. This test kernel can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc3-xenial-configs Can you see if this kernel exhibits the bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
Sorry the correct link for the new 4.12-rc3 kernel with Xenial configs is: http://kernel.ubuntu.com/~jsalisbury/lp1753662/v4.12-rc3-xenial-configs/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751266] Re: Missing firmware in linux-image-4.15.0-10-generic
I think I've got a related issue. I'm getting the following error while trying to netboot the last few netboot installers (including the most recent): bnx2 :06:00.0: Direct firmware load for bnx2/bnx2-rv2p-06-6.15.fw failed with error -2 bnx2: Can't load firmware file "bnx2/bnx2-rv2p-06-6.15.fw" It does indeed look like bnx2-rv2p-06-6.15.fw is referenced in bnx2.ko but the fw isn't in lib/firmware/bnx2/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1751266 Title: Missing firmware in linux-image-4.15.0-10-generic Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Bug description: linux-image-4.15.0-10-generic doesn't have the firmware that linux- image-4.13.0-32-generic has. It doesn't have any of the files that are present in 4.13 in /lib/firmware/4.13.0-32-generic/. For me, this means i can boot 4.15, but my network wont work because of: kernel: [ 13.468996] bnx2 :0b:00.0: Direct firmware load for bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2 kernel: [ 13.468998] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 feb 23 13:12 seq crw-rw 1 root audio 116, 33 feb 23 13:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Feb 23 13:50:38 2018 InstallationDate: Installed on 2018-02-14 (9 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM System x3550 M3 -[7944S77]- PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=4a958e16-f948-4619-bad5-51d238213cc5 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.171 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E158AUS-1.16]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E158AUS-1.16]-:bd11/26/2012:svnIBM:pnSystemx3550M3-[7944S77]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: System x3550 M3 -[7944S77]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756121] Re: Xenial update to 4.4.116 stable release
List of skipped patches (already applied previously or not applicable): * nvme: Fix managing degraded controllers * dccp: CVE-2017-8824: use-after-free in DCCP code ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-8824 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756121 Title: Xenial update to 4.4.116 stable release Status in linux package in Ubuntu: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.116 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.116 stable release shall be applied: * Linux 4.4.116 * ftrace: Remove incorrect setting of glob search field * mn10300/misalignment: Use SIGSEGV SEGV_MAPERR to report a failed user copy * ovl: fix failure to fsync lower dir * ACPI: sbshc: remove raw pointer from printk() message * nvme: Fix managing degraded controllers * btrfs: Handle btrfs_set_extent_delalloc failure in fixup worker * pktcdvd: Fix pkt_setup_dev() error path * EDAC, octeon: Fix an uninitialized variable warning * xtensa: fix futex_atomic_cmpxchg_inatomic * alpha: fix reboot on Avanti platform * alpha: fix crash if pthread_create races with signal delivery * signal/sh: Ensure si_signo is initialized in do_divide_error * signal/openrisc: Fix do_unaligned_access to send the proper signal * Bluetooth: btusb: Restore QCA Rome suspend/resume fix with a "rewritten" version * Revert "Bluetooth: btusb: fix QCA Rome suspend/resume" * Bluetooth: btsdio: Do not bind to non-removable BCM43341 * HID: quirks: Fix keyboard + touchpad on Toshiba Click Mini not working * kernel/async.c: revert "async: simplify lowest_in_progress()" * media: cxusb, dib0700: ignore XC2028_I2C_FLUSH * media: ts2020: avoid integer overflows on 32 bit machines * watchdog: imx2_wdt: restore previous timeout after suspend+resume * KVM: nVMX: Fix races when sending nested PI while dest enters/leaves L2 * arm: KVM: Fix SMCCC handling of unimplemented SMC/HVC calls * crypto: caam - fix endless loop when DECO acquire fails * media: v4l2-compat-ioctl32.c: refactor compat ioctl32 logic * media: v4l2-compat-ioctl32.c: don't copy back the result for certain errors * media: v4l2-compat-ioctl32.c: drop pr_info for unknown buffer type * media: v4l2-compat-ioctl32.c: copy clip list in put_v4l2_window32 * media: v4l2-compat-ioctl32: Copy v4l2_window->global_alpha * media: v4l2-compat-ioctl32.c: make ctrl_is_pointer work for subdevs * media: v4l2-compat-ioctl32.c: fix ctrl_is_pointer * media: v4l2-compat-ioctl32.c: copy m.userptr in put_v4l2_plane32 * media: v4l2-compat-ioctl32.c: avoid sizeof(type) * media: v4l2-compat-ioctl32.c: move 'helper' functions to __get/put_v4l2_format32 * media: v4l2-compat-ioctl32.c: fix the indentation * media: v4l2-compat-ioctl32.c: add missing VIDIOC_PREPARE_BUF * vb2: V4L2_BUF_FLAG_DONE is set after DQBUF * media: v4l2-ioctl.c: don't copy back the result for -ENOTTY * nsfs: mark dentry with DCACHE_RCUACCESS * crypto: poly1305 - remove ->setkey() method * crypto: cryptd - pass through absence of ->setkey() * crypto: hash - introduce crypto_hash_alg_has_setkey() * ahci: Add Intel Cannon Lake PCH-H PCI ID * ahci: Add PCI ids for Intel Bay Trail, Cherry Trail and Apollo Lake AHCI * ahci: Annotate PCI ids for mobile Intel chipsets as such * kernfs: fix regression in kernfs_fop_write caused by wrong type * NFS: reject request for id_legacy key without auxdata * NFS: commit direct writes even if they fail partially * NFS: Add a cond_resched() to nfs_commit_release_pages() * nfs/pnfs: fix nfs_direct_req ref leak when i/o falls back to the mds * ubi: block: Fix locking for idr_alloc/idr_remove * mtd: nand: sunxi: Fix ECC strength choice * mtd: nand: Fix nand_do_read_oob() return value * mtd: nand: brcmnand: Disable prefetch by default * mtd: cfi: convert inline functions to macros * media: dvb-usb-v2: lmedm04: move ts2020 attach to dm04_lme2510_tuner * media: dvb-usb-v2: lmedm04: Improve logic checking of warm start * dccp: CVE-2017-8824: use-after-free in DCCP code * sched/rt: Up the root domain ref count when passing it around via IPIs * sched/rt: Use container_of() to get root domain in rto
[Kernel-packages] [Bug 1751266] Re: Missing firmware in linux-image-4.15.0-10-generic
@koebbe - please open a new bug against linux-firmware and assign it to me. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1751266 Title: Missing firmware in linux-image-4.15.0-10-generic Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Bug description: linux-image-4.15.0-10-generic doesn't have the firmware that linux- image-4.13.0-32-generic has. It doesn't have any of the files that are present in 4.13 in /lib/firmware/4.13.0-32-generic/. For me, this means i can boot 4.15, but my network wont work because of: kernel: [ 13.468996] bnx2 :0b:00.0: Direct firmware load for bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2 kernel: [ 13.468998] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 feb 23 13:12 seq crw-rw 1 root audio 116, 33 feb 23 13:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Feb 23 13:50:38 2018 InstallationDate: Installed on 2018-02-14 (9 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM System x3550 M3 -[7944S77]- PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=4a958e16-f948-4619-bad5-51d238213cc5 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.171 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E158AUS-1.16]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E158AUS-1.16]-:bd11/26/2012:svnIBM:pnSystemx3550M3-[7944S77]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: System x3550 M3 -[7944S77]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747074] Re: System Freeze When Start Virtualbox
I am also affected by this bug, Virtualbox modules won't build with kernel 4.15, so I tried mainline kernel vmlinuz-4.13.16-041316-generic and it was also affected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747074 Title: System Freeze When Start Virtualbox Status in linux package in Ubuntu: Incomplete Bug description: System Freeze When Start Virtualbox The problem persists. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: paulo 2491 F pulseaudio /dev/snd/controlC0: paulo 2491 F pulseaudio /dev/snd/controlC1: paulo 2491 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-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.157.14 Tags: sylvia 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 vboxusers _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0607 dmi.board.asset.tag: Default string dmi.board.name: STRIX H270F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747074/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756367] [NEW] missing bnx2 firmware
Public bug reported: I'm getting the following error while trying to netboot the last few netboot installers (including the most recent, 20101020ubuntu534): bnx2 :06:00.0: Direct firmware load for bnx2/bnx2-rv2p-06-6.15.fw failed with error -2 bnx2: Can't load firmware file "bnx2/bnx2-rv2p-06-6.15.fw" It does indeed look like bnx2-rv2p-06-6.15.fw is referenced in bnx2.ko but the fw isn't in lib/firmware/bnx2/ Cheers, Brian ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-firmware (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/1756367 Title: missing bnx2 firmware Status in linux-firmware package in Ubuntu: New Bug description: I'm getting the following error while trying to netboot the last few netboot installers (including the most recent, 20101020ubuntu534): bnx2 :06:00.0: Direct firmware load for bnx2/bnx2-rv2p-06-6.15.fw failed with error -2 bnx2: Can't load firmware file "bnx2/bnx2-rv2p-06-6.15.fw" It does indeed look like bnx2-rv2p-06-6.15.fw is referenced in bnx2.ko but the fw isn't in lib/firmware/bnx2/ Cheers, Brian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1756367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754580] Re: [CVE] Spectre: System Z {kernel} UBUNTU18.04
The attached config does not seem to contain the new options. These are the values I've selected, please let me know if they should be changed. CONFIG_EXPOLINE=y CONFIG_EXPOLINE_FULL=y # CONFIG_EXPOLINE_MEDIUM is not set # CONFIG_EXPOLINE_OFF is not set CONFIG_KERNEL_NOBP=y ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754580 Title: [CVE] Spectre: System Z {kernel} UBUNTU18.04 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Comment will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1754580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756121] Re: Xenial update to 4.4.116 stable release
Reverted the following SAUCE patches. The update to .116 pulls in upstream's final implementation. 1a7bb6191224 UBUNTU: SAUCE: UBUNTU: [Config] Disable CONFIG_PPC_DEBUG_RFI 2a12cf7710e1 UBUNTU: SAUCE: rfi-flush: Fix some RFI conversions in the KVM code 68ee8a04f527 UBUNTU: SAUCE: rfi-flush: Fix the 32-bit KVM build b6a090d66183 UBUNTU: SAUCE: rfi-flush: Fallback flush add load dependency 9fb6d7509dcd UBUNTU: SAUCE: rfi-flush: Use rfi-flush in printks 2d8d8a2459d2 UBUNTU: SAUCE: rfi-flush: Add no_rfi_flush and nopti comandline options d275a2d6aa9b UBUNTU: SAUCE: rfi-flush: Refactor the macros so the nops are defined once e82cad5fc178 UBUNTU: SAUCE: rfi-flush: Fix HRFI_TO_UNKNOWN 1a65b15b16bd UBUNTU: SAUCE: rfi-flush: Fix the fallback flush to actually activate c049d338c5c2 UBUNTU: SAUCE: rfi-flush: Rework pseries logic to be more cautious 884242613372 UBUNTU: SAUCE: rfi-flush: Rework powernv logic to be more cautious ee71154ed061 UBUNTU: SAUCE: rfi-flush: Add barriers to the fallback L1D flushing cab09201eef8 UBUNTU: SAUCE: Fix compilation errors for arch/powerpc/lib/feature-fixups.c 4fc2e0b57c89 UBUNTU: SAUCE: Remove setup.h include file otherwise compilation complains about missing header file. 323c02b05b3a UBUNTU: SAUCE: powerpc/asm: Allow including ppc_asm.h in asm files d585250a68cd UBUNTU: SAUCE: rfi-flush: Add speculation barrier before ori 30,30,0 flush 5dcadca3b007 UBUNTU: SAUCE: rfi-flush: Allow HV to advertise multiple flush types 313e806c5d1f UBUNTU: SAUCE: rfi-flush: Support more than one flush type at once 00d9e152a174 UBUNTU: SAUCE: rfi-flush: Expand the RFI section to two nop slots e1f3564b8cc8 UBUNTU: SAUCE: rfi-flush: Push the instruction selection down to the patching routine 0929d8b8c889 UBUNTU: SAUCE: rfi-flush: Make l1d_flush_type bit flags 2d94edf362f5 UBUNTU: SAUCE: rfi-flush: Implement congruence-first fallback flush b9bc93cd2404 UBUNTU: SAUCE: KVM: Revert the implementation of H_GET_CPU_CHARACTERISTICS dad6dc82037d UBUNTU: SAUCE: rfi-flush: kvmppc_skip_(H)interrupt returns to host 341c0f15655c UBUNTU: SAUCE: Fixup rfid in kvmppc_skip_Hinterrupt should be hrfid 035298082b55 UBUNTU: SAUCE: rfi-flush: Add HRFI_TO_UNKNOWN and use it in denorm 8319f6cde6b4 UBUNTU: SAUCE: rfi-flush: Make DEBUG_RFI a CONFIG option 76b012587aa8 UBUNTU: SAUCE: powerpc: Secure memory rfi flush -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756121 Title: Xenial update to 4.4.116 stable release Status in linux package in Ubuntu: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.116 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.116 stable release shall be applied: * Linux 4.4.116 * ftrace: Remove incorrect setting of glob search field * mn10300/misalignment: Use SIGSEGV SEGV_MAPERR to report a failed user copy * ovl: fix failure to fsync lower dir * ACPI: sbshc: remove raw pointer from printk() message * nvme: Fix managing degraded controllers * btrfs: Handle btrfs_set_extent_delalloc failure in fixup worker * pktcdvd: Fix pkt_setup_dev() error path * EDAC, octeon: Fix an uninitialized variable warning * xtensa: fix futex_atomic_cmpxchg_inatomic * alpha: fix reboot on Avanti platform * alpha: fix crash if pthread_create races with signal delivery * signal/sh: Ensure si_signo is initialized in do_divide_error * signal/openrisc: Fix do_unaligned_access to send the proper signal * Bluetooth: btusb: Restore QCA Rome suspend/resume fix with a "rewritten" version * Revert "Bluetooth: btusb: fix QCA Rome suspend/resume" * Bluetooth: btsdio: Do not bind to non-removable BCM43341 * HID: quirks: Fix keyboard + touchpad on Toshiba Click Mini not working * kernel/async.c: revert "async: simplify lowest_in_progress()" * media: cxusb, dib0700: ignore XC2028_I2C_FLUSH * media: ts2020: avoid integer overflows on 32 bit machines * watchdog: imx2_wdt: restore previous timeout after suspend+resume * KVM: nVMX: Fix races when sending nested PI while dest enters/leaves L2 * arm: KVM: Fix SMCCC handling of unimplemented SMC/HVC calls * crypto: caam - fix endless loop when DECO acquire fails * media: v4l2-compat-ioctl32.c: refactor compat ioctl32 logic * media: v4l2-compat-ioctl32.c: don't copy back the result for certain errors * media: v4l2-compat-ioctl32.c: drop pr_info for unkn
[Kernel-packages] [Bug 1745938] Re: System Freezes while starting VM in virtualbox after Kernrel Upgrade 4.13.0-31.34
I have the same issue and was able to reproduce it on both 4.13.0-21 and 4.13.0-25, as well as mainline 4.13.16 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745938 Title: System Freezes while starting VM in virtualbox after Kernrel Upgrade 4.13.0-31.34 Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04.3 , I upgraded Kernel 4.13.0-31.34 , which includes specter and meltdown fixes. After Upgrade when I was going to start VM in virtualbox System is getting freezes. Reboot required to resume system. I faced 4 times. I rollback to kernel 4.10.0-42. Now I am able to start vm perfectly. Please look into this kernel issue. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ketankumar.patel 2098 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2a3a4447-c93a-46fc-96e9-56023bb774f8 InstallationDate: Installed on 2017-09-11 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: LENOVO 20FL000FMS Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.157.14 Tags: xenial Uname: Linux 4.10.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET30W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FL000FMS dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1KET30W(1.17):bd02/10/2017:svnLENOVO:pn20FL000FMS:pvrThinkPadP50s:rvnLENOVO:rn20FL000FMS:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FL000FMS dmi.product.version: ThinkPad P50s dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kk 1403 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fadbc245-ccb0-42f5-82ff-b5d99ccdb2fe InstallationDate: Installed on 2018-01-31 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=fafc16a4-e3f4-42a7-84d9-99ec94651ad2 ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-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.157.15 RfKill: Tags: xenial 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: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://laun
[Kernel-packages] [Bug 1751266] Re: Missing firmware in linux-image-4.15.0-10-generic
Thanks Seth, #1756367 created...but it seems I'm not able to assign it to you. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1751266 Title: Missing firmware in linux-image-4.15.0-10-generic Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Bug description: linux-image-4.15.0-10-generic doesn't have the firmware that linux- image-4.13.0-32-generic has. It doesn't have any of the files that are present in 4.13 in /lib/firmware/4.13.0-32-generic/. For me, this means i can boot 4.15, but my network wont work because of: kernel: [ 13.468996] bnx2 :0b:00.0: Direct firmware load for bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2 kernel: [ 13.468998] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 feb 23 13:12 seq crw-rw 1 root audio 116, 33 feb 23 13:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Feb 23 13:50:38 2018 InstallationDate: Installed on 2018-02-14 (9 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM System x3550 M3 -[7944S77]- PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=4a958e16-f948-4619-bad5-51d238213cc5 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.171 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E158AUS-1.16]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E158AUS-1.16]-:bd11/26/2012:svnIBM:pnSystemx3550M3-[7944S77]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: System x3550 M3 -[7944S77]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756097] Re: [Bionic][ARM64] enable ROCE and HNS3 driver support for hip08 SoC
** Changed in: linux (Ubuntu Bionic) Status: Triaged => 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/1756097 Title: [Bionic][ARM64] enable ROCE and HNS3 driver support for hip08 SoC Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: The following patches were cleanly cherry-picked from 4.16-rc to bionic to enable ROCE and HNS3 driver support for hip08 SoC based arm64 reference board. Fuyun Liang (19): net: hns3: cleanup mac auto-negotiation state query net: hns3: fix for getting auto-negotiation state in hclge_get_autoneg net: hns3: add Asym Pause support to phy default features net: hns3: fix for updating fc_mode_last_time net: hns3: fix for setting MTU net: hns3: fix for changing MTU net: hns3: add MTU initialization for hardware net: hns3: fix for not setting pause parameters net: hns3: add ethtool_ops.get_coalesce support to PF net: hns3: add ethtool_ops.set_coalesce support to PF net: hns3: refactor interrupt coalescing init function net: hns3: refactor GL update function net: hns3: remove unused GL setup function net: hns3: change the unit of GL value macro net: hns3: add int_gl_idx setup for TX and RX queues net: hns3: add support for get_regs net: hns3: add manager table initialization for hardware net: hns3: add get/set_coalesce support to VF net: hns3: add int_gl_idx setup for VF Huazhong Tan (1): net: hns: Fix for variable may be used uninitialized warnings Jason Gunthorpe (1): RDMA/hns: Fix endian problems around imm_data and rkey Jian Shen (18): net: hns3: Add ethtool interface for vlan filter net: hns3: Disable VFs change rxvlan offload status net: hns3: Unify the strings display of packet statistics net: hns3: Fix spelling errors net: hns3: Remove repeat statistic of rx_errors net: hns3: Modify the update period of packet statistics net: hns3: Mask the packet statistics query when NIC is down net: hns3: Fix an error of total drop packet statistics net: hns3: Fix a loop index error of tqp statistics query net: hns3: Fix an error macro definition of HNS3_TQP_STAT net: hns3: Remove a useless member of struct hns3_stats net: hns3: Add packet statistics of netdev net: hns3: Fix a response data read error of tqp statistics query net: hns3: Add more packet size statisctics net: hns3: add feature check when feature changed net: hns3: check for NULL function pointer in hns3_nic_set_features net: hns3: add ethtool -p support for fiber port net: hns3: add net status led support for fiber port Manoj Iyer (1): UBUNTU: [Config]: enable CONFIG_HNS3_HCLGEVF as module. Peng Li (19): net: hns3: add support to query tqps number net: hns3: add support to modify tqps number net: hns3: change the returned tqp number by ethtool -x net: hns3: free the ring_data structrue when change tqps net: hns3: get rss_size_max from configuration but not hardcode net: hns3: add a mask initialization for mac_vlan table net: hns3: add vlan offload config command net: hns3: add ethtool related offload command net: hns3: add handling vlan tag offload in bd net: hns3: add support for set_pauseparam net: hns3: add support to update flow control settings after autoneg net: hns3: add support for querying advertised pause frame by ethtool ethx net: hns3: Increase the default depth of bucket for TM shaper net: hns3: change TM sched mode to TC-based mode when SRIOV enabled net: hns3: remove redundant semicolon Revert "net: hns3: Add packet statistics of netdev" net: hns3: report the function type the same line with hns3_nic_get_stats64 net: hns3: add ethtool_ops.get_channels support for VF net: hns3: remove TSO config command from VF driver Salil Mehta (12): net: hns3: Refactor of the reset interrupt handling logic net: hns3: Add reset service task for handling reset requests net: hns3: Refactors the requested reset & pending reset handling code net: hns3: Add HNS3 VF IMP(Integrated Management Proc) cmd interface net: hns3: Add mailbox support to VF driver net: hns3: Add HNS3 VF HCL(Hardware Compatibility Layer) Support net: hns3: Add HNS3 VF driver to kernel build framework net: hns3: Unified HNS3 {VF|PF} Ethernet Driver for hip08 SoC net: hns3: Add mailbox support to PF driver net: hns3: Change PF to add ring-vect binding & resetQ to mailbox net: hns3
[Kernel-packages] [Bug 1756096] Re: [Bionic][ARM64] add RAS extension and SDEI features
** Changed in: linux (Ubuntu Bionic) Status: Triaged => 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/1756096 Title: [Bionic][ARM64] add RAS extension and SDEI features Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Following patches were cherry-picked/backported from 4.16-rc to enable RAS extensions and SDEI features in Bionic for ARM64. Dongjiu Geng (1): KVM: arm64: Emulate RAS error registers and set HCR_EL2's TERR & TEA James Morse (24): KVM: arm64: Store vcpu on the stack during __guest_enter() KVM: arm/arm64: Convert kvm_host_cpu_state to a static per-cpu allocation KVM: arm64: Change hyp_panic()s dependency on tpidr_el2 arm64: alternatives: use tpidr_el2 on VHE hosts KVM: arm64: Stop save/restoring host tpidr_el1 on VHE Docs: dt: add devicetree binding for describing arm64 SDEI firmware firmware: arm_sdei: Add driver for Software Delegated Exceptions arm64: Add vmap_stack header file arm64: uaccess: Add PAN helper arm64: kernel: Add arch-specific SDEI entry code and CPU masking firmware: arm_sdei: Add support for CPU and system power states firmware: arm_sdei: add support for CPU private events arm64: acpi: Remove __init from acpi_psci_use_hvc() for use by SDEI firmware: arm_sdei: Discover SDEI support via ACPI arm64: sysreg: Move to use definitions for all the SCTLR bits arm64: kernel: Survive corrected RAS errors notified by SError arm64: Unconditionally enable IESB on exception entry/return for firmware-first arm64: kernel: Prepare for a DISR user KVM: arm/arm64: mask/unmask daif around VHE guests KVM: arm64: Set an impdef ESR for Virtual-SError using VSESR_EL2. KVM: arm64: Save/Restore guest DISR_EL1 KVM: arm64: Save ESR_EL2 on guest SError KVM: arm64: Handle RAS SErrors from EL1 on guest exit KVM: arm64: Handle RAS SErrors from EL2 on guest exit Manoj Iyer (1): UBUNTU: [Config]: enable RAS_EXTN and ARM_SDE_INTERFACE Xie XiuQi (1): arm64: cpufeature: Detect CPU RAS Extentions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756103] Re: [bionic][arm64] d-i: add hisi_sas_v3_hw to scsi-modules
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1756103 Title: [bionic][arm64] d-i: add hisi_sas_v3_hw to scsi-modules Status in linux package in Ubuntu: Fix Committed Bug description: Add hisi_sas_v3_hw to scsi-modules so that d-i can detect the drive during install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756094] Re: [Bionic][ARM64] PCI and SAS driver patches for hip08 SoCs
** Changed in: linux (Ubuntu Bionic) Status: Triaged => 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/1756094 Title: [Bionic][ARM64] PCI and SAS driver patches for hip08 SoCs Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Following patches are required to boot and install Bionic on hip08 soc based server reference board. Bjorn Helgaas (4): PCI/ASPM: Calculate LTR_L1.2_THRESHOLD from device characteristics PCI/ASPM: Enable Latency Tolerance Reporting when supported PCI/ASPM: Unexport internal ASPM interfaces PCI: Make PCI_SCAN_ALL_PCIE_DEVS work for Root as well as Downstream Ports Keith Busch (2): PCI/AER: Return error if AER is not supported PCI/DPC: Enable DPC only if AER is available Rafael J. Wysocki (2): PM / core: Add LEAVE_SUSPENDED driver flag PCI / PM: Support for LEAVE_SUSPENDED driver flag Tyler Baicar (1): PCI/AER: Skip recovery callbacks for correctable errors from ACPI APEI Wei Yongjun (1): scsi: hisi_sas: make local symbol host_attrs static Xiang Chen (8): scsi: hisi_sas: fix dma_unmap_sg() parameter scsi: hisi_sas: modify hisi_sas_dev_gone() for reset scsi: hisi_sas: change ncq process for v3 hw scsi: hisi_sas: add some print to enhance debugging scsi: hisi_sas: fix SAS_QUEUE_FULL problem while running IO scsi: hisi_sas: re-add the lldd_port_deformed() scsi: hisi_sas: add v3 hw suspend and resume scsi: hisi_sas: fix a bug in hisi_sas_dev_gone() Xiaofei Tan (11): scsi: hisi_sas: relocate clearing ITCT and freeing device scsi: hisi_sas: optimise port id refresh function scsi: hisi_sas: some optimizations of host controller reset scsi: hisi_sas: add an mechanism to do reset work synchronously scsi: hisi_sas: add RAS feature for v3 hw scsi: hisi_sas: improve int_chnl_int_v2_hw() consistency with v3 hw scsi: hisi_sas: add v2 hw port AXI error handling support scsi: hisi_sas: use an general way to delay PHY work scsi: hisi_sas: do link reset for some CHL_INT2 ints scsi: hisi_sas: judge result of internal abort scsi: hisi_sas: add internal abort dev in some places chenxiang (4): scsi: ata: enhance the definition of SET MAX feature field value scsi: hisi_sas: Change frame type for SET MAX commands UBUNTU: SAUCE: scsi: hisi_sas: config for hip08 ES UBUNTU: SAUCE: scsi: hisi_sas: export device table of v3 hw to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754580] Re: [CVE] Spectre: System Z {kernel} UBUNTU18.04
** Changed in: ubuntu-z-systems 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/1754580 Title: [CVE] Spectre: System Z {kernel} UBUNTU18.04 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Comment will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1754580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor
Today the fuzzy screen depicted in the attachment appears spontaneously while using google maps. This time with a block around the pointer, that continued to move with the pointer. ** Attachment added: "IMG_20180316_172748_697.jpg" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1752145/+attachment/5081615/+files/IMG_20180316_172748_697.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752145 Title: system freeze after full screen video viewing with Xorg on ultrawide monitor Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: 1. open a video (either youtube or totem) 2. put it in full screen. 3. wait Eventually (within minutes) the system will freeze in one of 2 ways. 1. There will be only blackness with no response ( even unresponsive). 2. There will be snow that shifts with keyboard and mouse interaction (see photo). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 27 19:08:13 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['workspace-g...@mathematical.coffee.gmail.com', 'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'enable-hot-corners' b'true' b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'" InstallationDate: Installed on 2018-01-05 (53 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752145/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755624] Re: With intel-microcode 3.20180312, kernel reports as broken spectre v2 microcode
Hi dino99, Microcode rev 0xc2 looks to be the correct revision for your processor: $ iucode-tool -L microcode-20180312.dat | grep 506e3 01/147: sig 0x000506e3, pf mask 0x36, 2017-11-16, rev 0x00c2, size 99328 (You can perform a similar check on the specific microcode for your processor on the file in the installed package: $ iucode-tool -L /lib/firmware/intel-ucode/06-5e-03 microcode bundle 1: /lib/firmware/intel-ucode/06-5e-03 001/001: sig 0x000506e3, pf_mask 0x36, 2017-11-16, rev 0x00c2, size 99328 ) And in the detailed description from https://downloadcenter.intel.com/download/27591/Linux-Processor- Microcode-Data-File: SKL R0 6-5e-3:36 ba->c2 Processor model 0x5e is defined as #define INTEL_FAM6_SKYLAKE_DESKTOP 0x5E in the kernel, and looking at the upstream kernel, microcode version 0xc2 for INTEL_FAM6_SKYLAKE_DESKTOP is still blacklisted as being unfixed for spectre: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/kernel/cpu/intel.c#n126 So unfortunately, this all looks correct for your processor. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755624 Title: With intel-microcode 3.20180312, kernel reports as broken spectre v2 microcode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: With an intel-microcode package based off of https://downloadcenter.intel.com/download/27591/Linux-Processor- Microcode-Data-File, when booting, the kernel 4.15.0-10.11-generic reports the following in dmesg: [0.00] microcode: microcode updated early to revision 0x84, date = 2018-01-21 [0.00] Intel Spectre v2 broken microcode detected; disabling Speculation Control And indeed, none of ibrs, ibpb, or stibp show up in /proc/cpuinfo. Other testers of the updated microcode report seeing the same thing. The processor this is being tested on is: cpu family : 6 model : 142 model name : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz stepping: 9 microcode : 0x84 The test for the microcode is in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/tree/arch/x86/kernel/cpu/intel.c#n178 ; specifically, it looks like bad_spectre_microcode(c) is returning true. It seems https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d37fc6d360a404b208547ba112e7dabb6533c7fc has not been pulled in yet (though it's staged as 3e442a86b70eea274d01569244584d91e2f287e7 in bionic/master-next and is in 4.15.0-12.13 in bionic-proposed), which addresses things for Kaby Lake processors, but other processers may need to be verified for correctness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756367] Re: missing bnx2 firmware
** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu) Status: New => Triaged ** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1756367 Title: missing bnx2 firmware Status in linux-firmware package in Ubuntu: Triaged Bug description: I'm getting the following error while trying to netboot the last few netboot installers (including the most recent, 20101020ubuntu534): bnx2 :06:00.0: Direct firmware load for bnx2/bnx2-rv2p-06-6.15.fw failed with error -2 bnx2: Can't load firmware file "bnx2/bnx2-rv2p-06-6.15.fw" It does indeed look like bnx2-rv2p-06-6.15.fw is referenced in bnx2.ko but the fw isn't in lib/firmware/bnx2/ Cheers, Brian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1756367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756367] Re: missing bnx2 firmware
** Changed in: linux-firmware (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1756367 Title: missing bnx2 firmware Status in linux-firmware package in Ubuntu: Fix Committed Bug description: I'm getting the following error while trying to netboot the last few netboot installers (including the most recent, 20101020ubuntu534): bnx2 :06:00.0: Direct firmware load for bnx2/bnx2-rv2p-06-6.15.fw failed with error -2 bnx2: Can't load firmware file "bnx2/bnx2-rv2p-06-6.15.fw" It does indeed look like bnx2-rv2p-06-6.15.fw is referenced in bnx2.ko but the fw isn't in lib/firmware/bnx2/ Cheers, Brian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1756367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754425] Re: Lots of pcieport and nvme kernel errors - system non-responsive
So today, woke up properly from lid close. I'm not sure what to make of it, as I haven't restarted for over 2 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754425 Title: Lots of pcieport and nvme kernel errors - system non-responsive Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: If I open the lid, it seems that the computer flat-out doesn't wake up. HOWEVER, if I wait patiently more than 20 seconds, and press (not hold) the power button, SOMETIMES, the computer will "snap out of it" and come back to my desktop. Although RAM is 25% used, and CPU usage is around 25-50% or less (depending on apps), mouse will regularly freeze up for some seconds every 10 seconds or so. Wifi will claim to be "on", but there aren't any networks in the "select network" dialogue. Turning wifi off and then on does not fix this problem. So I'll be in this terrifying state of non-responsive every few seconds computer, with no ability to reconnect to networks and report bug. I force restart. The first restart, upon login, will hang indefinitely on a purple screen with the cursor in the middle. I will have to force restart again. Upon 2nd restart, it will boot "normally". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 8 12:38:24 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-02 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1387 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-02 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0JHP5H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1387 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-02 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi
[Kernel-packages] [Bug 1756408] [NEW] linux: 4.15.0-13.14 -proposed tracker
Public bug reported: This bug is for tracking the 4.15.0-13.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-development-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-development-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-development-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New => In Progress ** Changed in: kernel-development-workflow Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-development-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756408 Title: linux: 4.15.0-13.14 -proposed tracker Status in Kernel Development Workflow: In Progress Status in
[Kernel-packages] [Bug 1756408] Re: linux: 4.15.0-13.14 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the 4.15.0-13.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + kernel-phase:Packaging + kernel-phase-changed:Friday, 16. March 2018 18:02 UTC ** Description changed: This bug is for tracking the 4.15.0-13.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase:Packaging kernel-phase-changed:Friday, 16. March 2018 18:02 UTC + + -- swm properties -- + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756408 Title: linux: 4.15.0-13.14 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-13.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase:Packaging kernel-phase-changed:Friday, 16. March 2018 18:02 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1756408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755217] Re: linux-aws: 4.4.0-1053.62 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid -- 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/1755217 Title: linux-aws: 4.4.0-1053.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755208 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755217] Re: linux-aws: 4.4.0-1053.62 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1053.62 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1755217 Title: linux-aws: 4.4.0-1053.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755208 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755228] Re: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-precise ** Tags added: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1755228 Title: linux-lts-trusty: 3.13.0-144.193~precise1 -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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755227 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755227] Re: linux: 3.13.0-144.193 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1755228 (linux-lts-trusty) derivatives: - kernel-stable-phase-changed:Thursday, 15. March 2018 17:32 UTC - kernel-stable-phase:Uploaded - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 16. March 2018 18:32 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1755228 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 16. March 2018 18:32 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755227 Title: linux: 3.13.0-144.193 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1755228 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755857] Re: devpts: handle bind-mounts
** Changed in: linux (Ubuntu Bionic) Status: Triaged => 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/1755857 Title: devpts: handle bind-mounts Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Hey everyone, I sent a few patches to fix a regression caused by wrong behavior in the devpts filesystem when used with the TIOCGPTPEER ioctl() we implemented a while back. The context and reproducer can be taken from my following commit message. The required patches are in Greg's tree and are: 1. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-testing&id=7d71109df186d630a41280670c8d71d0cf9b0da9 2. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-testing&id=a319b01d9095da6f6c54bd20c1f1300762506255 3. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-testing&id=4e15f760a43c7cb88e2b7ad6882501ccab5de29f 4. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-testing&id=ce290a19609d5ecd4a240a4750e0ed9a476cf015 devpts: resolve devpts bind-mounts Most libcs will still look at /dev/ptmx when opening the master fd of a pty device. When /dev/ptmx is a bind-mount of /dev/pts/ptmx and the TIOCGPTPEER ioctl() is used to safely retrieve a file descriptor for the slave side of the pty based on the master fd, the /proc/self/fd/{0,1,2} symlinks will point to /. A very simply reproducer for this issue presupposing a libc that uses TIOCGPTPEER in its openpty() implementation is: unshare --mount mount --bind /dev/pts/ptmx /dev/ptmx chmod 666 /dev/ptmx script ls -al /proc/self/fd/0 Having bind-mounts of /dev/pts/ptmx to /dev/ptmx not working correctly is a regression. In addition, it is also a fairly common scenario in containers employing user namespaces. The reason for the current failure is that the kernel tries to verify the useability of the devpts filesystem without resolving the /dev/ptmx bind-mount first. This will lead it to detect that the dentry is escaping its bind-mount. The reason is that while the devpts filesystem mounted at /dev/pts has the devtmpfs mounted at /dev as its parent mount: 21 -- -- / /dev -- 21 -- / /dev/pts devtmpfs and devpts are on different devices -- -- 0:6 / /dev -- -- 0:20 / /dev/pts This has the consequence that the pathname of the parent directory of the devpts filesystem mount at /dev/pts is /. So if /dev/ptmx is a bind-mount of /dev/pts/ptmx then the /dev/ptmx bind-mount and the devpts mount at /dev/pts will end up being located on the same device which is recorded in the superblock of their vfsmount. This means the parent directory of the /dev/ptmx bind-mount will be /ptmx: -- -- /ptmx /dev/ptmx Without the bind-mount resolution patch the kernel will now perform the bind-mount escape check directly on /dev/ptmx. The function responsible for this is devpts_ptmx_path() which calls pts_path() which in turn calls path_parent_directory(). Based on the above explanation, path_parent_directory() will yield / as the parent directory for the /dev/ptmx bind-mount and not the expected /dev. Thus, the kernel detects that /dev/ptmx is escaping its bind-mount and will set /proc//fd/ to /. This patch changes the logic to first resolve any bind-mounts. After the bind-mounts have been resolved (i.e. we have traced it back to the associated devpts mount) devpts_ptmx_path() can be called. In order to guarantee correct path generation for the slave file descriptor the kernel now requires that a pts directory is found in the parent directory of the ptmx bind-mount. This implies that when doing bind-mounts the ptmx bind-mount and the devpts mount should have a common parent directory. A valid example is: mount -t devpts devpts /dev/pts mount --bind /dev/pts/ptmx /dev/ptmx an invalid example is: mount -t devpts devpts /dev/pts mount --bind /dev/pts/ptmx /ptmx This allows us to support: - calling open on ptmx devices located inside non-standard devpts mounts: mount -t devpts devpts /mnt master = open("/mnt/ptmx", ...); slave = ioctl(master, TIOCGPTPEER, ...); - calling open on ptmx devices located outside the devpts mount with a common ancestor directory: mount -t devpts devpts /dev/pts mount --bind /dev/pts/ptmx /dev/ptmx master = open("/dev/ptmx", ...); slave = ioctl(master, TIOCGPTPEER, ...); while failing on ptmx devices located outside the devpts mount without a common ancestor directory: mount -t devpts devpts /dev/pts mount --bind /dev/pts/ptmx /ptmx master = open("/ptmx", ...); slave = ioctl(master, TIOCGPTPEER, ...); in which case save path generation cannot be guaranteed. To manage
[Kernel-packages] [Bug 1755210] Re: linux-aws: 4.4.0-1015.15 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1015.15 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1755210 Title: linux-aws: 4.4.0-1015.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755208 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755227] Re: linux: 3.13.0-144.193 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755227 Title: linux: 3.13.0-144.193 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1755228 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755217] Re: linux-aws: 4.4.0-1053.62 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755208 phase: Packaging + kernel-stable-phase-changed:Friday, 16. March 2018 20:01 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755208 - phase: Packaging - kernel-stable-phase-changed:Friday, 16. March 2018 20:01 UTC - kernel-stable-phase:Uploaded + phase: 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/1755217 Title: linux-aws: 4.4.0-1053.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755208 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755210] Re: linux-aws: 4.4.0-1015.15 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755208 phase: Packaging + kernel-stable-phase-changed:Friday, 16. March 2018 20:00 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755208 - phase: Packaging - kernel-stable-phase-changed:Friday, 16. March 2018 20:00 UTC - kernel-stable-phase:Uploaded + phase: 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/1755210 Title: linux-aws: 4.4.0-1015.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1755208 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753497] Re: Quanta Optical touchscreen recognized as usb but not as input device
This turned out to be a hardware bug. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753497 Title: Quanta Optical touchscreen recognized as usb but not as input device Status in linux package in Ubuntu: Invalid Bug description: I bought a IIyama T2250MTS touchscreen with a Quanta Optical screen in it that is attached through USB. It fails to register as a hiddev at kernel level with the following message: [21071.312190] usbhid 1-12.2:1.0: can't add hid device: -110 [21071.312219] usbhid: probe of 1-12.2:1.0 failed with error -110 Looking into kernel.log shows the same message. Device is seen, udev tries to link it to the kernel module and this fails. I tried all sort of things: sudo modprobe hid-multitouch (this seems the new module that supports it, since hid-quanta has been dropped from the kernel after 3.2) The module loads, but the device is not recognized. It does appear in lsusb: Bus 001 Device 011: ID 0408:3000 Quanta Computer, Inc. Optical dual- touch panel xinput --list does not see it: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ PixArt USB Optical Mouse id=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Power Button id=7[slave keyboard (3)] ↳ Sleep Button id=8[slave keyboard (3)] ↳ UVC Camera (046d:0821)id=10 [slave keyboard (3)] ↳ DELL Dell USB Entry Keyboard id=11 [slave keyboard (3)] There haven't been bug reports on Quanta touchscreens for years. My problem seems most similar to this one: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514310 O yes and the device properly works on Windows 10... I've exchanged the USB cable for another one. No solution. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: maarten1288 F pulseaudio /dev/snd/controlC1: maarten1288 F pulseaudio /dev/snd/controlC2: maarten1288 F pulseaudio /dev/snd/controlC0: maarten1288 F pulseaudio CurrentDesktop: KDE Date: Mon Mar 5 14:49:49 2018 HibernationDevice: RESUME=UUID=419dcb02-2bfc-4caf-8e07-3bf2c1faf2a2 InstallationDate: Installed on 2016-12-30 (429 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) IwConfig: enp5s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7971 ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=6bc48507-dba2-4e26-beb8-4d999a7aa978 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.169.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-26 (130 days ago) dmi.bios.date: 05/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.70 dmi.board.asset.tag: Default string dmi.board.name: B150 PC MATE (MS-7971) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.70:bd05/23/2016:svnMSI:pnMS-7971:pvr2.0:rvnMSI:rnB150PCMATE(MS-7971):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7971 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755228] Re: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1755228 Title: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755227 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756408] Re: linux: 4.15.0-13.14 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-development-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-development-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-development-workflow/prepare-package-signed Status: New => Confirmed ** Changed in: kernel-development-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-development-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Description changed: This bug is for tracking the 4.15.0-13.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - kernel-phase:Packaging - kernel-phase-changed:Friday, 16. March 2018 18:02 UTC - -- swm properties -- phase: Packaging + kernel-phase:Uploaded + kernel-phase-changed:Friday, 16. March 2018 21:02 UTC ** Description changed: This bug is for tracking the 4.15.0-13.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - phase: Packaging - kernel-phase:Uploaded - kernel-phase-changed:Friday, 16. March 2018 21:02 UTC + phase: 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/1756408 Title: linux: 4.15.0-13.14 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-13.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1756408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756367] Re: missing bnx2 firmware
This bug was fixed in the package linux-firmware - 1.173 --- linux-firmware (1.173) bionic; urgency=medium * missing bnx2 firmware (LP: #1756367) - Revert "UBUNTU: Remove obsolete bnx2 firmware" - Revert "UBUNTU: Remove obsolete bnx2 firmware" - UBUNTU: Add additional files to nic-firmware.lst -- Seth Forshee Fri, 16 Mar 2018 14:19:07 -0500 ** Changed in: linux-firmware (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1756367 Title: missing bnx2 firmware Status in linux-firmware package in Ubuntu: Fix Released Bug description: I'm getting the following error while trying to netboot the last few netboot installers (including the most recent, 20101020ubuntu534): bnx2 :06:00.0: Direct firmware load for bnx2/bnx2-rv2p-06-6.15.fw failed with error -2 bnx2: Can't load firmware file "bnx2/bnx2-rv2p-06-6.15.fw" It does indeed look like bnx2-rv2p-06-6.15.fw is referenced in bnx2.ko but the fw isn't in lib/firmware/bnx2/ Cheers, Brian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1756367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] [NEW] Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004
You have been subscribed to a public bug: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 https://bugs.launchpad.net/bugs/1756455 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed 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 1756455] [NEW] Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004
Public bug reported: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Package changed: linphone (Ubuntu) => linux-signed (Ubuntu) -- 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/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755210] Re: linux-aws: 4.4.0-1015.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1755208 phase: 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/1755210 Title: linux-aws: 4.4.0-1015.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 upload-to-ppa 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: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755208 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755217] Re: linux-aws: 4.4.0-1053.62 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1755208 phase: 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/1755217 Title: linux-aws: 4.4.0-1053.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755208 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755228] Re: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755227 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 16. March 2018 23:32 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755227 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 16. March 2018 23:32 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1755228 Title: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755227 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Ok so I didn't know exactly what to do. I was using my machine and even though I didn't get any errors I rebooted, entered ubuntu live image and did fsck on /dev/nvme0n1p1 and /dev/nvme0n1p2, no errors showed up Then I continued using my machine and the error appeared. I rebooted into the live machine and did fsck /dev/nvme0n1p2 and fsck /dev/nvme0n1p1 here are the outputs: https://pastebin.com/jpz5SwrR https://pastebin.com/xNMQPuVi (in the nvme0n1p1 I got dirty bit, don't know what is this, and in nvme0n1p2 the output looks the same as when I've run the fsck from the SSD) The error persists. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVers
[Kernel-packages] [Bug 1729736] Re: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile
With Linux kernel 4.16.0-041600rc5 from http://kernel.ubuntu.com /~kernel-ppa/mainline, 'lspci' systematically fails to answer, and makes the whole machine freeze after some time. ** Tags removed: kernel-bug-exists-upstream-4.15 ** Tags added: bionic kernel-bug-exists-upstream-4.16 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729736 Title: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10 (Artful)' : - Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically fails (1 CPU stuck). - Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel- ppa/mainline seems to succeed. See attached kern.log After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted : $ lspci -nn -v -s 1:0.0 01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 1050 Ti Mobile] [1462:11c8] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at de00 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [disabled] [size=128] Expansion ROM at df00 [disabled] [size=512K] Capabilities: Kernel modules: nvidiafb, nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1729736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1740197] Re: Laptop does not suspend (instead, it shuts down) when lid is closed
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1740197 Title: Laptop does not suspend (instead, it shuts down) when lid is closed Status in linux package in Ubuntu: Expired Bug description: After a recent kernel update, when I close my laptop lid, instead of suspending, my laptop shuts down. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 26 18:57:53 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=fc36807e-e60f-4bbf-82f0-e9db1e6e967a ro quiet splash vt.handoff=7 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-07 (49 days ago) dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.10 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.10:bd10/12/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742095] Re: kernel 4.13.0-24 not working with nvidia drivers, monitor flickering
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742095 Title: kernel 4.13.0-24 not working with nvidia drivers, monitor flickering Status in linux package in Ubuntu: Expired Bug description: After update to kernel 4.13.0-24 gnome will not start and the monitors will be flickering... It is impossible to see were it stops on the startup since the flickering is too fast (I may have to film it and pause to check) Running: Ubuntu 17.10, 64 bit OS HP ZBooks G2 15" with latest bios update Processor: Intel® Xeon(R) CPU E3-1505M v5 @ 2.80GHz × 8 Memory: 15.6 GB GNOME: 3.26.2 vanilla with nvidia-387 drivers System is working fine if I keep using kernel 4.13.0-22 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carlo 4669 F pulseaudio /dev/snd/controlC2: carlo 4669 F pulseaudio /dev/snd/controlC0: carlo 4669 F pulseaudio DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=/dev/mapper/vg-swap InstallationDate: Installed on 2016-04-25 (624 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: HP HP ZBook Studio G3 Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-24-generic root=/dev/mapper/vg-data ro ProcVersionSignature: Ubuntu 4.13.0-24.28-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-24-generic N/A linux-backports-modules-4.13.0-24-generic N/A linux-firmware 1.169.2 Tags: artful Uname: Linux 4.13.0-24-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (81 days ago) UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: HP dmi.bios.version: N82 Ver. 01.19 dmi.board.name: 80D4 dmi.board.vendor: HP dmi.board.version: KBC Version 11.6F dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN82Ver.01.19:bd09/26/2017:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ZBook Studio G3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756408] Re: linux: 4.15.0-13.14 -proposed tracker
** Changed in: kernel-development-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the 4.15.0-13.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true phase: 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/1756408 Title: linux: 4.15.0-13.14 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-13.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1756408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
Ok, we see some differences with the three kernels. How do we want to proceed from here? v4.12-rc3 - bad (24 of 90 - 26.6%) http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3/ v4.12-rc3 #201803151851 - relatively good (2 of 151 - 1.3%) http://kernel.ubuntu.com/~jsalisbury/lp1753662/v4.12-rc3/ (artful configs) v4.12-rc3 #201803161156 - relatively bad (36 or 249 - 14.5%) http://kernel.ubuntu.com/~jsalisbury/lp1753662/v4.12-rc3-xenial-configs/ (xenial configs) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp