[Kernel-packages] [Bug 1922406]
A solution to the AX210 pnvm error that worked for me on Ubuntu 20.04.3 kernel 5.11.0-27-generic with an AX210 is to delete /lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm I found this at https://www.reddit.com/r/Fedora/comments/m9p2h2/ax210_drivers/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922406 Title: Intel AX210 Wi-Fi card does not work since updating to 1.196 Status in Linux: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Bug description: Running 21.04, updated daily. Since updating the linux-firmware package yesterday, the Wireless card does not work with current kernel (5.11.0-13). The error message is as follows: Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting for PNVM load! Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start RT ucode: -110 Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: iwl_trans_send_cmd bad state = 1 It **does** work with 5.11.0-11 (previous version) Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW date: 12/23/2020 CPU: Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP L2 cache: 4 MiB To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1922406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Actually Łukasz Spintzyk is the author of the fix and in comment #39 even he is only discussing open source drivers. Not sure if Nvidia-470 is expected to work. ** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** No longer affects: nvidia-graphics-drivers-470 (Ubuntu Focal) ** No longer affects: nvidia-graphics-drivers-470 (Ubuntu Hirsute) ** No longer affects: nvidia-graphics-drivers-470 (Ubuntu Impish) ** No longer affects: xserver-xorg-video-amdgpu (Ubuntu Focal) ** No longer affects: xserver-xorg-video-amdgpu (Ubuntu Hirsute) ** No longer affects: xserver-xorg-video-amdgpu (Ubuntu Impish) ** No longer affects: xserver-xorg-video-nouveau (Ubuntu Focal) ** No longer affects: xserver-xorg-video-nouveau (Ubuntu Hirsute) ** No longer affects: xserver-xorg-video-nouveau (Ubuntu Impish) ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Assignee: (unassigned) => Łukasz Spintzyk (lspintzy) ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Assignee: (unassigned) => Łukasz Spintzyk (lspintzy) ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => In Progress ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/merge_requests/2 https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/merge_requests/62 ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues #553 https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/553 ** Also affects: nouveau via https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/553 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943030] Re: Enable riscv64 build of nvidia-settings
** Tags added: fr-1689 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1943030 Title: Enable riscv64 build of nvidia-settings Status in nvidia-settings package in Ubuntu: New Bug description: Please enable the build on riscv64 architecture of nvidia-settings since it works fine using the attached debdiff: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940972] Re: v5.13 kernel ftrace selftest fails on riscv64 unmatched
Launchpad has imported 2 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=214185. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-08-26T11:18:31+00:00 colin.king wrote: While running some kernel selftests I discovered that the kernel ftrace func_stack_tracer.tc fails. How to reproduce: in the 5.13 kernel source tree: $ cd linux/tools/testing/selftests/ftrace $ sudo ./ftracetest test.d/ftrace/func_stack_tracer.tc [1] ftrace - Max stack tracer [FAIL] # of passed: 0 # of failed: 1 # of unresolved: 0 # of untested: 0 # of unsupported: 0 # of xfailed: 0 # of undefined(test bug): 0 ... I've looked at this test and the following occurs: 0. go to the tracking directory: cd /sys/kernel/debug/tracing 1. tracer is disabled: echo 0 > /proc/sys/kernel/stack_tracer_enabled 2. tracer is set to track all kernel functions with *lock* in the name: echo '*lock*' > stack_trace_filter (this takes a few minutes to configure, it's quite slow). one can see the functions filtered on by using cat stack_trace_filter 3. emabling the tracer: echo 0 > stack_max_size echo 1 > /proc/sys/kernel/stack_tracer_enabled 4. check if the tracer has found any functions that match: cat stack_trace | grep lock ..none appear in position 0 in the stack_trace file. This works on other arches such as arm64, amd64, s390x etc.. so I'm not sure why it's not working on RISC-V. Reply at: https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1940972/comments/6 On 2021-08-26T11:20:43+00:00 colin.king wrote: Tested in RISC-V SiFive Unmatched dev board and QEMU. Reply at: https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1940972/comments/7 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1940972 Title: v5.13 kernel ftrace selftest fails on riscv64 unmatched Status in Linux: Confirmed Status in ubuntu-kernel-tests: New Status in linux-riscv package in Ubuntu: New Bug description: $ sudo make -C tools/testing/selftests TARGETS=ftrace run_tests ... # [32] ftrace - Max stack tracer [FAIL] ... Testing using 5.13.0-1002.2 the full ftrace suite takes just over 2 hours on unmatched. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1940972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942619] Re: WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14/amd64/ Headers are not needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942619 Title: WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu] Status in linux package in Ubuntu: Confirmed Bug description: This has hit me twice in the last 24 hours. Displays come in and out of power saving, without actually displaying anything. The console doesn't become usable. It seems to be unrecoverable, shutdown gets stuck somewhere and I end up having to hit the reset button. This is a desktop machine, which suspends frequently, usually without issue. Radeon RX 570, dual monitor, display link ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.31.33 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 10:11:35 2021 InstallationDate: Installed on 2019-06-18 (808 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-09 (116 days ago) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943079] Re: Installing latest linux-firmware (1.187.16) causes wifi interface to disappear
Can you please attach `lspci -nn`? -- 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/1943079 Title: Installing latest linux-firmware (1.187.16) causes wifi interface to disappear Status in linux-firmware package in Ubuntu: New Bug description: Summary === Installing linux-firmware 1.187.16, which became available on 17th Aug 2021, caused my wifi interface to disappear after reboot. My machine: Lenovo T15 Gen2 CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 I tried force installing previous version 1.187.15, but that version isn't available! So, in the end, I rebooted into a live CD and re-installed the OS! In the newly installed OS, I just made sure to NOT select linux- firmware package in the list of available upgrades, and I will stick with version 1.187.15 till I have confidence there is better and working version. NOTE: On an older machine, with an older chipset, I did NOT experience this issue. Older machine: Lenovo x230 CPU: Intel(R) Core(TM) i5-3210M CPU Wifi: Centrino Advanced-N 6205 System == I'm running Linux Mint Edge, based on Ubuntu 20.04, but with upgraded kernel (5.11.0.34): lsb_release -rd Description: Linux Mint 20.2 Release: 20.2 Package === apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 Candidate: 1.187.16 Version table: *** 1.187.16 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages Expected Upgrade to linux-firmware=1.187.16 Reboot. Wifi network Interface must continue to be available and functioning. What Happened = Upgrade to linux-firmware=1.187.16 Reboot. Wifi network interface disappeared. Therefore, cannot use wifi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1943079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943083] Re: [i915] [Braswell] screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen
This reminds me of bug 1935901 and bug 1767654 but isn't quite the same... Next time the problem happens please run: journalctl -b0 > journal.txt and attach the resulting text file here. Also it might be helpful to see if you can find kernel versions older than 5.13 that don't have the bug: https://kernel.ubuntu.com/~kernel- ppa/mainline/?C=M;O=D ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943083 Title: [i915] [Braswell] screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen Status in linux package in Ubuntu: Incomplete Bug description: I reported that against mutter, but it can be gnome-shell as well, or even Intel driver/kernel related. It happens since my switch to Impish, I have never seen that issue before. Integrated Intel HD graphics 400 onboard. STEPS to reproduce: 1) Move the mouse pointer to the left edge of the screen 2) See that everything works as expected 3) Open an app so that the window comes up, eg. "Files" 4) Move the mouse pointer to the left edge again. 5) See that the screen goes black for a second, but the mouse pointer stays visible. Observation 1: At first I thought that it was related to dash-to-dock because moving the mouse to the area where I used to have the dock exhibits the flicker (I moved it to bottom for GNOME 40). But it turns out that it doesn't matter: I can turn off the extension completely or move it back to the left and the flicker always occurs. Observation 2: It doesn't happen without any window onscreen. Having a program minimized to the dock doesn't suffice to exhibit the bug. I have to bring up the window and then the bug shows up. Fun Fact 1: "Files" exhibits it more "aggresively" than "Terminal". It is easier to trigger. With gnome-terminal I sometimes can hit the edge with the pointer without triggering the glitch. Observation 3: I cannot record the issue: Recording a screencast via "Ctrl-Alt-Shift-R" doesn't work. Well, the screencasting itself does work, but when recording the screencast the glitch simply doesn't happen. I am a bit lost further debugging this, any help is highly welcome. I guess that my observations rather hint at mutter being to blame. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mutter 40.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 23:03:53 2021 InstallationDate: Installed on 2018-02-23 (1293 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935901] Re: Braswell video locks up under gnome-shell [Failed to post KMS update: drmModePageFlip on CRTC 93 failed: No space left on device]
** Changed in: mutter (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1935901 Title: Braswell video locks up under gnome-shell [Failed to post KMS update: drmModePageFlip on CRTC 93 failed: No space left on device] Status in linux-hwe-5.8 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I get a blank screen with a mouse cursor. Cursor doesn't respond to mouse inputs. System doesn't respond to keyboard inputs. I can still ssh in from another machine. I see the following in the journal: Jul 13 01:55:14 jenks gnome-shell[1403]: libinput error: client bug: timer event3 debounce: scheduled expiry is in the past (-442ms> Jul 13 01:55:14 jenks gnome-shell[1403]: libinput error: client bug: timer event3 debounce short: scheduled expiry is in the past (> Jul 13 01:57:07 jenks gnome-shell[1403]: Failed to post KMS update: drmModePageFlip on CRTC 93 failed: No space left on device ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 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 CasperMD5CheckResult: skip Date: Tue Jul 13 02:06:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-29 (14 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1935901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943083] Re: screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen
** Package changed: mutter (Ubuntu) => linux (Ubuntu) ** Summary changed: - screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen + [i915] [Braswell] screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the 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/1943083 Title: [i915] [Braswell] screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen Status in linux package in Ubuntu: Incomplete Bug description: I reported that against mutter, but it can be gnome-shell as well, or even Intel driver/kernel related. It happens since my switch to Impish, I have never seen that issue before. Integrated Intel HD graphics 400 onboard. STEPS to reproduce: 1) Move the mouse pointer to the left edge of the screen 2) See that everything works as expected 3) Open an app so that the window comes up, eg. "Files" 4) Move the mouse pointer to the left edge again. 5) See that the screen goes black for a second, but the mouse pointer stays visible. Observation 1: At first I thought that it was related to dash-to-dock because moving the mouse to the area where I used to have the dock exhibits the flicker (I moved it to bottom for GNOME 40). But it turns out that it doesn't matter: I can turn off the extension completely or move it back to the left and the flicker always occurs. Observation 2: It doesn't happen without any window onscreen. Having a program minimized to the dock doesn't suffice to exhibit the bug. I have to bring up the window and then the bug shows up. Fun Fact 1: "Files" exhibits it more "aggresively" than "Terminal". It is easier to trigger. With gnome-terminal I sometimes can hit the edge with the pointer without triggering the glitch. Observation 3: I cannot record the issue: Recording a screencast via "Ctrl-Alt-Shift-R" doesn't work. Well, the screencasting itself does work, but when recording the screencast the glitch simply doesn't happen. I am a bit lost further debugging this, any help is highly welcome. I guess that my observations rather hint at mutter being to blame. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mutter 40.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 23:03:53 2021 InstallationDate: Installed on 2018-02-23 (1293 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943083] [NEW] screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen
You have been subscribed to a public bug: I reported that against mutter, but it can be gnome-shell as well, or even Intel driver/kernel related. It happens since my switch to Impish, I have never seen that issue before. Integrated Intel HD graphics 400 onboard. STEPS to reproduce: 1) Move the mouse pointer to the left edge of the screen 2) See that everything works as expected 3) Open an app so that the window comes up, eg. "Files" 4) Move the mouse pointer to the left edge again. 5) See that the screen goes black for a second, but the mouse pointer stays visible. Observation 1: At first I thought that it was related to dash-to-dock because moving the mouse to the area where I used to have the dock exhibits the flicker (I moved it to bottom for GNOME 40). But it turns out that it doesn't matter: I can turn off the extension completely or move it back to the left and the flicker always occurs. Observation 2: It doesn't happen without any window onscreen. Having a program minimized to the dock doesn't suffice to exhibit the bug. I have to bring up the window and then the bug shows up. Fun Fact 1: "Files" exhibits it more "aggresively" than "Terminal". It is easier to trigger. With gnome-terminal I sometimes can hit the edge with the pointer without triggering the glitch. Observation 3: I cannot record the issue: Recording a screencast via "Ctrl-Alt-Shift-R" doesn't work. Well, the screencasting itself does work, but when recording the screencast the glitch simply doesn't happen. I am a bit lost further debugging this, any help is highly welcome. I guess that my observations rather hint at mutter being to blame. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mutter 40.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 23:03:53 2021 InstallationDate: Installed on 2018-02-23 (1293 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen https://bugs.launchpad.net/bugs/1943083 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
Hi Chis Chiu, I had a similar issue here with all kernels after 5.8.0-63-generic. I found this bug report and just finished trying your suggestion I'm pleased to tell you that at least in my Dell notebook it worked. The as previously reported the issue only happens after login into the X env. If I can provide any extra detail please let me know. Kind regards. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943092] Re: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dp
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943092 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: New Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 \linux-headers-5.11.0-34-generic: Installed: (none) Candidate: 5.11.0-34.36~20.04.1 Version table: 5.11.0-34.36~20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages Install failed during latest kernel update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-34-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 8 20:26:11 2021 DuplicateSignature: package:linux-headers-5.11.0-34-generic:(not installed) Unpacking linux-hwe-5.11-headers-5.11.0-34 (5.11.0-34.36~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-26WFDo/10-linux-hwe-5.11-headers-5.11.0-34_5.11.0-34.36~20.04.1_all.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-hwe-5.11-headers-5.11.0-34.list-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-02-21 (199 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943092] [NEW] package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.
Public bug reported: Description:Ubuntu 20.04.3 LTS Release:20.04 \linux-headers-5.11.0-34-generic: Installed: (none) Candidate: 5.11.0-34.36~20.04.1 Version table: 5.11.0-34.36~20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages Install failed during latest kernel update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-34-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 8 20:26:11 2021 DuplicateSignature: package:linux-headers-5.11.0-34-generic:(not installed) Unpacking linux-hwe-5.11-headers-5.11.0-34 (5.11.0-34.36~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-26WFDo/10-linux-hwe-5.11-headers-5.11.0-34_5.11.0-34.36~20.04.1_all.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-hwe-5.11-headers-5.11.0-34.list-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-02-21 (199 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943092 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: New Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 \linux-headers-5.11.0-34-generic: Installed: (none) Candidate: 5.11.0-34.36~20.04.1 Version table: 5.11.0-34.36~20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages Install failed during latest kernel update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-34-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 8 20:26:11 2021 DuplicateSignature: package:linux-headers-5.11.0-34-generic:(not installed) Unpacking linux-hwe-5.11-headers-5.11.0-34 (5.11.0-34.36~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-26WFDo/10-linux-hwe-5.11-headers-5.11.0-34_5.11.0-34.36~20.04.1_all.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-hwe-5.11-headers-5.11.0-34.list-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-02-21 (199 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942008] Re: Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs, won't wake from sleep
I made a post on a support site here: https://ubuntuforums.org/showthread.php?t=2466821. Even though this is clearly a bug in the 5.8+ kernels, updating to 5.11 and 20.04.3 still has this bug. The "solution" was to downgrade the kernel to 5.4, which is not a long-term solution. Hopefully, this bug will be resolved in future updates to the kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942008 Title: Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs, won't wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake from sleep worked fine. Updates for 20.04.2 caused issues where it wouldn't wake from sleep, rebooting hangs, and never actually shutdowns for the reboot, and shutdown causes an audible hardware clicking noise (somewhere to the left side of the computer underneath the keyboard) and corrupts the BIOS. The corrupted BIOS causes the computer to not boot at all and I have to do a BIOS reset via CMOS (Hold the power button for 2-3 sec while pressing the WIN+v keys until it begins to boot). This gets more difficult each time it's done, where I have to wait longer before trying it and it seems to take longer to work. I have tried shutdown from the GUI menu, from the log- out menu, from Konsole, and from a TTY (CTRL+ALT+F2). I also have tried reinstalling a couple of times. Computer specs: Host: HP Pavilion dv7-2180us Notebook PC Rev 1 Kernel: 5.8.0-59-generic Resolution: 1600x900 CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz GPU: AMD ATI Mobility Radeon HD 4650/5165 Memory: 6 GB --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kah1382 F pulseaudio /dev/snd/controlC1: kah1382 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (13 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 Tags: focal Uname: Linux 5.11.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2009 dmi.bios.release: 15.51 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.33 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3624 dmi.board.vendor: Quanta dmi.board.version: 18.42 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.ec.firmware.release: 24.66 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.sku: NV022UA#ABA dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942215] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI
Launchpad has imported 6 comments from the remote bug at
https://bugs.acpica.org/show_bug.cgi?id=1545.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2021-08-31T16:14:47+00:00 Colin Ian King wrote:
Source: source/components/dispatcher/dswexec.c
Function: AcpiDsExecEndOp
The following call can be problematic if OpType is out of range:
if (ACPI_SUCCESS (Status))
{
/*
* Dispatch the request to the appropriate interpreter handler
* routine. There is one routine per opcode "type" based upon the
* number of opcode arguments and return type.
*/
Status = AcpiGbl_OpTypeDispatch[OpType] (WalkState);
}
It has been observed that an invalid OpType in the Linux kernel has
triggered a trap where and out of range OpType was caught at run time.
Newer versions of gcc generate a trap on an out of range dispatch call
with a ud2 opcode causing kernel oopses such as:
[ 11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
[ 11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 89
c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 c0
6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
[ 11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
[ 11.513428] RAX: RBX: 8f08a7573800 RCX: 0040
[ 11.514972] RDX: RSI: 91ea9980 RDI: 02cb
[ 11.516100] RBP: aaeca1a77710 R08: R09: 8f08a8c84af0
[ 11.517479] R10: R11: 0003 R12:
[ 11.518985] R13: 8f08a8c84af0 R14: R15:
[ 11.520425] FS: 7f7fb403ed00() GS:8f348d5c()
knlGS:
[ 11.521931] CS: 0010 DS: ES: CR0: 80050033
[ 11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 007706e0
[ 11.524924] DR0: DR1: DR2:
[ 11.526221] DR3: DR6: fffe0ff0 DR7: 0400
[ 11.527636] PKRU: 5554
[ 11.528820] Call Trace:
[ 11.529807] acpi_ps_parse_loop+0x587/0x660
[ 11.531198] acpi_ps_parse_aml+0x1af/0x552
[ 11.532595] acpi_ps_execute_method+0x208/0x2ca
[ 11.533972] acpi_ns_evaluate+0x34e/0x4f0
[ 11.535361] acpi_evaluate_object+0x18e/0x3b4
[ 11.536736] acpi_evaluate_dsm+0xb3/0x120
[ 11.537943] ? acpi_evaluate_dsm+0xb3/0x120
[ 11.539214] nfit_intel_shutdown_status+0xed/0x1b0 [nfit]
[ 11.540603] acpi_nfit_add_dimm+0x3cb/0x670 [nfit]
[ 11.541990] acpi_nfit_register_dimms+0x141/0x460 [nfit]
[ 11.543377] acpi_nfit_init+0x54f/0x620 [nfit]
[ 11.544755] acpi_nfit_add+0x192/0x1f0 [nfit]
[ 11.546116] acpi_device_probe+0x49/0x170
I strongly suggest sanity out-of-bounds checks on the OpType before
calling the dispatcher.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942215/comments/6
On 2021-09-07T12:04:29+00:00 Colin Ian King wrote:
There is a similar array underflow error in the code here:
if (!(WalkState->OpInfo->Flags & AML_NO_OPERAND_RESOLVE))
{
/* Resolve all operands */
Status = AcpiExResolveOperands (WalkState->Opcode,
&(WalkState->Operands [WalkState->NumOperands -1]),
WalkState);
}
WalkState->NumOperands - 1 in one specific case is -1 causing an oops.
See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942215 -
comment #8. A check something like the following is required:
if (walk_state->num_operands - 1 >= ARRAY_SIZE(walk_state->operands)) {
ACPI_ERROR((AE_INFO, " many operands 0x%X for op_type 0x%X",
walk_state->num_operands - 1, op_type));
status = AE_AML_BAD_OPCODE;
goto cleanup;
}
..perhaps a walk_state->num_operands < 1 check is required to as the
above fix handles the 0 - 1 > 0x wraparound as too many args.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942215/comments/12
On 2021-09-07T14:57:06+00:00 Robert Moore wrote:
Colin,
I think there are many places where an invalid opcode will cause problems - it
is simply such a serious problem that it is nearly impossible to catch all of
the possible problems created.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942215/comments/14
On 2021-09-07T15:38:25+00:00 Robert Moore wrote:
In any case, the the DSDT that is posted in comment #4 show the problem?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942215/comments/15
[Kernel-packages] [Bug 1925246] Re: binderfs support is not enabled
** Description changed: + [Impact] + Hey, in https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1914568 we got binder support enabled but the configuration is completely different from what we have in our other cloud and generic kernels: ubuntu@machine-1:~$ cat /boot/config-5.4.0-1046-azure | grep BINDER CONFIG_ANDROID_BINDER_IPC=m # CONFIG_ANDROID_BINDERFS is not set CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set $ cat /boot/config-5.4.0-14-generic | grep BINDER CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set Not having binderfs support is breaking Anbox Cloud support. What is the reason for not having the config aligned between the kernels here? Thanks! + + + [Test Plan] + + After installing the extra modules package, binderfs should be available + via mount. + + [Where problems could occur] + + It could cause issues to any existing users of the existing binder_linux + module. However this module is currently shipped as extra and should not + affect regular users. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1925246 Title: binderfs support is not enabled Status in linux-azure package in Ubuntu: New Bug description: [Impact] Hey, in https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1914568 we got binder support enabled but the configuration is completely different from what we have in our other cloud and generic kernels: ubuntu@machine-1:~$ cat /boot/config-5.4.0-1046-azure | grep BINDER CONFIG_ANDROID_BINDER_IPC=m # CONFIG_ANDROID_BINDERFS is not set CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set $ cat /boot/config-5.4.0-14-generic | grep BINDER CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set Not having binderfs support is breaking Anbox Cloud support. What is the reason for not having the config aligned between the kernels here? Thanks! [Test Plan] After installing the extra modules package, binderfs should be available via mount. [Where problems could occur] It could cause issues to any existing users of the existing binder_linux module. However this module is currently shipped as extra and should not affect regular users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1925246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868105] Re: No Sound, dummy output in settings
Same issue on a Dell Inspiron 7559 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1868105 Title: No Sound, dummy output in settings Status in linux-oem-osp1 package in Ubuntu: Confirmed Bug description: After I updated my laptop today, sound is gone, "dummy output" is shown. SoundTroubleshootingProcedure did not help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1043-oem-osp1 5.0.0-1043.48 ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 Uname: Linux 5.0.0-1043-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: verigraf 3039 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 17:36:18 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2019-10-28 (143 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. G3 3590 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=9f6f0954-fa11-47dc-99b3-a4088a85724e ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 SourcePackage: linux-oem-osp1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.2 dmi.board.name: 0201H1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.2:bd01/03/2020:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn0201H1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1868105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943086] [NEW] linux-modules-nvidia-470-generic-hwe-20.04 dependency cant be installed
Public bug reported: linux-modules-nvidia-470-generic-hwe-20.04=5.11.0-34.36~20.04.1 depends on nvidia-kernel-common-470 (>= 470.63.01) but that version is not published, the latest one available today is 470.57.02-0ubuntu0.20.04.1 That means that installing latest hwe kernel for 20.04 breaks nvidia driver. This is problematic in distros like Elementary OS 6 as they dont expose the grub menu, so you have the latest kernel version installed only, which will not be able to boot on the graphical interface because there is no driver. ** Affects: linux-restricted-modules-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943086 Title: linux-modules-nvidia-470-generic-hwe-20.04 dependency cant be installed Status in linux-restricted-modules-hwe-5.11 package in Ubuntu: New Bug description: linux-modules-nvidia-470-generic-hwe-20.04=5.11.0-34.36~20.04.1 depends on nvidia-kernel-common-470 (>= 470.63.01) but that version is not published, the latest one available today is 470.57.02-0ubuntu0.20.04.1 That means that installing latest hwe kernel for 20.04 breaks nvidia driver. This is problematic in distros like Elementary OS 6 as they dont expose the grub menu, so you have the latest kernel version installed only, which will not be able to boot on the graphical interface because there is no driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.11/+bug/1943086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943086] Re: linux-modules-nvidia-470-generic-hwe-20.04 dependency cant be installed
looking at https://bugs.launchpad.net/ubuntu/focal/amd64/nvidia-kernel- common-470 it seems that the 470.63.01 is only in the proposed repository, while the other changes landed in the update/security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943086 Title: linux-modules-nvidia-470-generic-hwe-20.04 dependency cant be installed Status in linux-restricted-modules-hwe-5.11 package in Ubuntu: New Bug description: linux-modules-nvidia-470-generic-hwe-20.04=5.11.0-34.36~20.04.1 depends on nvidia-kernel-common-470 (>= 470.63.01) but that version is not published, the latest one available today is 470.57.02-0ubuntu0.20.04.1 That means that installing latest hwe kernel for 20.04 breaks nvidia driver. This is problematic in distros like Elementary OS 6 as they dont expose the grub menu, so you have the latest kernel version installed only, which will not be able to boot on the graphical interface because there is no driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.11/+bug/1943086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943079] [NEW] Installing latest linux-firmware (1.187.16) causes wifi interface to disappear
Public bug reported: Summary === Installing linux-firmware 1.187.16, which became available on 17th Aug 2021, caused my wifi interface to disappear after reboot. My machine: Lenovo T15 Gen2 CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 I tried force installing previous version 1.187.15, but that version isn't available! So, in the end, I rebooted into a live CD and re-installed the OS! In the newly installed OS, I just made sure to NOT select linux-firmware package in the list of available upgrades, and I will stick with version 1.187.15 till I have confidence there is better and working version. NOTE: On an older machine, with an older chipset, I did NOT experience this issue. Older machine: Lenovo x230 CPU: Intel(R) Core(TM) i5-3210M CPU Wifi: Centrino Advanced-N 6205 System == I'm running Linux Mint Edge, based on Ubuntu 20.04, but with upgraded kernel (5.11.0.34): lsb_release -rd Description:Linux Mint 20.2 Release:20.2 Package === apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 Candidate: 1.187.16 Version table: *** 1.187.16 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages Expected Upgrade to linux-firmware=1.187.16 Reboot. Wifi network Interface must continue to be available and functioning. What Happened = Upgrade to linux-firmware=1.187.16 Reboot. Wifi network interface disappeared. Therefore, cannot use wifi. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/1943079 Title: Installing latest linux-firmware (1.187.16) causes wifi interface to disappear Status in linux-firmware package in Ubuntu: New Bug description: Summary === Installing linux-firmware 1.187.16, which became available on 17th Aug 2021, caused my wifi interface to disappear after reboot. My machine: Lenovo T15 Gen2 CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 I tried force installing previous version 1.187.15, but that version isn't available! So, in the end, I rebooted into a live CD and re-installed the OS! In the newly installed OS, I just made sure to NOT select linux- firmware package in the list of available upgrades, and I will stick with version 1.187.15 till I have confidence there is better and working version. NOTE: On an older machine, with an older chipset, I did NOT experience this issue. Older machine: Lenovo x230 CPU: Intel(R) Core(TM) i5-3210M CPU Wifi: Centrino Advanced-N 6205 System == I'm running Linux Mint Edge, based on Ubuntu 20.04, but with upgraded kernel (5.11.0.34): lsb_release -rd Description: Linux Mint 20.2 Release: 20.2 Package === apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 Candidate: 1.187.16 Version table: *** 1.187.16 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages Expected Upgrade to linux-firmware=1.187.16 Reboot. Wifi network Interface must continue to be available and functioning. What Happened = Upgrade to linux-firmware=1.187.16 Reboot. Wifi network interface disappeared. Therefore, cannot use wifi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1943079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844858] Re: xhci_hcd 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xbe258880 flags=0x0000]
I am getting "device 2-8.1 not suspended yet" every few seconds in the dmesg log. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844858 Title: xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0xbe258880 flags=0x] Status in linux package in Ubuntu: Confirmed Bug description: Having activated iommu in AMD, the kernel generates a conflict and the USB 3.0 ports on the VIA VL805 Chip on the GA-970A-DS3P board do not work, in addition to delaying the boot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.12 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.415 CrashDB: ubuntu CurrentDesktop: KDE Date: Sat Sep 21 10:37:11 2019 LiveMediaBuild: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190921) PackageArchitecture: all ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kubuntu5276 F pulseaudio /dev/snd/controlC0: kubuntu5276 F pulseaudio /dev/snd/pcmC0D0p: kubuntu5276 F...m pulseaudio CasperVersion: 1.415 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 IwConfig: enp3s0no wireless extensions. lono wireless extensions. LiveMediaBuild: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190921) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 RfKill: Tags: eoan Uname: Linux 5.3.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FD dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-DS3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFD:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-DS3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844858] Re: xhci_hcd 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xbe258880 flags=0x0000]
I am seeing something very similar: zář 08 21:17:28 amber2 kernel: hub 2-8:1.0: hub_ext_port_status failed (err = -110) zář 08 21:17:42 amber2 kernel: usb 2-8: Failed to suspend device, error -110 zář 08 21:17:43 amber2 kernel: xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0xbc15f578 flags=0x0020] zář 08 21:17:43 amber2 kernel: xhci_hcd :02:00.0: WARN Event TRB for slot 2 ep 0 with no TDs queued? zář 08 21:17:47 amber2 kernel: xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0xb127d468 flags=0x0020] zář 08 21:17:47 amber2 kernel: xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 0 comp_code 1 zář 08 21:17:47 amber2 kernel: xhci_hcd :02:00.0: Looking for event-dma fecaf120 trb-start fecaf2c0 trb-end fecaf340 seg-start fecaf000 seg-end fecafff0 zář 08 21:17:49 amber2 kernel: hub 2-8:1.0: hub_ext_port_status failed (err = -110) zář 08 21:17:51 amber2 kernel: usb 2-8.1: Port disable: can't disable remote wake zář 08 21:17:53 amber2 kernel: usb 2-8-port1: cannot disable (err = -110) zář 08 21:17:53 amber2 kernel: usb 2-8-port1: device 2-8.1 not suspended yet Description:Ubuntu 21.04 Release:21.04 Codename: hirsute Linux amber2 5.11.0-34-lowlatency #36-Ubuntu SMP PREEMPT Thu Aug 26 20:55:33 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844858 Title: xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0xbe258880 flags=0x] Status in linux package in Ubuntu: Confirmed Bug description: Having activated iommu in AMD, the kernel generates a conflict and the USB 3.0 ports on the VIA VL805 Chip on the GA-970A-DS3P board do not work, in addition to delaying the boot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.12 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.415 CrashDB: ubuntu CurrentDesktop: KDE Date: Sat Sep 21 10:37:11 2019 LiveMediaBuild: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190921) PackageArchitecture: all ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kubuntu5276 F pulseaudio /dev/snd/controlC0: kubuntu5276 F pulseaudio /dev/snd/pcmC0D0p: kubuntu5276 F...m pulseaudio CasperVersion: 1.415 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 IwConfig: enp3s0no wireless extensions. lono wireless extensions. LiveMediaBuild: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190921) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 RfKill: Tags: eoan Uname: Linux 5.3.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FD dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-DS3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFD:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-DS3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1814481] Re: Keychron K1 keyboard not working
I was having the same issue on the Vissles 84 mech keyboard, but https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/comments/19 mostly fixed it. F11 & F12 don't seem to be affected by the fix, they still act as multimedia volume keys regardless of whether I hold the fn key or not. To clarify, my keyboard is also bluetooth but I use it wired due to hardware issues on the linux PC. I am a VERY recent Linux user. My problem was pretty much the same as OP: no fn keys, they only registered as multimedia even with the fn key held. No fix in BIOS. I used the same keyboard on a windows computer and it worked fine. Anyway, thanks! Was nervous since I don't know too much about the command line yet, but it seems mostly fixed now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: Keychron K1 keyboard not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: I recently got a nice mechanical bluetooth keyboard to use on my thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04 live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it only works after calling `sudo evtest /dev/input/eventN`. Xorg.0.log shows it is detected fine, and I can't see anything there after temporarily getting it to work using the evtest trick. 18.515] (II) config/udev: Adding input device Keychron K1 (/dev/input/event23) [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.515] (II) Using input driver 'libinput' for 'Keychron K1' [18.515] (**) Keychron K1: always reports core events [18.515] (**) Option "Device" "/dev/input/event23" [18.515] (**) Option "_source" "server/udev" [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.516] (II) event23 - Keychron K1: device is a keyboard [18.516] (II) event23 - Keychron K1: device removed [18.524] (II) libinput: Keychron K1: needs a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: MOUSE, id 20) [18.524] (**) Option "AccelerationScheme" "none" [18.524] (**) Keychron K1: (accel) selected scheme none/0 [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000 [18.524] (**) Keychron K1: (accel) acceleration threshold: 4 [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.524] (II) event23 - Keychron K1: device is a keyboard [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.524] (II) Using input driver 'libinput' for 'Keychron K1' [18.524] (**) Keychron K1: always reports core events [18.524] (**) Option "Device" "/dev/input/event23" [18.524] (**) Option "_source" "_driver/libinput" [18.524] (II) libinput: Keychron K1: is a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: KEYBOARD, id 21) [18.524] (**) Option "xkb_model" "pc105" [18.524] (**) Option "xkb_layout" "us" [18.524] (**) Option "xkb_variant" "altgr-intl" [18.524] (WW) Option "xkb_options" requires a string value I've also tried using the latest 4.20.6 from mainline-ppa and the latest bluetooth/bluz ppa without success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18 Uname: Linux 4.15.0-45-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Feb 3 23:51:29 2019 DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2017-07-24 (559 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
[Kernel-packages] [Bug 1814481] Re: Keychron K1 keyboard not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) 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/1814481 Title: Keychron K1 keyboard not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: I recently got a nice mechanical bluetooth keyboard to use on my thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04 live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it only works after calling `sudo evtest /dev/input/eventN`. Xorg.0.log shows it is detected fine, and I can't see anything there after temporarily getting it to work using the evtest trick. 18.515] (II) config/udev: Adding input device Keychron K1 (/dev/input/event23) [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.515] (II) Using input driver 'libinput' for 'Keychron K1' [18.515] (**) Keychron K1: always reports core events [18.515] (**) Option "Device" "/dev/input/event23" [18.515] (**) Option "_source" "server/udev" [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.516] (II) event23 - Keychron K1: device is a keyboard [18.516] (II) event23 - Keychron K1: device removed [18.524] (II) libinput: Keychron K1: needs a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: MOUSE, id 20) [18.524] (**) Option "AccelerationScheme" "none" [18.524] (**) Keychron K1: (accel) selected scheme none/0 [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000 [18.524] (**) Keychron K1: (accel) acceleration threshold: 4 [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.524] (II) event23 - Keychron K1: device is a keyboard [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.524] (II) Using input driver 'libinput' for 'Keychron K1' [18.524] (**) Keychron K1: always reports core events [18.524] (**) Option "Device" "/dev/input/event23" [18.524] (**) Option "_source" "_driver/libinput" [18.524] (II) libinput: Keychron K1: is a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: KEYBOARD, id 21) [18.524] (**) Option "xkb_model" "pc105" [18.524] (**) Option "xkb_layout" "us" [18.524] (**) Option "xkb_variant" "altgr-intl" [18.524] (WW) Option "xkb_options" requires a string value I've also tried using the latest 4.20.6 from mainline-ppa and the latest bluetooth/bluz ppa without success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18 Uname: Linux 4.15.0-45-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Feb 3 23:51:29 2019 DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2017-07-24 (559 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago) dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.version:
[Kernel-packages] [Bug 1943070] Re: linux-aws: Missing check for CONFIG_SUSPEND in amdgpu_acpi.c
** Description changed: SRU Justification [Impact] A missing check in drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c causes a link error when CONFIG_SUSPEND=n ERROR: modpost: "pm_suspend_target_state" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! - This issue was introduced by an upstream stable update. + This issue was introduced by an upstream stable update (commit + 5706cb3c910cc8283f344bc37a889a8d523a2c6d upstream). [Test Plan] Successfully build and link. [Where problems could occur] This is a build time issue. No run time regression is possible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1943070 Title: linux-aws: Missing check for CONFIG_SUSPEND in amdgpu_acpi.c Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Hirsute: New Bug description: SRU Justification [Impact] A missing check in drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c causes a link error when CONFIG_SUSPEND=n ERROR: modpost: "pm_suspend_target_state" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! This issue was introduced by an upstream stable update (commit 5706cb3c910cc8283f344bc37a889a8d523a2c6d upstream). [Test Plan] Successfully build and link. [Where problems could occur] This is a build time issue. No run time regression is possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1943070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942619] Re: WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]
This happened again today. I have discovered that recovery by suspend/resume is possible. ** Summary changed: - WARNING: CPU: 11 PID: 3608 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:2529 decide_link_settings+0x1ab/0x1d0 [amdgpu] + WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942619 Title: WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu] Status in linux package in Ubuntu: Confirmed Bug description: This has hit me twice in the last 24 hours. Displays come in and out of power saving, without actually displaying anything. The console doesn't become usable. It seems to be unrecoverable, shutdown gets stuck somewhere and I end up having to hit the reset button. This is a desktop machine, which suspends frequently, usually without issue. Radeon RX 570, dual monitor, display link ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.31.33 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 10:11:35 2021 InstallationDate: Installed on 2019-06-18 (808 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-09 (116 days ago) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943070] [NEW] linux-aws: Missing check for CONFIG_SUSPEND in amdgpu_acpi.c
Public bug reported: SRU Justification [Impact] A missing check in drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c causes a link error when CONFIG_SUSPEND=n ERROR: modpost: "pm_suspend_target_state" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! This issue was introduced by an upstream stable update. [Test Plan] Successfully build and link. [Where problems could occur] This is a build time issue. No run time regression is possible. ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Hirsute) Importance: Undecided Status: New ** Tags: bot-stop-nagging ** Also affects: linux-aws (Ubuntu Hirsute) Importance: Undecided Status: New ** Tags added: bot-stop-nagging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1943070 Title: linux-aws: Missing check for CONFIG_SUSPEND in amdgpu_acpi.c Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Hirsute: New Bug description: SRU Justification [Impact] A missing check in drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c causes a link error when CONFIG_SUSPEND=n ERROR: modpost: "pm_suspend_target_state" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! This issue was introduced by an upstream stable update. [Test Plan] Successfully build and link. [Where problems could occur] This is a build time issue. No run time regression is possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1943070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942060] Re: ath11k firmware and driver crash
This bug is also present in linux-image-5.13.0-1012-oem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1942060 Title: ath11k firmware and driver crash Status in linux-signed-oem-5.10 package in Ubuntu: New Bug description: When connecting with WLAN, the firmware and driver keeps crashing with kernel 5.10.0-1044-oem. This happens in an environment with many WLANs when connecting to a certain AP. It works OK with kernel 5.6.0.1047-oem. In other locations, WLAN works OK with the 5.10.0-1044-oem kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1044-oem 5.10.0-1044.46 ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19 Uname: Linux 5.6.0-1047-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 30 10:04:30 2021 InstallationDate: Installed on 2021-08-25 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1942060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
Can you provide steps to reproduce the issue you're seeing? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Xenial: New Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: New Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943066] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943066 Title: Speakup modules are not included in the kernel. These modulles are essential for blind systems administrators because they provide access to boot messages. Status in linux package in Ubuntu: Confirmed Bug description: b ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1777 F pulseaudio /dev/snd/pcmC0D0p: john 1777 F...m pulseaudio /dev/snd/controlC1: john 1777 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Sep 8 11:57:55 2021 InstallationDate: Installed on 2021-08-25 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=de5924a4-e0f6-4c11-a364-ea107efc1086 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2018 dmi.bios.release: 65.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd12/13/2018:br65.29:svnDellInc.:pnPrecisionTower5810:pvr:sku0617:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.product.sku: 0617 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942060] Re: ath11k firmware and driver crash
This bug is still present in linux-image-5.10.0-1045-oem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1942060 Title: ath11k firmware and driver crash Status in linux-signed-oem-5.10 package in Ubuntu: New Bug description: When connecting with WLAN, the firmware and driver keeps crashing with kernel 5.10.0-1044-oem. This happens in an environment with many WLANs when connecting to a certain AP. It works OK with kernel 5.6.0.1047-oem. In other locations, WLAN works OK with the 5.10.0-1044-oem kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1044-oem 5.10.0-1044.46 ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19 Uname: Linux 5.6.0-1047-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 30 10:04:30 2021 InstallationDate: Installed on 2021-08-25 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1942060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943066] [NEW] Speakup modules are not included in the kernel. These modulles are essential for blind systems administrators because they provide access to boot messages.
Public bug reported: b ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1777 F pulseaudio /dev/snd/pcmC0D0p: john 1777 F...m pulseaudio /dev/snd/controlC1: john 1777 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Sep 8 11:57:55 2021 InstallationDate: Installed on 2021-08-25 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=de5924a4-e0f6-4c11-a364-ea107efc1086 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2018 dmi.bios.release: 65.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd12/13/2018:br65.29:svnDellInc.:pnPrecisionTower5810:pvr:sku0617:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.product.sku: 0617 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943066 Title: Speakup modules are not included in the kernel. These modulles are essential for blind systems administrators because they provide access to boot messages. Status in linux package in Ubuntu: New Bug description: b ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1777 F pulseaudio /dev/snd/pcmC0D0p: john 1777 F...m pulseaudio /dev/snd/controlC1: john 1777 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Sep 8 11:57:55 2021 InstallationDate: Installed on 2021-08-25 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=de5924a4-e0f6-4c11-a364-ea107efc1086 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2018 dmi.bios.release: 65.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd12/13/2018:br65.29:svnDellInc.:pnPrecisionTower5810:pvr:sku0617:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.product.sku: 0617 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943065] [NEW] mlxbf_gige: update driver version to 1.25
Public bug reported: SRU Justification: [Impact] * The mlxbf_gige driver needs a version increase to identify a driver containing recent important bug fixes. [Fix] * The driver version implemented by the DRV_VERSION define and MODULE_VERSION macro will be incremented from 1.24 to 1.25 [Test Case] * To test this fix, need to check the driver version shown in the output of "modinfo mlxbf_gige" command. [Regression Potential] * There is low risk of this fix causing any problems. [Other] * The mlxbf_gige driver will display v1.25 in modinfo after these changes. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1943065 Title: mlxbf_gige: update driver version to 1.25 Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] * The mlxbf_gige driver needs a version increase to identify a driver containing recent important bug fixes. [Fix] * The driver version implemented by the DRV_VERSION define and MODULE_VERSION macro will be incremented from 1.24 to 1.25 [Test Case] * To test this fix, need to check the driver version shown in the output of "modinfo mlxbf_gige" command. [Regression Potential] * There is low risk of this fix causing any problems. [Other] * The mlxbf_gige driver will display v1.25 in modinfo after these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1943065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941657] Re: Server boot failure after adding checks for ACPI IRQ override
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1941657
Title:
Server boot failure after adding checks for ACPI IRQ override
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Bug description:
SRU Justification:
Impact:
The commit 0ec4e55e9f57 ("ACPI: resources: Add checks for ACPI IRQ
override") introduces regression on some platforms, at least it makes
the UART can't get correct irq setting on two different platforms, and
it makes the kernel can't bootup on these two platforms.
discussion regarding the regression:
https://bugzilla.kernel.org/show_bug.cgi?id=213031#c32
Fix: Revert "ACPI: resources: Add checks for ACPI IRQ override"
Risk: Reverting this patch will keep LP#1909814 ("Keyboard not working")
unfixed.
https://launchpad.net/bugs/1909814
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911360] Re: Nvidia-Graphics-Drivers-460 Causes System To Not Boot
Hi, I also received the error. I tried to deploy Dell Precision 5560 via MAAS Server. I used LTS Kernel 5.4.0-84-generic. Unfortunately deployment is freeze on hdaudio hdaudioC0D2: Unable to bind codec. I changed kernel version during deployment for hwe. Everything works fine. Unfortunately I'm not able to use hwe kernel version (short time support so only 6 months). With LTS I'm not able to deploy Ubuntu 20.04 on Dell Precision 5560 with T1200 Graphic card. Any suggestions for this one? Let me know if you need to have more logs or details, I'm able to provide that one. ** Also affects: maas-deployer Importance: Undecided Status: New -- 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/1911360 Title: Nvidia-Graphics-Drivers-460 Causes System To Not Boot Status in maas-deployer: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: After installing version 460, my 18.04 laptop stopping booting. Error reported: hdaudio hdaudioC0D2: Unable to bind codec. If I boot to grub, press 'e' and remove nomodeset, the systems boots normally. sudo lshw -C display *-display UNCLAIMED description: VGA compatible controller product: GM107GLM [Quadro M1000M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller cap_list configuration: latency=0 resources: memory:dc00-dcff memory:b000-bfff memory:c000-c1ff ioport:e000(size=128) memory:dd00-dd07 *-display UNCLAIMED description: VGA compatible controller product: HD Graphics P530 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list configuration: latency=0 resources: memory:db00-dbff memory:7000-7fff ioport:f000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/maas-deployer/+bug/1911360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
My assessment of the reason appears to be wrong, USB storage at boot time isn't working for me under 5.13, but the modules seem like they're present. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Xenial: New Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: New Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
I think this is affecting the latest 5.13 kernels, the usb-storage modules appear to be missing, and USB storage isn't working, I get the device detected when I plug it in, but modules to use it are missing since the 5.13 update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Xenial: New Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: New Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942991] Re: zfs: can't read /proc/sys/kernel/spl/hostid
This bug was fixed in the package zfs-linux - 2.0.3-8ubuntu8
---
zfs-linux (2.0.3-8ubuntu8) impish; urgency=medium
* Fix /proc/sys/kernel/spl/hostid (LP: #1942991)
- 4750-linux-spl-base-proc_dohostid-on-proc_dostring.patch
* Fix build issues with latest tool updates:
- 4751-suppress-regex_t.patch
* Move 470* patches to debian/ubuntu
-- Colin Ian King Tue, 7 Sep 2021 19:08:23
+0100
** Changed in: zfs-linux (Ubuntu Impish)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1942991
Title:
zfs: can't read /proc/sys/kernel/spl/hostid
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Hirsute:
In Progress
Status in zfs-linux source package in Impish:
Fix Released
Bug description:
[Impact]
Reading /proc/sys/kernel/spl/hostid no longer works in 5.7+ kernels
upwards.
The Fix:
commit 7de4c88b39473f358add601e8c227ca9002b1bee
Author: наб
Date: Sun Apr 11 01:18:40 2021 +0200
linux/spl: base proc_dohostid() on proc_dostring()
This fixes /proc/sys/kernel/spl/hostid on kernels with mainline commit
32927393dc1ccd60fb2bdc05b9e8e88753761469 ("sysctl: pass kernel pointers
to ->proc_handler") ‒ 5.7-rc1 and up
The access_ok() check in copy_to_user() in proc_copyout_string() would
always fail, so all userspace reads and writes would fail with EINVAL
proc_dostring() strips only the final new-line,
but simple_strtoul() doesn't actually need a back-trimmed string ‒
writing "012345678 \n" is still allowed, as is "012345678zupsko",
This alters what happens when an invalid value is written ‒
previously it'd get set to what-ever simple_strtoul() returned
(probably 0, thereby resetting it to default), now it does nothing
Reviewed-by: Brian Behlendorf
Signed-off-by: Ahelenia Ziemiańska
Closes #11878
Closes #11879
This applies cleanly for Impish and Hirsute 2.x ZFS so backporting is
straight forward.
[Test Plan]
cat /proc/sys/kernel/spl/hostid fails without the fix. With the fix it
returns a hex string of the hostid value.
[Where problems could occur]
This affects just a few /proc spl interfaces so the change is a low-
impact fix. Not many folk even use these and nobody has reported this
as a bug so the number of affected users is expected to be very small.
I suspect nobody is reading the hostid from /proc as this information
is available elsewhere and it's rather an old legacy interface.
The affected change is from upstream ZFS 2.x hence the patch applies
cleanly.
This fix has been in upstream ZFS for several months with no reported
regressions.
The change does not affect any core ZFS functionality.
Regression tested against the Ubuntu ZFS regression test suite and
passed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1942991/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set
Confirmed, I see many instances of the same. Trace below, can post anything else required. [16772.065057] WARNING: CPU: 4 PID: 12381 at build/nvidia/470.57.02/build/nvidia-drm/nvidia-drm-drv.c:574 nv_drm_master_set+0x27/0x30 [nvidia_drm] [16772.065067] Modules linked in: nvidia_uvm(PO) nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic intel_rapl_msr snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc mei_hdcp snd_sof snd_hda_codec_hdmi snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio intel_rapl_common snd_hda_intel x86_pkg_temp_thermal intel_powerclamp snd_intel_dspcfg nvidia_drm(PO) soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec snd_hda_core soundwire_bus nvidia_modeset(PO) snd_usb_audio kvm_intel snd_soc_core snd_usbmidi_lib snd_compress snd_hwdep r8153_ecm snd_seq_midi ac97_bus snd_seq_midi_event kvm cdc_ether snd_pcm_dmaengine usbnet snd_rawmidi mc r8152 snd_seq intel_cstate efi_pstore eeepc_wmi wmi_bmof ee1004 mii snd_pcm nvidia(PO) input_leds snd_seq_device joydev snd_timer snd mei_me soundcore mei sch_fq_codel nct6775 hwmon_vid coretemp msr mac_hid acpi_pad acpi_tad parport_pc ppdev lp [16772.065155] parport ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid uas usb_storage i915 asus_wmi sparse_keymap mfd_aaeon i2c_algo_bit crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel syscopyarea aesni_intel sysfillrect sysimgblt fb_sys_fops crypto_simd cec cryptd glue_helper rc_core e1000e i2c_i801 drm i2c_smbus nvme intel_lpss_pci ahci intel_lpss nvme_core idma64 xhci_pci libahci virt_dma xhci_pci_renesas wmi video pinctrl_tigerlake [16772.065208] CPU: 4 PID: 12381 Comm: gpu-manager Tainted: PW O 5.11.0-31-generic #33-Ubuntu [16772.065211] Hardware name: ASUS System Product Name/PRIME B560M-A, BIOS 0820 04/27/2021 [16772.065213] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm] [16772.065220] Code: c0 f8 be 0f 1f 44 00 00 55 48 8b 47 48 48 8b 78 20 48 8b 05 bb 6c 00 00 48 89 e5 48 8b 40 28 e8 0f 30 35 bf 84 c0 74 02 5d c3 <0f> 0b 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 [16772.065224] RSP: 0018:b649855cfb80 EFLAGS: 00010246 [16772.065227] RAX: RBX: 97e21cf48600 RCX: 0008 [16772.065229] RDX: c31ffed8 RSI: 0292 RDI: c31ffea0 [16772.065231] RBP: b649855cfb80 R08: 0008 R09: b649855cfb68 [16772.065233] R10: R11: 97e100459ff2 R12: 97e2a7f33cc0 [16772.065235] R13: 97e117089800 R14: R15: 97e117089800 [16772.065237] FS: 7fe249a08c80() GS:97e44f50() knlGS: [16772.065240] CS: 0010 DS: ES: CR0: 80050033 [16772.065243] CR2: 7fe249de1340 CR3: 0002195bc001 CR4: 00770ee0 [16772.065245] PKRU: 5554 [16772.065247] Call Trace: [16772.065249] drm_new_set_master+0x7e/0x100 [drm] [16772.065281] drm_master_open+0x6e/0xa0 [drm] [16772.065311] drm_open+0xf8/0x250 [drm] [16772.065343] drm_stub_open+0xba/0x140 [drm] [16772.065380] chrdev_open+0xf7/0x220 [16772.065386] ? cdev_device_add+0x90/0x90 [16772.065391] do_dentry_open+0x156/0x370 [16772.065396] vfs_open+0x2d/0x30 [16772.065402] do_open+0x1c3/0x340 [16772.065407] path_openat+0x10a/0x1d0 [16772.065412] do_filp_open+0x8c/0x130 [16772.065418] ? __check_object_size+0x1c/0x20 [16772.065423] do_sys_openat2+0x9b/0x150 [16772.065429] __x64_sys_openat+0x56/0x90 [16772.065435] do_syscall_64+0x38/0x90 [16772.065438] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [16772.065443] RIP: 0033:0x7fe249ea28db [16772.065446] Code: 25 00 00 41 00 3d 00 00 41 00 74 4b 64 8b 04 25 18 00 00 00 85 c0 75 67 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 91 00 00 00 48 8b 4c 24 28 64 48 2b 0c 25 [16772.065449] RSP: 002b:7ffd5aa4e8d0 EFLAGS: 0246 ORIG_RAX: 0101 [16772.065453] RAX: ffda RBX: 0001 RCX: 7fe249ea28db [16772.065456] RDX: 0002 RSI: 7ffd5aa4e9a0 RDI: ff9c [16772.065458] RBP: 7ffd5aa4e9a0 R08: R09: 7ffd5aa4e7e0 [16772.065460] R10: R11: 0246 R12: 0002 [16772.065462] R13: R14: R15: [16772.065467] ---[ end trace 35075447560cdf42 ]--- -- 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/1930903 Title: Frequent kernel oops related to nvidia / nv_drm_master_set Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: After upgrading yesterday from ubuntu 20 to 21.04 my machine now exhibits frequent involuntary restarts, related to a kernel oops of the form Jun 3 10:48:32 zotac
[Kernel-packages] [Bug 1943043] [NEW] Multiple CPUs stuck at 100% usage
Public bug reported: System boots fine, but after several hours, a random process will consume 100% CPU (all kernel time), if the pi is left on longer, this will happen to more cpus. At the same time the interrupt count for "fe00b880.mailbox" drops dramatically. Kernel stacktrace seems to point to an exception happening in scheduling: [<0>] __switch_to+0xb8/0xe4 [<0>] function_trace+0x98/0x98 [<0>] do_translation_fault+0x64/0x9c [<0>] do_mem_abort+0x4c/0xbc [<0>] el1_abort+0x74/0xf4 [<0>] el1_sync_handler+0xac/0xcc [<0>] el1_sync+0x7c/0x100 [<0>] schedule_tail+0x130/0x200 [<0>] ret_from_fork+0x4/0x3c System is booting from NFS over the build in ethernet - so its going to have a lot of NIC traffic. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-1016-raspi 5.11.0-1016.17 ProcVersionSignature: Ubuntu 5.11.0-1016.17-raspi 5.11.22 Uname: Linux 5.11.0-1016-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Sep 8 13:30:28 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.11.0-1017-raspi linux-base SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-07-15T11:07:35.169244 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 hirsute uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1943043 Title: Multiple CPUs stuck at 100% usage Status in linux-raspi package in Ubuntu: New Bug description: System boots fine, but after several hours, a random process will consume 100% CPU (all kernel time), if the pi is left on longer, this will happen to more cpus. At the same time the interrupt count for "fe00b880.mailbox" drops dramatically. Kernel stacktrace seems to point to an exception happening in scheduling: [<0>] __switch_to+0xb8/0xe4 [<0>] function_trace+0x98/0x98 [<0>] do_translation_fault+0x64/0x9c [<0>] do_mem_abort+0x4c/0xbc [<0>] el1_abort+0x74/0xf4 [<0>] el1_sync_handler+0xac/0xcc [<0>] el1_sync+0x7c/0x100 [<0>] schedule_tail+0x130/0x200 [<0>] ret_from_fork+0x4/0x3c System is booting from NFS over the build in ethernet - so its going to have a lot of NIC traffic. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-1016-raspi 5.11.0-1016.17 ProcVersionSignature: Ubuntu 5.11.0-1016.17-raspi 5.11.22 Uname: Linux 5.11.0-1016-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Sep 8 13:30:28 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.11.0-1017-raspi linux-base SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-07-15T11:07:35.169244 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1943043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943039] [NEW] Touchpad and/or keyboard stop working after some time
Public bug reported: I have a DELL XPS and since several weeks, after some time after login the touchpad (but also mouse when I connect a mouse) stops working. Sometimes, the keyboard also stops working. Before that, it almost always make a random right clic for no reason. I have been waiting for some updates to solve the issue but it did not happen. I know this issue may be common and I looked over the internet to find a solution but I did not.. Note that when booting I also have the following message: psmouse serio1: Failed to disable mouse on isa0060/serio1 which may be related to the issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 22:04:33 2021 InstallationDate: Installed on 2021-02-09 (210 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943039 Title: Touchpad and/or keyboard stop working after some time Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I have a DELL XPS and since several weeks, after some time after login the touchpad (but also mouse when I connect a mouse) stops working. Sometimes, the keyboard also stops working. Before that, it almost always make a random right clic for no reason. I have been waiting for some updates to solve the issue but it did not happen. I know this issue may be common and I looked over the internet to find a solution but I did not.. Note that when booting I also have the following message: psmouse serio1: Failed to disable mouse on isa0060/serio1 which may be related to the issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 22:04:33 2021 InstallationDate: Installed on 2021-02-09 (210 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic
Found with hirsute/linux 5.11.0-35.37 on node rizzo (amd64). ** Tags added: 5.11 hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836694 Title: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 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 Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830585] Re: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node)
Found with hirsute/linux 5.11.0-35.37 on node kili. ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Tags added: hirsute sru-20210906 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1830585 Title: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node) Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Focal: New Status in linux-azure source package in Focal: New Status in linux source package in Hirsute: New Status in linux-azure source package in Hirsute: New Bug description: Test failed with: cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected node(FilePages_For_Nodes(KB): _0: 2276 _1: 102428, Expect Nodes: 1). <<>> tag=cpuset_memory_spread stime=1558937747 cmdline=" cpuset_memory_spread_testset.sh" contacts="" analysis=exit <<>> 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 0.0993112 s, 1.1 GB/s cpuset_memory_spread 1 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 3 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 5 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected node(FilePages_For_Nodes(KB): _0: 2276 _1: 102428, Expect Nodes: 1). cpuset_memory_spread 9 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 11 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 13 TPASS: Cpuset memory spread page test succeeded. <<>> initiation_status="ok" duration=10 termination_type=exited termination_id=1 corefile=no cutime=364 cstime=383 <<>> ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 05:39 seq crw-rw 1 root audio 116, 33 May 27 05:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 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: Mon May 27 06:16:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value
@Colin, please excuse my late response. Version 1.9.1-1ubuntu0.5 unfortunately shows the same behavior. My colleague switched to the self compiled version again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Incomplete Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre
[Kernel-packages] [Bug 1943030] [NEW] Enable riscv64 build of nvidia-settings
Public bug reported: Please enable the build on riscv64 architecture of nvidia-settings since it works fine using the attached debdiff: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736 ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Attachment added: "nvidia_settings_debdiff.patch" https://bugs.launchpad.net/bugs/1943030/+attachment/5523773/+files/nvidia_settings_debdiff.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1943030 Title: Enable riscv64 build of nvidia-settings Status in nvidia-settings package in Ubuntu: New Bug description: Please enable the build on riscv64 architecture of nvidia-settings since it works fine using the attached debdiff: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline
Thx Harald for the verification (adjusting the tags accordingly ...)
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1939618
Title:
CryptoExpress EP11 cards are going offline
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification:
[Impact]
* With current focal kernels IBM Z CryptoExpress adapters in EP11 mode
go offline in case of unknown error indications from the hardware.
* This does not only lead to a software fallback, but can also lead to errors
and crashes,
if certain crypto operations are currently ongoing.
* A rework of the AP bus and zcrypt device driver, as it was done in
5.11, fixes the situation.
* From the below range of commits, the last 1/3 are the ones that fix the
issue mentioned here
and the others are pre-requisites to get the relevant ones applied.
* In theory the patch set could have been made smaller,
but with the cost that the code would be a mix between old and new, with
maybe some new code snippets,
hence it would divert from what's upstream accepted (in 5.11 and above),
the risk would increase,
increased effort to maintain and less test coverage.
[Fix]
* The SRU request was created as pull request,
so please pull f904c400c9c4^..f6d9ab1de03a (means starting at f904c400c9c4
{incl.} to head/f6d9ab1de03a {incl.})
from here: https://code.launchpad.net/~fheimes/+git/lp1939618
[Test Case]
* An Ubuntu Server 20.04 on IBM Z or LinuxONE installation is required,
with ideally three attached CryptoExpress adapters running in CCA, EP11 and
accelerator mode.
* Run stress test on these three CryptoExpress adapters.
* IBM has such stress tests and ran these based on a patched Ubuntu 20.04
kernel.
The tests come with a specially focus on error path tests,
since this patch set mainly focuses on doing a better error patch handling.
* Note: A a new config option for the zcrypt driver was introduced
that enables the possibility to inject erroneous messages.
* An application exists that generates such messages and thus tests
these error paths.
* Canonical's focus will mainly be on regression testing.
[Regression Potential]
* Like with all modification there is a certain risk of regressions,
especially with bigger patch sets.
* But the modifications here are limited to the s390x platform,
and there again largely to the s390x hardware crypto stack and driver
(CryptoExpress adapter) which is optional hardware.
(See the diff stat in the comment below.)
* The crypto-specific tools (located at the s390-tools package) may no longer
work with this patched driver.
But this got tested by IBM with the result that the changes are fully
backward compatible.
The 'older' s390 tools package (from focal) can just not show and control
the new (config state) feature,
but the functionality covered by the older s390 tools package is utterly
covered by this patch set.
* The core of this patch set went into the 5.11 kernel upstream,
hence is in hirsute (and has also been picked by other distros).
* Since this patch set is a rework of the AP bus and zcrypt driver code,
it may now show new errors that were never thrown before, like for or
example memory leaks.
However, this is not unique to this patch set, it the same for upstream,
Hirsute and Impish (and other distros).
* The patches are all upstream and all needed upstream commits could just be
cherry-picked,
hence no modifications were needed.
* So the commits were not only tested by IBM upfront,
but a patched focal master-next kernel is also available as PPA (see
comment below) for further testing.
* This patch set was also tested on 5.11, where two issues were found
that are already part of this set.
[Other]
* I iterated through all commits and found that that the latest ones got
upstream with 5.13,
hence Impish includes all commits needed and is not affected!
* Looks like all commits, expect three, are even upstream with 5.11,
but the missing three came in on top via upstream stable,
hence Hirsute master-next includes all commits needed too and is also not
affected!
* But non of the commits could be found in current Focal master-next (aot:
5.4.0-84),
the first commits from this set started to land with 5.7,
hence this SRU request is for focal only.
__
Here is the backport against current git for ubuntu 20.04.
It is a zip file with a patches subdir and all the patches in there together
with a series file. So just unpack it and
[Kernel-packages] [Bug 1939618] Comment bridged from LTC Bugzilla
--- Comment From fre...@de.ibm.com 2021-09-08 06:10 EDT---
I cloned the kernel as indicated with comment #18 and did
- check out the only branch master-next
- a code verification for the subdir drivers/s390/crypto
I compared this with an upstream kernel and checked that all the patches
are applied correctly and that the code level is showing what I would expect
and nothing more. Looks good to me.
- kernel build and install and ran my internal ap/zcrypt test suite.
No issues found - looks good to me.
So I assume this is verified now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1939618
Title:
CryptoExpress EP11 cards are going offline
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification:
[Impact]
* With current focal kernels IBM Z CryptoExpress adapters in EP11 mode
go offline in case of unknown error indications from the hardware.
* This does not only lead to a software fallback, but can also lead to errors
and crashes,
if certain crypto operations are currently ongoing.
* A rework of the AP bus and zcrypt device driver, as it was done in
5.11, fixes the situation.
* From the below range of commits, the last 1/3 are the ones that fix the
issue mentioned here
and the others are pre-requisites to get the relevant ones applied.
* In theory the patch set could have been made smaller,
but with the cost that the code would be a mix between old and new, with
maybe some new code snippets,
hence it would divert from what's upstream accepted (in 5.11 and above),
the risk would increase,
increased effort to maintain and less test coverage.
[Fix]
* The SRU request was created as pull request,
so please pull f904c400c9c4^..f6d9ab1de03a (means starting at f904c400c9c4
{incl.} to head/f6d9ab1de03a {incl.})
from here: https://code.launchpad.net/~fheimes/+git/lp1939618
[Test Case]
* An Ubuntu Server 20.04 on IBM Z or LinuxONE installation is required,
with ideally three attached CryptoExpress adapters running in CCA, EP11 and
accelerator mode.
* Run stress test on these three CryptoExpress adapters.
* IBM has such stress tests and ran these based on a patched Ubuntu 20.04
kernel.
The tests come with a specially focus on error path tests,
since this patch set mainly focuses on doing a better error patch handling.
* Note: A a new config option for the zcrypt driver was introduced
that enables the possibility to inject erroneous messages.
* An application exists that generates such messages and thus tests
these error paths.
* Canonical's focus will mainly be on regression testing.
[Regression Potential]
* Like with all modification there is a certain risk of regressions,
especially with bigger patch sets.
* But the modifications here are limited to the s390x platform,
and there again largely to the s390x hardware crypto stack and driver
(CryptoExpress adapter) which is optional hardware.
(See the diff stat in the comment below.)
* The crypto-specific tools (located at the s390-tools package) may no longer
work with this patched driver.
But this got tested by IBM with the result that the changes are fully
backward compatible.
The 'older' s390 tools package (from focal) can just not show and control
the new (config state) feature,
but the functionality covered by the older s390 tools package is utterly
covered by this patch set.
* The core of this patch set went into the 5.11 kernel upstream,
hence is in hirsute (and has also been picked by other distros).
* Since this patch set is a rework of the AP bus and zcrypt driver code,
it may now show new errors that were never thrown before, like for or
example memory leaks.
However, this is not unique to this patch set, it the same for upstream,
Hirsute and Impish (and other distros).
* The patches are all upstream and all needed upstream commits could just be
cherry-picked,
hence no modifications were needed.
* So the commits were not only tested by IBM upfront,
but a patched focal master-next kernel is also available as PPA (see
comment below) for further testing.
* This patch set was also tested on 5.11, where two issues were found
that are already part of this set.
[Other]
* I iterated through all commits and found that that the latest ones got
upstream with 5.13,
hence Impish includes all commits needed and is not affected!
* Looks like all commits, expect three, are even upstream with 5.11,
but the missing three came in on top via upstream stable,
hence Hirsute master-next includes all commits needed too and is also not
affected!
* But non of the commits could be found in current Focal master-next (aot:
[Kernel-packages] [Bug 1942991] Re: zfs: can't read /proc/sys/kernel/spl/hostid
** Description changed:
+ [Impact]
- Reading /proc/sys/kernel/spl/hostid no longer works in 5.7+ kernels
+ Reading /proc/sys/kernel/spl/hostid no longer works in 5.7+ kernels
upwards.
The Fix:
commit 7de4c88b39473f358add601e8c227ca9002b1bee
Author: наб
Date: Sun Apr 11 01:18:40 2021 +0200
+ linux/spl: base proc_dohostid() on proc_dostring()
- linux/spl: base proc_dohostid() on proc_dostring()
+ This fixes /proc/sys/kernel/spl/hostid on kernels with mainline commit
+ 32927393dc1ccd60fb2bdc05b9e8e88753761469 ("sysctl: pass kernel pointers
+ to ->proc_handler") ‒ 5.7-rc1 and up
- This fixes /proc/sys/kernel/spl/hostid on kernels with mainline commit
- 32927393dc1ccd60fb2bdc05b9e8e88753761469 ("sysctl: pass kernel pointers
- to ->proc_handler") ‒ 5.7-rc1 and up
+ The access_ok() check in copy_to_user() in proc_copyout_string() would
+ always fail, so all userspace reads and writes would fail with EINVAL
- The access_ok() check in copy_to_user() in proc_copyout_string() would
- always fail, so all userspace reads and writes would fail with EINVAL
+ proc_dostring() strips only the final new-line,
+ but simple_strtoul() doesn't actually need a back-trimmed string ‒
+ writing "012345678 \n" is still allowed, as is "012345678zupsko",
- proc_dostring() strips only the final new-line,
- but simple_strtoul() doesn't actually need a back-trimmed string ‒
- writing "012345678 \n" is still allowed, as is "012345678zupsko",
+ This alters what happens when an invalid value is written ‒
+ previously it'd get set to what-ever simple_strtoul() returned
+ (probably 0, thereby resetting it to default), now it does nothing
- This alters what happens when an invalid value is written ‒
- previously it'd get set to what-ever simple_strtoul() returned
- (probably 0, thereby resetting it to default), now it does nothing
+ Reviewed-by: Brian Behlendorf
+ Signed-off-by: Ahelenia Ziemiańska
+ Closes #11878
+ Closes #11879
- Reviewed-by: Brian Behlendorf
- Signed-off-by: Ahelenia Ziemiańska
- Closes #11878
- Closes #11879
+
+ This applies cleanly for Impish and Hirsute 2.x ZFS so backporting is
straight forward.
+
+ [Test Plan]
+
+ cat /proc/sys/kernel/spl/hostid fails without the fix. With the fix it
+ returns a hex string of the hostid value.
+
+ [Where problems could occur]
+
+ This affects just a few /proc spl interfaces so the change is a low-
+ impact fix. Not many folk even use these and nobody has reported this as
+ a bug so the number of affected users is expected to be very small. I
+ suspect nobody is reading the hostid from /proc as this information is
+ available elsewhere and it's rather an old legacy interface.
+
+ The affected change is from upstream ZFS 2.x hence the patch applies
+ cleanly.
+
+ This fix has been in upstream ZFS for several months with no reported
+ regressions.
+
+ The change does not affect any core ZFS functionality.
+
+ Regression tested against the Ubuntu ZFS regression test suite and
+ passed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1942991
Title:
zfs: can't read /proc/sys/kernel/spl/hostid
Status in zfs-linux package in Ubuntu:
In Progress
Status in zfs-linux source package in Hirsute:
In Progress
Status in zfs-linux source package in Impish:
In Progress
Bug description:
[Impact]
Reading /proc/sys/kernel/spl/hostid no longer works in 5.7+ kernels
upwards.
The Fix:
commit 7de4c88b39473f358add601e8c227ca9002b1bee
Author: наб
Date: Sun Apr 11 01:18:40 2021 +0200
linux/spl: base proc_dohostid() on proc_dostring()
This fixes /proc/sys/kernel/spl/hostid on kernels with mainline commit
32927393dc1ccd60fb2bdc05b9e8e88753761469 ("sysctl: pass kernel pointers
to ->proc_handler") ‒ 5.7-rc1 and up
The access_ok() check in copy_to_user() in proc_copyout_string() would
always fail, so all userspace reads and writes would fail with EINVAL
proc_dostring() strips only the final new-line,
but simple_strtoul() doesn't actually need a back-trimmed string ‒
writing "012345678 \n" is still allowed, as is "012345678zupsko",
This alters what happens when an invalid value is written ‒
previously it'd get set to what-ever simple_strtoul() returned
(probably 0, thereby resetting it to default), now it does nothing
Reviewed-by: Brian Behlendorf
Signed-off-by: Ahelenia Ziemiańska
Closes #11878
Closes #11879
This applies cleanly for Impish and Hirsute 2.x ZFS so backporting is
straight forward.
[Test Plan]
cat /proc/sys/kernel/spl/hostid fails without the fix. With the fix it
returns a hex string of the hostid value.
[Where problems could occur]
This affects just a few
[Kernel-packages] [Bug 1942991] Re: zfs: can't read /proc/sys/kernel/spl/hostid
** Description changed:
+
Reading /proc/sys/kernel/spl/hostid no longer works in 5.7+ kernels
upwards.
The Fix:
commit 7de4c88b39473f358add601e8c227ca9002b1bee
Author: наб
Date: Sun Apr 11 01:18:40 2021 +0200
- linux/spl: base proc_dohostid() on proc_dostring()
-
- This fixes /proc/sys/kernel/spl/hostid on kernels with mainline commit
- 32927393dc1ccd60fb2bdc05b9e8e88753761469 ("sysctl: pass kernel pointers
- to ->proc_handler") ‒ 5.7-rc1 and up
-
- The access_ok() check in copy_to_user() in proc_copyout_string() would
- always fail, so all userspace reads and writes would fail with EINVAL
-
- proc_dostring() strips only the final new-line,
- but simple_strtoul() doesn't actually need a back-trimmed string ‒
- writing "012345678 \n" is still allowed, as is "012345678zupsko",
-
- This alters what happens when an invalid value is written ‒
- previously it'd get set to what-ever simple_strtoul() returned
- (probably 0, thereby resetting it to default), now it does nothing
-
- Reviewed-by: Brian Behlendorf
- Signed-off-by: Ahelenia Ziemiańska
- Closes #11878
- Closes #11879
+ linux/spl: base proc_dohostid() on proc_dostring()
+
+ This fixes /proc/sys/kernel/spl/hostid on kernels with mainline commit
+ 32927393dc1ccd60fb2bdc05b9e8e88753761469 ("sysctl: pass kernel pointers
+ to ->proc_handler") ‒ 5.7-rc1 and up
+
+ The access_ok() check in copy_to_user() in proc_copyout_string() would
+ always fail, so all userspace reads and writes would fail with EINVAL
+
+ proc_dostring() strips only the final new-line,
+ but simple_strtoul() doesn't actually need a back-trimmed string ‒
+ writing "012345678 \n" is still allowed, as is "012345678zupsko",
+
+ This alters what happens when an invalid value is written ‒
+ previously it'd get set to what-ever simple_strtoul() returned
+ (probably 0, thereby resetting it to default), now it does nothing
+
+ Reviewed-by: Brian Behlendorf
+ Signed-off-by: Ahelenia Ziemiańska
+ Closes #11878
+ Closes #11879
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1942991
Title:
zfs: can't read /proc/sys/kernel/spl/hostid
Status in zfs-linux package in Ubuntu:
In Progress
Status in zfs-linux source package in Hirsute:
In Progress
Status in zfs-linux source package in Impish:
In Progress
Bug description:
Reading /proc/sys/kernel/spl/hostid no longer works in 5.7+ kernels
upwards.
The Fix:
commit 7de4c88b39473f358add601e8c227ca9002b1bee
Author: наб
Date: Sun Apr 11 01:18:40 2021 +0200
linux/spl: base proc_dohostid() on proc_dostring()
This fixes /proc/sys/kernel/spl/hostid on kernels with mainline commit
32927393dc1ccd60fb2bdc05b9e8e88753761469 ("sysctl: pass kernel pointers
to ->proc_handler") ‒ 5.7-rc1 and up
The access_ok() check in copy_to_user() in proc_copyout_string() would
always fail, so all userspace reads and writes would fail with EINVAL
proc_dostring() strips only the final new-line,
but simple_strtoul() doesn't actually need a back-trimmed string ‒
writing "012345678 \n" is still allowed, as is "012345678zupsko",
This alters what happens when an invalid value is written ‒
previously it'd get set to what-ever simple_strtoul() returned
(probably 0, thereby resetting it to default), now it does nothing
Reviewed-by: Brian Behlendorf
Signed-off-by: Ahelenia Ziemiańska
Closes #11878
Closes #11879
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1942991/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync
Hi Kleber, I installed it later yesterday, but I won't know until the next resync. This has been a problem since at least linux 5.4 kernel that shipped with Ubuntu 20.04. I don't think I had these problems on Ubuntu 18.04 LTS, the same hardware, running the linux-image-generic at that time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30 [921588.559081] ? kmem_cache_alloc+0x38e/0x440 [921588.559084] ? ext4_init_io_end+0x1f/0x50 [921588.559088]
[Kernel-packages] [Bug 1942215] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI
An Impish 5.13 test kernel is available here: https://people.canonical.com/~ppisati/lp1942215/ linux-image-unsigned-5.13.0-16-generic_5.13.0-16.16~lp1942215_amd64.deb linux-modules-5.13.0-16-generic_5.13.0-16.16~lp1942215_amd64.deb linux-modules-extra-5.13.0-16-generic_5.13.0-16.16~lp1942215_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942215 Title: OOPs on boot: invalid opcode: [#1] SMP NOPTI Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: Incomplete Bug description: Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon boot on vought we get this: ... [ 11.502916] invalid opcode: [#1] SMP NOPTI [ 11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 5.13.0-15-generic #15-Ubuntu [ 11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS SE5C620.86B.0D.01.0395.022720191340 02/27/2019 [ 11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774 [ 11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01 [ 11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286 [ 11.513428] RAX: RBX: 8f08a7573800 RCX: 0040 [ 11.514972] RDX: RSI: 91ea9980 RDI: 02cb [ 11.516100] RBP: aaeca1a77710 R08: R09: 8f08a8c84af0 [ 11.517479] R10: R11: 0003 R12: [ 11.518985] R13: 8f08a8c84af0 R14: R15: [ 11.520425] FS: 7f7fb403ed00() GS:8f348d5c() knlGS: [ 11.521931] CS: 0010 DS: ES: CR0: 80050033 [ 11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 007706e0 [ 11.524924] DR0: DR1: DR2: [ 11.526221] DR3: DR6: fffe0ff0 DR7: 0400 [ 11.527636] PKRU: 5554 [ 11.528820] Call Trace: [ 11.529807] acpi_ps_parse_loop+0x587/0x660 [ 11.531198] acpi_ps_parse_aml+0x1af/0x552 [ 11.532595] acpi_ps_execute_method+0x208/0x2ca [ 11.533972] acpi_ns_evaluate+0x34e/0x4f0 [ 11.535361] acpi_evaluate_object+0x18e/0x3b4 [ 11.536736] acpi_evaluate_dsm+0xb3/0x120 [ 11.537943] ? acpi_evaluate_dsm+0xb3/0x120 [ 11.539214] nfit_intel_shutdown_status+0xed/0x1b0 [nfit] [ 11.540603] acpi_nfit_add_dimm+0x3cb/0x670 [nfit] [ 11.541990] acpi_nfit_register_dimms+0x141/0x460 [nfit] [ 11.543377] acpi_nfit_init+0x54f/0x620 [nfit] [ 11.544755] acpi_nfit_add+0x192/0x1f0 [nfit] [ 11.546116] acpi_device_probe+0x49/0x170 [ 11.547431] really_probe+0x245/0x4c0 [ 11.548749] driver_probe_device+0xf0/0x160 [ 11.550064] device_driver_attach+0xab/0xb0 [ 11.551387] __driver_attach+0xb2/0x140 [ 11.552692] ? device_driver_attach+0xb0/0xb0 [ 11.554001] bus_for_each_dev+0x7e/0xc0 [ 11.555326] driver_attach+0x1e/0x20 [ 11.556630] bus_add_driver+0x135/0x1f0 [ 11.557917] driver_register+0x95/0xf0 [ 11.559226] acpi_bus_register_driver+0x39/0x50 [ 11.560139] nfit_init+0x168/0x1000 [nfit] [ 11.561230] ? 0xc0649000 [ 11.562442] do_one_initcall+0x46/0x1d0 [ 11.563701] ? kmem_cache_alloc_trace+0x11c/0x240 [ 11.564846] do_init_module+0x62/0x290 [ 11.565768] load_module+0xaa6/0xb40 [ 11.566811] __do_sys_finit_module+0xc2/0x120 [ 11.567825] __x64_sys_finit_module+0x18/0x20 [ 11.568747] do_syscall_64+0x61/0xb0 [ 11.569694] ? syscall_exit_to_user_mode+0x27/0x50 [ 11.570680] ? __x64_sys_mmap+0x33/0x40 [ 11.571606] ? do_syscall_64+0x6e/0xb0 [ 11.572442] ? asm_exc_page_fault+0x8/0x30 [ 11.573395] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 11.574392] RIP: 0033:0x7f7fb45d670d [ 11.575373] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48 [ 11.577496] RSP: 002b:7ffe815a56d8 EFLAGS: 0246 ORIG_RAX: 0139 [ 11.578573] RAX: ffda RBX: 5624b212e410 RCX: 7f7fb45d670d [ 11.579646] RDX: RSI: 7f7fb47683fe RDI: 0006 [ 11.580712] RBP: 0002 R08: R09: [ 11.581774] R10: 0006 R11: 0246 R12: 7f7fb47683fe [ 11.582847] R13: 5624b2090bf0 R14: 5624b208f940 R15: 5624b2096cd0 [ 11.583907] Modules linked in: nfit(+) mac_hid sch_fq_codel msr ip_tables x_tables autofs4 btrfs blake2b_generic
[Kernel-packages] [Bug 1942991] Re: zfs: can't read /proc/sys/kernel/spl/hostid
** Also affects: zfs-linux (Ubuntu Impish)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Also affects: zfs-linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: zfs-linux (Ubuntu Hirsute)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: zfs-linux (Ubuntu Hirsute)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1942991
Title:
zfs: can't read /proc/sys/kernel/spl/hostid
Status in zfs-linux package in Ubuntu:
In Progress
Status in zfs-linux source package in Hirsute:
In Progress
Status in zfs-linux source package in Impish:
In Progress
Bug description:
Reading /proc/sys/kernel/spl/hostid no longer works in 5.7+ kernels
upwards.
The Fix:
commit 7de4c88b39473f358add601e8c227ca9002b1bee
Author: наб
Date: Sun Apr 11 01:18:40 2021 +0200
linux/spl: base proc_dohostid() on proc_dostring()
This fixes /proc/sys/kernel/spl/hostid on kernels with mainline commit
32927393dc1ccd60fb2bdc05b9e8e88753761469 ("sysctl: pass kernel pointers
to ->proc_handler") ‒ 5.7-rc1 and up
The access_ok() check in copy_to_user() in proc_copyout_string() would
always fail, so all userspace reads and writes would fail with EINVAL
proc_dostring() strips only the final new-line,
but simple_strtoul() doesn't actually need a back-trimmed string ‒
writing "012345678 \n" is still allowed, as is "012345678zupsko",
This alters what happens when an invalid value is written ‒
previously it'd get set to what-ever simple_strtoul() returned
(probably 0, thereby resetting it to default), now it does nothing
Reviewed-by: Brian Behlendorf
Signed-off-by: Ahelenia Ziemiańska
Closes #11878
Closes #11879
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1942991/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828153] Re: gicv2 related tests in ubuntu_kvm_unit_tests failed with SIGABRT on X-hwe ARM64 ThunderX
With updated test suite it's not failing with SIGABRT now. Please find the following bug reports: * bug 1936405 (FAIL gicv2-ipi (timeout; duration=90s)) * bug 1828027 (gicv2-mmio-3p failed on x:hwe arm64) * bug 1828026 (gicv2-mmio-up failed on x:hwe arm64) ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-hwe (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1828153 Title: gicv2 related tests in ubuntu_kvm_unit_tests failed with SIGABRT on X-hwe ARM64 ThunderX Status in ubuntu-kernel-tests: Fix Released Status in linux-hwe package in Ubuntu: Invalid Bug description: All the gicv2 related tests have failed on the ARM64 ThunderX testing node with X-HWE kernel:; FAIL gicv2-ipi (terminated on SIGABRT) FAIL gicv2-mmio (terminated on SIGABRT) FAIL gicv2-mmio-up (terminated on SIGABRT) FAIL gicv2-mmio-3p (terminated on SIGABRT) FAIL gicv2-active (terminated on SIGABRT) This is because: Failed to set device address: No such device Take one of them for example: # MAX_SMP=48 # TESTNAME=gicv2-mmio TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'mmio' timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/gic.flat -smp 8 -machine gic-version=2 -append mmio # -initrd /tmp/tmp.Xn7TN56BKl Failed to set device address: No such device timeout: the monitored command dumped core QEMU Aborted ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51~16.04.1 ProcVersionSignature: User Name 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic aarch64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 Date: Wed May 8 03:57:01 2019 SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922099] Re: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 on armhf
Groovy has reached EOL. Invalidating tasks. ** Summary changed: - nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 + nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 on armhf ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1922099 Title: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 on armhf Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in nvidia-graphics-drivers-390 source package in Focal: New Status in linux source package in Groovy: Invalid Status in nvidia-graphics-drivers-390 source package in Groovy: Invalid Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether this is caused by the tested source or the kernel has, yet, to be determined. Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942999] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1942999 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942999 Title: [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Hirsute: New Bug description: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942932] Re: oob_net0 up but stops processing Rx packets
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1942932 Title: oob_net0 up but stops processing Rx packets Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: In Progress Bug description: SRU Justification: [Impact] * The oob_net0 interface, managed by the mlxbf_gige driver, will be up and enabled but can stop processing received packets if three specific conditions occur: 1) driver has received more than (N * RxRingSize) packets but less than (N+1 * RxRingSize) packets where N is an odd number. Note: the command "ethtool -g oob_net0" will display the current receive ring size, which currently defaults to 128. 2) the driver's interface was disabled via "ifconfig oob_net0 down" during the window described in #1. 3) the driver's interface is re-enabled via "ifconfig oob_net0 up" Without this fix, the driver needs to be unloaded and re-loaded to correct this condition. [Fix] * The fix is to ensure that the driver's "valid_polarity" field is cleared during the open() method so that it always matches the receive polarity used by hardware. [Test Case] * To test this fix, need to send in a specific number of packets to the "oob_net0" interface, then issue "ifconfig oob_net0 down" to disable the interface. A subsequent "ifconfig oob_net0 up" command will succesfully bring up the "oob_net0" interface and start the processing of received packets. [Regression Potential] * There is low risk of this fix causing any problems. [Other] * The mlxbf_gige driver will display v1.25 in modinfo after these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943001] [NEW] hwe 20.04 kernel 5.11 series hang at graphical login leaving laptop unusable
Public bug reported: The 5.11-series 20.04 HWE kernels are not usable on my laptop. They boot up to graphical login. Then the screen goes black for a second every few seconds. When i try to log in the machine seems to hang and the desktop never appears... The kern.log shows a lot of these errors: "[drm:amdgpu_pci_remove [amdgpu]] *ERROR* Hotplug removal is not supported" Many call traces appear as well, involving [amdgpu] and [ttm]. I have reverted to using the 5.8 kernels. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic-hwe-20.04 5.11.0.34.36~20.04.13 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Sep 8 09:58:49 2021 InstallationDate: Installed on 2014-07-16 (2610 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: linux-meta-hwe-5.11 UpgradeStatus: Upgraded to focal on 2021-02-24 (195 days ago) ** Affects: linux-meta-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: The 5.11-series 20.04 HWE kernels are not usable on my laptop. They boot up to graphical login. Then the screen goes black for a second every few seconds. When i try to log in the machine seems to hang and the desktop never appears... - The kernel.log shows a lot of these errors: + The kern.log shows a lot of these errors: "[drm:amdgpu_pci_remove [amdgpu]] *ERROR* Hotplug removal is not supported" Many call traces appear as well, involving [amdgpu] and [ttm]. I have reverted to using the 5.8 kernels. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic-hwe-20.04 5.11.0.34.36~20.04.13 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Sep 8 09:58:49 2021 InstallationDate: Installed on 2014-07-16 (2610 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: linux-meta-hwe-5.11 UpgradeStatus: Upgraded to focal on 2021-02-24 (195 days ago) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943001 Title: hwe 20.04 kernel 5.11 series hang at graphical login leaving laptop unusable Status in linux-meta-hwe-5.11 package in Ubuntu: New Bug description: The 5.11-series 20.04 HWE kernels are not usable on my laptop. They boot up to graphical login. Then the screen goes black for a second every few seconds. When i try to log in the machine seems to hang and the desktop never appears... The kern.log shows a lot of these errors: "[drm:amdgpu_pci_remove [amdgpu]] *ERROR* Hotplug removal is not supported" Many call traces appear as well, involving [amdgpu] and [ttm]. I have reverted to using the 5.8 kernels. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic-hwe-20.04 5.11.0.34.36~20.04.13 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Sep 8 09:58:49 2021 InstallationDate: Installed on 2014-07-16 (2610 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: linux-meta-hwe-5.11 UpgradeStatus: Upgraded to focal on 2021-02-24 (195 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.11/+bug/1943001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942931] Re: "ethtool -S oob_net0" does not report interrupt counts
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1942931 Title: "ethtool -S oob_net0" does not report interrupt counts Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: In Progress Bug description: SRU Justification: [Impact] * The command "ethtool -S oob_net0" displays a set of statistics related to mlxbf_gige driver. This set of statistics does not include the driver's interrupt counts. [Fix] * The fix is to extend the statistics list supported by "ethtool -S" so that it includes MAC, receive packet, and LLU/PLU interrupt counts. [Test Case] * The command "ethtool -S oob_net0" should be executed before and after this fix to verify that three new fields are displayed: mac_intr_count rx_intr_count llu_plu_intr_count [Regression Potential] * There is low risk of this fix causing any problems. [Other] * n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync
Hello Chad Wagner, Thank you for reporting this issue. Could you please try installing the latest 20.04 HWE kernel and check whether the problem persists? The version currently in focal-updates is 5.11.0-34.36~20.04.1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30 [921588.559081] ? kmem_cache_alloc+0x38e/0x440 [921588.559084] ? ext4_init_io_end+0x1f/0x50 [921588.559088] ext4_io_submit+0x4d/0x60 [921588.559091] ext4_writepages+0x2c6/0xcd0
[Kernel-packages] [Bug 1942999] Re: [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock
the only reason of this issue, is that the version is not supported. Either the ubuntu with macbook or vice versa. Even you may got the best answer here or had chance to know about world current updates then you have to type just type https://www.nayatime.com/ at the google and you will be surprise with current updates all around the world. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942999 Title: [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Hirsute: New Bug description: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936771] Re: disable “CONFIG_HISI_DMA” config for ubuntu version
Thanks. 5.11.0-35.37 kernel works fine with soft RAID5 on kunpeng920. $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 57.4M 1 loop /snap/core20/1084 loop1 7:10 28.1M 1 loop /snap/snapd/12707 loop2 7:2061M 1 loop /snap/lxd/21042 loop3 7:30 28.1M 1 loop /snap/snapd/12886 loop4 7:40 65.1M 1 loop /snap/lxd/21462 sda 8:00 894.3G 0 disk ├─sda1 8:10 100G 0 part │ └─md127 9:127 0 199.9G 0 raid5 ├─sda2 8:20 100G 0 part │ └─md127 9:127 0 199.9G 0 raid5 └─sda3 8:30 100G 0 part └─md127 9:127 0 199.9G 0 raid5 sdb 8:16 0 894.3G 0 disk ├─sdb1 8:17 0 512M 0 part /boot/efi └─sdb2 8:18 0 893.8G 0 part / $ uname -a Linux segers 5.11.0-35-generic #37-Ubuntu SMP Fri Sep 3 14:00:38 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux $ sudo dmesg | grep raid | tail -3 [ 21.269566] md/raid:md127: device sda2 operational as raid disk 1 [ 21.298316] md/raid:md127: device sda1 operational as raid disk 0 [ 21.305059] md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1936771 Title: disable “CONFIG_HISI_DMA” config for ubuntu version Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] Setup soft RAID5 on kunpeng920 machine and system will crash because of hisi_dma timeout. This issue can be reproduced with all Ubuntu kernel with hisi_dma. [Test Plan] Setup soft RAID5 and wait for few seconds. Kernel will crash. [Regression Risk] CONFIG_HISI_DMA only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] disable “CONFIG_HISI_DMA” config for ubuntu version [Steps to Reproduce] 1) 2) 3) [Actual Results] this module cause some error [Expected Results] ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1936771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942999] [NEW] [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock
Public bug reported: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1942744 originate-from-1942746 sutton ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oem-5.13 (Ubuntu Hirsute) ** No longer affects: linux-oem-5.14 (Ubuntu Hirsute) ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** Tags added: oem-priority originate-from-1942746 sutton ** Tags added: originate-from-1942744 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942999 Title: [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Hirsute: New Bug description: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939855] Re: [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands
I have verified the proposed kernel and I do not see any issue. Thank you for the help. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939855 Title: [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands Status in dellserver: Incomplete Status in focal package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in focal source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] When we run the command, ethtool -d with Intel cards (ice driver), the kernel crashes because of the ice driver. The same works fine with HWE kernel (5.11). Here, we do not see any crash. [FIXES] ice: Fix bad register reads The "ethtool -d" handler reads registers in the ice_regs_dump_list array and returns read values back to the userspace. commitID: 1fba4a8a92706c89716449b1aab1b6879f438d34 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/ethernet/intel/ice?id=1fba4a8a92706c89716449b1aab1b6879f438d34 [TESTING] Install Focal on a system with an E810 network device. Ensure the network device has an IP address and has connectivity Run ethtool -d Expected result: Prints a register dump for the specified network device [REGRESSION RISK] The regression risk is low [OTHER INFO] I have added the fix, built the kernel and tested the fix. https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e810_ethtool_fix_next To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1939855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934261] Re: use debian source format 3.0 (native)
also, we should aim for not being native, since each upload is a 220+MB load on the archive -- 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/1934261 Title: use debian source format 3.0 (native) Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: Won't Fix Status in linux-firmware source package in Hirsute: Invalid Status in linux-firmware source package in Impish: Invalid Bug description: In Hirsute/Impish, debian source package Standards-Version moved to 4.5.0, and debian/source/format is created with content "3.0 (native)". It should be also helpful to backport this change to other maintaining series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942994] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1942994 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942994 Title: [SRU][OEM-5.13/OEM-5.14/U] Fix mt7921e wifi timeout error after resume Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Bug description: SRU justification: [Impact] Mediatek 7921 wifi card is lost when stress S3. [Fix] Check the valid events from firmware, make it resume back. The patch is in maintainer's tree, but not merged to Linus's tree. Due to the schedule, send SRU as SAUCE patch. [Test] Verified on hardware, wifi works fine after stress S3. Tested on 3 platforms include the one platform that can reproduce the issue, all good. [Where problems could occur] Mediatek 7921 wifi may be broken. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936771] Re: disable “CONFIG_HISI_DMA” config for ubuntu version
Thanks. 5.4.0-85.95 kernel works fine with soft RAID5 on kunpeng920 $ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0062M 1 loop /snap/lxd/21032 loop1 7:10 48.9M 1 loop /snap/core18/2127 loop2 7:20 28.1M 1 loop /snap/snapd/12707 sda 8:00 557.9G 0 disk ├─sda18:10 512M 0 part /boot/efi └─sda28:20 557.4G 0 part / sdb 8:16 0 557.9G 0 disk ├─sdb18:17 0 100G 0 part │ └─md0 9:00 199.9G 0 raid5 ├─sdb28:18 0 100G 0 part │ └─md0 9:00 199.9G 0 raid5 └─sdb38:19 0 100G 0 part └─md0 9:00 199.9G 0 raid5 $ uname -a Linux saenger 5.4.0-85-generic #95-Ubuntu SMP Fri Sep 3 16:13:17 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux $ dmesg | tail -3 [ 531.883803] md0: detected capacity change from 0 to 214612049920 [ 531.883914] md: recovery of RAID array md0 [ 739.851754] hns3 :7d:00.0 enp125s0f0: link down ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936771 Title: disable “CONFIG_HISI_DMA” config for ubuntu version Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] Setup soft RAID5 on kunpeng920 machine and system will crash because of hisi_dma timeout. This issue can be reproduced with all Ubuntu kernel with hisi_dma. [Test Plan] Setup soft RAID5 and wait for few seconds. Kernel will crash. [Regression Risk] CONFIG_HISI_DMA only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] disable “CONFIG_HISI_DMA” config for ubuntu version [Steps to Reproduce] 1) 2) 3) [Actual Results] this module cause some error [Expected Results] ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1936771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942994] Re: [SRU][OEM-5.13/OEM-5.14/U] Fix mt7921e wifi timeout error after resume
** Description changed: SRU justification: [Impact] Mediatek 7921 wifi card is lost when stress S3. [Fix] Check the valid events from firmware, make it resume back. The patch is in maintainer's tree, but not merged to Linus's tree. Due to the schedule, send SRU as SAUCE patch. [Test] Verified on hardware, wifi works fine after stress S3. - This issus is only produced on 1 platform, tested on 3 platforms, all good. + Tested on 3 platforms include the one platform that can reproduce the issue, all good. [Where problems could occur] Mediatek 7921 wifi may be broken. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942994 Title: [SRU][OEM-5.13/OEM-5.14/U] Fix mt7921e wifi timeout error after resume Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Bug description: SRU justification: [Impact] Mediatek 7921 wifi card is lost when stress S3. [Fix] Check the valid events from firmware, make it resume back. The patch is in maintainer's tree, but not merged to Linus's tree. Due to the schedule, send SRU as SAUCE patch. [Test] Verified on hardware, wifi works fine after stress S3. Tested on 3 platforms include the one platform that can reproduce the issue, all good. [Where problems could occur] Mediatek 7921 wifi may be broken. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942994] [NEW] [SRU][OEM-5.13/OEM-5.14/U] Fix mt7921e wifi timeout error after resume
Public bug reported: SRU justification: [Impact] Mediatek 7921 wifi card is lost when stress S3. [Fix] Check the valid events from firmware, make it resume back. The patch is in maintainer's tree, but not merged to Linus's tree. Due to the schedule, send SRU as SAUCE patch. [Test] Verified on hardware, wifi works fine after stress S3. This issus is only produced on 1 platform, tested on 3 platforms, all good. [Where problems could occur] Mediatek 7921 wifi may be broken. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1940512 sutton ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** Tags added: oem-priority originate-from-1940512 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942994 Title: [SRU][OEM-5.13/OEM-5.14/U] Fix mt7921e wifi timeout error after resume Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Bug description: SRU justification: [Impact] Mediatek 7921 wifi card is lost when stress S3. [Fix] Check the valid events from firmware, make it resume back. The patch is in maintainer's tree, but not merged to Linus's tree. Due to the schedule, send SRU as SAUCE patch. [Test] Verified on hardware, wifi works fine after stress S3. This issus is only produced on 1 platform, tested on 3 platforms, all good. [Where problems could occur] Mediatek 7921 wifi may be broken. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942991] [NEW] zfs: can't read /proc/sys/kernel/spl/hostid
Public bug reported:
Reading /proc/sys/kernel/spl/hostid no longer works in 5.7+ kernels
upwards.
The Fix:
commit 7de4c88b39473f358add601e8c227ca9002b1bee
Author: наб
Date: Sun Apr 11 01:18:40 2021 +0200
linux/spl: base proc_dohostid() on proc_dostring()
This fixes /proc/sys/kernel/spl/hostid on kernels with mainline commit
32927393dc1ccd60fb2bdc05b9e8e88753761469 ("sysctl: pass kernel pointers
to ->proc_handler") ‒ 5.7-rc1 and up
The access_ok() check in copy_to_user() in proc_copyout_string() would
always fail, so all userspace reads and writes would fail with EINVAL
proc_dostring() strips only the final new-line,
but simple_strtoul() doesn't actually need a back-trimmed string ‒
writing "012345678 \n" is still allowed, as is "012345678zupsko",
This alters what happens when an invalid value is written ‒
previously it'd get set to what-ever simple_strtoul() returned
(probably 0, thereby resetting it to default), now it does nothing
Reviewed-by: Brian Behlendorf
Signed-off-by: Ahelenia Ziemiańska
Closes #11878
Closes #11879
** Affects: zfs-linux (Ubuntu)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1942991
Title:
zfs: can't read /proc/sys/kernel/spl/hostid
Status in zfs-linux package in Ubuntu:
In Progress
Bug description:
Reading /proc/sys/kernel/spl/hostid no longer works in 5.7+ kernels
upwards.
The Fix:
commit 7de4c88b39473f358add601e8c227ca9002b1bee
Author: наб
Date: Sun Apr 11 01:18:40 2021 +0200
linux/spl: base proc_dohostid() on proc_dostring()
This fixes /proc/sys/kernel/spl/hostid on kernels with mainline commit
32927393dc1ccd60fb2bdc05b9e8e88753761469 ("sysctl: pass kernel pointers
to ->proc_handler") ‒ 5.7-rc1 and up
The access_ok() check in copy_to_user() in proc_copyout_string() would
always fail, so all userspace reads and writes would fail with EINVAL
proc_dostring() strips only the final new-line,
but simple_strtoul() doesn't actually need a back-trimmed string ‒
writing "012345678 \n" is still allowed, as is "012345678zupsko",
This alters what happens when an invalid value is written ‒
previously it'd get set to what-ever simple_strtoul() returned
(probably 0, thereby resetting it to default), now it does nothing
Reviewed-by: Brian Behlendorf
Signed-off-by: Ahelenia Ziemiańska
Closes #11878
Closes #11879
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1942991/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939349] Re: frequent hangs with latest hirsute kernel (nvidia graphics)
Before I had a chance to try uninstalling the nvidia driver, the laptop crashed again, and then I was unable to get it to boot across multiple (10+) attempts. After catching kernel output on one hung boot (by pressing Esc to clear plymouth), I was able to see that the hardware hang happened right after the start of gpu-manager.service. So I went into the firmware and tried disabling hybrid graphics in favor of discrete graphics. The machine booted successfully on the very next boot and has been stable now for just over a day (at the expense of having no brightness control). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939349 Title: frequent hangs with latest hirsute kernel (nvidia graphics) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to the latest kernel, I am experiencing frequent kernel hangs. The system does not respond to Alt+SysRq, and I have to power it off. In some cases the hang happens before X has even been launched at boot. When it hangs, the fan spins up to full speed. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vorlon10452 F pulseaudio /dev/snd/controlC0: vorlon10452 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 9 14:15:58 2021 InstallationDate: Installed on 2019-12-23 (594 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_di672m@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_di672m ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2019 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET40W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN2OET40W(1.27):bd10/17/2019:br1.27:efr1.19:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vorlon 8854 F pulseaudio /dev/snd/controlC0: vorlon 8854 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2019-12-23 (600 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_di672m@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_di672m ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 Tags: hirsute Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild src sudo _MarkForUpload: True dmi.bios.date: 04/28/2021 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET52W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias:
[Kernel-packages] [Bug 1941669] Re: alsa: the soundwire audio doesn't work on the Dell TGL-H machines
Installed the proposed kernel in the hirsute on the machine dell precision 5760, reboot and check dmesg, there is no audio related error, open the gnome-sound-setting, the spk and internal mic work well, plug headset, the headphone and headset-mic work well too. Verification done. ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1941669 Title: alsa: the soundwire audio doesn't work on the Dell TGL-H machines Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Fix Committed Bug description: These 2 patches were merged to upstream kernel from v5.12, no need to send them to impish/oem-5.13/unstable kernels. And this patch is already in the oem-5.10 kernel, for focal kernel, since focal kernel doesn't support soundwire audio, these 2 patches are useless for focal kernel. [Impact] The Dell precision 5760 is a TGL-H machine, and it has soundwire audio design, when running the hirsute kernel, the audio driver fails to load sof-firmware, then the whole audio fails to initialize and fails to work. [Fix] Backport 2 patches, these will remove hardcoded firmware name and allow load firmware according to the firmware name defined by pciid [Test] Booting the patched kernel, check dmesg, there is no errors about loading audio sof-firmware, playsound to spk and headphone, all worked well, record sound from internal mic and external mic, all worked well. [Where problems could occur] The patch remove the hardcoded firmware for all TGL soundwire machines, this could make the TGL soundwire machines fail to load the sof-firmware then the whole audio fail to work. But this possibiliy is low, since we tested the patches on different TGL soundwire machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940488] Re: dell300x: rsi wifi and bluetooth crash after suspend and resume
Install the -proposed kernel in the bionic, reboot and run '$sudo rtcwake -m freeze -s 10' for 50 times, the wifi and bluetooth still worked well. Verification done. ** 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-dell300x in Ubuntu. https://bugs.launchpad.net/bugs/1940488 Title: dell300x: rsi wifi and bluetooth crash after suspend and resume Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-dell300x package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-dell300x source package in Bionic: Fix Released Bug description: I tested the upstream stable kernel 4.19.191, also could reproduce this issue, and reported this testing result to stable mail list. [Impact] On the Dell300x machine, after system suspend and resume, the wifi and bluetooth can't work anymore. [Fix] Revert a patch which was applied to bionic kernel from stable update. [Test] Booting up with the patched kernel, run $sudo rtcwake -m freeze -s 10, then check dmesg to make sure there is crashing log, and run 'nmcli d wifi' and 'bluetoothctl, power on, scan on', all worked well. [Where problems could occur] After applying this SRU, the rsi wifi and bluetooth could have come change, like wifi and bluetooth can't work well after resume, but this possibility is very low, I already run '$sudo rtcwake -m freeze -s 10' for 50 times, the wifi and bluetooth still worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
