[Kernel-packages] [Bug 1801986] Re: Cosmic update: 4.18.14 upstream stable release
** Changed in: linux (Ubuntu Cosmic) 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/1801986 Title: Cosmic update: 4.18.14 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.18.14 upstream stable release from git://git.kernel.org/ The following patches will be applied: * perf/core: Add sanity check to deal with pinned event failure * mm: migration: fix migration of huge PMD shared pages * mm, thp: fix mlocking THP page with migration enabled * mm/vmstat.c: skip NR_TLB_REMOTE_FLUSH* properly * KVM: VMX: check for existence of secondary exec controls before accessing * blk-mq: I/O and timer unplugs are inverted in blktrace * pstore/ram: Fix failure-path memory leak in ramoops_init * clocksource/drivers/timer-atmel-pit: Properly handle error cases * fbdev/omapfb: fix omapfb_memory_read infoleak * mmc: core: Fix debounce time to use microseconds * mmc: slot-gpio: Fix debounce time to use miliseconds again * mac80211: allocate TXQs for active monitor interfaces * drm/amdgpu: Fix vce work queue was not cancelled when suspend * drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set * drm: fix use-after-free read in drm_mode_create_lease_ioctl() * x86/vdso: Fix asm constraints on vDSO syscall fallbacks * selftests/x86: Add clock_gettime() tests to test_vdso * x86/vdso: Only enable vDSO retpolines when enabled and supported * x86/vdso: Fix vDSO syscall fallback asm constraint regression * Revert "UBUNTU: SAUCE: PCI: Reprogram bridge prefetch registers on resume" * PCI: Reprogram bridge prefetch registers on resume * mac80211: fix setting IEEE80211_KEY_FLAG_RX_MGMT for AP mode keys * PM / core: Clear the direct_complete flag on errors * dm mpath: fix attached_handler_name leak and dangling hw_handler_name pointer * dm cache metadata: ignore hints array being too small during resize * dm cache: fix resize crash if user doesn't reload cache table * xhci: Add missing CAS workaround for Intel Sunrise Point xHCI * usb: xhci-mtk: resume USB3 roothub first * USB: serial: simple: add Motorola Tetra MTP6550 id * USB: serial: option: improve Quectel EP06 detection * USB: serial: option: add two-endpoints device-id flag * usb: cdc_acm: Do not leak URB buffers * tty: Drop tty->count on tty_reopen() failure * of: unittest: Disable interrupt node tests for old world MAC systems * powerpc: Avoid code patching freed init sections * powerpc/lib: fix book3s/32 boot failure due to code patching * ARC: clone syscall to setp r25 as thread pointer * f2fs: fix invalid memory access * tipc: call start and done ops directly in __tipc_nl_compat_dumpit() * ucma: fix a use-after-free in ucma_resolve_ip() * ubifs: Check for name being NULL while mounting * rds: rds_ib_recv_alloc_cache() should call alloc_percpu_gfp() instead * ath10k: fix scan crash due to incorrect length calculation * Linux 4.18.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802119] Re: Cosmic update: 4.18.17 upstream stable release
** Changed in: linux (Ubuntu Cosmic) 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/1802119 Title: Cosmic update: 4.18.17 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.18.17 upstream stable release from git://git.kernel.org/ The following patches will be applied: * xfrm: Validate address prefix lengths in the xfrm selector. * xfrm6: call kfree_skb when skb is toobig * xfrm: reset transport header back to network header after all input transforms ahave been applied * xfrm: reset crypto_done when iterating over multiple input xfrms * mac80211: Always report TX status * cfg80211: reg: Init wiphy_idx in regulatory_hint_core() * mac80211: fix pending queue hang due to TX_DROP * cfg80211: Address some corner cases in scan result channel updating * mac80211: TDLS: fix skb queue/priority assignment * mac80211: fix TX status reporting for ieee80211s * xfrm: Fix NULL pointer dereference when skb_dst_force clears the dst_entry. * ARM: 8799/1: mm: fix pci_ioremap_io() offset check * xfrm: validate template mode * drm/i2c: tda9950: fix timeout counter check * drm/i2c: tda9950: set MAX_RETRIES for errors only * netfilter: bridge: Don't sabotage nf_hook calls from an l3mdev * netfilter: conntrack: get rid of double sizeof * arm64: hugetlb: Fix handling of young ptes * ARM: dts: BCM63xx: Fix incorrect interrupt specifiers * net: macb: Clean 64b dma addresses if they are not detected * soc: fsl: qbman: qman: avoid allocating from non existing gen_pool * soc: fsl: qe: Fix copy/paste bug in ucc_get_tdm_sync_shift() * nl80211: Fix possible Spectre-v1 for NL80211_TXRATE_HT * mac80211_hwsim: fix locking when iterating radios during ns exit * mac80211_hwsim: fix race in radio destruction from netlink notifier * mac80211_hwsim: do not omit multicast announce of first added radio * Bluetooth: SMP: fix crash in unpairing * pxa168fb: prepare the clock * qed: Avoid implicit enum conversion in qed_set_tunn_cls_info * qed: Fix mask parameter in qed_vf_prep_tunn_req_tlv * qed: Avoid implicit enum conversion in qed_roce_mode_to_flavor * qed: Avoid constant logical operation warning in qed_vf_pf_acquire * qed: Avoid implicit enum conversion in qed_iwarp_parse_rx_pkt * nl80211: Fix possible Spectre-v1 for CQM RSSI thresholds * scsi: qedi: Initialize the stats mutex lock * rxrpc: Fix checks as to whether we should set up a new call * rxrpc: Fix RTT gathering * rxrpc: Fix transport sockopts to get IPv4 errors on an IPv6 socket * rxrpc: Fix error distribution * netfilter: nft_set_rbtree: add missing rb_erase() in GC routine * netfilter: avoid erronous array bounds warning * asix: Check for supported Wake-on-LAN modes * ax88179_178a: Check for supported Wake-on-LAN modes * lan78xx: Check for supported Wake-on-LAN modes * sr9800: Check for supported Wake-on-LAN modes * r8152: Check for supported Wake-on-LAN Modes * smsc75xx: Check for Wake-on-LAN modes * smsc95xx: Check for Wake-on-LAN modes * cfg80211: fix use-after-free in reg_process_hint() * KVM: nVMX: Do not expose MPX VMX controls when guest MPX disabled * KVM: x86: Do not use kvm_x86_ops->mpx_supported() directly * KVM: nVMX: Fix emulation of VM_ENTRY_LOAD_BNDCFGS * perf/core: Fix perf_pmu_unregister() locking * perf/x86/intel/uncore: Use boot_cpu_data.phys_proc_id instead of hardcorded physical package ID 0 * perf/ring_buffer: Prevent concurent ring buffer access * perf/x86/intel/uncore: Fix PCI BDF address of M3UPI on SKX * perf/x86/amd/uncore: Set ThreadMask and SliceMask for L3 Cache perf events * thunderbolt: Do not handle ICM events after domain is stopped * thunderbolt: Initialize after IOMMUs * net: fec: fix rare tx timeout * declance: Fix continuation with the adapter identification message * RISCV: Fix end PFN for low memory * Revert "serial: 8250_dw: Fix runtime PM handling" * locking/ww_mutex: Fix runtime warning in the WW mutex selftest * drm/amd/display: Signal hw_done() after waiting for flip_done() * be2net: don't flip hw_features when VXLANs are added/deleted * powerpc/numa: Skip onlining a offline node in kdump path * net: cxgb3_main: fix a missing-check bug * yam: fix a missing-check bug *
[Kernel-packages] [Bug 1802100] Re: Cosmic update: 4.18.16 upstream stable release
** Changed in: linux (Ubuntu Cosmic) 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/1802100 Title: Cosmic update: 4.18.16 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.18.16 upstream stable release from git://git.kernel.org/ The following patches will be applied: * soundwire: Fix duplicate stream state assignment * soundwire: Fix incorrect exit after configuring stream * soundwire: Fix acquiring bus lock twice during master release * media: af9035: prevent buffer overflow on write * spi: gpio: Fix copy-and-paste error * batman-adv: Avoid probe ELP information leak * batman-adv: Fix segfault when writing to throughput_override * batman-adv: Fix segfault when writing to sysfs elp_interval * batman-adv: Prevent duplicated gateway_node entry * batman-adv: Prevent duplicated nc_node entry * batman-adv: Prevent duplicated softif_vlan entry * batman-adv: Prevent duplicated global TT entry * batman-adv: Prevent duplicated tvlv handler * batman-adv: fix backbone_gw refcount on queue_work() failure * batman-adv: fix hardif_neigh refcount on queue_work() failure * cxgb4: fix abort_req_rss6 struct * clocksource/drivers/ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs * scsi: ibmvscsis: Fix a stringop-overflow warning * scsi: ibmvscsis: Ensure partition name is properly NUL terminated * intel_th: pci: Add Ice Lake PCH support * Input: atakbd - fix Atari keymap * Input: atakbd - fix Atari CapsLock behaviour * selftests: pmtu: properly redirect stderr to /dev/null * net: emac: fix fixed-link setup for the RTL8363SB switch * ravb: do not write 1 to reserved bits * net/smc: fix non-blocking connect problem * net/smc: fix sizeof to int comparison * qed: Fix populating the invalid stag value in multi function mode. * qed: Do not add VLAN 0 tag to untagged frames in multi-function mode. * PCI: dwc: Fix scheduling while atomic issues * RDMA/uverbs: Fix validity check for modify QP * scsi: lpfc: Synchronize access to remoteport via rport * drm: mali-dp: Call drm_crtc_vblank_reset on device init * scsi: ipr: System hung while dlpar adding primary ipr adapter back * scsi: sd: don't crash the host on invalid commands * bpf: sockmap only allow ESTABLISHED sock state * bpf: sockmap, fix transition through disconnect without close * bpf: test_maps, only support ESTABLISHED socks * net/mlx4: Use cpumask_available for eq->affinity_mask * clocksource/drivers/fttmr010: Fix set_next_event handler * RDMA/bnxt_re: Fix system crash during RDMA resource initialization * RISC-V: include linux/ftrace.h in asm-prototypes.h * iommu/rockchip: Free irqs in shutdown handler * pinctrl/amd: poll InterruptEnable bits in amd_gpio_irq_set_type * powerpc/tm: Fix userspace r13 corruption * powerpc/tm: Avoid possible userspace r1 corruption on reclaim * powerpc/numa: Use associativity if VPHN hcall is successful * iommu/amd: Return devid as alias for ACPI HID devices * x86/boot: Fix kexec booting failure in the SEV bit detection code * Revert "vfs: fix freeze protection in mnt_want_write_file() for overlayfs" * mremap: properly flush TLB before releasing the page * ARC: build: Get rid of toolchain check * ARC: build: Don't set CROSS_COMPILE in arch's Makefile * Linux 4.18.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801931] Re: Cosmic update: 4.18.13 upstream stable release
** Changed in: linux (Ubuntu Cosmic) 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/1801931 Title: Cosmic update: 4.18.13 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.18.13 upstream stable release from git://git.kernel.org/ The following patches will be applied: * rseq/selftests: fix parametrized test with -fpie * mac80211: Run TXQ teardown code before de-registering interfaces * mac80211_hwsim: require at least one channel * Btrfs: fix unexpected failure of nocow buffered writes after snapshotting when low on space * KVM: PPC: Book3S HV: Don't truncate HPTE index in xlate function * cfg80211: remove division by size of sizeof(struct ieee80211_wmm_rule) * btrfs: btrfs_shrink_device should call commit transaction at the end * scsi: csiostor: add a check for NULL pointer after kmalloc() * scsi: csiostor: fix incorrect port capabilities * scsi: libata: Add missing newline at end of file * scsi: aacraid: fix a signedness bug * bpf, sockmap: fix potential use after free in bpf_tcp_close * bpf, sockmap: fix psock refcount leak in bpf_tcp_recvmsg * bpf: sockmap, decrement copied count correctly in redirect error case * mac80211: correct use of IEEE80211_VHT_CAP_RXSTBC_X * mac80211_hwsim: correct use of IEEE80211_VHT_CAP_RXSTBC_X * cfg80211: make wmm_rule part of the reg_rule structure * mac80211_hwsim: Fix possible Spectre-v1 for hwsim_world_regdom_custom * nl80211: Fix nla_put_u8 to u16 for NL80211_WMMR_TXOP * nl80211: Pass center frequency in kHz instead of MHz * bpf: fix several offset tests in bpf_msg_pull_data * gpio: adp5588: Fix sleep-in-atomic-context bug * mac80211: mesh: fix HWMP sequence numbering to follow standard * mac80211: avoid kernel panic when building AMSDU from non-linear SKB * gpiolib: acpi: Switch to cansleep version of GPIO library call * gpiolib-acpi: Register GpioInt ACPI event handlers from a late_initcall * gpio: dwapb: Fix error handling in dwapb_gpio_probe() * bpf: fix msg->data/data_end after sg shift repair in bpf_msg_pull_data * bpf: fix shift upon scatterlist ring wrap-around in bpf_msg_pull_data * bpf: fix sg shift repair start offset in bpf_msg_pull_data * tipc: switch to rhashtable iterator * sh_eth: Add R7S9210 support * net: mvpp2: initialize port of_node pointer * tc-testing: add test-cases for numeric and invalid control action * cfg80211: nl80211_update_ft_ies() to validate NL80211_ATTR_IE * mac80211: do not convert to A-MSDU if frag/subframe limited * mac80211: always account for A-MSDU header changes * tools/kvm_stat: fix python3 issues * tools/kvm_stat: fix handling of invalid paths in debugfs provider * tools/kvm_stat: fix updates for dead guests * gpio: Fix crash due to registration race * ARC: atomics: unbork atomic_fetch_##op() * Revert "blk-throttle: fix race between blkcg_bio_issue_check() and cgroup_rmdir()" * md/raid5-cache: disable reshape completely * RAID10 BUG_ON in raise_barrier when force is true and conf->barrier is 0 * selftests: pmtu: maximum MTU for vti4 is 2^16-1-20 * selftests: pmtu: detect correct binary to ping ipv6 addresses * ibmvnic: Include missing return code checks in reset function * bpf: Fix bpf_msg_pull_data() * bpf: avoid misuse of psock when TCP_ULP_BPF collides with another ULP * i2c: uniphier: issue STOP only for last message or I2C_M_STOP * i2c: uniphier-f: issue STOP only for last message or I2C_M_STOP * net: cadence: Fix a sleep-in-atomic-context bug in macb_halt_tx() * fs/cifs: don't translate SFM_SLASH (U+F026) to backslash * mac80211: fix an off-by-one issue in A-MSDU max_subframe computation * cfg80211: fix a type issue in ieee80211_chandef_to_operating_class() * mac80211: fix WMM TXOP calculation * mac80211: fix a race between restart and CSA flows * mac80211: Fix station bandwidth setting after channel switch * mac80211: don't Tx a deauth frame if the AP forbade Tx * mac80211: shorten the IBSS debug messages * fsnotify: fix ignore mask logic in fsnotify() * net/ibm/emac: wrong emac_calc_base call was used by typo * nds32: fix logic for module * nds32: add NULL entry to the end of_device_id array * nds32: Fix empty call trace * nds32: Fix get_user/put_user
[Kernel-packages] [Bug 1802082] Re: Cosmic update: 4.18.15 upstream stable release
** Changed in: linux (Ubuntu Cosmic) 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/1802082 Title: Cosmic update: 4.18.15 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.18.15 upstream stable release from git://git.kernel.org/ The following patches will be applied: * bnxt_en: Fix TX timeout during netpoll. * bnxt_en: free hwrm resources, if driver probe fails. * bonding: avoid possible dead-lock * ip6_tunnel: be careful when accessing the inner header * ip_tunnel: be careful when accessing the inner header * ipv4: fix use-after-free in ip_cmsg_recv_dstaddr() * ipv6: take rcu lock in rawv6_send_hdrinc() * net: dsa: bcm_sf2: Call setup during switch resume * net: hns: fix for unmapping problem when SMMU is on * net: ipv4: update fnhe_pmtu when first hop's MTU changes * net/ipv6: Display all addresses in output of /proc/net/if_inet6 * netlabel: check for IPV4MASK in addrinfo_get * net: mvpp2: Extract the correct ethtype from the skb for tx csum offload * net: mvpp2: fix a txq_done race condition * net: sched: Add policy validation for tc attributes * net: sched: cls_u32: fix hnode refcounting * net: systemport: Fix wake-up interrupt race during resume * net/usb: cancel pending work when unbinding smsc75xx * qlcnic: fix Tx descriptor corruption on 82xx devices * qmi_wwan: Added support for Gemalto's Cinterion ALASxx WWAN interface * rtnl: limit IFLA_NUM_TX_QUEUES and IFLA_NUM_RX_QUEUES to 4096 * sctp: update dst pmtu with the correct daddr * team: Forbid enslaving team device to itself * tipc: fix flow control accounting for implicit connect * udp: Unbreak modules that rely on external __skb_recv_udp() availability * net: qualcomm: rmnet: Skip processing loopback packets * net: qualcomm: rmnet: Fix incorrect allocation flag in transmit * net: qualcomm: rmnet: Fix incorrect allocation flag in receive path * tun: remove unused parameters * tun: initialize napi_mutex unconditionally * tun: napi flags belong to tfile * net: stmmac: Fixup the tail addr setting in xmit path * net/packet: fix packet drop as of virtio gso * net: dsa: bcm_sf2: Fix unbind ordering * net/mlx5e: Set vlan masks for all offloaded TC rules * net: aquantia: memory corruption on jumbo frames * net/mlx5: E-Switch, Fix out of bound access when setting vport rate * bonding: pass link-local packets to bonding master also. * bonding: fix warning message * net: stmmac: Rework coalesce timer and fix multi-queue races * nfp: avoid soft lockups under control message storm * bnxt_en: don't try to offload VLAN 'modify' action * net-ethtool: ETHTOOL_GUFO did not and should not require CAP_NET_ADMIN * net: phy: phylink: fix SFP interface autodetection * sfp: fix oops with ethtool -m * tcp/dccp: fix lockdep issue when SYN is backlogged * inet: make sure to grab rcu_read_lock before using ireq->ireq_opt * net: dsa: b53: Keep CPU port as tagged in all VLANs * rtnetlink: Fail dump if target netnsid is invalid * bnxt_en: Fix VNIC reservations on the PF. * net: ipv4: don't let PMTU updates increase route MTU * net/mlx5: Check for SQ and not RQ state when modifying hairpin SQ * bnxt_en: Fix enables field in HWRM_QUEUE_COS2BW_CFG request * bnxt_en: get the reduced max_irqs by the ones used by RDMA * net/ipv6: Remove extra call to ip6_convert_metrics for multipath case * net/ipv6: stop leaking percpu memory in fib6 info * net: mscc: fix the frame extraction into the skb * qed: Fix shmem structure inconsistency between driver and the mfw. * r8169: fix network stalls due to missing bit TXCFG_AUTO_FIFO * r8169: set RX_MULTI_EN bit in RxConfig for 8168F-family chips * vxlan: fill ttl inherit info * ASoC: dapm: Fix NULL pointer deference on CODEC to CODEC DAIs * ASoC: max98373: Added speaker FS gain cotnrol register to volatile. * ASoC: rt5514: Fix the issue of the delay volume applied again * selftests: android: move config up a level * selftests: kselftest: Remove outdated comment * ASoC: max98373: Added 10ms sleep after amp software reset * ASoC: wm8804: Add ACPI support * ASoC: sigmadsp: safeload should not have lower byte limit * ASoC: q6routing: initialize data correctly * selftests: add
[Kernel-packages] [Bug 1802248] [NEW] Disable LPM for Raydium Touchscreens
Public bug reported: [Impact] Raydium touchscreens don't work on LPM capable platforms. [Test] Raydium touchscreens start to work with the patch. [Fix] Disable LPM for Raydium touchscreens. [Regression Potential] Low. Limits to specific Raydium touchscreens. Also, USB runtime PM (SeletiveSuspend) still works, so disabling LPM doesn't really increase power consumption. ** 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/1802248 Title: Disable LPM for Raydium Touchscreens Status in linux package in Ubuntu: New Bug description: [Impact] Raydium touchscreens don't work on LPM capable platforms. [Test] Raydium touchscreens start to work with the patch. [Fix] Disable LPM for Raydium touchscreens. [Regression Potential] Low. Limits to specific Raydium touchscreens. Also, USB runtime PM (SeletiveSuspend) still works, so disabling LPM doesn't really increase power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801893] Re: Xenial update: 4.4.161 upstream stable release
** Changed in: linux (Ubuntu) Status: New => 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/1801893 Title: Xenial update: 4.4.161 upstream stable release Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.161 upstream stable release from git://git.kernel.org/ The following patches will be applied: * mm/vmstat.c: skip NR_TLB_REMOTE_FLUSH* properly * fbdev/omapfb: fix omapfb_memory_read infoleak * x86/vdso: Fix asm constraints on vDSO syscall fallbacks * x86/vdso: Fix vDSO syscall fallback asm constraint regression * PCI: Reprogram bridge prefetch registers on resume * mac80211: fix setting IEEE80211_KEY_FLAG_RX_MGMT for AP mode keys * PM / core: Clear the direct_complete flag on errors * dm cache: fix resize crash if user doesn't reload cache table * xhci: Add missing CAS workaround for Intel Sunrise Point xHCI * USB: serial: simple: add Motorola Tetra MTP6550 id * of: unittest: Disable interrupt node tests for old world MAC systems * ext4: always verify the magic number in xattr blocks * cgroup: Fix deadlock in cpu hotplug path * ath10k: fix use-after-free in ath10k_wmi_cmd_send_nowait * powerpc/fadump: Return error when fadump registration fails * ARC: clone syscall to setp r25 as thread pointer * ucma: fix a use-after-free in ucma_resolve_ip() * ubifs: Check for name being NULL while mounting * tcp: increment sk_drops for dropped rx packets * tcp: use an RB tree for ooo receive queue * tcp: fix a stale ooo_last_skb after a replace * tcp: free batches of packets in tcp_prune_ofo_queue() * tcp: call tcp_drop() from tcp_data_queue_ofo() * tcp: add tcp_ooo_try_coalesce() helper * ath10k: fix scan crash due to incorrect length calculation * ebtables: arpreply: Add the standard target sanity check * Linux 4.4.161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800537] Re: Bionic update: upstream stable patchset 2018-10-29
** 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/1800537 Title: Bionic update: upstream stable patchset 2018-10-29 Status in linux package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2018-10-29 (ported from v4.14.52 and v4.16.18) from git://git.kernel.org/ genirq/migration: Avoid out of line call if pending is not set genirq/affinity: Defer affinity setting if irq chip is busy genirq/generic_pending: Do not lose pending affinity update irq_remapping: Use apic_ack_irq() x86/platform/uv: Use apic_ack_irq() x86/ioapic: Use apic_ack_irq() x86/apic: Provide apic_ack_irq() x86/apic/vector: Prevent hlist corruption and leaks x86/vector: Fix the args of vector_alloc tracepoint cpufreq: ti-cpufreq: Fix an incorrect error return value net: phy: dp83822: use BMCR_ANENABLE instead of BMSR_ANEGCAPABLE for DP83620 mm, page_alloc: do not break __GFP_THISNODE by zonelist reset HID: wacom: Correct logical maximum Y for 2nd-gen Intuos Pro large HID: intel_ish-hid: ipc: register more pm callbacks to support hibernation orangefs: report attributes_mask and attributes for statx orangefs: set i_size on new symlink iwlwifi: fw: harden page loading code x86/intel_rdt: Enable CMT and MBM on new Skylake stepping w1: mxc_w1: Enable clock before calling clk_get_rate() on it libata: Drop SanDisk SD7UB3Q*G1001 NOLPM quirk libata: zpodd: small read overflow in eject_tray() cpufreq: governors: Fix long idle detection logic in load calculation cpufreq: Fix new policy initialization during limits updates via sysfs bdi: Move cgroup bdi_writeback to a dedicated low concurrency workqueue blk-mq: reinit q->tag_set_list entry only after grace period nbd: use bd_set_size when updating disk size nbd: update size when connected nbd: fix nbd device deletion cifs: For SMB2 security informaion query, check for minimum sized security descriptor instead of sizeof FileAllInformation class CIFS: 511c54a2f69195b28afb9dd119f03787b1625bb4 adds a check for session expiry smb3: fix various xid leaks x86/MCE: Fix stack out-of-bounds write in mce-inject.c: Flags_read() ALSA: hda: add dock and led support for HP ProBook 640 G4 ALSA: hda: add dock and led support for HP EliteBook 830 G5 ALSA: hda - Handle kzalloc() failure in snd_hda_attach_pcm_stream() ALSA: hda/conexant - Add fixup for HP Z2 G4 workstation btrfs: scrub: Don't use inode pages for device replace btrfs: return error value if create_io_em failed in cow_file_range Btrfs: fix memory and mount leak in btrfs_ioctl_rm_dev_v2() Btrfs: fix clone vs chattr NODATASUM race driver core: Don't ignore class_dir_create_and_add() failure. ext4: fix fencepost error in check for inode count overflow during resize ext4: bubble errors from ext4_find_inline_data_nolock() up to ext4_iget() ext4: update mtime in ext4_punch_hole even if no blocks are released ext4: fix hole length detection in ext4_ind_map_blocks() tls: fix use-after-free in tls_push_record net: in virtio_net_hdr only add VLAN_HLEN to csum_start if payload holds vlan udp: fix rx queue len reported by diag and proc interface tcp: verify the checksum of the first data segment in a new connection net/sched: act_simple: fix parsing of TCA_DEF_DATA net: dsa: add error handling for pskb_trim_rcsum ipv6: allow PMTU exceptions to local routes cdc_ncm: avoid padding beyond end of skb bonding: re-evaluate force_primary when the primary slave name changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801900] Re: Xenial update: 4.4.162 upstream stable release
** Changed in: linux (Ubuntu) Status: New => 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/1801900 Title: Xenial update: 4.4.162 upstream stable release Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.162 upstream stable release from git://git.kernel.org/ Linux 4.4.162 HV: properly delay KVP packets when negotiation is in progress Drivers: hv: kvp: fix IP Failover Drivers: hv: util: Pass the channel information during the init call Drivers: hv: utils: Invoke the poll function after handshake usb: gadget: serial: fix oops when data rx'd after close ARC: build: Get rid of toolchain check powerpc/tm: Avoid possible userspace r1 corruption on reclaim powerpc/tm: Fix userspace r13 corruption net/mlx4: Use cpumask_available for eq->affinity_mask Input: atakbd - fix Atari CapsLock behaviour Input: atakbd - fix Atari keymap clocksource/drivers/ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs media: af9035: prevent buffer overflow on write x86/fpu: Finish excising 'eagerfpu' x86/fpu: Remove struct fpu::counter x86/fpu: Remove use_eager_fpu() KVM: x86: remove eager_fpu field of struct kvm_vcpu_arch rtnl: limit IFLA_NUM_TX_QUEUES and IFLA_NUM_RX_QUEUES to 4096 net: systemport: Fix wake-up interrupt race during resume net: mvpp2: Extract the correct ethtype from the skb for tx csum offload team: Forbid enslaving team device to itself qlcnic: fix Tx descriptor corruption on 82xx devices net/usb: cancel pending work when unbinding smsc75xx netlabel: check for IPV4MASK in addrinfo_get net/ipv6: Display all addresses in output of /proc/net/if_inet6 net: ipv4: update fnhe_pmtu when first hop's MTU changes ipv4: fix use-after-free in ip_cmsg_recv_dstaddr() ip_tunnel: be careful when accessing the inner header ip6_tunnel: be careful when accessing the inner header bonding: avoid possible dead-lock bnxt_en: Fix TX timeout during netpoll. jffs2: return -ERANGE when xattr buffer is too small xhci: Don't print a warning when setting link state for disabled ports i2c: i2c-scmi: fix for i2c_smbus_write_block_data perf script python: Fix export-to-postgresql.py occasional failure mach64: detect the dot clock divider correctly on sparc mm/vmstat.c: fix outdated vmstat_text ext4: add corruption check in ext4_xattr_set_entry() drm/amdgpu: Fix SDMA HQD destroy error on gfx_v7 ARM: dts: at91: add new compatibility string for macb on sama5d3 net: macb: disable scatter-gather for macb on sama5d3 stmmac: fix valid numbers of unicast filter entries sound: enable interrupt after dma buffer initialization mfd: omap-usb-host: Fix dts probe of children selftests/efivarfs: add required kernel configs ASoC: sigmadsp: safeload should not have lower byte limit ASoC: wm8804: Add ACPI support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799276] Re: [Bionic] ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver
** 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/1799276
Title:
[Bionic] ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
The IPMI spec states:
The purpose of the SPMI Table is to provide a mechanism that can be
used by the OSPM (an ACPI term for “OS Operating System-directed
configuration and Power Management” essentially meaning an ACPI-aware
OS or OS loader) very early in the boot process, e.g., before the
ability to execute ACPI control methods in the OS is available.
When we are probing IPMI in Linux, ACPI control methods are available,
so we shouldn't be probing using SPMI. It could cause some confusion
during the probing process.
[Fix]
Fixed upstream in 4.17:
commit 4866b1dce0389013a268f0ab63f7229b30c6e5fe
Author: Corey Minyard
Date: Thu Mar 8 15:00:28 2018 -0600
ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver
[Test]
-- Test case --
for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe
ipmi_ssif || exit; done
--
-- Before Applying the patch --
Jun 19 18:53:04 starbuck kernel: [ 126.351580] ipmi_ssif 0-000e: Found new
BMC (man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)
Jun 19 18:53:06 starbuck kernel: [ 128.725391] ipmi_ssif: probe of
dmi-ipmi-ssif.1 failed with error -17
-- With patch applied --
Oct 19 19:59:49 starbuck kernel: [ 1501.699109] IPMI SSIF Interface driver
Oct 19 19:59:49 starbuck kernel: [ 1501.730439] ipmi_ssif: Trying
SMBIOS-specified SSIF interface at i2c address 0xe, adapter xlp9xx-i2c, slave
address 0x20
Oct 19 19:59:49 starbuck kernel: [ 1501.862509] ipmi_ssif 0-000e: Found new
BMC (man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)
[Regression Potential]
This patch applies to ipmi_ssif driver and was tested on ARM64 Cavium
ThunderX2 platform and no regressions were found.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799276/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799281] Re: [Bionic][Cosmic] ipmi: Fix timer race with module unload
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
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/1799281
Title:
[Bionic][Cosmic] ipmi: Fix timer race with module unload
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
If you attempt to remove and insert the ipmi_ssif module a number of times,
it would result in a kernel panic. This is due to mod_timer from arming a timer
that was already removed by del_timer during module unload.
[Fix]
In linux-next:
0711e8c1b457 ipmi: Fix timer race with module unload
[Test]
-- Test Case --
for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe
ipmi_ssif || exit; done
After the patch was applied, no kernel panics were obsereved. Tested on
Cavium ThunderX2.
[Regression Risk]
The patch was applied to bionic and tested tested on a Cavium ThunderX2 and
no regressions were found. Risk of regression none.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799281/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793451] Re: mlock203 test in ubuntu_ltp_syscalls failed with Xenial kernel
** Changed in: linux (Ubuntu Xenial) Status: New => 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/1793451 Title: mlock203 test in ubuntu_ltp_syscalls failed with Xenial kernel Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: == Justification == When one vma was with flag VM_LOCKED|VM_LOCKONFAULT (by invoking mlock2(,MLOCK_ONFAULT)), it can again be populated with mlock() with VM_LOCKED flag only. There is a hole in mlock_fixup() which increase mm->locked_vm twice even the two operations are on the same vma and both with VM_LOCKED flags. The issue can be reproduced by following code: mlock2(p, 1024 * 64, MLOCK_ONFAULT); //VM_LOCKED|VM_LOCKONFAULT mlock(p, 1024 * 64); //VM_LOCKED Then check the increase VmLck field in /proc/pid/status(to 128k). When vma is set with different vm_flags, and the new vm_flags is with VM_LOCKED, it is not necessarily be a "new locked" vma. There is a dedicated reproducer, the "mlock203" test in ubuntu_ltp_syscalls, you can see the failure for all the Ubuntu 4.4 kernel: <<>> tag=mlock203 stime=1537369891 cmdline="mlock203" contacts="" analysis=exit <<>> tst_test.c:1063: INFO: Timeout per run is 0h 05m 00s mlock203.c:63: FAIL: Locking one memory again increased VmLck Summary: passed 0 failed 1 skipped 0 warnings 0 == Fix == b155b4fd (mm: mlock: avoid increase mm->locked_vm on mlock() when already mlock2(,MLOCK_ONFAULT)) A test kernel for Xenial / Xenial-KVM could be found here: http://people.canonical.com/~phlin/kernel/lp-1793451-mlock203/ == Regression Potential == Low, this patch prevents mm->locked_vm from increment just by adding an extra check to see if the old vm_flags is already VM_LOCKED. == Test Case == Run the mlock203 test in ubuntu_ltp_syscalls test suite. And it will pass with the patched kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1068-aws 4.4.0-1068.78 ProcVersionSignature: User Name 4.4.0-1068.78-aws 4.4.144 Uname: Linux 4.4.0-1068-aws x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Sep 20 06:44:13 2018 Ec2AMI: ami-0e32ec5bc225539f5 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: c3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1793451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786729] Re: execveat03 in ubuntu_ltp_syscalls failed on X/B
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** 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/1786729
Title:
execveat03 in ubuntu_ltp_syscalls failed on X/B
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux-aws source package in Xenial:
New
Status in linux source package in Bionic:
Fix Committed
Status in linux-aws source package in Bionic:
New
Bug description:
== Justification ==
The code in cap_inode_getsecurity(), introduced by commit 8db6c34f1dbc
("Introduce v3 namespaced file capabilities"), should use
d_find_any_alias() instead of d_find_alias() do handle unhashed dentry
correctly. This is needed, for example, if execveat() is called with an
open but unlinked overlayfs file, because overlayfs unhashes dentry on
unlink.
This is a regression of real life application, first reported at
https://www.spinics.net/lists/linux-unionfs/msg05363.html
With the execveat03 test in the LTP test suite on an affected kernel, it will
fail with:
<<>>
tag=execveat03 stime=1534135632
cmdline="execveat03"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
execveat03.c:70: FAIL: execveat() returned unexpected errno: EINVAL
Summary:
passed 0
failed 1
skipped 0
warnings 0
== Fix ==
355139a8 (cap_inode_getsecurity: use d_find_any_alias() instead of
d_find_alias())
It can be cherry-picked for Bionic, but it needs to be backported to
Xenial along with the logic when we backport 8db6c34f1dbc (bug
1778286).
The test kernel for Xenial / Bionic could be found here:
http://people.canonical.com/~phlin/kernel/lp-1786729-execveat03/
This patch has already been cherry-picked into Cosmic and Unstable.
== Regression Potential ==
Low, this patch just uses a correct function to handle unhashed dentry, and
it's been applied in both upstream and our newer kernel.
== Test Case ==
Run the reproducer in the commit message, or,
run the execveat03 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1064-aws 4.4.0-1064.74
ProcVersionSignature: User Name 4.4.0-1064.74-aws 4.4.140
Uname: Linux 4.4.0-1064-aws x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Mon Aug 13 04:51:09 2018
Ec2AMI: ami-529fb82a
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2b
Ec2InstanceType: x1e.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: linux-aws
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1786729/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799411] Re: linux: 4.15.0-39.42 -proposed tracker
4.15.0-39.42 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_ecryptfs - should be skipped ubuntu_kvm_unit_tests - 29 failed on amaura, 17 failed on gummo, 14 failed on michael, 25 failed on pepe ubuntu_ltp - growfiles test eat up all the disk space (bug 1790445) ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) getrandom02 timed out (bug 1797327) msgstress03 (bug 1797341) ubuntu_performance_fio_aws - test for nvidia project, should be skipped ubuntu_performance_pts_aws - test for nvidia project, should be skipped ubuntu_qrt_apparmor - python package installation issue (bug 1799206), passed after re-test ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test ubuntu_qrt_kernel_security - python package installation issue (bug 1799206), passed after re-test xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_bpf - test_map failed (bug 1788562) ubuntu_ecryptfs - should be skipped ubuntu_kvm_smoke_test - Unable to boot Xenial cloud image on Bionic ARM64 ThunderX / Azure (bug 1765668) ubuntu_kvm_unit_tests - gicv3-ipi and gicv3-active failed on Moonshot (bug 1790825) ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) ubuntu_qrt_apparmor - python package installation issue (bug 1799206), passed after re-test ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in i386: ubuntu_bpf - Some test in test_verifier failed on i386 Bionic (bug 1788578) ubuntu_ecryptfs - should be skipped subuntu_kvm_unit_tests - 29 failed on pepe ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in ppc64le (P8): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_ecryptfs - should be skipped ubuntu_kvm_smoke_test - test case issue, KVM works fine ubuntu_kvm_unit_tests - sprs timed out (bug 1740017) ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) fallocate05 (bug 1783880) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) ubuntu_qrt_apparmor - python package installation issue (bug 1799206), passed after re-test ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test ubuntu_vfat_stress - can only be triggered when running with the test suite (bug 1801907) xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in ppc64le (P9): hwclock - hwclock test failed on Power9 due to 0.02 sec differences (bug 1802233) ubuntu_bpf - test_map failed (bug 1788562) ubuntu_ecryptfs - should be skipped ubuntu_kvm_unit_tests - sprs timed out (bug 1740017) ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) fallocate05 (bug 1783880) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) ubuntu_qrt_apparmor - python package installation issue (bug 1799206), passed after re-test ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test Issue to note in s390x (Ubuntu on LPAR): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) ubuntu_lxc - lxc-test-api-reboot failed (bug 1776381) Container "reboot" is defined (bug 1788574) ubuntu_qrt_apparmor - passed after re-test Issue to note in s390x (zKVM): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kvm_unit_tests - No KVM support on zKVM ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) ubuntu_lxc - Container "reboot" is defined (bug 1788574) ubuntu_qrt_kernel_security - sysdig module should be removed after test (bug 1798295) Issue to note in s390x (zVM): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kvm_unit_tests - skey failed (bug 1778705) ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) ubuntu_lxc - Container "reboot" is defined (bug 1788574) ubuntu_nbd_smoke_test - passed after re-test ubuntu_qrt_kernel_security - sysdig module should be removed after test (bug 1798295) Note: No xfstests for P9 as it does not have a scratch drive ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in
[Kernel-packages] [Bug 1799411] Re: linux: 4.15.0-39.42 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1800788 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) kernel-stable-phase-changed:Tuesday, 23. October 2018 16:06 UTC kernel-stable-phase:Uploaded -- swm properties -- backports: null boot-testing-requested: true bugs-spammed: true derivatives: null phase: Uploaded reason: - regression-testing: Testing in progress verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799411 Title: linux: 4.15.0-39.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1800788 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) kernel-stable-phase-changed:Tuesday, 23. October 2018 16:06 UTC kernel-stable-phase:Uploaded -- swm properties -- backports: null boot-testing-requested: true bugs-spammed: true derivatives: null phase: Uploaded reason: verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784501] Re: libvirtd is unable to configure bridge devices inside of LXD containers
** 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/1784501 Title: libvirtd is unable to configure bridge devices inside of LXD containers Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] libvirtd cannot properly configure the default bridge device when installed inside of unprivileged LXD containers. 'systemctl status libvirtd' shows the following error: error : virNetDevBridgeSet:140 : Unable to set bridge virbr0 forward_delay: Permission denied This is caused due to the files under /sys/class/net/ being owned by init namespace root rather than container root even when the bridge device is created inside of the container. Here's an example from inside of an unprivileged container: # brctl addbr testbr0 # ls -al /sys/class/net/testbr0/bridge/forward_delay -rw-r--r-- 1 nobody nogroup 4096 Jul 30 22:33 /sys/class/net/testbr0/bridge/forward_delay libvirt cannot open this file for writing even though it created the device. Where safe, files under /sys/class/net/ should be owned by container root. [Test Case] A simple kernel test is to verify that you can write to the /sys/class/net// files as root inside of an unprivileged LXD container. Unpatched kernels will see a Permission denied error: $ lxc exec c1 -- sh -c 'brctl addbr testbr && \ echo 1 > /sys/class/net/testbr/bridge/flush' sh: 1: cannot create /sys/class/net/testbr/bridge/flush: Permission denied The echo command will succeed when using a patched kernel. You can also install libvirt inside of a an unprivileged LXD container, restart the container, and verify that the default bridge (virbr0) is up. Unpatched kernels will not see the virbr0 bridge: $ lxc exec c1 -- sh -c 'brctl show virbr0' bridge name bridge id STP enabled interfaces virbr0 can't get info No such device The brctl command will show a valid device when using a patched kerne: $ lxc exec c1 -- sh -c 'brctl show virbr0' bridge name bridge id STP enabled interfaces virbr0 8000.5254005451e8 yes virbr0-nic [Regression Potential] The biggest concern with these patches is that they could cause a sensitive /sys/class/net/** file to be read from or written to inside of an unprivileged container. I've (tyhicks) audited all on the in- tree objects exposed to unprivileged containers by this patch set and I don't see any concerns. I did find one file (tx_maxrate) that I couldn't make heads or tails of so I added a CAP_NET_ADMIN check against the init namespace so that it couldn't be modified inside of a container. These patches were released in 4.19 and also in the Ubuntu 18.10 release kernel. No issues have been reported in those releases. [Other info] The following upstream patches have been merged into linux-next which fix this bug: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=c59e18b876da3e466abe5fa066aa69050f5be17c https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=d1753390274f7760e5b593cb657ea34f0617e559 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802233] 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 1802233
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.02 sec differences
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
The hwclock test will fail on the Power9 system due to a <0.02 second
difference
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
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:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802233] [NEW] hwclock test failed on Power9 due to 0.02 sec differences
Public bug reported:
The hwclock test will fail on the Power9 system due to a <0.02 second
difference
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
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:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: apport-bug bionic ppc64el uec-images
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.02 sec differences
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
The hwclock test will fail on the Power9 system due to a <0.02 second
difference
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20
[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Hi. Thanks for trying to help, but unfortunately I can't test that at this time since I'm not that experienced and i can't take the risk of ruining this installation. Sorry. On my computer the transition from 4.5.7 to 4.6.0 is the cause of this bug. Toshiba A210 with AMD CPU and graphics. 4.5.7 - Works 4.6.0 - Doesn't work Can anyone try to install the following kernels to check if the same behavior happens on other computers? http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5.7-yakkety/ http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/21/2018 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775068] Re: Volume control not working Dell XPS 27 (7760)
I think trolinka uses Bionic but the patch lands at Xenial through upstream stable update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Committed Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800639] Re: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** 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/1800639
Title:
[Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
== SRU Justification ==
Fix socket buffer (skb) leaks for HiperTransport
Description: net/af_iucv: fix skb leaks for HiperTransport
Symptom: Memory leaks and/or double-freed network packets.
Problem: Inbound packets may have any combination of flag bits set in
their iucv header. Current code only handles certain
combinations, and ignores (ie. leaks) all packets with other flags.
On Transmit, current code is inconsistent about whether the error
paths need to free the skb. Depending on which error path is
taken, it may either get freed twice, or leak.
Solution: On receive, drop any skb with an unexpected combination of iucv
Header flags.
On transmit, be consistent in all error paths about free'ing the skb.
== Fix ==
222440996d6daf635bed6cb35041be22ede3e8a0 ("net/af_iucv: drop inbound packets
with invalid flags")
b2f543949acd1ba64313fdad9e672ef47550d773 ("net/af_iucv: fix skb handling on
HiperTransport xmit error")
== Patch ==
commit 222440996d6daf635bed6cb35041be22ede3e8a0
Author: Julian Wiedmann
Date: Wed Sep 5 16:55:10 2018 +0200
net/af_iucv: drop inbound packets with invalid flags
Inbound packets may have any combination of flag bits set in their iucv
header. If we don't know how to handle a specific combination, drop the
skb instead of leaking it.
To clarify what error is returned in this case, replace the hard-coded
0 with the corresponding macro.
Signed-off-by: Julian Wiedmann
Signed-off-by: David S. Miller
==
commit b2f543949acd1ba64313fdad9e672ef47550d773
Author: Julian Wiedmann
Date: Wed Sep 5 16:55:11 2018 +0200
net/af_iucv: fix skb handling on HiperTransport xmit error
When sending an skb, afiucv_hs_send() bails out on various error
conditions. But currently the caller has no way of telling whether the
skb was freed or not - resulting in potentially either
a) leaked skbs from iucv_send_ctrl(), or
b) double-free's from iucv_sock_sendmsg().
As dev_queue_xmit() will always consume the skb (even on error), be
consistent and also free the skb from all other error paths. This way
callers no longer need to care about managing the skb.
Signed-off-by: Julian Wiedmann
Reviewed-by: Ursula Braun
Signed-off-by: David S. Miller
== Regression Potential ==
Low, because:
- IUCV functionality is very special to s390x and is only supported in z/VM
environments
(z/VM hypervisor to guest or guest to guest communications)
- So everything is s390x specific.
- Patch is limited to this single file: /net/iucv/af_iucv.c
- Patch was tested by IBM, and fixes an identified problem situation.
== Test Case ==
Set IUCV communication on an Ubuntu s390x system that runs as z/VM guest:
https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.linux.z.ludd/ludd_r_afiucv_setup.html
Provoke an error situation.
This is btw. hard to do, because the 'Inter-User Communication Vehicle"
(IUCV) is a virtual z/VM internal
network that does not use any real media.
To check for regressions one can use a shell over an ssh connection using an
IUCV interface
or use an application that utilises AF_IUCV sockets (like ICC).
__
Description: net/af_iucv: fix skb leaks for HiperTransport
Symptom: Memory leaks and/or double-freed network packets.
Problem: Inbound packets may have any combination of flag bits set in
their iucv header. Current code only handles certain
combinations, and ignores (ie. leaks) all packets with other
flags.
On Transmit, current code is inconsistent about whether the error
paths need to free the skb. Depending on which error path is
taken, it may either get freed twice, or leak.
Solution: On receive, drop any skb with an unexpected combination of iucv
Header flags.
On transmit, be consistent in all error paths about free'ing the
skb.
kerne 4.19
Upstream-ID: 222440996d6daf635bed6cb35041be22ede3e8a0
b2f543949acd1ba64313fdad9e672ef47550d773
Should also be applied, to all other Ubuntu Releases in the field !
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800639/+subscriptions
--
Mailing list:
[Kernel-packages] [Bug 1801686] Re: [Ubuntu] qdio: reset old sbal_state flags
** 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/1801686
Title:
[Ubuntu] qdio: reset old sbal_state flags
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
New
Bug description:
== SRU Justification ==
Description: qdio: reset old sbal_state flags
Symptom:
af_iucv socket using HiperSockets may stall.
Problem:
When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution:
Unconditionally clear the buffer's flags field.
== Fix ==
64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old
sbal_state flags")
== Regression Potential ==
Low, because:
- s390x only
- further limited to qeth driver (OSA Express networking)
- changes are limited to two files and 6 lines
- arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
- drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
- error was identified at IBM/customer, fix was created there and tested
upfront
- (changes are upstream in 4.20 (according to bug description,
but in 4.19 according to 'git tag'),
hence will make it automatically into 'disco')
== Test Case ==
Test case / reproduction:
Error inject and then simulate out-of-memory situation.
__
Description: qdio: reset old sbal_state flags
Symptom: af_iucv socket using HiperSockets may stall.
Problem: When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution: Unconditionally clear the buffer's flags field.
Reproduction: Error inject, simulating out-of-memory.
kernel 4.20
Upstream-ID: 64e03ff72623b8c2ea89ca3cb660094e019ed4ae
Canonical , please provide this fix for all Releases in Service
Ubuntu 18.10, 18.04 and 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1801686/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801305] Re: Restore request-based mode to xen-blkfront for AWS kernels
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801305 Title: Restore request-based mode to xen-blkfront for AWS kernels Status in linux package in Ubuntu: Fix Committed Bug description: In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. For X this needs a small patch from upstream for error handling. For B/C this patchset is bigger as it includes the suspend/resume patches already in X, and a new fixup. These are desirable as the request mode patch assumes their presence. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
Hi. On my computer the transition from 4.5.7 to 4.6.0 is the cause of this bug. Can anyone try to install the following kernels to see if this bug happens? http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5.7-yakkety/ http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778323] Re: Touchpad doesn't work in 4.17 or later
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778323 Title: Touchpad doesn't work in 4.17 or later Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Confirmed Bug description: Using the builds at http://kernel.ubuntu.com/~kernel-ppa/mainline/ I can successfully install and run 4.16.17 (Linux version 4.16.17-041617-generic (kernel@tangerine) (gcc version 7.3.0 (Ubuntu 7.3.0-23ubuntu2)) #201806201630 SMP Wed Jun 20 20:32:55 UTC 2018) but not 4.17.2 or 4.18-rc1. In the later ones, the touchpad does not work after boot and rebooting stalls: Jun 18 15:42:50 pkxps kernel: [ 242.366528] INFO: task systemd-udevd:309 blocked for more than 120 seconds. Jun 18 15:42:50 pkxps kernel: [ 242.366540] Not tainted 4.17.2-041702-generic #201806160433 Jun 18 15:42:50 pkxps kernel: [ 242.366545] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 18 15:42:50 pkxps kernel: [ 242.366551] systemd-udevd D0 309 273 0x8104 Jun 18 15:42:50 pkxps kernel: [ 242.366558] Call Trace: Jun 18 15:42:50 pkxps kernel: [ 242.366576] __schedule+0x291/0x870 Jun 18 15:42:50 pkxps kernel: [ 242.366582] ? __switch_to_asm+0x34/0x70 Jun 18 15:42:50 pkxps kernel: [ 242.366587] ? __switch_to_asm+0x40/0x70 Jun 18 15:42:50 pkxps kernel: [ 242.366596] ? get_work_pool+0x40/0x40 Jun 18 15:42:50 pkxps kernel: [ 242.366602] schedule+0x2c/0x80 Jun 18 15:42:50 pkxps kernel: [ 242.366609] schedule_timeout+0x1db/0x360 Jun 18 15:42:50 pkxps kernel: [ 242.366615] ? __schedule+0x299/0x870 Jun 18 15:42:50 pkxps kernel: [ 242.366623] ? get_work_pool+0x40/0x40 Jun 18 15:42:50 pkxps kernel: [ 242.366629] wait_for_completion+0xba/0x140 Jun 18 15:42:50 pkxps kernel: [ 242.366637] ? wake_up_q+0x80/0x80 Jun 18 15:42:50 pkxps kernel: [ 242.366645] flush_work+0x127/0x1e0 Jun 18 15:42:50 pkxps kernel: [ 242.366652] ? worker_detach_from_pool+0xa0/0xa0 Jun 18 15:42:50 pkxps kernel: [ 242.31] __cancel_work_timer+0x131/0x1b0 Jun 18 15:42:50 pkxps kernel: [ 242.39] cancel_delayed_work_sync+0x13/0x20 Jun 18 15:42:50 pkxps kernel: [ 242.366676] power_supply_unregister+0x37/0xb0 Jun 18 15:42:50 pkxps kernel: [ 242.366682] devm_power_supply_release+0x11/0x20 Jun 18 15:42:50 pkxps kernel: [ 242.366692] release_nodes+0x110/0x1f0 Jun 18 15:42:50 pkxps kernel: [ 242.366701] devres_release_group+0x7c/0xb0 Jun 18 15:42:50 pkxps kernel: [ 242.366718] wacom_remove+0xce/0x120 [wacom] Jun 18 15:42:50 pkxps kernel: [ 242.366733] hid_device_remove+0x55/0xb0 [hid] Jun 18 15:42:50 pkxps kernel: [ 242.366741] device_release_driver_internal+0x15b/0x220 Jun 18 15:42:50 pkxps kernel: [ 242.366751] ? __hid_bus_driver_added+0x40/0x40 [hid] Jun 18 15:42:50 pkxps kernel: [ 242.366760] ? hid_destroy_device+0x60/0x60 [hid] Jun 18 15:42:50 pkxps kernel: [ 242.366766] device_release_driver+0x12/0x20 Jun 18 15:42:50 pkxps kernel: [ 242.366771] device_reprobe+0x30/0x50 Jun 18 15:42:50 pkxps kernel: [ 242.366782] __hid_bus_reprobe_drivers+0x4b/0x60 [hid] Jun 18 15:42:50 pkxps kernel: [ 242.366793] bus_for_each_dev+0x74/0xb0 Jun 18 15:42:50 pkxps kernel: [ 242.366803] __hid_bus_driver_added+0x2c/0x40 [hid] -- Jun 18 15:42:50 pkxps kernel: [ 242.366859] ? __vunmap+0x81/0xb0 Jun 18 15:42:50 pkxps kernel: [ 242.366867] ? _cond_resched+0x19/0x40 Jun 18 15:42:50 pkxps kernel: [ 242.366874] ? kmem_cache_alloc_trace+0xb8/0x1c0 Jun 18 15:42:50 pkxps kernel: [ 242.366883] ? do_init_module+0x27/0x209 Jun 18 15:42:50 pkxps kernel: [ 242.366892] do_init_module+0x5f/0x209 Jun 18 15:42:50 pkxps kernel: [ 242.366900] load_module+0x1987/0x1f10 Jun 18 15:42:50 pkxps kernel: [ 242.366913] __do_sys_finit_module+0xfc/0x120 Jun 18 15:42:50 pkxps kernel: [ 242.366919] ? __do_sys_finit_module+0xfc/0x120 Jun 18 15:42:50 pkxps kernel: [ 242.366929] __x64_sys_finit_module+0x1a/0x20 Jun 18 15:42:50 pkxps kernel: [ 242.366936] do_syscall_64+0x5a/0x120 Jun 18 15:42:50 pkxps kernel: [ 242.366942] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 18 15:42:50 pkxps kernel: [ 242.366948] RIP: 0033:0x7f03e2729839 Jun 18 15:42:50 pkxps kernel: [ 242.366952] RSP: 002b:7ffde9a0e588 EFLAGS: 0246 ORIG_RAX: 0139 Jun 18 15:42:50 pkxps kernel: [ 242.366959] RAX: ffda RBX: 561aff969a00 RCX: 7f03e2729839 Jun 18 15:42:50 pkxps kernel: [ 242.366963] RDX: RSI: 7f03e24080e5 RDI: 0007 Jun 18 15:42:50 pkxps kernel: [ 242.366967] RBP: 7f03e24080e5 R08: R09: 7ffde9a0e6a0 Jun 18 15:42:50 pkxps kernel: [ 242.366970] R10: 0007 R11: 0246 R12:
[Kernel-packages] [Bug 1800849] Re: [Ubuntu] kvm: fix deadlock when killed by oom
** 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/1800849
Title:
[Ubuntu] kvm: fix deadlock when killed by oom
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
Description: kvm: fix deadlock when killed by oom
Symptom: oom killer leaves processes in a deadlock state.
Problem: The problem arises in the rare cases in which
handle_mm_fault does not release the mm_sem.
Solution: Correct the issue by manually release the mm_sem when needed.
== Fix ==
306d6c49ac9ded4cb53b0925da52f2c2ada1 ("s390/kvm: fix deadlock when
killed by oom")
== Patch ==
commit 306d6c49ac9ded4cb53b0925da52f2c2ada1
Author: Claudio Imbrenda
Date: Mon Jul 16 10:38:57 2018 +0200
s390/kvm: fix deadlock when killed by oom
When the oom killer kills a userspace process in the page fault handler
while in guest context, the fault handler fails to release the mm_sem
if the FAULT_FLAG_RETRY_NOWAIT option is set. This leads to a deadlock
when tearing down the mm when the process terminates. This bug can only
happen when pfault is enabled, so only KVM clients are affected.
The problem arises in the rare cases in which handle_mm_fault does not
release the mm_sem. This patch fixes the issue by manually releasing
the mm_sem when needed.
Fixes: 24eb3a824c4f3 ("KVM: s390: Add FAULT_FLAG_RETRY_NOWAIT for guest
fault")
Cc: # 3.15+
Signed-off-by: Claudio Imbrenda
Signed-off-by: Martin Schwidefsky
== Regression Potential ==
Low and minimal, because:
- code change is s390x only
- limited to one single file: /arch/s390/mm/fault.c
- just two additional lines added (if stmt)
- Xenial and Cosmic already have this commit via upstream stable updates.
- Hence patch is just missing in Bionic.
- Test kernel was build for testting.
== Test Case ==
Create numerous KVM guests so that the host starts swapping
and memory becomes overcomitted and the oom killer is triggered.
__
Description: kvm: fix deadlock when killed by oom
Symptom: oom killer leaves processes in a deadlock state.
Problem: The problem arises in the rare cases in which
handle_mm_fault does not release the mm_sem.
Solution: Correct the issue by manually relaese the mm_sem
when needed.
Reproduction: Create numerous KVM guests so that the host starts
swapping and memory becomes overcomitted and the oom
killer is triggered.
kernel 4.19
Upstream-ID: 306d6c49ac9ded4cb53b0925da52f2c2ada1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800849/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800306] Re: Computer hangs completely passed 15~25 days of usage
Do you see the same issue on v4.19, without adding any kernel parameter? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800306 Title: Computer hangs completely passed 15~25 days of usage Status in linux package in Ubuntu: Incomplete Bug description: Computer hangs every 3 weeks or so. It seems a graphics card problem but I changed by a new one, tried nvidia driver with the same behaviour too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-138-generic 4.4.0-138.164 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 27 16:20:18 2018 HibernationDevice: RESUME=/dev/mapper/LINUX--vg-swap_1 InstallationDate: Installed on 2017-11-02 (359 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: MSI MS-7885 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-138-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-138-generic N/A linux-backports-modules-4.4.0-138-generic N/A linux-firmware 1.157.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P.50 dmi.board.asset.tag: Default string dmi.board.name: X99A RAIDER (MS-7885) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP.50:bd07/19/2016:svnMSI:pnMS-7885:pvr5.0:rvnMSI:rnX99ARAIDER(MS-7885):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7885 dmi.product.version: 5.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800639] Re: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
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/1800639
Title:
[Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
== SRU Justification ==
Fix socket buffer (skb) leaks for HiperTransport
Description: net/af_iucv: fix skb leaks for HiperTransport
Symptom: Memory leaks and/or double-freed network packets.
Problem: Inbound packets may have any combination of flag bits set in
their iucv header. Current code only handles certain
combinations, and ignores (ie. leaks) all packets with other flags.
On Transmit, current code is inconsistent about whether the error
paths need to free the skb. Depending on which error path is
taken, it may either get freed twice, or leak.
Solution: On receive, drop any skb with an unexpected combination of iucv
Header flags.
On transmit, be consistent in all error paths about free'ing the skb.
== Fix ==
222440996d6daf635bed6cb35041be22ede3e8a0 ("net/af_iucv: drop inbound packets
with invalid flags")
b2f543949acd1ba64313fdad9e672ef47550d773 ("net/af_iucv: fix skb handling on
HiperTransport xmit error")
== Patch ==
commit 222440996d6daf635bed6cb35041be22ede3e8a0
Author: Julian Wiedmann
Date: Wed Sep 5 16:55:10 2018 +0200
net/af_iucv: drop inbound packets with invalid flags
Inbound packets may have any combination of flag bits set in their iucv
header. If we don't know how to handle a specific combination, drop the
skb instead of leaking it.
To clarify what error is returned in this case, replace the hard-coded
0 with the corresponding macro.
Signed-off-by: Julian Wiedmann
Signed-off-by: David S. Miller
==
commit b2f543949acd1ba64313fdad9e672ef47550d773
Author: Julian Wiedmann
Date: Wed Sep 5 16:55:11 2018 +0200
net/af_iucv: fix skb handling on HiperTransport xmit error
When sending an skb, afiucv_hs_send() bails out on various error
conditions. But currently the caller has no way of telling whether the
skb was freed or not - resulting in potentially either
a) leaked skbs from iucv_send_ctrl(), or
b) double-free's from iucv_sock_sendmsg().
As dev_queue_xmit() will always consume the skb (even on error), be
consistent and also free the skb from all other error paths. This way
callers no longer need to care about managing the skb.
Signed-off-by: Julian Wiedmann
Reviewed-by: Ursula Braun
Signed-off-by: David S. Miller
== Regression Potential ==
Low, because:
- IUCV functionality is very special to s390x and is only supported in z/VM
environments
(z/VM hypervisor to guest or guest to guest communications)
- So everything is s390x specific.
- Patch is limited to this single file: /net/iucv/af_iucv.c
- Patch was tested by IBM, and fixes an identified problem situation.
== Test Case ==
Set IUCV communication on an Ubuntu s390x system that runs as z/VM guest:
https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.linux.z.ludd/ludd_r_afiucv_setup.html
Provoke an error situation.
This is btw. hard to do, because the 'Inter-User Communication Vehicle"
(IUCV) is a virtual z/VM internal
network that does not use any real media.
To check for regressions one can use a shell over an ssh connection using an
IUCV interface
or use an application that utilises AF_IUCV sockets (like ICC).
__
Description: net/af_iucv: fix skb leaks for HiperTransport
Symptom: Memory leaks and/or double-freed network packets.
Problem: Inbound packets may have any combination of flag bits set in
their iucv header. Current code only handles certain
combinations, and ignores (ie. leaks) all packets with other
flags.
On Transmit, current code is inconsistent about whether the error
paths need to free the skb. Depending on which error path is
taken, it may either get freed twice, or leak.
Solution: On receive, drop any skb with an unexpected combination of iucv
Header flags.
On transmit, be consistent in all error paths about free'ing the
skb.
kerne 4.19
Upstream-ID: 222440996d6daf635bed6cb35041be22ede3e8a0
b2f543949acd1ba64313fdad9e672ef47550d773
Should also be applied, to all other Ubuntu Releases in the field !
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1801875] Re: Power consumption during s2idle is higher than long idle(sk hynix)
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => 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/1801875 Title: Power consumption during s2idle is higher than long idle(sk hynix) Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] On some Dell XPS models, we observed the power consumption raises higher than long idle does during s2idle with sk hynix nvme. C2: Short idle: 4 Long idle: 1 S2I: 3.7 S5: 0.19 C3: Short idle: 7.2 Long idle: 4.5 S2I: 6.22 S5: 0.18 C5: Short idle: 6.5 Long idle: 1 S2I: 2.88 S5: 0.18 [Fix] From SK hynix FE, MS Windows doesn't put nvme to D3, and uses its own APST feature to do the power management. To leverage its APST feature during s2idle, we can't disable nvme device while suspending, too. So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. prevent nvme from being disabled when suspending. [Test] Verified on different XPS machines with different sk hynix nvme disks, it fixes the power consumption issue with no regression. And the power consumption drops to 0.77W during s2idle. [Regression Potential] Low, the patches only applied to specific nvme module, and from our test, the system is still stable. [Misc] This issue should be fixed by the firmware, and we're pushing sk hynix to fix it. But before sk hynix find out how to solve it, we have to preserve these commits in our kernel for a while. BTW, the patches use pm_suspend_via_s2idle() function from below commit which is still under reviewing. https://lists.ubuntu.com/archives/kernel-team/2018-October/096141.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800427] Re: sudo apt-get upgrade hangs
It's the "Backup+ Desk" that has issue. See if kernel parameter `usb-storage.quirks=0bc2:ab34:u` helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800427 Title: sudo apt-get upgrade hangs Status in linux package in Ubuntu: Incomplete Bug description: Installer Wine then did sudo apt-get update then sudo apt-get upgrade. Upgrade proceeded up to "Found initrd image: /boot/initrd.img-4.15.0-20-generic" then hung. While I waited a system error window popped up. I clicked send report. Then I got an error window stating that the error report asked for two things and only got 1. That the error report would not be sent. Below are the screen images of the terminal screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: robert 2158 F...m pulseaudio /dev/snd/controlC1: robert 2158 F pulseaudio /dev/snd/controlC0: robert 2158 F pulseaudio CurrentDesktop: MATE Date: Mon Oct 29 03:19:53 2018 HibernationDevice: RESUME=UUID=aa95f07d-f769-44ca-8b33-0c5b3c78bdeb InstallationDate: Installed on 2018-10-25 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=26dc3ca5-f3ae-47eb-92b6-4f02ed5ba4f0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: 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/1800427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799411] Re: linux: 4.15.0-39.42 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1800788 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) kernel-stable-phase-changed:Tuesday, 23. October 2018 16:06 UTC kernel-stable-phase:Uploaded -- swm properties -- backports: null boot-testing-requested: true bugs-spammed: true derivatives: null phase: Uploaded reason: - automated-testing: Testing FAILED regression-testing: Testing in progress verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799411 Title: linux: 4.15.0-39.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1800788 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) kernel-stable-phase-changed:Tuesday, 23. October 2018 16:06 UTC kernel-stable-phase:Uploaded -- swm properties -- backports: null boot-testing-requested: true bugs-spammed: true derivatives: null phase: Uploaded reason: regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801878] Re: NULL pointer dereference at 0000000000000020 when access dst_orig->ops->family in function xfrm_lookup_with_ifid()
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: New => 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/1801878
Title:
NULL pointer dereference at 0020 when access
dst_orig->ops->family in function xfrm_lookup_with_ifid()
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
NULL pointer access happens when trying to access dst_orig->ops.
The function xfrm_lookup() calls xfrm_lookup_with_ifid() and there is
a line inside trying to access dst_orig->ops and it's exactly where the
panicing happens:
u16 family = dst_orig->ops->family;
As you can see that the symbol offset of ops is about 32(0x20) which
definitely is the error message shows in the kern.log:
[267265.140511] BUG: unable to handle kernel NULL pointer dereference
at 0020
struct dst_entry {
struct callback_head callback_head; /* 0 16 */
struct dst_entry * child; /* 16 8 */
struct net_device * dev; /* 24 8 */
struct dst_ops * ops; <-- /* 32 8 */
The oops:
BUG: unable to handle kernel NULL pointer dereference at 0020
IP: xfrm_lookup+0x31/0x870
PGD 0 P4D 0
Oops: [#1] SMP PTI
CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.15.0-36-generic
#39~16.04.1-Ubuntu
Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
RIP: 0010:xfrm_lookup+0x31/0x870
RSP: 0018:98b542343a48 EFLAGS: 00010246
RAX: RBX: 98b542343ac8 RCX:
RDX: 98b542343ac8 RSI: RDI: b39e4380
RBP: 98b542343ab8 R08: 0002 R09:
R10: 0020 R11: 7fb56465 R12:
R13: b39e4380 R14: 0002 R15: b39e4380
FS: () GS:98b54234() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0020 CR3: 0004ed40a001 CR4: 001606e0
DR0: DR1: DR2:
DR3: DR6: fffe0ff0 DR7: 0400
Call Trace:
? __xfrm_policy_check+0x41d/0x630
__xfrm_route_forward+0xa3/0x110
ip_forward+0x38c/0x470
? ip_route_input_noref+0x28/0x40
ip_rcv_finish+0x124/0x410
ip_rcv+0x28e/0x3b0
? inet_del_offload+0x40/0x40
__netif_receive_skb_core+0x879/0xba0
? __skb_checksum+0x188/0x2c0
__netif_receive_skb+0x18/0x60
? __netif_receive_skb+0x18/0x60
netif_receive_skb_internal+0x37/0xe0
? tcp4_gro_complete+0x86/0x90
napi_gro_complete+0x73/0x90
dev_gro_receive+0x2ee/0x5c0
napi_gro_frags+0xa3/0x230
ena_clean_rx_irq+0x486/0x7c0 [ena]
ena_io_poll+0x41d/0x770 [ena]
net_rx_action+0x265/0x3b0
__do_softirq+0xf5/0x28f
irq_exit+0xb8/0xc0
xen_evtchn_do_upcall+0x30/0x40
xen_hvm_callback_vector+0x84/0x90
[Fix]
The patch tries to avoid the NULL pointer access before the line
mentioned "dst_orig->ops->family" in function __xfrm_route_forward.
And the function calling sequence is:
__xfrm_route_forward -> xfrm_lookup -> xfrm_lookup_with_ifid
It definitely avoids the NULL pointer access in the
xfrm_lookup_with_ifid.
commit c5e39ef174ad34cd4d26af3a83bdbccddd2ad9d6
Author: Steffen Klassert
Date: Tue Sep 11 10:31:15 2018 +0200
xfrm: Fix NULL pointer dereference when skb_dst_force clears the
dst_entry.
Since commit 222d7dbd258d ("net: prevent dst uses after free")
skb_dst_force() might clear the dst_entry attached to the skb.
The xfrm code don't expect this to happen, so we crash with
a NULL pointer dereference in this case. Fix it by checking
skb_dst(skb) for NULL after skb_dst_force() and drop the packet
in cast the dst_entry was cleared.
[Test]
The fix has been tested in the production system with the IPSec enabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801878/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801686] Re: [Ubuntu] qdio: reset old sbal_state flags
*Correction, I meant "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/1801686
Title:
[Ubuntu] qdio: reset old sbal_state flags
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
New
Bug description:
== SRU Justification ==
Description: qdio: reset old sbal_state flags
Symptom:
af_iucv socket using HiperSockets may stall.
Problem:
When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution:
Unconditionally clear the buffer's flags field.
== Fix ==
64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old
sbal_state flags")
== Regression Potential ==
Low, because:
- s390x only
- further limited to qeth driver (OSA Express networking)
- changes are limited to two files and 6 lines
- arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
- drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
- error was identified at IBM/customer, fix was created there and tested
upfront
- (changes are upstream in 4.20 (according to bug description,
but in 4.19 according to 'git tag'),
hence will make it automatically into 'disco')
== Test Case ==
Test case / reproduction:
Error inject and then simulate out-of-memory situation.
__
Description: qdio: reset old sbal_state flags
Symptom: af_iucv socket using HiperSockets may stall.
Problem: When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution: Unconditionally clear the buffer's flags field.
Reproduction: Error inject, simulating out-of-memory.
kernel 4.20
Upstream-ID: 64e03ff72623b8c2ea89ca3cb660094e019ed4ae
Canonical , please provide this fix for all Releases in Service
Ubuntu 18.10, 18.04 and 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1801686/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801686] Re: [Ubuntu] qdio: reset old sbal_state flags
This patch already exists in Xenial as 75443f02ecfdd7c8e998063f9371f046126a21d5
which was part
of the update to 4.4.154
This patch already exists in Cosmic as 0f4772f38723c41bf79c8ca1f58a00723e900749
which was part
of the update to 4.18.6
Marking both those releases as "Fixed release"
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: New => 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/1801686
Title:
[Ubuntu] qdio: reset old sbal_state flags
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
New
Bug description:
== SRU Justification ==
Description: qdio: reset old sbal_state flags
Symptom:
af_iucv socket using HiperSockets may stall.
Problem:
When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution:
Unconditionally clear the buffer's flags field.
== Fix ==
64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old
sbal_state flags")
== Regression Potential ==
Low, because:
- s390x only
- further limited to qeth driver (OSA Express networking)
- changes are limited to two files and 6 lines
- arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
- drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
- error was identified at IBM/customer, fix was created there and tested
upfront
- (changes are upstream in 4.20 (according to bug description,
but in 4.19 according to 'git tag'),
hence will make it automatically into 'disco')
== Test Case ==
Test case / reproduction:
Error inject and then simulate out-of-memory situation.
__
Description: qdio: reset old sbal_state flags
Symptom: af_iucv socket using HiperSockets may stall.
Problem: When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution: Unconditionally clear the buffer's flags field.
Reproduction: Error inject, simulating out-of-memory.
kernel 4.20
Upstream-ID: 64e03ff72623b8c2ea89ca3cb660094e019ed4ae
Canonical , please provide this fix for all Releases in Service
Ubuntu 18.10, 18.04 and 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1801686/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802023] Re: hns3: map tx ring to tc
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed ** 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/1802023 Title: hns3: map tx ring to tc Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Bug description: [Impact] hns3 supports hardware-based traffic classes. However, this requires that the driver map the classes to hardware rings during initialization. [Test Case] I don't have a way to verify that the hardware is behaving as programmed, so this is regression-tested only. [Fix] 1c77215480bcf net: hns3: Set tx ring' tc info when netdev is up [Regression Risk] Restricted to a single driver, which has been tested on the target SoC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799399] Re: linux: 3.13.0-162.212 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress - regression-testing: Testing in progress verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799399 Title: linux: 3.13.0-162.212 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797546] Re: dev test in ubuntu_stress_smoke_test cause kernel oops on T-3.13
** Changed in: linux (Ubuntu Trusty)
Status: New => 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/1797546
Title:
dev test in ubuntu_stress_smoke_test cause kernel oops on T-3.13
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Fix Committed
Bug description:
SRU Request [Trusty]
== Justification ==
It is possible to cause an oops in drm with an unimplemented ioctl call
with the following reproducer run as root:
#include
#include
#include
#include
int main(void)
{
int ptnum, fd;
fd = open("/dev/dri/card0", O_RDWR);
return ioctl(fd, TIOCGPTN, );
}
== Fix ==
A backport (minor wiggle) of upstream commit 1539fb9bd405
("drm: fix NULL pointer access by wrong ioctl").
== Testing ==
Run the reproducer above as root, it will trip the oops. With the fix
this oops won't occur.
== Regression Potential ==
Minimal, this is an upstream fix to this exact issue and has been in
the kernel since 3.16
This is a bare-metal node running with 3.13.0-160 amd64 kernel.
The dev test will cause kernel oops:
dev STARTING
dev RETURNED 0
dev FAILED (kernel oopsed)
[ 222.555784] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 222.564547] IP: [] memset+0x9/0xb0
[ 222.570101] PGD 8004586b1067 PUD 45784a067 PMD 0
[ 222.575767] Oops: 0002 [#1] SMP
[ 222.579385] Modules linked in: macvlan(+) dccp_ipv4 dccp ghash_generic
salsa20_generic salsa20_x86_64 camellia_generic camellia_aesni_avx2
camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 cast6_generic
cast_common serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic
twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64
twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4
algif_hash af_alg ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt
x86_pkg_temp_thermal coretemp kvm_intel kvm joydev lpc_ich shpchp mac_hid
hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel igb
aesni_intel aes_x86_64 i915_bdw dca lrw gf128mul ahci intel_ips glue_helper ptp
ablk_helper drm_kms_helper cryptd pps_core libahci i2c_algo_bit drm video
[ 222.647301] CPU: 0 PID: 23159 Comm: stress-ng-dev Not tainted
3.13.0-160-generic #210-Ubuntu
[ 222.647301] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS
S1200RP.86B.03.02.0003.070120151022 07/01/2015
[ 222.647302] task: 880035bf1800 ti: 880453b6 task.ti:
880453b6
[ 222.647303] RIP: 0010:[] []
memset+0x9/0xb0
[ 222.647306] RSP: 0018:880453b61db8 EFLAGS: 00010246
[ 222.647306] RAX: 88045af55d00 RBX: 880455538000 RCX:
0004
[ 222.647307] RDX: 0004 RSI: RDI:
[ 222.647307] RBP: 880453b61ec0 R08: 81c43740 R09:
[ 222.647308] R10: a002f260 R11: 880453b61e10 R12:
880455f07a00
[ 222.647309] R13: 0004 R14: R15:
0030
[ 222.647310] FS: 7f64909ef700() GS:88047040()
knlGS:
[ 222.647310] CS: 0010 DS: ES: CR0: 80050033
[ 222.647311] CR2: CR3: 000458904000 CR4:
00360770
[ 222.647312] DR0: DR1: DR2:
[ 222.647312] DR3: DR6: fffe0ff0 DR7:
0400
[ 222.647313] Stack:
[ 222.647314] a0010c05 88040001 a003ace4
00410086
[ 222.647316] 880453b61e10 880453b61e10 a00185d0
643054506240
[ 222.647317] 7f64909ebce0 88040004 a002f260
[ 222.647317] Call Trace:
[ 222.647329] [] ? drm_ioctl+0x4d5/0x630 [drm]
[ 222.647337] [] ? drm_agp_info_ioctl+0x10/0x10 [drm]
[ 222.647341] [] do_vfs_ioctl+0x2e3/0x4d0
[ 222.647343] [] ? SYSC_newfstat+0x25/0x30
[ 222.647344] [] SyS_ioctl+0x81/0xa0
[ 222.647347] [] system_call_fastpath+0x26/0x2b
[ 222.647359] Code: 16 fe 66 44 89 1f 66 44 89 54 17 fe eb 0c 48 83 fa 01
72 06 44 8a 1e 44 88 1f c3 90 90 90 90 90 90 90 49 89 f9 40 88 f0 48 89 d1
aa 4c 89 c8 c3 0f 1f 84 00 00 00 00 00 0f 1f 84 00 00 00 00
[ 222.647360] RIP [] memset+0x9/0xb0
[ 222.647361] RSP
[ 222.647361] CR2:
[ 222.647363] ---[ end trace f74524d41bff5843 ]---
[ 222.678166] program stress-ng-dev is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 222.678173] program stress-ng-dev is using a deprecated
[Kernel-packages] [Bug 1799399] Re: linux: 3.13.0-162.212 -proposed tracker
3.13.0-162.212 - generic Regression test CMPL, RTB. Issue to note in amd64: libhugetlbfs - failed on groucho only ubuntu_kvm_smoke_test - Unable to start KVM, timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - 43 failed on amaura, 37 failed on chico, 26 failed on harpo, 42 failed on pepe, 26 failed on zeppo ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fsync01, msync04, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) fcntl35 / fcntl35_64 in LTP syscall test failed with T/X/X-LTS kernel (bug 1774394) fanotify06 failed with T kernel (bug 1775378) fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 failed with T/X/A/B kernel (bug 1775153) keyctl03, keyctl05, keyctl07 (bug 1798045) keyctl06 (bug 1798025) openat03 (bug 1798027) request_key03 (bug 1798052) ubuntu_stress_smoke_test - dev test in ubuntu_stress_smoke_test cause kernel oops on T-3.13 (bug 1797546) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) libhugetlbfs - noresv-preserve-resv-page failed (bug 1747823) chunk-overcommit failed (bug 1747828) ubuntu_kvm_smoke_test - getlogin will fail to open /proc/self/loginuid (bug 1770245) ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fsync01, msync04, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) fcntl35 / fcntl35_64 in LTP syscall test failed with T/X/X-LTS kernel (bug 1774394) fanotify06 failed with T kernel (bug 1775378) fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 failed with T/X/A/B kernel (bug 1775153) keyctl03, keyctl05, keyctl07 (bug 1798045) keyctl06 (bug 1798025) open14 (bug 1798061) openat03 (bug 1798027) request_key03 (bug 1798052) ubuntu_qrt_apparmor - test_old_trusty_regression_testsuite failed to build (bug 1699987) ubuntu_qrt_kernel_security - test 021, 022 (bug 1747847) test 050 (bug 1684776) ubuntu_stress_smoke_test - seccomp (bug 1801856) Issue to note in i386: ubuntu_docker_smoke_test - passed after re-test ubuntu_kvm_smoke_test - uvt-kvm wait issue on Trusty(bug 1732883) ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007) ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fsync01, msync04, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) fcntl35 / fcntl35_64 in LTP syscall test failed with T/X/X-LTS kernel (bug 1774394) fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 failed with T/X/A/B kernel (bug 1775153) openat03 (bug 1798027) request_key03 (bug 1798052) Issue to note in ppc64le (P8): ubuntu_kvm_smoke_test - no supported architecture for 'hvm' (bug 1752550) ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fsync01, msync04, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) fanotify06 failed with T kernel (bug 1775378) fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 failed with T/X/A/B kernel (bug 1775153) keyctl03, keyctl05, keyctl07 (bug 1798045) keyctl06 (bug 1798025) open14 (bug 1798061) openat03 (bug 1798027) request_key03 (bug 1798052) ubuntu_stress_smoke_test - af-alg (bug 1801865) seccomp (bug 1801856) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799399 Title: linux: 3.13.0-162.212 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400
[Kernel-packages] [Bug 1799453] Re: linux-kvm: 4.18.0-1004.4 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799445 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress - regression-testing: Testing in progress verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1799453 Title: linux-kvm: 4.18.0-1004.4 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799445 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799453] Re: linux-kvm: 4.18.0-1004.4 -proposed tracker
4.18.0-1004.4 - kvm Regression test CMPL, RTB. Issue to note in amd64: libhugetlbfs - should be skipped ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4/4.15 kvm kernel (bug 1763323) ubuntu_kvm_unit_tests - 40 failed ubuntu_ltp - maximum recursion depth exceeded ubuntu_ltp_syscalls - getrandom02 timed out (bug 1797327) process_vm_readv01, process_vm_writev01 failed (bug 1797330) process_vm_writev02, process_vm_readv02, process_vm_readv03 failed (bug 1797331) quotactl01 failed (bug 1790028) ubuntu_performance_fio_aws - test for nvidia project, should not be run ubuntu_performance_pts_aws - test for nvidia project, should not be run ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test ubuntu_quota_smoke_test - failed with KVM kernel (bug 1784535) ubuntu_sysdig_smoke_test - Unable to insert sysdig_probe module on B-KVM kernel (bug 1766565) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1799453 Title: linux-kvm: 4.18.0-1004.4 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799445 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
Sounds like a kernel bug instead? Please boot with kernel parameter `usbcore.dyndbg=+p` and attach dmesg. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm
** Description changed: [Impact] * A kexec/crash kernel might get stuck and fail to boot (for crash kernel, kdump fails to collect a crashdump) if a PCI device is buggy/stuck/looping and triggers a continuous flood of MSI(X) interrupts (that the kernel does not yet know about). * This fix allowed to obtain crashdumps when debugging a heavy-load scenario, in which a (heavy-loaded) network adapter wouldn't stop triggering MSI-X interrupts ever after panic()->kdump kicked in. - * This fix disables MSI(X) in all PCI devices on early -boot (this is OK as it's (re-)enabled normally later) -with a kernel cmdline parameter (disabled by default). + * This fix disables MSI(X) in all PCI devices on early + boot (this is OK as it's (re-)enabled normally later) + with a kernel cmdline parameter (disabled by default). [Test Case] * A synthetic test-case is not yet available, however, this particular system/workload triggered the problem consistently, and it was used for development/testing. * We'll update this bug once a synthetic test-case is available; we're working on patching QEMU for this. + + * $ dmesg | grep 'Clearing MSI' +[0.00] Clearing MSI/MSI-X enable bits early in boot (quirk) + + * The comparison of 'dmesg -t | sort' has been reviewed +between option disabled/enabled on boot & kexec modes, +and only expected differences found (MHz, PIDs, MIPS). [Regression Potential] * The potential area for regressions is early boot, particularly effects of applying quirks during PCI bus scan, which is changed/broader w/ these patches. * However, all quirks are applied based on PCI ID matching, so would only apply if actually targeting a new device. * Moreover, the new quirk is only applied based on a kernel cmdline parameter that is disabled by default, which constraints even more when this is actually in effect. [Other Info] * The patch series is still under review/discussion upstream, but it's relatively important for Ubuntu users at this point, and after internal discussions we decided to submit it for SRU. * These are links to the linux-pci archive with the patches [1, 2, 3] [1] [PATCH 1/3] x86/quirks: Scan all busses for early PCI quirks https://lore.kernel.org/linux-pci/20181018183721.27467-1-gpicc...@canonical.com/ [2] [PATCH 2/3] x86/PCI: Export find_cap() to be used in early PCI code https://lore.kernel.org/linux-pci/20181018183721.27467-2-gpicc...@canonical.com/ [3] [PATCH 3/3] x86/quirks: Add parameter to clear MSIs early on boot https://lore.kernel.org/linux-pci/20181018183721.27467-3-gpicc...@canonical.com/ [Original Description] We have reports of a kdump failure in Ubuntu (in x86 machine) that was narrowed down to a MSI irq storm coming from a PCI network device. The bug manifests as a lack of progress in the boot process of the kdump kernel, and a storm of kernel messages like: [...] [ 342.265294] do_IRQ: 0.155 No irq handler for vector [ 342.266916] do_IRQ: 0.155 No irq handler for vector [ 347.258422] do_IRQ: 14053260 callbacks suppressed [...] The root cause of the issue is that the kdump kernel kexec process does not ensure PCI devices are reset and/or MSI capabilities are disabled, so a PCI device could produce a huge amount of PCI irqs which would take all the processing time for the CPU (specially since we restrict the kdump kernel to use one single CPU only). This was tested using upstream kernel version 4.18, and the problem reproduces. In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit [8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under high load on the guest. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797990 Title: kdump fail due to an IRQ storm Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: [Impact] * A kexec/crash kernel might get stuck and fail to boot (for crash kernel, kdump fails to collect a crashdump) if a PCI device is buggy/stuck/looping and triggers a continuous flood of MSI(X) interrupts (that the kernel does not yet know about). * This fix allowed to obtain crashdumps when debugging a heavy-load scenario, in which a (heavy-loaded) network adapter wouldn't stop triggering MSI-X interrupts ever after panic()->kdump kicked in. * This fix disables MSI(X) in all PCI devices on early boot (this is OK as it's
[Kernel-packages] [Bug 1799718] Re: Ubuntu 18.10 fr FAN always ON 5 400 rpm
IT'S A problem of ACPI Error bad adress ! Already exist SEE ATTACHMENT !!! How can I correct this? For info, the same problem on linuxmint 18 and 19... It seems to be with Ubuntu 16... If you upgrade from 14 ... Its ok, if you install new... Crashes ** Attachment added: "IMG_20181108_002623_DRO.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799718/+attachment/5210151/+files/IMG_20181108_002623_DRO.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/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD 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.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity
Day 3: No issue after wake from suspend. Day 4: Issue comes back again (after suspend). Resolved after toggling "Autosuspend on" for two unknown USB devices to "Bad". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1801642 Title: Bluetooth mouse sleeps after 5 seconds of inactivity Status in bluez package in Ubuntu: Invalid Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1801642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800752] Re: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance
I've been looking (briefly) for some docs on the Intel GPU hardware layout. Came across this: https://01.org/linuxgraphics/documentation/hardware-specification-prms leading to: https://01.org/sites/default/files/documentation/intel-gfx-prm-osrc-bdw-vol04-configurations_3.pdf which says that a Intel HD graphics 6000 set-up (which is what this system has) will have 47* EUs. *(*) Intel reserves the right to increase the number of EUs on these SKUs. So perhaps this is a strange oddity that doesn't fit into the mask counting? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance Status in beignet package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-03-23 (228 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-28 (9 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm
** Description changed: + [Impact] + + * A kexec/crash kernel might get stuck and fail to boot +(for crash kernel, kdump fails to collect a crashdump) +if a PCI device is buggy/stuck/looping and triggers a +continuous flood of MSI(X) interrupts (that the kernel +does not yet know about). + + * This fix allowed to obtain crashdumps when debugging a +heavy-load scenario, in which a (heavy-loaded) network +adapter wouldn't stop triggering MSI-X interrupts ever +after panic()->kdump kicked in. + + * This fix disables MSI(X) in all PCI devices on early +boot; this is OK as it's (re-)enabled normally later. + + [Test Case] + + * A synthetic test-case is not yet available, however, +this particular system/workload triggered the problem +consistently, and it was used for development/testing. + + * We'll update this bug once a synthetic test-case is +available; we're working on patching QEMU for this. + + [Regression Potential] + + * The potential area for regressions is early boot, +particularly effects of applying quirks during PCI +bus scan, which is changed/broader w/ these patches. + + * However, all quirks are applied based on PCI ID +matching, so would only apply if actually targeting +a new device. + + * Moreover, the new quirk is only applied based on +a kernel cmdline parameter that is disabled by +default, which constraints even more when this +is actually in effect. + + [Other Info] + + * The patch series is still under review/discussion +upstream, but it's relatively important for Ubuntu +users at this point, and after internal discussions +we decided to submit it for SRU. + + * These are links to the linux-pci archive with the +patches [1, 2, 3] + +[1] [PATCH 1/3] x86/quirks: Scan all busses for early PCI quirks + https://lore.kernel.org/linux-pci/20181018183721.27467-1-gpicc...@canonical.com/ + +[2] [PATCH 2/3] x86/PCI: Export find_cap() to be used in early PCI code + https://lore.kernel.org/linux-pci/20181018183721.27467-2-gpicc...@canonical.com/ + +[3] [PATCH 3/3] x86/quirks: Add parameter to clear MSIs early on boot + https://lore.kernel.org/linux-pci/20181018183721.27467-3-gpicc...@canonical.com/ + + + [Original Description] + We have reports of a kdump failure in Ubuntu (in x86 machine) that was narrowed down to a MSI irq storm coming from a PCI network device. The bug manifests as a lack of progress in the boot process of the kdump kernel, and a storm of kernel messages like: [...] [ 342.265294] do_IRQ: 0.155 No irq handler for vector [ 342.266916] do_IRQ: 0.155 No irq handler for vector [ 347.258422] do_IRQ: 14053260 callbacks suppressed [...] The root cause of the issue is that the kdump kernel kexec process does not ensure PCI devices are reset and/or MSI capabilities are disabled, so a PCI device could produce a huge amount of PCI irqs which would take all the processing time for the CPU (specially since we restrict the kdump kernel to use one single CPU only). This was tested using upstream kernel version 4.18, and the problem reproduces. In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit [8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under high load on the guest. ** Description changed: [Impact] - * A kexec/crash kernel might get stuck and fail to boot -(for crash kernel, kdump fails to collect a crashdump) -if a PCI device is buggy/stuck/looping and triggers a -continuous flood of MSI(X) interrupts (that the kernel -does not yet know about). + * A kexec/crash kernel might get stuck and fail to boot + (for crash kernel, kdump fails to collect a crashdump) + if a PCI device is buggy/stuck/looping and triggers a + continuous flood of MSI(X) interrupts (that the kernel + does not yet know about). - * This fix allowed to obtain crashdumps when debugging a -heavy-load scenario, in which a (heavy-loaded) network -adapter wouldn't stop triggering MSI-X interrupts ever -after panic()->kdump kicked in. + * This fix allowed to obtain crashdumps when debugging a + heavy-load scenario, in which a (heavy-loaded) network + adapter wouldn't stop triggering MSI-X interrupts ever + after panic()->kdump kicked in. * This fix disables MSI(X) in all PCI devices on early -boot; this is OK as it's (re-)enabled normally later. +boot (this is OK as it's (re-)enabled normally later) +with a kernel cmdline parameter (disabled by default). [Test Case] - * A synthetic test-case is not yet available, however, -this particular system/workload triggered the problem -consistently, and it was used for development/testing. + * A synthetic test-case is not yet available, however, + this particular system/workload triggered the problem + consistently, and it was used for
[Kernel-packages] [Bug 50692]
*** Bug 98998 has been marked as a duplicate of this 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/50692 Title: New Sony Vaios hotkeys don't work (fn_key polling) Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: On new Sony Vaios (FS and FJ series) hotkeys don't work. A piece of code that enables them as been released on gentoo forums. The programs runs as a service and as a config file in /etc/fsfn.conf. Here is the dmidecode output on my laptop: System Information Manufacturer: Sony Corporation Product Name: VGN-FJ3S_W Basically, the same config (default) enables hotkeys on all VGN-FN* computers and adding BRT_HACK_FJS=1 parameter in /etc/fsfn.conf files, enables them for VGN-FJ* series. As an attachement to this bug, here is the fsfn tarball (latest version from the gentoo boards). To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/50692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714178]
I posted a patch series for -modesetting that fixes this issue, and also adds TearFree support: https://gitlab.freedesktop.org/xorg/xserver/merge_requests/24 The patch series from Ville (https://patchwork.freedesktop.org/series/49663/) will however be what you are looking for, as it will not reduce the performance at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1499858] Re: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic
Hello again, I compiled bluez-5.46 & installed it on ubuntu 16.04 and this has taken care of all of the "Not enough free handles to register service" errors and also "Failed to obtain handles for "Service Changed" characteristic" errors and bluetooth is working better than it ever has, for me anyway. So for me this is solved, I suppose. Don't know if this will help anyone?? But I hope so! Cheers, Singtoh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1499858 Title: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic Status in bluez package in Ubuntu: Confirmed Bug description: sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Error adding Link Loss service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Current Time Service could not be registered sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: gatt-time-server: Input/output error (5) sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Sap driver initialization failed. sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: sap-server: Operation not permitted (1) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.34-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 25 16:37:42 2015 InstallationDate: Installed on 2015-07-26 (61 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) InterestingModules: rfcomm bnep btusb bluetooth MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C4:85:08:6C:01:0A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:12620731 acl:54193 sco:0 events:799035 errors:0 TX bytes:447934374 acl:1637190 sco:0 commands:1459 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1499858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210098/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
I never made a battery reset but it's the same since the day when I bought it and I've try differents bios, resetting bios, reinstalling entire ssd, and I still get a fast dried battery on linux. (so it should not linked to my battery but to linux) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772675] Re: Intel i40e PF reset due to incorrect MDD detection (continues...again...)
Hi, We have disabled TSO and GSO and we are still experiencing the interface resets. This usually happens under high load. Kernel version: 4.4.0-135-generic driver: i40e version: 2.4.10 firmware-version: 6.01 0x80003493 0.0.0 bus-info: :05:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772675 Title: Intel i40e PF reset due to incorrect MDD detection (continues...again...) Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: [impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the nic, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [fix] The fix for this is currently unknown. As the "MDD event" is generated by the i40e firmware, and is completely undocumented, there is no way to tell what the i40e driver did to cause the MDD event. [test case] the bug is unfortunately very difficult to reproduce, but as shown in this (and previous) bug comments, some users of the i40e have traffic that can consistently reproduce the problem (although usually on the order of days, or longer, to reproduce). Reproducing is easily detected, as the nw traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued [regression potential] unknown since the specific fix is unknown. [original description] This is a continuation from bug 1713553 and then bug 1723127; a patch was added in the first bug and then the second bug, to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. See bug 1713553 and bug 1723127 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210105/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210092/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] Re: Unable to get right-click working on ThinkPad T480s
apport information ** Tags added: apport-collected cosmic ** Description changed: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. - Found a very very close report from RedHat, on the same model of laptop, - around kernel 4.18, with a fix: - https://bugzilla.redhat.com/show_bug.cgi?id=1628715 + Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: alex 2871 F pulseaudio + CurrentDesktop: GNOME + DistroRelease: Ubuntu 18.10 + HibernationDevice: RESUME=LABEL="Swap" + InstallationDate: Installed on 2012-11-03 (2195 days ago) + InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) + MachineType: LENOVO 20L7CTO1WW + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 + RelatedPackageVersions: + linux-restricted-modules-4.18.0-10-generic N/A + linux-backports-modules-4.18.0-10-generic N/A + linux-firmware 1.175 + Tags: cosmic + Uname: Linux 4.18.0-10-generic x86_64 + UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) + UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video + _MarkForUpload: True + dmi.bios.date: 09/13/2018 + dmi.bios.vendor: LENOVO + dmi.bios.version: N22ET49W (1.26 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20L7CTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad T480s + dmi.product.name: 20L7CTO1WW + dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s + dmi.product.version: ThinkPad T480s + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210091/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s
[Kernel-packages] [Bug 1802168] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210103/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798427] Re: kvm doesn't work on 36 physical bits systems
Tested with 4.18.0-11, and it is working fine now.
Thanks.
Cascardo.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798427
Title:
kvm doesn't work on 36 physical bits systems
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
A guest will hang while booting under 4.18.0-10.11 because of "kvm: x86: Set
highest physical address bits in non-present/reserved SPTEs", which came in via
4.18.y.
[Test Case]
A guest was booted after applying the patch.
[Regression Potential]
It might break KVM on systems with different physical memory limits, which is
just what upstream might have been testing the most.
A fix is already upstream, and already present in 4.18.14.
This would be upstream commit
daa07cbc9ae3da2d61b7ce900c0b9107d134f2c1 ("KVM: x86: fix L1TF's MMIO GFN
calculation").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798427/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210096/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210100/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210094/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210097/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210099/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210095/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210104/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210093/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27
I added debug into the kernel and observed /dev/vdb is being mounted by
systemd:
[9.859895] mount: 1624 mount, parent 1 systemd
[9.866398] mount: 1624 mount /dev/vdb
and also snap-confine is mounting mount too:
[9.966827] mount: 1663 snap-confine /mnt
Curiously, I've not seen any associated umounts.
I wonder if the namespace/confinement is causing the issue of not being
able to see the mount. I need to debug this further.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801349
Title:
zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27
Status in OpenStack LXD Charm:
New
Status in linux package in Ubuntu:
In Progress
Bug description:
Test: tests/gate-basic-cosmic-rocky
As part of the config, the lxd charm creates a pool device depending
on the config. The test config is:
lxd_config = {
'block-devices': '/dev/vdb',
'ephemeral-unmount': '/mnt',
'storage-type': 'zfs',
'overwrite': True
}
The config drive is normally mounted on /mnt, and the lxd charm
umounts it as part of the start up. The /etc/fstab on the unit is:
# cat /etc/fstab
LABEL=cloudimg-rootfs /ext4 defaults0 0
LABEL=UEFI /boot/efi vfatdefaults0 0
/dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig
0 2
/dev/vdcnoneswapsw,comment=cloudconfig 0 0
However, even after umount-ing the /mnt off of /dev/vdb, the zpool create
command still fails:
# zpool create -f lxd /dev/vdb
/dev/vdb is in use and contains a unknown filesystem.
If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then
rebooted, then the zpool create command succeeds:
# zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT
lxd 14.9G 106K 14.9G - 0% 0% 1.00x ONLINE -
# zpool status lxd
pool: lxd
state: ONLINE
scan: none requested
config:
NAMESTATE READ WRITE CKSUM
lxd ONLINE 0 0 0
vdb ONLINE 0 0 0
errors: No known data errors
Something odd is going on with cosmic (18.10) and the combination of
lxd, zfs and the kernel
lxd version: 3.6
zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
Linux: 4.18.0-10-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210102/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1802168/+attachment/5210101/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798127] Re: CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as root FS
** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu Bionic) Status: Triaged => 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/1798127 Title: CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as root FS Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This was reported by a hardware partner. The system set up is a server with 512GB RAM and an M.2 NVMe drive as the root filesystem/boot device. Per the customer, when running the certification Memory Stress test (utilizing several stress-ng stressors run in sequence) the system freezes with CPU Soft Lockup errors appearing on console whe the "stack" stressor is run. Tester has tried with 2.5” SATA (1TB), 2.5” NVMe (800GB), and M.2 NVMe (1.9TB). So far, this only seems to affect the 4.15 kernel. The tester has tried using the 2.5" SATA SSD as the RootFS/Boot device and the tests pass on all attempts. It is ONLY when using the M.2 NVMe as the root / boot device that the tests cause a lockup. The tester is re-trying now with the 2.5" NVMe device to see if this only occurs with the M.2 NVMe. The tester has tried this on the following while using the M.2 NVMe as the rootFS/Boot device: Test run #1 – 16.04.5 at kernel 4.15; Result: Failed stress-ng memory on stack stressor Test run #2 – 18.04.1 at kernel 4.15; Result: Failed stress-ng memory on stack stressor Test run #3 – 16.04.5 at kernel 4.4; Result: Passed stress-ng memory test The stress-ng command invoked at the time the soft lockups occur is this: 'stress-ng -k --aggressive --verify --timeout 300 --stack 0' This can be reproduced by running the memory_stress_ng test script from the cert suite: sudo /usr/lib/plainbox-provider-certification- server/bin/memory_stress_ng It may be more easily reproducible running the stack stressor alone, or the whole memory stress script without dealing with Checkbox. UPDATE: The tester also confirms that the 2.5" NVMe drives also fail with the 4.15 kernel and pass with the 4.4 kernel. The SSD works on all kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] Re: Unable to get right-click working on ThinkPad T480s
Reloading the psmouse kernel module with "elantech_smbus=0", I get back the right-click, as documented in the upstream 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/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685442]
Created attachment 142084 dmesg from old MacBook running lubuntu 18.04 Same problem here on an old MacBook running lubuntu 18.04. A good workaround is adding "video=SVIDEO-1:d" to the grub kernel parameters. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I had been running Ubuntu 16.04 LTS on many laptop computers (especially Dell D620, D630, E6400) with no problem. I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell D630. It was very slow to boot up (about 90 seconds) as opposed to the 30-45 seconds it usually takes. For a few seconds there were error messages that included the phrase "flip_done timed out". When the Ubuntu desktop appeared, the mouse cursor hung for a while, but then came back to life. I didn't do much testing from there. I did a Live session with the 16.04.2 LTS on a different D630 laptop, and the same problem occureed. I Googled the problem, and found several hits. - On an Arch forum, someone reported the problem on a Dell D630, like mine. It also occured on other laptops: https://bbs.archlinux.org/viewtopic.php?id=218581 The suggestion was that the bug was related to kernel version 4.8.x and the 965GM chipset, which is what the D630 has. So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the problem DID NOT occur. --- For a similar boot-up problem, Ubuntu Forum suggested going back to an earlier version of Ubuntu. https://ubuntuforums.org/showthread.php?t=2348892 I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and the problem did NOT occur. So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather than 16.04.2. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon.
[Kernel-packages] [Bug 1797881] Re: Display goes blank soon after boot on dell xps13 on linux-image-4.18.0-10-generic
Launchpad has imported 8 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=108083. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-09-27T07:36:16+00:00 Shun Terabayashi wrote: Created attachment 141757 full dmesg Kernel is 4.18.8, 4.18.9(Arch), mainline(AUR), and drm/drm-intel(https://github.com/shunonymous/aur-linux-drm-intel-git). My laptop displays nothing in builtin monitor when launching Wayland compositor.(weston, mutter) It displays by connecting or disconnecting external monitor (by HDMI) (mutter. weston doesn't work). startx works without any problem. I tried to revert https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=399334708b4f07b107094e5db4a390f0f25d2d4f on mainline, this symptom was disappeared. Machine: Razer Blade Stealth (2016 Later, UHD Model, w/o any eGPU) External Display: LG 27UD88-W (3840x2160) connected with HDMI OS: Arch Linux Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797881/comments/0 On 2018-10-02T05:58:02+00:00 Lakshminarayana-vudum wrote: Shun, Can you apply following path and test if the issue is still existing? (https://bugs.freedesktop.org/attachment.cgi?id=141229). If the issue persists, send dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M. This way we know more information about the bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797881/comments/1 On 2018-10-02T16:30:23+00:00 Shun Terabayashi wrote: I re-tested on latest drm/drm-intel (without patch), this issue is not exist. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797881/comments/2 On 2018-10-03T07:12:12+00:00 Lakshminarayana-vudum wrote: Thankyou for your feedback. I will resolve this bug as worksforme. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797881/comments/3 On 2018-10-20T19:35:42+00:00 Karolherbst-g wrote: this is actually an issue on the 4.18.8 and newer. Those commits need to be applied to 4.18 to fix this regression: 9ebd8202393dde9d3678c9ec162c1aa63ba17eac f24f6eb95807bca0dbd8dc5b2f3a4099000f4472 regression was caused by 399334708b4f07b107094e5db4a390f0f25d2d4f Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797881/comments/14 On 2018-10-20T19:37:42+00:00 Karolherbst-g wrote: I think the same applies for the upcoming 4.19 as well. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797881/comments/15 On 2018-10-23T11:28:57+00:00 Jani-nikula wrote: (In reply to Karol Herbst from comment #4) > this is actually an issue on the 4.18.8 and newer. > > Those commits need to be applied to 4.18 to fix this regression: > > 9ebd8202393dde9d3678c9ec162c1aa63ba17eac commit 9ebd8202393dde9d3678c9ec162c1aa63ba17eac Author: Dhinakaran Pandiyan Date: Thu Sep 27 13:57:30 2018 -0700 drm/i915/dp: Fix link retraining comment in intel_dp_long_pulse() > f24f6eb95807bca0dbd8dc5b2f3a4099000f4472 commit f24f6eb95807bca0dbd8dc5b2f3a4099000f4472 Author: Dhinakaran Pandiyan Date: Thu Sep 27 13:57:31 2018 -0700 drm/i915/dp: Restrict link retrain workaround to external monitors > regression was caused by > > 399334708b4f07b107094e5db4a390f0f25d2d4f commit 399334708b4f07b107094e5db4a390f0f25d2d4f Author: Jan-Marek Glogowski Date: Sat Aug 25 15:10:35 2018 -0400 drm/i915: Re-apply "Perform link quality check, unconditionally during long pulse" Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797881/comments/16 On 2018-11-02T09:31:48+00:00 Jani-nikula wrote: The commits are headed upstream and tagged with appropriate tags to be backported to stable kernels. Please let us know if the fixes don't show up in v4.18 in a few weeks. Thanks for the report, closing. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797881/comments/17 ** Changed in: linux Status: Unknown => Fix Released ** Changed in: linux Importance: Unknown => 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/1797881 Title: Display goes blank soon after boot on dell xps13 on linux- image-4.18.0-10-generic Status in
[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU
Launchpad has imported 25 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=107899. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-09-11T08:19:25+00:00 yurikoles wrote: It was discoverd that ANV doesn't free up allocated memory, original discussion: https://github.com/doitsujin/dxvk/issues/632 Affected configuration: ANV + DXVK + Wine. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798165/comments/0 On 2018-09-11T08:21:14+00:00 yurikoles wrote: Created attachment 141521 Top 10 stacks with outstanding allocations: Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798165/comments/1 On 2018-09-11T14:23:55+00:00 2-jason-v wrote: >From the github issue, it sounded like these allocations are never freed even after closing the app; is this correct? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798165/comments/2 On 2018-09-11T15:00:36+00:00 Leonardo Müller wrote: Yes, this is correct. Even closing the application the memory is not freed. If the application is opened again it does not use that memory it used before, it allocates new memory to itself. Note: I'm FurretUber on GitHub. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798165/comments/3 On 2018-09-14T15:21:10+00:00 Leonardo Müller wrote: Note: Dota 2 is causing GPU hangs, I have to set INTEL_DEBUG=nohiz to make it work. It seems it's not a DXVK-only issue. Dota 2 has, after 12 hours, allocated 719 MB of i915_request cache too. What I have noticed is that it was not allocating any i915_request cache for 20 minutes, then it started to allocate the memory too but at rates much slower than the DXVK applications. As a comparison, Forsaken Castle, in the same 20 minutes, allocated 213 MB. I already tried to debug this (see the GitHub issue) using perf and the only thing that looked strange in the DXVK application was one of the variables having values way off compared to the value of the variable in other applications. Using perf to debug @ and looking at the values of in_fence and fences: Forsaken_Castle 16943 [003] 17521.309896: probe:i915_gem_do_execbuffer: (c07690af) in_fence=0x0 fences=0x952366b7bb00 Xorg 2215 [000] 17521.309986: probe:i915_gem_do_execbuffer: (c07690af) in_fence=0x0 fences=0x2d28 rolc.exe 15796 [001] 17521.311725: probe:i915_gem_do_execbuffer: (c07690af) in_fence=0x0 fences=0x1d8 I can do more tests if needed. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798165/comments/4 On 2018-09-14T20:39:48+00:00 Chris Wilson wrote: The accumulation of i915_request implies there is a fence leak. Assuming it is not internal (an unmatched dma_fence_get/dma_fence_put), all userspace owners would be tied to an fd and eventually one would notice the fd exhaustion (after a few million depending on rlimit). But for the fd to stick around requires the process to be kept alive, which would imply the fence fd being passed to a display server. I don't think that is how fences are handled under X, which makes the likelihood of it being a singular userspace fence leak less likely. 'ls -1 /proc/$suspect/fd/ | wc -l' might be interesting to watch. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798165/comments/5 On 2018-09-15T22:06:47+00:00 2-jason-v wrote: I suspect this is some sort of fence leak with syncobj which would explain why only anv hits it (the GL driver doesn't use syncobj yet). Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798165/comments/6 On 2018-09-16T16:14:47+00:00 Richard Yao wrote: > The accumulation of i915_request implies there is a fence leak. Assuming it is not internal (an unmatched dma_fence_get/dma_fence_put), all userspace owners would be tied to an fd and eventually one would notice the fd exhaustion (after a few million depending on rlimit). It is not tied to a file descriptor because I915_EXEC_FENCE_OUT is not set in args->flags (that was worked out by working backward from a perf trace). This means that DEFINE_DRM_GEM_FOPS->drm_release is never called, and we never get dma_fence_put() from this (hypothetical) stack: dma_fence_put drm_syncobj_free
[Kernel-packages] [Bug 1802168] 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 1802168 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802168] [NEW] Unable to get right-click working on ThinkPad T480s
Public bug reported: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in linux package in Ubuntu: Incomplete Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778323] Re: Touchpad doesn't work in 4.17 or later
I haven't experienced this for a while now (since 4.19-rc1?), can be closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778323 Title: Touchpad doesn't work in 4.17 or later Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: Using the builds at http://kernel.ubuntu.com/~kernel-ppa/mainline/ I can successfully install and run 4.16.17 (Linux version 4.16.17-041617-generic (kernel@tangerine) (gcc version 7.3.0 (Ubuntu 7.3.0-23ubuntu2)) #201806201630 SMP Wed Jun 20 20:32:55 UTC 2018) but not 4.17.2 or 4.18-rc1. In the later ones, the touchpad does not work after boot and rebooting stalls: Jun 18 15:42:50 pkxps kernel: [ 242.366528] INFO: task systemd-udevd:309 blocked for more than 120 seconds. Jun 18 15:42:50 pkxps kernel: [ 242.366540] Not tainted 4.17.2-041702-generic #201806160433 Jun 18 15:42:50 pkxps kernel: [ 242.366545] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 18 15:42:50 pkxps kernel: [ 242.366551] systemd-udevd D0 309 273 0x8104 Jun 18 15:42:50 pkxps kernel: [ 242.366558] Call Trace: Jun 18 15:42:50 pkxps kernel: [ 242.366576] __schedule+0x291/0x870 Jun 18 15:42:50 pkxps kernel: [ 242.366582] ? __switch_to_asm+0x34/0x70 Jun 18 15:42:50 pkxps kernel: [ 242.366587] ? __switch_to_asm+0x40/0x70 Jun 18 15:42:50 pkxps kernel: [ 242.366596] ? get_work_pool+0x40/0x40 Jun 18 15:42:50 pkxps kernel: [ 242.366602] schedule+0x2c/0x80 Jun 18 15:42:50 pkxps kernel: [ 242.366609] schedule_timeout+0x1db/0x360 Jun 18 15:42:50 pkxps kernel: [ 242.366615] ? __schedule+0x299/0x870 Jun 18 15:42:50 pkxps kernel: [ 242.366623] ? get_work_pool+0x40/0x40 Jun 18 15:42:50 pkxps kernel: [ 242.366629] wait_for_completion+0xba/0x140 Jun 18 15:42:50 pkxps kernel: [ 242.366637] ? wake_up_q+0x80/0x80 Jun 18 15:42:50 pkxps kernel: [ 242.366645] flush_work+0x127/0x1e0 Jun 18 15:42:50 pkxps kernel: [ 242.366652] ? worker_detach_from_pool+0xa0/0xa0 Jun 18 15:42:50 pkxps kernel: [ 242.31] __cancel_work_timer+0x131/0x1b0 Jun 18 15:42:50 pkxps kernel: [ 242.39] cancel_delayed_work_sync+0x13/0x20 Jun 18 15:42:50 pkxps kernel: [ 242.366676] power_supply_unregister+0x37/0xb0 Jun 18 15:42:50 pkxps kernel: [ 242.366682] devm_power_supply_release+0x11/0x20 Jun 18 15:42:50 pkxps kernel: [ 242.366692] release_nodes+0x110/0x1f0 Jun 18 15:42:50 pkxps kernel: [ 242.366701] devres_release_group+0x7c/0xb0 Jun 18 15:42:50 pkxps kernel: [ 242.366718] wacom_remove+0xce/0x120 [wacom] Jun 18 15:42:50 pkxps kernel: [ 242.366733] hid_device_remove+0x55/0xb0 [hid] Jun 18 15:42:50 pkxps kernel: [ 242.366741] device_release_driver_internal+0x15b/0x220 Jun 18 15:42:50 pkxps kernel: [ 242.366751] ? __hid_bus_driver_added+0x40/0x40 [hid] Jun 18 15:42:50 pkxps kernel: [ 242.366760] ? hid_destroy_device+0x60/0x60 [hid] Jun 18 15:42:50 pkxps kernel: [ 242.366766] device_release_driver+0x12/0x20 Jun 18 15:42:50 pkxps kernel: [ 242.366771] device_reprobe+0x30/0x50 Jun 18 15:42:50 pkxps kernel: [ 242.366782] __hid_bus_reprobe_drivers+0x4b/0x60 [hid] Jun 18 15:42:50 pkxps kernel: [ 242.366793] bus_for_each_dev+0x74/0xb0 Jun 18 15:42:50 pkxps kernel: [ 242.366803] __hid_bus_driver_added+0x2c/0x40 [hid] -- Jun 18 15:42:50 pkxps kernel: [ 242.366859] ? __vunmap+0x81/0xb0 Jun 18 15:42:50 pkxps kernel: [ 242.366867] ? _cond_resched+0x19/0x40 Jun 18 15:42:50 pkxps kernel: [ 242.366874] ? kmem_cache_alloc_trace+0xb8/0x1c0 Jun 18 15:42:50 pkxps kernel: [ 242.366883] ? do_init_module+0x27/0x209 Jun 18 15:42:50 pkxps kernel: [ 242.366892] do_init_module+0x5f/0x209 Jun 18 15:42:50 pkxps kernel: [ 242.366900] load_module+0x1987/0x1f10 Jun 18 15:42:50 pkxps kernel: [ 242.366913] __do_sys_finit_module+0xfc/0x120 Jun 18 15:42:50 pkxps kernel: [ 242.366919] ? __do_sys_finit_module+0xfc/0x120 Jun 18 15:42:50 pkxps kernel: [ 242.366929] __x64_sys_finit_module+0x1a/0x20 Jun 18 15:42:50 pkxps kernel: [ 242.366936] do_syscall_64+0x5a/0x120 Jun 18 15:42:50 pkxps kernel: [ 242.366942] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 18 15:42:50 pkxps kernel: [ 242.366948] RIP: 0033:0x7f03e2729839 Jun 18 15:42:50 pkxps kernel: [ 242.366952] RSP: 002b:7ffde9a0e588 EFLAGS: 0246 ORIG_RAX: 0139 Jun 18 15:42:50 pkxps kernel: [ 242.366959] RAX: ffda RBX: 561aff969a00 RCX: 7f03e2729839 Jun 18 15:42:50 pkxps kernel: [ 242.366963] RDX: RSI: 7f03e24080e5 RDI: 0007 Jun 18 15:42:50 pkxps kernel: [ 242.366967] RBP: 7f03e24080e5 R08: R09: 7ffde9a0e6a0 Jun 18 15:42:50 pkxps kernel: [ 242.366970] R10: 0007 R11: 0246 R12:
[Kernel-packages] [Bug 1800254] Re: packet socket panic in Trusty 3.13.0-157 and later
** Tags removed: verification-needed-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1800254
Title:
packet socket panic in Trusty 3.13.0-157 and later
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Fix Committed
Bug description:
SRU Justification:
Due to changes added as part of c108ac876c02 ("packet: hold bind lock when
rebinding to fanout hook"), it is possible for fanout_add to add a
packet_type handler via dev_add_pack and then kfree the memory backing the
packet_type. This corrupts the ptype_all list, causing the system to
panic when network packet processing next traverses ptype_all. The
erroneous path is taken when a PACKET_FANOUT setsockopt is performed on a
packet socket that is bound to an interface that is administratively down.
This is not due to any flaw of c108ac876c02, but rather than the packet
socket code base differs subtly in 3.13 as compared to 4.4.
This affects only the Trusty 3.13 kernel series, starting with
3.13.0-157.
Fix:
The remedy for this is to backport additional changes in the management of
the dev_add_pack calls from 4.4. This moves the dev_add_pack and
dev_remove_pack calls from fanout_add and _release into __fanout_link and
_unlink.
Testcase:
The issue can be reproduced reliably by (a) creating an AF_PACKET socket,
binding it to an interface that is administratively down, and then (c)
attempting to set the PACKET_FANOUT sockopt. The setsockopt call will
fail, but will corrupt ptype_all in the kernel. Subsequent network traffic
will induce a panic when evaulating the corrupted ptype_all entry. A
test program is attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800254/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771431]
*** MASS BUG UPDATE ** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.17.7-200.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771431 Title: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer) Status in linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux package in Fedora: Invalid Bug description: Hi I got an issue on Ubuntu 18.04 with latest packages. uname -a: Linux MyLaptop 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lshw: *-usb:0 description: Keyboard product: Lenovo USB Receiver vendor: Lenovo physical id: 3 bus info: usb@1:3 version: 1.05 capabilities: usb-2.00 configuration: driver=usbhid maxpower=100mA speed=12Mbit/s My wireless keyboard is not working, Ubuntu only recognize some special keys (Super, Ctrl, Shift, Alt) This is a Mouse+Keyboard combo using a wireless receiver by usb: lsusb: Bus 001 Device 005: ID 17ef:609b Lenovo Mouse works fine, and in Windows 10 it works with no issues. I found multiple reported problems with this keyboard in other distros (and from Asus too, as the real manufacturer is Primax Electronics). https://forums.lenovo.com/t5/Linux-Discussion/Professional-Wireless-Keyboard-not-working-on-Linux/td-p/3726486 https://ubuntuforums.org/showthread.php?t=2378862 https://askubuntu.com/questions/897729/lenovo-professional-wireless-keyboard-and-mouse-combo-not-working-in-ubuntu https://forums.linuxmint.com/viewtopic.php?f=49=260093=20a073d5dd8abb1b7f23be608d7fdfd7 https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/ REPORTS ON KERNEL MAILING LISTS: https://www.spinics.net/lists/linux-usb/msg168719.html https://www.spinics.net/lists/linux-input/msg56210.html https://www.spinics.net/lists/linux-usb/msg173012.html https://www.spinics.net/lists/linux-input/msg58221.html There is a workaround (I still didn't tried) but it needs to compile an specific driver. https://github.com/y-trudeau/linux_lenovo_ultraslim_plus There is already a kernel report about this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: julian 1342 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 15 15:53:41 2018 InstallationDate: Installed on 2018-05-14 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20FJS0NT07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=818481db-36cb-4dba-8da5-8ecf15750b3b ro noapic acpi=off vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET38W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FJS0NT07 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1KET38W(1.25):bd03/27/2018:svnLENOVO:pn20FJS0NT07:pvrThinkPadT560:rvnLENOVO:rn20FJS0NT07:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T560 dmi.product.name: 20FJS0NT07 dmi.product.version: ThinkPad T560 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1771431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771431] Re: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer)
** Changed in: linux (Fedora) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771431 Title: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer) Status in linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux package in Fedora: Invalid Bug description: Hi I got an issue on Ubuntu 18.04 with latest packages. uname -a: Linux MyLaptop 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lshw: *-usb:0 description: Keyboard product: Lenovo USB Receiver vendor: Lenovo physical id: 3 bus info: usb@1:3 version: 1.05 capabilities: usb-2.00 configuration: driver=usbhid maxpower=100mA speed=12Mbit/s My wireless keyboard is not working, Ubuntu only recognize some special keys (Super, Ctrl, Shift, Alt) This is a Mouse+Keyboard combo using a wireless receiver by usb: lsusb: Bus 001 Device 005: ID 17ef:609b Lenovo Mouse works fine, and in Windows 10 it works with no issues. I found multiple reported problems with this keyboard in other distros (and from Asus too, as the real manufacturer is Primax Electronics). https://forums.lenovo.com/t5/Linux-Discussion/Professional-Wireless-Keyboard-not-working-on-Linux/td-p/3726486 https://ubuntuforums.org/showthread.php?t=2378862 https://askubuntu.com/questions/897729/lenovo-professional-wireless-keyboard-and-mouse-combo-not-working-in-ubuntu https://forums.linuxmint.com/viewtopic.php?f=49=260093=20a073d5dd8abb1b7f23be608d7fdfd7 https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/ REPORTS ON KERNEL MAILING LISTS: https://www.spinics.net/lists/linux-usb/msg168719.html https://www.spinics.net/lists/linux-input/msg56210.html https://www.spinics.net/lists/linux-usb/msg173012.html https://www.spinics.net/lists/linux-input/msg58221.html There is a workaround (I still didn't tried) but it needs to compile an specific driver. https://github.com/y-trudeau/linux_lenovo_ultraslim_plus There is already a kernel report about this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: julian 1342 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 15 15:53:41 2018 InstallationDate: Installed on 2018-05-14 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20FJS0NT07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=818481db-36cb-4dba-8da5-8ecf15750b3b ro noapic acpi=off vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET38W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FJS0NT07 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1KET38W(1.25):bd03/27/2018:svnLENOVO:pn20FJS0NT07:pvrThinkPadT560:rvnLENOVO:rn20FJS0NT07:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T560 dmi.product.name: 20FJS0NT07 dmi.product.version: ThinkPad T560 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1771431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771431]
*** This bug has been marked as a duplicate of bug 1625415 *** -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771431 Title: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer) Status in linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux package in Fedora: Invalid Bug description: Hi I got an issue on Ubuntu 18.04 with latest packages. uname -a: Linux MyLaptop 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lshw: *-usb:0 description: Keyboard product: Lenovo USB Receiver vendor: Lenovo physical id: 3 bus info: usb@1:3 version: 1.05 capabilities: usb-2.00 configuration: driver=usbhid maxpower=100mA speed=12Mbit/s My wireless keyboard is not working, Ubuntu only recognize some special keys (Super, Ctrl, Shift, Alt) This is a Mouse+Keyboard combo using a wireless receiver by usb: lsusb: Bus 001 Device 005: ID 17ef:609b Lenovo Mouse works fine, and in Windows 10 it works with no issues. I found multiple reported problems with this keyboard in other distros (and from Asus too, as the real manufacturer is Primax Electronics). https://forums.lenovo.com/t5/Linux-Discussion/Professional-Wireless-Keyboard-not-working-on-Linux/td-p/3726486 https://ubuntuforums.org/showthread.php?t=2378862 https://askubuntu.com/questions/897729/lenovo-professional-wireless-keyboard-and-mouse-combo-not-working-in-ubuntu https://forums.linuxmint.com/viewtopic.php?f=49=260093=20a073d5dd8abb1b7f23be608d7fdfd7 https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/ REPORTS ON KERNEL MAILING LISTS: https://www.spinics.net/lists/linux-usb/msg168719.html https://www.spinics.net/lists/linux-input/msg56210.html https://www.spinics.net/lists/linux-usb/msg173012.html https://www.spinics.net/lists/linux-input/msg58221.html There is a workaround (I still didn't tried) but it needs to compile an specific driver. https://github.com/y-trudeau/linux_lenovo_ultraslim_plus There is already a kernel report about this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: julian 1342 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 15 15:53:41 2018 InstallationDate: Installed on 2018-05-14 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20FJS0NT07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=818481db-36cb-4dba-8da5-8ecf15750b3b ro noapic acpi=off vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET38W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FJS0NT07 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1KET38W(1.25):bd03/27/2018:svnLENOVO:pn20FJS0NT07:pvrThinkPadT560:rvnLENOVO:rn20FJS0NT07:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T560 dmi.product.name: 20FJS0NT07 dmi.product.version: ThinkPad T560 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1771431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797367] Re: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding
SRU submitted:
[SRU][Cosmic][Bionic][PATCH 0/6] Fixes for LP1797367
https://lists.ubuntu.com/archives/kernel-team/2018-November/096556.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797367
Title:
Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding
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:
== SRU Justification ==
While running a series of stress tests for network on a bond device on Ubuntu
18.04.1 with kernel 4.15.0-36.39,
kernel panic is observed (btw. also on non-bond devices).
This looks like a race between disabling a qeth device and accessing debugfs.
This is critical and leads repeatedly to a crash (sooner or later).
== Fix ==
e19e5be8b4ca ("s390/qeth: sanitize strings in debug messages")
pre-reqs:
750b162 ("s390/qeth: reduce hard-coded access to ccw channels")
d857e11 ("s390/qeth: remove outdated portname debug msg")
9d0a58f ("s390/qeth: avoid using is_multicast_ether_addr_64bits on (u8 *)[6]")
8174aa8 ("s390/qeth: consolidate qeth MAC address helpers")
4641b02 ("s390/qeth: don't keep track of MAC address's cast type")
== Regression Potential ==
Low, because:
- limited to s390x
- and again limited to qeth driver
- patches a problem identified during testing
- fix was tested by IBM before submitted
== Test Case ==
run:
#!/bin/bash
var=0
while :
do
var=$((var + 1))
echo "DBG count is $var"
mkdir /tmp/DBGINFO
dbginfo.sh -d /tmp/DBGINFO
rm -rf /tmp/DBGINFO*
echo "chzdev now is $var"
chzdev -e
chzdev -d
done
and in avg. in less than 20 cycles a crash happens (usually < 10).
__
== Comment: #0 - Athira Rajeev
---Problem Description---
While running a series of stress tests for network bonding on UBUNTU 18.04.1
with kernel 4.15.0-36.39, kernel panic is observed.
There are two instance of panic experienced with the same test procedures one
of which indicates to be a kernel BUG.
Contact Information = Athira Rajeev , Waiki
Wright < wa...@us.ibm.com >
---uname output---
#39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 4.15.0-36.39
Machine Type = This issue is observed on z13 system
---Debugger---
A debugger was configured,
---Steps to Reproduce---
This happens while running stress tests for network bonding. kernel memory
exposure attempt is detected and the BUG() is called from the code snippet:
mm/usercopy.c:72
dump was configured and crash dump is available.
Results of few crash commands like bt, log are added in Attachment
Relevant part of dmesg pointing to kernel BUG
<<>>
[14746.977364] kernel BUG at
/build/linux-PABIrW/linux-4.15.0/mm/usercopy.c:72!
[14746.977377] illegal operation: 0001 ilc:1 [#1] SMP
[14746.977378] Modules linked in: macsec vsock_diag vsock sctp_diag sctp
dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag
netlink_diag bonding binfmt_misc qeth_l3 8021q garp mrp stp llc xt_tcpudp
qeth_l2 nf_conntrack_ipv6 nf_defrag_ipv6 scsi_dh_rdac scsi_dh_emc scsi_dh_alua
s390_trng ghash_s390 prng sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch
eadm_sch nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c
crc32_vx_s390 qeth ccwgroup ip6table_filter ip6_tables vfio_ccw vfio_mdev mdev
vfio_iommu_type1 vfio iptable_filter sch_fq_codel ip_tables x_tables aes_s390
des_s390 des_generic dm_crypt dm_service_time dm_multipath zfcp
scsi_transport_fc qdio dasd_eckd_mod dasd_mod btrfs xor zstd_compress raid6_pq
zlib_deflate
[14746.977401] CPU: 1 PID: 20905 Comm: dump2tar Tainted: G OE
4.15.0-36-generic #39-Ubuntu
[14746.977403] Hardware name: IBM 3906 M02 757 (LPAR)
[14746.977404] Krnl PSW : 0f2d230d 6abe14d5
(__check_object_size+0x15a/0x1e0)
[14746.977408]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0
RI:0 EA:3
[14746.977410] Krnl GPRS: 0002 00e95334 0064
0001e6518828
[14746.977412]0037cc8e 00a9577c
[14746.977413]647b 0001d8c120a8 0001
8088
[14746.977433]0001d8c0a020 0090da38 0037cc8e
00016fdfbcd0
[14746.977440] Krnl Code: 0037cc82: c0200038ef69larl
%r2,a9ab54
0037cc88: c0e5fff32838brasl
%r14,1e1cf8
#0037cc8e: a7f40001brc
15,37cc90
>0037cc92: e330d0080004lg
%r3,8(%r13)
0037cc98: e320d004lg
%r2,0(%r13)
[Kernel-packages] [Bug 1771431]
Kernel 4.18.11-200.fc28.x86_64 and it still doesn't work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771431 Title: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer) Status in linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux package in Fedora: Invalid Bug description: Hi I got an issue on Ubuntu 18.04 with latest packages. uname -a: Linux MyLaptop 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lshw: *-usb:0 description: Keyboard product: Lenovo USB Receiver vendor: Lenovo physical id: 3 bus info: usb@1:3 version: 1.05 capabilities: usb-2.00 configuration: driver=usbhid maxpower=100mA speed=12Mbit/s My wireless keyboard is not working, Ubuntu only recognize some special keys (Super, Ctrl, Shift, Alt) This is a Mouse+Keyboard combo using a wireless receiver by usb: lsusb: Bus 001 Device 005: ID 17ef:609b Lenovo Mouse works fine, and in Windows 10 it works with no issues. I found multiple reported problems with this keyboard in other distros (and from Asus too, as the real manufacturer is Primax Electronics). https://forums.lenovo.com/t5/Linux-Discussion/Professional-Wireless-Keyboard-not-working-on-Linux/td-p/3726486 https://ubuntuforums.org/showthread.php?t=2378862 https://askubuntu.com/questions/897729/lenovo-professional-wireless-keyboard-and-mouse-combo-not-working-in-ubuntu https://forums.linuxmint.com/viewtopic.php?f=49=260093=20a073d5dd8abb1b7f23be608d7fdfd7 https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/ REPORTS ON KERNEL MAILING LISTS: https://www.spinics.net/lists/linux-usb/msg168719.html https://www.spinics.net/lists/linux-input/msg56210.html https://www.spinics.net/lists/linux-usb/msg173012.html https://www.spinics.net/lists/linux-input/msg58221.html There is a workaround (I still didn't tried) but it needs to compile an specific driver. https://github.com/y-trudeau/linux_lenovo_ultraslim_plus There is already a kernel report about this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: julian 1342 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 15 15:53:41 2018 InstallationDate: Installed on 2018-05-14 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20FJS0NT07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=818481db-36cb-4dba-8da5-8ecf15750b3b ro noapic acpi=off vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET38W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FJS0NT07 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1KET38W(1.25):bd03/27/2018:svnLENOVO:pn20FJS0NT07:pvrThinkPadT560:rvnLENOVO:rn20FJS0NT07:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T560 dmi.product.name: 20FJS0NT07 dmi.product.version: ThinkPad T560 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1771431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771431]
*** MASS BUG UPDATE ** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771431 Title: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer) Status in linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux package in Fedora: Invalid Bug description: Hi I got an issue on Ubuntu 18.04 with latest packages. uname -a: Linux MyLaptop 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lshw: *-usb:0 description: Keyboard product: Lenovo USB Receiver vendor: Lenovo physical id: 3 bus info: usb@1:3 version: 1.05 capabilities: usb-2.00 configuration: driver=usbhid maxpower=100mA speed=12Mbit/s My wireless keyboard is not working, Ubuntu only recognize some special keys (Super, Ctrl, Shift, Alt) This is a Mouse+Keyboard combo using a wireless receiver by usb: lsusb: Bus 001 Device 005: ID 17ef:609b Lenovo Mouse works fine, and in Windows 10 it works with no issues. I found multiple reported problems with this keyboard in other distros (and from Asus too, as the real manufacturer is Primax Electronics). https://forums.lenovo.com/t5/Linux-Discussion/Professional-Wireless-Keyboard-not-working-on-Linux/td-p/3726486 https://ubuntuforums.org/showthread.php?t=2378862 https://askubuntu.com/questions/897729/lenovo-professional-wireless-keyboard-and-mouse-combo-not-working-in-ubuntu https://forums.linuxmint.com/viewtopic.php?f=49=260093=20a073d5dd8abb1b7f23be608d7fdfd7 https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/ REPORTS ON KERNEL MAILING LISTS: https://www.spinics.net/lists/linux-usb/msg168719.html https://www.spinics.net/lists/linux-input/msg56210.html https://www.spinics.net/lists/linux-usb/msg173012.html https://www.spinics.net/lists/linux-input/msg58221.html There is a workaround (I still didn't tried) but it needs to compile an specific driver. https://github.com/y-trudeau/linux_lenovo_ultraslim_plus There is already a kernel report about this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: julian 1342 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 15 15:53:41 2018 InstallationDate: Installed on 2018-05-14 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20FJS0NT07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=818481db-36cb-4dba-8da5-8ecf15750b3b ro noapic acpi=off vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET38W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FJS0NT07 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1KET38W(1.25):bd03/27/2018:svnLENOVO:pn20FJS0NT07:pvrThinkPadT560:rvnLENOVO:rn20FJS0NT07:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T560 dmi.product.name: 20FJS0NT07 dmi.product.version: ThinkPad T560 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1771431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797367] Re: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding
** Description changed:
- == Comment: #0 - Athira Rajeev
+ == SRU Justification ==
+
+ While running a series of stress tests for network on a bond device on Ubuntu
18.04.1 with kernel 4.15.0-36.39,
+ kernel panic is observed (btw. also on non-bond devices).
+ This looks like a race between disabling a qeth device and accessing debugfs.
+ This is critical and leads repeatedly to a crash (sooner or later).
+
+ == Fix ==
+
+ e19e5be8b4ca ("s390/qeth: sanitize strings in debug messages")
+
+ pre-reqs:
+ 750b162 ("s390/qeth: reduce hard-coded access to ccw channels")
+ d857e11 ("s390/qeth: remove outdated portname debug msg")
+ 9d0a58f ("s390/qeth: avoid using is_multicast_ether_addr_64bits on (u8 *)[6]")
+ 8174aa8 ("s390/qeth: consolidate qeth MAC address helpers")
+ 4641b02 ("s390/qeth: don't keep track of MAC address's cast type")
+
+ == Regression Potential ==
+
+ Low, because:
+
+ - limited to s390x
+ - and again limited to qeth driver
+ - patches a problem identified during testing
+ - fix was tested by IBM before submitted
+
+ == Test Case ==
+
+ run:
+#!/bin/bash
+var=0
+while :
+do
+ var=$((var + 1))
+ echo "DBG count is $var"
+ mkdir /tmp/DBGINFO
+ dbginfo.sh -d /tmp/DBGINFO
+ rm -rf /tmp/DBGINFO*
+ echo "chzdev now is $var"
+ chzdev -e
+ chzdev -d
+done
+ and in avg. in less than 20 cycles a crash happens (usually < 10).
+
+ __
+
+ == Comment: #0 - Athira Rajeev
---Problem Description---
While running a series of stress tests for network bonding on UBUNTU 18.04.1
with kernel 4.15.0-36.39, kernel panic is observed.
There are two instance of panic experienced with the same test procedures one
of which indicates to be a kernel BUG.
-
- Contact Information = Athira Rajeev , Waiki Wright <
wa...@us.ibm.com >
-
+
+ Contact Information = Athira Rajeev , Waiki Wright
+ < wa...@us.ibm.com >
+
---uname output---
#39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 4.15.0-36.39
-
- Machine Type = This issue is observed on z13 system
- ---Debugger---
- A debugger was configured,
-
+
+ Machine Type = This issue is observed on z13 system
+ ---Debugger---
+ A debugger was configured,
+
---Steps to Reproduce---
- This happens while running stress tests for network bonding. kernel memory
exposure attempt is detected and the BUG() is called from the code snippet:
mm/usercopy.c:72
- dump was configured and crash dump is available.
- Results of few crash commands like bt, log are added in Attachment
+ This happens while running stress tests for network bonding. kernel memory
exposure attempt is detected and the BUG() is called from the code snippet:
mm/usercopy.c:72
+ dump was configured and crash dump is available.
+ Results of few crash commands like bt, log are added in Attachment
Relevant part of dmesg pointing to kernel BUG
<<>>
[14746.977364] kernel BUG at
/build/linux-PABIrW/linux-4.15.0/mm/usercopy.c:72!
[14746.977377] illegal operation: 0001 ilc:1 [#1] SMP
[14746.977378] Modules linked in: macsec vsock_diag vsock sctp_diag sctp
dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag
netlink_diag bonding binfmt_misc qeth_l3 8021q garp mrp stp llc xt_tcpudp
qeth_l2 nf_conntrack_ipv6 nf_defrag_ipv6 scsi_dh_rdac scsi_dh_emc scsi_dh_alua
s390_trng ghash_s390 prng sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch
eadm_sch nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c
crc32_vx_s390 qeth ccwgroup ip6table_filter ip6_tables vfio_ccw vfio_mdev mdev
vfio_iommu_type1 vfio iptable_filter sch_fq_codel ip_tables x_tables aes_s390
des_s390 des_generic dm_crypt dm_service_time dm_multipath zfcp
scsi_transport_fc qdio dasd_eckd_mod dasd_mod btrfs xor zstd_compress raid6_pq
zlib_deflate
[14746.977401] CPU: 1 PID: 20905 Comm: dump2tar Tainted: G OE
4.15.0-36-generic #39-Ubuntu
[14746.977403] Hardware name: IBM 3906 M02 757 (LPAR)
[14746.977404] Krnl PSW : 0f2d230d 6abe14d5
(__check_object_size+0x15a/0x1e0)
[14746.977408]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0
RI:0 EA:3
[14746.977410] Krnl GPRS: 0002 00e95334 0064
0001e6518828
[14746.977412]0037cc8e 00a9577c
[14746.977413]647b 0001d8c120a8 0001
8088
[14746.977433]0001d8c0a020 0090da38 0037cc8e
00016fdfbcd0
[14746.977440] Krnl Code: 0037cc82: c0200038ef69larl
%r2,a9ab54
- 0037cc88: c0e5fff32838brasl
%r14,1e1cf8
- #0037cc8e: a7f40001brc
15,37cc90
- >0037cc92: e330d0080004lg
%r3,8(%r13)
- 0037cc98: e320d004lg
[Kernel-packages] [Bug 1800465] Re: Vulkan error when using NVIDIA-Prime
I solved this just putting nvidia-drm.modeset=0 option into my grub config. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1800465 Title: Vulkan error when using NVIDIA-Prime Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-prime package in Ubuntu: Confirmed Bug description: After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils, switching to NVIDIA and then running vulkaninfo or vulkan-cube works perfectly. But when you reboot and update, then switch to Intel, then back to Nvidia, all Vulkan programs give an "Assertion `!err' failed." Vulkaninfo: === Presentable Surfaces: = GPU id : 0 (GeForce GTX 960M) Surface type : VK_KHR_xcb_surface vulkaninfo: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253: AppDumpSurfaceFormats: Assertion `!err' failed. Annullato (core dump creato) Vulkancube: vulkan-cube: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: demo_init_vk_swapchain: Assertion `!err' failed. Annullato (core dump creato) I still have not found a workaround for that, the only way to get it working again is to reinstall everything. - Install Ubuntu 18.10 - Install proprietary 390 NVIDIA drivers - Switch NVIDIA-Prime to NVIDIA - Testing the vulkan capabilities works - Updating the system then switching to intel - Reboot - Switch to nvida - Now all Vulkan programs when using NVIDIA give that error To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@albertomilone so this is happening to me since 18.04 is my gpu not supported also? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility 3.30.1' the pendrive
Launchpad has imported 3 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=201371. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-10-10T18:34:55+00:00 caravena wrote: Hello, Open bug in launchpad.net https://bugs.launchpad.net/bugs/1797190 "I am trying to format a pendrive of 2TB(Purchased in China for ebay). What I do is the following: 1) I start the notebook with Linux 4.18.0-9 2) I start with my GNOME session 3) I connect the pendrive 4) I open Nautilus 5) The pendrive in nautilus appears as mounted 6) In nautilus I hit a right click with the mouse to my pedrive 7) I choose 'Format' 8) A window opens where I can only choose between: ext4, NTFS or FAT 9) I leave the default -> 'NTFS' 10) Next press 11) I change to the next window where the information of what is going to happen appears and I confirm the format 12) Then I return to nautilius 13) The pendrive appears in nautilus 14) It can not be accessed, even though the pendrive is mounted" Best regards, -- Cristian Aravena Romero (caravena) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797190/comments/5 On 2018-10-10T18:44:22+00:00 caravena wrote: List: linux-usb https://marc.info/?l=linux-usb=153919676204905=2 -- Cristian Aravena Romero (caravena) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797190/comments/6 On 2018-10-10T19:14:47+00:00 greg wrote: On Wed, Oct 10, 2018 at 06:34:55PM +, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=201371 > > Bug ID: 201371 >Summary: It can not be formatted with 'gnome-disk-utility' the > pendrive >Product: Drivers >Version: 2.5 > Kernel Version: Ubuntu 4.18.0-9.10-generic 4.18.12 All USB bugs should be sent to the linux-...@vger.kernel.org mailing list, and not entered into bugzilla. Please bring this issue up there, if it is still a problem in the latest kernel release. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797190/comments/7 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => 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/1797190 Title: It can not be formatted with 'gnome-disk-utility 3.30.1' the pendrive Status in Linux: Confirmed Status in gnome-disk-utility package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: New Bug description: List: linux-usb https://marc.info/?l=linux-usb=153919676204905=2 --- https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104 --- Hello, I am trying to format a pendrive of 2TB(Purchased in China for ebay). What I do is the following: 1) I start the notebook with Linux 4.18.0-9 2) I start with my GNOME session 3) I connect the pendrive 4) I open Nautilus 5) The pendrive in nautilus appears as mounted 6) In nautilus I hit a right click with the mouse to my pedrive 7) I choose 'Format' 8) A window opens where I can only choose between: ext4, NTFS or FAT 9) I leave the default -> 'NTFS' 10) Next press 11) I change to the next window where the information of what is going to happen appears and I confirm the format 12) Then I return to nautilius 13) The pendrive appears in nautilus 14) It can not be accessed, even though the pendrive is mounted Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2162 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 14:30:28 2018 InstallationDate: Installed on 2017-10-13 (362 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175
[Kernel-packages] [Bug 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu
Launchpad has imported 165 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=199911. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-06-03T17:46:08+00:00 soundhermit wrote: Razer Blade 15 2018 touchpad support [1532:0233] Bus 001 Device 005: ID 1532:0233 Razer USA, Ltd Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x1532 Razer USA, Ltd idProduct 0x0233 bcdDevice2.00 iManufacturer 1 Razer iProduct2 Razer Blade iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0054 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 61 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 159 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 94 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 1 can't get device qualifier: Resource temporarily unavailable can't get debug descriptor: Resource temporarily unavailable Device Status: 0x (Bus Powered) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/0 On 2018-06-24T18:56:55+00:00 soundhermit wrote: Created attachment 276785
[Kernel-packages] [Bug 1797359] Re: Not work 802.11ac WLAN Adapter
Launchpad has imported 2 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=201375. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-10-11T11:09:40+00:00 caravena wrote: Hello, Open bug in launchpad.net https://bugs.launchpad.net/bugs/1797359 "At the moment I have two WiFi adapters: 1) TP-LINK TL-WN722N (working) 2) USB WiFi adapter (not working)" Best regards, -- Cristian Aravena Romero (caravena) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797359/comments/2 On 2018-10-11T11:27:30+00:00 caravena wrote: Created attachment 278991 dmesg_4.19.0-041900rc7-generic Hello, It also does not work with this version of the kernel. Best regards, -- Cristian Aravena Romero (caravena) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797359/comments/3 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => 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/1797359 Title: Not work 802.11ac WLAN Adapter Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: Hello, At the moment I have two WiFi adapters: 1) TP-LINK TL-WN722N (working) 2) USB WiFi adapter (not working) Initial report: Bug 1743872 Best regards, - Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2027 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 11 07:57:40 2018 InstallationDate: Installed on 2017-10-13 (362 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1797359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Created attachment 279239 fedora kernel config for linux 4.18.6 You can use it to build a kernel with the arch build system and test if it works in archlinux. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
*kms -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796743] Re: Ubuntu 18.10 - Alienware 17 R5 crashes on sleep
Launchpad has imported 2 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=201353. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-10-09T11:58:56+00:00 caravena wrote: Hello, Open bug in launchpad.net https://bugs.launchpad.net/bugs/1796743 "If the machine goes to sleep, either because I close the lid or because it idles too long, it ends up in a weird state when I try to resume. If I press the power/Alien button, the fan runs and the keyboard/trackpad light up but nothing happens. Ultimately I need to hard power off the laptop (by holding the power button in for three seconds) which causes it to boot from scratch." Best regards, -- Cristian Aravena Romero (caravena) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796743/comments/4 On 2018-10-17T01:00:29+00:00 yu.c.chen wrote: Fixed in 4.19-rc7. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796743/comments/7 ** Changed in: linux Status: Unknown => Fix Released ** Changed in: linux Importance: Unknown => 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/1796743 Title: Ubuntu 18.10 - Alienware 17 R5 crashes on sleep Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: If the machine goes to sleep, either because I close the lid or because it idles too long, it ends up in a weird state when I try to resume. If I press the power/Alien button, the fan runs and the keyboard/trackpad light up but nothing happens. Ultimately I need to hard power off the laptop (by holding the power button in for three seconds) which causes it to boot from scratch. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: feoh 2895 F pulseaudio CurrentDesktop: GNOME Date: Mon Oct 8 14:25:16 2018 InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) MachineType: Alienware Alienware 17 R5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.5.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.5.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
Launchpad has imported 34 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=201275. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-09-28T16:51:31+00:00 quirin.blaeser wrote: Created attachment 278829 lsusb lspci cpuinfo config url sensors sensors reports a power consumption of 13 W idle for 4.18.10 sensors reports a power consumption of 7 W idle for 4.18.9 Attached: lsusb lspci cpuinfo url to mainboard an graphics card kernel config output of sensors while idle Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796720/comments/0 On 2018-09-28T17:11:57+00:00 alexdeucher wrote: Can you bisect? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796720/comments/1 On 2018-09-28T18:14:20+00:00 alexdeucher wrote: Git bisect howto: https://www.kernel.org/doc/html/v4.18/admin-guide/bug-bisect.html Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796720/comments/2 On 2018-09-28T21:51:16+00:00 quirin.blaeser wrote: Am 28.09.18 um 20:14 schrieb bugzilla-dae...@bugzilla.kernel.org: > https://bugzilla.kernel.org/show_bug.cgi?id=201275 > > --- Comment #2 from Alex Deucher (alexdeuc...@gmail.com) --- > Git bisect howto: > https://www.kernel.org/doc/html/v4.18/admin-guide/bug-bisect.html > Sounds prakticable, but may take 1-2 days. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796720/comments/3 On 2018-09-29T02:44:41+00:00 Dieter wrote: I can second that for RX580 (Polaris20) It raised to 60 W 'idle' (from ~31/32 W with 4.18.9) bisect? - Not so fast 'cause I use openSUSE Tumbleweed 'Kernel:stable' when 'amd-staging-drm-next' do NOT work for me --- and it do NOT work for me since 21/22 August but that come with another ticket. amdgpu-pci-0100 Adapter: PCI adapter vddgfx: +1.20 V fan1: 886 RPM temp1:+43.0°C (crit = +94.0°C, hyst = -273.1°C) power1: 59.16 W (cap = 175.00 W) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796720/comments/4 On 2018-09-29T21:20:33+00:00 quirin.blaeser wrote: Created attachment 278841 bisect result Includes bisect steps + sensors output Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796720/comments/5 On 2018-09-29T21:28:30+00:00 quirin.blaeser wrote: RX560 is Polaris11, so Bug may be ported from Polaris20 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796720/comments/6 On 2018-09-30T14:07:38+00:00 quirin.blaeser wrote: For now i have resolved this problem by simply removing patch for 4.18.11 git diff 93b100ddda3be284be160e9ccba28c7f8f21ab73^1..93b100ddda3be284be160e9ccba28c7f8f21ab73 and patch -R -p1 or without "-R": git diff 93b100ddda3be284be160e9ccba28c7f8f21ab73..93b100ddda3be284be160e9ccba28c7f8f21ab73^1 Maybe the specs for Vega and Polaris just differ at this point? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796720/comments/7 On 2018-10-04T17:56:53+00:00 quirin.blaeser wrote: 4.18.12 Bug still present, removing 93b100ddda3be284be160e9ccba28c7f8f21ab73 solves this problem for now. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796720/comments/8 On 2018-10-04T20:21:41+00:00 alexdeucher wrote: I don't think this is a bug. The problem is, prior to that patch, the display component was requesting minimum clocks that were 10x too low. This saved power, but led to display problems on some systems because the clocks were too low to sustain the display requirements. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796720/comments/9 On 2018-10-04T22:48:47+00:00 Dieter wrote: (In reply to Alex Deucher from comment #9) > I don't think this is a bug. The problem is, prior to that patch, the > display component was requesting minimum clocks that were 10x too low. This > saved power, but led to display problems on some systems because the clocks > were too low to sustain the display requirements. Sorry Alex, what? _All_ was fine _before_ this commit for ages with
[Kernel-packages] [Bug 1776563]
Hmm, maybe a different configuration of the kernel or a different version? Not sure what kernel Fedora uses. BTW the latest 1.05 BIOS update on my Lenovo A485 fixes the underlying BIOS issue, so my system doesn't suffer from this issue anymore (doesn't mean a kernel fix wouldn't be a good idea, since not all OEM's are good about fixing issues for "unsupported platforms"). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27
Some notes:
1. /dev/vdb did appear to have an ext4 file system on it before we created the
file system.
2. [jbd2/vdb-8] running implies the file system was mounted at some point on
/dev/vdb
3. Nothing seemed to have mounted /dev/vdb
The file system was indeed mounted during boot:
[ 94.945578] EXT4-fs (vdb): mounted filesystem with ordered data mode.
Opts: (null)
After a reboot the [jbd2/vdb-8] thread is no longer running and zfs can
create the file systems w/o any issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801349
Title:
zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27
Status in OpenStack LXD Charm:
New
Status in linux package in Ubuntu:
In Progress
Bug description:
Test: tests/gate-basic-cosmic-rocky
As part of the config, the lxd charm creates a pool device depending
on the config. The test config is:
lxd_config = {
'block-devices': '/dev/vdb',
'ephemeral-unmount': '/mnt',
'storage-type': 'zfs',
'overwrite': True
}
The config drive is normally mounted on /mnt, and the lxd charm
umounts it as part of the start up. The /etc/fstab on the unit is:
# cat /etc/fstab
LABEL=cloudimg-rootfs /ext4 defaults0 0
LABEL=UEFI /boot/efi vfatdefaults0 0
/dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig
0 2
/dev/vdcnoneswapsw,comment=cloudconfig 0 0
However, even after umount-ing the /mnt off of /dev/vdb, the zpool create
command still fails:
# zpool create -f lxd /dev/vdb
/dev/vdb is in use and contains a unknown filesystem.
If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then
rebooted, then the zpool create command succeeds:
# zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT
lxd 14.9G 106K 14.9G - 0% 0% 1.00x ONLINE -
# zpool status lxd
pool: lxd
state: ONLINE
scan: none requested
config:
NAMESTATE READ WRITE CKSUM
lxd ONLINE 0 0 0
vdb ONLINE 0 0 0
errors: No known data errors
Something odd is going on with cosmic (18.10) and the combination of
lxd, zfs and the kernel
lxd version: 3.6
zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
Linux: 4.18.0-10-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
we could use the same config...,if we use the same config and the problem persists then it is probably a fedora kernel patch that fixes the issues with Acer Aspire A315-41G series. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Changed in: ubuntu-power-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/1790832
Title:
crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
IBM is requesting this patch in all releases order to fix the sleep-in-atomic
bugs in AES-CBC and AES-XTS VMX implementations.
This patch is a clean cherry pick and has already been applied to
Cosmic. It is also needed in Xenial, but there was a minor context
diff, so the Xenial SRU will be sent separatly.
== Fix ==
0522236d4f9c ("crypto: vmx - Fix sleep-in-atomic bugs")
== Regression Potential ==
Low. This patch has also been cc'd to upstream stable, so it has had
additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Paulo Flabiano Smorigo
Please include the following commit in order to fix the sleep-in-atomic bugs
in AES-CBC and AES-XTS VMX implementations [1]:
0522236 crypto: vmx - Fix sleep-in-atomic bugs
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
siyia: I seem to be getting freezing during suspend too (though you seem to be getting it more than I). There are some with Ryzen that their crashes were fixed if they disabled C6 powerstate. Since I use a laptop that was mostly a non-option for me, but I wrote as script so systemd will disable C6 sleep before suspend and then enable it again after suspend (so CPU doesn't happen to be in C6 state aronud suspend time). May or may not work. Since it has only happened every once in a while for me, I may not know for several days if the fix worked or not. You can test it out by putting https://gist.github.com/samcv/0b6a915aadcddc0e19640c20d9dd3164 as /usr/lib/systemd/system-sleep/disable-enable-c6-state.sh and doing `chmod +x /usr/lib/systemd/system-sleep/disable-enable-c6-state.sh`. You will need download https://github.com/r4m0n/ZenStates-Linux/blob/master/zenstates.py and then set the ZENSTATES variable in my `disable-enable-c6-state.sh` script to wherever you put the script. If the script is working you should get an output from `journalctl -b 0 | grep -Ei '(enabled|disabled)\s*c6'` after you have done a suspend/resume cycle. If that doesn't fix it, your issue (and possibly mine depending on how my results go) should probably have their own bug filed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
ok i figured this out.it's more like fedora has acpi working on these laptops with noapic.Other distros with noapic cannot sleep but fedora can. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
My wi-fi: 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) Subsystem: Lite-On Communications Inc QCA9377 802.11ac Wireless Network Adapter Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci Also in dmeseg i have errors for this module (firmware load failed) but wifi and bluetooth works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
