[Kernel-packages] [Bug 1935728] Re: [radeon] Mouse pointer randomly disappears - other mouse operations still work
Also occurred on GNOME (I think this was on wayland also) unity was limited functionality so didn't try for too long. Any other suggestions? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935728 Title: [radeon] Mouse pointer randomly disappears - other mouse operations still work Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: The mouse pointer randomly dissappears (same behavior in ubuntu 20.04 LTS and ubuntu 20.10). When this occurs all other mouse operations still function - left/right click - scroll wheel - mouse position still moves Just the actual mouse pointer not visible. Only way to resolve is to restart the machine. Tried numerous ways to restart the mouse driver but nothing else successful ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 14:45:22 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6] InstallationDate: Installed on 2021-07-05 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Apple Inc. iMac10,1 ProcKernelCmdLine: ro root=UUID=30ee9195-f382-4721-8655-6933b38f1842 initrd=boot\initrd.img-5.8.0-59-generic SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 215.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F2268DC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268DC8 dmi.modalias: dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268DC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268DC8: dmi.product.family: Mac dmi.product.name: iMac10,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935728/+subscriptions -- Mailing list: https://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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Em segunda-feira, 12 de julho de 2021, às 15:12:19 -03, Alex Deucher escreveu: > Does the latest firmware in the firmware git tree help? > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.g > it/log/amdgpu I updated the picasso* files from commit: d79c26779d45 amdgpu: update vcn firmware for green sardine for 21.20 And I still see the issue. It took a while to reproduce: I updated the firmware (and ran `update-initramfs -u -k all` to get it into the initramfs) on July 12 and had the laptop turned on since then (closing the lid to put it to sleep), and today I saw the problem again. The full dmesg is attached. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1928393/+attachment/5511525/+files/dmesg.log -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881319] Re: [Lenovo IdeaPad 5 15ARE05] Touchpad not recognized
Lenovo IdeaPad 5 15ARE05 - Processor: AMD® Ryzen 7 4700u with radeon graphics × 8 - OS: Ubuntu 21.04 - GNOME: 3.38.5 - Kernel: 5.11.0-22-generic Main issues: * Touchpad is not working. * Finger-print is not working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: [Lenovo IdeaPad 5 15ARE05] Touchpad not recognized Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all 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/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 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: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1936295 Title: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate the FW bug Status in linux package in Ubuntu: Confirmed Bug description: *Problem description:* On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. Currently, the Trackpoint is barely usable and it's impossible to productively work using it. For a long while, Elantech has not yet put forward (nor confirmed) a firmware update. However, there is a Linux kernel patch mitigating the firmware bug. The kernel bugfix discards the wrongly reported packages by the Elantech hardware. This solves the problem for the user. *Solution:* Please apply existing kernel patch here. https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux Kernel.org Bugzilla https://bugzilla.kernel.org/attachment.cgi?id=295733&action=diff Diff of bugfix *T14s and X13 are Ubuntu certified:* The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this hardware issue has slipped the Ubuntu certification process! https://ubuntu.com/certified/202006-27978 and https://ubuntu.com/certified/202006-27979 *Further information:* https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo employee MarkRHPearson *My System:* Lenovo Thinkpad T14s (AMD) 20ujs00k00 Ubuntu 21.04 and 20.04 see entries in kernel.org bugzilla for logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936688] Re: Hirsute update: upstream stable patchset 2021-07-16
** Description changed: 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 2021-07-16 + + Ported from the following upstream stable releases: + v5.10.45, v5.12.12 + v5.10.46, v5.12.13 + from git://git.kernel.org/ net: ieee802154: fix null deref in parse dev addr HID: quirks: Set INCREMENT_USAGE_ON_DUPLICATE for Saitek X65 HID: a4tech: use A4_2WHEEL_MOUSE_HACK_B8 for A4TECH NB-95 HID: hid-input: add mapping for emoji picker key HID: hid-sensor-hub: Return error for hid_set_field() failure HID: quirks: Add quirk for Lenovo optical mouse HID: multitouch: set Stylus suffix for Stylus-application devices, too HID: Add BUS_VIRTUAL to hid_connect logging HID: usbhid: fix info leak in hid_submit_ctrl drm/tegra: sor: Do not leak runtime PM reference gpu: host1x: Split up client initalization and registration drm/tegra: sor: Fully initialize SOR before registration ARM: OMAP1: Fix use of possibly uninitialized irq variable ARM: OMAP2+: Fix build warning when mmc_omap is not built gfs2: Prevent direct-I/O write fallback errors from getting lost gfs2: fix a deadlock on withdraw-during-mount HID: gt683r: add missing MODULE_DEVICE_TABLE riscv: Use -mno-relax when using lld linker gfs2: Fix use-after-free in gfs2_glock_shrink_scan scsi: target: core: Fix warning on realtime kernels ethernet: myri10ge: Fix missing error code in myri10ge_probe() scsi: qedf: Do not put host in qedf_vport_create() unconditionally Bluetooth: Add a new USB ID for RTL8822CE scsi: scsi_devinfo: Add blacklist entry for HPE OPEN-V nvme-loop: reset queue count to 1 in nvme_loop_destroy_io_queues() nvme-loop: clear NVME_LOOP_Q_LIVE when nvme_loop_configure_admin_queue() fails nvme-loop: check for NVME_LOOP_Q_LIVE in nvme_loop_destroy_admin_queue() nvme-loop: do not warn for deleted controllers during reset net: ipconfig: Don't override command-line hostnames or domains drm/amd/display: Allow bandwidth validation for 0 streams. drm/amdgpu: refine amdgpu_fru_get_product_info drm/amd/display: Fix potential memory leak in DMUB hw_init drm/amd/amdgpu:save psp ring wptr to avoid attack rtnetlink: Fix missing error code in rtnl_bridge_notify() net/x25: Return the correct errno code net: Return the correct errno code fib: Return the correct errno code HID: asus: Filter keyboard EC for old ROG keyboard HID: quirks: Add HID_QUIRK_NO_INIT_REPORTS quirk for Dell K15A keyboard-dock HID: asus: filter G713/G733 key event to prevent shutdown hwmon/pmbus: (q54sj108a2) The PMBUS_MFR_ID is actually 6 chars instead of 5 gfs2: Clean up revokes on normal withdraws HID: intel-ish-hid: ipc: Add Alder Lake device IDs ALSA: hda: Add AlderLake-M PCI ID UBUNTU: upstream stable to v5.10.45, v5.12.12 dmaengine: idxd: add missing dsa driver unregister dmaengine: fsl-dpaa2-qdma: Fix error return code in two functions dmaengine: xilinx: dpdma: initialize registers before request_irq dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM dmaengine: SF_PDMA depends on HAS_IOMEM dmaengine: stedma40: add missing iounmap() on error in d40_probe() afs: Fix an IS_ERR() vs NULL check mm/memory-failure: make sure wait for page writeback in memory_failure kvm: LAPIC: Restore guard to prevent illegal APIC register access fanotify: fix copy_event_to_user() fid error clean up batman-adv: Avoid WARN_ON timing related checks mac80211: fix skb length check in ieee80211_scan_rx() mlxsw: reg: Spectrum-3: Enforce lowest max-shaper burst size of 11 mlxsw: core: Set thermal zone polling delay argument to real value at init libbpf: Fixes incorrect rx_ring_setup_done net: ipv4: fix memory leak in netlbl_cipsov4_add_std vrf: fix maximum MTU net: rds: fix memory leak in rds_recvmsg net: dsa: felix: re-enable TX flow control in ocelot_port_flush() net: lantiq: disable interrupt before sheduling NAPI netfilter: nft_fib_ipv6: skip ipv6 packets from any to link-local ice: add ndo_bpf callback for safe mode netdev ops ice: parameterize functions responsible for Tx ring management udp: fix race between close() and udp_abort() rtnetlink: Fix regression in bridge VLAN configuration net/sched: act_ct: handle DNAT tuple collision net/mlx5e: Remove dependency in IPsec initialization flows net/mlx5e: Fix page reclaim for dead peer hairpin net/mlx5: Consider RoCE cap before init RDMA resources net/mlx5: DR, Allow
[Kernel-packages] [Bug 1936688] Re: Hirsute update: upstream stable patchset 2021-07-16
** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - 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: - 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 2021-07-16 + from git://git.kernel.org/ -upstream stable patchset 2021-07-16 -from git://git.kernel.org/ + net: ieee802154: fix null deref in parse dev addr + HID: quirks: Set INCREMENT_USAGE_ON_DUPLICATE for Saitek X65 + HID: a4tech: use A4_2WHEEL_MOUSE_HACK_B8 for A4TECH NB-95 + HID: hid-input: add mapping for emoji picker key + HID: hid-sensor-hub: Return error for hid_set_field() failure + HID: quirks: Add quirk for Lenovo optical mouse + HID: multitouch: set Stylus suffix for Stylus-application devices, too + HID: Add BUS_VIRTUAL to hid_connect logging + HID: usbhid: fix info leak in hid_submit_ctrl + drm/tegra: sor: Do not leak runtime PM reference + gpu: host1x: Split up client initalization and registration + drm/tegra: sor: Fully initialize SOR before registration + ARM: OMAP1: Fix use of possibly uninitialized irq variable + ARM: OMAP2+: Fix build warning when mmc_omap is not built + gfs2: Prevent direct-I/O write fallback errors from getting lost + gfs2: fix a deadlock on withdraw-during-mount + HID: gt683r: add missing MODULE_DEVICE_TABLE + riscv: Use -mno-relax when using lld linker + gfs2: Fix use-after-free in gfs2_glock_shrink_scan + scsi: target: core: Fix warning on realtime kernels + ethernet: myri10ge: Fix missing error code in myri10ge_probe() + scsi: qedf: Do not put host in qedf_vport_create() unconditionally + Bluetooth: Add a new USB ID for RTL8822CE + scsi: scsi_devinfo: Add blacklist entry for HPE OPEN-V + nvme-loop: reset queue count to 1 in nvme_loop_destroy_io_queues() + nvme-loop: clear NVME_LOOP_Q_LIVE when nvme_loop_configure_admin_queue() fails + nvme-loop: check for NVME_LOOP_Q_LIVE in nvme_loop_destroy_admin_queue() + nvme-loop: do not warn for deleted controllers during reset + net: ipconfig: Don't override command-line hostnames or domains + drm/amd/display: Allow bandwidth validation for 0 streams. + drm/amdgpu: refine amdgpu_fru_get_product_info + drm/amd/display: Fix potential memory leak in DMUB hw_init + drm/amd/amdgpu:save psp ring wptr to avoid attack + rtnetlink: Fix missing error code in rtnl_bridge_notify() + net/x25: Return the correct errno code + net: Return the correct errno code + fib: Return the correct errno code + HID: asus: Filter keyboard EC for old ROG keyboard + HID: quirks: Add HID_QUIRK_NO_INIT_REPORTS quirk for Dell K15A keyboard-dock + HID: asus: filter G713/G733 key event to prevent shutdown + hwmon/pmbus: (q54sj108a2) The PMBUS_MFR_ID is actually 6 chars instead of 5 + gfs2: Clean up revokes on normal withdraws + HID: intel-ish-hid: ipc: Add Alder Lake device IDs + ALSA: hda: Add AlderLake-M PCI ID + UBUNTU: upstream stable to v5.10.45, v5.12.12 + dmaengine: idxd: add missing dsa driver unregister + dmaengine: fsl-dpaa2-qdma: Fix error return code in two functions + dmaengine: xilinx: dpdma: initialize registers before request_irq + dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM + dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM + dmaengine: SF_PDMA depends on HAS_IOMEM + dmaengine: stedma40: add missing iounmap() on error in d40_probe() + afs: Fix an IS_ERR() vs NULL check + mm/memory-failure: make sure wait for page writeback in memory_failure + kvm: LAPIC: Restore guard to prevent illegal APIC register access + fanotify: fix copy_event_to_user() fid error clean up + batman-adv: Avoid WARN_ON timing related checks + mac80211: fix skb length check in ieee80211_scan_rx() + mlxsw: reg: Spectrum-3: Enforce lowest max-shaper burst size of 11 + mlxsw: core: Set thermal zone polling delay argument to real value at init + libbpf: Fixes incorrect rx_ring_setup_done + net: ipv4: fix memory leak in netlbl_cipsov4_add_std + vrf: fix maximum MTU + ne
[Kernel-packages] [Bug 1890848] Re: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
>From the commits mentioned that solve the issue, 338d0be437ef was not
available on 4.15 kernels. The cherry-pick was submitted to the kernel
team for approval.
** Description changed:
- Per 'man namespaces':
+ SRU Justification:
- "Permission to dereference or read (readlink(2)) these symbolic links is
- governed by a ptrace access mode PTRACE_MODE_READ_FSCREDS check; see
+ [Impact]
+ Permission 'ptrace trace' is required to readlink() /proc/*/ns/*, when
+ only 'ptrace read' should be required according to 'man namespaces':
+
+ "Permission to dereference or read (readlink(2)) these symbolic links
+ is governed by a ptrace access mode PTRACE_MODE_READ_FSCREDS check; see
ptrace(2)."
- This suggests that a 'ptrace read' rule should be sufficient to
- readlink() /proc/*/ns/*, which is the case with 5.4.0-42.46-generic
- (Ubuntu 20.04 LTS).
+ [Fix]
- However, on Ubuntu 18.04 LTS and 16.04 LTS, 'ptrace trace' is needed.
- Here is a reproducer:
+ Upstream commit 338d0be437ef10e247a35aed83dbab182cf406a2 fixes ptrace
+ read check.
- $ cat ./readlink-ns.c
- #include
- #include
- #include
- #include
- #include
- #include
- #include
+ [Test Plan]
- void usage() {
- fprintf(stderr, "Usage: readlink-ns -p -n \n");
- }
+ BugLink contains the source of a binary that reproduces the issue. In
+ summary, it executes readlink() on /proc/*/ns/*. There's also a policy
+ that has only 'ptrace read' permission. When the bug is fixed,
+ execution is allowed.
- int main(int argc, char *argv[])
- {
- pid_t pid = 0;
- char *ns = NULL;
- char path[PATH_MAX] = {};
- char rpath[PATH_MAX] = {};
- int c;
+ [Where problems could occur]
- while ((c = getopt(argc, argv, "hn:p:")) != -1) {
- switch(c) {
- case 'n':
- ns = optarg;
- break;
- case 'p':
- pid = atoi(optarg);
- break;
- case 'h':
- usage();
- return 0;
- case '?':
- usage();
- return 1;
- default:
- return 1;
- }
- }
-
- int n = snprintf(path, sizeof(path), "/proc/%d/ns/%s", pid, ns);
- if (n < 0 || (size_t)n >= sizeof(path)) {
- fprintf(stderr, "cannot format string\n");
- return 1;
- }
- path[n] = '\0';
- printf("path: %s\n", path);
-
- n = readlink(path, rpath, sizeof(rpath));
- if (n < 0) {
- perror("readlink()");
- return 1;
- } else if (n == sizeof(rpath)) {
- fprintf(stderr, "cannot readlink()\n");
- return 1;
- }
- printf("rpath: %s\n", rpath);
-
- return 0;
- }
-
- $ cat ./readlink-ns.apparmor
- #include
-
- profile test {
- #include
-
- # focal
- ptrace (read) peer="unconfined",
-
- # xenial, bionic
- #ptrace (trace) peer="unconfined",
- }
-
-
- # bionic and xenial need 'ptrace trace'
- $ gcc ./readlink-ns.c && sudo apparmor_parser -r ./readlink-ns.apparmor &&
sudo aa-exec -p test -- ./a.out -p 1 -n pid
- path: /proc/1/ns/pid
- readlink(): Permission denied
-
- Denial:
- Aug 07 14:40:59 sec-bionic-amd64 kernel: audit: type=1400
audit(1596829259.675:872): apparmor="DENIED" operation="ptrace" profile="test"
pid=1311 comm="a.out" requested_mask="trace" denied_mask="trace"
peer="unconfined"
-
-
- # focal needs only 'ptrace read'
- $ gcc ./readlink-ns.c && sudo apparmor_parser -r ./readlink-ns.apparmor &&
sudo aa-exec -p test -- ./a.out -p 1 -n pid
- path: /proc/1/ns/pid
- rpath: pid:[4026531836]
+ The regression can be considered as low, since it's lowering the number
+ of permissions required. Existing policies that already contain the
+ permission 'ptrace trace' and 'ptrace read' will have a broader policy
+ than required.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890848
Title:
'ptrace trace' needed to readlink() /proc/*/ns/* files on older
kernels
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
SRU Justification:
[Impact]
Permission 'ptrace trace' is required to readlink() /proc/*/ns/*, when
only 'ptrace read' should be required according to 'man namespaces':
"Permission to dereference or read (readlink(2)) these symbolic links
is governed by a ptrace access mode PTRACE_MODE_READ_FSCREDS check; see
ptrace(2)."
[Fix]
Upstream commit 338d0be437ef10e247a35aed83dbab182cf406a2 fixes ptrace
read check.
[Test Plan]
BugLink contains the source of a
[Kernel-packages] [Bug 1936688] [NEW] Hirsute update: upstream stable patchset 2021-07-16
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 2021-07-16 from git://git.kernel.org/ net: ieee802154: fix null deref in parse dev addr HID: quirks: Set INCREMENT_USAGE_ON_DUPLICATE for Saitek X65 HID: a4tech: use A4_2WHEEL_MOUSE_HACK_B8 for A4TECH NB-95 HID: hid-input: add mapping for emoji picker key HID: hid-sensor-hub: Return error for hid_set_field() failure HID: quirks: Add quirk for Lenovo optical mouse HID: multitouch: set Stylus suffix for Stylus-application devices, too HID: Add BUS_VIRTUAL to hid_connect logging HID: usbhid: fix info leak in hid_submit_ctrl drm/tegra: sor: Do not leak runtime PM reference gpu: host1x: Split up client initalization and registration drm/tegra: sor: Fully initialize SOR before registration ARM: OMAP1: Fix use of possibly uninitialized irq variable ARM: OMAP2+: Fix build warning when mmc_omap is not built gfs2: Prevent direct-I/O write fallback errors from getting lost gfs2: fix a deadlock on withdraw-during-mount HID: gt683r: add missing MODULE_DEVICE_TABLE riscv: Use -mno-relax when using lld linker gfs2: Fix use-after-free in gfs2_glock_shrink_scan scsi: target: core: Fix warning on realtime kernels ethernet: myri10ge: Fix missing error code in myri10ge_probe() scsi: qedf: Do not put host in qedf_vport_create() unconditionally Bluetooth: Add a new USB ID for RTL8822CE scsi: scsi_devinfo: Add blacklist entry for HPE OPEN-V nvme-loop: reset queue count to 1 in nvme_loop_destroy_io_queues() nvme-loop: clear NVME_LOOP_Q_LIVE when nvme_loop_configure_admin_queue() fails nvme-loop: check for NVME_LOOP_Q_LIVE in nvme_loop_destroy_admin_queue() nvme-loop: do not warn for deleted controllers during reset net: ipconfig: Don't override command-line hostnames or domains drm/amd/display: Allow bandwidth validation for 0 streams. drm/amdgpu: refine amdgpu_fru_get_product_info drm/amd/display: Fix potential memory leak in DMUB hw_init drm/amd/amdgpu:save psp ring wptr to avoid attack rtnetlink: Fix missing error code in rtnl_bridge_notify() net/x25: Return the correct errno code net: Return the correct errno code fib: Return the correct errno code HID: asus: Filter keyboard EC for old ROG keyboard HID: quirks: Add HID_QUIRK_NO_INIT_REPORTS quirk for Dell K15A keyboard-dock HID: asus: filter G713/G733 key event to prevent shutdown hwmon/pmbus: (q54sj108a2) The PMBUS_MFR_ID is actually 6 chars instead of 5 gfs2: Clean up revokes on normal withdraws HID: intel-ish-hid: ipc: Add Alder Lake device IDs ALSA: hda: Add AlderLake-M PCI ID UBUNTU: upstream stable to v5.10.45, v5.12.12 dmaengine: idxd: add missing dsa driver unregister dmaengine: fsl-dpaa2-qdma: Fix error return code in two functions dmaengine: xilinx: dpdma: initialize registers before request_irq dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM dmaengine: SF_PDMA depends on HAS_IOMEM dmaengine: stedma40: add missing iounmap() on error in d40_probe() afs: Fix an IS_ERR() vs NULL check mm/memory-failure: make sure wait for page writeback in memory_failure kvm: LAPIC: Restore guard to prevent illegal APIC register access fanotify: fix copy_event_to_user() fid error clean up batman-adv: Avoid WARN_ON timing related checks mac80211: fix skb length check in ieee80211_scan_rx() mlxsw: reg: Spectrum-3: Enforce lowest max-shaper burst size of 11 mlxsw: core: Set thermal zone polling delay argument to real value at init libbpf: Fixes incorrect rx_ring_setup_done net: ipv4: fix memory leak in netlbl_cipsov4_add_std vrf: fix maximum MTU net: rds: fix memory leak in rds_recvmsg net: dsa: felix: re-enable TX flow control in ocelot_port_flush() net: lantiq: disable interrupt before sheduling NAPI netfilter: nft_fib_ipv6: skip ipv6 packets from any to link-local ice: add ndo_bpf callback for safe mode netdev ops ice: parameterize functions responsible for Tx ring management udp: fix race between close() and udp_abort() rtnetlink: Fix regression in bridge VLAN configuration net/sched: act_ct: handle DNAT tuple collision net/mlx5e: Remove dependency in IPsec initialization flows net/mlx5e: Fix page reclaim for dead peer hairpin net/mlx5: Consider RoCE cap before init RDMA resources net/mlx5: DR, Allow SW steering for sw_owner_v2 devices net/mlx5: DR, Don't use SW steering when RoCE is not supported net/mlx5e: Block offload of outer header csum for UDP tunnels netfilter: synproxy: Fix out of bounds when parsing TCP options mptcp: Fix out of bounds when parsing TCP options sch_cake: Fix out of bounds when parsing TCP options and header mptcp:
[Kernel-packages] [Bug 1935951] Re: [nvidia] HomeOffice & Un-/Docking: X11 crash on resume when docked to multi monitor
Just an update:
I can reproduce this problem with Ubuntu 20.04, stock Gnome and latest
NVidia beta driver 470.42.01 as suggested by X11 maintainers.
Gnome doesn't crash, but just restarts the desktop.
The var/crash folder is also empty, and EnterVT errors are printed in
syslog
I posted at NVIDIA the issue:
https://forums.developer.nvidia.com/t/linux-for-homeoffice-docking-undocking-produces-ee-nvidia-0-failed-to-enter-vt-mode-initialization-failed/183481/2
I observed, that when the monitors and dockingstations are powercycled,
the sporadic desktop crash on resume ahppens almost every 2nd time.
MIght be the monitors just need just more time the be ready for
X11/nvidia??
** Attachment added: "desktopcrash_after_resume.2_nvidia470_beta.zip"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1935951/+attachment/5511468/+files/desktopcrash_after_resume.2_nvidia470_beta.zip
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1935951
Title:
[nvidia] HomeOffice & Un-/Docking: X11 crash on resume when docked to
multi monitor
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Incomplete
Bug description:
X11 crashes on resume and my current desktop is lost and the login
manager appears.
I posted a bugreported here
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1197
with configu details.
But it seems to be nvidia, but may be a workaround is possible in Ubuntu?
This bug prevents me to use Linux for daily docking /undocking cycles for
HomeOffice (works fine with Windows).
[ 1272.639] (II) NVIDIA(0): Setting mode "DP-4: nvidia-auto-select
@1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[ 1272.639] (WW) NVIDIA(0): Failed to set the display configuration
[ 1272.639] (WW) NVIDIA(0): - Setting a mode on head 1 failed: Invalid
surface parameters
[ 1272.639] (WW) NVIDIA(0): were specified
[ 1272.639] (EE) NVIDIA(0): Failed to enter VT (mode initialization failed)
[ 1272.639] (EE)
Fatal server error:
[ 1272.639] (EE) EnterVT failed for screen 0
[ 1272.639] (EE)
[ 1272.639] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 1272.639] (EE) Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
[ 1272.639] (EE)
[ 1274.034] (EE) Server terminated with error (1). Closing log file.
I found something similar which could handle the EnterVT failed issue:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/
but I am not sure if it is already in Ubuntu 20.04 LTS
Hardware:
Hardware used:
Dell Precision 15" 7540, Xeon E-2286M@2.4GHz, 128 GB ECC RAM, NVIDIA Quadro
RTX 5000 16GB VRAM
Dockingstations at Home and Offices: WD19DC (240W)
Monitors used for Linux migration Office1: 2x 4K U4320Q, 42.5" @ 96dpi font /
No scaling a
Monitors used for Linux migration Office2: 2xU3818DW, 37.5"
Monitors used for Linux migration at home: 3x FullHD Dell monitors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1935951/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909814] Re: Keyboard not working
Yeah, it's really nice that the responsible kernel & distro people picked up the fix that soon. According to the kernel Changelogs, it's in v5.4.132, v5.10.50, v5.12.17 and v5.13.2 and upcoming 5.14. I also want to thank you all again for helping to find courage and a way on how to get this done and a little lucky testing fortune! Let's hope there won't be drawbacks for other machines. Cheers ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936682] [NEW] Fix kernel panic caused by legacy devices on AMD platforms
Public bug reported: [Impact] When a legacy device is only 32bit DMA capable and it's in the same IOMMU group with iommu_v2 capable devices, the device in question will be forced to use identity mapping and triggers kernel panic on DMA operation because it can't do 64bit DMA. [Fix] Keep swiotlb enabled so legacy devices can do 64bit DMA. This is also how Intel and ARM64 platforms deal with legacy devices. [Test] Boot an affected system. Kernel panic in Realtek WiFi driver's probe routine. After the patch is applied, the system can work normally. [Where problems could occur] The default swiotlb uses 64MB memory, so if the system doesn't have any legacy device, there are 64MB ram less for the system to use. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: High Status: Confirmed ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: High Status: Confirmed ** Affects: linux (Ubuntu Hirsute) Importance: High Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Impish) Importance: High Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1933798 stella ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Tags added: oem-priority originate-from-1933798 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936682 Title: Fix kernel panic caused by legacy devices on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] When a legacy device is only 32bit DMA capable and it's in the same IOMMU group with iommu_v2 capable devices, the device in question will be forced to use identity mapping and triggers kernel panic on DMA operation because it can't do 64bit DMA. [Fix] Keep swiotlb enabled so legacy devices can do 64bit DMA. This is also how Intel and ARM64 platforms deal with legacy devices. [Test] Boot an affected system. Kernel panic in Realtek WiFi driver's probe routine. After the patch is applied, the system can work normally. [Where problems could occur] The default swiotlb uses 64MB memory, so if the system
[Kernel-packages] [Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
Observed in B/aws-fips (kernel 4.15), cycle sru-20210621. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1866323 Title: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem-5.6 source package in Bionic: New Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Confirmed Bug description: Test failure in fallocate06 was composed by two issues, one is xfs fill_fs test issue addressed in bug 1865967. Another is this one, this is the case 2 of btrfs (fill_fs): tst_test.c:1290: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2 This issue can be found from X to F X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/ B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/ D - https://pastebin.ubuntu.com/p/cryTnnn5wF/ E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/ F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/ Note that the hint printed in the test: HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e It something that will get printed after the test, as it's for XFS so it has nothing to do with this issue here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876684] Re: fanotify09 case 3 (Events on files and dirs with both inode and mount marks) from ubuntu_ltp_syscalls failed
Observed in B/aws-fips (kernel 4.15), cycle sru-20210621. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876684 Title: fanotify09 case 3 (Events on files and dirs with both inode and mount marks) from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is a new test case added 7 days ago [1] Test failed on Focal 5.4.0-29.33 with: fanotify09.c:150: FAIL: group 1 got event: mask 10 pid=41059 fd=24 path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint fanotify09.c:150: FAIL: group 2 got event: mask 10 pid=41059 fd=24 path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint [1] https://github.com/linux-test-project/ltp/commit/70ca1e8806d227d47c6801262d3f7983652159a4#diff-234c27c769cf07468a81748a0e7330dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1876684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923284] Re: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic
Observed in B/aws-fips (kernel 4.15), cycle sru-20210621. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923284 Title: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test fails with timeout on Bionic 4.15.0-141.145 host rizzo this failed on the previous version of bionic 4.15.0-140.144 as well, so not a regression. vmx_host_state_area has an error before giving timeout: 04/10 01:29:18 DEBUG| utils:0153| [stderr] KVM: entry failed, hardware error 0x8021 04/10 01:29:18 DEBUG| utils:0153| [stderr] 04/10 01:29:18 DEBUG| utils:0153| [stderr] If you're running a guest on an Intel machine without unrestricted mode 04/10 01:29:18 DEBUG| utils:0153| [stderr] support, the failure can be most likely due to the guest entering an invalid 04/10 01:29:18 DEBUG| utils:0153| [stderr] state for Intel VT. For example, the guest maybe running in big real mode 04/10 01:29:18 DEBUG| utils:0153| [stderr] which is not supported on less recent Intel processors. 04/10 01:29:18 DEBUG| utils:0153| [stderr] 04/10 01:29:47 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 21956 (timeout) 04/10 01:29:47 DEBUG| utils:0153| [stdout] FAIL vmx_host_state_area (timeout; duration=30) vmx_intr_window_test / vmx_nmi_window_test shows passing until the timeout: 28. 04/10 01:29:49 DEBUG| utils:0153| [stdout] PASS: interrupt-window: active, RFLAGS.IF = 0: Activity state (0) is 'ACTIVE' 29. 04/10 01:30:19 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22161 (timeout) 30. 04/10 01:30:19 DEBUG| utils:0153| [stdout] FAIL vmx_intr_window_test (timeout; duration=30) 31. 04/10 01:30:19 ERROR| test:0414| Exception escaping from test: -- 26. 04/10 01:30:24 DEBUG| utils:0153| [stdout] PASS: NMI-window: active, blocking by NMI: #UD handler executed once (actual 1 times) 27. 04/10 01:30:53 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22570 (timeout) 28. 04/10 01:30:53 DEBUG| utils:0153| [stdout] FAIL vmx_nmi_window_test (timeout; duration=30) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918692] Re: ubuntu-kvm-unit-test/vmx_apic_passthrough_thread reports assertion failure
Observed in B/aws-fips (kernel 4.15), cycle sru-20210621. ** Tags added: fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918692 Title: ubuntu-kvm-unit-test/vmx_apic_passthrough_thread reports assertion failure Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: Running the ubuntu_kvm_unit_test/vmx_apic_passthrough_thread subtest on rumford shows the following failure: 14. 03/03 06:44:40 DEBUG| utils:0153| [stdout] Test suite: vmx_apic_passthrough_thread_test 15. 03/03 06:44:40 DEBUG| utils:0153| [stdout] FAIL: x86/vmx_tests.c:7705: Assertion failed: (0) == ((int)ioapic_read_redir(0xf).remote_irr) 16. 03/03 06:44:40 DEBUG| utils:0153| [stdout] LHS: 00 - ''''''''''''''' - 0 17. 03/03 06:44:40 DEBUG| utils:0153| [stdout] RHS: 0x0001 - '''''''''''''''0001 - 1 18. 03/03 06:44:40 DEBUG| utils:0153| [stdout] IOAPIC pass-through: remote_irr=0 after EOI 19. 03/03 06:44:40 DEBUG| utils:0153| [stdout] STACK: 4083de 40841a 40158a 403a60 400312 20. 03/03 06:44:40 DEBUG| utils:0153| [stdout] SUMMARY: 5 tests, 1 unexpected failures This sounds like some hardware related setup issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1918692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900951] Re: ptrace10 from ubuntu_ltp_syscalls failed on T/X/B
Observed in B/aws-fips (kernel 4.15), cycle sru-20210621. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900951 Title: ptrace10 from ubuntu_ltp_syscalls failed on T/X/B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: Issue found on B-AWS 4.15.0-1087.92 This is a new test case added a week ago [1]. Test failed with: startup='Wed Oct 21 13:10:37 2020' tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s ptrace10.c:60: TFAIL: The rd0 wasn't set on second PTRACE_POKEUSER HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd14406b78e6 Summary: passed 0 failed 1 skipped 0 warnings 0 tag=ptrace10 stime=1603285837 dur=0 exit=exited stat=1 core=no cu=0 cs=0 [1] https://github.com/linux-test- project/ltp/blob/master/testcases/kernel/syscalls/ptrace/ptrace10.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15
Observed in B/aws-fips (kernel 4.15), cycle sru-20210621. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931325 Title: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [Impact] Test case cfs_bandwidth01 in LTP sched test suite is a reproducer of a CFS unthrottle_cfs_rq() issue (fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning). This test triggers a warning on our 4.15 kernel: LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5) [ cut here ] rq->tmp_alone_branch != &rq->leaf_cfs_rq_list WARNING: CPU: 0 PID: 0 at /build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 unthrottle_cfs_rq+0x16f/0x200 Modules linked in: input_leds joydev serio_raw mac_hid qemu_fw_cfg kvm_intel kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse virtio_blk pata_acpi floppy virtio_net i2c_piix4 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic #148-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 RIP: 0010:unthrottle_cfs_rq+0x16f/0x200 RSP: 0018:989ebfc03e80 EFLAGS: 00010082 RAX: RBX: 989eb4c6ac00 RCX: RDX: 0005 RSI: acb63c4d RDI: 0046 RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: acb63c20 R10: R11: 0001 R12: 989eb57fe400 R13: 989ebfc21900 R14: 0001 R15: 0001 FS: () GS:989ebfc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55593258d618 CR3: 7a044000 CR4: 06f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: distribute_cfs_runtime+0xc3/0x110 sched_cfs_period_timer+0xff/0x220 ? sched_cfs_slack_timer+0xd0/0xd0 __hrtimer_run_queues+0xdf/0x230 hrtimer_interrupt+0xa0/0x1d0 smp_apic_timer_interrupt+0x6f/0x140 apic_timer_interrupt+0x90/0xa0 RIP: 0010:native_safe_halt+0x12/0x20 RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: ff11 RAX: abbc9280 RBX: RCX: RDX: RSI: RDI: RBP: ac603e28 R08: 00af39850067 R09: 989e73749d00 R10: R11: 7fff R12: R13: R14: R15: ? __sched_text_end+0x1/0x1 default_idle+0x20/0x100 arch_cpu_idle+0x15/0x20 default_idle_call+0x23/0x30 do_idle+0x172/0x1f0 cpu_startup_entry+0x73/0x80 rest_init+0xae/0xb0 start_kernel+0x4dc/0x500 x86_64_start_reservations+0x24/0x26 x86_64_start_kernel+0x74/0x77 secondary_startup_64+0xa5/0xb0 Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 00 75 5f 31 db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 48 85 db 74 43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00 ---[ end trace b6b9a70bc2945c0c ]--- [Fix] Base on the test case description, we will need these fixes: * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair() Backport needed for Bionic since we're missing some new variables / coding style changes introduced in the following commits (and their corresponding fixes): * 97fb7a0a8944bd sched: Clean up and harmonize the coding style of the scheduler code base * 9f68395333ad7f sched/pelt: Add a new runnable average signal * 6212437f0f6043 sched/fair: Fix runnable_avg for throttled cfs * 43e9f7f231e40e sched/fair: Start tracking SCHED_IDLE tasks count in cfs_rq I have also searched in the upstream tree to see if there is any other commit claim to be a fix of these but didn't see any. [Test] Test kernel can be found here: https://people.canonical.com/~phlin/kernel/lp-1931325-cfs_bandwidth01/ With these patches applied, the test can pass without triggering
[Kernel-packages] [Bug 1928686] Re: Oracle kernel has Android related config options disabled
$ wget https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/unstable/+build/21743664/+files/linux- buildinfo-5.11.0-1012-oracle_5.11.0-1012.12+21.10.1_amd64.deb $ egrep 'ANDROI|ASHMEM' unpack/usr/lib/linux/5.11.0-1012-oracle/config CONFIG_ASHMEM=m CONFIG_ANDROID=y CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1928686 Title: Oracle kernel has Android related config options disabled Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle source package in Bionic: New Status in linux-oracle source package in Focal: Fix Released Status in linux-oracle source package in Groovy: Fix Released Status in linux-oracle source package in Hirsute: Fix Committed Bug description: For Anbox Cloud we require certain CONFIG_ANDROID_* options to be enabled in the kernel. We do this already for most of our cloud kernels (GCE, AWS, Azure) and the generic kernel and should do so for the oracle (and possible others too). We have customers looking at running Anbox Cloud on OCI instances and having the ashmem and binder kernel modules available is a precondition for this to work. The following options are what we need CONFIG_ANDROID=y CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set CONFIG_ASHMEM=m These should be the same across all our kernels where we're going to support Anbox Cloud. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1928686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934709] Re: btrfs: Automatic balance returns -EUCLEAN and leads to forced readonly filesystem
** 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/1934709
Title:
btrfs: Automatic balance returns -EUCLEAN and leads to forced readonly
filesystem
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/1934709
[Impact]
During an automatic balance, users may encounter an error when writing
the transaction log to disk, when the log tree is being parsed, which
forces the filesystem to be remounted read-only and outputs the
following kernel oops:
BTRFS: error (device dm-14) in balance_level:1962: errno=-117 unknown
BTRFS info (device dm-14): forced readonly
BTRFS: Transaction aborted (error -117)
WARNING: CPU: 7 PID: 10818 at
/build/linux-99Rib2/linux-4.15.0/fs/btrfs/tree-log.c:2908
btrfs_sync_log+0xa28/0xbc0 [btrfs]
CPU: 7 PID: 10818 Comm: qemu-system-s39 Tainted: G OE
4.15.0-136-generic #140-Ubuntu
Hardware name: IBM 3907 LR1 A00 (LPAR)
Krnl PSW : 76bc1d64 9cc65255 (btrfs_sync_log+0xa28/0xbc0
[btrfs])
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
Krnl GPRS: 007899a6 0006 0027 0007
03ff801fdd8c 0002394c 0053650a7000 ff8b
00536b7f6000 0053ff8b 0053650a3800 005385935000
00532054de01 005385935290 03ff801fdd8c 004eebb1fae0
Krnl Code: 03ff801fdd80: c022a032 larl%r2,03ff80251de4
03ff801fdd86: c0e5fffb2181 brasl %r14,03ff80162088
#03ff801fdd8c: a7f40001 brc 15,03ff801fdd8e
>03ff801fdd90: e3a0f0a80004 lg %r10,168(%r15)
03ff801fdd96: b9040057 lgr %r5,%r7
03ff801fdd9a: a7490b5c lghi%r4,2908
03ff801fdd9e: b904002a lgr %r2,%r10
03ff801fdda2: c032604f larl%r3,03ff80249e40
Call Trace:
([<03ff801fdd8c>] btrfs_sync_log+0xa24/0xbc0 [btrfs])
[<03ff801c74e2>] btrfs_sync_file+0x3e2/0x550 [btrfs]
[<003ce6ce>] do_fsync+0x5e/0x90
[<003ce9ca>] SyS_fdatasync+0x32/0x48
[<008ffe5c>] system_call+0xd8/0x2c8
Last Breaking-Event-Address:
[<03ff801fdd8c>] btrfs_sync_log+0xa24/0xbc0 [btrfs]
BTRFS: error (device dm-14) in btrfs_sync_log:2908: errno=-117 unknown
BTRFS error (device dm-14): pending csums is 269639680
This bug appears to be linked to bug 1933172, but is different and has
a different root cause. Again, I believe that this is a regression
introduced in the fixing of CVE-2019-19036, from 4.15.0-109-generic.
[Fix]
Analysis of the kernel oops is as follows:
The first thing we see is that BTRFS entered ERROR state with the
reason:
in balance_level:1962: errno=-117 unknown
Now errno -117 is:
100 #define EUCLEAN 117 /* Structure needs cleaning */
btrfs treats -EUCLEAN as if corruption has happened. Let's see where
this is returned from.
If we start at fs/btrfs/ctree.c in balance_level(), line 1962:
1917 static noinline int balance_level(struct btrfs_trans_handle *trans,
1918 struct btrfs_root *root,
1919 struct btrfs_path *path, int level)
1920 {
...
1958 /* promote the child to a root */
1959 child = read_node_slot(fs_info, mid, 0);
1960 if (IS_ERR(child)) {
1961 ret = PTR_ERR(child);
1962 btrfs_handle_fs_error(fs_info, ret, NULL);
1963 goto enospc;
1964 }
...
2136 }
We are in the middle of a balancing operation, and if you happen to be
familiar with how b-tree data structures work, we are promoting a
child node to a topmost root node.
The error most likely happens in read_node_slot(), with the lines
after it printing that an error has happened.
1887 static noinline struct extent_buffer *
1888 read_node_slot(struct btrfs_fs_info *fs_info, struct extent_buffer
*parent,
1889int slot)
1890 {
...
1900 btrfs_node_key_to_cpu(parent, &first_key, slot);
1901 eb = read_tree_block(fs_info, btrfs_node_blockptr(parent, slot),
1902 btrfs_node_ptr_generation(parent, slot),
1903 level - 1, &first_key);
...
1910 }
There are two calls here which are relevant. btrfs_node_key_to_cpu()
and read_tree_block().
Let's look at read_tree_block() in fs/btrfs/disk-io.c:
1147 struct extent_buffer *read_tree_block(struct btrfs_fs_info *fs_info, u64
bytenr,
1148 u64 parent_transid, int level,
1149 struct btrfs_key *first_key)
1150 {
1151
[Kernel-packages] [Bug 1936678] Re: Samsung Laptop support module doesn't load
** Attachment added: "Output from ubuntu-bug linux" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936678/+attachment/5511456/+files/apport.linux-image-5.8.0-59-generic.ck7x5ypx.apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936678 Title: Samsung Laptop support module doesn't load Status in linux package in Ubuntu: New Bug description: This is identical to bug # 1170885, which was filed 2013-04-20. The last comment on that bug was by Kai-Heng Feng (kaihengfeng), who requested a new bug report. This is a Samsung laptop NP730QCJ. $ sudo modprobe samsung-laptop modprobe: ERROR: could not insert 'samsung_laptop': No such device About my system: $ sudo dmidecode | grep -A 2 -i 'base board' Base Board Information Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: NP730QCJ-K01US $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" $ cat /proc/version_signature Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 $ file /sys/firmware/efi/ /sys/firmware/efi/: directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936678] [NEW] Samsung Laptop support module doesn't load
Public bug reported: This is identical to bug # 1170885, which was filed 2013-04-20. The last comment on that bug was by Kai-Heng Feng (kaihengfeng), who requested a new bug report. This is a Samsung laptop NP730QCJ. $ sudo modprobe samsung-laptop modprobe: ERROR: could not insert 'samsung_laptop': No such device About my system: $ sudo dmidecode | grep -A 2 -i 'base board' Base Board Information Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: NP730QCJ-K01US $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" $ cat /proc/version_signature Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 $ file /sys/firmware/efi/ /sys/firmware/efi/: directory ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936678 Title: Samsung Laptop support module doesn't load Status in linux package in Ubuntu: New Bug description: This is identical to bug # 1170885, which was filed 2013-04-20. The last comment on that bug was by Kai-Heng Feng (kaihengfeng), who requested a new bug report. This is a Samsung laptop NP730QCJ. $ sudo modprobe samsung-laptop modprobe: ERROR: could not insert 'samsung_laptop': No such device About my system: $ sudo dmidecode | grep -A 2 -i 'base board' Base Board Information Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: NP730QCJ-K01US $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" $ cat /proc/version_signature Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 $ file /sys/firmware/efi/ /sys/firmware/efi/: directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934759] Re: Enable fib-onlink-tests.sh and msg_zerocopy.sh in kselftests/net on Bionic
** 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/1934759 Title: Enable fib-onlink-tests.sh and msg_zerocopy.sh in kselftests/net on Bionic Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Found this issue while debugging missing tests with bug 1934282. On Bionic there are 3 scripts that are not in the Makefile of the kselftests/net: $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done fib-onlink-tests.sh in_netns.sh msg_zerocopy.sh [Fix] * 830669e691464c selftests/net: enable msg_zerocopy test * 1751eb42ddb56b selftests: net: use TEST_PROGS_EXTENDED * a52b839752aab7 selftests: Add fib-onlink-tests.sh to TEST_PROGS * Set fib-onlink-tests.sh as executable They all need to be backported to Bionic. For the in_netns.sh it's not causing any issue to us when being called by run_afpackettests, but I think it's no harm to fix it to reduce confusions. Commit 1751eb42ddb56b will replace the change in 9faedd64 selftests: net: add in_netns.sh TEST_GEN_PROGS_EXTENDED [1] and 5ff9c1a3 selftests: net: add in_netns.sh to TEST_PROGS [2], and since we need to backport it there is no need to work on these two. [1] https://github.com/torvalds/linux/commit/9faedd643fd9 [2] https://github.com/torvalds/linux/commit/5ff9c1a3dd92 [Test] Run the "net" test suite in the kselftest directory from a patched source tree. fib-onlink-tests.sh and msg_zerocopy.sh tests will be executed. [Where problems could occur] This change will bring in more test for our SRU, we might see new failures because of these test in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934175] Re: Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)
** 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/1934175
Title:
Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
* We had a recent report of a kernel crash due to a NULL pointer dereference
in a Bionic 4.15 derivative kernel, as per the following log collected:
[...]
[537105.767348] SLUB: Unable to allocate memory on node -1,
gfp=0x14000c0(GFP_KERNEL)
[...]
[537105.767368] BUG: unable to handle kernel NULL pointer dereference at
0008
[537105.11] IP: kernfs_kill_sb+0x31/0x70
[537105.783582] PGD 0 P4D 0
[537105.787844] Oops: 0002 [#1] SMP PTI
[...]
RIP: 0010:kernfs_kill_sb+0x31/0x70
RSP: 0018:b90aec1afd00 EFLAGS: 00010286
RAX: RBX: 9fdbd567d900 RCX: a0143885ae01
RDX: RSI: a0143885ae00 RDI: a2937c40
RBP: b90aec1afd10 R08: a0150b581510 R09: 0001814d
R10: b90aec1afcd8 R11: 0100 R12: a01436e43000
R13: a01436e43000 R14: R15: 9fdbd567d900
FS: 7fe41a615b80() GS:a01afea4() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0008 CR3: 007dfe3cc003 CR4: 003606e0
DR0: DR1: DR2:
DR3: DR6: fffe0ff0 DR7: 0400
Call Trace:
sysfs_kill_sb+0x1f/0x40
deactivate_locked_super+0x48/0x80
kernfs_mount_ns+0x1eb/0x230
sysfs_mount+0x66/0xc0
mount_fs+0x37/0x160
? alloc_vfsmnt+0x1b3/0x230
vfs_kern_mount.part.24+0x5d/0x110
do_mount+0x5ed/0xce0
[...]
* The following detailed call stack plus the disassembly help to
understand the cause of the issue:
mount_fs()
--sysfs_mount()
kernfs_mount_ns()
--deactivate_locked_super()
sysfs_kill_sb()
--kernfs_kill_sb()
The below disassembly of kernfs_kill_sb() clarifies exactly the issue:
812f46e0 :
[ ... prologue ...]
48 8b 9f 08 04 00 00mov0x408(%rdi),%rbx # %rbx = kernfs_super_info
*info = sb->s_fs_info
49 89 fcmov%rdi,%r12 # %r12 = super_block *sb
48 c7 c7 40 7c 53 82mov$0x82537c40,%rdi # %rdi =
&kernfs_mutex (global)
812f46f9: R_X86_64_32S kernfs_mutex
e8 ee da 67 00 callq 819721f0 #
mutex_lock(&kernfs_mutex);
[...]
48 8b 53 18 mov0x18(%rbx),%rdx # %rdx = info->node
48 8b 43 20 mov0x20(%rbx),%rax # based on splat, RAX == 0x0
[info->head.prev]
48 89 42 08 mov%rax,0x8(%rdx) # <- OOPS [tried to assign
next->prev = prev, see __list_del()]
48 89 10mov%rdx,(%rax)
48 b8 00 01 00 00 00movabs $0xdead0100,%rax # node->next =
LIST_POISON1
[...]
* The fix for this issue comes from upstream commit 82382acec0c9
("kernfs: deal with kernfs_fill_super() failures"); this commit is a
very trivial fix that adds an INIT_LIST_HEAD(&info->node) in
kernfs_mount_ns(), making the list prev/next pointers valid since the
beginning. Unfortunately this commit wasn't CCed to stable email when
sent, so it wasn't automatically picked up by Ubuntu kernel; now it
was properly submitted to stable list [0].
* Along with this fix, we found another commit (7b745a4e4051) which is
a small/simple fix to correlated code, that also should have been sent
to 4.14.y stable branch, but for some reason wasn't. Since both
commits were accepted in linux-stable, we are hereby proposing the
backport for Ubuntu kernel 4.15.
[0]
https://lore.kernel.org/stable/20210622210622.9925-1-gpicc...@canonical.com/
[Test Case]
* We don't have a real test case, although low-memory condition or an
artificial kprobe reproducer could easily trigger the issue.
* We booted a qemu virtual machine with a kernel containing both
patches with no issues.
[Where problems could occur]
* The likelihood of issues are low, specially due to the fact both patches
are very simple and they are on upstream kernel for more than 3 years (and were
quickly accepted in 4.14.y stable branch last week).
* With that sad, the second patch could potentially introduce issues
with super_block references - I honestly cannot conceive any issues
potentially caused by patch 1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934175/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHe
[Kernel-packages] [Bug 1936673] Re: BUG: kernel NULL pointer dereference, address: 0000000000000000
BTW, booting back into 5.4.0-74.83-generic and everything works fine again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936673 Title: BUG: kernel NULL pointer dereference, address: Status in linux package in Ubuntu: New Bug description: Hi Kernelguys, after updating my kernel from 5.4.0-74.83-generic to 5.4.0-77.86 I get a kernelpanic when putting load onto my NFSv4.1 mount. About the System: I run a Galera Cluster on a VMWare VM with data stored on a NetApp system with NFSv4.1: # grep nfs4 /proc/mounts server:/GALERANFS_MUC_2_LOG /GALERANFS_MUC_LOG nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_BACKUP /GALERANFS_MUC_BACKUP nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_DATA /GALERANFS_MUC_DATA nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 The panic I get when I give a little load on the NFS mount with my mariadb-server is: Jul 16 15:26:10 maria2021-muc-2 systemd[1]: Starting MariaDB 10.5.11 database server... Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.549355] BUG: kernel NULL pointer dereference, address: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.551391] #PF: supervisor read access in kernel mode Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.553377] #PF: error_code(0x) - not-present page Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.555350] PGD 0 P4D 0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.557268] Oops: [#7] SMP PTI Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.559186] CPU: 0 PID: 44171 Comm: mysqld Tainted: P DO 5.4.0-77-generic #86-Ubuntu Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.560644] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.17369862.B64.2012240522 12/24/2020 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.562497] RIP: 0010:pnfs_mark_matching_lsegs_return+0x108/0x150 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.563447] Code: 01 f0 80 4b 40 08 49 8b 06 4c 89 f3 4c 39 75 d0 75 9d 8b 45 bc 85 c0 75 3b 48 8b 4d c8 48 8b 41 38 48 8d 51 38 48 39 c2 74 23 <41> 8b 34 24 48 8b 7d c8 44 89 fa e8 88 e3 ff ff 31 c0 48 83 c4 20 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.565380] RSP: 0018:a6e91c113d68 EFLAGS: 00010283 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.566361] RAX: 95e263669540 RBX: 95e263669268 RCX: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.567364] RDX: 95e263669278 RSI: 95e263669540 RDI: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.568358] RBP: a6e91c113db0 R08: 0064 R09: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.569356] R10: 95e24b0ed480 R11: 003d R12: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.570355] R13: 95e263669278 R14: 95e263669268 R15: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.571353] FS: 7f5d988cf800() GS:95e277a0() knlGS: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.572340] CS: 0010 DS: ES: CR0: 80050033 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.573317] CR2: CR3: 0002229a2003 CR4: 001606f0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.574289] Call Trace: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.575260] _pnfs_return_layout+0x118/0x230 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.576272] ? nfs_inode_detach_delegation+0x29/0x70 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.577244] nfs4_evict_inode+0x70/0x80 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.578205] evict+0xd2/0x1b0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.579174] iput+0x148/0x210 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.580104] do_unlinkat+0x1c5/0x2d0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581014] __x64_sys_unlink+0x23/0x30 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581905] do_syscall_64+0x57/0x190 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.582763] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.583615] RIP: 0033:0x7f5d98b78e3b Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.584429] Code: f0 ff ff 73 01 c3 48 8b 0d 52 80 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 57 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 25 80 0d 00 f7
[Kernel-packages] [Bug 1936673] [NEW] BUG: kernel NULL pointer dereference, address: 0000000000000000
Public bug reported: Hi Kernelguys, after updating my kernel from 5.4.0-74.83-generic to 5.4.0-77.86 I get a kernelpanic when putting load onto my NFSv4.1 mount. About the System: I run a Galera Cluster on a VMWare VM with data stored on a NetApp system with NFSv4.1: # grep nfs4 /proc/mounts server:/GALERANFS_MUC_2_LOG /GALERANFS_MUC_LOG nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_BACKUP /GALERANFS_MUC_BACKUP nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_DATA /GALERANFS_MUC_DATA nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 The panic I get when I give a little load on the NFS mount with my mariadb-server is: Jul 16 15:26:10 maria2021-muc-2 systemd[1]: Starting MariaDB 10.5.11 database server... Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.549355] BUG: kernel NULL pointer dereference, address: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.551391] #PF: supervisor read access in kernel mode Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.553377] #PF: error_code(0x) - not-present page Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.555350] PGD 0 P4D 0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.557268] Oops: [#7] SMP PTI Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.559186] CPU: 0 PID: 44171 Comm: mysqld Tainted: P DO 5.4.0-77-generic #86-Ubuntu Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.560644] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.17369862.B64.2012240522 12/24/2020 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.562497] RIP: 0010:pnfs_mark_matching_lsegs_return+0x108/0x150 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.563447] Code: 01 f0 80 4b 40 08 49 8b 06 4c 89 f3 4c 39 75 d0 75 9d 8b 45 bc 85 c0 75 3b 48 8b 4d c8 48 8b 41 38 48 8d 51 38 48 39 c2 74 23 <41> 8b 34 24 48 8b 7d c8 44 89 fa e8 88 e3 ff ff 31 c0 48 83 c4 20 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.565380] RSP: 0018:a6e91c113d68 EFLAGS: 00010283 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.566361] RAX: 95e263669540 RBX: 95e263669268 RCX: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.567364] RDX: 95e263669278 RSI: 95e263669540 RDI: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.568358] RBP: a6e91c113db0 R08: 0064 R09: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.569356] R10: 95e24b0ed480 R11: 003d R12: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.570355] R13: 95e263669278 R14: 95e263669268 R15: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.571353] FS: 7f5d988cf800() GS:95e277a0() knlGS: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.572340] CS: 0010 DS: ES: CR0: 80050033 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.573317] CR2: CR3: 0002229a2003 CR4: 001606f0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.574289] Call Trace: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.575260] _pnfs_return_layout+0x118/0x230 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.576272] ? nfs_inode_detach_delegation+0x29/0x70 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.577244] nfs4_evict_inode+0x70/0x80 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.578205] evict+0xd2/0x1b0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.579174] iput+0x148/0x210 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.580104] do_unlinkat+0x1c5/0x2d0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581014] __x64_sys_unlink+0x23/0x30 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581905] do_syscall_64+0x57/0x190 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.582763] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.583615] RIP: 0033:0x7f5d98b78e3b Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.584429] Code: f0 ff ff 73 01 c3 48 8b 0d 52 80 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 57 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 25 80 0d 00 f7 d8 64 89 01 48 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.586086] RSP: 002b:7fff18df17c8 EFLAGS: 0246 ORIG_RAX: 0057 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.586907] RAX: ffda RBX: 56024b32e8a0 RCX: 7f5d98b78e3b Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.587739] RDX: 000e RSI: 0010 RDI: 7fff18df1910 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.588561] RBP:
[Kernel-packages] [Bug 1934557] Re: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop
Hi! Do you need some extra information from me? I also have the P14s Gen2 with a 4K screen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934557 Title: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop Status in linux package in Ubuntu: Confirmed Bug description: Backlight does not change. Neither with the keys, nor with the slider. Values in /sys/class/backlight/amdgpu_bl0/brightness do change. However without effect on the actual brightness of the screen, which seems to be stuck at maximum brightness. Following the instructions from here: https://wiki.ubuntu.com/Kernel/Debugging/Backlight ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: simon 1886 F pulseaudio /dev/snd/pcmC2D0p: simon 1886 F...m pulseaudio /dev/snd/controlC1: simon 1886 F pulseaudio /dev/snd/controlC0: simon 1886 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 3 09:46:53 2021 InstallationDate: Installed on 2021-07-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 21A0CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 1.5 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET35W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR1MET35W(1.05):bd04/23/2021:br1.5:efr1.5:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0CTO1WW dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934557] Re: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1934557 Title: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop Status in linux package in Ubuntu: Confirmed Bug description: Backlight does not change. Neither with the keys, nor with the slider. Values in /sys/class/backlight/amdgpu_bl0/brightness do change. However without effect on the actual brightness of the screen, which seems to be stuck at maximum brightness. Following the instructions from here: https://wiki.ubuntu.com/Kernel/Debugging/Backlight ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: simon 1886 F pulseaudio /dev/snd/pcmC2D0p: simon 1886 F...m pulseaudio /dev/snd/controlC1: simon 1886 F pulseaudio /dev/snd/controlC0: simon 1886 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 3 09:46:53 2021 InstallationDate: Installed on 2021-07-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 21A0CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 1.5 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET35W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR1MET35W(1.05):bd04/23/2021:br1.5:efr1.5:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0CTO1WW dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936583] Re: Fix resume failure on Tongfang GMxZGxx Barebone
I messed up: The patch is already in 5.11, what I somehow missed when checking for it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936583 Title: Fix resume failure on Tongfang GMxZGxx Barebone Status in linux package in Ubuntu: New Bug description: SRU Justification: Impact: The Tongfang GMxZGxx Barebone and propably also other new AMD based laptops fail to resume after suspend, and reboot instead with the 5.11 or earlier kernel. Fix: There is a quirk in newer linux kernel that can easily applied to 5.11 also. Testcase: A colleauge tested on a Tongfang GMxZGxx. The Ubuntu 5.11 kernel without the patch fails to resume, with the patch the issue is gone. Patch on upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d1658268e43980c071dbffc3d894f6f6c4b6732a Commit-hash: d1658268e43980c071dbffc3d894f6f6c4b6732a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933385] Re: selftests: bpf: test_verifier fixes
4.15.0-150-generic Summary: 802 PASSED, 0 FAILED ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933385 Title: selftests: bpf: test_verifier fixes Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] kselftest bpf ./test_verifier fails on bionic, preventing regression from being identified. [Test case] Run selftest bpf ./test_verifier and check that it passes. [Potential regressions] The test could still fail or crash the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876687] Re: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on B/F
Failed on bionic:linux generic amd64 host spitfire sru-20210621. ** Summary changed: - function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on Focal + function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on B/F ** Tags added: sru-20210621 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876687 Title: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on B/F Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Focal 5.4.0-29.33 with node amaura (passed on rizzo, rizzo failed with other failures) # [27] ftrace - test for function traceon/off triggers [FAIL] Need to retest on amaura to check if this is just a glitch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1876687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839912] Re: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED"
Manually tested with 4.15.0-150-generic on node glameow. This test-map test can pass without any issue. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839912 Title: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] test_maps bpf selftests is failing on bionic. [Regression potential] Kernel is not changed, but test may give a false pass with this change. [Test case] The fixed test has been run on the kernel in -proposed, and passes. After building it, just run ./test_maps from tools/testing/selftests/bpf/. -- This is at lease a test case regression with the proposed kernel: selftests: test_maps Allowed update sockmap '0:3' not in ESTABLISHED not ok 1..3 selftests: test_maps [FAIL] But with older kernel: selftests: test_maps test_maps: OK ok 1..3 selftests: test_maps [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 13 03:42 seq crw-rw 1 root audio 116, 33 Aug 13 03:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 13 03:52:52 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839912/+subscriptions -- Mailing list: https://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 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Hi Steve, Looks launchpad does not forward the updated comment through mail. I updated step 3 because of OEM kernel 5.13 is only in focal-proposed now: 3. # to install OEM 5.13 # Please manually click on Pre-released updates(focal-proposed) in `Software & Updates` UI first. $ sudo apt-get install linux-image-oem-20.04c On Fri, Jul 16, 2021 at 10:00 AM Steve Barriault <1932...@bugs.launchpad.net> wrote: > Hi Alex: > > I did steps 1 and 2 already. > > Step 3, I get the following error: could not find > > (Actual message is in French) > > Could you check if this has been uploaded to the database? > > Best Regards, > > Steve > > On Wed, Jul 14, 2021 at 10:01 AM Alex Tu <1932...@bugs.launchpad.net> > wrote: > > > sorry for confusing, let me break down the steps: > > 1. # Add PPA from > > > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/comments/2 > > $ sudo add-apt-repository ppa:vicamo/linux-firmware-staging > > > > 2. # to get linux-firmware from Vicamo's PPA > > $ sudo apt-get install linux-firmware > > > > 3. # to install OEM 5.13 > > $ sudo apt-get install linux-image-oem-20.04c > > > > 4. # reboot, and make sure you are running under oem kernel 5.13 > > $ uanme -r > > 5.13.0-1007-oem > > > > 5. # check if the target firmware `-63` loaded > > $ dmesg | grep iwlwifi > > iwlwifi :00:14.3: loaded firmware version 63.c04f3485.0 > > QuZ-a0-hr-b0-63.ucode op_mode iwlmvm > > > > 6. # check if the wifi issue can still be reproduced. > > - if it is there, please also attach the dmesg here. > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1932548 > > > > Title: > > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on > > wireless [8086:a0f0] > > > > Status in Linux Firmware: > > New > > Status in OEM Priority Project: > > Confirmed > > Status in linux-oem-5.10 package in Ubuntu: > > New > > > > Bug description: > > Whenever I am using a wireless connection, the image freezes roughly > > every two minutes. Sometimes, email cannot be retrieved / computer > > complains the connection was momentarily lost. > > > > - If I am on a wire, this problem does NOT occur. > > - This problems occurs on wireless independent of the platform used > > (behavior seen in both Google Hangout and Zoom) > > - This problem does NOT occur on Windows. I did a meeting where both my > > Linux and Windows machines were connected to the same meeting and using > the > > same wifi router, and while the performance on Windows was flawless, > > unfortunately it was not so on the Ubuntu box. So I don't think my wifi > > router or network is to blame. > > - As far as I can recall, the problem used not to be there 2 weeks ago. > > So it may have been introduced by a recent update. > > - As communicated before, I am on a certified machine from Dell, > > recently purchased with Ubuntu already on board from factory (I assume > the > > logs there were sent to you would contain the information). > > - I tried to generate a log on the wireless, but the process did not > let > > me do this very easily. I am more than happy to send you additional > > information - but please let me know which package you want me to spy > upon > > exactly, as I am not sure what would be helpful in this matter. > > > > ProblemType: Bug > > DistroRelease: Ubuntu 20.04 > > Package: xorg 1:7.7+19ubuntu14 > > ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 > > Uname: Linux 5.10.0-1029-oem x86_64 > > ApportVersion: 2.20.11-0ubuntu27.18 > > Architecture: amd64 > > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > > CasperMD5CheckResult: skip > > CompositorRunning: None > > CurrentDesktop: ubuntu:GNOME > > Date: Fri Jun 18 09:47:58 2021 > > DistUpgraded: Fresh install > > DistributionChannelDescriptor: > ># This is the distribution channel descriptor for the OEM CDs > ># For more information see > > http://wiki.ubuntu.com/DistributionChannelDescriptor > >canonical-oem-somerville-focal-amd64-20200502-85 > > DistroCodename: focal > > DistroVariant: ubuntu > > EcryptfsInUse: Yes > > ExtraDebuggingInterest: Yes > > GraphicsCard: > >Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA > > controller]) > > Subsystem: Dell Device [1028:0991] > > InstallationDate: Installed on 2021-04-24 (54 days ago) > > InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary > > 20200502-05:58 > > MachineType: Dell Inc. XPS 13 9310 > > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem > > root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash > vt.handoff=7 > > SourcePackage: xorg > > Symptom: display > > UpgradeStatus: No upgrade log present (probably fresh install) > > dmi.bios.date: 03/25/2021 > > dmi.bios.release: 2.1 > > dmi.bios.vendor: Dell Inc. > > dmi.bios.version: 2.1.1 > > dmi.board.nam
[Kernel-packages] [Bug 1936583] [NEW] Fix resume failure on Tongfang GMxZGxx Barebone
Public bug reported: SRU Justification: Impact: The Tongfang GMxZGxx Barebone and propably also other new AMD based laptops fail to resume after suspend, and reboot instead with the 5.11 or earlier kernel. Fix: There is a quirk in newer linux kernel that can easily applied to 5.11 also. Testcase: A colleauge tested on a Tongfang GMxZGxx. The Ubuntu 5.11 kernel without the patch fails to resume, with the patch the issue is gone. Patch on upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d1658268e43980c071dbffc3d894f6f6c4b6732a Commit-hash: d1658268e43980c071dbffc3d894f6f6c4b6732a ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: SRU Justification: Impact: - The Tongfang GMxZGxx Barebone and propably also other new AMD based laptops fail to resume after suspend and reboot instead with the 5.11 or earlier kernel. + The Tongfang GMxZGxx Barebone and propably also other new AMD based laptops fail to resume after suspend, and reboot instead with the 5.11 or earlier kernel. Fix: There is a quirk in newer linux kernel that can easily applied to 5.11 also. Testcase: A colleauge tested on a Tongfang GMxZGxx. The Ubuntu 5.11 kernel without the patch fails to resume, with the patch the issue is gone. Patch on upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d1658268e43980c071dbffc3d894f6f6c4b6732a Commit-hash: d1658268e43980c071dbffc3d894f6f6c4b6732a -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936583 Title: Fix resume failure on Tongfang GMxZGxx Barebone Status in linux package in Ubuntu: New Bug description: SRU Justification: Impact: The Tongfang GMxZGxx Barebone and propably also other new AMD based laptops fail to resume after suspend, and reboot instead with the 5.11 or earlier kernel. Fix: There is a quirk in newer linux kernel that can easily applied to 5.11 also. Testcase: A colleauge tested on a Tongfang GMxZGxx. The Ubuntu 5.11 kernel without the patch fails to resume, with the patch the issue is gone. Patch on upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d1658268e43980c071dbffc3d894f6f6c4b6732a Commit-hash: d1658268e43980c071dbffc3d894f6f6c4b6732a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936573] [NEW] logitech-djreceiver spams Dmesg
Public bug reported: the Logitech C537 spams dmesg specifically with: logitech-djreceiver 0003:046D:C537.0005: Unexpected input report number 128 fixed upstream: https://www.spinics.net/lists/linux-input/msg71897.html ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936573 Title: logitech-djreceiver spams Dmesg Status in linux package in Ubuntu: New Bug description: the Logitech C537 spams dmesg specifically with: logitech-djreceiver 0003:046D:C537.0005: Unexpected input report number 128 fixed upstream: https://www.spinics.net/lists/linux-input/msg71897.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932065] Re: Upstream v5.9 introduced 'module' patches that removed exported symbols
root@test-b1:~# uname -a Linux test-b1 4.15.0-150-generic #155-Ubuntu SMP Sat Jul 3 13:37:31 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux root@test-b1:~# grep -e ' ref_module' -e ' find_symbol' -e ' each_symbol_section$' -e ' __module_address' -e ' __module_text_address' /proc/kallsyms 9d127720 t find_symbol_in_section 9d128530 T each_symbol_section 9d128590 T find_symbol 9d128740 T ref_module 9d129120 T __module_address 9d129200 T __module_text_address ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932065 Title: Upstream v5.9 introduced 'module' patches that removed exported symbols Status in linux package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: SRU Justification: [Impact] * The following patches removed an exported symbol that will cause potential disruption and breakage for customers modules: inherit TAINT_PROPRIETARY_MODULE modules: return licensing information from find_symbol modules: rename the licence field in struct symsearch to license modules: unexport __module_address modules: unexport __module_text_address modules: mark each_symbol_section static modules: mark find_symbol static modules: mark ref_module static [Fix] * Temporarily revert as SAUCE patches to allow customers time to make necessary changes to support eventual patch changes. [Test Plan] * Check symbols on running kernel sudo grep -e ' ref_module' -e ' find_symbol' -e ' each_symbol_section$' -e ' __module_address' -e ' __module_text_address' /proc/kallsyms * Check symbols on all installed kernels sudo grep -e ' ref_module' -e ' find_symbol' -e ' each_symbol_section$' -e ' __module_address' -e ' __module_text_address' /boot/System.map-* [Where problems could occur] * The new functionality provided by patches will be removed, since we aren't removing existing functionality the risk should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936475] Re: ipv6: fix 'disable_policy' for forwarded packets
** Also affects: linux (Ubuntu Impish)
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/1936475
Title:
ipv6: fix 'disable_policy' for forwarded packets
Status in linux package in Ubuntu:
New
Status in linux source package in Impish:
New
Bug description:
[Impact]
The ipv6 sysctl entry 'disable_policy' has effect for local packets
only (while the ipv4 version is for all packets coming from the
specified interface).
This is fixed upstream with commit ccd27f05ae7b ("ipv6: fix
'disable_policy' for fwd packets").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ccd27f05ae7b
[Test Case]
Enable 'disable_policy' for an interface:
sysctl -w net.ipv6.conf.eth0.disable_policy=1
Add an ipsec policy:
ip xfrm policy add src fd00:100::/64 dst fd00:200::/64 dir out tmpl src
fd00:125::1 dst fd00:125::2 proto esp mode tunnel
Try a ping from subnet fd00:100::/64 to subnet fd00:200::/64.
[Regression Potential]
The patch is small and located in ip6_forward(), thus only this
function is affected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936475/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936478] [NEW] AUFS is missing on Focal v5.11 edge kernels
Public bug reported: [Impact] * Several Focal v5.11 edge kernels are missing AUFS. * This is a regression against previous Focal kernels (v5.4 and v5.8) because it is expected to support same set of features on v5.11. [Test Plan] * Run ubuntu_aufs_smoke_test autotest. [Where problems could occur] * Mounting AUFS file system could succeed introducing a variety of failures due to bugs in AUFS. ** Affects: linux-aws-5.11 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure-5.11 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp-5.11 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oracle-5.11 (Ubuntu) Importance: High Assignee: Krzysztof Kozlowski (krzk) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-aws-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-azure-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-gcp-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oracle-5.11 (Ubuntu Focal) Importance: High Assignee: Krzysztof Kozlowski (krzk) Status: In Progress ** Tags: aws azure focal gcp oracle v5.11 ** Tags added: focal oracle v5.11 ** Tags added: aws azure ** Also affects: linux-oracle-5.11 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws-5.11 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-aws-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oracle-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-azure-5.11 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-gcp-5.11 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oracle-5.11 (Ubuntu) Status: New => In Progress ** Changed in: linux-oracle-5.11 (Ubuntu Focal) Status: New => In Progress ** Tags added: gcp ** Changed in: linux-oracle-5.11 (Ubuntu) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux-oracle-5.11 (Ubuntu Focal) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux-oracle-5.11 (Ubuntu) Importance: Undecided => High ** Changed in: linux-oracle-5.11 (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936478 Title: AUFS is missing on Focal v5.11 edge kernels Status in linux-aws-5.11 package in Ubuntu: New Status in linux-azure-5.11 package in Ubuntu: New Status in linux-gcp-5.11 package in Ubuntu: New Status in linux-oracle-5.11 package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux-aws-5.11 source package in Focal: New Status in linux-azure-5.11 source package in Focal: New Status in linux-gcp-5.11 source package in Focal: New Status in linux-oracle-5.11 source package in Focal: In Progress Bug description: [Impact] * Several Focal v5.11 edge kernels are missing AUFS. * This is a regression against previous Focal kernels (v5.4 and v5.8) because it is expected to support same set of features on v5.11. [Test Plan] * Run ubuntu_aufs_smoke_test autotest. [Where problems could occur] * Mounting AUFS file system could succeed introducing a variety of failures due to bugs in AUFS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.11/+bug/1936478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922334] Re: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16)
@koba, would it be better to move this issue to https://gitlab.freedesktop.org/drm/intel/-/issues, or is this more likely related to Thunderbolt in this generation of XPS going to Titan Ridge? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1922334 Title: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16) Status in Dell Sputnik: New Status in linux package in Ubuntu: In Progress Status in linux-meta-oem-5.6 package in Ubuntu: New Bug description: I've recently upgraded my workhorse from XPS 9560 (2016) to a newer generation XPS 9500 (2020) and ran into several things that feel like regressions, but are probably related to hardware changes. This is one of them. tl;dr: When using XPS 9500 with a TB16 dock and an external monitor (Benq EX2780Q) connected to the dock via USB-C to USB-C (DP alternate mode), most of the time the monitor fails to wake up after going blank. details: Simplest way to reproduce is for hit Super+L, wait for the monitor to properly go in standby, then type something in or move the mouse to wake it up. 8 times out of 10 it does not wake up when using XPS 9500. Most of the time this can be fixed by power cycling the monitor, however this has a seemingly random chance of triggering two other issues: 1. The system to lose sight of the monitor for a brief period of time, which sometimes causes it to hang with a black screen and needs some combination of restarting the monitor, the dock, and the laptop, because there is a separate USB issue making hot-plugging unusable. 2. The monitor itself gets stuck in a weird standby state where it stops reacting to button presses and I need to hold the power button a bit longer for it to sort of hard reset? Notably, it wakes up fine every time when using XPS 9560 or Precision 5520 in the same setup which I have been using for ages. This becomes particularly troublesome when screens go into short-lived standby during boot: after the Dell logo, after entering the LUKS password, after logging in. Each of these points has a chance of triggering the bug, because it looks like there is some sort of mode change and waking signal submission happening between them that triggers it. I had to disable screen timeout as a temporary workaround to be able to work on this system at all without having to play "monitor wake lottery" every time I go brew a cuppa. The workaround at boot time is to either re-roll the lottery, or boot with the dock connected and lid open, then close the lid and keep working from there. The dock, the monitor, all USB peripherals are the same in both cases - it's literally just the TB16 cable plugged into a different laptop. I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM (-20.04b and -20.04-edge) kernels on the 9500 with same results. I have attempted disabling USB autosuspend via a GRUB kernel parameter to usbcore. I have attempted both NVidia and Intel GPUs. I have attempted playing with BIOS settings: wake on dell usb-c docks, disable early sign of life for both checkboxes, disabling SGX and SMM, checking all 3 boxes for Thunderbolt and switching off Thunderbolt security. None of these make a noticeable difference. Since it was fine with 9560, 5520 and a friend with a 9570 has no issues either, my gut feeling is that this is due to the upgrade from Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in this generation - something wrong with the driver, or the firmware may have missed some of the "lessons learned" in Alpine Ridge and caused this regression. That would also make it applicable to 9300, which has a "developer edition" option under Project Sputnik and several reports of the same problem scattered across the internet: https://www.dell.com/community/XPS/XPS-13-9300-with-WD19TB-External-display-not-coming-on-after/td-p/7676922 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342 (may be a duplicate, but for WD19TB dock on 9300, so may be slightly different too) https://www.reddit.com/r/linuxquestions/comments/ka0w2j/monitor_doesnt_wake_from_sleep/ etc etc. Those reports suggest high bandwidth usage sometimes affects it, so it's worth noting that my external monitor is a 1440p 144Hz one that uses tons of bandwidth indeed. The only hint in terms of logs seems to be this message in dmesg that I see when power cycling the monitor and getting back into the system: [ 250.777684] pcieport :09:04.0: pciehp: Slot(0-1): Card not present [ 250.777695] xhci_hcd :0b:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 250.778293] xhci_hcd :0b:00.0: can't change power state from D3hot to D0 (config space inaccessible) [ 250.778336] xhci_hcd :0b:00.0: Controlle
[Kernel-packages] [Bug 1931432] Re: crash FTBFS on riscv64
#1935679 has a patch for the segfault. But additional work will be needed to enable building on RISC-V. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1931432 Title: crash FTBFS on riscv64 Status in crash package in Ubuntu: Confirmed Status in crash source package in Focal: Confirmed Status in crash source package in Groovy: Confirmed Bug description: Crash fails to build from source on riscv at least for Focal and Groovy, later releases may also be affected but I haven't confirm it. Examples of failed builds : Groovy : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630864 Focal : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1/+build/21630885 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935679] Re: crash: build failure on RISC-V
*** This bug is a duplicate of bug 1931432 *** https://bugs.launchpad.net/bugs/1931432 ** This bug has been marked a duplicate of bug 1931432 crash FTBFS on riscv64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1935679 Title: crash: build failure on RISC-V Status in crash package in Ubuntu: New Bug description: version: 7.3.0-1ubuntu1 Building crash for RISC-V fails with a segfault. This segfault is due to missing support for architecture RISC-V in file configure.c. configure is used to update Makefile. It replaces "TARGET " by "(NULL)". A patch is at https://github.com/xypron/crash/commit/2391175c7936a3d873b7b7f1b6c6cae2f4c166b8 Current upstream crash uses an version 7.6 for gdb which does not support RISC-V. Patch series https://listman.redhat.com/archives/crash- utility/2021-March/msg00078.html provides an update to gdb 10.1. https://github.com/YustasSwamp/crash/tree/crash-gdb10.2-devel-temp provides patches for using gdb 10.2. For building we need command makeinfo which is provided by missing package texinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1935679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936475] [NEW] ipv6: fix 'disable_policy' for forwarded packets
Public bug reported:
[Impact]
The ipv6 sysctl entry 'disable_policy' has effect for local packets only
(while the ipv4 version is for all packets coming from the specified
interface).
This is fixed upstream with commit ccd27f05ae7b ("ipv6: fix
'disable_policy' for fwd packets").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ccd27f05ae7b
[Test Case]
Enable 'disable_policy' for an interface:
sysctl -w net.ipv6.conf.eth0.disable_policy=1
Add an ipsec policy:
ip xfrm policy add src fd00:100::/64 dst fd00:200::/64 dir out tmpl src
fd00:125::1 dst fd00:125::2 proto esp mode tunnel
Try a ping from subnet fd00:100::/64 to subnet fd00:200::/64.
[Regression Potential]
The patch is small and located in ip6_forward(), thus only this function
is affected.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1936475
Title:
ipv6: fix 'disable_policy' for forwarded packets
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
The ipv6 sysctl entry 'disable_policy' has effect for local packets
only (while the ipv4 version is for all packets coming from the
specified interface).
This is fixed upstream with commit ccd27f05ae7b ("ipv6: fix
'disable_policy' for fwd packets").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ccd27f05ae7b
[Test Case]
Enable 'disable_policy' for an interface:
sysctl -w net.ipv6.conf.eth0.disable_policy=1
Add an ipsec policy:
ip xfrm policy add src fd00:100::/64 dst fd00:200::/64 dir out tmpl src
fd00:125::1 dst fd00:125::2 proto esp mode tunnel
Try a ping from subnet fd00:100::/64 to subnet fd00:200::/64.
[Regression Potential]
The patch is small and located in ip6_forward(), thus only this
function is affected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936475/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
Inadvertently,I found Realtek NIC came in and out of the aspm L1 state in an unreasonably high frequency even during downloading something.For a NVME device,it does not show this symptom during it's working and having workloads in flight which can be indicated by monitoring clkreq# being asserted/deasserted.To dig deeper for this issue,is someone familiar with Realtek NIC internal logic of aspm,maybe it will do the trick by tweaking some of the specific registers? -- You 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: Confirmed Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Confirmed 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 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 su
[Kernel-packages] [Bug 1935951] Re: [nvidia] HomeOffice & Un-/Docking: X11 crash on resume when docked to multi monitor
I cannot find any X11 specific crash file(s).
But I think these KDE files are related to this bug:
As soon as X11 shows up these messages(crash) (see Xorg.log.old):
1272.639] (WW) NVIDIA(0): Failed to set the display configuration
[ 1272.639] (WW) NVIDIA(0): - Setting a mode on head 1 failed: Invalid surface
parameters
...
"[ 1272.639] (EE) EnterVT failed for screen 0"
the kde sesssion is crashing and then a new Xorg.log is created. and
the login manager starts.
I am out of ideas ... might be the nvidia beta drivers might help?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1935951
Title:
[nvidia] HomeOffice & Un-/Docking: X11 crash on resume when docked to
multi monitor
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Incomplete
Bug description:
X11 crashes on resume and my current desktop is lost and the login
manager appears.
I posted a bugreported here
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1197
with configu details.
But it seems to be nvidia, but may be a workaround is possible in Ubuntu?
This bug prevents me to use Linux for daily docking /undocking cycles for
HomeOffice (works fine with Windows).
[ 1272.639] (II) NVIDIA(0): Setting mode "DP-4: nvidia-auto-select
@1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[ 1272.639] (WW) NVIDIA(0): Failed to set the display configuration
[ 1272.639] (WW) NVIDIA(0): - Setting a mode on head 1 failed: Invalid
surface parameters
[ 1272.639] (WW) NVIDIA(0): were specified
[ 1272.639] (EE) NVIDIA(0): Failed to enter VT (mode initialization failed)
[ 1272.639] (EE)
Fatal server error:
[ 1272.639] (EE) EnterVT failed for screen 0
[ 1272.639] (EE)
[ 1272.639] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 1272.639] (EE) Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
[ 1272.639] (EE)
[ 1274.034] (EE) Server terminated with error (1). Closing log file.
I found something similar which could handle the EnterVT failed issue:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/
but I am not sure if it is already in Ubuntu 20.04 LTS
Hardware:
Hardware used:
Dell Precision 15" 7540, Xeon E-2286M@2.4GHz, 128 GB ECC RAM, NVIDIA Quadro
RTX 5000 16GB VRAM
Dockingstations at Home and Offices: WD19DC (240W)
Monitors used for Linux migration Office1: 2x 4K U4320Q, 42.5" @ 96dpi font /
No scaling a
Monitors used for Linux migration Office2: 2xU3818DW, 37.5"
Monitors used for Linux migration at home: 3x FullHD Dell monitors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1935951/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
