[Kernel-packages] [Bug 1878990] Re: Eoan update: upstream stable patchset 2020-05-15
** Changed in: linux (Ubuntu Eoan) 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/1878990 Title: Eoan update: upstream stable patchset 2020-05-15 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: 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 2020-05-15 Ported from the following upstream stable releases: v4.19.120, v5.4.37 v5.4.38 from git://git.kernel.org/ remoteproc: Fix wrong rvring index computation usb: dwc3: gadget: Do link recovery for SS and SSP usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete iio:ad7797: Use correct attribute_group ASoC: q6dsp6: q6afe-dai: add missing channels to MI2S DAIs ASoC: tas571x: disable regulators on failed probe ASoC: wm8960: Fix wrong clock after suspend & resume nfsd: memory corruption in nfsd4_lock() i2c: altera: use proper variable to hold errno rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket net/cxgb4: Check the return from t4_query_params properly xfs: acquire superblock freeze protection on eofblocks scans svcrdma: Fix trace point use-after-free race svcrdma: Fix leak of svc_rdma_recv_ctxt objects PCI: Move Apex Edge TPU class quirk to fix BAR assignment ARM: dts: bcm283x: Disable dsi0 node cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled net/mlx5: Fix failing fw tracer allocation on s390 perf/core: fix parent pid/tid in task exit events bpf, x86_32: Fix incorrect encoding in BPF_LDX zero-extension mm: shmem: disable interrupt when acquiring info->lock in userfaultfd_copy path xfs: clear PF_MEMALLOC before exiting xfsaild thread bpf, x86: Fix encoding for lower 8-bit registers in BPF_STX BPF_B net: fec: set GPR bit on suspend by DT configuration. x86: hyperv: report value of misc_features xfs: fix partially uninitialized structure in xfs_reflink_remap_extent ALSA: hda: Keep the controller initialization even if no codecs found ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported scsi: target: fix PR IN / READ FULL STATUS for FC scsi: target: tcmu: reset_ring should reset TCMU_DEV_BIT_BROKEN objtool: Fix CONFIG_UBSAN_TRAP unreachable warnings objtool: Support Clang non-section symbols in ORC dump xen/xenbus: ensure xenbus_map_ring_valloc() returns proper grant status ALSA: hda: call runtime_allow() for all hda controllers arm64: Delete the space separator in __emit_inst ext4: use matching invalidatepage in ext4_writepage ext4: increase wait time needed before reuse of deleted inode numbers ext4: convert BUG_ON's to WARN_ON's in mballoc.c hwmon: (jc42) Fix name to have no illegal characters bpf, x86_32: Fix clobbering of dst for BPF_JSET qed: Fix use after free in qed_chain_free ext4: check for non-zero journal inum in ext4_calculate_overhead ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans() printk: queue wake_up_klogd irq_work only if per-CPU areas are ready ASoC: stm32: sai: fix sai probe kbuild: fix DT binding schema rule again to avoid needless rebuilds usb: gadget: udc: atmel: Fix vbus disconnect handling afs: Make record checking use TASK_UNINTERRUPTIBLE when appropriate afs: Fix to actually set AFS_SERVER_FL_HAVE_EPOCH counter: 104-quad-8: Add lock guards - generic interface s390/ftrace: fix potential crashes when switching tracers drivers: soc: xilinx: fix firmware driver Kconfig dependency bpf: Forbid XADD on spilled pointers for unprivileged users net/mlx5e: Don't trigger IRQ multiple times on XSK wakeup to avoid WQ overruns net/mlx5e: Get the latest values from counters in switchdev mode PCI: Add ACS quirk for Zhaoxin multi-function devices PCI: Make ACS quirk implementations more uniform PCI: Unify ACS quirk desired vs provided checking PCI: Add Zhaoxin Vendor ID PCI: Add ACS quirk for Zhaoxin Root/Downstream Ports s390/pci: do not set affinity for floating irqs sched/core: Fix reset-on-fork from RT with uclamp netfilter: nat: fix error handling upon registering inet hook PM: sleep: core: Switch back to async_schedule_dev() um: ensure `make ARCH=um mrproper` removes arch/$(SUBARCH)/include/generated/ bpf, x86_32: Fix logic error in BPF_LDX zero-extension libbpf: Initialize *nl_pid s
[Kernel-packages] [Bug 1879994] Re: Eoan update: upstream stable patchset 2020-05-21
** Changed in: linux (Ubuntu Eoan) 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/1879994 Title: Eoan update: upstream stable patchset 2020-05-21 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: 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 2020-05-21 Ported from the following upstream stable releases: v4.19.122, v5.4.40 from git://git.kernel.org/ vhost: vsock: kick send_pkt worker once device is started ASoC: topology: Check return value of pcm_new_ver selftests/ipc: Fix test failure seen after initial test run ASoC: sgtl5000: Fix VAG power-on handling usb: dwc3: gadget: Properly set maxpacket limit ASoC: rsnd: Fix parent SSI start/stop in multi-SSI mode ASoC: rsnd: Fix HDMI channel mapping for multi-SSI mode ASoC: codecs: hdac_hdmi: Fix incorrect use of list_for_each_entry drm/amdgpu: Correctly initialize thermal controller for GPUs with Powerplay table v0 (e.g Hawaii) wimax/i2400m: Fix potential urb refcnt leak net: stmmac: fix enabling socfpga's ptp_ref_clock net: stmmac: Fix sub-second increment ASoC: rsnd: Don't treat master SSI in multi SSI setup as parent ASoC: rsnd: Fix "status check failed" spam for multi-SSI cifs: protect updating server->dstaddr with a spinlock scripts/config: allow colons in option strings for sed lib/mpi: Fix building for powerpc with clang net: bcmgenet: suppress warnings on failed Rx SKB allocations net: systemport: suppress warnings on failed Rx SKB allocations sctp: Fix SHUTDOWN CTSN Ack in the peer restart case drm/amdgpu: Fix oops when pp_funcs is unset in ACPI event hexagon: clean up ioremap hexagon: define ioremap_uc ALSA: hda: Match both PCI ID and SSID for driver blacklist platform/x86: GPD pocket fan: Fix error message when temp-limits are out of range mac80211: add ieee80211_is_any_nullfunc() cgroup, netclassid: remove double cond_resched ASoC: topology: Check return value of soc_tplg_create_tlv ASoC: topology: Check return value of soc_tplg_*_create ASoC: topology: Check soc_tplg_add_route return value ASoC: topology: Check return value of soc_tplg_dai_config ASoC: topology: Fix endianness issue remoteproc: qcom_q6v5_mss: fix a bug in q6v5_probe() cifs: do not share tcons with DFS tracing: Fix memory leaks in trace_events_hist.c drm/i915: Extend WaDisableDARBFClkGating to icl,ehl,tgl Revert "software node: Simplify software_node_release() function" ACPI: PM: s2idle: Fix comment in acpi_s2idle_prepare_late() Revert "drm/amd/display: setting the DIG_MODE to the correct value." tools headers UAPI: Sync copy of arm64's asm/unistd.h with the kernel sources udp: document udp_rcv_segment special case for looped packets PM / devfreq: Add missing locking while setting suspend_freq UBUNTU: upstream stable to v4.19.122, v5.4.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880758] Re: Eoan update: upstream stable patchset 2020-05-26
** Changed in: linux (Ubuntu Eoan) 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/1880758 Title: Eoan update: upstream stable patchset 2020-05-26 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: 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 2020-05-26 Ported from the following upstream stable releases: v4.19.123, v5.4.41 from git://git.kernel.org/ USB: serial: qcserial: Add DW5816e support tracing/kprobes: Fix a double initialization typo vt: fix unicode console freeing with a common interface dp83640: reverse arguments to list_add_tail fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks net: macsec: preserve ingress frame ordering net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() net_sched: sch_skbprio: add message validation to skbprio_change() net: usb: qmi_wwan: add support for DW5816e sch_choke: avoid potential panic in choke_reset() sch_sfq: validate silly quantum values tipc: fix partial topology connection closure bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). net/mlx5: Fix forced completion access non initialized command entry net/mlx5: Fix command entry leak in Internal Error State bnxt_en: Improve AER slot reset. bnxt_en: Fix VF anti-spoof filter setup. net: stricter validation of untrusted gso packets HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices sctp: Fix bundling of SHUTDOWN with COOKIE-ACK HID: usbhid: Fix race between usbhid_close() and usbhid_stop() USB: uas: add quirk for LaCie 2Big Quadra USB: serial: garmin_gps: add sanity checking for data length tracing: Add a vmalloc_sync_mappings() for safe measure KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER KVM: arm64: Fix 32bit PC wrap-around arm64: hugetlb: avoid potential NULL dereference mm/page_alloc: fix watchdog soft lockups during set_zone_contiguous() staging: gasket: Check the return value of gasket_get_bar_index() coredump: fix crash when umh is disabled batman-adv: fix batadv_nc_random_weight_tq batman-adv: Fix refcnt leak in batadv_show_throughput_override batman-adv: Fix refcnt leak in batadv_store_throughput_override batman-adv: Fix refcnt leak in batadv_v_ogm_process x86/entry/64: Fix unwind hints in register clearing code x86/entry/64: Fix unwind hints in kernel exit path x86/entry/64: Fix unwind hints in rewind_stack_do_exit() x86/unwind/orc: Don't skip the first frame for inactive tasks x86/unwind/orc: Prevent unwinding before ORC initialization x86/unwind/orc: Fix error path for bad ORC entry type x86/unwind/orc: Fix premature unwind stoppage due to IRET frames netfilter: nat: never update the UDP checksum when it's 0 netfilter: nf_osf: avoid passing pointer to local var objtool: Fix stack offset tracking for indirect CFAs scripts/decodecode: fix trapping instruction formatting ipc/mqueue.c: change __do_notify() to bypass check_kill_permission() net: macb: Fix runtime PM refcounting drm/amdgpu: move kfd suspend after ip_suspend_phase1 drm/amdgpu: drop redundant cg/pg ungate on runpm enter tty: xilinx_uartps: Fix missing id assignment to the console devlink: fix return value after hitting end in region read ipv6: Use global sernum for dst validation with nexthop objects mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly neigh: send protocol value in neighbor create notification net: dsa: Do not leave DSA master with NULL netdev_ops net: macb: fix an issue about leak related system resources net: tc35815: Fix phydev supported/advertising mask net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() net/tls: Fix sk_psock refcnt leak when in tls_data_ready() nfp: abm: fix a memory leak bug tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. bnxt_en: Return error when allocating zero size context memory. net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx() net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del() Revert "HID: wacom: generic: read the number of expected touches on a per collection basis" HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT crypto:
[Kernel-packages] [Bug 1879397] Re: Eoan update: upstream stable patchset 2020-05-18
** Changed in: linux (Ubuntu Eoan) 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/1879397 Title: Eoan update: upstream stable patchset 2020-05-18 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: 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 2020-05-18 Ported from the following upstream stable releases: v4.19.121, v5.4.39 from git://git.kernel.org/ drm/edid: Fix off-by-one in DispID DTD pixel clock drm/qxl: qxl_release leak in qxl_draw_dirty_fb() drm/qxl: qxl_release leak in qxl_hw_surface_alloc() drm/qxl: qxl_release use after free btrfs: fix block group leak when removing fails ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter ALSA: usb-audio: Correct a typo of NuPrime DAC-10 USB ID ALSA: hda/hdmi: fix without unlocked before return ALSA: pcm: oss: Place the plugin buffer overflow checks correctly PM: ACPI: Output correct message on target power state PM: hibernate: Freeze kernel threads in software_resume() dm verity fec: fix hash block number in verity_fec_decode dm writecache: fix data corruption when reloading the target dm multipath: use updated MPATHF_QUEUE_IO on mapping for bio-based mpath scsi: qla2xxx: set UNLOADING before waiting for session deletion scsi: qla2xxx: check UNLOADING before posting async work RDMA/mlx5: Set GRH fields in query QP on RoCE RDMA/mlx4: Initialize ib_spec on the stack RDMA/core: Prevent mixed use of FDs between shared ufiles RDMA/core: Fix race between destroy and release FD object vfio: avoid possible overflow in vfio_iommu_type1_pin_pages vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() iommu/qcom: Fix local_base status check scsi: target/iblock: fix WRITE SAME zeroing iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system ALSA: opti9xx: shut up gcc-10 range warning nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl dmaengine: dmatest: Fix iteration non-stop logic selinux: properly handle multiple messages in selinux_netlink_send() btrfs: fix partial loss of prealloc extent past i_size after fsync btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info mmc: cqhci: Avoid false "cqhci: CQE stuck on" by not open-coding timeout loop mmc: sdhci-xenon: fix annoying 1.8V regulator warning mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers mmc: sdhci-msm: Enable host capabilities pertains to R1b response mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY mmc: meson-mx-sdio: remove the broken ->card_busy() op dma-buf: Fix SET_NAME ioctl uapi drm/amd/display: Fix green screen issue after suspend NFSv4.1: fix handling of backchannel binding in BIND_CONN_TO_SESSION btrfs: fix transaction leak in btrfs_recover_relocation crypto: caam - fix the address of the last entry of S/G ALSA: line6: Fix POD HD500 audio playback i2c: amd-mp2-pci: Fix Oops in amd_mp2_pci_init() error handling dlmfs_file_write(): fix the bogosity in handling non-zero *ppos IB/rdmavt: Always return ERR_PTR from rvt_create_mmap_info() ARM: dts: imx6qdl-sr-som-ti: indicate powering off wifi is safe RDMA/siw: Fix potential siw_mem refcnt leak in siw_fastreg_mr() RDMA/cm: Fix ordering of xa_alloc_cyclic() in ib_create_cm_id() RDMA/cm: Fix an error check in cm_alloc_id_priv() i2c: iproc: generate stop event for slave writes i2c: aspeed: Avoid i2c interrupt status clear race condition. nvme: prevent double free in nvme_alloc_ns() error handling dmaengine: dmatest: Fix process hang when reading 'wait' parameter arm64: vdso: Add -fasynchronous-unwind-tables to cflags UBUNTU: upstream stable to v4.19.121, v5.4.39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881657] Re: Eoan update: upstream stable patchset 2020-06-01
** Changed in: linux (Ubuntu Eoan) 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/1881657 Title: Eoan update: upstream stable patchset 2020-06-01 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: 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 2020-06-01 Ported from the following upstream stable releases: v4.19.124, v5.4.42 from git://git.kernel.org/ net: dsa: Do not make user port errors fatal shmem: fix possible deadlocks on shmlock_user_lock net/sonic: Fix a resource leak in an error handling path in 'jazz_sonic_probe()' net: moxa: Fix a potential double 'free_irq()' drop_monitor: work around gcc-10 stringop-overflow warning virtio-blk: handle block_device_operations callbacks after hot unplug scsi: sg: add sg_remove_request in sg_write mmc: sdhci-acpi: Add SDHCI_QUIRK2_BROKEN_64_BIT_DMA for AMDI0040 net: fix a potential recursive NETDEV_FEAT_CHANGE netlabel: cope with NULL catmap net: phy: fix aneg restart in phy_ethtool_set_eee pppoe: only process PADT targeted at local interfaces Revert "ipv6: add mtu lock check in __ip6_rt_update_pmtu" tcp: fix error recovery in tcp_zerocopy_receive() virtio_net: fix lockdep warning on 32 bit hinic: fix a bug of ndo_stop net: dsa: loop: Add module soft dependency net: ipv4: really enforce backoff for redirects netprio_cgroup: Fix unlimited memory leak of v2 cgroups net: tcp: fix rx timestamp behavior for tcp_recvmsg tcp: fix SO_RCVLOWAT hangs with fat skbs riscv: fix vdso build with lld dmaengine: pch_dma.c: Avoid data race between probe and irq handler dmaengine: mmp_tdma: Reset channel error on release cpufreq: intel_pstate: Only mention the BIOS disabling turbo mode once ALSA: hda/hdmi: fix race in monitor detection during probe drm/qxl: lost qxl_bo_kunmap_atomic_page in qxl_image_init_helper() ipc/util.c: sysvipc_find_ipc() incorrectly updates position index ALSA: hda/realtek - Fix S3 pop noise on Dell Wyse gfs2: Another gfs2_walk_metadata fix pinctrl: baytrail: Enable pin configuration setting for GPIO chip pinctrl: cherryview: Add missing spinlock usage in chv_gpio_irq_handler i40iw: Fix error handling in i40iw_manage_arp_cache() mmc: core: Check request type before completing the request mmc: block: Fix request completion in the CQE timeout path NFS: Fix fscache super_cookie index_key from changing after umount nfs: fscache: use timespec64 in inode auxdata NFSv4: Fix fscache cookie aux_data to ensure change_attr is included netfilter: conntrack: avoid gcc-10 zero-length-bounds warning arm64: fix the flush_icache_range arguments in machine_kexec netfilter: nft_set_rbtree: Introduce and use nft_rbtree_interval_start() IB/mlx4: Test return value of calls to ib_get_cached_pkey hwmon: (da9052) Synchronize access with mfd pnp: Use list_for_each_entry() instead of open coding gcc-10 warnings: fix low-hanging fruit Stop the ad-hoc games with -Wno-maybe-initialized UBUNTU: [Config] updateconfigs for CC_HAS_WARN_MAYBE_UNINITIALIZED gcc-10: disable 'zero-length-bounds' warning for now gcc-10: disable 'array-bounds' warning for now gcc-10: disable 'stringop-overflow' warning for now gcc-10: disable 'restrict' warning for now gcc-10: avoid shadowing standard library 'free()' in crypto ALSA: hda/realtek - Limit int mic boost for Thinkpad T530 ALSA: rawmidi: Fix racy buffer resize under concurrent accesses ALSA: usb-audio: Add control message quirk delay for Kingston HyperX headset usb: core: hub: limit HUB_QUIRK_DISABLE_AUTOSUSPEND to USB5534B usb: host: xhci-plat: keep runtime active when removing host USB: gadget: fix illegal array access in binding with UDC usb: xhci: Fix NULL pointer dereference when enqueuing trbs from urb sg list ARM: dts: dra7: Fix bus_dma_limit for PCIe ARM: dts: imx27-phytec-phycard-s-rdk: Fix the I2C1 pinctrl entries cifs: fix leaked reference on requeued write x86: Fix early boot crash on gcc-10, third try x86/unwind/orc: Fix error handling in __unwind_start() exec: Move would_dump into flush_old_exec clk: rockchip: fix incorrect configuration of rk3228 aclk_gpu* clocks dwc3: Remove check for HWO flag in dwc3_gadget_ep_reclaim_trb_sg() usb: gadget: net2272: Fix a memory leak in an error hand
[Kernel-packages] [Bug 1879536] Re: Bionic update: upstream stable patchset 2020-05-19
** 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/1879536 Title: Bionic update: upstream stable patchset 2020-05-19 Status in linux package in Ubuntu: Confirmed 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 2020-05-19 Ported from the following upstream stable releases: v4.14.180, v4.19.122 from git://git.kernel.org/ vhost: vsock: kick send_pkt worker once device is started powerpc/pci/of: Parse unassigned resources ASoC: topology: Check return value of pcm_new_ver selftests/ipc: Fix test failure seen after initial test run ASoC: sgtl5000: Fix VAG power-on handling ASoC: rsnd: Fix HDMI channel mapping for multi-SSI mode ASoC: codecs: hdac_hdmi: Fix incorrect use of list_for_each_entry wimax/i2400m: Fix potential urb refcnt leak net: stmmac: fix enabling socfpga's ptp_ref_clock net: stmmac: Fix sub-second increment cifs: protect updating server->dstaddr with a spinlock s390/ftrace: fix potential crashes when switching tracers scripts/config: allow colons in option strings for sed lib/mpi: Fix building for powerpc with clang net: bcmgenet: suppress warnings on failed Rx SKB allocations net: systemport: suppress warnings on failed Rx SKB allocations sctp: Fix SHUTDOWN CTSN Ack in the peer restart case ALSA: hda: Match both PCI ID and SSID for driver blacklist mac80211: add ieee80211_is_any_nullfunc() cgroup, netclassid: remove double cond_resched ASoC: rsnd: Fix parent SSI start/stop in multi-SSI mode drm/amdgpu: Correctly initialize thermal controller for GPUs with Powerplay table v0 (e.g Hawaii) ASoC: rsnd: Don't treat master SSI in multi SSI setup as parent ASoC: rsnd: Fix "status check failed" spam for multi-SSI drm/amdgpu: Fix oops when pp_funcs is unset in ACPI event hexagon: clean up ioremap hexagon: define ioremap_uc drm/atomic: Take the atomic toys away from X UBUNTU: upstream stable to v4.14.180, v4.19.122 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880014] Re: Bionic update: upstream stable patchset 2020-05-21
** 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/1880014 Title: Bionic update: upstream stable patchset 2020-05-21 Status in linux package in Ubuntu: Confirmed 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 2020-05-21 Ported from the following upstream stable releases: v4.14.181, v4.19.123 v4.19.124 from git://git.kernel.org/ USB: serial: qcserial: Add DW5816e support dp83640: reverse arguments to list_add_tail fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks net: macsec: preserve ingress frame ordering net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() net: usb: qmi_wwan: add support for DW5816e sch_choke: avoid potential panic in choke_reset() sch_sfq: validate silly quantum values bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). net/mlx5: Fix forced completion access non initialized command entry net/mlx5: Fix command entry leak in Internal Error State bnxt_en: Improve AER slot reset. bnxt_en: Fix VF anti-spoof filter setup. net: stricter validation of untrusted gso packets ipv6: fix cleanup ordering for ip6_mr failure HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices HID: usbhid: Fix race between usbhid_close() and usbhid_stop() USB: uas: add quirk for LaCie 2Big Quadra USB: serial: garmin_gps: add sanity checking for data length tracing: Add a vmalloc_sync_mappings() for safe measure KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER mm/page_alloc: fix watchdog soft lockups during set_zone_contiguous() coredump: fix crash when umh is disabled batman-adv: fix batadv_nc_random_weight_tq batman-adv: Fix refcnt leak in batadv_show_throughput_override batman-adv: Fix refcnt leak in batadv_store_throughput_override batman-adv: Fix refcnt leak in batadv_v_ogm_process x86/entry/64: Fix unwind hints in kernel exit path x86/entry/64: Fix unwind hints in rewind_stack_do_exit() x86/unwind/orc: Don't skip the first frame for inactive tasks x86/unwind/orc: Prevent unwinding before ORC initialization x86/unwind/orc: Fix error path for bad ORC entry type netfilter: nat: never update the UDP checksum when it's 0 objtool: Fix stack offset tracking for indirect CFAs scripts/decodecode: fix trapping instruction formatting net: stmmac: Use mutex instead of spinlock shmem: fix possible deadlocks on shmlock_user_lock net/sonic: Fix a resource leak in an error handling path in 'jazz_sonic_probe()' net: moxa: Fix a potential double 'free_irq()' drop_monitor: work around gcc-10 stringop-overflow warning virtio-blk: handle block_device_operations callbacks after hot unplug scsi: sg: add sg_remove_request in sg_write dmaengine: pch_dma.c: Avoid data race between probe and irq handler dmaengine: mmp_tdma: Reset channel error on release cpufreq: intel_pstate: Only mention the BIOS disabling turbo mode once ALSA: hda/hdmi: fix race in monitor detection during probe drm/qxl: lost qxl_bo_kunmap_atomic_page in qxl_image_init_helper() ipc/util.c: sysvipc_find_ipc() incorrectly updates position index ALSA: hda/realtek - Fix S3 pop noise on Dell Wyse x86/entry/64: Fix unwind hints in register clearing code ipmi: Fix NULL pointer dereference in ssif_probe pinctrl: baytrail: Enable pin configuration setting for GPIO chip pinctrl: cherryview: Add missing spinlock usage in chv_gpio_irq_handler i40iw: Fix error handling in i40iw_manage_arp_cache() netfilter: conntrack: avoid gcc-10 zero-length-bounds warning IB/mlx4: Test return value of calls to ib_get_cached_pkey hwmon: (da9052) Synchronize access with mfd pnp: Use list_for_each_entry() instead of open coding gcc-10 warnings: fix low-hanging fruit kbuild: compute false-positive -Wmaybe-uninitialized cases in Kconfig Stop the ad-hoc games with -Wno-maybe-initialized gcc-10: disable 'zero-length-bounds' warning for now gcc-10: disable 'array-bounds' warning for now gcc-10: disable 'stringop-overflow' warning for now gcc-10: disable 'restrict' warning for now gcc-10: avoid shadowing standard library 'free()' in crypto x86/asm: Add instruction suffixes to bitops net: phy: micrel: Use strlcpy()
[Kernel-packages] [Bug 1881801] Re: Bionic update: upstream stable patchset 2020-06-02
** 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/1881801 Title: Bionic update: upstream stable patchset 2020-06-02 Status in linux package in Ubuntu: Confirmed 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 2020-06-02 Ported from the following upstream stable releases: v4.14.182, v4.19.125 from git://git.kernel.org/ i2c: dev: Fix the race between the release of i2c_dev and cdev ima: Set file->f_mode instead of file->f_flags in ima_calc_file_hash() evm: Check also if *tfm is an error pointer in init_desc() ima: Fix return value of ima_write_policy() fix multiplication overflow in copy_fdtable() iommu/amd: Fix over-read of ACPI UID from IVRS table i2c: mux: demux-pinctrl: Fix an error handling path in 'i2c_demux_pinctrl_probe()' ubi: Fix seq_file usage in detailed_erase_block_info debugfs file gcc-common.h: Update for GCC 10 HID: multitouch: add eGalaxTouch P80H84 support scsi: qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV configfs: fix config_item refcnt leak in configfs_rmdir() vhost/vsock: fix packet delivery order to monitoring devices component: Silence bind error on -EPROBE_DEFER scsi: ibmvscsi: Fix WARN_ON during event pool release x86/apic: Move TSC deadline timer debug printk gtp: set NLM_F_MULTI flag in gtp_genl_dump_pdp() ceph: fix double unlock in handle_cap_export() USB: core: Fix misleading driver bug report platform/x86: asus-nb-wmi: Do not load on Asus T100TA and T200TA ARM: futex: Address build warning padata: Replace delayed timer with immediate workqueue in padata_reorder padata: initialize pd->cpu with effective cpumask padata: purge get_cpu and reorder_via_wq from padata_do_serial arm64: fix the flush_icache_range arguments in machine_kexec ALSA: iec1712: Initialize STDSP24 properly when using the model=staudio option ALSA: pcm: fix incorrect hw_base increase apparmor: Fix aa_label refcnt leak in policy_update dmaengine: tegra210-adma: Fix an error handling path in 'tegra_adma_probe()' powerpc: restore alphabetic order in Kconfig powerpc: Remove STRICT_KERNEL_RWX incompatibility with RELOCATABLE powerpc/64s: Disable STRICT_KERNEL_RWX x86/uaccess, ubsan: Fix UBSAN vs. SMAP ubsan: build ubsan.c more conservatively libnvdimm/btt: Remove unnecessary code in btt_freelist_init libnvdimm/btt: Fix LBA masking during 'free list' population media: fdp1: Fix R-Car M3-N naming in debug message cxgb4: free mac_hlist properly cxgb4/cxgb4vf: Fix mac_hlist initialization and free Revert "gfs2: Don't demote a glock until its revokes are written" staging: iio: ad2s1210: Fix SPI reading staging: greybus: Fix uninitialized scalar variable iio: sca3000: Remove an erroneous 'get_device()' iio: dac: vf610: Fix an error handling path in 'vf610_dac_probe()' mei: release me_cl object reference rapidio: fix an error in get_user_pages_fast() error handling rxrpc: Fix a memory leak in rxkad_verify_response() x86/unwind/orc: Fix unwind_get_return_address_ptr() for inactive tasks iio: adc: stm32-adc: Use dma_request_chan() instead dma_request_slave_channel() iio: adc: stm32-adc: fix device used to request dma riscv: set max_pfn to the PFN of the last page ubifs: remove broken lazytime support HID: alps: Add AUI1657 device ID HID: alps: ALPS_1657 is too specific; use U1_UNICORN_LEGACY instead aquantia: Fix the media type of AQC100 ethernet controller in the driver HID: i2c-hid: reset Synaptics SYNA2393 on resume HID: quirks: Add HID_QUIRK_NO_INIT_REPORTS quirk for Dell K12A keyboard-dock stmmac: fix pointer check after utilization in stmmac_interrupt ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Xtreme ALSA: hda/realtek - Add more fixup entries for Clevo machines drm/etnaviv: fix perfmon domain interation nfit: Add Hyper-V NVDIMM DSM command set to white list thunderbolt: Drop duplicated get_switch_at_route() net: bcmgenet: code movement net: bcmgenet: abort suspend on error misc: rtsx: Add short delay after exit from ASPM UBUNTU: upstream stable to v4.14.182, v4.19.125 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881801/+subscriptions --
[Kernel-packages] [Bug 1882195] 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 1882195 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue Status in linux package in Ubuntu: Incomplete Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882194] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882194 Title: Latest Kernel WiFi Bug Status in linux package in Ubuntu: Confirmed Bug description: Hello. I previously tried to manually update the kernel via Terminal and ran into a series of errors from the apt which refused to fully install the kernet update. After several unsuccessful attempt through various other Terminal means, the update seemed to be accepted; but after rebooting my machine; the Intel WiFi drivers collapsed and I no longer could connect to the internet. After reinstalling previously saved Intel drivers from my Trash bin, I managed to get the Bluetooth to work, and then I used the UBS tethering feature of my startphone to connect this machine to the Internet, which till this moment; is my only method of going online. I consulted with a professioanl web-developer from Europe, whom confirmed this bug and suggested I report it; which I am now doing. Thanks to the kernel developers for all your hard work. You're such appreciated! ;-) PS: Here's additional info --- frederick@frederickpina:~$ cat/proc/version_signature>version.log bash: cat/proc/version_signature: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frederick 1983 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 5 02:13:54 2020 InstallationDate: Installed on 2020-01-30 (126 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. usb0 no wireless extensions. MachineType: HP HP Spectre x360 Convertible ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=3ad1fd87-8287-4943-af05-e0fcb04a210d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago) dmi.bios.date: 05/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8174 dmi.board.vendor: HP dmi.board.version: 38.41 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.21:bd05/16/2019:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn8174:rvr38.41:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.product.sku: T6T09UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882195] [NEW] Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue
Public bug reported: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue Status in linux package in Ubuntu: Incomplete Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880032] Re: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1880032 Title: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: Fix Committed Bug description: Microsoft would like to request commits to enable VM hibernation in the Azure 5.4 kernels for 18.04 and 20.04. Some of the commits needed to enable VM hibernation were included in mainline 5.4 and older. However, 24 commits were added in 5.5 and later, which are required in the 5.4 kernel. The list of commits requested are: 38dce4195f0d x86/hyperv: Properly suspend/resume reenlightenment notifications 2351f8d295ed PM: hibernate: Freeze kernel threads in software_resume() 421f090c819d x86/hyperv: Suspend/resume the VP assist page for hibernation 1a06d017fb3f Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM 3704a6a44579 PM: hibernate: Propagate the return value of hibernation_restore() 54e19d34011f hv_utils: Add the support of hibernation ffd1d4a49336 hv_utils: Support host-initiated hibernation request 3e9c72056ed5 hv_utils: Support host-initiated restart request 9fc3c01a1fae6 Tools: hv: Reopen the devices if read() or write() returns 05bd330a7fd8 x86/hyperv: Suspend/resume the hypercall page for hibernation 382a46221757 video: hyperv_fb: Fix hibernation for the deferred IO feature e2379b30324c Input: hyperv-keyboard: Add the support of hibernation ac82fc8327088 PCI: hv: Add hibernation support a8e37506e79a PCI: hv: Reorganize the code in preparation of hibernation 1349401ff1aa4 clocksource/drivers/hyper-v: Suspend/resume Hyper-V clocksource for hibernation af13f9ed6f9a HID: hyperv: Add the support of hibernation 25bd2b2f1f053 hv_balloon: Add the support of hibernation b96f86534fa31 x86/hyperv: Implement hv_is_hibernation_supported() 4df4cb9e99f83 x86/hyperv: Initialize clockevents earlier in CPU onlining 0efeea5fb1535 hv_netvsc: Add the support of hibernation 2194c2eb6717f hv_sock: Add the support of hibernation 1ecf302021040 video: hyperv_fb: Add the support of hibernation 56fb105859345 scsi: storvsc: Add the support of hibernation f2c33ccacb2d4 PCI/PM: Always return devices to D0 when thawing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882194] [NEW] Latest Kernel WiFi Bug
Public bug reported: Hello. I previously tried to manually update the kernel via Terminal and ran into a series of errors from the apt which refused to fully install the kernet update. After several unsuccessful attempt through various other Terminal means, the update seemed to be accepted; but after rebooting my machine; the Intel WiFi drivers collapsed and I no longer could connect to the internet. After reinstalling previously saved Intel drivers from my Trash bin, I managed to get the Bluetooth to work, and then I used the UBS tethering feature of my startphone to connect this machine to the Internet, which till this moment; is my only method of going online. I consulted with a professioanl web-developer from Europe, whom confirmed this bug and suggested I report it; which I am now doing. Thanks to the kernel developers for all your hard work. You're such appreciated! ;-) PS: Here's additional info --- frederick@frederickpina:~$ cat/proc/version_signature>version.log bash: cat/proc/version_signature: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frederick 1983 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 5 02:13:54 2020 InstallationDate: Installed on 2020-01-30 (126 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. usb0 no wireless extensions. MachineType: HP HP Spectre x360 Convertible ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=3ad1fd87-8287-4943-af05-e0fcb04a210d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago) dmi.bios.date: 05/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8174 dmi.board.vendor: HP dmi.board.version: 38.41 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.21:bd05/16/2019:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn8174:rvr38.41:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.product.sku: T6T09UA#ABA dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882194 Title: Latest Kernel WiFi Bug Status in linux package in Ubuntu: Confirmed Bug description: Hello. I previously tried to manually update the kernel via Terminal and ran into a series of errors from the apt which refused to fully install the kernet update. After several unsuccessful attempt through various other Terminal means, the update seemed to be accepted; but after rebooting my machine; the Intel WiFi drivers collapsed and I no longer could connect to the internet. After reinstalling previously saved Intel drivers from my Trash bin, I managed to get the Bluetooth to work, and then I used the UBS tethering feature of my startphone to connect this machine to the Internet, which till this moment; is my only method of going online. I consulted with a professioanl web-developer from Europe, whom confirmed this bug and suggested I report it; which I am now doing. Thanks to the kernel developers for all your hard work. You're such appreciated! ;-) PS: Here's additional info --- frederick@frederickpina:~$ cat/proc/version_signature>version.log bash: cat/proc/version_signature: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frederick 1983 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME
[Kernel-packages] [Bug 1876165] Re: Binder and ashmem drivers are missing from AWS kernel
** Changed in: linux-aws (Ubuntu Eoan) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-aws-5.3 (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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1876165 Title: Binder and ashmem drivers are missing from AWS kernel Status in linux-aws package in Ubuntu: Invalid Status in linux-aws-5.3 package in Ubuntu: Invalid Status in linux-aws-5.3 source package in Bionic: Fix Committed Status in linux-aws source package in Eoan: Fix Committed Status in linux-aws source package in Focal: Fix Committed Bug description: For quite a while the Ubuntu kernel now ships the Ashmem and Binder drivers as part of linux-modules-extra-*. They were available on previous linux-aws kernels but seem to have dropped with the 5.3.0 based edge kernel. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493 for a similar bug report I filed in the past for the GCP kernels. Can we get both ashmem and binder enabled and added to linux-aws-edge as they are used for Anbox Cloud? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1876165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881662] Re: Add Description To Hyper-V Modules
** Changed in: linux-azure-4.15 (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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1881662
Title:
Add Description To Hyper-V Modules
Status in linux-azure package in Ubuntu:
New
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Committed
Status in linux-azure source package in Eoan:
Invalid
Status in linux-azure-4.15 source package in Eoan:
Invalid
Status in linux-azure source package in Focal:
Invalid
Status in linux-azure-4.15 source package in Focal:
Invalid
Bug description:
There are three modules where no description exists causing issues
during a customers certification test:
hid_hyperv
hyperv_keyboard
hv_vmbus
Three patches exist upstream which fix this issue. The mainline
commits are:
64caea53e07f ("HID: hyperv: Add a module description line")
674eecb3d35a ("drivers: hv: Add a module description line to the hv_vmbus
driver")
9d1c2f067e50 ("Input: hyperv-keyboard - add module description")
Can you pull these commits into all releases that are supported on
Azure?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881662/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882159] Re: 10s delay after grub, before kernel messages start
Please be specific about what you want me to modify. > try booting with "initcall_debug earlycon=efifb" GRUB_CMDLINE_LINUX_DEFAULT="initcall_debug earlycon=efifb" ? > please insert one line "debug=all" in the grub boot entry ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882159 Title: 10s delay after grub, before kernel messages start Status in linux package in Ubuntu: Incomplete Bug description: - fresh install of 20.04 X64 in a vmware vm - "quiet splash" kernel args have been removed - the kernel messages should start immediately after grub menu selection - but there's a 10s delay grub config ``` GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=menu GRUB_TIMEOUT=3 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 20:34:38 2020 InstallationDate: Installed on 2020-06-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. ens32 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=606fed4f-11b6-4349-803e-69c555177718 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881710] Re: tpm: fix TIS locality timeout problems
** Changed in: linux (Ubuntu Focal)
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/1881710
Title:
tpm: fix TIS locality timeout problems
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux-oem-osp1 package in Ubuntu:
Invalid
Status in linux-oem-osp1 source package in Bionic:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
In Progress
Bug description:
[Impact]
It has been reported that some TIS based TPMs are giving unexpected errors
when using the O_NONBLOCK path of the TPM device. The problem is that some TPMs
don't like it when you get and then relinquish a locality (as the
tpm_try_get_ops()/tpm_put_ops() pair does) without sending a command. This
currently happens all the time in the O_NONBLOCK write path. This affects
Nuvoton TPMs and was a regression caused by the patch d23d12484307 ("tpm: fix
invalid locking in NONBLOCKING mode").
PatchLink: https://patchwork.kernel.org/patch/11576453/
[Fix]
Fix this by moving the tpm_try_get_ops()
further down the code to after the O_NONBLOCK determination is made.
This is safe because the priv->buffer_mutex still protects the priv
state being modified.
[Regression Risk]
Low. This patch only for fix the patch d23d12484307 ("tpm: fix invalid
locking in NONBLOCKING mode").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881710/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881631] Re: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII
** Changed in: linux-raspi2 (Ubuntu Eoan) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881631 Title: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Committed Bug description: The CONFIG_NLS_ASCII was already set to Y in the raspi-5.4 kernel and bionic kernel by Juerg, now do the same change in the raspi2-5.3 kernel. [Impact] users reported that the raspi ubuntu core has some problem to mount filessytem, need to enable the NLS_ASCII and make it built-in. [Fix] change it from m to y just as the focal and bionic raspi kernel. [Test Case] building the kernel and boot the kernel, it could mount the filesystem successfully. [Regression Risk] Low, just changing a kconfig to y from m. Remounting log mounts in Ubuntu core are failing on arm64 builds due to missing CONFIG_NLS_ASCII in the arm64 kernel build options. This option is enabled on the other kernel builds but somehow was overlooked on arm64 appears to affect our ability to access logs via journalctl with data from prior to restart because certain mounts are failing. Other Raspberry Pi kernel builds, such as the armhf build, have the option enabled and so do not encounter the mount error. The kernel option that needs to be turned on to resolve this is CONFIG_NLS_ASCII. It needs to be set to either 'm' or 'y'. Most of the other chips have it set to 'y', keeping it built-in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879704] Re: [UBUNTU 20.04] s390x/pci: fix linking between PF and VF for multifunction devices
** 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/1879704
Title:
[UBUNTU 20.04] s390x/pci: fix linking between PF and VF for
multifunction devices
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* It's currently not possible on s390x to verify the relationships
between PFs and VFs of network interfaces (neither natively nor in
libvirt).
* So s390x currently behaves differently here compared to other
architectures, but shouldn't, since this is needed for proper
management.
* The creation of not only the sysfs, but also the in-kernel link
(struct pci_dev->physfn), solves this and on top allows the use of a
common code path for disabling/shutdown of PFs.
* This code path is right now fenced off by the struct
pci_dev->no_vf_scan flag of which s390x is currently the only user.
* This allows to gracefully and orderly shutdown VFs associated with a
PF as triggered by '/sys/bus/pci/devices//sriov_numvfs'
* Previously this could leave the card in an unresponsive error state.
[Fix]
* a1ceea67f2e5b73cebd456e7fb463b3052bc6344 a1ceea67f2e5 "PCI/IOV:
Introduce pci_iov_sysfs_link() function"
* e5794cf1a270d813a5b9373a6876487d4d154195 e5794cf1a270 "s390/pci:
create links between PFs and VFs"
[Test Case]
* Setup an s390x LPAR with at least one SR-IOV card and assign PF and
VFs to that system.
* Determine if a device is a virtual function: for other architectures
this is currently available in the file 'physfn' which is a link to
the parent PF's device.
* Determine virtual functions of a physical function: for other
architectures this is currently available as 'virtfn{index}' links
under the PF device's directory.
* Determine the physical function of a virtual function: on x86 this
is currently available in the file 'physfn' which is a link to the
parent PF.
* This verification needs to be done by IBM on a system with SR-IOV
(PCI-based) hardware.
[Regression Potential]
* There is a certain regression risk with having code changes in the PCI/IOV
space,
even is they are limited, especially is the patches touche common code.
* The changes in pci.h are very minimal, and the iov.c changes are
traceable, too. All other modifications are s390x specific.
* Nevertheless, it could be that PCI hardware get harmed, here
especially (SR-)IOV hardware.
* The patches got cross-company verified (IBM and Google).
* They were brought upstream and are currently tagged with 20200521,
and are planned to be included in 5.8.
* A patched kernel was created based on a LP PPA and successfully
tested by IBM.
[Other]
* Since the fix/patch is planned to be included in kernel v5.8, it
will later automatically land in groovy.
* But because groovy is not there yet (5.8 is not yet out), this SRU
got requested for focal and groovy.
* This SRU depends on the SRU from LP 1874056, and this has already two ACKs.
So LP 1874056 needs to be applied before this one!
__
As with other architectures, we must be able on s390x to verify the
following relationships between PFs and VFs for proper management
(including by libvirt) of network interfaces:
1. Determine if a device is a virtual function: for other architectures this
is currently available in the file `physfn` which is a link to the parent PF's
device.
2. Determine virtual functions of a physical function: for other
architectures this is currently available as `virtfn{index}` links under the PF
device's directory.
3. Determine the physical function of a virtual function: on x86 this is
currently available in the file `physfn` which is a link to the parent PF
More details for the already existing parameters mentioned above can
be found here: https://www.kernel.org/doc/Documentation/ABI/testing
/sysfs-bus-pci
Moreover creating not just the sysfs but also the in-kernel link
(struct pci_dev->physfn) also allows us to use the common code path
for disabling/shutdown of PFs.
This code path is currently fenced off by the
struct pci_dev->no_vf_scan flag of which s390 is currently the only user.
This in turn allows for a graceful and orderly shutdown of VFs
associated with a VF as triggered by:
echo 0 > /sys/bus/pci/devices//sriov_numvfs
Previously this could leave the card in an unresponsive error state.
The patches for this have been discussed and Acked-by the
responsible upstream maintainer here:
[RFC 0/2] Enable PF-VF linking with pdev->no_vf_scan (s390)
https://lore.kernel.org/linux-pci/202005061541
[Kernel-packages] [Bug 1879704] Re: [UBUNTU 20.04] s390x/pci: fix linking between PF and VF for multifunction devices
** Changed in: linux (Ubuntu Focal)
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/1879704
Title:
[UBUNTU 20.04] s390x/pci: fix linking between PF and VF for
multifunction devices
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* It's currently not possible on s390x to verify the relationships
between PFs and VFs of network interfaces (neither natively nor in
libvirt).
* So s390x currently behaves differently here compared to other
architectures, but shouldn't, since this is needed for proper
management.
* The creation of not only the sysfs, but also the in-kernel link
(struct pci_dev->physfn), solves this and on top allows the use of a
common code path for disabling/shutdown of PFs.
* This code path is right now fenced off by the struct
pci_dev->no_vf_scan flag of which s390x is currently the only user.
* This allows to gracefully and orderly shutdown VFs associated with a
PF as triggered by '/sys/bus/pci/devices//sriov_numvfs'
* Previously this could leave the card in an unresponsive error state.
[Fix]
* a1ceea67f2e5b73cebd456e7fb463b3052bc6344 a1ceea67f2e5 "PCI/IOV:
Introduce pci_iov_sysfs_link() function"
* e5794cf1a270d813a5b9373a6876487d4d154195 e5794cf1a270 "s390/pci:
create links between PFs and VFs"
[Test Case]
* Setup an s390x LPAR with at least one SR-IOV card and assign PF and
VFs to that system.
* Determine if a device is a virtual function: for other architectures
this is currently available in the file 'physfn' which is a link to
the parent PF's device.
* Determine virtual functions of a physical function: for other
architectures this is currently available as 'virtfn{index}' links
under the PF device's directory.
* Determine the physical function of a virtual function: on x86 this
is currently available in the file 'physfn' which is a link to the
parent PF.
* This verification needs to be done by IBM on a system with SR-IOV
(PCI-based) hardware.
[Regression Potential]
* There is a certain regression risk with having code changes in the PCI/IOV
space,
even is they are limited, especially is the patches touche common code.
* The changes in pci.h are very minimal, and the iov.c changes are
traceable, too. All other modifications are s390x specific.
* Nevertheless, it could be that PCI hardware get harmed, here
especially (SR-)IOV hardware.
* The patches got cross-company verified (IBM and Google).
* They were brought upstream and are currently tagged with 20200521,
and are planned to be included in 5.8.
* A patched kernel was created based on a LP PPA and successfully
tested by IBM.
[Other]
* Since the fix/patch is planned to be included in kernel v5.8, it
will later automatically land in groovy.
* But because groovy is not there yet (5.8 is not yet out), this SRU
got requested for focal and groovy.
* This SRU depends on the SRU from LP 1874056, and this has already two ACKs.
So LP 1874056 needs to be applied before this one!
__
As with other architectures, we must be able on s390x to verify the
following relationships between PFs and VFs for proper management
(including by libvirt) of network interfaces:
1. Determine if a device is a virtual function: for other architectures this
is currently available in the file `physfn` which is a link to the parent PF's
device.
2. Determine virtual functions of a physical function: for other
architectures this is currently available as `virtfn{index}` links under the PF
device's directory.
3. Determine the physical function of a virtual function: on x86 this is
currently available in the file `physfn` which is a link to the parent PF
More details for the already existing parameters mentioned above can
be found here: https://www.kernel.org/doc/Documentation/ABI/testing
/sysfs-bus-pci
Moreover creating not just the sysfs but also the in-kernel link
(struct pci_dev->physfn) also allows us to use the common code path
for disabling/shutdown of PFs.
This code path is currently fenced off by the
struct pci_dev->no_vf_scan flag of which s390 is currently the only user.
This in turn allows for a graceful and orderly shutdown of VFs
associated with a VF as triggered by:
echo 0 > /sys/bus/pci/devices//sriov_numvfs
Previously this could leave the card in an unresponsive error state.
The patches for this have been discussed and Acked-by the
responsible upstream maintainer here:
[RFC 0/2] Enable PF-VF linking with pdev->no_vf_scan (s390)
https://lore.kernel.org/linux-pci/20200506
[Kernel-packages] [Bug 1865988] Re: Performing function level reset of AMD onboard USB and audio devices causes system lockup
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) 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/1865988 Title: Performing function level reset of AMD onboard USB and audio devices causes system lockup Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Eoan: Fix Committed Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: Invalid Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux-oem-osp1 source package in Groovy: Invalid Bug description: [SRU Justifcation] [Impact] Devices affected: * [1022:148c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller * [1022:1487] Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller Despite advertising FLReset device capabilities, performing a function level reset of either of these devices causes the system to lock up. This is of particular issue where these devices appear in their own IOMMU groups and are well suited to VFIO passthrough. Issue was introduced in AMD's "AGESA Combo-AM4 1.0.0.4 Patch B" microcode update, and affects dozens of motherboard models across various vendors. Additional discussion of this issue: https://www.reddit.com/r/VFIO/comments/eba5mh/workaround_patch_for_passing_through_usb_and/ [Fix] Two commits currently landed in linux-pci pci/virutualization: * 0d14f06cd665 PCI: Avoid FLR for AMD Matisse HD Audio & USB 3.0 * 5727043c73fd PCI: Avoid FLR for AMD Starship USB 3.0 [Test Case] Peform the test on an impacted system: * B350, B450, X370, X470, X570 motherboards (practically anything with an AM4 socket); * Ryzen 3000-series CPU (2000-series possibly also affected); * BIOS/UEFI firmware that includes "AGESA Combo-AM4 1.0.0.4 Patch B" (check vendor release notes) In the above case where ':10:00.3' is the USB controller '1022:149c', issue a reset command: $ echo 1 | sudo tee /sys/bus/pci/devices/\:10\:00.3/reset Impacted systems will not return successfully and become unstable, requiring a reboot. `/var/logs/syslog` will show something resembling the following: xhci_hcd :10:00.3: not ready 1023ms after FLR; waiting xhci_hcd :10:00.3: not ready 2047ms after FLR; waiting xhci_hcd :10:00.3: not ready 4095ms after FLR; waiting xhci_hcd :10:00.3: not ready 8191ms after FLR; waiting xhci_hcd :10:00.3: not ready 16383ms after FLR; waiting xhci_hcd :10:00.3: not ready 32767ms after FLR; waiting xhci_hcd :10:00.3: not ready 65535ms after FLR; giving up clocksource: timekeeping watchdog on CPU14: Marking clocksource 'tsc' as unstable because the skew is too large: clocksource: 'hpet' wd_now: f63fcfe wd_last: d468894 mask: clocksource: 'tsc' cs_now: 60e67e17758 cs_last: 60d2a81ce24 mask: tsc: Marking TSC unstable due to clocksource watchdog TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. sched_clock: Marking unstable (1817664630139, 314261908)<-(1817981099530, -2209419) [Regression Risk] Low. These two patches affect only systems with a device needs fix. == Original Bug Description == $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 [Impact] Devices affected: * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller * [1022:1487] Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller Despite advertising FLReset device capabilities, performing a function level reset of either of these devices causes the system to lock up. This is of particular issue where these devices appear in their own IOMMU groups and are well suited to VFIO passthrough. Issue was introduced in AMD's "AGESA Combo-AM4 1.0.0.4 Patch B" microcode update, and affects dozens of
[Kernel-packages] [Bug 1881576] Re: seccomp_benchmark times out on eoan
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) 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/1881576 Title: seccomp_benchmark times out on eoan Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] seccomp selftests will timeout, causing the test to be detected as failure. [Fix] Set timeout to 90s. [Test case] Run sudo make run_tests under tools/testing/selftests/seccomp/. [Regression potential] Minimal, the test could still timeout, but by reading the code, it should take around 42s to 50s to execute in the worst cases, so 90s seem safe enough. == As it tries to calibrate how many samples will take more than 5 seconds to execute, it may end up picking up a number of samples that take 10 (but up to 12) seconds. As the calibration will take double that time, it takes around 20 seconds. Then, it executes the whole thing again, and then once more, with some added overhead. So, the thing might take more than 40 seconds, which is too close to the 45s timeout. So, it times out once in a while depending on the system. Using a timeout of 90 seconds should be safe enough for this test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877955] Re: Fix for secure boot rules in IMA arch policy on powerpc
** 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/1877955
Title:
Fix for secure boot rules in IMA arch policy on powerpc
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* Currently the kernel module appended signature is verified twice
(finit_module) - once by the module_sig_check() and again by IMA.
* To prevent this the powerpc secure boot rules define an IMA
architecture specific policy rule only if CONFIG_MODULE_SIG_FORCE is
not enabled.
* But this doesn't take the ability into account of enabling
"sig_enforce" at the boot command line (module.sig_enforce=1).
* Including the IMA module appraise rule results in failing the
finit_module syscall, unless the module signing public key is loaded
onto the IMA keyring.
* This patch fixes secure boot policy rules to be based on
CONFIG_MODULE_SIG instead.
[Fix]
* fa4f3f56ccd28ac031ab275e673ed4098855fed4 fa4f3f56ccd2 "powerpc/ima:
Fix secure boot rules in ima arch policy"
[Test Case]
* Perform a secure boot on a powerpc system with
'module.sig_enforce=1' set at the boot command.
* If the IMA module appraise rule is included, the finit_module
syscall will fail (unless the module signing public key got loaded
onto the IMA keyring) without having the patch in place.
* The verification needs to be done by the IBM Power team.
[Regression Potential]
* There is (always) a certain regression risk with having code
changes, especially in the secure boot area.
* But this patch is limited to the powerpc platform and will not
affect any other architecture.
* It got discussed at
https://lore.kernel.org/r/1588342612-14532-1-git-send-email-na...@linux.ibm.com
before it became finally upstream accepted with kernel 5.7-rc7.
* The secure boot code itself wasn't really touched, rather than it's basis
for execution.
The IMA policy rule for module appraisal is now added only if
'CONFIG_MODULE_SIG' is not enabled (instead of CONFIG_MODULE_SIG_FORCE).
Hence the change is very limited and straightforward.
[Other]
* Since the patch got upstream with 5.7-rc7, it is already in groovy, hence
this SRU is for focal only.
__
== Comment: #0 - Michael Ranweiler - 2020-04-22
14:44:31 ==
+++ This bug was initially created as a clone of Bug #184073 +++
This bug is a follow on to LP 1866909 to address a missing piece -
only half the following patch was included in 5.4.0-24.28.
The upstream patch has an additional fix but it?s not critical for GA.
It can get included as part of bug fixes. It also affects only power.
The patch("powerpc/ima: fix secure boot rules in ima arch policy") is
posted to linux-integrity and linuxppc-dev mailing list
(https://lore.kernel.org/linux-integrity/1586549618-6106-1-git-send-
email-na...@linux.ibm.com/T/#u)
If there are any issues identified during further testing, they will
get opened as separate issue to be addressed later.
Thanks & Regards,
- Nayna
== Comment: #4 - Michael Ranweiler - 2020-05-11
02:23:35 ==
Updated posting:
https://lore.kernel.org/linux-integrity/1588342612-14532-1-git-send-
email-na...@linux.ibm.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1877955/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880834] Re: qeth: utilize virtual MAC for Layer2 OSD devices
** 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/1880834 Title: qeth: utilize virtual MAC for Layer2 OSD devices Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * A qeth device on a DPM-managed (HMC) IBM Z machine does not obtain its MAC address for layer2 OSD interfaces from the OSA Network Adapter, instead it uses a random MAC address. * This can cause connectivity issues in environments where reliable and pre-determined MAC addresses are required, ie. when doing network configuration based on DHCP. [Fix] * Backport 1: https://launchpadlibrarian.net/481647649/0001-s390-qeth- improve-fallback-to-random-MAC-address.patch * Backport 2: https://launchpadlibrarian.net/481647657/0002-s390-qeth- utilize-virtual-MAC-for-Layer2-OSD-devices.patch [Test Case] * Bring up a qeth L2 OSD interface in DPM-managed (HMC) LPAR * Inspect the interface's MAC address. It should be the same as displayed in the HMC DPM panels. * Due to the fact that a system is needed where the HMC is in DPM moce (rather than in classic mode) this needs to be tested by IBM. [Regression Potential] * There is a certain risk for a regression, since OSA devices are the standard netweork devices on s390x. * But static network configurations are still more popular for the usually long running workload on s390x and not dynamic assignments. * On the other hand qeth devices are s390x only, so this will at least not affect common code or code for other architectures. * The modifications are limited to drivers/s390/net/qeth_*. * The patches are upstream since quite a while, which speaks for their stability. [Other Info] * The upstream patch 21b1702af12e "s390/qeth: improve fallback to random MAC address" got upstream accepted with 4.18, hence is already in all Ubuntu release that are newer than bionic * And the upstream patch b144b99fff69 "s390/qeth: utilize virtual MAC for Layer2 OSD devices" got upstream accepted with 5.0, hence is also already in all Ubuntu release that are newer than bionic. __ ---Problem Description--- qeth on a DPM-managed IBM Z machine does not obtain its MAC Address for L2 OSD interfaces from the OSA Network Adapter. Instead it uses a random MAC Address. This causes connectivity issues in setups where a reliable & pre- determined MAC Address is required - ie. when doing network configuration via DHCP. ---uname output--- Ubuntu 18.04 / vmlinuz-4.15.0-101-generic Machine Type = IBM z14 GA2 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- - Bring up a qeth L2 OSD interface in DPM-managed LPAR. - Inspect the interface's MAC Address. It should be the same as displayed in the DPM Panels. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Attach sysctl -a output output to the bug. Backport of "s390/qeth: improve fallback to random MAC address" Backport of "s390/qeth: utilize virtual MAC for Layer2 OSD devices" This ticket is for 18.04 only. Already available with 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1880834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881046] Re: ASoC/amd: add audio driver for amd renoir
** Changed in: linux (Ubuntu Focal) 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/1881046 Title: ASoC/amd: add audio driver for amd renoir Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: Incomplete Bug description: This patchset is for mainline kernel-5.8, after backporting to 5.6, there is no need to change anything, but after backporting to 5.4 kernel, because of API differences, need to do some change to adapt to 5.4 kernel's API. So there is one more patch for focal than for oem-5.6. [Impact] We have a couple of LENOVO machines which has amd renoir audio on them, our kernel doesn't have the driver for it yet. [Fix] amd just upstreamed the driver, it is for kernel-5.8, we backport them to ubunt kernel. [Test Case] boot the kernel with those patches, we could see a sound card named "acp" and the dmic on it could record sound via arecord. [Regression Risk] Low, just adding a new driver, no change to existing drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874055] Re: [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available
** 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/1874055 Title: [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: == [Impact] * Code that is using s390_pci_mmio_write/read system calls on a z15 (that comes with enhanced PCI load/store instructions), fails with "Unable to handle kernel pointer dereference in virtual kernel address space". * This issue happens if enablement for z15 PCI enhancements is in place and where customers run workloads which access PCI adapters from user space, like RoCE/RDMA. * To solve this, the system call implementation needs to be improved to execute the enhanced PCI load/store instructions on behalf of the user space application, making use of the mappings into its virtual address space. [Fix] * f058599e22d59e594e5aae1dc10560568d8f4a8b f058599e22d5 "s390/pci: Fix s390_mmio_read/write with MIO" [Test Case] * Setting up a z15 with at least one PCI card (like RoCE) using an operating system that includes support and enablement for z15 (line 20.04). * Install the rdma tools: sudo apt install ibverbs-providers ibverbs- utils * Verify you have some RDMA devices (requires ConnectX adapter) $ ibv_devices device node GUID -- mlx5_0 98039b0300c682b4 * Verify MIO instructions are enabled for the device $ cat /sys/bus/pci/devices/\:00\:00.0/mio_enabled 1 * Try to run an RDMA application from user space, e.g. ibv_rc_pingpong server side: ibv_rc_pingpong -d mlx5_0 -g 0 & client side: ibv_rc_pingpong -d mlx5_0 -g 0 localhost * Verify whether the kernel crashes or not. * Verification needs to be done by IBM on z15 hardware. [Regression Potential] * There is some regression potential with having code changes in the zPCI sub-system (zPCI is limited to s390x) * It could be that zPCI hardware get harmed, but zPCI hardware is not as wide-spread on s390x than ccw hardware components. * Only z15 hardware is affected - no other s390x hardware that is supported by Ubuntu. * However, the zPCI system is s390x only and the patch was accepted upstream with v5.7-rc7 and Linus commented: "And none of the fixes look like there's anything particularly scary going on. Most of it is very small, and the slightly larger patches aren't huge either and are well-contained (the two slightly larger patches are to s390 and rxrpc - and even those patches aren't really all _that_ big)" __ One of the PCI enhancements on Z15 are the enhanced PCI load/store instructions which can be executed directly from user space code. When these instructions are available and preexisting user space code still uses the old s390_pci_mmio_write/read system calls, the system calls fail with an "Unable to handle kernel pointer dereference in virtual kernel address space" in the kernel. This issue affects distributions which have the enablement for Z15 PCI enhancements and where customers run workloads which accesses PCI adapters from user space, e.g. RDMA applications. To solve this, the system call implementation needs to be enhanced to provide to execute enhanced PCI load/store instructions on behalf of the user space application making use of the mappings into its virtual address space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882159] Re: 10s delay after grub, before kernel messages start
The second way: please insert one line "debug=all" in the grub boot entry before "linux ". This would turn on grub debug messages. So if it's still printing, it's not under linux kernel's control yet. Please clarify the origin of the delay first. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882159 Title: 10s delay after grub, before kernel messages start Status in linux package in Ubuntu: Incomplete Bug description: - fresh install of 20.04 X64 in a vmware vm - "quiet splash" kernel args have been removed - the kernel messages should start immediately after grub menu selection - but there's a 10s delay grub config ``` GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=menu GRUB_TIMEOUT=3 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 20:34:38 2020 InstallationDate: Installed on 2020-06-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. ens32 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=606fed4f-11b6-4349-803e-69c555177718 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882159] Re: 10s delay after grub, before kernel messages start
Please try booting with "initcall_debug earlycon=efifb" and see if kernel starts printing without that delay. Note this would usually slow done the boot process quite a lot, and I'm not sure if it actually works on a VMware virtual machine. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1882159 Title: 10s delay after grub, before kernel messages start Status in linux package in Ubuntu: Incomplete Bug description: - fresh install of 20.04 X64 in a vmware vm - "quiet splash" kernel args have been removed - the kernel messages should start immediately after grub menu selection - but there's a 10s delay grub config ``` GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=menu GRUB_TIMEOUT=3 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 20:34:38 2020 InstallationDate: Installed on 2020-06-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. ens32 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=606fed4f-11b6-4349-803e-69c555177718 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876699] Re: add 16-bit width registers support for EEPROM at24 device
** 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/1876699 Title: add 16-bit width registers support for EEPROM at24 device Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: SRU For Bionic [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. The i2c/smbus currently only support to access data with 8-bit width of address. In some larger device, such as larger EEPROM, it requires to access the address large than 0xff, so it needs to extend address space to 16-bit width. [Fix] This commit is derivated from below commit, and then modified and provided by customer https://patchwork.ozlabs.org/patch/545292/ Unfortunately, this commit doesn't get into mainline in the end, so I migrate the commit to latest kernel and finally get it merged. https://lkml.org/lkml/2020/4/24/635 [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch only changes the behavior of the device which has AT24_FLAG_ADDR16 flag and change the page_size to 64 if the device name is 24c256. = SRU For Focal [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. The i2c/smbus currently only support to access data with 8-bit width of address. In some larger device, such as larger EEPROM, it requires to access the address large than 0xff, so it needs to extend address space to 16-bit width. [Fix] Clear cherry pick from linux-next 82f25bd73c0b regmap-i2c: add 16-bit width registers support [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch provides new access functions for 16-bit registers, shouldn't affect any other devices which are already working well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874055] Re: [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available
** Changed in: linux (Ubuntu Focal) 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/1874055 Title: [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: == [Impact] * Code that is using s390_pci_mmio_write/read system calls on a z15 (that comes with enhanced PCI load/store instructions), fails with "Unable to handle kernel pointer dereference in virtual kernel address space". * This issue happens if enablement for z15 PCI enhancements is in place and where customers run workloads which access PCI adapters from user space, like RoCE/RDMA. * To solve this, the system call implementation needs to be improved to execute the enhanced PCI load/store instructions on behalf of the user space application, making use of the mappings into its virtual address space. [Fix] * f058599e22d59e594e5aae1dc10560568d8f4a8b f058599e22d5 "s390/pci: Fix s390_mmio_read/write with MIO" [Test Case] * Setting up a z15 with at least one PCI card (like RoCE) using an operating system that includes support and enablement for z15 (line 20.04). * Install the rdma tools: sudo apt install ibverbs-providers ibverbs- utils * Verify you have some RDMA devices (requires ConnectX adapter) $ ibv_devices device node GUID -- mlx5_0 98039b0300c682b4 * Verify MIO instructions are enabled for the device $ cat /sys/bus/pci/devices/\:00\:00.0/mio_enabled 1 * Try to run an RDMA application from user space, e.g. ibv_rc_pingpong server side: ibv_rc_pingpong -d mlx5_0 -g 0 & client side: ibv_rc_pingpong -d mlx5_0 -g 0 localhost * Verify whether the kernel crashes or not. * Verification needs to be done by IBM on z15 hardware. [Regression Potential] * There is some regression potential with having code changes in the zPCI sub-system (zPCI is limited to s390x) * It could be that zPCI hardware get harmed, but zPCI hardware is not as wide-spread on s390x than ccw hardware components. * Only z15 hardware is affected - no other s390x hardware that is supported by Ubuntu. * However, the zPCI system is s390x only and the patch was accepted upstream with v5.7-rc7 and Linus commented: "And none of the fixes look like there's anything particularly scary going on. Most of it is very small, and the slightly larger patches aren't huge either and are well-contained (the two slightly larger patches are to s390 and rxrpc - and even those patches aren't really all _that_ big)" __ One of the PCI enhancements on Z15 are the enhanced PCI load/store instructions which can be executed directly from user space code. When these instructions are available and preexisting user space code still uses the old s390_pci_mmio_write/read system calls, the system calls fail with an "Unable to handle kernel pointer dereference in virtual kernel address space" in the kernel. This issue affects distributions which have the enablement for Z15 PCI enhancements and where customers run workloads which accesses PCI adapters from user space, e.g. RDMA applications. To solve this, the system call implementation needs to be enhanced to provide to execute enhanced PCI load/store instructions on behalf of the user space application making use of the mappings into its virtual address space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877955] Re: Fix for secure boot rules in IMA arch policy on powerpc
** Changed in: linux (Ubuntu Focal)
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/1877955
Title:
Fix for secure boot rules in IMA arch policy on powerpc
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* Currently the kernel module appended signature is verified twice
(finit_module) - once by the module_sig_check() and again by IMA.
* To prevent this the powerpc secure boot rules define an IMA
architecture specific policy rule only if CONFIG_MODULE_SIG_FORCE is
not enabled.
* But this doesn't take the ability into account of enabling
"sig_enforce" at the boot command line (module.sig_enforce=1).
* Including the IMA module appraise rule results in failing the
finit_module syscall, unless the module signing public key is loaded
onto the IMA keyring.
* This patch fixes secure boot policy rules to be based on
CONFIG_MODULE_SIG instead.
[Fix]
* fa4f3f56ccd28ac031ab275e673ed4098855fed4 fa4f3f56ccd2 "powerpc/ima:
Fix secure boot rules in ima arch policy"
[Test Case]
* Perform a secure boot on a powerpc system with
'module.sig_enforce=1' set at the boot command.
* If the IMA module appraise rule is included, the finit_module
syscall will fail (unless the module signing public key got loaded
onto the IMA keyring) without having the patch in place.
* The verification needs to be done by the IBM Power team.
[Regression Potential]
* There is (always) a certain regression risk with having code
changes, especially in the secure boot area.
* But this patch is limited to the powerpc platform and will not
affect any other architecture.
* It got discussed at
https://lore.kernel.org/r/1588342612-14532-1-git-send-email-na...@linux.ibm.com
before it became finally upstream accepted with kernel 5.7-rc7.
* The secure boot code itself wasn't really touched, rather than it's basis
for execution.
The IMA policy rule for module appraisal is now added only if
'CONFIG_MODULE_SIG' is not enabled (instead of CONFIG_MODULE_SIG_FORCE).
Hence the change is very limited and straightforward.
[Other]
* Since the patch got upstream with 5.7-rc7, it is already in groovy, hence
this SRU is for focal only.
__
== Comment: #0 - Michael Ranweiler - 2020-04-22
14:44:31 ==
+++ This bug was initially created as a clone of Bug #184073 +++
This bug is a follow on to LP 1866909 to address a missing piece -
only half the following patch was included in 5.4.0-24.28.
The upstream patch has an additional fix but it?s not critical for GA.
It can get included as part of bug fixes. It also affects only power.
The patch("powerpc/ima: fix secure boot rules in ima arch policy") is
posted to linux-integrity and linuxppc-dev mailing list
(https://lore.kernel.org/linux-integrity/1586549618-6106-1-git-send-
email-na...@linux.ibm.com/T/#u)
If there are any issues identified during further testing, they will
get opened as separate issue to be addressed later.
Thanks & Regards,
- Nayna
== Comment: #4 - Michael Ranweiler - 2020-05-11
02:23:35 ==
Updated posting:
https://lore.kernel.org/linux-integrity/1588342612-14532-1-git-send-
email-na...@linux.ibm.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1877955/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802691] Re: Slow send speed with Intel I219-V on Ubuntu 18.04.1
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) 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/1802691 Title: Slow send speed with Intel I219-V on Ubuntu 18.04.1 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] The throughput measured by iperf3 is around 70% of 1Gbps (Intel I219-LM [8086:15b7]) I219 is a rather cheap NIC and it impacts its throughput if TSO(TCP segmentation offload) is enabled. [Fix] Disable TSO on NIC and move this task back to CPU fixes this issue. The impact of CPU loading is little to none. On target machine with Xeon(R) CPU E3-1505L v6 @ 2.20GHz(4c8t), the CPU usage of iperf3 increases from 1% to 4% [Verify] Origin [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 918 MBytes 770 Mbits/sec 0 sender [ 4] 0.00-10.00 sec 916 MBytes 769 Mbits/sec receiver Becomes [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 1.09 GBytes 936 Mbits/sec 0 sender [ 4] 0.00-10.00 sec 1.09 GBytes 934 Mbits/sec receiver [Regression Potential] Low, disable TSO on Ethernet chip will move the TCP segmentation task to CPU. This increase CPU loading a little bit, and should not introduce any regression. = Testing with iperf3 send speed is only 750mbps while receive speed is normal - 940mbps. Ubuntu 18.04.1 Msi b250m mortar --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: django 1016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-09 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A69 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=991b4393-3308-4615-97c8-9854b3bdc67e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.60 dmi.board.asset.tag: Default string dmi.board.name: B250M MORTAR ARCTIC (MS-7A69) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd06/29/2018:svnMSI:pnMS-7A69:pvr2.0:rvnMSI:rnB250MMORTARARCTIC(MS-7A69):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7A69 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1802691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880834] Re: qeth: utilize virtual MAC for Layer2 OSD devices
** 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/1880834 Title: qeth: utilize virtual MAC for Layer2 OSD devices Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * A qeth device on a DPM-managed (HMC) IBM Z machine does not obtain its MAC address for layer2 OSD interfaces from the OSA Network Adapter, instead it uses a random MAC address. * This can cause connectivity issues in environments where reliable and pre-determined MAC addresses are required, ie. when doing network configuration based on DHCP. [Fix] * Backport 1: https://launchpadlibrarian.net/481647649/0001-s390-qeth- improve-fallback-to-random-MAC-address.patch * Backport 2: https://launchpadlibrarian.net/481647657/0002-s390-qeth- utilize-virtual-MAC-for-Layer2-OSD-devices.patch [Test Case] * Bring up a qeth L2 OSD interface in DPM-managed (HMC) LPAR * Inspect the interface's MAC address. It should be the same as displayed in the HMC DPM panels. * Due to the fact that a system is needed where the HMC is in DPM moce (rather than in classic mode) this needs to be tested by IBM. [Regression Potential] * There is a certain risk for a regression, since OSA devices are the standard netweork devices on s390x. * But static network configurations are still more popular for the usually long running workload on s390x and not dynamic assignments. * On the other hand qeth devices are s390x only, so this will at least not affect common code or code for other architectures. * The modifications are limited to drivers/s390/net/qeth_*. * The patches are upstream since quite a while, which speaks for their stability. [Other Info] * The upstream patch 21b1702af12e "s390/qeth: improve fallback to random MAC address" got upstream accepted with 4.18, hence is already in all Ubuntu release that are newer than bionic * And the upstream patch b144b99fff69 "s390/qeth: utilize virtual MAC for Layer2 OSD devices" got upstream accepted with 5.0, hence is also already in all Ubuntu release that are newer than bionic. __ ---Problem Description--- qeth on a DPM-managed IBM Z machine does not obtain its MAC Address for L2 OSD interfaces from the OSA Network Adapter. Instead it uses a random MAC Address. This causes connectivity issues in setups where a reliable & pre- determined MAC Address is required - ie. when doing network configuration via DHCP. ---uname output--- Ubuntu 18.04 / vmlinuz-4.15.0-101-generic Machine Type = IBM z14 GA2 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- - Bring up a qeth L2 OSD interface in DPM-managed LPAR. - Inspect the interface's MAC Address. It should be the same as displayed in the DPM Panels. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Attach sysctl -a output output to the bug. Backport of "s390/qeth: improve fallback to random MAC address" Backport of "s390/qeth: utilize virtual MAC for Layer2 OSD devices" This ticket is for 18.04 only. Already available with 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1880834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880656] Re: Fix incorrect speed/duplex when I210 device is runtime suspended
** Changed in: linux (Ubuntu Focal) 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/1880656 Title: Fix incorrect speed/duplex when I210 device is runtime suspended Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-5.6 source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: New Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] When I210 device is runtime suspended, trying to read speed or duplex from sysfs causes an error: [ 385.991957] igb :03:00.0 enp3s0: PCIe link lost [Fix] Only try to read the device register when it's not runtime suspended. [Test] Without the fix: $ cat /sys/class/net/enp3s0/speed 1000 With the fix: $ cat /sys/class/net/enp3s0/speed -1 -1 means "unknown speed", which is the correct status when device is runtime suspend. [Regression Potential] Low. It's a trivial fix which limits to one driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1880656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880660] Re: security: lockdown: remove trailing semicolon before function body
** Changed in: linux (Ubuntu Focal)
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/1880660
Title:
security: lockdown: remove trailing semicolon before function body
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Confirmed
Bug description:
[Impact]
In focal commit 40fc208c8aae ("UBUNTU: SAUCE: (lockdown) security:
lockdown: expose a hook to lock the kernel down") adds an inline
function with a trailing semicolon before the function body, that can
potentially cause build errors.
[Test case]
Build anything that includes linux/security.h and check for
warnings/errors.
[Fix]
Fix by removing the trailing semicolon.
[Regression potential]
The problem is an obvious syntax error, fix is trivial, so regression
potential is minimal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880660/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Confirmed Status in linux source package in Focal: Fix Committed Bug description: This is for alsa-ucm-conf: The patches are already in the mainline alsa-ucm-conf, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] After fixing the kernel, we also need to change the ucm2 to make it support the machine without Intel hdmi audio. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline alsa-ucm-conf. And we already tested them on 4 HP machines. This is for linux kernel: The patch is already in the oem-5.6 kernel and unstable kernel, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] Intel upstream 2 patches in the kernel to fix it. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline kernel. On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880213] Re: ext2 build failure on 4.4.0-180.210
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880213 Title: ext2 build failure on 4.4.0-180.210 Status in linux package in Ubuntu: Invalid Status in linux-snapdragon package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-snapdragon source package in Xenial: Fix Committed Bug description: [Impact] Build failure when building ext2 fs/ext2/xattr.c:828:18: error: 'ext2_xattr_cache' undeclared (first use in this function) atomic_read(&ext2_xattr_cache->c_entry_count)); [Fix] The fix is upstream commit 32302085a8d90859c40cf1a5e8313f575d06ec75 "ext2: fix debug reference to ext2_xattr_cache" [Test case] Enable CONFIG_EXT2_FS and build kernel [Regression potential] Low, fix is changing the contents of a print to a string literal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881576] Re: seccomp_benchmark times out on eoan
This issue can be found on E-kvm ** Tags added: 5.3 eoan sru-20200518 ubuntu-kernel-selftests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881576 Title: seccomp_benchmark times out on eoan Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] seccomp selftests will timeout, causing the test to be detected as failure. [Fix] Set timeout to 90s. [Test case] Run sudo make run_tests under tools/testing/selftests/seccomp/. [Regression potential] Minimal, the test could still timeout, but by reading the code, it should take around 42s to 50s to execute in the worst cases, so 90s seem safe enough. == As it tries to calibrate how many samples will take more than 5 seconds to execute, it may end up picking up a number of samples that take 10 (but up to 12) seconds. As the calibration will take double that time, it takes around 20 seconds. Then, it executes the whole thing again, and then once more, with some added overhead. So, the thing might take more than 40 seconds, which is too close to the 45s timeout. So, it times out once in a while depending on the system. Using a timeout of 90 seconds should be safe enough for this test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Changed in: linux (Debian) Status: Unknown => 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/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882167] Re: ubuntu_zfs_xfs_generic failed to build on X-4.4
Boot back to 4.4.0-180 on the same instance, it's still having this issue. And it looks like we're using the same test suite for 4.4.0-180 and 4.4.0-181 >From the test history with 4.4.0-180: Running 'git clone https://github.com/tytso/xfstests-bld' Cloning into 'xfstests-bld'... Using head commit for xfstests-blda4df7d7b31125901cb1fe9b092f495b6aa950448 Running 'git reset --hard a4df7d7b31125901cb1fe9b092f495b6aa950448' HEAD is now at a4df7d7 Update the default version of quota and xfsprogs Running './get-all' Cloning into 'fio'... Checking out fio fio-3.15 (previously was fio-3.19-74-gb09c96c) Cloning into 'quota'... Checking out quota 6e631074330a (previously was fdd774b) Cloning into 'xfsprogs-dev'... Checking out xfsprogs-dev v5.2.0 (previously was v5.6.0) Cloning into 'xfstests-dev'... Cloning into 'fsverity'... Cloning into 'blktests'... Using xfs from known stable commit point 82eda8820ddd68dab0bc35199a53a08f58b1d26c Running 'git reset --hard 82eda8820ddd68dab0bc35199a53a08f58b1d26c' >From the test history with 4.4.0-181: Running 'git clone https://github.com/tytso/xfstests-bld' Cloning into 'xfstests-bld'... Using head commit for xfstests-blda4df7d7b31125901cb1fe9b092f495b6aa950448 Running 'git reset --hard a4df7d7b31125901cb1fe9b092f495b6aa950448' HEAD is now at a4df7d7 Update the default version of quota and xfsprogs Fetching all repos.. Running './get-all' Cloning into 'fio'... Checking out fio fio-3.15 (previously was fio-3.20-21-g00ca8df) Cloning into 'quota'... Checking out quota 6e631074330a (previously was 13bb8c2) Cloning into 'xfsprogs-dev'... Checking out xfsprogs-dev v5.2.0 (previously was v5.6.0) Cloning into 'xfstests-dev'... Cloning into 'fsverity'... Cloning into 'blktests'... Using xfs from known stable commit point 82eda8820ddd68dab0bc35199a53a08f58b1d26c Running 'git reset --hard 82eda8820ddd68dab0bc35199a53a08f58b1d26c' HEAD is now at 82eda88 btrfs: Verify falloc on multiple holes won't leak qgroup reserved data space -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882167 Title: ubuntu_zfs_xfs_generic failed to build on X-4.4 Status in linux package in Ubuntu: Incomplete Bug description: The test compilation will fail with: cc: error: unrecognized command line option '-Wimplicit-fallthrough' This build issue does not exist with 4.4.0-180 + gcc 5.4.0-6ubuntu1~16.04.12 Please find attachment for the full build log. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-181-generic 4.4.0-181.211 ProcVersionSignature: Ubuntu 4.4.0-181.211-generic 4.4.223 Uname: Linux 4.4.0-181-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Jun 4 22:56:00 2020 HibernationDevice: RESUME=/dev/mapper/mpatha1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kernel01_vg-kernel01_lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-181-generic N/A linux-backports-modules-4.4.0-181-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882167] Re: ubuntu_zfs_xfs_generic failed to build on X-4.4
This option appears in the "fio" repo: ubuntu@kernel01:~/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld$ grep -r "Wimplicit-fallthrough" * fio/configure:# check if gcc has -Wimplicit-fallthrough fio/configure:if compile_prog "-Wimplicit-fallthrough" "" "-Wimplicit-fallthrough"; then fio/configure:print_config "-Wimplicit-fallthrough" "$fallthrough" fio/configure: CFLAGS="$CFLAGS -Wimplicit-fallthrough" $ gcc --version gcc (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609 ** Description changed: The test compilation will fail with: - cc: error: unrecognized command line option '-Wimplicit-fallthrough' + cc: error: unrecognized command line option '-Wimplicit-fallthrough' + This build issue does not exist with 4.4.0-180 + gcc + 5.4.0-6ubuntu1~16.04.12 Please find attachment for the full build log. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-181-generic 4.4.0-181.211 ProcVersionSignature: Ubuntu 4.4.0-181.211-generic 4.4.223 Uname: Linux 4.4.0-181-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: - + Date: Thu Jun 4 22:56:00 2020 HibernationDevice: RESUME=/dev/mapper/mpatha1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: - + Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: - + ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kernel01_vg-kernel01_lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: - linux-restricted-modules-4.4.0-181-generic N/A - linux-backports-modules-4.4.0-181-generic N/A - linux-firmware 1.157.23 + linux-restricted-modules-4.4.0-181-generic N/A + linux-backports-modules-4.4.0-181-generic N/A + linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882167 Title: ubuntu_zfs_xfs_generic failed to build on X-4.4 Status in linux package in Ubuntu: Incomplete Bug description: The test compilation will fail with: cc: error: unrecognized command line option '-Wimplicit-fallthrough' This build issue does not exist with 4.4.0-180 + gcc 5.4.0-6ubuntu1~16.04.12 Please find attachment for the full build log. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-181-generic 4.4.0-181.211 ProcVersionSignature: Ubuntu 4.4.0-181.211-generic 4.4.223 Uname: Linux 4.4.0-181-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Jun 4 22:56:00 2020 HibernationDevice: RESUME=/dev/mapper/mpatha1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kernel01_vg-kernel01_lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-181-generic N/A linux-backports-modules-4.4.0-181-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882167] 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 1882167 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/1882167 Title: ubuntu_zfs_xfs_generic failed to build on X-4.4 Status in linux package in Ubuntu: Incomplete Bug description: The test compilation will fail with: cc: error: unrecognized command line option '-Wimplicit-fallthrough' This build issue does not exist with 4.4.0-180 + gcc 5.4.0-6ubuntu1~16.04.12 Please find attachment for the full build log. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-181-generic 4.4.0-181.211 ProcVersionSignature: Ubuntu 4.4.0-181.211-generic 4.4.223 Uname: Linux 4.4.0-181-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Jun 4 22:56:00 2020 HibernationDevice: RESUME=/dev/mapper/mpatha1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kernel01_vg-kernel01_lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-181-generic N/A linux-backports-modules-4.4.0-181-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879680] Re: Elantech PS/2 [ACPI/ETD0449] Touchpad not detected on Wortmann 1460p
So it seems you have an Elantech PS/2 [ACPI/ETD0449] Touchpad, but somehow it's not probed by kernel. Please append following kernel boot parameters, reboot and attach output of `journalctl -b`: "dyndbg=file drivers/input/* +pt" i8042.debug=1 log_buf_len=32M For detailed steps, please see https://askubuntu.com/questions/19486 /how-do-i-add-a-kernel-boot-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/1879680 Title: Elantech PS/2 [ACPI/ETD0449] Touchpad not detected on Wortmann 1460p Status in linux package in Ubuntu: Incomplete Bug description: The Touchpad is not detected on any Ubuntu Live or installed Version from 16.04 to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabi 1399 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 12:52:57 2020 InstallationDate: Installed on 2020-05-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Wortmann_AG 1220615;1470142 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgubuntu-root ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 52.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: A35 dmi.board.vendor: EA dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: EA dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr52.10:bd06/01/2018:svnWortmann_AG:pn1220615;1470142:pvr1460P;1470142:rvnEA:rnA35:rvrType2-BoardVersion:cvnEA:ct10:cvrChassisVersion: dmi.product.family: NB-TERRA;MOBILE-B;14 dmi.product.name: 1220615;1470142 dmi.product.sku: 4039407048694 dmi.product.version: 1460P;1470142 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882167] [NEW] ubuntu_zfs_xfs_generic failed to build on X-4.4
Public bug reported: The test compilation will fail with: cc: error: unrecognized command line option '-Wimplicit-fallthrough' Please find attachment for the full build log. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-181-generic 4.4.0-181.211 ProcVersionSignature: Ubuntu 4.4.0-181.211-generic 4.4.223 Uname: Linux 4.4.0-181-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Jun 4 22:56:00 2020 HibernationDevice: RESUME=/dev/mapper/mpatha1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kernel01_vg-kernel01_lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-181-generic N/A linux-backports-modules-4.4.0-181-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug package-from-proposed s390x xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882167 Title: ubuntu_zfs_xfs_generic failed to build on X-4.4 Status in linux package in Ubuntu: New Bug description: The test compilation will fail with: cc: error: unrecognized command line option '-Wimplicit-fallthrough' Please find attachment for the full build log. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-181-generic 4.4.0-181.211 ProcVersionSignature: Ubuntu 4.4.0-181.211-generic 4.4.223 Uname: Linux 4.4.0-181-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Jun 4 22:56:00 2020 HibernationDevice: RESUME=/dev/mapper/mpatha1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kernel01_vg-kernel01_lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-181-generic N/A linux-backports-modules-4.4.0-181-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882167] Re: ubuntu_zfs_xfs_generic failed to build on X-4.4
** Attachment added: "build.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882167/+attachment/5380474/+files/build.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882167 Title: ubuntu_zfs_xfs_generic failed to build on X-4.4 Status in linux package in Ubuntu: New Bug description: The test compilation will fail with: cc: error: unrecognized command line option '-Wimplicit-fallthrough' Please find attachment for the full build log. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-181-generic 4.4.0-181.211 ProcVersionSignature: Ubuntu 4.4.0-181.211-generic 4.4.223 Uname: Linux 4.4.0-181-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Jun 4 22:56:00 2020 HibernationDevice: RESUME=/dev/mapper/mpatha1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kernel01_vg-kernel01_lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-181-generic N/A linux-backports-modules-4.4.0-181-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882159] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882159 Title: 10s delay after grub, before kernel messages start Status in linux package in Ubuntu: Confirmed Bug description: - fresh install of 20.04 X64 in a vmware vm - "quiet splash" kernel args have been removed - the kernel messages should start immediately after grub menu selection - but there's a 10s delay grub config ``` GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=menu GRUB_TIMEOUT=3 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 20:34:38 2020 InstallationDate: Installed on 2020-06-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. ens32 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=606fed4f-11b6-4349-803e-69c555177718 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882159] [NEW] 10s delay after grub, before kernel messages start
Public bug reported: - fresh install of 20.04 X64 in a vmware vm - "quiet splash" kernel args have been removed - the kernel messages should start immediately after grub menu selection - but there's a 10s delay grub config ``` GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=menu GRUB_TIMEOUT=3 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 20:34:38 2020 InstallationDate: Installed on 2020-06-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. ens32 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=606fed4f-11b6-4349-803e-69c555177718 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882159 Title: 10s delay after grub, before kernel messages start Status in linux package in Ubuntu: Confirmed Bug description: - fresh install of 20.04 X64 in a vmware vm - "quiet splash" kernel args have been removed - the kernel messages should start immediately after grub menu selection - but there's a 10s delay grub config ``` GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=menu GRUB_TIMEOUT=3 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 20:34:38 2020 InstallationDate: Installed on 2020-06-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. ens32 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=606fed4f-11b6-4349-803e-69c555177718 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPl
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Upgrading the bios to latest version fixed the problem here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 WORKAROUND 3: upgrade BIOS Asus has released updated BIOSes, which probably include the newest microcode. After upgrading workarounds 1,2 are not needed. Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be (easily) reverted. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel
[Kernel-packages] [Bug 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.
** No longer affects: linux (Ubuntu) ** No longer affects: linux-firmware (Ubuntu) -- 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/1876847 Title: HP-Spectre 2019 Intel wireless driver is detected incorrectly. Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Incorrect wifi drivers detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1876847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.
** Attachment removed: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5366548/+files/lspci-vnvn.log ** Attachment removed: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5366549/+files/version.log ** Attachment removed: "wireless.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5366550/+files/wireless.png ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367085/+files/AlsaInfo.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367086/+files/CRDA.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367087/+files/CurrentDmesg.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367088/+files/IwConfig.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367089/+files/Lspci.txt ** Attachment removed: "Lspci-vt.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367090/+files/Lspci-vt.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367091/+files/Lsusb.txt ** Attachment removed: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367092/+files/Lsusb-t.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367093/+files/Lsusb-v.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367094/+files/ProcCpuinfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367095/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367096/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367097/+files/ProcModules.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367098/+files/PulseList.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367099/+files/UdevDb.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5367100/+files/WifiSyslog.txt ** Description changed: - Output of lsb_release -rd, - Description: Ubuntu 20.04 LTS - Release: 20.04 - - Issue: - I have Intel AX-201 for wireless but when i do "lspci -k", the driver is detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows that the wireless driver detected is "Intel AX-201". - - Output of lspci -k, - 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 - Subsystem: Intel Corporation Wireless-AC 9462 - Kernel driver in use: iwlwifi - Kernel modules: iwlwifi - - Output of journalctl -k | grep iwlwifi, - May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002) - May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2 - May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2 - May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 - May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM - May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0 - May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm - May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354 - May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM - May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. - May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 7c:b2:7d:d0:d5:95 - May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0 - May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM - May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - re-configuring - - In the additional drivers module, it shows that module Intel-9462 no - longer works. My bluetooth is also not detected and doesn't work. - - I came across this but no else responded yet. So decided to report a bug here. - https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems - - Pleas
[Kernel-packages] [Bug 1881096] Re: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf
** Also affects: linux (Ubuntu Focal) 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/1881096 Title: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: ---Problem Description--- ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable with perf stat -e ---uname output--- Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = z15 8561 ---Steps to Reproduce--- lscpumf -c gives a list of available counters, but a few of them are not usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR perf list is also not offering these counters. A solution will be a backport to 20.04, and tried to made available for next SRU , code needed before 06-12. Addl Info from Dev: I have downloaded the following repository https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal and checked out branch master-next. Both patches appended apply without warning and the compilation showed no error. For the perf tool: e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM z15 For the s390 kernel d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15 All accepted for kernel 5.7 rc1 Please include both patches into Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1881096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
Also appears in focal, generating a syslog warning about every 5 seconds, which makes using a tty console quite difficult: $ uname -r 5.4.0-33-generic $ tail /var/log/syslog Jun 4 21:48:16 alpe kernel: [ 1350.631168] usb usb4-port1: Cannot enable. Maybe the USB cable is bad? Jun 4 21:48:20 alpe kernel: [ 1355.047109] usb usb4-port1: Cannot enable. Maybe the USB cable is bad? Jun 4 21:48:25 alpe kernel: [ 1359.507044] usb usb4-port1: Cannot enable. Maybe the USB cable is bad? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856608 Title: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Incomplete Bug description: This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81. This bug was fixed by simply reverting the offending change. Bug 1859873 tracks root causing the issue and reapplying the change w/ any necessary fixes. [Impact] USB port unusable and boot time takes ~5 minutes longer to complete. Kernel emits messages like: usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [Test Case] dmesg | grep "Cannot enable" [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Just to add some info. Hereafter you will find xinput with 5.4.0-34.38 loaded. Elan touchpad is not detected at all. Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ PixArt USB Optical Mouse id=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Ideapad extra buttons id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] Please, can you give some hints? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Confirmed Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879559] Re: net/bpfilter: remove superfluous testing message
Same issue on Raspberry PI running Eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879559
Title:
net/bpfilter: remove superfluous testing message
Status in linux package in Ubuntu:
Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
Confirmed
Bug description:
[Impact]
A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
usage for /dev/kmsg") but should've been deleted before patch submission.
Although it doesn't cause any harm to the code or functionality itself, it's
totally unpleasant to have it displayed on every loop iteration with no real
use case. Thus remove it unconditionally.
Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699
[Test Case]
Just check dmesg:
[ 10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
[ 15.306015] bpfilter: Loaded bpfilter_umh pid 1036
[ 15.306280] Started bpfilter
[ 15.306283] testing the buffer
[ 15.306458] testing the buffer
[ 15.306880] testing the buffer
[ 15.318003] testing the buffer
[ 15.318057] testing the buffer
[ 15.318814] testing the buffer
[ 15.442147] testing the buffer
[ 15.479556] testing the buffer
[ 15.479572] testing the buffer
[Regression Potential]
Very low. The fix is a one line upstream patch that removes one
printf.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879559/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880421] Re: zfsutils-linux fails to install if `modprobe zfs` fails
This bug was fixed in the package zfs-linux - 0.8.4-1ubuntu4 --- zfs-linux (0.8.4-1ubuntu4) groovy; urgency=medium * Don't report errors if modprobe fails (LP: #1880421) - loading ZFS modules on zfs-utils installation is a nice to have feature, but don't throw an error if modules are not available to load -- Colin Ian King Thu, 4 Jun 2020 13:54:54 +0100 ** Changed in: zfs-linux (Ubuntu Groovy) Status: In Progress => Fix Released -- 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/1880421 Title: zfsutils-linux fails to install if `modprobe zfs` fails Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Groovy: Fix Released Bug description: Description: When installing zfsutils-linux, failure to `modprobe zfs` cause the package installation to fail. Ideally, modprobe should be attempted but not fatal. Steps to reproduce: # Prevent module loading $ sudo sysctl kernel.modules_disabled=1 # Install the package $ sudo apt install -y zfsutils-linux This should succeed but fails with: Reading package lists... Done Building dependency tree Reading state information... Done zfsutils-linux is already the newest version (0.8.3-1ubuntu12). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up zfsutils-linux (0.8.3-1ubuntu12) ... insmod /lib/modules/5.4.0-31-generic/kernel/zfs/zlua.ko modprobe: ERROR: could not insert 'zfs': Operation not permitted zfs-import-scan.service is a disabled or a static unit, not starting it. A dependency job for zfs-import-cache.service failed. See 'journalctl -xe' for details. Job for zfs-load-module.service failed because the control process exited with error code. See "systemctl status zfs-load-module.service" and "journalctl -xe" for details. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-load-module.service failed because the control process exited with error code. See "systemctl status zfs-load-module.service" and "journalctl -xe" for details. A dependency job for zfs-import-cache.service failed. See 'journalctl -xe' for details. Job for zfs-share.service failed because the control process exited with error code. See "systemctl status zfs-share.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-share, action "start" failed. ● zfs-share.service - ZFS file system shares Loaded: loaded (/lib/systemd/system/zfs-share.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-05-24 16:56:03 UTC; 52ms ago Docs: man:zfs(8) Process: 9283 ExecStartPre=/bin/rm -f /etc/dfs/sharetab (code=exited, status=0/SUCCESS) Process: 9284 ExecStart=/sbin/zfs share -a (code=exited, status=1/FAILURE) Main PID: 9284 (code=exited, status=1/FAILURE) May 24 16:56:03 ocelot systemd[1]: Starting ZFS file system shares... May 24 16:56:03 ocelot zfs[9284]: The ZFS modules are not loaded. May 24 16:56:03 ocelot zfs[9284]: Try running '/sbin/modprobe zfs' as root to load them. May 24 16:56:03 ocelot systemd[1]: zfs-share.service: Main process exited, code=exited, status=1/FAILURE May 24 16:56:03 ocelot systemd[1]: zfs-share.service: Failed with result 'exit-code'. May 24 16:56:03 ocelot systemd[1]: Failed to start ZFS file system shares. dpkg: error processing package zfsutils-linux (--configure): installed zfsutils-linux package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of zfs-zed: zfs-zed depends on zfsutils-linux (>= 0.8.3-1ubuntu12); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-zed (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: zfsutils-linux zfs-zed E: Sub-process /usr/bin/dpkg returned an error code (1) Additional information: $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12 Candidate: 0.8.3-1ubuntu12 Version table: *** 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1880421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: Unknown Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882135] [NEW] System doesn't resume from suspend when bcmwl-kernel-source is installed
Public bug reported: 1) The release of Ubuntu you are using: Ubuntu 20.04 LTS 2) The version of the package you are using: 6.30.223.271+bdcom-0ubuntu5 3) What you expected to happen When I wake my PC from suspend by touching a button on the keyboard, I expect the PC to resume. 4) What happened instead 1 time out of 10: The PC resumes. 9 times out of 10: The fans spin up, but the display doesn't even wake up. The system isn't reachable over the network. Ping doesn't work, CTRL-ALT-Fx keys have no effect, the reset button of the PC doesn't work. The only way to reset my PC is by pressing and holding the power button for 10 seconds. (When the PC is running normally, the reset button works. I did verify the wiring of that button.) When this package isn't installed, the PC wakes up 10 times out of 10. I personally don't need this driver, so I will just uninstall it as a workaround. I have just verified that, when installed, the wifi seems to function correctly at the maximum speed I can reasonably test. I noticed, but didn't thoroughly test, that when the PC is suspended while connected to a wireless nerwork, resume always works. (I suspend/resumed 5 times). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 21:51:55 2020 InstallationDate: Installed on 2019-10-31 (217 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: bcmwl UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1882135 Title: System doesn't resume from suspend when bcmwl-kernel-source is installed Status in bcmwl package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using: Ubuntu 20.04 LTS 2) The version of the package you are using: 6.30.223.271+bdcom-0ubuntu5 3) What you expected to happen When I wake my PC from suspend by touching a button on the keyboard, I expect the PC to resume. 4) What happened instead 1 time out of 10: The PC resumes. 9 times out of 10: The fans spin up, but the display doesn't even wake up. The system isn't reachable over the network. Ping doesn't work, CTRL-ALT-Fx keys have no effect, the reset button of the PC doesn't work. The only way to reset my PC is by pressing and holding the power button for 10 seconds. (When the PC is running normally, the reset button works. I did verify the wiring of that button.) When this package isn't installed, the PC wakes up 10 times out of 10. I personally don't need this driver, so I will just uninstall it as a workaround. I have just verified that, when installed, the wifi seems to function correctly at the maximum speed I can reasonably test. I noticed, but didn't thoroughly test, that when the PC is suspended while connected to a wireless nerwork, resume always works. (I suspend/resumed 5 times). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 21:51:55 2020 InstallationDate: Installed on 2019-10-31 (217 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: bcmwl UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1882135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Speaking of cloud-images generally I propose the following:
* Images in the ubuntu-cpc project by default should boot with an initramfs.
* Revert the livecd-rootfs change which "Unconditionally set
GRUB_FORCE_PARTUUID in cloud images"
* Images with custom kernels can boot without an initramfs
* Set GRUB_FORCE_PARTUUID as part of livefs-rootfs:live-build/functions
replace_kernel() as this is used by the ubuntu-cpc project for each image that
ships an optimized kernel intended to boot without initramfs.
Steve, I agree with everything you said in comment #21 about removing
not this functionality from Azure images. I think there is room to
improve the experience for users that change their kernel and encounter
this behavior. The panic/reboot behavior is unexpected and the mapping
of GRUB_FORCE_PARTUUID to initramfs-less boot is non-obvious to the end
user. I don't immediately have suggestions to smooth this rough edge
but I feel that we need to take some time on this before completely
closing this bug out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
New
Status in grub2 package in Ubuntu:
Won't Fix
Status in linux-azure package in Ubuntu:
Invalid
Status in livecd-rootfs package in Ubuntu:
Triaged
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882128] [NEW] Disco update: upstream stable patchset 2020-06-04
Public bug reported: 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 2020-06-04 Ported from the following upstream stable releases: v4.19.125, v.5.4.43 from git://git.kernel.org/ x86/uaccess, ubsan: Fix UBSAN vs. SMAP ubsan: build ubsan.c more conservatively i2c: dev: Fix the race between the release of i2c_dev and cdev KVM: SVM: Fix potential memory leak in svm_cpu_init() riscv: set max_pfn to the PFN of the last page ima: Set file->f_mode instead of file->f_flags in ima_calc_file_hash() evm: Check also if *tfm is an error pointer in init_desc() ima: Fix return value of ima_write_policy() mtd: spinand: Propagate ECC information to the MTD structure fix multiplication overflow in copy_fdtable() ubifs: remove broken lazytime support iommu/amd: Fix over-read of ACPI UID from IVRS table i2c: mux: demux-pinctrl: Fix an error handling path in 'i2c_demux_pinctrl_probe()' ubi: Fix seq_file usage in detailed_erase_block_info debugfs file gcc-common.h: Update for GCC 10 HID: multitouch: add eGalaxTouch P80H84 support HID: alps: Add AUI1657 device ID HID: alps: ALPS_1657 is too specific; use U1_UNICORN_LEGACY instead scsi: qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV scsi: qla2xxx: Delete all sessions before unregister local nvme port configfs: fix config_item refcnt leak in configfs_rmdir() vhost/vsock: fix packet delivery order to monitoring devices aquantia: Fix the media type of AQC100 ethernet controller in the driver component: Silence bind error on -EPROBE_DEFER scsi: ibmvscsi: Fix WARN_ON during event pool release HID: i2c-hid: reset Synaptics SYNA2393 on resume x86/apic: Move TSC deadline timer debug printk gtp: set NLM_F_MULTI flag in gtp_genl_dump_pdp() HID: quirks: Add HID_QUIRK_NO_INIT_REPORTS quirk for Dell K12A keyboard-dock ceph: fix double unlock in handle_cap_export() stmmac: fix pointer check after utilization in stmmac_interrupt USB: core: Fix misleading driver bug report platform/x86: asus-nb-wmi: Do not load on Asus T100TA and T200TA ARM: futex: Address build warning padata: Replace delayed timer with immediate workqueue in padata_reorder padata: initialize pd->cpu with effective cpumask padata: purge get_cpu and reorder_via_wq from padata_do_serial ALSA: iec1712: Initialize STDSP24 properly when using the model=staudio option ALSA: pcm: fix incorrect hw_base increase ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Xtreme ALSA: hda/realtek - Add more fixup entries for Clevo machines drm/etnaviv: fix perfmon domain interation apparmor: fix potential label refcnt leak in aa_change_profile apparmor: Fix aa_label refcnt leak in policy_update dmaengine: tegra210-adma: Fix an error handling path in 'tegra_adma_probe()' dmaengine: owl: Use correct lock in owl_dma_get_pchan() drm/i915/gvt: Init DPLL/DDI vreg for virtual display instead of inheritance. powerpc: Remove STRICT_KERNEL_RWX incompatibility with RELOCATABLE powerpc/64s: Disable STRICT_KERNEL_RWX nfit: Add Hyper-V NVDIMM DSM command set to white list libnvdimm/btt: Remove unnecessary code in btt_freelist_init libnvdimm/btt: Fix LBA masking during 'free list' population staging: most: core: replace strcpy() by strscpy() thunderbolt: Drop duplicated get_switch_at_route() media: fdp1: Fix R-Car M3-N naming in debug message Revert "net/ibmvnic: Fix EOI when running in XIVE mode" Revert "gfs2: Don't demote a glock until its revokes are written" staging: iio: ad2s1210: Fix SPI reading staging: greybus: Fix uninitialized scalar variable iio: sca3000: Remove an erroneous 'get_device()' iio: dac: vf610: Fix an error handling path in 'vf610_dac_probe()' misc: rtsx: Add short delay after exit from ASPM mei: release me_cl object reference ipack: tpci200: fix error return code in tpci200_register() rapidio: fix an error in get_user_pages_fast() error handling rxrpc: Fix a memory leak in rxkad_verify_response() x86/unwind/orc: Fix unwind_get_return_address_ptr() for inactive tasks iio: adc: stm32-adc: Use dma_request_chan() instead dma_request_slave_channel() iio: adc: stm32-adc: fix device used to request dma iio: adc: stm32-dfsdm: Use dma_request_chan() instead dma_request_slave_channel() iio: adc: stm32-dfsdm: fix device used to request dma rxrpc: Trace discarded ACKs rxrpc: Fix ack discard ubifs: fix wrong use of crypto_shash_descsize() i2c: fix missing pm_runtime_put_sync in i2c_device_probe evm: Fix a small race in init_desc() afs: Don't unlock fetched data pages until the op completes successfully mtd: Fix mtd not registered due to nvmem name collis
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Ok Kai, I modified grub options to select the kernel version. Now "uname -r" output is: 5.4.0-34-generic Touchpad is still not working. I run dmesg and udevadm again and attached the logs on this message. Sorry for the inconvenience. ** Attachment added: "logs2.tar" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+attachment/5380406/+files/logs2.tar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
Hi same problem here. Lenovo Thinkpad P53S Ubuntu 20.04. If I connect the HDMI, keeps loading and loading If I don't connect it, it works perfect. Problem appeared in 20, was perfect in 18 and 19. Thanks!!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Hi kai, I am probably doing something wrong installing test kernel published in https://people.canonical.com/~khfeng/lp1853277/ I downloaded every file in the link you shared and install them using: sudo dpkg -i each-.deb-file However you are right, output of uname -r is: 5.6.15-050615-generic which is the newest stable kernel What am I missing? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881601] Re: Fan excessively runs, even when idle
To add some additional information... I upgraded the BIOS of the machine to the latest, plugged in the TB display and rebooted to -33. The fan spun up and it didn't pass beyond C3. I unplugged the TB display and it then progressed all the way to C7 so it appears to be a TB issue. Kai- Heng is looking into the TB issue. I've plugged the second display into the HDMI port for now. Colin - yeah, the underload powerstat was taken when I was in an active Google Meet, handling docs, etc, at the same time. The machine would have been using a considerable amount of CPU. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881601 Title: Fan excessively runs, even when idle Status in linux package in Ubuntu: In Progress Bug description: I have a skull canyon NUC as my daily driver and the fan is running much higher than it should, even when the machine is completely idle. This happened with the 5.3 kernel and also with the 5.4 kernel during focal development cycle. It was fixed somewhere along the way prior to release but it's back with a vengeance now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 4523 F pulseaudio /dev/snd/controlC0: dean 4523 F pulseaudio /dev/snd/controlC1: dean 4523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 08:37:23 2020 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (677 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-07 (145 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878544] Re: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub)
Hi @koba, After checking for a couple of hours, plugging and unplugging both power, hub, and USBs/HDMI in the hub, it seems to all work perfectly with that 0-21 version of the Kernel!!! What would be the next steps? Would the fix be pushed to the latest kernel update soon? Thank you for your help! Best -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878544 Title: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub) Status in linux package in Ubuntu: Confirmed Bug description: Asus Zenbook Flip S (UX-370UAR). Intel Core i7-8550U CPU). The X freezes and doesnt even allow to start a console session. Only happening on Ubuntu 18.04 and 20.04. Does not happen in the same computer under Ubuntu 16.04 or Windows 10. Can be replicated easily. Every time I plug/unplug the power USB-C or the USB-c hub. Mostly, on any interaction with the USB-c or I/O ports. If I plug/unplug the USB-c without X in a console session (CTRL+ALT+F3) I get the following: BUG: kernel NULL point dereference, address: 0080 ... Workqueue: events ucsi_connector_change [typec_usci] RIP: 0010:ucsi_displayport_remove_partner+0xe/0x30 [typec_usci] ... Find a picture of the full error attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vks20 1808 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 23:46:49 2020 InstallationDate: Installed on 2020-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. UX370UAR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=acc6d87c-574b-4c1e-8e8f-e75c1e9ff1fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX370UAR.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX370UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.311:bd10/15/2019:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX370UAR 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/1878544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879973] Re: There is no sound from the built-in speakers and does not see the built-in microphone
I did a new install of Ubuntu 20.04 and sound work fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879973 Title: There is no sound from the built-in speakers and does not see the built-in microphone Status in linux package in Ubuntu: Confirmed Bug description: After update my Inspiron 5490 from Ubuntu 18.04 to 20.04 system see only "Dummy Sound". I updated kernel to 5.6.13-050613-lowlatency, reinstall pulseaudio, add "options snd-hda-intel dmic_detect=0" to /etc/modprobe.d/alsa- base.con, add "blacklist snd_soc_skl" to /etc/modprobe.d/blacklist.conf. I applied the solution from this source: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1876238. I still have this problem. Audio: Device-1: Intel driver: sof-audio-pci Sound Server: ALSA v: k5.6.13-050613-lowlatency $ aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-2 Uname: Linux 5.6.13-050613-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 17:18:36 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2020-01-31 (111 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-05-18 (2 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-31 (113 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: focal Uname: Linux 5.6.13-050613-lowlatency x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-31 (113 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5538 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4b1d1189-110f-4f43-a4ad-eaf0b866e9c4 ro mem_sleep_default=deep quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-3
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Tags added: sts-sponsor-mfo ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => 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/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: Unknown Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
The kernel isn't the one I compiled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
Debdiff for Bionic ** Patch added: "lp1869465_bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380403/+files/lp1869465_bionic.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: Unknown Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
Debdiff for Eoan ** Patch added: "lp1869465_eoan.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380402/+files/lp1869465_eoan.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: Unknown Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
Debdiff for Focal ** Patch added: "lp1869465_focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380401/+files/lp1869465_focal.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: Unknown Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
Debdiff for Xenial ** Patch added: "lp1869465_xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380404/+files/lp1869465_xenial.debdiff ** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: Unknown Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
Debdiff for Groovy ** Also affects: linux (Ubuntu Groovy) Importance: Medium Assignee: Ioanna Alifieraki (joalif) Status: Confirmed ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Patch added: "lp1869465_groovy.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380399/+files/lp1869465_groovy.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: Unknown Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861009] Re: Asus Zenbook Flip 15 ux563fd no sound
Thanks a lot! Sound works flawless now :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861009 Title: Asus Zenbook Flip 15 ux563fd no sound Status in linux package in Ubuntu: Confirmed Bug description: Bought a new laptop for a couple weeks ago and want to have a dual boot with W10 and Linux like my older one. First, I installed Ubuntu 18.04 and tried to make sound working via the speakers. I tried alsamixer, made sure everything was on OO, reinstalled both alsamixer and pulseaudio couple times, checked permissions on the config of pulseaudio and more what could fix it in regular terms including installing and replacing kernels older and new ones. As a last option, I installed version 19.10 from Ubuntu as someone mentioned that the higher version could fix it because of the different supported packages but is not resolving it. Nothing of the above mentioned things where fixing it, but I still see some movement at streaming bar in the sound option menu when I'm playing some music. I hope there is a workaround for this issue, I just found the whole Zenbook laptop line that has this problem so I really hope for a solution to this. Version - kernel: Ubuntu 5.3.0-26.28-generic 5.3.13 lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b61] (rev 0c) Subsystem: ASUSTeK Computer Inc. Device [1043:1b31] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) DeviceName: VGA Subsystem: ASUSTeK Computer Inc. Device [1043:1b31] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [1043:1b31] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [1043:1b31] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel_ish_ipc Kernel modules: intel_ish_ipc 00:14.0 USB controller [0c
[Kernel-packages] [Bug 1881675] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:0010] iwlwifi Microcode SW Error ubuntu 20.04
When my wifi card has issues after long usage, I re-init wifi driver like "modprobe -r iwlwifi ; modprobe iwlwifi", and it may save some troubles rebooting. I don't have Intel wifi but this works on my Qualcomm Atheros QCA6174 (which uses ath10k_pci). You may also clear the logs in /var/log/ directory. There are also discussion about limiting log size (i.e. https://serverfault.com/questions/546072/how-to-avoid-log-files-growing- too-big) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881675 Title: Intel Wireless 8260 [8086:24f3] Subsystem [8086:0010] iwlwifi Microcode SW Error ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, this bug happens and keep logging as long as I do not not shut down the computer. Internet becomes irresponsive, and the whole computer is slowed. It will keep logging until saturating the hard drive. I had to format the hard drive and reinstall to be able to use the computer again once. Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846676] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846823] iwlwifi :02:00.0: Start IWL Error Log Dump: Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846829] iwlwifi :02:00.0: Status: 0x0040, count: 6 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846833] iwlwifi :02:00.0: Loaded firmware version: 36.77d01142.0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846838] iwlwifi :02:00.0: 0x0039 | BAD_COMMAND Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846842] iwlwifi :02:00.0: 0x0230 | trm_hw_status0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846845] iwlwifi :02:00.0: 0x | trm_hw_status1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846849] iwlwifi :02:00.0: 0x00024200 | branchlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846853] iwlwifi :02:00.0: 0x00039872 | interruptlink1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846856] iwlwifi :02:00.0: 0x | interruptlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846860] iwlwifi :02:00.0: 0x0002 | data1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846863] iwlwifi :02:00.0: 0xDEADBEEF | data2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846867] iwlwifi :02:00.0: 0xDEADBEEF | data3 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846870] iwlwifi :02:00.0: 0x2D004C01 | beacon time Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846874] iwlwifi :02:00.0: 0x39E4BA08 | tsf low Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846877] iwlwifi :02:00.0: 0x0046 | tsf hi Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846880] iwlwifi :02:00.0: 0x | time gp1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846884] iwlwifi :02:00.0: 0xE24C9E94 | time gp2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846887] iwlwifi :02:00.0: 0x0001 | uCode revision type Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846891] iwlwifi :02:00.0: 0x0024 | uCode version major Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846894] iwlwifi :02:00.0: 0x77D01142 | uCode version minor Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846898] iwlwifi :02:00.0: 0x0201 | hw version Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846901] iwlwifi :02:00.0: 0x00489008 | board version Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846905] iwlwifi :02:00.0: 0x000D0304 | hcmd Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846908] iwlwifi :02:00.0: 0x24022080 | isr0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846912] iwlwifi :02:00.0: 0x | isr1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846915] iwlwifi :02:00.0: 0x0820180A | isr2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846919] iwlwifi :02:00.0: 0x004154C0 | isr3 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846922] iwlwifi :02:00.0: 0x | isr4 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846926] iwlwifi :02:00.0: 0x9B5E009D | last cmd Id Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846929] iwlwifi :02:00.0: 0x | wait_event Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846933] iwlwifi :02:00.0: 0x0080 | l2p_control Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846936] iwlwifi :02:00.0: 0x00010030 | l2p_duration Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846940] iwlwifi :02:00.0: 0x003F | l2p_mhvalid Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846943] iwlwifi :02:00.0: 0x0080 | l2p_addr_match Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846946] iwlwifi :02:00.0: 0x000D | lmpm_pmg_sel Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846950] iwlwifi :02:00.0: 0x08081421 | timestamp Jun 1 16:58:36 maxime-lx-home
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Bug watch added: Debian Bug tracker #96 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=96 ** Also affects: linux (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=96 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux package in Debian: Unknown Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
No change is necessary on the linux-azure.
** Changed in: linux-azure (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
New
Status in grub2 package in Ubuntu:
Won't Fix
Status in linux-azure package in Ubuntu:
Invalid
Status in livecd-rootfs package in Ubuntu:
Triaged
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Hi Kai, Sorry, I didn't follow you before. I attached both logs again after blacklisted elan_i2c ** Attachment added: "logs.tar" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+attachment/5380394/+files/logs.tar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881601] Re: Fan excessively runs, even when idle
Looking at the powerstat data it is also interesting to note that your machine is consuming a lot of CPU, ~50% userspace, ~29% kernel. It may be worth checking to see if there are any rouge processes running using top or htop to see if that's also contributing to the machine busy state. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881601 Title: Fan excessively runs, even when idle Status in linux package in Ubuntu: In Progress Bug description: I have a skull canyon NUC as my daily driver and the fan is running much higher than it should, even when the machine is completely idle. This happened with the 5.3 kernel and also with the 5.4 kernel during focal development cycle. It was fixed somewhere along the way prior to release but it's back with a vengeance now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 4523 F pulseaudio /dev/snd/controlC0: dean 4523 F pulseaudio /dev/snd/controlC1: dean 4523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 08:37:23 2020 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (677 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-07 (145 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881601] Re: Fan excessively runs, even when idle
Unplugging my second display (which was plugged into the USB-C (thunderbolt) port) gets me: :~# cat /sys/kernel/debug/pmc_core/package_cstate_show Package C2 : 9432921176 Package C3 : 31184452865 Package C6 : 2187632 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881601 Title: Fan excessively runs, even when idle Status in linux package in Ubuntu: In Progress Bug description: I have a skull canyon NUC as my daily driver and the fan is running much higher than it should, even when the machine is completely idle. This happened with the 5.3 kernel and also with the 5.4 kernel during focal development cycle. It was fixed somewhere along the way prior to release but it's back with a vengeance now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 4523 F pulseaudio /dev/snd/controlC0: dean 4523 F pulseaudio /dev/snd/controlC1: dean 4523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 08:37:23 2020 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (677 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-07 (145 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881601] Re: Fan excessively runs, even when idle
The -23 kernel doesn't seem to be better. In general on a well-behaves Intel SoC it should reach Package C8. I _guess_ it's because there's something connect to Thunderbolt. Can you please try unplug the "Cable Matters USB-C Video Cable" device from thunderbolt port, and see if the SoC can reach deeper Package C-state? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881601 Title: Fan excessively runs, even when idle Status in linux package in Ubuntu: In Progress Bug description: I have a skull canyon NUC as my daily driver and the fan is running much higher than it should, even when the machine is completely idle. This happened with the 5.3 kernel and also with the 5.4 kernel during focal development cycle. It was fixed somewhere along the way prior to release but it's back with a vengeance now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 4523 F pulseaudio /dev/snd/controlC0: dean 4523 F pulseaudio /dev/snd/controlC1: dean 4523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 08:37:23 2020 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (677 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-07 (145 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881675] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:0010] iwlwifi Microcode SW Error ubuntu 20.04
After reading the bug you linked (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214), it does look very similar indeed, the result is the same, and it seems to happen "randomly" after long usage, so maybe linked to a router switch indeed. I am not expert enough to try many things on my own unfortunately, but I can try to investigate more if you give me directions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881675 Title: Intel Wireless 8260 [8086:24f3] Subsystem [8086:0010] iwlwifi Microcode SW Error ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, this bug happens and keep logging as long as I do not not shut down the computer. Internet becomes irresponsive, and the whole computer is slowed. It will keep logging until saturating the hard drive. I had to format the hard drive and reinstall to be able to use the computer again once. Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846676] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846823] iwlwifi :02:00.0: Start IWL Error Log Dump: Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846829] iwlwifi :02:00.0: Status: 0x0040, count: 6 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846833] iwlwifi :02:00.0: Loaded firmware version: 36.77d01142.0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846838] iwlwifi :02:00.0: 0x0039 | BAD_COMMAND Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846842] iwlwifi :02:00.0: 0x0230 | trm_hw_status0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846845] iwlwifi :02:00.0: 0x | trm_hw_status1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846849] iwlwifi :02:00.0: 0x00024200 | branchlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846853] iwlwifi :02:00.0: 0x00039872 | interruptlink1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846856] iwlwifi :02:00.0: 0x | interruptlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846860] iwlwifi :02:00.0: 0x0002 | data1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846863] iwlwifi :02:00.0: 0xDEADBEEF | data2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846867] iwlwifi :02:00.0: 0xDEADBEEF | data3 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846870] iwlwifi :02:00.0: 0x2D004C01 | beacon time Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846874] iwlwifi :02:00.0: 0x39E4BA08 | tsf low Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846877] iwlwifi :02:00.0: 0x0046 | tsf hi Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846880] iwlwifi :02:00.0: 0x | time gp1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846884] iwlwifi :02:00.0: 0xE24C9E94 | time gp2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846887] iwlwifi :02:00.0: 0x0001 | uCode revision type Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846891] iwlwifi :02:00.0: 0x0024 | uCode version major Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846894] iwlwifi :02:00.0: 0x77D01142 | uCode version minor Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846898] iwlwifi :02:00.0: 0x0201 | hw version Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846901] iwlwifi :02:00.0: 0x00489008 | board version Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846905] iwlwifi :02:00.0: 0x000D0304 | hcmd Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846908] iwlwifi :02:00.0: 0x24022080 | isr0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846912] iwlwifi :02:00.0: 0x | isr1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846915] iwlwifi :02:00.0: 0x0820180A | isr2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846919] iwlwifi :02:00.0: 0x004154C0 | isr3 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846922] iwlwifi :02:00.0: 0x | isr4 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846926] iwlwifi :02:00.0: 0x9B5E009D | last cmd Id Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846929] iwlwifi :02:00.0: 0x | wait_event Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846933] iwlwifi :02:00.0: 0x0080 | l2p_control Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846936] iwlwifi :02:00.0: 0x00010030 | l2p_duration Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846940] iwlwifi :02:00.0: 0x003F | l2p_mhvalid Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846943] iwlwifi :02:00.0: 0x0080 | l2p_addr_match Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846946] iwlwifi :02:00.0: 0x000D | lmpm_pmg_sel Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846950] iwlwifi :02:00.0: 0x08081421 | timestamp Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846953] iwlwifi :02:00.0: 0x3848 | flow_
[Kernel-packages] [Bug 1881601] Re: Fan excessively runs, even when idle
Here's a powerstat log from the machine under load running 5.4.0-23. I can do the same for -33 if that's more helpful. :~# cat /sys/kernel/debug/pmc_core/package_cstate_show Package C2 : 9390902880 Package C3 : 31168180646 Package C6 : 0 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 0 ** Attachment added: "5.4.0-23-underload-generic.powerstat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881601/+attachment/5380393/+files/5.4.0-23-underload-generic.powerstat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881601 Title: Fan excessively runs, even when idle Status in linux package in Ubuntu: In Progress Bug description: I have a skull canyon NUC as my daily driver and the fan is running much higher than it should, even when the machine is completely idle. This happened with the 5.3 kernel and also with the 5.4 kernel during focal development cycle. It was fixed somewhere along the way prior to release but it's back with a vengeance now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 4523 F pulseaudio /dev/snd/controlC0: dean 4523 F pulseaudio /dev/snd/controlC1: dean 4523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 08:37:23 2020 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (677 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-07 (145 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
OK, I just did the following (all on 5.4.0-33-generic): * modified /etc/default/grub to include " pcie_aspm=off" in the kernel command line * `update-grub` * `reboot` * double-checked that "pcie_aspm=off" was in the kernel command line, then booted * once booted and logged in, I disabled networking Unfortunately: * re-enabling networking did not restore my network connection * rebooting did not restore my network connection * only rebooting into Windows fixed my network connection * I see the same trace on the boots with broken networking as in the original report AFAICT, the kernel command line option had no effect on the issue at hand. Anything else I can try? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220
[Kernel-packages] [Bug 1881828] Re: Lenovo X1 Extreme screen never wakes up
Tested lightly yesterday as I didn't get much time to use my laptop, however I went through several sleep/wake cycles, some with power plugged in lid left open, on battery lid left open, on battery lid down to lid up several hours later. Whenever I walked past it I did "something" to wake it up, unlock it, then walk away. 0 crashes. I will continue to use the laptop to attempt to "prove a negative." Please let me know any data to collect or further testing would be useful to attempt. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881828 Title: Lenovo X1 Extreme screen never wakes up Status in linux package in Ubuntu: Confirmed Bug description: Unreliably, but 9 times out of 10, if my screen goes to sleep on my laptop it will never wake back up. Looking in kern.log I see this output, scrolling on repeat, until I long-press the power button to shut off the laptop. Happened occasionally in Ubuntu 19.10, now regularly on 20.04. Persisted with the nvidia proprietary driver as well as the open source one. It has persisted across several official ubuntu packaged kernel revisions. I got kernel taint down to "0" and it kept happening. (Previously virtualbox and nvidia driver were in there.) May 26 20:02:30 hawk-x1 kernel: [28401.972981] No Local Variables are initialized for Method [NVPO] May 26 20:02:30 hawk-x1 kernel: [28401.972986] No Arguments are initialized for method [NVPO] May 26 20:02:30 hawk-x1 kernel: [28401.972991] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.NVPO due to previous error (AE_AML_LOOP_TIMEOUT) (20190816/psparse-529) May 26 20:02:30 hawk-x1 kernel: [28401.973016] ACPI Error: Aborting method \_SB.PCI0.PGON due to previous error (AE_AML_LOOP_TIMEOUT) (20190816/psparse-529) May 26 20:02:30 hawk-x1 kernel: [28401.973033] ACPI Error: Aborting method \_SB.PCI0.PEG0.PG00._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20190816/psparse-529) May 26 20:02:30 hawk-x1 kernel: [28401.973058] acpi device:00: Failed to change power state to D0 May 26 20:02:31 hawk-x1 kernel: [28403.217052] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) May 26 20:02:31 hawk-x1 kernel: [28403.217064] nouveau :01:00.0: Refused to change power state, currently in D3 May 26 20:02:31 hawk-x1 kernel: [28403.277092] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) May 26 20:02:31 hawk-x1 kernel: [28403.296906] nouveau :01:00.0: Refused to change power state, currently in D3 May 26 20:02:31 hawk-x1 kernel: [28403.296915] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) May 26 20:02:31 hawk-x1 kernel: [28403.316894] nouveau :01:00.0: Refused to change power state, currently in D3 May 26 20:02:31 hawk-x1 kernel: [28403.319495] nouveau :01:00.0: tmr: stalled at May 26 20:02:31 hawk-x1 kernel: [28403.319497] [ cut here ] May 26 20:02:31 hawk-x1 kernel: [28403.319498] nouveau :01:00.0: timeout May 26 20:02:31 hawk-x1 kernel: [28403.319551] WARNING: CPU: 2 PID: 2697 at drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0xd6/0xe0 [nouveau] May 26 20:02:31 hawk-x1 kernel: [28403.319552] Modules linked in: xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_addrtype bpfilter ccm overlay aufs bnep binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt iwlmvm snd_sof_intel_ipc snd_sof mac80211 uvcvideo snd_sof_xtensa_dsp snd_hda_ext_core videobuf2_vmalloc snd_soc_acpi_intel_match videobuf2_memops snd_soc_acpi btusb libarc4 videobuf2_v4l2 btrtl videobuf2_common btbcm wmi_bmof thinkpad_acpi input_leds joydev snd_hda_codec_realtek btintel snd_soc_core snd_seq_midi videodev bluetooth snd_hda_codec_generic serio_raw snd_seq_midi_event nvram snd_compress ac97_bus intel_wmi_thunderbolt snd_pcm_dmaengine ledtrig_audio mc iwlwifi snd_rawmidi ecdh_generic 8250_dw ecc snd_hda_intel mei_me cfg80211 May 26 20:02:31 hawk-x1 kernel: [28403.319567] snd_intel_dspcfg mei snd_hda_codec snd_seq snd_hda_core ucsi_acpi snd_hwdep processor_thermal_device typec_ucsi intel_rapl_common snd_pcm intel_pch_thermal intel_soc_dts_iosf typec snd_seq_device snd_timer snd soundcore int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad acpi_thermal_rel sch_fq_codel iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc arp_tables parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt uas usb_storage crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nouveau mxm_wmi i2c_algo_bit ttm drm_kms_he
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Can you please attach `dmesg` and `udevadm info -e` with elan_i2c blacklisted? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Description changed: + [Impact] + + On some arm systems makedumpfile fails to translate virtual to physical addresses properly. + This may result in makedumpfile looping forever exhausting + all memory, or translating a virtual address to an invalid physical address + and then failing and falling back to cp. + The reason it cannot resolve some addresses is because the PMD mask is wrong. + When physical address mask allows up to 48bits pmd mask should allow the + same, currently pmd mask is set to 40bits (see commit [1]). + + Commit [1] fixes this bug. + + [Test Case] + + To hit this bug you need a system that needs physical addresses over 1TB. + This may be either because you have a lot + of memory or because the firmware mapped some memory above 1TB for some + reason [1]. + + A user hit this bug because firmware mapped memory above 1TB and provided a + dump so I could reproduce the bug when running makedumpfile on the dump. + + [Regression Potential] + + This commit changes the PMD_SECTION_MASK for arm64. So any regression potential + would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation + from virtual to physical addresses and therefore any regression would happen during + this process. + + [Other] + + [1] + https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b + + When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section arr
[Kernel-packages] [Bug 1879680] Re: Elantech PS/2 [ACPI/ETD0449] Touchpad not detected on Wortmann 1460p
** Summary changed: - Touchpad not detected on Wortmann 1460p + Elantech PS/2 [ACPI/ETD0449] Touchpad not detected on Wortmann 1460p -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879680 Title: Elantech PS/2 [ACPI/ETD0449] Touchpad not detected on Wortmann 1460p Status in linux package in Ubuntu: Incomplete Bug description: The Touchpad is not detected on any Ubuntu Live or installed Version from 16.04 to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabi 1399 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 12:52:57 2020 InstallationDate: Installed on 2020-05-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Wortmann_AG 1220615;1470142 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgubuntu-root ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 52.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: A35 dmi.board.vendor: EA dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: EA dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr52.10:bd06/01/2018:svnWortmann_AG:pn1220615;1470142:pvr1460P;1470142:rvnEA:rnA35:rvrType2-BoardVersion:cvnEA:ct10:cvrChassisVersion: dmi.product.family: NB-TERRA;MOBILE-B;14 dmi.product.name: 1220615;1470142 dmi.product.sku: 4039407048694 dmi.product.version: 1460P;1470142 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881214] Re: syslog and kern.log grow endlessly - related to channel switch, Intel wifi?
syslog and kern.log grew until the filesystem was full. This happened twice. It can be replicated. My workaround is to regress to 19.10. I have a system on 20.04 that does not use wireless and there is no error. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881214 Title: syslog and kern.log grow endlessly - related to channel switch, Intel wifi? Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu Mate 20.04, with all supplied kernels up to 5.4.0.33 I occasionally see a message on my screen that disk space is low. I try rebooting since my computer is unresponsive. Normal reboot does not work, sudo reboot does not work. I have to power off the machine using power button. Machine boots but hangs because its trying to repair journal info. I can't see what causes that since I was not using my computer at the time. edit: see comment #14 So with a live session, I can see that syslog and kern.log files have grown to several GB until the drive is full. When using an upstream kernel 5.4.43-050443-generic x86_64, I haven't had any problem so far. edit: not true actually, this happened again using this upstream kernel. Never had this issue with previous Ubuntu versions with the very same hardware configuration, since 16.04. Included: partial syslog and kern.log with the same message repeated over and over. edit: and when the event starts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867900] Re: CPU stress test fails with focal kernel
Email exchange with Yekai and I am told hisi_sec2 only support 2 threads in default. We can enable more threads when modprobe. I will try to find out the best way to enable more threads as default. ubuntu@kreiken:~$ sudo modprobe -r hisi_sec2 ubuntu@kreiken:~$ sudo modprobe hisi_sec2 ctx_q_num=2 pf_q_num=1024 ubuntu@kreiken:~$ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz --times --af-alg 0 stress-ng: info: [29055] dispatching hogs: 128 af-alg stress-ng: info: [29055] successful run completed in 330.18s (5 mins, 30.18 secs) stress-ng: info: [29055] stressor bogo ops real time usr time sys time bogo ops/s bogo ops/s stress-ng: info: [29055] (secs)(secs)(secs) (real time) (usr+sys time) stress-ng: info: [29055] af-alg111959371330.08299.71 10668.10 339193.31 10208.00 stress-ng: info: [29055] thermal zone temperatures not available stress-ng: info: [29055] for a 330.18s run time: stress-ng: info: [29055] 42263.02s available CPU time stress-ng: info: [29055] 300.36s user time ( 0.71%) stress-ng: info: [29055] 10668.78s system time ( 25.24%) stress-ng: info: [29055] 10969.14s total time ( 25.95%) stress-ng: info: [29055] load average: 138.79 94.92 43.18 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867900 Title: CPU stress test fails with focal kernel Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] We have several crypto accelerators for Hisilicon 1620 but unfortunately one of them is not mature and causes stress-ng tests failure. Disabling hisi_sec2 makes kernel to run crypto functions without accelerator. [Fix] Disable CONFIG_CRYPTO_DEV_HISI_SEC2 temporarily until we have proper driver. [Test] $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz --times --af-alg 0 $ echo $? [Regression Potential] This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other platform. == [Bug Description] CPU stress test fails with focal kernel [Steps to Reproduce] 1) sudo apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable 2) sudo apt-add-repository -y ppa:hardware-certification/public 3) sudo apt install -y canonical-certification-server 4) Install focal kernel debs from https://launchpad.net/ubuntu/+source/linux 5) Run CPU stress test with `sudo certify-advanced` [Actual Results] Failed with stress-ng: fail: [6118] stress-ng-af-alg: bind failed, errno=19 (No such device) [Expected Results] Passed [Reproducibility] 100% [Additional information] Same test with bionic-update kernel passed [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Hi Kai, I edited /etc/modprobe.d/blacklist.conf file adding the following line: # Do not load elan_i2c module blacklist elan_i2c I rebooted the laptop but nothing happened. Touchpad is still unrecognized -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
The fix does not work for me: uname -r 5.4.0-33-generic ournalctl -b0 -u rtkit-daemon -- Logs begin at Wed 2020-04-29 18:57:09 EEST, end at Thu 2020-06-04 18:41:05 EEST. -- Jun 04 18:26:06 n552vw systemd[1]: Starting RealtimeKit Scheduling Policy Service... Jun 04 18:26:06 n552vw systemd[1]: Started RealtimeKit Scheduling Policy Service. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully called chroot. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully dropped privileges. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully limited resources. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Running. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Canary thread running. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Watchdog thread running. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:49 n552vw
[Kernel-packages] [Bug 1882012] Re: Dependency issue for 3.2 linux-lowlatency meta package
Confirmed this is a different source package on precise. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882012 Title: Dependency issue for 3.2 linux-lowlatency meta package Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: When trying to install linux-lowlatency package on Precise 3.2, it will fail with: The following packages have unmet dependencies: linux-lowlatency : Depends: linux-headers-lowlatency (= 3.2.0.82.69) but it is not going to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882012] Re: Dependency issue for 3.2 linux-lowlatency meta package
This is a very old version, present in precise-updates, not the ESM repo. I don't see us producing lowlatency kernels or meta packages on ESM. Was that a different source package that produced those lowlatency packages? It looks to me this is not a regression, or even a problem at all. It should not be a blocker. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882012 Title: Dependency issue for 3.2 linux-lowlatency meta package Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: When trying to install linux-lowlatency package on Precise 3.2, it will fail with: The following packages have unmet dependencies: linux-lowlatency : Depends: linux-headers-lowlatency (= 3.2.0.82.69) but it is not going to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880421] Re: zfsutils-linux fails to install if `modprobe zfs` fails
** Also affects: zfs-linux (Ubuntu Groovy) Importance: Medium Assignee: Colin Ian King (colin-king) Status: In Progress ** Also affects: zfs-linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: zfs-linux (Ubuntu Focal) Status: New => In Progress -- 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/1880421 Title: zfsutils-linux fails to install if `modprobe zfs` fails Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Groovy: In Progress Bug description: Description: When installing zfsutils-linux, failure to `modprobe zfs` cause the package installation to fail. Ideally, modprobe should be attempted but not fatal. Steps to reproduce: # Prevent module loading $ sudo sysctl kernel.modules_disabled=1 # Install the package $ sudo apt install -y zfsutils-linux This should succeed but fails with: Reading package lists... Done Building dependency tree Reading state information... Done zfsutils-linux is already the newest version (0.8.3-1ubuntu12). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up zfsutils-linux (0.8.3-1ubuntu12) ... insmod /lib/modules/5.4.0-31-generic/kernel/zfs/zlua.ko modprobe: ERROR: could not insert 'zfs': Operation not permitted zfs-import-scan.service is a disabled or a static unit, not starting it. A dependency job for zfs-import-cache.service failed. See 'journalctl -xe' for details. Job for zfs-load-module.service failed because the control process exited with error code. See "systemctl status zfs-load-module.service" and "journalctl -xe" for details. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-load-module.service failed because the control process exited with error code. See "systemctl status zfs-load-module.service" and "journalctl -xe" for details. A dependency job for zfs-import-cache.service failed. See 'journalctl -xe' for details. Job for zfs-share.service failed because the control process exited with error code. See "systemctl status zfs-share.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-share, action "start" failed. ● zfs-share.service - ZFS file system shares Loaded: loaded (/lib/systemd/system/zfs-share.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-05-24 16:56:03 UTC; 52ms ago Docs: man:zfs(8) Process: 9283 ExecStartPre=/bin/rm -f /etc/dfs/sharetab (code=exited, status=0/SUCCESS) Process: 9284 ExecStart=/sbin/zfs share -a (code=exited, status=1/FAILURE) Main PID: 9284 (code=exited, status=1/FAILURE) May 24 16:56:03 ocelot systemd[1]: Starting ZFS file system shares... May 24 16:56:03 ocelot zfs[9284]: The ZFS modules are not loaded. May 24 16:56:03 ocelot zfs[9284]: Try running '/sbin/modprobe zfs' as root to load them. May 24 16:56:03 ocelot systemd[1]: zfs-share.service: Main process exited, code=exited, status=1/FAILURE May 24 16:56:03 ocelot systemd[1]: zfs-share.service: Failed with result 'exit-code'. May 24 16:56:03 ocelot systemd[1]: Failed to start ZFS file system shares. dpkg: error processing package zfsutils-linux (--configure): installed zfsutils-linux package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of zfs-zed: zfs-zed depends on zfsutils-linux (>= 0.8.3-1ubuntu12); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-zed (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: zfsutils-linux zfs-zed E: Sub-process /usr/bin/dpkg returned an error code (1) Additional information: $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12 Candidate: 0.8.3-1ubuntu12 Version table: *** 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1880421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1879680] Re: Touchpad not detected on Wortmann 1460p
Here are some Information from the Windows Device-Manager and Eventlog. Am Donnerstag, den 04.06.2020, 09:44 + schrieb Kai-Heng Feng: > Can you please take a screenshot under Windows, shows what the > touchpad > looks like in Device Manager? > ** Attachment added: "elan-touchpad-data.txt" https://bugs.launchpad.net/bugs/1879680/+attachment/5380355/+files/elan-touchpad-data.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/1879680 Title: Touchpad not detected on Wortmann 1460p Status in linux package in Ubuntu: Incomplete Bug description: The Touchpad is not detected on any Ubuntu Live or installed Version from 16.04 to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabi 1399 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 12:52:57 2020 InstallationDate: Installed on 2020-05-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Wortmann_AG 1220615;1470142 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgubuntu-root ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 52.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: A35 dmi.board.vendor: EA dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: EA dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr52.10:bd06/01/2018:svnWortmann_AG:pn1220615;1470142:pvr1460P;1470142:rvnEA:rnA35:rvrType2-BoardVersion:cvnEA:ct10:cvrChassisVersion: dmi.product.family: NB-TERRA;MOBILE-B;14 dmi.product.name: 1220615;1470142 dmi.product.sku: 4039407048694 dmi.product.version: 1460P;1470142 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867900] Re: CPU stress test fails with focal kernel
** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Groovy) Status: Incomplete => 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/1867900 Title: CPU stress test fails with focal kernel Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] We have several crypto accelerators for Hisilicon 1620 but unfortunately one of them is not mature and causes stress-ng tests failure. Disabling hisi_sec2 makes kernel to run crypto functions without accelerator. [Fix] Disable CONFIG_CRYPTO_DEV_HISI_SEC2 temporarily until we have proper driver. [Test] $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz --times --af-alg 0 $ echo $? [Regression Potential] This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other platform. == [Bug Description] CPU stress test fails with focal kernel [Steps to Reproduce] 1) sudo apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable 2) sudo apt-add-repository -y ppa:hardware-certification/public 3) sudo apt install -y canonical-certification-server 4) Install focal kernel debs from https://launchpad.net/ubuntu/+source/linux 5) Run CPU stress test with `sudo certify-advanced` [Actual Results] Failed with stress-ng: fail: [6118] stress-ng-af-alg: bind failed, errno=19 (No such device) [Expected Results] Passed [Reproducibility] 100% [Additional information] Same test with bionic-update kernel passed [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
** Tags removed: rls-gg-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
New
Status in grub2 package in Ubuntu:
Won't Fix
Status in linux-azure package in Ubuntu:
Confirmed
Status in livecd-rootfs package in Ubuntu:
Triaged
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
New
Status in grub2 package in Ubuntu:
Won't Fix
Status in linux-azure package in Ubuntu:
Confirmed
Status in livecd-rootfs package in Ubuntu:
Triaged
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882088] Comment bridged from LTC Bugzilla
--- Comment From stefan.ra...@de.ibm.com 2020-06-04 11:02 EDT--- That's a very valid question. The problem is that we cannot talk about v2 yet for legal reasons. We're pending some internal processing and especially a new RFC on v2. We assume that we get a lot of resistance upstream if we post any code for v2 in absence of an RFC. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882088 Title: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: Description: smc: SMC connections hang with later-level implementations Symptom: Connections from later-level SMC versions to an SMC-enabled server on Linux hang. Problem: Later-level versions of SMC present, although backwards- compatible, a higher version number, and use larger messages during the CLC handshake. Solution: Adjust for tolerating later version numbers, and support CLC messages of arbitrary length. Reproduction: Enable a server on Linux for SMC, and connect using a later- level version of SMC Applicable for: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746613] Re: freezes after resuming from disk hibernation
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746613 Title: freezes after resuming from disk hibernation Status in linux package in Ubuntu: Invalid Bug description: Resuming from disk hibernation works fine with previous kernel 4.10.0-32. Now the computer freezes on a black screen at the end, just after decompressing the image. I am using uswsuspc and s2disk to hibernate successfully with the previous kernel 4.10.-32 Output from lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 Output from uname -r: 4.13.0-32-generic (If I boot with 4.10.0-28-generic from advanced options in grub, resuming works fine) Output from lspci: 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) 04:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57785 Gigabit Ethernet PCIe (rev 10) 04:00.1 SD Host controller: Broadcom Corporation BCM57765/57785 SDXC/MMC Card Reader (rev 10) Please tell me what else can I provide to help with this. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: MATE Date: Wed Jan 31 16:44:27 2018 InstallationDate: Installed on 2018-01-28 (3 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2018-01-28T01:19:21.792226 --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eguerras 2172 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b933b9cf-bad2-4f44-a703-b408e19a611a InstallationDate: Installed on 2018-01-28 (6 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer V5-171 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=4a50e1e8-56d9-413e-9954-5564a31d ro intel_pstate=disable resume=/dev/sda2 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/06/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.08 dmi.modalias: dmi:bvnAcer:bvrV2.08:bd11/06/2012:svnAcer:pnV5-171:pvrV2.08:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.08: dmi.product.family: Type1Family dmi.product.name: V5-171
