[Kernel-packages] [Bug 2083598] [NEW] Machine found rebooted into busybox overnight
Public bug reported: Went to bed with my machine sitting at the desktop with a display timeout set to 15 minutes (did not enable automatic sleep). Woke up to my machine in busybox and unable to boot until I ran e2fsck on my disk. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 06:19:45 2024 InstallationDate: Installed on 2024-10-02 (1 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20241002) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: ASUS ROG CROSSHAIR X670E HERO ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-8-generic root=UUID=0cfad749-5f02-4b36-83c4-6d65e0f1fd05 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2024 dmi.bios.release: 24.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2403 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR X670E HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2403:bd09/24/2024:br24.3:svnASUS:pnROGCROSSHAIRX670EHERO:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRX670EHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: ROG CROSSHAIR X670E HERO dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2083598 Title: Machine found rebooted into busybox overnight Status in linux package in Ubuntu: New Bug description: Went to bed with my machine sitting at the desktop with a display timeout set to 15 minutes (did not enable automatic sleep). Woke up to my machine in busybox and unable to boot until I ran e2fsck on my disk. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 06:19:45 2024 InstallationDate: Installed on 2024-10-02 (1 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20241002) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: ASUS ROG CROSSHAIR X670E HERO ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-8-generic root=UUID=0cfad749-5f02-4b36-83c4-6d65e0f1fd05 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2024 dmi.bios.release: 24.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2403 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR X670E HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2403:bd09/24/2024:br24.3:svnASUS:pnROGCROSSHAIRX670EHERO:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRX670EHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: ROG CROSSHAIR X670E HERO dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug g
[Kernel-packages] [Bug 2049688] Re: nvidia stoped working, , package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subp
This seems to be related to the Ubuntu-Kernel-Update (6.2 to 6.5). I can confirm a similar issue installing the official nvidia linux driver. Worked fine some weeks ago, but update some days ago failed. Checking /var/log/nvidia-installer.log tells an interface conflict (error) and a warning (about cc compiler version). Even the nvidia-update 2 days ago did not solve this new conflict. Other related issues (all came up 1 week ago) https://forums.developer.nvidia.com/t/ubuntu-22-04-no-display-after-nvidia-driver-installed/278855 or new kernel 6.5.0-14(22.04) can not compile NVIDIA display card driver https://ubuntuforums.org/showthread.php?t=2494273&page=3&p=14175822#post14175822 PS: I also wait for a solution. ** Description changed: after latest update on 22.04 nvidia driver stoped working, gpu not found, cannot reinstall, even after upgrade I get : package nvidia- dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10. I also had errors with dependencies, when trying to reinstall and with kernel headers. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: nvidia-dkms-390 390.157-0ubuntu5.23.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 22:54:39 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-11-28 (50 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: - dpkg 1.21.21ubuntu1 - apt 2.6.0ubuntu0.1 + dpkg 1.21.21ubuntu1 + apt 2.6.0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to lunar on 2024-01-17 (0 days ago) -- 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/2049688 Title: nvidia stoped working,, package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia- dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: after latest update on 22.04 nvidia driver stoped working, gpu not found, cannot reinstall, even after upgrade I get : package nvidia- dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10. I also had errors with dependencies, when trying to reinstall and with kernel headers. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: nvidia-dkms-390 390.157-0ubuntu5.23.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 22:54:39 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-11-28 (50 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to lunar on 2024-01-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038998] Re: [amdgpu] Screen corruption, distorted geometry and misplaced triangles
I've tried the kernel parameter and those artifacts are still happening.
But just on my FHD screen; not on my other screens (1440p).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038998
Title:
[amdgpu] Screen corruption, distorted geometry and misplaced triangles
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 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.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024113] Re: Linux 6.2.0-20 kernel update tries to install low latency and oracle versions
+1 upvote See comment #17 & #49 here: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-530/+bug/2023946?comments=all / quote, copy and paste from my own comment #49 (bug 2023946) into this ongoing bug report (2024113): "Typing this from my phone rn, so bare with me please. I kept digging into this because it turns out that the computer that my wife uses also had a few Nvidia related issues recently, and she also has the Oracle and low latency kernel installed, even though she didn't install these manually, willingly or knowingly. There is a bunch of information about this out there: - https://www.reddit.com/r/Kubuntu/comments/14ndb7a/why_do_i_keep_getting_these_oracle_and_lowlatency/ - https://ubuntuforums.org/showthread.php?t=2482558 - https://ubuntuforums.org/showthread.php?t=2473057 - https://ubuntuforums.org/showthread.php?t=2483064 Going by the information at hand, it seems that this is indeed caused either by the Nvidia driver update in Ubuntu - or - it's a dependency from Virtualbox or Gnome Boxes, which I mentioned in the comments of the bug report further below. Two things here: a) having the kernel change like this from the default Ubuntu kernel to something from Oracle without any form of obvious user info or confirmation is something to worry about imo b) it seems to be tied to some of the gpu driver update issues that a few of us have been experiencing, and it has even nuked or rendered some systems unusable too, see posts above I haven't found the time to further diagnose my own Ubuntu + Nvidia related issues (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776), and I don't see myself troubleshooting my wife's computer right now, so I leave this comment here just in case someone wants to open up a new or separate bug report about this, which I'll gladly upvote in order to provide whatever little information that I have right now. If there is already an ongoing bug report for this available, a point in the right direction is highly appreciated. Thanks!" / End of quote. The text above includes other related bug reports and also a few additional links. I recommend looking into this asap as it seems to be affecting a number of Nvidia, Virtualbox and Gnome Boxes users, causing all sorts of issues and even rendering some systems unbootable. Ty! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024113 Title: Linux 6.2.0-20 kernel update tries to install low latency and oracle versions Status in linux package in Ubuntu: Confirmed Bug description: when I ran software updates to update my 23.04 Budgie system today to Linux 6.2.0-20-generic apt treis to install the low latency and Oracle versions of the kernel too, breaking my system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006042] Re: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram
Got a similar issue with Asus K513. It happens every time I suspend with a type-C dock connected (the laptop does not support the HDMI out on type-C, so I'm only using it as a USB 3.0 hub). The power indicator starts blinking with a strange pattern: 0.1 sec of light every two seconds. And I have to press the POWER button for an unusually long time (10-15 seconds or more) to get the reboot. Other than that, this laptop tends to crash when resuming from the suspend much more often if you have the SATA SSD installed. Also, it might smth to have with the light-locker which switches the console when locking/unlocking 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/2006042 Title: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram Status in linux package in Ubuntu: Confirmed Bug description: Hi, After waking up from suspend to RAM, my computer actually wakes up but can sometimes then hang on a black screen (no prompt, nothing displayed, screen is active). This issue happens quite frequently but seems rather random. I think certain circumstances lower the frequency (I'll elaborate in the report). First of all, I'm not exactly sure when it started but I would say first notable frequent occurrences were around summer 2021 (yes, I'm late, sorry for that). When this happens, Algr+SysRQ+[usb] is unresponsive. Or at least that's what I used to believe as it used to be true as I always tried from the laptop integrated keyboard. Until I connected an USB-C mechanical keyboard, from which I'm *sometimes* able to use the magic keys (not always, and with a lot of lag, but still). If magic keys are unresponsive, I need to hard reset/long press power. There is nothing unusual before that in syslog nor kern.log, at least not that I know of. Except the ^@^@^@ characters when I had to hard reset the computer. If I leave the laptop like that for a while, it eventually reboots by itself and stays on the FDE passphrase prompt (which is not nice as the screen can then stay on for a very long like that if I did not notice). I'm running KDE/Plasma desktop, and this issue has happened regardless of the display manager. I used to run Xorg but now I'm on wayland flavor (mostly to alleviate firefox rendering/compositing issues). This also seems unrelated to external screen being connected or not, as it happened in the past regardless of that parameter. Although, it *seems* frequency has lowered a bit since I changed the way I wake up my laptop. Higher frequency (almost every day): - no external screen or external screen connected to HDMI port - waking up from integrated keyboard power button short press Lower frequency (one to multiple times a week, but somewhat irregular, since ~ 2 months ago): - external screen connected to USB-C port - mechanical keyboard connected to USB-C port of screen - waking up from the mechanical keyboard It also seems to happen more frequently if I wake up the computer, do some very fast task and send it to sleep in under a few minutes. It's not guaranteed to happen, but seems to highly increase the probability. Also, this might be related so I'm adding that bit: I had to disable shutting the screen Off in energy saving settings, as enabling that option would trigger a similar behavior after a break long enough for that setting to trigger. I would come back on a laptop having self-rebooted and waiting for my input on the FDE passphrase prompt. During ACPI options testing, I noticed that setting might cause the sleep order to get cancelled. From that, I suspect in that case the laptop would go to sleep, then wake up immediately, which could have been triggering the bug as I described previously that rapid state changes would increase probability. Then as I described earlier, if I do nothing when this happens, the computer eventually reboots. This is only speculation as I'm usually not here to observe the behavior (this mostly happened during lunch breaks, which are long enough for all of these steps to happen). I disabled screen turn-off energy saving option a long while ago and have taken the habit of manually suspending to RAM when I intend on going away from the computer for more than a few minutes. As I described above, I've tried a few changes to check for behavior but that was a few months ago and I don't clearly remember all scenario. What I remember is that changing any of these did not resolve my issue and some even prevented my computer to even suspend to RAM properly (waking up immediately after). Among the options I tried is: - booting with a previous kernel, but then it's been happening for so long this would obviously not work (just for the sake of completion) - booting on latest mainstream kerne
[Kernel-packages] [Bug 2024287] [NEW] Wayland session not working with nvidia-driver-530 (proprietary, tested) on high refresh rate monitors.
Public bug reported: The currently "tested" Nvidia driver 530 has a critical bug which causes Wayland sessions to crash during logon. It affects all desktop environments but apparently it only happens when the monitor refresh rate is more than 120hz. https://forums.developer.nvidia.com/t/cant-boot-into-kde-wayland- session-with-530-30-02/244559/42 https://forums.developer.nvidia.com/t/rtx4090-530-drivers-not-working- on-wayland-gnome-screen-turns-off-works-on-xorg/249204 Apparently it is solved in driver version 535.54.03 which is not yet available in the Ubuntu repos. Downgrading to nvidia-driver-525 solves the problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 17 14:03:10 2023 InstallationDate: Installed on 2021-08-24 (661 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: Upgraded to lunar on 2023-04-20 (57 days ago) ** Affects: nvidia-graphics-drivers-530 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-530 in Ubuntu. https://bugs.launchpad.net/bugs/2024287 Title: Wayland session not working with nvidia-driver-530 (proprietary, tested) on high refresh rate monitors. Status in nvidia-graphics-drivers-530 package in Ubuntu: New Bug description: The currently "tested" Nvidia driver 530 has a critical bug which causes Wayland sessions to crash during logon. It affects all desktop environments but apparently it only happens when the monitor refresh rate is more than 120hz. https://forums.developer.nvidia.com/t/cant-boot-into-kde-wayland- session-with-530-30-02/244559/42 https://forums.developer.nvidia.com/t/rtx4090-530-drivers-not-working- on-wayland-gnome-screen-turns-off-works-on-xorg/249204 Apparently it is solved in driver version 535.54.03 which is not yet available in the Ubuntu repos. Downgrading to nvidia-driver-525 solves the problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 17 14:03:10 2023 InstallationDate: Installed on 2021-08-24 (661 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: Upgraded to lunar on 2023-04-20 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2024287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020395] [NEW] No sound on ROG STRIX X670E-E GAMING WIFI
Public bug reported: alsa-ucm-conf is very out of date on 22.04, hardware support for a ton of motherboards that use the ALC4080 is missing. Please update to v1.2.9 released a few weeks ago which fixes this. https://github.com/alsa-project/alsa-ucm-conf/releases/tag/v1.2.9 ** Affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2020395 Title: No sound on ROG STRIX X670E-E GAMING WIFI Status in alsa-ucm-conf package in Ubuntu: New Bug description: alsa-ucm-conf is very out of date on 22.04, hardware support for a ton of motherboards that use the ALC4080 is missing. Please update to v1.2.9 released a few weeks ago which fixes this. https://github.com/alsa-project/alsa-ucm-conf/releases/tag/v1.2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2020395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013316] [NEW] package linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-35-generic package pre-removal script subproces
Public bug reported: It crashed on startup ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 28 09:25:19 2023 ErrorMessage: installed linux-image-5.19.0-35-generic package pre-removal script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-35-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-10-04 (176 days ago) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2013316 Title: package linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-35-generic package pre- removal script subprocess returned error exit status 1 Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: It crashed on startup ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 28 09:25:19 2023 ErrorMessage: installed linux-image-5.19.0-35-generic package pre-removal script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-35-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-10-04 (176 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2013316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011924] Re: Can't adjust brightness on MacBookPro9, 2
Brightness controls are working normally again as of updates today (at least; I haven't had access to this machine for a few days). Also working in a live session of daily-live build 20230325. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2011924 Title: Can't adjust brightness on MacBookPro9,2 Status in linux package in Ubuntu: Fix Released Bug description: Since installing updates to Lunar roughly a week ago, there has been no way to adjust the brightness on my MacBookPro9,2. There are no brightness controls in the GNOME system menu (in the upper right) or in the Settings app. The brightness keys also don't do anything. The issue occurs on Wayland and X11 GNOME sessions. It had previously worked fine in Lunar and earlier Ubuntu versions. I tried clean installing Lunar (and updating) with no change. I tried booting to a 22.04 live session, and brightness controls do appear and work normally. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.1.0-16-generic 6.1.0-16.16 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtech 1466 F wireplumber /dev/snd/seq:mtech 1463 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 16 13:36:55 2023 InstallationDate: Installed on 2023-03-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) MachineType: Apple Inc. MacBookPro9,2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=01a674e8-5e68-4287-990f-859e738f1c29 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230302.git60971a64-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 233.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr233.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011924] [NEW] Can't adjust brightness on MacBookPro9, 2
Public bug reported: Since installing updates to Lunar roughly a week ago, there has been no way to adjust the brightness on my MacBookPro9,2. There are no brightness controls in the GNOME system menu (in the upper right) or in the Settings app. The brightness keys also don't do anything. The issue occurs on Wayland and X11 GNOME sessions. It had previously worked fine in Lunar and earlier Ubuntu versions. I tried clean installing Lunar (and updating) with no change. I tried booting to a 22.04 live session, and brightness controls do appear and work normally. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.1.0-16-generic 6.1.0-16.16 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtech 1466 F wireplumber /dev/snd/seq:mtech 1463 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 16 13:36:55 2023 InstallationDate: Installed on 2023-03-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) MachineType: Apple Inc. MacBookPro9,2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=01a674e8-5e68-4287-990f-859e738f1c29 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230302.git60971a64-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 233.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr233.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2011924 Title: Can't adjust brightness on MacBookPro9,2 Status in linux package in Ubuntu: Confirmed Bug description: Since installing updates to Lunar roughly a week ago, there has been no way to adjust the brightness on my MacBookPro9,2. There are no brightness controls in the GNOME system menu (in the upper right) or in the Settings app. The brightness keys also don't do anything. The issue occurs on Wayland and X11 GNOME sessions. It had previously worked fine in Lunar and earlier Ubuntu versions. I tried clean installing Lunar (and updating) with no change. I tried booting to a 22.04 live session, and brightness controls do appear and work normally. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.1.0-16-generic 6.1.0-16.16 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtech 1466 F wireplumber /dev/snd/seq:mtech 1463 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 16 13:36:55 2023 InstallationDate: Installed on 2023-03-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) MachineType: Apple Inc. MacBookPro9,2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=01a674e8-5e68-4287-990f-859e738f1c29 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230302.git60971a64-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 233.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vend
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Hello ChengEn, Du , Thanks for the test Kernel. I can no longer find a problem with this Kernel and NFS client. I also think that the kernel has fixed the problem. Best 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMwa
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
What I have noticed now only occurs at NFS clients, not with the NFS server. NFS Client Server that create a large amount of simultaneous accesses have the problem. NFS Client Server that create few accesses do not have the problem. We have now booted our web servers on an older kernel version and the problem was gone. Even if the NFS Server servers have the current 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version:
[Kernel-packages] [Bug 2009325] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651922/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:p
[Kernel-packages] [Bug 2009325] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651921/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvr
[Kernel-packages] [Bug 2009325] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651924/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnI
[Kernel-packages] [Bug 2009325] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651925/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnolog
[Kernel-packages] [Bug 2009325] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651923/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone
[Kernel-packages] [Bug 2009325] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651915/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlat
[Kernel-packages] [Bug 2009325] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651920/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlat
[Kernel-packages] [Bug 2009325] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651918/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:p
[Kernel-packages] [Bug 2009325] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651917/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:p
[Kernel-packages] [Bug 2009325] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651913/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnInt
[Kernel-packages] [Bug 2009325] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651919/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnI
[Kernel-packages] [Bug 2009325] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651916/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVir
[Kernel-packages] [Bug 2009325] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651912/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:p
[Kernel-packages] [Bug 2009325] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651911/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform
[Kernel-packages] [Bug 2009325] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651914/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:p
[Kernel-packages] [Bug 2009325] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651910/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVir
[Kernel-packages] [Bug 2009325] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651909/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntel
[Kernel-packages] [Bug 2009325] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651908/+files/ProcCpuinfo.txt ** Description changed: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Mär 4 15:03 seq + crw-rw 1 root audio 116, 33 Mär 4 15:03 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.28 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: VMware, Inc. VMware Virtual Platform + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 svgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop + ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-43-generic N/A + linux-backports-modules-5.0.0-43-generic N/A + linux-firmware1.173.21 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic + Uname: Linux 5.0.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 12/12/2018 + dmi.bios.vendor: Phoenix Technologies LTD + dmi.bios.version: 6.00 + dmi.board.name: 440BX Desktop Reference Platform + dmi.board.vendor: Intel Corporation + dmi.board.version: None + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 1 + dmi.chassis.vendor: No Enclosure + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: + dmi.product.name: VMware Virtual Platform + dmi.product.version: None + dmi.sys.vendor: VMware, Inc. -- You received this bug notification because you are a member of Kernel
[Kernel-packages] [Bug 2009325] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651906/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnInt
[Kernel-packages] [Bug 2009325] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651907/+files/Lspci-vt.txt ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMware
[Kernel-packages] [Bug 2009325] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651905/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
apport information ** Tags added: apport-collected focal ** Description changed: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Mär 4 15:00 seq + crw-rw 1 root audio 116, 33 Mär 4 15:00 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.25 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: + + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: VMware, Inc. VMware Virtual Platform + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 svgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop + ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-67-generic N/A + linux-backports-modules-5.15.0-67-generic N/A + linux-firmware 1.187.36 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal + Uname: Linux 5.15.0-67-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 11/12/2020 + dmi.bios.release: 4.6 + dmi.bios.vendor: Phoenix Technologies LTD + dmi.bios.version: 6.00 + dmi.board.name: 440BX Desktop Reference Platform + dmi.board.vendor: Intel Corporation + dmi.board.version: None + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 1 + dmi.chassis.vendor: No Enclosure + dmi.chassis.version: N/A + dmi.ec.firmware.release: 0.0 + dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: + dmi.product.name: VMware Virtual Platform + dmi.product.version: None + dmi.sys.vendor: VMware, Inc. ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2009325/+attachment/5651904/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or dire
[Kernel-packages] [Bug 2009325] [NEW] NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Public bug reported: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: New Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918252] Re: WWAN Q SD X55 LTE+5G (Huawei for HP) doesn't work [03f0:0a6c]
The linked entry seems to mention the same HW and might help to reduce the complexity of implementation: https://forums.lenovo.com/t5/Other-Linux-Discussions/Finally-X55-5G-modem-works-under-linux/m-p/5082236 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918252 Title: WWAN Q SD X55 LTE+5G (Huawei for HP) doesn't work [03f0:0a6c] Status in linux package in Ubuntu: Confirmed Bug description: There is no driver for it [03f0:0a6c]. using 5.10 kernel. $ sudo lspci -nnnv -s 55:00.0 55:00.0 Wireless controller [0d40]: Device [03f0:0a6c] Subsystem: Hewlett-Packard Company Device [103c:877f] Flags: fast devsel Memory at 6e30 (64-bit, non-prefetchable) [disabled] [size=4K] Memory at 6e301000 (64-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Secondary PCI Express Capabilities: [168] Physical Layer 16.0 GT/s Capabilities: [18c] Lane Margining at the Receiver Capabilities: [19c] Transaction Processing Hints Capabilities: [228] Latency Tolerance Reporting Capabilities: [230] L1 PM Substates Capabilities: [240] Data Link Feature To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990190] Re: Focal update: v5.4.211 upstream stable release
It seems that commit bcf91619e32fe584ecfafa49a3db3d1db4ff70b2 included in 5.4.0-132.148 breaks Node Exporter and cadvisor, cf. https://github.com/prometheus/node_exporter/issues/2500. A minimal reproducer in Go is available at https://github.com/prometheus/node_exporter/issues/2500#issuecomment-1304847221 I have reverted that commit in my test environment and haven't been able to reproduce the problem since. ** Bug watch added: github.com/prometheus/node_exporter/issues #2500 https://github.com/prometheus/node_exporter/issues/2500 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990190 Title: Focal update: v5.4.211 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.211 upstream stable release from git://git.kernel.org/ Makefile: link with -z noexecstack --no-warn-rwx-segments x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments scsi: Revert "scsi: qla2xxx: Fix disk failure to rediscover" ALSA: bcd2000: Fix a UAF bug on the error path of probing igc: Remove _I_PHY_ID checking wifi: mac80211_hwsim: fix race condition in pending packet wifi: mac80211_hwsim: add back erroneously removed cast wifi: mac80211_hwsim: use 32-bit skb cookie add barriers to buffer_uptodate and set_buffer_uptodate HID: wacom: Only report rotation for art pen HID: wacom: Don't register pad_input for touch switch KVM: nVMX: Snapshot pre-VM-Enter BNDCFGS for !nested_run_pending case KVM: nVMX: Snapshot pre-VM-Enter DEBUGCTL for !nested_run_pending case KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0 KVM: nVMX: Let userspace set nVMX MSR to any _host_ supported value KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP mm/mremap: hold the rmap lock in write mode when moving page table entries. ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model ALSA: hda/cirrus - support for iMac 12,1 model ALSA: hda/realtek: Add quirk for another Asus K42JZ model tty: vt: initialize unicode screen buffer vfs: Check the truncate maximum size in inode_newsize_ok() fs: Add missing umask strip in vfs_tmpfile thermal: sysfs: Fix cooling_device_stats_setup() error code path fbcon: Fix boundary checks for fbcon=vc:n1-n2 parameters usbnet: Fix linkwatch use-after-free on disconnect ovl: drop WARN_ON() dentry is NULL in ovl_encode_fh() parisc: Fix device names in /proc/iomem parisc: io_pgetevents_time64() needs compat syscall in 32-bit compat mode drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error drm/nouveau: fix another off-by-one in nvbios_addr drm/amdgpu: Check BO's requested pinning domains against its preferred_domains iio: light: isl29028: Fix the warning in isl29028_remove() fuse: limit nsec serial: mvebu-uart: uart2 error bits clearing md-raid10: fix KASAN warning ia64, processor: fix -Wincompatible-pointer-types in ia64_get_irr() PCI: Add defines for normal and subtractive PCI bridges powerpc/fsl-pci: Fix Class Code of PCIe Root Port powerpc/ptdump: Fix display of RW pages on FSL_BOOK3E powerpc/powernv: Avoid crashing if rng is NULL MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK coresight: Clear the connection field properly USB: HCD: Fix URB giveback issue in tasklet function ARM: dts: uniphier: Fix USB interrupts for PXs2 SoC arm64: dts: uniphier: Fix USB interrupts for PXs3 SoC netfilter: nf_tables: fix null deref due to zeroed list head epoll: autoremove wakers even more aggressively x86: Handle idle=nomwait cmdline properly for x86_idle arm64: Do not forget syscall when starting a new thread. arm64: fix oops in concurrently setting insn_emulation sysctls ext2: Add more validity checks for inode counts genirq: Don't return error on missing optional irq_request_resources() wait: Fix __wait_event_hrtimeout for RT/DL tasks ARM: dts: imx6ul: add missing properties for sram ARM: dts: imx6ul: change operating-points to uint32-matrix ARM: dts: imx6ul: fix csi node compatible ARM: dts: imx6ul: fix lcdif node compatible ARM: dts: imx6ul: fix qspi node compatible spi: synquacer: Add missing clk_disable_unprepare() ARM: OMAP2+: display: Fix refcount leak bug ACPI: EC: Remove duplicate Thin
[Kernel-packages] [Bug 1980848] Re: arc_summary doesn't work with HWE kernel 5.15
I can confirm that the (naive) patch sidesteps the issue, but that it is otherwise present on all our 5.15/ZFS installs. -- 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/1980848 Title: arc_summary doesn't work with HWE kernel 5.15 Status in zfs-linux package in Ubuntu: Confirmed Bug description: # Issue description `arc_summary` no longer works with kernel 5.15. It used to work with previous kernel like 5.13. # Steps to reproduce 1) setup 20.04 with HWE kernel 5.15 2) install `zfsutils-linux` 3) run `arc_summary` $ arc_summary Traceback (most recent call last): File "/usr/sbin/arc_summary", line 875, in main() File "/usr/sbin/arc_summary", line 826, in main kstats = get_kstats() File "/usr/sbin/arc_summary", line 259, in get_kstats with open(PROC_PATH+section, 'r') as proc_location: FileNotFoundError: [Errno 2] No such file or directory: '/proc/spl/kstat/zfs/xuio_stats' Indeed, the xuio_stats file isn't there anymore: $ ll /proc/spl/kstat/zfs/ total 0 dr-xr-xr-x 21 root root 0 Jul 6 10:49 ./ dr-xr-xr-x 4 root root 0 Jul 6 10:49 ../ -rw-r--r-- 1 root root 0 Jul 6 10:49 abdstats -rw-r--r-- 1 root root 0 Jul 6 10:49 arcstats dr-xr-xr-x 20 root root 0 Jul 6 10:49 data/ -rw--- 1 root root 0 Jul 6 10:49 dbgmsg -rw--- 1 root root 0 Jul 6 10:49 dbufs -rw-r--r-- 1 root root 0 Jul 6 10:49 dbufstats dr-xr-xr-x 70 root root 0 Jul 6 10:49 default/ -rw-r--r-- 1 root root 0 Jul 6 10:49 dmu_tx -rw-r--r-- 1 root root 0 Jul 6 10:49 dnodestats -rw-r--r-- 1 root root 0 Jul 6 10:49 fletcher_4_bench -rw-r--r-- 1 root root 0 Jul 6 10:49 fm -rw-r--r-- 1 root root 0 Jul 6 10:49 import_progress -rw-r--r-- 1 root root 0 Jul 6 10:49 metaslab_stats -rw-r--r-- 1 root root 0 Jul 6 10:49 vdev_cache_stats -rw-r--r-- 1 root root 0 Jul 6 10:49 vdev_mirror_stats -rw-r--r-- 1 root root 0 Jul 6 10:49 vdev_raidz_bench -rw-r--r-- 1 root root 0 Jul 6 10:49 zfetchstats -rw-r--r-- 1 root root 0 Jul 6 10:49 zil -rw-r--r-- 1 root root 0 Jul 6 10:49 zstd # Workaround This (naive) patch sidesteps the problem: $ diff -Naur /usr/sbin/arc_summary.old /usr/sbin/arc_summary --- /usr/sbin/arc_summary.old 2022-07-06 10:59:50.752833101 -0400 +++ /usr/sbin/arc_summary 2022-07-06 10:59:22.449113169 -0400 @@ -255,6 +255,8 @@ secs = SECTION_PATHS.values() for section in secs: +if not os.path.exists(PROC_PATH+section): +continue with open(PROC_PATH+section, 'r') as proc_location: lines = [line for line in proc_location] # Additional information $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 $ uname -r 5.15.0-41-generic $ apt-cache policy zfsutils-linux linux-image-generic-hwe-20.04 zfsutils-linux: Installed: 0.8.3-1ubuntu12.14 Candidate: 0.8.3-1ubuntu12.14 Version table: *** 0.8.3-1ubuntu12.14 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages linux-image-generic-hwe-20.04: Installed: 5.15.0.41.44~20.04.13 Candidate: 5.15.0.41.44~20.04.13 Version table: *** 5.15.0.41.44~20.04.13 400 400 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.13.0.52.59~20.04.31 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1980848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988475] [NEW] 22.04 and vc4-fkms-v3d / vc4-kms-v3d overlays problem
Public bug reported: I have RPi4/8GB RAM. I had no problems with 20.04LTS. 'fkms' overlay was used by default, and I never changed it. I have serious problem after upgrade to 22.04. 1. vc4-fkms-v3d overlay (is used by default) causes very big lags in windows dragging by mouse. Also video player (any) freezes the video while mouse is moved across the screen. Sound goes OK though. 2. vc4-kms-v3d works softly, without any lags, when 'builtin-Xpresent' or 'picom:GLX' window manager is on. But both 'vc4-kms-v3d' and 'vc4-kms-v3d-pi4' cause random HDMI signal disappearance when video is running in any video player (both Celluloid and VLC were tested). Screen becomes black, then "No signal" message appears. Green "SD-card access" indicator is on at this time. This behavior was checked in both 20.04LTS and 22.04LTS. But 'fkms' overlay worked OK in 20.04, so it was the solution there. Now in 22.04 I have no solution, so I need to downgrade back to 20.04 unless this bug will be fixed. Also I tried to install KODI in 22.04. It runs with permanent (100%-reproduced) bug, as it was described above. Black screen appears instead of main KODI menu, then "No signal" message appears. Of course, it so happens only with 'kms' overlay. 'fkms' overlay works for KODI, though with big visual lags, as it was described above. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- 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/1988475 Title: 22.04 and vc4-fkms-v3d / vc4-kms-v3d overlays problem Status in linux-raspi package in Ubuntu: New Bug description: I have RPi4/8GB RAM. I had no problems with 20.04LTS. 'fkms' overlay was used by default, and I never changed it. I have serious problem after upgrade to 22.04. 1. vc4-fkms-v3d overlay (is used by default) causes very big lags in windows dragging by mouse. Also video player (any) freezes the video while mouse is moved across the screen. Sound goes OK though. 2. vc4-kms-v3d works softly, without any lags, when 'builtin-Xpresent' or 'picom:GLX' window manager is on. But both 'vc4-kms-v3d' and 'vc4-kms-v3d-pi4' cause random HDMI signal disappearance when video is running in any video player (both Celluloid and VLC were tested). Screen becomes black, then "No signal" message appears. Green "SD-card access" indicator is on at this time. This behavior was checked in both 20.04LTS and 22.04LTS. But 'fkms' overlay worked OK in 20.04, so it was the solution there. Now in 22.04 I have no solution, so I need to downgrade back to 20.04 unless this bug will be fixed. Also I tried to install KODI in 22.04. It runs with permanent (100%-reproduced) bug, as it was described above. Black screen appears instead of main KODI menu, then "No signal" message appears. Of course, it so happens only with 'kms' overlay. 'fkms' overlay works for KODI, though with big visual lags, as it was described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1988475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988470] [NEW] System runs into emergency mode if SSD is missing
Public bug reported: I have M.2 SSD, attached to USB3 port. Everything worked fine in 20.04LTS. I could detach the drive, then boot the system, and it ran correctly in UI mode with desktop, etc. I have another behavior after upgrade to 22.04LTS with 5.15.0.1013 core. Now the system boots into emergency mode with command prompt, if SSD is detached. SSD linking is defined in the /etc/fstab. System works fine if SSD is attached to USB3 port before power is on. Also I can attach SDD when the system is in the command prompt mode (see above) then reboot from the command line, then system will boot the GUI. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- 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/1988470 Title: System runs into emergency mode if SSD is missing Status in linux-raspi package in Ubuntu: New Bug description: I have M.2 SSD, attached to USB3 port. Everything worked fine in 20.04LTS. I could detach the drive, then boot the system, and it ran correctly in UI mode with desktop, etc. I have another behavior after upgrade to 22.04LTS with 5.15.0.1013 core. Now the system boots into emergency mode with command prompt, if SSD is detached. SSD linking is defined in the /etc/fstab. System works fine if SSD is attached to USB3 port before power is on. Also I can attach SDD when the system is in the command prompt mode (see above) then reboot from the command line, then system will boot the GUI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1988470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
Thanks to Stefan Bader, Andrea Righi and Kleber Souza. Looks like
patches were applied to all supported and affected kernels.
https://lists.ubuntu.com/archives/kernel-team/2022-August/132662.html
https://lists.ubuntu.com/archives/kernel-team/2022-August/132688.html
https://lists.ubuntu.com/archives/kernel-team/2022-August/132781.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
** Description changed:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce patch:
- UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
+ UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
- No specific test case provided.
+ The following script can be used to trigger the issue:
+ #!/bin/bash
+
+ cat > test.py << EOF
+ import sys
+
+ f = open("/proc/self/maps")
+
+ for l in f.readlines():
+ if "python" not in l:
+ continue
+ print(l)
+ s = l.split()
+ start, end = s[0].split("-")
+ fname = s[-1]
+ print(start, end, fname)
+ break
+ else:
+ sys.exit(1)
+
+ test_file1 = open(fname)
+ test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
+
+ fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
+ fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
+
+ if fdinfo1 != fdinfo2:
+ print("FAIL")
+ print(test_file1)
+ print(fdinfo1)
+ print(test_file2)
+ print(fdinfo2)
+ sys.exit(1)
+ print("PASS")
+ EOF
+ sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
The original SAUCE patch relies on AUFS in order to use vma->vm_prfile,
but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to be
dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions in
overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
It was discovered that we also have problems with
Focal/hwe-5.13/hwe-5.15 and Kinetic/master kernels too. Patches were
sent.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
** Tags removed: verification-needed-jammy
** Tags added: verification-failed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
I've changed state because technically, issue still persists on the Ubuntu
Jammy in default kernel configurations. I've prepared fixes for two kernels:
- master-next
- hwe-5.17
I'm not sure if I need to port these changes to some other branches. I
think I need some advice from ubuntu kernel team guys regarding this.
** Changed in: linux (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
fix for Jammy linux kernel 5.15 master-next branch was sent to kernel-
t...@lists.ubuntu.com
** Patch added:
"0001-UBUNTU-SAUCE-overlayfs-remove-CONFIG_AUFS_FS-depende.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+attachment/5606321/+files/0001-UBUNTU-SAUCE-overlayfs-remove-CONFIG_AUFS_FS-depende.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
Fix for Jammy linux master branch (linux kernel 5.15) will be ready
tomorrow.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
Fix for Jammy hwe-5.17 was sent to kernel-t...@lists.ubuntu.com
** Attachment added: "Jammy hwe-5.17"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+attachment/5606318/+files/jammy-hwe-5.17.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
Ugh, it looks like CONFIG_AUFS_FS is disabled in all branches of jammy
kernel. It means that this fix commit is totally useless. Okay, I'll fix
that too :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
Dmitry, couldn't you show:
cat /boot/config-$(uname -r) | grep AUFS
?
5.15 kernel it's master branch, this branch contains corresponding fix:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/tree/fs/overlayfs/file.c?h=master#n493
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
As far as I understand hwe kernels on Jammy lacks aufs, so our fix for
shiftfs+overlayfs was dropped on these kernels. I'll work on the proper
fixes for these kernels and send it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983070] [NEW] Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook
Public bug reported: I just installed Ubuntu 22.04 on my new laptop Asus Vivobook Pro 15 OLED. I noticed a weird behavior when the screens goes locked, the brightness level is automatically increased when the screen turns on back again. I also noticed that the file /sys/class/backlight/amdgpu_bl0/actual_brightness is automatically changed to a higher level that the one that I had before the screen went locked. The problem WAS NOT PRESENT in kernel version 15.5.0-25-generic. After that version the problem comes as described. Thank you. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexrm 1954 F pulseaudio /dev/snd/controlC0: alexrm 1954 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 28 22:39:38 2022 InstallationDate: Installed on 2022-07-29 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop M3500QA_M3500QA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=6094f527-24fc-43a9-b689-6a3922fec129 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: M3500QA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M3500QA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrM3500QA.308:bd04/27/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopM3500QA_M3500QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM3500QA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Vivobook dmi.product.name: Vivobook_ASUSLaptop M3500QA_M3500QA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy regression-release regression-update wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983070 Title: Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook Status in linux package in Ubuntu: New Bug description: I just installed Ubuntu 22.04 on my new laptop Asus Vivobook Pro 15 OLED. I noticed a weird behavior when the screens goes locked, the brightness level is automatically increased when the screen turns on back again. I also noticed that the file /sys/class/backlight/amdgpu_bl0/actual_brightness is automatically changed to a higher level that the one that I had before the screen went locked. The problem WAS NOT PRESENT in kernel version 15.5.0-25-generic. After that version the problem comes as described. Thank you. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexrm 1954 F pulseaudio /dev/snd/controlC0: alexrm 1954 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 28 22:39:38 2022 InstallationDate: Installed on 2022-07-29 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop M3500QA_M3500QA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=6094f527-24fc-43a9-b689-6a3922fec129 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: M3500QA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M3500QA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset
[Kernel-packages] [Bug 1971428] Re: CPU pipe A FIFO underrun
Same here on Lenovo Thinkpad T490 with i915 and external monitor attached via Thunderbolt. External monitor goes black several times a day. Only when I move the mouse cursor into the lower 10% part of the monitor screen. It stays black if I don't move the mouse. Once I move the mouse, the screen comes back. It does not always happen in that lower 10% part. But when it happens, the cursor is in that area. Around that time I see in dmesg: i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun I tried a fix from here: https://bbs.archlinux.org/viewtopic.php?id=263720 But adding the kernel parameter intel_idle.max_cstate=4 did not help in my case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971428 Title: CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Bug description: Upgraded from Ubuntu 20.04 to 22.04 at the release date. I get a blinking screen about 2-3 times a day. Dmesg shows the following: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Lenovo Thinkpad T480s connected to Lenovo Thinkpad Basic Docking Station, type 40AG. I'm not doing anything special when this happens. I've been using the same monitor, dock and cables for several years. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: oystein6834 F wireplumber /dev/snd/controlC1: oystein6834 F wireplumber /dev/snd/controlC0: oystein6834 F wireplumber /dev/snd/seq:oystein6832 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 3 14:46:03 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-08-03 (273 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20L8002VMX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e9eb1db1-6947-4826-85ca-b36e8bdf8f75 ro quiet splash i915.enable_psr=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-21 (11 days ago) WifiSyslog: dmi.bios.date: 11/17/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET72W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8002VMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN22ET72W(1.49):bd11/17/2021:br1.49:efr1.22:svnLENOVO:pn20L8002VMX:pvrThinkPadT480s:rvnLENOVO:rn20L8002VMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8002VMX dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570
I experience the same on my Lenovo Thinkpad (Intel® Xeon(R) E-2176M CPU @ 2.70GHz × 12 ) with ubuntu 18.04 and the *-177 kernel. No wireless, no external monitor detected. Happened after a hard reset. Switching to previous kernel fixes everything. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973482 Title: kernel 4.15.0.177 break everything on Dell XPS 15 9570 Status in linux package in Ubuntu: Confirmed Bug description: There are many issues including: - wireless card DISBLED / UNCLAIMED - no sound output device listed - strange electrical noise in the speakers when the cpu is under load - mounting /boot/efi hangs for 1m30 - various services not starting (snap, etc) Rolling back to 4.15.0.176 fixes all the issues. Can you let me know which logs I could provide to help? Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18 Uname: Linux 4.15.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 16 00:39:58 2022 InstallationDate: Installed on 2018-12-15 (1247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: virbr0no wireless extensions. lono wireless extensions. virbr0-nic no wireless extensions. MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off clocksource=hpet RelatedPackageVersions: linux-restricted-modules-4.15.0-177-generic N/A linux-backports-modules-4.15.0-177-generic N/A linux-firmware 1.173.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
Hi Andrea,
thanks a lot!
1. In my original patch here:
https://patchwork.ozlabs.org/project/ubuntu-kernel/patch/20210426081121.37363-1-alexan...@mihalicyn.com/
there was no "fput" call inside ovl_vm_prfile_set helper. fput was in
the outer ovl_mmap() function in fs/overlayfs/file.c
You last fix looks fully correct.
2. If we compare ovl_mmap function between 5.8 branch and 5.15:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/fs/overlayfs/file.c?h=hwe-5.8#n461
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/tree/fs/overlayfs/file.c?h=hwe-5.15-next&id=e3e60b65fa4db4722bd4b02a9dae58f7ff5d83d2#n528
we can see that ovl_mmap function was changed after:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/fs/overlayfs/file.c?h=hwe-5.15-next&id=2896900e22f8212606a1837d89a6bbce314ceeda
that's the point where the problem was introduced and ovl_vm_prfile_set
with this "fput" become incorrect.
Right now, with your fix all seems correct.
3. But there is a question. Can we split this thing out of AUFS? As I mentioned
before all that we really need here is this part:
https://github.com/JPyke3/mbp-manjaro-kernel/blob/master/aufs5-mmap.patch
Why we can't remove this `#if IS_ENABLED(CONFIG_AUFS_FS)` and use "shadow file"
helper all the time?
I'm ready to prepare and test full version of patches to achieve that if it's
needed.
Regards,
Alex
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
Hi Andrea,
Do I understand you correctly, that this patch without AUFS works fine,
but on kernels with AUFS enabled it triggers the issue described above?
Please, feel free to ping me if you need help with reworking that.
Thanks a lot for your attention to this problem!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: One overlayfs fix has not been backported to the 5.13 branch
We have a minimal reproducer test for this issue prepared by Andrei in the
original commit description
https://patchwork.ozlabs.org/project/ubuntu-kernel/patch/20210426081121.37363-1-alexan...@mihalicyn.com/
--
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/1967924
Title:
One overlayfs fix has not been backported to the 5.13 branch
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: One overlayfs fix has not been backported to the 5.13 branch
Hello, Andrea!
Thanks a lot for your attention to this problem!
This patch lightly relies on AUFS.
All that we need is
https://github.com/JPyke3/mbp-manjaro-kernel/blob/master/aufs5-mmap.patch
to bring needed helpers. Can we keep these changes in ubuntu sauce after AUFS
will be dropped?
Please, reach me if it's needed to prepare some patches to the Ubuntu kernel
and send it from our (CRIU project) side.
Regards,
Alex
--
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/1967924
Title:
One overlayfs fix has not been backported to the 5.13 branch
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: One overlayfs fix has not been backported to the 5.13 branch
** Summary changed:
- One overlayfs fix has not been backported to the 5.13 bracnh
+ One overlayfs fix has not been backported to the 5.13 branch
--
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/1967924
Title:
One overlayfs fix has not been backported to the 5.13 branch
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: One overlayfs fix has not been backported to the 5.13 bracnh
Thanks, Andrew!
That's really strange that this fix wasn't ported.
All needed helpers are present:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/focal/tree/mm/prfile.c?h=azure-5.13-next
--
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/1967924
Title:
One overlayfs fix has not been backported to the 5.13 bracnh
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961581] Re: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411'
Thanks for that workaround “i2c-hid-acpi” definitely worked so after next reboot "/etc/modules" will work propably too. Thanks again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1961581 Title: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411' Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Touchpad used to work fine initially but I recently realised that it's not responding at all, since I'm mostly working with an external mouse. Therefore, I'm not sure when this problem started or what really caused it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 12:13:55 2022 InstallationDate: Installed on 2021-11-02 (111 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1961581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961581] Re: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411'
My bug report is this one: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe-5.13/+bug/1963554 just for the sake of completeness. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1961581 Title: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411' Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Touchpad used to work fine initially but I recently realised that it's not responding at all, since I'm mostly working with an external mouse. Therefore, I'm not sure when this problem started or what really caused it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 12:13:55 2022 InstallationDate: Installed on 2021-11-02 (111 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1961581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961581] Re: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411'
Hi this could be a issue of Fujitsu Laptops in general, i have propably the same problem just on a different laptop model. I did issue a similar bug report, because it's a different model, but i think its definitely possible, that this bug is connected to the touchpad that Fujitsu uses in general respectively the manufacturer. If you did find a fix, pleas tell me then i will try it on my model as well. With best regards, Alexander -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1961581 Title: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411' Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Touchpad used to work fine initially but I recently realised that it's not responding at all, since I'm mostly working with an external mouse. Therefore, I'm not sure when this problem started or what really caused it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 12:13:55 2022 InstallationDate: Installed on 2021-11-02 (111 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1961581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956467] Re: powerlight stays on after shutdown
Can confirm same issue with following setup AMD® A12-9720p Ubuntu 20.04 LTS. Suspend is broken in 5.13.0-39-generic and 5.13.0-37-generic, it only works in 5.13.0-35-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956467 Title: powerlight stays on after shutdown Status in linux package in Ubuntu: Confirmed Bug description: After kernel upgrade from 5.11.0.40 to versions 5.11.0.41, 5.11.0.43, 5.11.0.44 power-button light fails to switch off, after shutdown. shutdown can be triggered from command line or via desktop menu, result is the same. After rebooting from 5.11.0.40 normal functionality is restored. systemd appears to complete shutdown looking at the logs (see attached) Switching to suspend mode (sleep) functions as expected (power light blinks) and stays permanently on after wake-up. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christian 1896 F pulseaudio /dev/snd/controlC0: christian 1896 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81MT Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.24 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2019 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN23WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.23 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963554] [NEW] Touchpad of Fujitsu Lifebook U9310X does not work anymore
Public bug reported: What i expect to happen: use touchpad as mouse input device what happend instead: the touchpad does not register any input anymore (did work fine before) and doesn't show up in devices General Information: - the laptop model is the "Fujitsu Lifebook U9310X" - i don't know the manufacturer of the touchpad. I remember not finding anything labeled "touchpad" in "/proc/bus/input/devices" but at that time it worked. I think there was something labeled "3 button" or something like that, but i don't remember correctly - the problem first appeared around end of January i think, but i am not certain about that because if use my notebook mostly docked at the moment with a mouse connected. It certainly did work until around Christmas last 2021. I waited a while for it to maybe get resolved with a patch until now the problem persists. Ubuntu Version: Description:Ubuntu 20.04.4 LTS Release:20.04 not quite sure which package/version i should put here. I added the output of "cat /proc/bus/input/devices > ~/devices" to this bug. If further informations are needed i will gladly help. I really hope someone can help here, best regards aletschius ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Mar 3 22:10:30 2022 InstallationDate: Installed on 2021-07-21 (225 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "output of "cat /proc/bus/input/devices > ~/devices"" https://bugs.launchpad.net/bugs/1963554/+attachment/5565374/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1963554 Title: Touchpad of Fujitsu Lifebook U9310X does not work anymore Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: What i expect to happen: use touchpad as mouse input device what happend instead: the touchpad does not register any input anymore (did work fine before) and doesn't show up in devices General Information: - the laptop model is the "Fujitsu Lifebook U9310X" - i don't know the manufacturer of the touchpad. I remember not finding anything labeled "touchpad" in "/proc/bus/input/devices" but at that time it worked. I think there was something labeled "3 button" or something like that, but i don't remember correctly - the problem first appeared around end of January i think, but i am not certain about that because if use my notebook mostly docked at the moment with a mouse connected. It certainly did work until around Christmas last 2021. I waited a while for it to maybe get resolved with a patch until now the problem persists. Ubuntu Version: Description: Ubuntu 20.04.4 LTS Release: 20.04 not quite sure which package/version i should put here. I added the output of "cat /proc/bus/input/devices > ~/devices" to this bug. If further informations are needed i will gladly help. I really hope someone can help here, best regards aletschius ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Mar 3 22:10:30 2022 InstallationDate: Installed on 2021-07-21 (225 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1963554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956467] Re: powerlight stays on after shutdown
Recent 5.13.0-28-generic kernel update fixed issue for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956467 Title: powerlight stays on after shutdown Status in linux package in Ubuntu: Confirmed Bug description: After kernel upgrade from 5.11.0.40 to versions 5.11.0.41, 5.11.0.43, 5.11.0.44 power-button light fails to switch off, after shutdown. shutdown can be triggered from command line or via desktop menu, result is the same. After rebooting from 5.11.0.40 normal functionality is restored. systemd appears to complete shutdown looking at the logs (see attached) Switching to suspend mode (sleep) functions as expected (power light blinks) and stays permanently on after wake-up. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christian 1896 F pulseaudio /dev/snd/controlC0: christian 1896 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81MT Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.24 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2019 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN23WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.23 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958718] [NEW] Crash on wake with kernel version 5.13
Public bug reported: With "linux-image-5.13.0-27-generic" on Ubuntu 20.04.3 LTS, my notebook (Thinkpad T14) crashes when waking up after being suspended. The screen displays what I would describe as "colourful snow" with some vertical stripes on the right edge of the display. The only thing I can do is power off the machine by holding the power button for several seconds and then restart. With "linux-image-5.11.0-46-generic", this does not happen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 22 16:05:18 2022 InstallationDate: Installed on 2020-12-28 (389 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958718 Title: Crash on wake with kernel version 5.13 Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: With "linux-image-5.13.0-27-generic" on Ubuntu 20.04.3 LTS, my notebook (Thinkpad T14) crashes when waking up after being suspended. The screen displays what I would describe as "colourful snow" with some vertical stripes on the right edge of the display. The only thing I can do is power off the machine by holding the power button for several seconds and then restart. With "linux-image-5.11.0-46-generic", this does not happen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 22 16:05:18 2022 InstallationDate: Installed on 2020-12-28 (389 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1958718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956467] Re: powerlight stays on after shutdown
Same issue here: AMD® A12-9720p radeon r7 Ubuntu 20.04.3 LTS Kernels from 5.11.0-46 to 5.13.0-27 fail at shutdown, restart and suspend. Only working kernel is 5.11.0-40 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956467 Title: powerlight stays on after shutdown Status in linux package in Ubuntu: Confirmed Bug description: After kernel upgrade from 5.11.0.40 to versions 5.11.0.41, 5.11.0.43, 5.11.0.44 power-button light fails to switch off, after shutdown. shutdown can be triggered from command line or via desktop menu, result is the same. After rebooting from 5.11.0.40 normal functionality is restored. systemd appears to complete shutdown looking at the logs (see attached) Switching to suspend mode (sleep) functions as expected (power light blinks) and stays permanently on after wake-up. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christian 1896 F pulseaudio /dev/snd/controlC0: christian 1896 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81MT Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.24 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2019 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN23WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.23 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918252] Re: WWAN Q SD X55 LTE+5G (Huawei for HP) doesn't work [03f0:0a6c]
Hi What is the status of this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918252 Title: WWAN Q SD X55 LTE+5G (Huawei for HP) doesn't work [03f0:0a6c] Status in linux package in Ubuntu: Confirmed Bug description: There is no driver for it [03f0:0a6c]. using 5.10 kernel. $ sudo lspci -nnnv -s 55:00.0 55:00.0 Wireless controller [0d40]: Device [03f0:0a6c] Subsystem: Hewlett-Packard Company Device [103c:877f] Flags: fast devsel Memory at 6e30 (64-bit, non-prefetchable) [disabled] [size=4K] Memory at 6e301000 (64-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Secondary PCI Express Capabilities: [168] Physical Layer 16.0 GT/s Capabilities: [18c] Lane Margining at the Receiver Capabilities: [19c] Transaction Processing Hints Capabilities: [228] Latency Tolerance Reporting Capabilities: [230] L1 PM Substates Capabilities: [240] Data Link Feature To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538693/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538694/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538684/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538695/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538685/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538691/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538692/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538689/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] Re: Warning message in logs after kernel update to linux-image-4.15.0-66-generic
Problem still visible with linux-image-4.15.0-161-generic on Intel NUC5i5MYBE -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538686/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538687/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538688/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538690/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] Re: Warning message in logs after kernel update to linux-image-4.15.0-66-generic
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1302 F pulseaudio /dev/snd/controlC1: bob1302 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=8cc37bc2-8e6b-42a0-8d35-815fac62d66b InstallationDate: Installed on 2015-12-13 (2156 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-161-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-161.169-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-161-generic N/A linux-backports-modules-4.15.0-161-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-161-generic x86_64 UpgradeStatus: Upgraded to bionic on 2020-10-07 (396 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/24/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: MYBDWi5v.86A.0033.2016.1124.2006 dmi.board.name: NUC5i5MYBE dmi.board.vendor: Intel Corporation dmi.board.version: H47797-202 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrMYBDWi5v.86A.0033.2016.1124.2006:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5MYBE:rvrH47797-202:cvn:ct3:cvr: ** Tags added: apport-collected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 003
[Kernel-packages] [Bug 1942627] [NEW] Internal trackpad of ASUS laptop not recognized at all by Ubuntu
Public bug reported: I installed Ubuntu 20.04.3 LTS on a new ASUS TUF706HE-DS74 laptop alonside Windows 10. The trackpad is recognized and functions normally in Windows and in the BIOS UEFI interface. The trackpad has not responded at all anytime I am running Ubuntu. An external mouse works normally in all cases, whether plugged in before boot up or after. Running cat /proc/bus/input/devices resulted in no entry for the trackpad. I also tried running sudo apt install xserver-xorg-input-synaptics and sudo apt update, with no change. I have rebooted with no periferals attached or with different ones attached, and there is no difference in the devices listed when running cat /proc/bus/input/devices. I am attaching the list generated with this report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 10:01:31 2021 InstallationDate: Installed on 2021-08-27 (6 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 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 ** Attachment added: "List of input devices and version information" https://bugs.launchpad.net/bugs/1942627/+attachment/5522861/+files/agunn_trackpad_bug_files.zip -- 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/1942627 Title: Internal trackpad of ASUS laptop not recognized at all by Ubuntu Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I installed Ubuntu 20.04.3 LTS on a new ASUS TUF706HE-DS74 laptop alonside Windows 10. The trackpad is recognized and functions normally in Windows and in the BIOS UEFI interface. The trackpad has not responded at all anytime I am running Ubuntu. An external mouse works normally in all cases, whether plugged in before boot up or after. Running cat /proc/bus/input/devices resulted in no entry for the trackpad. I also tried running sudo apt install xserver-xorg-input-synaptics and sudo apt update, with no change. I have rebooted with no periferals attached or with different ones attached, and there is no difference in the devices listed when running cat /proc/bus/input/devices. I am attaching the list generated with this report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 10:01:31 2021 InstallationDate: Installed on 2021-08-27 (6 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 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/1942627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
Tested the kernel provided now and it seems to still act the same. Attaching GIF with output of the `watch -n0 cat /proc/interrupts` command. I also tried switching the sleep mode back to the default (S0ix) yesterday and this seems to work a lot better with 5.13 kernels than the 5.11 one and preserves battery very well now. I had it set back to "Linux S3" again for this kernel test though. `uname -a` output: Linux lomez 5.13.0-2010-oem #11 SMP Tue Aug 10 13:37:12 CST 2021 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "Peek 2021-08-10 12-37.gif" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938096/+attachment/5517063/+files/Peek%202021-08-10%2012-37.gif -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in linux package in Ubuntu: New Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1
[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
> Can you please run `watch -n0 cat /proc/interrupts` and check whether
"i2c_designware" or "SYNA8009:00" number is increasing without touching
the touchpad?
Tried this now, and yes, both of these ("idma64.0, i2c_designware.0" and
"SYNA8009:00") are increasing while not using the touchpad at all after
resuming from suspend. Right after a reboot these values remain stable
and do not increase while not using it.
> We have an internal bug tracking this and were working with the touchpad
> vendor but strong recommendation is to use Modern Standby/S0ix suspend
> support.
>
> Are you sure you're seeing worse battery time with S0ix? Recommendation from
> Intel is that it is the same as or better than S3 and on these Tigerlake
> CPU's is what Intel are recommending for use.
Awesome!
I only gave the modern standby/sleep a couple of chances in the
beginning, and at that point the laptop battery was drained by the next
morning if I closed the lid on it after work (around 5-6 pm the evening
before). Bear in mind that that was with the stock kernel that came with
Pop 21.04, which is 5.11.0. I can give it a try again now that I am
running 5.13.9, if a lot has changed regarding that since then.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1938096
Title:
[Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after
resume from suspend
Status in libinput package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hardware: Thinkpad X1 Carbon, 9th generation
Touchpad: SYNA8009:00 06CB:CE57
Right after a clean reboot, the touchpad works fine. No issues
whatsoever. But after resuming from even its first suspend after a
clean boot, the touchpad feels less responsive, choppy or even laggy.
I have tried removing and re-inserting some HID kernel modules,
"psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't
found anything that fixes it yet. The trackpoint works flawlessly all
the time, so that is the current backup when I don't have an external
mouse connected.
My installed OS is Pop!_Os 21.04, but I have tested and confirmed this
on a live USB with Ubuntu 21.04 as well.
I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels
from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from
the impish repos.
To recreate:
1. Reboot a X1C9 machine and see that the touchpad works fine
2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a
software suspend)
3. Resume from suspend and see that touchpad acts differently and less
responsive than right after a clean boot
What is expected:
1. Same responsive touchpad experience after resuming from suspend as right
after a clean boot.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: pop:GNOME
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroRelease: Pop!_OS 21.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Iris Xe Graphics [17aa:22d5]
MachineType: LENOVO 20XW005PMX
Package: libinput10 1.18.0-1 [origin: unknown]
PackageArchitecture: amd64
ProcKernelCmdLine:
initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img
root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet
systemd.show_status=false loglevel=0 splash
Tags: hirsute third-party-packages ubuntu
Uname: Linux 5.13.5-051305-generic x86_64
UnreportableReason: This does not seem to be an official Pop!_OS package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm lpadmin plugdev sudo
_MarkForUpload: True
dmi.bios.date: 06/15/2021
dmi.bios.release: 1.42
dmi.bios.vendor: LENOVO
dmi.bios.version: N32ET66W (1.42 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20XW005PMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.26
dmi.modalias:
dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon Gen 9
dmi.product.name: 20XW005PMX
dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1
[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
Further investigation reveals that this only occurs when S3 suspend is enabled in BiOS. The default that is shipped is identified as s2idle in systemd (just called "Windows 10 and Linux" in BiOS[1]) and is a sort of software suspend that does not preserve much battery time (which is also why I switched to S3). S3 is suspend to RAM I think. I have upgraded to a new BiOS release that was made available today (N32ET68W 1.44), and an update to the Embed Controller. This did not help with the issue unfortunately. Seeing as the touchpad works fine with the software suspend, but not the S3 RAM suspend, is there perhaps some module that is not handled correctly when waking up from a more thorough suspend? [1] https://i.imgur.com/7ddEvpW.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-
[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
Update: tested new kernels 5.13.7 and 5.14rc4 now and issue still persists in those kernels as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1938096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
Tested 5.14rc3 from https://kernel.ubuntu.com/~kernel-ppa/mainline now, and the issue occurs there as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1938096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
I am currently using the 5.13.5 kernel from the Ubuntu kernel team here: https://kernel.ubuntu.com/~kernel-ppa/mainline/ I have also tested the 5.14.0rc2 kernel from the same repo. Can give rc3 a try too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1938096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
fine on hirsute with linux-image-5.11.0-18-generic_5.11.0-18.19_amd64 ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute ** Tags removed: verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
fine on groovy linux-image-5.8.0-54-generic ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
fine on focal linux-image-5.4.0-74-generic_5.4.0-74.83_amd64 ** 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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925452] Re: [Ubuntu 21.04]: net/mlx5: Fix HW spec violation configuring uplink (mandatory for 20.04)
Eli Cohen from Mellanox/Nvidia had a look at the back ports and approved them: Both patches look good to me. You can add Reviewed-by: Eli Cohen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925452 Title: [Ubuntu 21.04]: net/mlx5: Fix HW spec violation configuring uplink (mandatory for 20.04) Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: In Progress Bug description: With the 5.4.0-48 update for Ubuntu 20.04, the commit "net/mlx5e: Modify uplink state on interface up/down" was integrated which contains a regression for mlx5 adapters with older adapter firmware. This is the second bugfix to repair the regression, required to operate the adapter in switchdev mode. The first part was integrated via Bug 192185 - LP1921104. This is the upstream fix required to be backported to Ubuntu 20.04: https://github.com/torvalds/linux/commit/1a73704c82ed4ee95532ac04645d02075bd1ce3d ---Additional Hardware Info--- Mellanox ConnectX network adapter ---uname output--- 5.4.0-73-generic ---Steps to Reproduce--- enable switchdev mode try to ping external host Backports need to be provide for 21.04, 20.10 and 20.04 (if not cleanly applyable)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
** Patch added: "ubuntu-focal kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+attachment/5492385/+files/0001-UBUNTU-SAUCE-overlayfs-fix-incorrect-mnt_id-of-files.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
The previous fix was reverted due to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690 that's weird and I can't see any logical connection between the previous fix and problem with docker registry. We proposed a new fix https://lists.openvz.org/pipermail/criu/2021-April/045238.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925452] Re: [Ubuntu 21.04]: net/mlx5: Fix HW spec violation configuring uplink (mandatory for 20.04)
Hi Frank, I think the patch did not apply cleanly on 5.10 an earlier, so we need the backport here for groovy and 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/1925452 Title: [Ubuntu 21.04]: net/mlx5: Fix HW spec violation configuring uplink (mandatory for 20.04) Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: In Progress Bug description: With the 5.4.0-48 update for Ubuntu 20.04, the commit "net/mlx5e: Modify uplink state on interface up/down" was integrated which contains a regression for mlx5 adapters with older adapter firmware. This is the second bugfix to repair the regression, required to operate the adapter in switchdev mode. The first part was integrated via Bug 192185 - LP1921104. This is the upstream fix required to be backported to Ubuntu 20.04: https://github.com/torvalds/linux/commit/1a73704c82ed4ee95532ac04645d02075bd1ce3d ---Additional Hardware Info--- Mellanox ConnectX network adapter ---uname output--- 5.4.0-73-generic ---Steps to Reproduce--- enable switchdev mode try to ping external host Backports need to be provide for 21.04, 20.10 and 20.04 (if not cleanly applyable)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923846] [NEW] Kernel panic
Public bug reported: I use Hyper-V and created VM with "Generation 2", I cannot boot Ubuntu Hirsute Hippo Live CD, it gives me kernel panic, I tried it when there were included 5.11.0-13 and 5.11.0-14 kernels - same result, when there was 5.11.0-11 and older it was fine. ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Kernel panic screenshot" https://bugs.launchpad.net/bugs/1923846/+attachment/5487827/+files/Screenshot%20%28550%29.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1923846 Title: Kernel panic Status in linux-signed package in Ubuntu: New Bug description: I use Hyper-V and created VM with "Generation 2", I cannot boot Ubuntu Hirsute Hippo Live CD, it gives me kernel panic, I tried it when there were included 5.11.0-13 and 5.11.0-14 kernels - same result, when there was 5.11.0-11 and older it was fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1923846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04
Hi Frank, thank you very much! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Triaged Status in linux source package in Groovy: Triaged Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * If a kernel without the backport is used on an adapter which does not have the latest adapter firmware, the adapter silently drops outgoing traffic. * This is a regression which was introduced with kernel 5.4.0-48. [Fix] * upstream fix (as in 5.11): 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" * backport for focal: https://launchpadlibrarian.net/529543695/0001 -Backport-net-mlx5e-Add-missing-capability-check-for-.patch * backport for groovy: https://launchpadlibrarian.net/529775887/0001 -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch [Test Case] * Two IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04 or 20.10 on LPAR, are needed. * Each with RoCE Express 2.x adapters (Mellanox ConnectX4/5) attached and firmware 16.29.1006 or earlier. * Assign an IP address to the adapters on both systems and try to ping one node from the other. * The ping will just fail with the stock Ubuntu kernels (not having the patch), but will succeed with kernels that incl. the patches (like the test builds from the PPA mentioned below). * Due to the lack of hardware this needs to be verified by IBM. [Regression Potential] * Undesired / erroneous behavior in case the modified if condition is assembled in a wrong way. * Again wrong behavior in case the modification of the capability bits in mlx5_ifc_cmd_hca_cap_bits are wrong. * All modification are limited to the mlx5 driver only. * The changes are relatively limited with effectively two lines removed and 4 added (three of them adjustments of the capability bits only). * The modifications were done and tested by IBM and reviewed by Mellanox (see LP comments), based on a PPA test build. [Other] * The above patch/commit was upstream accepted with kernel 5.11. * Hence the patch is not needed for hirsute, just needs to be SRUed for groovy and focal. * The commit couldn't be cleanly cherry-picked, mainly due to changed context, hence the backport(s). __ Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04
Additional comment for the SRU description: this backport fixes a regression which was introduced with the kernel 5.4.0-48 update for Ubuntu 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Triaged Status in linux source package in Groovy: Triaged Status in linux source package in Hirsute: Fix Released Bug description: Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
