[Kernel-packages] [Bug 1327532] Re: err:module:attach_process_dlls krnl386.exe16 failed to initialize, aborting
With latest linux from -updates, I can run apps under wine if I run: sudo sysctl abi.ldt16=1 For this to be applied on boot, I've added a new /etc/sysctl.d/20-wine-ldt16.conf with: abi.ldt16=1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327532 Title: err:module:attach_process_dlls krnl386.exe16 failed to initialize, aborting Status in “linux” package in Ubuntu: Incomplete Bug description: After installing the latest software updates to Trusty, my Win16 apps no longer launch. Attempting to launch from the command line yields the following error messages: err:module:attach_process_dlls krnl386.exe16 failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for LC:\\windows\\system32\\winevdm.exe failed, status c005 Running the 64-bit version of Trusty with the lastest 3.13.0-29 kernel. It worked with the previous 3.13.0-27 kernel. Thanks, --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 2129 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-03 (35 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 274673U Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=4a232e29-6c76-4506-b946-8303ab446fd1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 274673U dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn274673U:pvrThinkPadSL500:rvnLENOVO:rn274673U:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 274673U dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20 - 5.3
** Bug watch added: Linux Kernel Bug Tracker #204837 https://bugzilla.kernel.org/show_bug.cgi?id=204837 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=204837 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 - 5.3 Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) [Fix] Let HID core allow longer input report length. [Test] User confirmed the fix works. [Regression Potential] Low. Longer input report length is now considered valid, shorter input report length doesn't get touched. === Original Bug Report === Dmesg is a constant barrage of the same error: ``` [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) ``` This does not occur in 4.19 but does occur in all mainline 4.20 releases including 4.20.13 (linux-image-unsigned-4.20.13-042013). Tested with both Ubuntu's included libinput 1.10 and an updated libinput 1.12. Hardware (from lspci) includes a synaptic touchpad. Having the xorg synaptic driver installed makes no difference. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1818547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Just to confirm that I still have broken WiFi with linux- image-5.4.0-14-generic 5.4.0-14.17 (but it works with linux- image-5.3.0-26-generic 5.3.0-26.28 and worked with iwlwifi backports when I tried). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi there, Laptop: Dell XPS 13 7390 2-in-1 Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04. Firmware crashes after loading and interface doesn't show up. This is with: linux-image-5.4.0-9-generic 5.4.0-9.12 linux-firmware 1.184 I've noticed the driver was trying to load a more recent firmware: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 I've downloaded this file from upstream iwlwifi firmware git and tried unloading/reloading iwlwifi. Driver crashes as well, but with a different error code. Best, - LM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lool 1579 F pulseaudio /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 15:02:08 2020 InstallationDate: Installed on 2019-12-02 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off plymouth.force-scale=3 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago) dmi.bios.date: 11/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Should also mention I've upgraded all packages to latest in focal including linux-firmware 1.186. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi there, Laptop: Dell XPS 13 7390 2-in-1 Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04. Firmware crashes after loading and interface doesn't show up. This is with: linux-image-5.4.0-9-generic 5.4.0-9.12 linux-firmware 1.184 I've noticed the driver was trying to load a more recent firmware: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 I've downloaded this file from upstream iwlwifi firmware git and tried unloading/reloading iwlwifi. Driver crashes as well, but with a different error code. Best, - LM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lool 1579 F pulseaudio /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 15:02:08 2020 InstallationDate: Installed on 2019-12-02 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off plymouth.force-scale=3 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago) dmi.bios.date: 11/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859287] [NEW] iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Public bug reported: Hi there, Laptop: Dell XPS 13 7390 2-in-1 Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04. Firmware crashes after loading and interface doesn't show up. This is with: linux-image-5.4.0-9-generic 5.4.0-9.12 linux-firmware 1.184 I've noticed the driver was trying to load a more recent firmware: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 I've downloaded this file from upstream iwlwifi firmware git and tried unloading/reloading iwlwifi. Driver crashes as well, but with a different error code. Best, - LM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lool 1579 F pulseaudio /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 15:02:08 2020 InstallationDate: Installed on 2019-12-02 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off plymouth.force-scale=3 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago) dmi.bios.date: 11/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Hi there, Laptop: Dell XPS 13 7390 2-in-1 Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04. Firmware crashes after loading and interface doesn't show up. This is with: linux-image-5.4.0-9-generic 5.4.0-9.12 linux-firmware 1.184 I've noticed the driver was trying to load a more recent firmware: - Direct firmware load for iwlwifi-Qu-b0-hr-b0-49.ucode failed with error -2 + Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 I've downloaded this file from upstream iwlwifi firmware git and tried unloading/reloading iwlwifi. Driver crashes as well, but with a different error code. Best, - LM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: lool 1579 F pulseaudio - /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: lool 1579 F pulseaudio + /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 15:02:08 2020 InstallationDate: Installed on 2019-12-02 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off plymouth.force-scale=3 quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-9-generic N/A - linux-backports-modules-5.4.0-9-generic N/A - linux-firmware 1.184 + linux-restricted-modules-5.4.0-9-generic N/A + linux-backports-modules-5.4.0-9-generic N/A + linux-firmware 1.184 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft
[Kernel-packages] [Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Tried with: linux-image-unsigned-5.5.0-050500rc6-generic_5.5.0-050500rc6.202001122031_amd64.deb linux-modules-5.5.0-050500rc6-generic_5.5.0-050500rc6.202001122031_amd64.deb (after disabling secure boot) => no wifi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi there, Laptop: Dell XPS 13 7390 2-in-1 Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04. Firmware crashes after loading and interface doesn't show up. This is with: linux-image-5.4.0-9-generic 5.4.0-9.12 linux-firmware 1.184 I've noticed the driver was trying to load a more recent firmware: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 I've downloaded this file from upstream iwlwifi firmware git and tried unloading/reloading iwlwifi. Driver crashes as well, but with a different error code. Best, - LM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lool 1579 F pulseaudio /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 15:02:08 2020 InstallationDate: Installed on 2019-12-02 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off plymouth.force-scale=3 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago) dmi.bios.date: 11/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Dkms module worked with 5.4.0-9-generic and current linux-firmware, thanks! ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+attachment/5320091/+files/dmesg.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/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi there, Laptop: Dell XPS 13 7390 2-in-1 Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04. Firmware crashes after loading and interface doesn't show up. This is with: linux-image-5.4.0-9-generic 5.4.0-9.12 linux-firmware 1.184 I've noticed the driver was trying to load a more recent firmware: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 I've downloaded this file from upstream iwlwifi firmware git and tried unloading/reloading iwlwifi. Driver crashes as well, but with a different error code. Best, - LM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lool 1579 F pulseaudio /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 15:02:08 2020 InstallationDate: Installed on 2019-12-02 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off plymouth.force-scale=3 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago) dmi.bios.date: 11/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Can confirm 5.4.0-18.22 in proposed fixes iwlwifi for me; thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi there, Laptop: Dell XPS 13 7390 2-in-1 Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04. Firmware crashes after loading and interface doesn't show up. This is with: linux-image-5.4.0-9-generic 5.4.0-9.12 linux-firmware 1.184 I've noticed the driver was trying to load a more recent firmware: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 I've downloaded this file from upstream iwlwifi firmware git and tried unloading/reloading iwlwifi. Driver crashes as well, but with a different error code. Best, - LM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lool 1579 F pulseaudio /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 15:02:08 2020 InstallationDate: Installed on 2019-12-02 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off plymouth.force-scale=3 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago) dmi.bios.date: 11/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881631] Re: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII
ubuntu-focal.git, focal/raspi2 branch: debian.raspi2/config/config.common.ubuntu:CONFIG_NLS_ASCII=y ubuntu-bionic.git, bionic/raspi2 branch: debian.raspi2/config/config.common.ubuntu:CONFIG_NLS_ASCII=y So not quite sure where this is coming from -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881631 Title: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Remounting log mounts in Ubuntu core are failing on arm64 builds due to missing CONFIG_NLS_ASCII in the arm64 kernel build options. This option is enabled on the other kernel builds but somehow was overlooked on arm64 appears to affect our ability to access logs via journalctl with data from prior to restart because certain mounts are failing. Other Raspberry Pi kernel builds, such as the armhf build, have the option enabled and so do not encounter the mount error. The kernel option that needs to be turned on to resolve this is CONFIG_NLS_ASCII. It needs to be set to either 'm' or 'y'. Most of the other chips have it set to 'y', keeping it built-in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007001] Re: Blank console display with aarch64 kernel 5.19.0-31
Hi Matthew, Thanks for your test kernel (and thanks for upload the jammy hwe version of it too) I can confirm this kernels gives me video output in VMware Fusion 13.0.1 No error on vmwgfx startup: [0.00] Linux version 5.19.0-38-generic (buildd@bos02-arm64-003) (aarch64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #39~22.04.1+TEST2007001v20230418b1-Ubuntu SMP PREEMPT_DYNAMIC Tu (Ubuntu 5.19.0-38.39~22.04.1+TEST2007001v20230418b1-generic 5.19.17) [...] [1.284460] vmwgfx :00:0f.0: [drm] Register MMIO at 0x0x3d00 size is 4096 kiB [1.285181] vmwgfx :00:0f.0: [drm] VRAM at 0x7000 size is 131072 kiB [1.285193] vmwgfx :00:0f.0: [drm] Running on SVGA version 3. [1.285196] vmwgfx :00:0f.0: [drm] Capabilities: cursor, cursor bypass, alpha cursor, 3D, pitchlock, irq mask, traces, command buffers, command buffers 2, gbobject, dx, hp cmd queue, no bb restriction, cap2 register, [1.285201] vmwgfx :00:0f.0: [drm] Capabilities2: grow otable, intra surface copy, dx2, gb memsize 2, screendma reg, otable ptdepth2, non ms to ms stretchblt, cursor mob, mshint, cb max size 4mb, dx3, frame type, trace full fb, extra regs, lo staging, [1.285204] vmwgfx :00:0f.0: [drm] DMA map mode: Caching DMA mappings. [1.285243] vmwgfx :00:0f.0: [drm] Legacy memory limits: VRAM = 4096 kB, FIFO = 256 kB, surface = 524288 kB [1.285259] vmwgfx :00:0f.0: [drm] MOB limits: max mob size = 1048576 kB, max mob pages = 524288 [1.285261] vmwgfx :00:0f.0: [drm] Maximum display memory size is 262144 kiB [1.289628] vmwgfx :00:0f.0: [drm] No GMR memory available. Graphics memory resources are very limited. [1.289794] vmwgfx :00:0f.0: [drm] Screen Target display unit initialized [1.290031] vmwgfx :00:0f.0: [drm] Using command buffers with DMA pool. [1.290037] vmwgfx :00:0f.0: [drm] Available shader model: SM_5_1X. [1.290439] Console: switching to colour frame buffer device 128x48 [1.291782] [drm] Initialized vmwgfx 2.20.0 20211206 for :00:0f.0 on minor 0 To double check, I reinstalled the latest 5.19 HWE kernel for 22.04 and double-checked I could reproduce the issue in the archive: [0.00] Linux version 5.19.0-40-generic (buildd@bos02-arm64-021) (aarch64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 31 16:02:33 UTC 2 (Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17) [...] [0.739889] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 0x7000-0x77ff 64bit pref] [0.739893] vmwgfx: probe of :00:0f.0 failed with error -16 Thanks a lot for the fix and looking forward to seeing it in jammy- updates :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007001 Title: Blank console display with aarch64 kernel 5.19.0-31 Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: In Progress Bug description: Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion 13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade and after rebooting the VM no text or graphical console appears on the VM. The VM is running and can be accessed through SSH. Rebooting the VM with kernel 5.19.0-29 - everything is working as expected. Text and graphical consoles now display properly. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sat Feb 11 13:04:22 2023 InstallationDate: Installed on 2022-09-11 (153 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911) IwConfig: lono wireless extensions. ens160no wireless extensions. MachineType: VMware, Inc. VMware20,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW201.00V.20904234.BA64.2212051119
[Kernel-packages] [Bug 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display
Is it worth having a separate task for linux-hwe in 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/2007001 Title: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-hwe-5.19 source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2007001 [Impact] Numerous VMWare users have reported that vmwgfx cannot reserve the memory region for the graphics framebuffer, leading their VMs to have blank screens. They see the following in dmesg: [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 0x7000-0x77ff 64bit pref] [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16 And a cat /proc/iomem shows this: 5000-7fff : PCI Bus :00 7000-77ff : :00:0f.0 7000-702f : BOOTFB The kernel has failed to release this memory region for vmwgfx to occupy. Most affected users are on aarch64, with the host being Apple silicon systems. [Fix] The regression was introduced by the below commit in 5.19.0-30-generic: commit 5e01376124309b4dbd30d413f43c0d9c2f60edea Author: Thomas Zimmermann Date: Mon Jul 18 09:23:18 2022 +0200 Subject: video/aperture: Disable and unregister sysfb devices via aperture helpers Link: https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea This commit was part of a larger refactoring of the video subsystem, and requires the entire series to function correctly. You can review the whole series below: https://patchwork.freedesktop.org/series/106040/ The patch series also requires quite a few additional fixups to fix bugs introduced by the series, making the size about 15 commits in total. The contents of the series don't really fix any bugs, and their purpose is to refactor the code for future changes to the fbdev subsystem, and really aren't appropriate to be backported to a stable kernel series. "video/aperture: Disable and unregister sysfb devices via aperture helpers" seems to have been selected for -stable by mistake by its fixes: tag, and was pulled into upstream stable by a robot with little human review. The best course of action is to revert. No action needed for Lunar, as the entire series is present in that release. [Testcase] This bug affects users running Ubuntu in VMWare VMs, notably on aarch64 devices, like modern Apple computers. Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on Apple silicon, and see if the display comes up or not. Affected users will see a blank screen. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test If you install the test kernel and reboot, you will be able to see the screen on your VM like normal. [Where problems could occur] This commit changes when the sysfb is disabled and memory region for the graphics framebuffer is released to the proper device driver. If a regression were to occur, then graphics drivers may fail to reserve the framebuffer memory, and fail to start, leaving users with a blank screen. There are no workarounds, other than booting a previous kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display
I've tested 5.19.0-42.43~22.04.1 from jammy-proposed which had a few vmwgfx changes listed in its changelog, but it didn't work; I didn't see the same revert as in 5.19.0-44.45 or a reference to that bug, so I'll open a jammy task to land this fix there too. ** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-hwe-5.19 (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: linux-hwe-5.19 (Ubuntu Kinetic) ** No longer affects: linux (Ubuntu 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/2007001 Title: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2007001 [Impact] Numerous VMWare users have reported that vmwgfx cannot reserve the memory region for the graphics framebuffer, leading their VMs to have blank screens. They see the following in dmesg: [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 0x7000-0x77ff 64bit pref] [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16 And a cat /proc/iomem shows this: 5000-7fff : PCI Bus :00 7000-77ff : :00:0f.0 7000-702f : BOOTFB The kernel has failed to release this memory region for vmwgfx to occupy. Most affected users are on aarch64, with the host being Apple silicon systems. [Fix] The regression was introduced by the below commit in 5.19.0-30-generic: commit 5e01376124309b4dbd30d413f43c0d9c2f60edea Author: Thomas Zimmermann Date: Mon Jul 18 09:23:18 2022 +0200 Subject: video/aperture: Disable and unregister sysfb devices via aperture helpers Link: https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea This commit was part of a larger refactoring of the video subsystem, and requires the entire series to function correctly. You can review the whole series below: https://patchwork.freedesktop.org/series/106040/ The patch series also requires quite a few additional fixups to fix bugs introduced by the series, making the size about 15 commits in total. The contents of the series don't really fix any bugs, and their purpose is to refactor the code for future changes to the fbdev subsystem, and really aren't appropriate to be backported to a stable kernel series. "video/aperture: Disable and unregister sysfb devices via aperture helpers" seems to have been selected for -stable by mistake by its fixes: tag, and was pulled into upstream stable by a robot with little human review. The best course of action is to revert. No action needed for Lunar, as the entire series is present in that release. [Testcase] This bug affects users running Ubuntu in VMWare VMs, notably on aarch64 devices, like modern Apple computers. Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on Apple silicon, and see if the display comes up or not. Affected users will see a blank screen. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test If you install the test kernel and reboot, you will be able to see the screen on your VM like normal. [Where problems could occur] This commit changes when the sysfb is disabled and memory region for the graphics framebuffer is released to the proper device driver. If a regression were to occur, then graphics drivers may fail to reserve the framebuffer memory, and fail to start, leaving users with a blank screen. There are no workarounds, other than booting a previous kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
