[Kernel-packages] [Bug 2058750] Re: i915 GPU HANG: ecode 12:1:db96edba
Looks the log from #comment3 is similar as this link. https://www.reddit.com/r/archlinux/comments/14zifl8/gpu_hang_issue_on_laptop_had_to_hard_shutdown/ Could you try with latest firmware from upstream? The latest version is 70.20.0 per the log. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/log/i915/adlp_guc_70.bin -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058750 Title: i915 GPU HANG: ecode 12:1:db96edba Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: This has happened several times over a period of months when visiting the site https://www.windy.com and viewing satellite images. The computer completely freezes and must be hard restarted. I don't think I have triggered this freeze by visiting any other site. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 14:14:41 2024 InstallationDate: Installed on 2023-04-12 (344 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 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-6.5/+bug/2058750/+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 2058483] Re: touchpad not working
Please run `apport-collect 2058483`, thanks! ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058483 Title: touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: The touchpad is not in the xinput list and it doesn't work. I'm using hp pavilion 15 ec1021nl ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 14:21:02 2024 InstallationDate: Installed on 2024-03-20 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058483/+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 2059973] Re: my touch pad doesn't wok at all.
Please run `apport-collect 2059973`, thanks! ** Package changed: linux-signed-hwe-6.5 (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059973 Title: my touch pad doesn't wok at all. Status in linux package in Ubuntu: Incomplete Bug description: i'm new at linux. firstly i have installed ubuntu as dual boot besides windows 11 pro. that time the touchpad worked as expected. but when i gain confident enough that i can use linux, i installed ubuntu as primary setup, after that the touch pad is not working. it detects the touch pad as follows cat /proc/bus/input/devices I: Bus=0018 Vendor=06cb Product=ce78 Version=0100 N: Name="SYNA2BA6:00 06CB:CE78 Mouse" P: Phys=i2c-SYNA2BA6:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA2BA6:00/0018:06CB:CE78.0001/input/input22 U: Uniq= H: Handlers=mouse0 event19 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 I: Bus=0018 Vendor=06cb Product=ce78 Version=0100 N: Name="SYNA2BA6:00 06CB:CE78 Touchpad" P: Phys=i2c-SYNA2BA6:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA2BA6:00/0018:06CB:CE78.0001/input/input23 U: Uniq= H: Handlers=mouse1 event20 B: PROP=5 B: EV=1b B: KEY=e520 1 0 0 0 0 B: ABS=2e08003 B: MSC=20 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 02:29:41 2024 InstallationDate: Installed on 2024-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059973/+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 2060770] Re: NVMe drive fails at high write workload after kernel upgrades
Is it possible to attach said logs? ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060770 Title: NVMe drive fails at high write workload after kernel upgrades Status in linux package in Ubuntu: Incomplete Bug description: My problem is similarly described in this old thread: https://unix.stackexchange.com/questions/742360/ journalctl message: one of the many related logs Apr 09 15:37:40.096850 ** kernel: Linux version 6.5.0-26-lowlatency (buildd@lcy02-amd64-109) (x86_64-linux-gnu-gcc-12 (Ubunntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #26.1~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Mar 13 10:41:42 UTC (Ubuntu 6.5.0-26.26.1~22.04.1-lowlatency 6.5.13) Apr 09 15:43:46.238697 ** kernel: nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 Apr 09 15:43:46.239162 ** kernel: nvme nvme0: Does your device have a faulty power saving mode enabled? Apr 09 15:43:46.239266 ** kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug Apr 09 15:43:46.690200 ** kernel: nvme :06:00.0: enabling device ( -> 0002) Apr 09 15:43:46.690409 ** kernel: nvme nvme0: Disabling device after reset failure: -19 Apr 09 15:43:46.698188 ** kernel: I/O error, dev nvme0n1, sector 1216896 op 0x1:(WRITE) flags 0xc800 phys_seg 1 prio clas> I was using 22.04.4 with hwe kernel, as shown above (kernel 6.5) upgrade to 24.04 dev hoping the problem would be resolved, but no it still exists (kernel 6.8) The problem happens after some kernel upgrades that I'd done after 2024-03-01, but I cannot pinpoint when; the nvme_core kernel param as shown in the message above does not help. The problem does NOT exist with 22.04 regular kernel: Currently I'd created a VM to perform my heavy write workload using pci passthrough of the NVMe drive, and it works okay. Cannot downgrade host to older kernel because of ZFS pool being upgraded VM info (where my NVMe drive works okay) uname -r 5.15.0-78-lowlatency lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy (maybe) related hardware spec CPU: AMD Ryzen 5750G (x8x4x4) Chipset: AMD B450 NVMe: Samsung MZ1LB960HBJR-000FB (PM983a, f/w EDW73F2Q) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060770/+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 2061040] Re: I2C HID device sometimes fails to initialize causing touchpad to not work
** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Anthony Wong (anthonywong) -- 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/2061040 Title: I2C HID device sometimes fails to initialize causing touchpad to not work Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Hi, Touchpad on my new Lenovo X1 Carbon (Gen12) with the Sensel haptic pad doesn't work on boot. I see this: | [Thu Apr 11 13:57:26 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack reset within 1000 ms | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | ... | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unbalanced collection at end of report description | [Thu Apr 11 13:57:26 2024] hid-generic: probe of 0018:2C2F:0028.0001 failed with error -22 Per the Arch Linux wiki page[1], removing and reloading the `i2c_hid_acpi` seems to fix it: | [Thu Apr 11 13:58:02 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack reset within 1000 ms | [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input15 | [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input16 | [Thu Apr 11 13:58:02 2024] hid-multitouch 0018:2C2F:0028.0002: input,hidraw0: I2C HID v1.00 Mouse [SNSL0028:00 2C2F:0028] on i2c-SNSL0028:00 | [Thu Apr 11 13:58:03 2024] psmouse serio1: trackpoint: Synaptics TrackPoint firmware: 0x08, buttons: 3/3 | [Thu Apr 11 13:58:03 2024] input: TPPS/2 Synaptics TrackPoint as /devices/platform/i8042/serio1/input/input18 From that Arch Linux wiki page, it seems to be a bug upstream[2] with the commit fixing this: | https://github.com/torvalds/linux/commit/af93a167eda90192563bce64c4bb989836afac1f Or | https://lore.kernel.org/linux- input/20240331182440.14477-1...@kl.wtf/T/#u Can we get fix this backported? | [hloeung@dharkan tmp]$ apt-cache policy linux-image-generic-hwe-24.04 | linux-image-generic-hwe-24.04: | Installed: 6.8.0-22.22 | Candidate: 6.8.0-22.22 | Version table: | *** 6.8.0-22.22 500 | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 Packages | 100 /var/lib/dpkg/status | [hloeung@dharkan tmp]$ uname -a | Linux dharkan.local 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux | [hloeung@dharkan tmp]$ Thanks, Haw [1]: https://wiki.archlinux.org/title/Lenovo_ThinkPad_Z16_Gen_2 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=2271136 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061040/+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 2061295] Re: No graphical boot with default Kubuntu 24.04
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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/2061295 Title: No graphical boot with default Kubuntu 24.04 Status in linux package in Ubuntu: New Bug description: I upgraded from 23.10 to 24.04, and with it the new 6.8 kernel. I do not see the Kubuntu EFI logo, and the system never reaches the sddm login screen. I could not switch to a tty to login either. If I boot kernel 6.5 it works as expected. If I remove "quiet splash" from the boot parameters, then kernel 6.8 also boots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 14 16:08:22 2024 InstallationDate: Installed on 2023-01-16 (454 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-13 (1 days ago) dmi.bios.date: 03/01/2024 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.08 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.08:bd03/01/2024:br5.32:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061295/+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 2061087] Re: Conflict with linux-laptop-tools-common
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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/2061087 Title: Conflict with linux-laptop-tools-common Status in linux package in Ubuntu: New Bug description: Doing an apt upgrade on Noble today, linux-tools-common is attempting to overwrite /usr/bin/cpupower, which is also provided by linux- laptop-tools-common: ---> Vorbereitung zum Entpacken von .../310-linux-tools-common_6.8.0-22.22_all.deb ... Entpacken von linux-tools-common (6.8.0-22.22) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-GERI65/310-linux-tools-common_6.8.0-22.22_all.deb (--unpack): Versuch, »/usr/bin/cpupower« zu überschreiben, welches auch in Paket linux-laptop-tools-common 6.5.0-1004.7 ist dpkg-deb: Fehler: »einfügen«-Unterprozess wurde durch Signal (Broken pipe) getötet <--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061087/+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 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 09:42:52 2024 InstallationDate: Installed on 2022-06-28 (653 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.5 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-6.5/+bug/2061091/+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 2060981] Re: ACPI BIOS errors
ACPI AE_NOT_FOUND errors usually come from buggy firmware which uses the objects but not actually implemented. Can spot which parts of firmware errors if you can support acpidump log. $sudo acpidump > acpidump.log ** Changed in: linux (Ubuntu) Status: In Progress => Triaged -- 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/2060981 Title: ACPI BIOS errors Status in linux package in Ubuntu: Triaged Bug description: dmesg show the below ACPI errors, is this normal? # dmesg | grep -i acpi [0.00] BIOS-e820: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] BIOS-e820: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] reserve setup_data: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] reserve setup_data: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] efi: ACPI=0x59dc3000 ACPI 2.0=0x59dc3014 TPMFinalLog=0x59e4a000 SMBIOS=0x5a609000 SMBIOS 3.0=0x5a608000 MEMATTR=0x528f6018 ESRT=0x53983818 MOKvar=0x5a5e4000 INITRD=0x4fde3f98 RNG=0x59d28018 TPMEventLog=0x4fdc7018 [0.020042] ACPI: Early table checksum verification disabled [0.020046] ACPI: RSDP 0x59DC3014 24 (v02 _ASUS_) [0.020052] ACPI: XSDT 0x59DC2728 00011C (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020060] ACPI: FACP 0x59DBD000 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [0.020066] ACPI: DSDT 0x59D6 05C524 (v02 _ASUS_ Notebook 01072009 INTL 20191018) [0.020070] ACPI: FACS 0x59EBC000 40 [0.020074] ACPI: MCFG 0x59DC1000 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [0.020077] ACPI: SSDT 0x59DBE000 00255D (v02 CpuRef CpuSsdt 3000 INTL 20191018) [0.020081] ACPI: FIDT 0x59D5F000 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020084] ACPI: ECDT 0x59D5E000 C1 (v01 _ASUS_ Notebook 01072009 AMI. 0005) [0.020088] ACPI: MSDM 0x59D5D000 55 (v03 _ASUS_ Notebook 01072009 ASUS 0001) [0.020092] ACPI: SSDT 0x59D58000 004F42 (v02 DptfTa DptfTabl 1000 INTL 20191018) [0.020095] ACPI: SSDT 0x59D56000 0017B5 (v02 SaSsdt SaSsdt 3000 INTL 20191018) [0.020099] ACPI: SSDT 0x59D52000 003350 (v02 INTEL IgfxSsdt 3000 INTL 20191018) [0.020103] ACPI: SSDT 0x59D46000 00B1B2 (v02 INTEL TcssSsdt 1000 INTL 20191018) [0.020106] ACPI: HPET 0x59D45000 38 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020110] ACPI: APIC 0x59D44000 00012C (v04 _ASUS_ Notebook 01072009 AMI 0113) [0.020114] ACPI: SSDT 0x59D43000 0002A7 (v02 _ASUS_ TcssSsdt INTL 20191018) [0.020118] ACPI: SSDT 0x59D3B000 007504 (v02 _ASUS_ TglU_Rvp 1000 INTL 20191018) [0.020122] ACPI: NHLT 0x59D39000 001B54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020126] ACPI: LPIT 0x59D38000 CC (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020129] ACPI: SSDT 0x59D36000 00012A (v02 _ASUS_ TbtTypeC INTL 20191018) [0.020133] ACPI: DBGP 0x59D35000 34 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020137] ACPI: DBG2 0x59D34000 54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020141] ACPI: SSDT 0x59D33000 000D8A (v02 _ASUS_ UsbCTabl 1000 INTL 20191018) [0.020145] ACPI: DMAR 0x59D32000 B8 (v02 INTEL EDK2 0002 0113) [0.020148] ACPI: SSDT 0x59D31000 0004B8 (v02 HgRef HgRpSsdt 1000 INTL 20191018) [0.020152] ACPI: SSDT 0x59D3 000144 (v02 Intel ADebTabl 1000 INTL 20191018) [0.020155] ACPI: BGRT 0x59D2F000 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020159] ACPI: UEFI 0x59E28000 00063A (v01 INTEL RstVmdE ?? ) [0.020163] ACPI: UEFI 0x59E27000 5C (v01 INTEL RstVmdV ?? ) [0.020166] ACPI: TPM2 0x59D2E000 4C (v04 _ASUS_ Notebook 0001 AMI ) [0.020170] ACPI: SSDT 0x59D2B000 002495 (v01 OptRf1 Opt1Tabl 1000 INTL 20191018) [0.020173] ACPI: PTDT 0x59D2A000 000D44 (v00 _ASUS_ Notebook 0005 MSFT 010D) [0.020177] ACPI: WSMT 0x59D37000 28 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020181] ACPI: FPDT 0x59D29000 44 (v01 _ASUS_ A M I 01072009 AMI 0113) [0.020184] ACPI: Reserving FACP table memory at [mem 0x59dbd000-0x59dbd113] [0.020186] ACPI: Reserving DSDT table memory at [mem 0x59d6-0x59dbc523] [0.020187] ACPI: Reserving FACS table memory at [mem 0x59ebc000-0x59ebc03f] [0.020187] ACPI: Reserving MCFG table memory at [mem
[Kernel-packages] [Bug 2060981] Re: ACPI BIOS errors
** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060981 Title: ACPI BIOS errors Status in linux package in Ubuntu: In Progress Bug description: dmesg show the below ACPI errors, is this normal? # dmesg | grep -i acpi [0.00] BIOS-e820: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] BIOS-e820: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] reserve setup_data: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] reserve setup_data: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] efi: ACPI=0x59dc3000 ACPI 2.0=0x59dc3014 TPMFinalLog=0x59e4a000 SMBIOS=0x5a609000 SMBIOS 3.0=0x5a608000 MEMATTR=0x528f6018 ESRT=0x53983818 MOKvar=0x5a5e4000 INITRD=0x4fde3f98 RNG=0x59d28018 TPMEventLog=0x4fdc7018 [0.020042] ACPI: Early table checksum verification disabled [0.020046] ACPI: RSDP 0x59DC3014 24 (v02 _ASUS_) [0.020052] ACPI: XSDT 0x59DC2728 00011C (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020060] ACPI: FACP 0x59DBD000 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [0.020066] ACPI: DSDT 0x59D6 05C524 (v02 _ASUS_ Notebook 01072009 INTL 20191018) [0.020070] ACPI: FACS 0x59EBC000 40 [0.020074] ACPI: MCFG 0x59DC1000 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [0.020077] ACPI: SSDT 0x59DBE000 00255D (v02 CpuRef CpuSsdt 3000 INTL 20191018) [0.020081] ACPI: FIDT 0x59D5F000 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020084] ACPI: ECDT 0x59D5E000 C1 (v01 _ASUS_ Notebook 01072009 AMI. 0005) [0.020088] ACPI: MSDM 0x59D5D000 55 (v03 _ASUS_ Notebook 01072009 ASUS 0001) [0.020092] ACPI: SSDT 0x59D58000 004F42 (v02 DptfTa DptfTabl 1000 INTL 20191018) [0.020095] ACPI: SSDT 0x59D56000 0017B5 (v02 SaSsdt SaSsdt 3000 INTL 20191018) [0.020099] ACPI: SSDT 0x59D52000 003350 (v02 INTEL IgfxSsdt 3000 INTL 20191018) [0.020103] ACPI: SSDT 0x59D46000 00B1B2 (v02 INTEL TcssSsdt 1000 INTL 20191018) [0.020106] ACPI: HPET 0x59D45000 38 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020110] ACPI: APIC 0x59D44000 00012C (v04 _ASUS_ Notebook 01072009 AMI 0113) [0.020114] ACPI: SSDT 0x59D43000 0002A7 (v02 _ASUS_ TcssSsdt INTL 20191018) [0.020118] ACPI: SSDT 0x59D3B000 007504 (v02 _ASUS_ TglU_Rvp 1000 INTL 20191018) [0.020122] ACPI: NHLT 0x59D39000 001B54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020126] ACPI: LPIT 0x59D38000 CC (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020129] ACPI: SSDT 0x59D36000 00012A (v02 _ASUS_ TbtTypeC INTL 20191018) [0.020133] ACPI: DBGP 0x59D35000 34 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020137] ACPI: DBG2 0x59D34000 54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020141] ACPI: SSDT 0x59D33000 000D8A (v02 _ASUS_ UsbCTabl 1000 INTL 20191018) [0.020145] ACPI: DMAR 0x59D32000 B8 (v02 INTEL EDK2 0002 0113) [0.020148] ACPI: SSDT 0x59D31000 0004B8 (v02 HgRef HgRpSsdt 1000 INTL 20191018) [0.020152] ACPI: SSDT 0x59D3 000144 (v02 Intel ADebTabl 1000 INTL 20191018) [0.020155] ACPI: BGRT 0x59D2F000 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020159] ACPI: UEFI 0x59E28000 00063A (v01 INTEL RstVmdE ?? ) [0.020163] ACPI: UEFI 0x59E27000 5C (v01 INTEL RstVmdV ?? ) [0.020166] ACPI: TPM2 0x59D2E000 4C (v04 _ASUS_ Notebook 0001 AMI ) [0.020170] ACPI: SSDT 0x59D2B000 002495 (v01 OptRf1 Opt1Tabl 1000 INTL 20191018) [0.020173] ACPI: PTDT 0x59D2A000 000D44 (v00 _ASUS_ Notebook 0005 MSFT 010D) [0.020177] ACPI: WSMT 0x59D37000 28 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020181] ACPI: FPDT 0x59D29000 44 (v01 _ASUS_ A M I 01072009 AMI 0113) [0.020184] ACPI: Reserving FACP table memory at [mem 0x59dbd000-0x59dbd113] [0.020186] ACPI: Reserving DSDT table memory at [mem 0x59d6-0x59dbc523] [0.020187] ACPI: Reserving FACS table memory at [mem 0x59ebc000-0x59ebc03f] [0.020187] ACPI: Reserving MCFG table memory at [mem 0x59dc1000-0x59dc103b] [0.020188] ACPI: Reserving SSDT table memory at [mem 0x59dbe000-0x59dc055c] [0.020189] ACPI: Reserving FIDT table
[Kernel-packages] [Bug 2036135] Re: thermald assert failure: *** stack smashing detected ***: terminated
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2036135 Title: thermald assert failure: *** stack smashing detected ***: terminated Status in thermald package in Ubuntu: Confirmed Bug description: suddenly occured ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: thermald 2.5.4-2 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AssertionMessage: *** stack smashing detected ***: terminated CasperMD5CheckResult: pass Date: Thu Sep 14 12:41:34 2023 ExecutablePath: /usr/sbin/thermald InstallationDate: Installed on 2023-09-14 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2) ProcCmdline: /usr/sbin/thermald --systemd --dbus-enable --adaptive ProcEnviron: LANG=ja_JP.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: thermald StacktraceTop: __libc_message (fmt=fmt@entry=0x7fad897c38d3 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150 __GI___fortify_fail (msg=msg@entry=0x7fad897c38eb "stack smashing detected") at ./debug/fortify_fail.c:24 __stack_chk_fail () at ./debug/stack_chk_fail.c:24 cthd_acpi_rel::read_psvt() () ?? () Title: thermald assert failure: *** stack smashing detected ***: terminated UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A modified.conffile..etc.init.thermald.conf: [deleted] mtime.conffile..etc.thermald.thermal-cpu-cdev-order.xml: 2023-08-25T19:29:11 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2036135/+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 2060852] Re: nvidia-driver-550-open fails with secure boot enabled
linux-restricted-modules providing 550 is now available, so closing this blocking bug. ** Changed in: nvidia-graphics-drivers-550-server (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-550 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-550 in Ubuntu. https://bugs.launchpad.net/bugs/2060852 Title: nvidia-driver-550-open fails with secure boot enabled Status in nvidia-graphics-drivers-550 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-550-server package in Ubuntu: Fix Released Bug description: I switched to the 550-open driver to test this out but the module fails to load with secureboot enabled. The key is rejected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nvidia-kernel-source-550-open 550.67-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 13:45:43 2024 Dependencies: InstallationDate: Installed on 2023-04-10 (366 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nvidia-graphics-drivers-550 UpgradeStatus: Upgraded to noble on 2024-04-10 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2023-12-15T17:01:26.953508 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2060852/+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 1852916] Re: GPU problem, screen flikers a lot on start and log off. Unable to see anything black out.
@punisher01 : I think this bug has been reported for the wrong component, ** Changed in: intel-gpu-tools (Ubuntu) Status: New => Invalid ** Changed in: intel-gpu-tools (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1852916 Title: GPU problem, screen flikers a lot on start and log off. Unable to see anything black out. Status in intel-gpu-tools package in Ubuntu: Invalid Bug description: I am using Dell Vostro 15 3568 runing on Ubuntu 19.04 with Graphics : Intel® HD Graphics 620 (Kaby Lake GT2) and Amd Radeon on it. But lately have some problem with something either the GPU, GRUB or kernel. The I uninstalled the driver for Amd Radeon after reading articles over internet but it did not help. Also tried to add "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" in GRUB but did not work. I do not know what is the problem I have tried almost everything available but it does not fix. Please help me in fixing the problem. It so irritating, while restarting of siging in it takes ages. This problem was encountred after some package update while I was using Ubuntu 18.04 LTE, so later I upgraded to Ubuntu 19.04 in hope of solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1852916/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
Here is the debdiff for the proposed fix ** Attachment added: "intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765384/+files/intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Bug description: When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Changed in: intel-gpu-tools (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Bug description: When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 2060193] Re: iwlwifi microcode crash when using wrong password to join a WPA3 access point
It's not only when using wrong password. Even if a password is good and the network is connected hardware restart is requested. When this error appears packets are dropped and the network speed slows down. As a workaround you can add options iwlwifi 11n_disable=1 to /etc/modprobe.d/iwlwifi.conf file. This slows network to 54MBit/s but it is stable, with no packet drops and hardware reset. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2060193 Title: iwlwifi microcode crash when using wrong password to join a WPA3 access point Status in linux-firmware package in Ubuntu: Confirmed Bug description: I noticed that whenever I try to join a wireless network using WPA3 SAE and type the password wrong, I get a microcode crash from iwlwifi. The chip is Intel 9462 (AX201). Ubuntu release 22.04 LTS, faithfully kept up to date. System info available via: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2058226 Crash log seems to be always similar: Apr 3 22:13:55 waplinuc kernel: [1158486.254336] iwlwifi :00:14.3: Not associated and the session protection is over already... Apr 3 22:13:57 waplinuc kernel: [1158487.456868] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Apr 3 22:13:57 waplinuc kernel: [1158487.456960] iwlwifi :00:14.3: Start IWL Error Log Dump: Apr 3 22:13:57 waplinuc kernel: [1158487.456962] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Apr 3 22:13:57 waplinuc kernel: [1158487.456965] iwlwifi :00:14.3: Loaded firmware version: 77.206b0184.0 QuZ-a0-jf-b0-77.ucode Apr 3 22:13:57 waplinuc kernel: [1158487.456967] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Apr 3 22:13:57 waplinuc kernel: [1158487.456969] iwlwifi :00:14.3: 0x008022F3 | trm_hw_status0 Apr 3 22:13:57 waplinuc kernel: [1158487.456971] iwlwifi :00:14.3: 0x | trm_hw_status1 Apr 3 22:13:57 waplinuc kernel: [1158487.456973] iwlwifi :00:14.3: 0x004C03F2 | branchlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456974] iwlwifi :00:14.3: 0x64CC | interruptlink1 Apr 3 22:13:57 waplinuc kernel: [1158487.456976] iwlwifi :00:14.3: 0x64CC | interruptlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456977] iwlwifi :00:14.3: 0x0001191E | data1 Apr 3 22:13:57 waplinuc kernel: [1158487.456979] iwlwifi :00:14.3: 0x1000 | data2 Apr 3 22:13:57 waplinuc kernel: [1158487.456980] iwlwifi :00:14.3: 0x | data3 Apr 3 22:13:57 waplinuc kernel: [1158487.456982] iwlwifi :00:14.3: 0x04C0678B | beacon time Apr 3 22:13:57 waplinuc kernel: [1158487.456983] iwlwifi :00:14.3: 0x920B688C | tsf low Apr 3 22:13:57 waplinuc kernel: [1158487.456985] iwlwifi :00:14.3: 0x0221 | tsf hi Apr 3 22:13:57 waplinuc kernel: [1158487.456986] iwlwifi :00:14.3: 0x0DFD | time gp1 Apr 3 22:13:57 waplinuc kernel: [1158487.456988] iwlwifi :00:14.3: 0x00A909B7 | time gp2 Apr 3 22:13:57 waplinuc kernel: [1158487.456989] iwlwifi :00:14.3: 0x0001 | uCode revision type Apr 3 22:13:57 waplinuc kernel: [1158487.456991] iwlwifi :00:14.3: 0x004D | uCode version major Apr 3 22:13:57 waplinuc kernel: [1158487.456992] iwlwifi :00:14.3: 0x206B0184 | uCode version minor Apr 3 22:13:57 waplinuc kernel: [1158487.456994] iwlwifi :00:14.3: 0x0351 | hw version Apr 3 22:13:57 waplinuc kernel: [1158487.456995] iwlwifi :00:14.3: 0x00489001 | board version Apr 3 22:13:57 waplinuc kernel: [1158487.456997] iwlwifi :00:14.3: 0x001C | hcmd Apr 3 22:13:57 waplinuc kernel: [1158487.456998] iwlwifi :00:14.3: 0x00023000 | isr0 Apr 3 22:13:57 waplinuc kernel: [1158487.456999] iwlwifi :00:14.3: 0x0004C000 | isr1 Apr 3 22:13:57 waplinuc kernel: [1158487.457001] iwlwifi :00:14.3: 0x08F80002 | isr2 Apr 3 22:13:57 waplinuc kernel: [1158487.457002] iwlwifi :00:14.3: 0x00C3000C | isr3 Apr 3 22:13:57 waplinuc kernel: [1158487.457004] iwlwifi :00:14.3: 0x | isr4 Apr 3 22:13:57 waplinuc kernel: [1158487.457005] iwlwifi :00:14.3: 0x0101001C | last cmd Id Apr 3 22:13:57 waplinuc kernel: [1158487.457006] iwlwifi :00:14.3: 0x0001191E | wait_event Apr 3 22:13:57 waplinuc kernel: [1158487.457008] iwlwifi :00:14.3: 0x54B6 | l2p_control Apr 3 22:13:57 waplinuc kernel: [1158487.457009] iwlwifi :00:14.3: 0x1C02 | l2p_duration Apr 3 22:13:57 waplinuc kernel: [1158487.457011] iwlwifi :00:14.3: 0x0003 | l2p_mhvalid Apr 3 22:13:57 waplinuc kernel: [1158487.457012] iwlwifi :00:14.3: 0x | l2p_addr_match Apr 3 22:13:57 waplinuc kernel: [1158487.457013] iwlwifi :00:14.3: 0x000B | lmpm_pmg_sel Apr 3 22:13:57 waplinuc kernel: [1158487.457015] iwlwifi :00:14.3: 0x |
[Kernel-packages] [Bug 2061324] Re: Error when re-building package from source
here is the debdiff of the fix
** Attachment added: "intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz"
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+attachment/5765373/+files/intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
In Progress
Bug description:
When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+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 2060193] Re: iwlwifi microcode crash when using wrong password to join a WPA3 access point
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2060193 Title: iwlwifi microcode crash when using wrong password to join a WPA3 access point Status in linux-firmware package in Ubuntu: Confirmed Bug description: I noticed that whenever I try to join a wireless network using WPA3 SAE and type the password wrong, I get a microcode crash from iwlwifi. The chip is Intel 9462 (AX201). Ubuntu release 22.04 LTS, faithfully kept up to date. System info available via: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2058226 Crash log seems to be always similar: Apr 3 22:13:55 waplinuc kernel: [1158486.254336] iwlwifi :00:14.3: Not associated and the session protection is over already... Apr 3 22:13:57 waplinuc kernel: [1158487.456868] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Apr 3 22:13:57 waplinuc kernel: [1158487.456960] iwlwifi :00:14.3: Start IWL Error Log Dump: Apr 3 22:13:57 waplinuc kernel: [1158487.456962] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Apr 3 22:13:57 waplinuc kernel: [1158487.456965] iwlwifi :00:14.3: Loaded firmware version: 77.206b0184.0 QuZ-a0-jf-b0-77.ucode Apr 3 22:13:57 waplinuc kernel: [1158487.456967] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Apr 3 22:13:57 waplinuc kernel: [1158487.456969] iwlwifi :00:14.3: 0x008022F3 | trm_hw_status0 Apr 3 22:13:57 waplinuc kernel: [1158487.456971] iwlwifi :00:14.3: 0x | trm_hw_status1 Apr 3 22:13:57 waplinuc kernel: [1158487.456973] iwlwifi :00:14.3: 0x004C03F2 | branchlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456974] iwlwifi :00:14.3: 0x64CC | interruptlink1 Apr 3 22:13:57 waplinuc kernel: [1158487.456976] iwlwifi :00:14.3: 0x64CC | interruptlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456977] iwlwifi :00:14.3: 0x0001191E | data1 Apr 3 22:13:57 waplinuc kernel: [1158487.456979] iwlwifi :00:14.3: 0x1000 | data2 Apr 3 22:13:57 waplinuc kernel: [1158487.456980] iwlwifi :00:14.3: 0x | data3 Apr 3 22:13:57 waplinuc kernel: [1158487.456982] iwlwifi :00:14.3: 0x04C0678B | beacon time Apr 3 22:13:57 waplinuc kernel: [1158487.456983] iwlwifi :00:14.3: 0x920B688C | tsf low Apr 3 22:13:57 waplinuc kernel: [1158487.456985] iwlwifi :00:14.3: 0x0221 | tsf hi Apr 3 22:13:57 waplinuc kernel: [1158487.456986] iwlwifi :00:14.3: 0x0DFD | time gp1 Apr 3 22:13:57 waplinuc kernel: [1158487.456988] iwlwifi :00:14.3: 0x00A909B7 | time gp2 Apr 3 22:13:57 waplinuc kernel: [1158487.456989] iwlwifi :00:14.3: 0x0001 | uCode revision type Apr 3 22:13:57 waplinuc kernel: [1158487.456991] iwlwifi :00:14.3: 0x004D | uCode version major Apr 3 22:13:57 waplinuc kernel: [1158487.456992] iwlwifi :00:14.3: 0x206B0184 | uCode version minor Apr 3 22:13:57 waplinuc kernel: [1158487.456994] iwlwifi :00:14.3: 0x0351 | hw version Apr 3 22:13:57 waplinuc kernel: [1158487.456995] iwlwifi :00:14.3: 0x00489001 | board version Apr 3 22:13:57 waplinuc kernel: [1158487.456997] iwlwifi :00:14.3: 0x001C | hcmd Apr 3 22:13:57 waplinuc kernel: [1158487.456998] iwlwifi :00:14.3: 0x00023000 | isr0 Apr 3 22:13:57 waplinuc kernel: [1158487.456999] iwlwifi :00:14.3: 0x0004C000 | isr1 Apr 3 22:13:57 waplinuc kernel: [1158487.457001] iwlwifi :00:14.3: 0x08F80002 | isr2 Apr 3 22:13:57 waplinuc kernel: [1158487.457002] iwlwifi :00:14.3: 0x00C3000C | isr3 Apr 3 22:13:57 waplinuc kernel: [1158487.457004] iwlwifi :00:14.3: 0x | isr4 Apr 3 22:13:57 waplinuc kernel: [1158487.457005] iwlwifi :00:14.3: 0x0101001C | last cmd Id Apr 3 22:13:57 waplinuc kernel: [1158487.457006] iwlwifi :00:14.3: 0x0001191E | wait_event Apr 3 22:13:57 waplinuc kernel: [1158487.457008] iwlwifi :00:14.3: 0x54B6 | l2p_control Apr 3 22:13:57 waplinuc kernel: [1158487.457009] iwlwifi :00:14.3: 0x1C02 | l2p_duration Apr 3 22:13:57 waplinuc kernel: [1158487.457011] iwlwifi :00:14.3: 0x0003 | l2p_mhvalid Apr 3 22:13:57 waplinuc kernel: [1158487.457012] iwlwifi :00:14.3: 0x | l2p_addr_match Apr 3 22:13:57 waplinuc kernel: [1158487.457013] iwlwifi :00:14.3: 0x000B | lmpm_pmg_sel Apr 3 22:13:57 waplinuc kernel: [1158487.457015] iwlwifi :00:14.3: 0x | timestamp Apr 3 22:13:57 waplinuc kernel: [1158487.457016] iwlwifi :00:14.3: 0x88D4 | flow_handler Apr 3 22:13:57 waplinuc kernel: [1158487.457058] iwlwifi :00:14.3: Start IWL Error Log Dump: Apr 3 22:13:57 waplinuc kernel:
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
I was able to reproduce this problen on 22.04 ** Changed in: intel-gpu-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Confirmed Bug description: When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 2061324] Re: Error when re-building package from source
The package with proposed fixed for Jammy can be found at:
https://launchpad.net/~hectorcao/+archive/ubuntu/lp2061324
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
In Progress
Bug description:
When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+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 2061324] Re: Error when re-building package from source
This problem has been fixed upstream:
963917a3565466832a3b2fc22e9285d34a0bf944
lib/meson.build: Fix underscorify call
f.underscorify() is correct, f.underscorify(f) is an error that later
meson versions don't like at all.
Closes: #107
Fixes: 588555f7
See : https://gitlab.freedesktop.org/drm/igt-gpu-
tools/-/commit/963917a3565466832a3b2fc22e9285d34a0bf944
I propose to backport this patch
** Changed in: intel-gpu-tools (Ubuntu)
Status: New => In Progress
** Changed in: intel-gpu-tools (Ubuntu)
Assignee: (unassigned) => Hector CAO (hectorcao)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
In Progress
Bug description:
When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+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 2061248] Re: kernel 5.15.0-102 - CIFS mount problem (NAS)
*** This bug is a duplicate of bug 2060780 *** https://bugs.launchpad.net/bugs/2060780 Come over to bug 2060780 and talk about it with us there. ** This bug has been marked a duplicate of bug 2060780 CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 -- 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/2061248 Title: kernel 5.15.0-102 - CIFS mount problem (NAS) Status in linux package in Ubuntu: New Bug description: CIFS are regulary mounted via fstab (system has been stable for several years) and everything was fine with .101 but after the 08-apr-2024 kernel update suddenly the NAS shares are often stuck or timed out, unresponsive and not accessible (unavailable). Reverting from .102 to .101 brought everything back to working order as it was before kernel update. Something in the latest kernel 5.15.0-102 is not good for CIFS shares. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061248/+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 2061324] [NEW] Error when re-building package from source
Public bug reported:
When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
** Affects: intel-gpu-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
New
Bug description:
When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+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 2061322] [NEW] package nvidia-driver-535-server 535.161.07-0ubuntu0.22.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: i don't know ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-driver-535-server 535.161.07-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 11 18:55:04 2024 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2022-11-01 (529 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: nvidia-graphics-drivers-535-server Title: package nvidia-driver-535-server 535.161.07-0ubuntu0.22.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-535-server (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 nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2061322 Title: package nvidia-driver-535-server 535.161.07-0ubuntu0.22.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-driver-535-server 535.161.07-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 11 18:55:04 2024 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2022-11-01 (529 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: nvidia-graphics-drivers-535-server Title: package nvidia-driver-535-server 535.161.07-0ubuntu0.22.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2061322/+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 1574196] Re: Card with chipset BCM4360 [14e4:43a0] (rev 03) doesn't see 5Ghz networks with high channel number.
I know that it is a closed source driver and to be honest with you, this is the only place where I see this bug being reported. But I really don't know where else to report it other than the ones that are currently working on this driver (which again, idk of to contact them) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1574196 Title: Card with chipset BCM4360 [14e4:43a0] (rev 03) doesn't see 5Ghz networks with high channel number. Status in bcmwl package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: The card Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03) doesn't see 5Ghz networks with an high channel number, if you change the channel back to a lower one the network will be found again. In my case with channel 104 the network wasn't seen by the card, with channel 40 it works fine wireless-info script result: ## wireless info START ## Report from: 22 Apr 2016 19:23 CEST +0200 Booted last: 22 Apr 2016 18:51 CEST +0200 Script from: 27 Sep 2015 00:34 UTC + # release ### Distributor ID: Ubuntu Description: Ubuntu 14.04.4 LTS Release: 14.04 Codename: trusty # kernel Linux 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Parameters: ro, quiet, splash, vt.handoff=7 # desktop ### Ubuntu # lspci # 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7758] Kernel driver in use: r8169 04:00.0 Network controller [0280]: Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03) Subsystem: Broadcom Corporation Device [14e4:0619] Kernel driver in use: wl # lsusb # Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 004: ID 1532:0016 Razer USA, Ltd DeathAdder Mouse Bus 001 Device 003: ID 258a:0001 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # PCMCIA card info ## # rfkill 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no # lsmod # wl 6367819 0 mxm_wmi13021 1 nouveau wmi19177 2 mxm_wmi,nouveau cfg80211 496328 1 wl # interfaces auto lo iface lo inet loopback # ifconfig ## eth0 Link encap:Ethernet HWaddr UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) virbr0Link encap:Ethernet HWaddr inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan2 Link encap:Ethernet HWaddr inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:45040 errors:0 dropped:0 overruns:0 frame:7469 TX packets:33232 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:33581962 (33.5 MB) TX bytes:6334838 (6.3 MB) Interrupt:18 # iwconfig ## eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. wlan2 IEEE 802.11abg ESSID:"LamerTexWiFi" Mode:Managed Frequency:2.437 GHz Access Point: Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off # route # Kernel IP routing table Destination Gateway Genmask
[Kernel-packages] [Bug 2043801] Re: make linux-libc-dev & linux-libc-dev-cross M-A:foreign Arch:all
this is a no-go for now, linux-libc-dev providing all linux-libc-dev- cross-, making the c-t-b packages uninstallable and forcing the /usr/include on the include path of the cross toolchain -- 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/2043801 Title: make linux-libc-dev & linux-libc-dev-cross M-A:foreign Arch:all Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-mipsen package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in linux package in Ubuntu: Triaged Bug description: make linux-libc-dev & linux-libc-dev-cross M-A:foreign Arch:all 1) there was broad agreement in Riga 2) there is partial agreement in Debian too https://lists.debian.org/debian-kernel/2023/11/msg00131.html https://salsa.debian.org/kernel-team/linux/-/merge_requests/909/diffs 3) attempt to implement this in noble 4) changes required to: linux linux-uapi cross-toolchain-base-* 5) if things don't work out, fallback plan is to revert linux-libc- dev-cross; or to revert linux-libc-dev changes; or both of them and go back to how things were in mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cross-toolchain-base/+bug/2043801/+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 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
Same problem on Debian 12 with kernel 6.1.0-17-amd64 (OK with kernel 6.1.0-16-amd64). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Bug description: Remote filesystems mounted as CIFS are not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64). The remote filesystem is correctly mounted and seems to work but trying to write data to the filesystem ends in a kernel error exception. After that error the CIFS filesystem just became unusable. Previous Kernel version works correctly. = Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64) = # lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 # uname -a Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 6.5.0-27.28-generic 6.5.13 How to reproduce the problem For instance, I'm using KeePassXC (https://launchpad.net/ubuntu/+source/keepassxc) to update a database located at CIFS filesystem. Any change done to that database causes this Kernel error exception: abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: fffe abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 abr 11 09:34:59 fpgmsi kernel: Oops: [#1] PREEMPT SMP NOPTI abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022 abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 abr 11 09:34:59 fpgmsi kernel: RAX: RBX: fffe RCX: abr 11 09:34:59 fpgmsi kernel: RDX: RSI: RDI: abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 R09: abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11: R12: abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 abr 11 09:34:59 fpgmsi kernel: FS: 7bd4d594b6c0() GS:90753f80() knlGS: abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0: 80050033 abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 CR4: 00750ef0 abr 11 09:34:59 fpgmsi kernel: PKRU: 5554 abr 11 09:34:59 fpgmsi kernel: Call Trace: abr 11 09:34:59 fpgmsi kernel: abr 11 09:34:59 fpgmsi kernel: ? show_regs+0x6d/0x80 abr 11 09:34:59 fpgmsi kernel: ? __die+0x24/0x80 abr 11 09:34:59 fpgmsi kernel: ? page_fault_oops+0x99/0x1b0 abr 11 09:34:59 fpgmsi kernel: ? kernelmode_fixup_or_oops+0xb2/0x140 abr 11 09:34:59 fpgmsi kernel: ? __bad_area_nosemaphore+0x1a5/0x2c0 abr 11 09:34:59 fpgmsi kernel: ? bad_area_nosemaphore+0x16/0x30 abr 11 09:34:59 fpgmsi kernel: ? do_kern_addr_fault+0x7b/0xa0 abr 11 09:34:59 fpgmsi kernel: ? exc_page_fault+0x1a4/0x1b0 abr 11 09:34:59 fpgmsi kernel: ? asm_exc_page_fault+0x27/0x30 abr 11 09:34:59 fpgmsi kernel: ? cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: ? cifs_flush_folio+0x37/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: cifs_remap_file_range+0x172/0x660 [cifs] abr 11 09:34:59 fpgmsi kernel: do_clone_file_range+0x101/0x2d0 abr 11 09:34:59 fpgmsi kernel: vfs_clone_file_range+0x3f/0x150 abr 11 09:34:59 fpgmsi kernel: ioctl_file_clone+0x52/0xc0 abr 11 09:34:59 fpgmsi kernel: do_vfs_ioctl+0x68f/0x910 abr 11 09:34:59 fpgmsi kernel: ? __fget_light+0xa5/0x120 abr 11 09:34:59 fpgmsi kernel:
[Kernel-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
What's the resolution here? I've tried every incantation of fixes and patches. I'm currently running 6.9-rc but even that doesn't resolve the problem. Latest installs of sof-firmwre, updating alsa tools...nothing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module
I would like to know if anyone found a solution for lg gram systems. Currently i am using HW and os see below. kernel is from mainline archive Operating System: Linux Mint 21.3 Kernel: Linux 5.19.17-051917-generic Architecture: x86-64 Hardware Vendor: LG Electronics Hardware Model: 17Z90Q-G.AA78G This kernel works, when you start the system without AC plugged. suspend, plug AC, wakeup. boot param for kernel is acpi_mask_gpe=0x6E 0x6e can be unmasked immediately after boot. All newer kernels i tested have the problem with kworkers driving the load to 3 and more, rendering the system unusable when on ac. Without AC plugged they all work fine, with far better performance and energy saving as the 5.19 The kernelfunction hogging cpu is always something like os_map_remove. Cant check it right now exactly while writing. Did anyone find a kernel version > 5.19 that works also on AC on these Systems? -- 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/1990876 Title: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu 22.04, as of yesterday night upon rebooting the framework laptop (which had not been rebooted for several weeks), the fans come on strong and I see, with top, a kworker process at nearly 100% CPU utilization, which makes the laptop unusable. I have an early Framework laptop with an 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz. I removed all USB-c expansion cards except for one with an USB-c pass through, to no avail. With perf I have been able to determine that the xhci_hub_control and perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop cannot suspend any more, when it was working flawlessly until the reboot. $ sudo apt install linux-tools-common linux-tools-$(uname -r) $ sudo -i # echo -1 > /proc/sys/kernel/perf_event_paranoid # perf record control-c # perf report Samples: 125K of event 'cycles', Event count (approx.): 142991820424 Overhead Command Shared Object Symbol 54.11% kworker/5:2+usb [kernel.kallsyms] [k] xhci_hub_control ◆ 7.94% kworker/5:2+usb [kernel.kallsyms] [k] xhci_bus_suspend ▒ 0.98% kworker/5:2+usb [kernel.kallsyms] [k] kfree ▒ 0.86% kworker/5:2+usb [kernel.kallsyms] [k] _raw_spin_lock_irqsave ... What can be done to address this issue with a kworker? I suspect perhaps the new kernel is at fault. I tried rebooting to the prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the same result. What has changed? What can be done about this kworker and the xchi_hub_control? A temporary solution: $ sudo modprobe -r xhci_pci … which results in the kworker process disappearing from `top` (reduced CPU usage to near zero), the fans wind down, and unfortunately the ethernet expansion bay doesn’t work anymore but at least wifi does. Keyboard and touchpad also work. And suspend with deep also work well, just tested it. I assume other expansion bays will stop working too, but the laptop is at least charging: the USB-c pass-through works. See also: https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 4870 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 18:14:26 2022 InstallationDate: Installed on 2022-03-11 (199 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked:
[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
I can mount cifs shares with kernel 6.5.0-27, but when copying files from the share to the same share the process is killed everytime. Same effect using bash "cp" or KDE kio copy via Krusader. Running with kernel 6.5.0-26 anything works perfect. Syslog says: 2024-04-14T16:06:01.997083+02:00 monster kernel: [ 42.667380] BUG: unable to handle page fault for address: fffe 2024-04-14T16:06:01.997099+02:00 monster kernel: [ 42.667391] #PF: supervisor read access in kernel mode 2024-04-14T16:06:01.997100+02:00 monster kernel: [ 42.667393] #PF: error_code(0x) - not-present page 2024-04-14T16:06:01.997101+02:00 monster kernel: [ 42.667396] PGD 1afa3f067 P4D 1afa3f067 PUD 1afa41067 PMD 0 2024-04-14T16:06:01.997101+02:00 monster kernel: [ 42.667411] Oops: [#1] PREEMPT SMP PTI 2024-04-14T16:06:01.997102+02:00 monster kernel: [ 42.667414] CPU: 0 PID: 4326 Comm: cp Tainted: P O 6.5.0-27-generic #28-Ubuntu 2024-04-14T16:06:01.997104+02:00 monster kernel: [ 42.667418] Hardware name: System manufacturer System Product Name/P8B75-V, BIOS 1608 03/18/2014 2024-04-14T16:06:01.997104+02:00 monster kernel: [ 42.667420] RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] 2024-04-14T16:06:01.997105+02:00 monster kernel: [ 42.667495] Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 13 ed 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 2024-04-14T16:06:01.997107+02:00 monster kernel: [ 42.667498] RSP: 0018:9f2c835bbcb0 EFLAGS: 00010282 2024-04-14T16:06:01.997107+02:00 monster kernel: [ 42.667501] RAX: RBX: fffe RCX: 2024-04-14T16:06:01.997108+02:00 monster kernel: [ 42.667503] RDX: RSI: RDI: 2024-04-14T16:06:01.997109+02:00 monster kernel: [ 42.667505] RBP: 9f2c835bbce0 R08: 0001 R09: 2024-04-14T16:06:01.997110+02:00 monster kernel: [ 42.667507] R10: 0028 R11: R12: 2024-04-14T16:06:01.997110+02:00 monster kernel: [ 42.667509] R13: 9f2c835bbd30 R14: 89ca1f3d8d60 R15: 9f2c835bbd28 2024-04-14T16:06:01.997111+02:00 monster kernel: [ 42.667511] FS: 7a893d461540() GS:89cb15c0() knlGS: 2024-04-14T16:06:01.997112+02:00 monster kernel: [ 42.667513] CS: 0010 DS: ES: CR0: 80050033 2024-04-14T16:06:01.997113+02:00 monster kernel: [ 42.667516] CR2: fffe CR3: 00017f140006 CR4: 001706f0 2024-04-14T16:06:01.997113+02:00 monster kernel: [ 42.667518] Call Trace: 2024-04-14T16:06:01.997114+02:00 monster kernel: [ 42.667521] 2024-04-14T16:06:01.997115+02:00 monster kernel: [ 42.667524] ? show_regs+0x6d/0x80 2024-04-14T16:06:01.997116+02:00 monster kernel: [ 42.667532] ? __die+0x24/0x80 2024-04-14T16:06:01.997116+02:00 monster kernel: [ 42.667536] ? page_fault_oops+0x99/0x1b0 2024-04-14T16:06:01.997117+02:00 monster kernel: [ 42.667541] ? kernelmode_fixup_or_oops+0xb2/0x140 2024-04-14T16:06:01.997117+02:00 monster kernel: [ 42.667544] ? __bad_area_nosemaphore+0x1a5/0x2c0 2024-04-14T16:06:01.997118+02:00 monster kernel: [ 42.667556] ? bad_area_nosemaphore+0x16/0x30 2024-04-14T16:06:01.997119+02:00 monster kernel: [ 42.667558] ? do_kern_addr_fault+0x7b/0xa0 2024-04-14T16:06:01.997119+02:00 monster kernel: [ 42.667561] ? exc_page_fault+0x1a4/0x1b0 2024-04-14T16:06:01.997120+02:00 monster kernel: [ 42.667567] ? asm_exc_page_fault+0x27/0x30 2024-04-14T16:06:01.997121+02:00 monster kernel: [ 42.667575] ? cifs_flush_folio+0x41/0xf0 [cifs] 2024-04-14T16:06:01.997121+02:00 monster kernel: [ 42.667639] cifs_remap_file_range+0x172/0x660 [cifs] 2024-04-14T16:06:01.997122+02:00 monster kernel: [ 42.667703] do_clone_file_range+0x104/0x2d0 2024-04-14T16:06:01.997122+02:00 monster kernel: [ 42.667708] vfs_clone_file_range+0x3f/0x150 2024-04-14T16:06:01.997123+02:00 monster kernel: [ 42.667713] ioctl_file_clone+0x52/0xc0 2024-04-14T16:06:01.997123+02:00 monster kernel: [ 42.667718] do_vfs_ioctl+0x68f/0x910 2024-04-14T16:06:01.997124+02:00 monster kernel: [ 42.667721] ? switch_fpu_return+0x55/0xf0 2024-04-14T16:06:01.997125+02:00 monster kernel: [ 42.667726] ? exit_to_user_mode_prepare+0x9b/0xb0 2024-04-14T16:06:01.997125+02:00 monster kernel: [ 42.667730] __x64_sys_ioctl+0x7d/0xf0 2024-04-14T16:06:01.997126+02:00 monster kernel: [ 42.667734] do_syscall_64+0x5c/0x90 2024-04-14T16:06:01.997126+02:00 monster kernel: [ 42.667739] ? do_syscall_64+0x68/0x90 2024-04-14T16:06:01.997127+02:00 monster kernel: [ 42.667742] ? irqentry_exit_to_user_mode+0x17/0x20 2024-04-14T16:06:01.997128+02:00 monster kernel: [ 42.667747] ? irqentry_exit+0x43/0x50 2024-04-14T16:06:01.997128+02:00 monster kernel: [ 42.667751] ?
[Kernel-packages] [Bug 2061295] Re: No graphical boot with default Kubuntu 24.04
Here's a log file when booting with kernel 6.5. ** Attachment added: "Kernel-6.5-boot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061295/+attachment/5765233/+files/Kernel-6.5-boot.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/2061295 Title: No graphical boot with default Kubuntu 24.04 Status in linux package in Ubuntu: New Bug description: I upgraded from 23.10 to 24.04, and with it the new 6.8 kernel. I do not see the Kubuntu EFI logo, and the system never reaches the sddm login screen. I could not switch to a tty to login either. If I boot kernel 6.5 it works as expected. If I remove "quiet splash" from the boot parameters, then kernel 6.8 also boots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 14 16:08:22 2024 InstallationDate: Installed on 2023-01-16 (454 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-13 (1 days ago) dmi.bios.date: 03/01/2024 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.08 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.08:bd03/01/2024:br5.32:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061295/+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 2061295] Re: No graphical boot with default Kubuntu 24.04
Attaching a log file from a failed boot with kernel 6.8 with splash enabled ** Attachment added: "failedboot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061295/+attachment/5765213/+files/failedboot.txt ** Description changed: I upgraded from 23.10 to 24.04, and with it the new 6.8 kernel. I do not see the Kubuntu EFI logo, and the system never reaches the sddm login - screen. If I boot kernel 6.5 it works as expected. + screen. I could not switch to a tty to login either. If I boot kernel + 6.5 it works as expected. If I remove "quiet splash" from the boot parameters, then kernel 6.8 also boots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 14 16:08:22 2024 InstallationDate: Installed on 2023-01-16 (454 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro RelatedPackageVersions: - linux-restricted-modules-6.8.0-22-generic N/A - linux-backports-modules-6.8.0-22-generic N/A - linux-firmware20240318.git3b128b60-0ubuntu2 + linux-restricted-modules-6.8.0-22-generic N/A + linux-backports-modules-6.8.0-22-generic N/A + linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-13 (1 days ago) dmi.bios.date: 03/01/2024 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.08 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.08:bd03/01/2024:br5.32:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock -- 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/2061295 Title: No graphical boot with default Kubuntu 24.04 Status in linux package in Ubuntu: New Bug description: I upgraded from 23.10 to 24.04, and with it the new 6.8 kernel. I do not see the Kubuntu EFI logo, and the system never reaches the sddm login screen. I could not switch to a tty to login either. If I boot kernel 6.5 it works as expected. If I remove "quiet splash" from the boot parameters, then kernel 6.8 also boots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 14 16:08:22 2024 InstallationDate: Installed on 2023-01-16 (454 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-13 (1 days ago) dmi.bios.date: 03/01/2024 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.08 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.08:bd03/01/2024:br5.32:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage
[Kernel-packages] [Bug 2061295] [NEW] No graphical boot with default Kubuntu 24.04
Public bug reported: I upgraded from 23.10 to 24.04, and with it the new 6.8 kernel. I do not see the Kubuntu EFI logo, and the system never reaches the sddm login screen. I could not switch to a tty to login either. If I boot kernel 6.5 it works as expected. If I remove "quiet splash" from the boot parameters, then kernel 6.8 also boots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 14 16:08:22 2024 InstallationDate: Installed on 2023-01-16 (454 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-13 (1 days ago) dmi.bios.date: 03/01/2024 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.08 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.08:bd03/01/2024:br5.32:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- 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/2061295 Title: No graphical boot with default Kubuntu 24.04 Status in linux package in Ubuntu: New Bug description: I upgraded from 23.10 to 24.04, and with it the new 6.8 kernel. I do not see the Kubuntu EFI logo, and the system never reaches the sddm login screen. I could not switch to a tty to login either. If I boot kernel 6.5 it works as expected. If I remove "quiet splash" from the boot parameters, then kernel 6.8 also boots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 14 16:08:22 2024 InstallationDate: Installed on 2023-01-16 (454 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-13 (1 days ago) dmi.bios.date: 03/01/2024 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.08 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.08:bd03/01/2024:br5.32:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061295/+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 1471380] Re: [Fujitsu Lifebook AH532] Installing Ubuntu on a USB-drive locks out firmware access
The workaround has now landed in all currently supported linux-stable branches: linux-6.8: 6.8-rc7 (f45812cc23fb74bef62d4eb8a69fe7218f4b9f2a) linux-6.7: 6.7.9(cbf12e716a52d260fabecdca7d5f6e7cd07aed6c) linux-6.6: 6.6.21 (71da10e633a96593cf59af3f322a9c49a22cb71e) linux-6.1: 6.1.81 (249d6ca4ff0022a4b51a8eb9fac6d7bff2c94d1b) linux-5.15: 5.15.154 (9bc9c11c151ab27214cc204d954ee902e9bbe8e2) linux-5.10: 5.10.215 (f33255ccbb0f627da76364cce72cf980d027142c) linux-5.4: 5.4.274 (34b5d2ff9ed5cdea9f971f394c0d623761a4d357) linux-4.19: 4.19.312 (a7bd7dbaa2ddcf8c5ed5d96df240f1442447d252) I tested the recent Ubuntu 24.04 beta and made sure the issue is already fixed there. Sadly, we just about missed the time (by about two months) to get the fix into the ISOs for Ubuntu 22.04.4. -- 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/1471380 Title: [Fujitsu Lifebook AH532] Installing Ubuntu on a USB-drive locks out firmware access Status in linux package in Ubuntu: Confirmed Bug description: I've been running pre-installed Windows 7 on a Fujitsu AH532 since 2012. Two weeks back, I installed a Live-USB with Ubuntu 14.04. All working well, but I struggled getting it persistent, so I decided to do a full Ubuntu installation to another USB-drive. Leaving my Windows hard drive untouched. What I did: 1) I entered my "BIOS" to change boot order, and booting from my Ubuntu Live-USB. 2) I tried following the installation guide https://help.ubuntu.com/community/Installation/UEFI-and-BIOS, but sizes were changed to: - 1MB BIOS Boot (pretty sure I left this unformatted,but it now reports as Ext4) - 666MB EFI System, FAT32 - 30GB Linux Filesystem, Ext4 - 999MB Linux Swap, Swap 3) I installed Ubuntu on a second USB-drive. Leaving my Windows hard- drive "intact" (?) The result: Now, I can only boot my machine by inserting my second full-installation-USB-drive. I cannot boot Windows, and I cannot boot from my LiveUSB. If I boot without inserting my full-installation-USB-drive, I get the boot screen telling me I can press F2 or F12. However, none of these have any effect, apart from making the beep. Then the computer enters the "Boot menu" (as well as the second menu "Application menu"). This bug feels very related to: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387 $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-41-generic 3.16.0-41.55~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 4 08:05:03 2015 InstallationDate: Installed on 2015-06-18 (15 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vegard 2045 F...m pulseaudio /dev/snd/controlC0: vegard 2045 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=b7bfbfab-671b-471c-ba59-210445db2063 InstallationDate: Installed on 2015-06-18 (16 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: FUJITSU LIFEBOOK AH532 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-41-generic.efi.signed root=UUID=b9d1f4be-275f-4b97-a68a-ccb2afa41781 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/22/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.09 dmi.board.name: FJNBB1C dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.09:bd05/22/2012:svnFUJITSU:pnLIFEBOOKAH532:pvr:rvnFUJITSU:rnFJNBB1C:rvr:cvnFUJITSU:ct10:cvr:
[Kernel-packages] [Bug 2061276] [NEW] package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1 failed to install/upgrade: підпроцес встановлено пакунок bcmwl-kernel-source сценарій post-instal
Public bug reported: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1 failed to install/upgrade: підпроцес встановлено пакунок bcmwl-kernel-source сценарій post-installation повернув помилковий код завершення 10 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Apr 14 12:25:55 2024 ErrorMessage: підпроцес встановлено пакунок bcmwl-kernel-source сценарій post-installation повернув помилковий код завершення 10 InstallationDate: Installed on 2024-04-13 (1 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1 failed to install/upgrade: підпроцес встановлено пакунок bcmwl-kernel-source сценарій post-installation повернув помилковий код завершення 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (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 bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/2061276 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1 failed to install/upgrade: підпроцес встановлено пакунок bcmwl-kernel- source сценарій post-installation повернув помилковий код завершення 10 Status in bcmwl package in Ubuntu: New Bug description: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1 failed to install/upgrade: підпроцес встановлено пакунок bcmwl-kernel- source сценарій post-installation повернув помилковий код завершення 10 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Apr 14 12:25:55 2024 ErrorMessage: підпроцес встановлено пакунок bcmwl-kernel-source сценарій post-installation повернув помилковий код завершення 10 InstallationDate: Installed on 2024-04-13 (1 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10~22.04.1 failed to install/upgrade: підпроцес встановлено пакунок bcmwl-kernel-source сценарій post-installation повернув помилковий код завершення 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/2061276/+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 2058483] Re: touchpad not working
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => Kai-Heng Feng (kaihengfeng) -- 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/2058483 Title: touchpad not working Status in linux package in Ubuntu: New Bug description: The touchpad is not in the xinput list and it doesn't work. I'm using hp pavilion 15 ec1021nl ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 14:21:02 2024 InstallationDate: Installed on 2024-03-20 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058483/+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 2058752] Re: ath11k high jitter and packet loss when operating in 802.11ax mode
** Changed in: linux (Ubuntu)
Assignee: Anthony Wong (anthonywong) => AceLan Kao (acelankao)
--
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/2058752
Title:
ath11k high jitter and packet loss when operating in 802.11ax mode
Status in linux package in Ubuntu:
New
Bug description:
On 6.5.0-26-generic, my QCNFA765 cannot really operate in 802.11ax
mode.
I have a Thinkpad P16s Gen 2 with a (soldered, sadly) QCNFA765 card, which
uses the ath11k driver.
I also have a Ruckus R650 AP, which supports wifi6.
Connecting the two and pinging the AP yields the following:
```
64 bytes from 192.168.16.77: icmp_seq=45 ttl=64 time=22.4 ms
64 bytes from 192.168.16.77: icmp_seq=46 ttl=64 time=29.6 ms
64 bytes from 192.168.16.77: icmp_seq=47 ttl=64 time=26.8 ms
64 bytes from 192.168.16.77: icmp_seq=48 ttl=64 time=2174 ms
64 bytes from 192.168.16.77: icmp_seq=49 ttl=64 time=1158 ms
64 bytes from 192.168.16.77: icmp_seq=50 ttl=64 time=130 ms
64 bytes from 192.168.16.77: icmp_seq=51 ttl=64 time=503 ms
64 bytes from 192.168.16.77: icmp_seq=54 ttl=64 time=1832 ms
64 bytes from 192.168.16.77: icmp_seq=55 ttl=64 time=808 ms
64 bytes from 192.168.16.77: icmp_seq=56 ttl=64 time=9.32 ms
64 bytes from 192.168.16.77: icmp_seq=57 ttl=64 time=2.11 ms
64 bytes from 192.168.16.77: icmp_seq=58 ttl=64 time=25.6 ms
64 bytes from 192.168.16.77: icmp_seq=59 ttl=64 time=30.9 ms
64 bytes from 192.168.16.77: icmp_seq=60 ttl=64 time=95.6 ms
^C
--- 192.168.16.77 ping statistics ---
60 packets transmitted, 55 received, 8.3% packet loss, time 59273ms
rtt min/avg/max/mdev = 2.105/275.084/2344.792/560.334 ms, pipe 3
```
Those periodic bursts of >1s latency make some webpages fail to load
and videochats unusable.
No interference is present in my channel of choice.
Nothing interesting is printed in dmesg while the above occurs.
The above does not happen if:
* I disable wifi 6 in the AP
* I ping a wifi 5 AP (I also have an older R710, which is a 802.11ac AP)
* I ping the R650 in wifi 6 mode from a AX210 on kernel 6.2
* I ping the R650 from a completely different OS and device (e.g. Android)
I'll test with a 24.04 daily image next.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 21 16:58:07 2024
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: root=zfs:zroot/ROOT/ubuntu quiet loglevel=4
rtc_cmos.use_acpi_alarm=1 spl.spl_hostid=0x4605c990
RelatedPackageVersions:
linux-restricted-modules-6.5.0-26-generic N/A
linux-backports-modules-6.5.0-26-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/15/2024
dmi.bios.release: 1.18
dmi.bios.vendor: LENOVO
dmi.bios.version: R2FET38W (1.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21K9001NUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrR2FET38W(1.18):bd01/15/2024:br1.18:efr1.11:svnLENOVO:pn21K9001NUS:pvrThinkPadP16sGen2:rvnLENOVO:rn21K9001NUS:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K9_BU_Think_FM_ThinkPadP16sGen2:
dmi.product.family: ThinkPad P16s Gen 2
dmi.product.name: 21K9001NUS
dmi.product.sku: LENOVO_MT_21K9_BU_Think_FM_ThinkPad P16s Gen 2
dmi.product.version: ThinkPad P16s Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058752/+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 2059820] Re: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: Anthony Wong (anthonywong) => En-Wei Wu (rickywu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059820 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1 Status in linux-signed-hwe-6.5 package in Ubuntu: Invalid Bug description: 每次开机 提示一个报错 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-generic-hwe-22.04:amd64: Remove linux-image-generic-hwe-22.04:amd64: Remove linux-image-6.5.0-26-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 29 16:19:20 2024 ErrorMessage: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2024-03-29 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.11 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1 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-6.5/+bug/2059820/+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 2059973] Re: my touch pad doesn't wok at all.
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: Anthony Wong (anthonywong) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059973 Title: my touch pad doesn't wok at all. Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: i'm new at linux. firstly i have installed ubuntu as dual boot besides windows 11 pro. that time the touchpad worked as expected. but when i gain confident enough that i can use linux, i installed ubuntu as primary setup, after that the touch pad is not working. it detects the touch pad as follows cat /proc/bus/input/devices I: Bus=0018 Vendor=06cb Product=ce78 Version=0100 N: Name="SYNA2BA6:00 06CB:CE78 Mouse" P: Phys=i2c-SYNA2BA6:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA2BA6:00/0018:06CB:CE78.0001/input/input22 U: Uniq= H: Handlers=mouse0 event19 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 I: Bus=0018 Vendor=06cb Product=ce78 Version=0100 N: Name="SYNA2BA6:00 06CB:CE78 Touchpad" P: Phys=i2c-SYNA2BA6:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA2BA6:00/0018:06CB:CE78.0001/input/input23 U: Uniq= H: Handlers=mouse1 event20 B: PROP=5 B: EV=1b B: KEY=e520 1 0 0 0 0 B: ABS=2e08003 B: MSC=20 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 02:29:41 2024 InstallationDate: Installed on 2024-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 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-6.5/+bug/2059973/+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 2060748] Re: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card
@Jess, Yes, that would be helpful if you can help to collect the dynamic debug log by the trace-cmd. There is no update for the iwlwifi firmware(-83) you are using now, but it might worth of trying to upgrade the firmware version to -84. You can download the latest firmware from the linux-firmware git tree[1], but please remember that only copy the files you need. That help us to narrow down the required firmware. In this case you probably only need iwlwifi-ty-a0-gf-a0-84.ucode, you can check your boot dmesg to see which firmware is loaded. You can upload the boot dmesg here if you are not sure which firmware you are using. 1. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/ -- 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/2060748 Title: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card Status in linux package in Ubuntu: New Bug description: I just installed Kubuntu 23.10 (using latest default kernel) on a new desktop PC I built, which uses an AX210NGW DTK M.2 wifi/bluetooth card. Here is output from lspci -v: e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15 Memory at ba30 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi Wifi error popping up every few minutes in Kubuntu I just installed Kubuntu 23.10 on a new desktop PC I built, which uses an AX210NGW DTK M.2 wifi card: Code: e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15 Memory at ba30 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi The internet seems to be somewhat working, but at least once a minute I have two "Network Management" error notifications that pop up in KDE that say "Connection Wired Connection 3 deactivated" and "Wired Interface e2x52e8ae7d39d1: IP configuration was unavailable". I checked the logs in /var/log/dmesg and saw that there were a ton of iwlwifi error messages in there that look like this: [ 44.926474] kernel: Intel(R) Wireless WiFi driver for Linux [ 44.926508] kernel: iwlwifi :e4:00.0: enabling device ( -> 0002) [ 44.927758] kernel: iwlwifi :e4:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x8000 [ 44.927763] kernel: iwlwifi :e4:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000 [ 44.931064] kernel: iwlwifi :e4:00.0: api flags index 2 larger than supported by driver [ 44.931076] kernel: iwlwifi :e4:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41 [ 44.931318] kernel: iwlwifi :e4:00.0: loaded firmware version 83.e8f84e98.0 ty-a0-gf-a0-83.ucode op_mode iwlmvm [ 44.955070] kernel: Bluetooth: Core ver 2.22 [ 44.955089] kernel: NET: Registered PF_BLUETOOTH protocol family [ 44.955090] kernel: Bluetooth: HCI device and connection manager initialized [ 44.955095] kernel: Bluetooth: HCI socket layer initialized [ 44.955097] kernel: Bluetooth: L2CAP socket layer initialized [ 44.955101] kernel: Bluetooth: SCO socket layer initialized [ 45.275827] kernel: Bluetooth: hci0: Device revision is 0 [ 45.275833] kernel: Bluetooth: hci0: Secure boot is enabled [ 45.275836] kernel: Bluetooth: hci0: OTP lock is enabled [ 45.275838] kernel: Bluetooth: hci0: API lock is enabled [ 45.275840] kernel: Bluetooth: hci0: Debug lock is disabled [ 45.275842] kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 45.275845] kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 [ 45.276888] kernel: nvidia :c1:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none [ 45.278400] kernel: Bluetooth: hci0:
[Kernel-packages] [Bug 2060193] Re: iwlwifi microcode crash when using wrong password to join a WPA3 access point
** Changed in: linux-firmware (Ubuntu) Assignee: Anthony Wong (anthonywong) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2060193 Title: iwlwifi microcode crash when using wrong password to join a WPA3 access point Status in linux-firmware package in Ubuntu: New Bug description: I noticed that whenever I try to join a wireless network using WPA3 SAE and type the password wrong, I get a microcode crash from iwlwifi. The chip is Intel 9462 (AX201). Ubuntu release 22.04 LTS, faithfully kept up to date. System info available via: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2058226 Crash log seems to be always similar: Apr 3 22:13:55 waplinuc kernel: [1158486.254336] iwlwifi :00:14.3: Not associated and the session protection is over already... Apr 3 22:13:57 waplinuc kernel: [1158487.456868] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Apr 3 22:13:57 waplinuc kernel: [1158487.456960] iwlwifi :00:14.3: Start IWL Error Log Dump: Apr 3 22:13:57 waplinuc kernel: [1158487.456962] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Apr 3 22:13:57 waplinuc kernel: [1158487.456965] iwlwifi :00:14.3: Loaded firmware version: 77.206b0184.0 QuZ-a0-jf-b0-77.ucode Apr 3 22:13:57 waplinuc kernel: [1158487.456967] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Apr 3 22:13:57 waplinuc kernel: [1158487.456969] iwlwifi :00:14.3: 0x008022F3 | trm_hw_status0 Apr 3 22:13:57 waplinuc kernel: [1158487.456971] iwlwifi :00:14.3: 0x | trm_hw_status1 Apr 3 22:13:57 waplinuc kernel: [1158487.456973] iwlwifi :00:14.3: 0x004C03F2 | branchlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456974] iwlwifi :00:14.3: 0x64CC | interruptlink1 Apr 3 22:13:57 waplinuc kernel: [1158487.456976] iwlwifi :00:14.3: 0x64CC | interruptlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456977] iwlwifi :00:14.3: 0x0001191E | data1 Apr 3 22:13:57 waplinuc kernel: [1158487.456979] iwlwifi :00:14.3: 0x1000 | data2 Apr 3 22:13:57 waplinuc kernel: [1158487.456980] iwlwifi :00:14.3: 0x | data3 Apr 3 22:13:57 waplinuc kernel: [1158487.456982] iwlwifi :00:14.3: 0x04C0678B | beacon time Apr 3 22:13:57 waplinuc kernel: [1158487.456983] iwlwifi :00:14.3: 0x920B688C | tsf low Apr 3 22:13:57 waplinuc kernel: [1158487.456985] iwlwifi :00:14.3: 0x0221 | tsf hi Apr 3 22:13:57 waplinuc kernel: [1158487.456986] iwlwifi :00:14.3: 0x0DFD | time gp1 Apr 3 22:13:57 waplinuc kernel: [1158487.456988] iwlwifi :00:14.3: 0x00A909B7 | time gp2 Apr 3 22:13:57 waplinuc kernel: [1158487.456989] iwlwifi :00:14.3: 0x0001 | uCode revision type Apr 3 22:13:57 waplinuc kernel: [1158487.456991] iwlwifi :00:14.3: 0x004D | uCode version major Apr 3 22:13:57 waplinuc kernel: [1158487.456992] iwlwifi :00:14.3: 0x206B0184 | uCode version minor Apr 3 22:13:57 waplinuc kernel: [1158487.456994] iwlwifi :00:14.3: 0x0351 | hw version Apr 3 22:13:57 waplinuc kernel: [1158487.456995] iwlwifi :00:14.3: 0x00489001 | board version Apr 3 22:13:57 waplinuc kernel: [1158487.456997] iwlwifi :00:14.3: 0x001C | hcmd Apr 3 22:13:57 waplinuc kernel: [1158487.456998] iwlwifi :00:14.3: 0x00023000 | isr0 Apr 3 22:13:57 waplinuc kernel: [1158487.456999] iwlwifi :00:14.3: 0x0004C000 | isr1 Apr 3 22:13:57 waplinuc kernel: [1158487.457001] iwlwifi :00:14.3: 0x08F80002 | isr2 Apr 3 22:13:57 waplinuc kernel: [1158487.457002] iwlwifi :00:14.3: 0x00C3000C | isr3 Apr 3 22:13:57 waplinuc kernel: [1158487.457004] iwlwifi :00:14.3: 0x | isr4 Apr 3 22:13:57 waplinuc kernel: [1158487.457005] iwlwifi :00:14.3: 0x0101001C | last cmd Id Apr 3 22:13:57 waplinuc kernel: [1158487.457006] iwlwifi :00:14.3: 0x0001191E | wait_event Apr 3 22:13:57 waplinuc kernel: [1158487.457008] iwlwifi :00:14.3: 0x54B6 | l2p_control Apr 3 22:13:57 waplinuc kernel: [1158487.457009] iwlwifi :00:14.3: 0x1C02 | l2p_duration Apr 3 22:13:57 waplinuc kernel: [1158487.457011] iwlwifi :00:14.3: 0x0003 | l2p_mhvalid Apr 3 22:13:57 waplinuc kernel: [1158487.457012] iwlwifi :00:14.3: 0x | l2p_addr_match Apr 3 22:13:57 waplinuc kernel: [1158487.457013] iwlwifi :00:14.3: 0x000B | lmpm_pmg_sel Apr 3 22:13:57 waplinuc kernel: [1158487.457015] iwlwifi :00:14.3: 0x | timestamp Apr 3 22:13:57 waplinuc kernel: [1158487.457016] iwlwifi :00:14.3: 0x88D4 | flow_handler Apr 3 22:13:57 waplinuc kernel: [1158487.457058] iwlwifi :00:14.3: Start IWL Error Log Dump: Apr 3 22:13:57 waplinuc kernel: [1158487.457059] iwlwifi :00:14.3: Transport
[Kernel-packages] [Bug 2060308] Re: no bluetooth detected
Need more hardware info to debug. Can you attach the output of lshw and dmesg? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060308 Title: no bluetooth detected Status in linux-signed-hwe-6.5 package in Ubuntu: Incomplete Bug description: no bluetooth detected ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 16:52:43 2024 InstallationDate: Installed on 2022-12-17 (475 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.5 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-6.5/+bug/2060308/+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 2060308] Re: no bluetooth detected
** Summary changed: - no bluettoth detected + no bluetooth detected ** Changed in: linux-signed-hwe-6.5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060308 Title: no bluetooth detected Status in linux-signed-hwe-6.5 package in Ubuntu: Incomplete Bug description: no bluetooth detected ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 16:52:43 2024 InstallationDate: Installed on 2022-12-17 (475 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.5 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-6.5/+bug/2060308/+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 2060373] Re: package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade: 의존성 문제 - 설정하지 않고 남겨둠
** Changed in: linux (Ubuntu)
Assignee: Anthony Wong (anthonywong) => En-Wei Wu (rickywu)
--
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/2060373
Title:
package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade:
의존성 문제 - 설정하지 않고 남겨둠
Status in linux package in Ubuntu:
New
Bug description:
This occured while system updater installing packages with no user
operation.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-generic-hwe-22.04 6.5.0.26.26
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jungwonyong 2613 F wireplumber
/dev/snd/controlC0: jungwonyong 2613 F wireplumber
/dev/snd/seq:jungwonyong 2607 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Apr 7 12:08:46 2024
ErrorMessage: 의존성 문제 - 설정하지 않고 남겨둠
InstallationDate: Installed on 2024-01-25 (73 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ricifp@/vmlinuz-6.5.0-21-generic
root=ZFS=rpool/ROOT/ubuntu_ricifp ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade:
의존성 문제 - 설정하지 않고 남겨둠
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2021
dmi.bios.release: 16.20
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1620
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H470-PLUS
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.:bvr1620:bd07/08/2021:br16.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH470-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060373/+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 2060716] Re: Screen flickering again
** Changed in: linux (Ubuntu)
Assignee: Anthony Wong (anthonywong) => AaronMa (mapengyu)
--
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/2060716
Title:
Screen flickering again
Status in linux package in Ubuntu:
New
Bug description:
There is random screen flickering with the build of kernel 6.5.0-27.
Also other builds of 6.5.0 have this flickering.
The *only* build of this version that does work without flickering is
6.5.0-13
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bf 5114 F pipewire
bf 5119 F wireplumber
/dev/snd/controlC0: bf 5119 F wireplumber
/dev/snd/seq:bf 5114 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 9 18:48:35 2024
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=be4de94b-3fb1-44d1-875a-edcd620dc310
InstallationDate: Installed on 2016-03-18 (2944 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=17026de9-c699-420e-ae96-01ac290b69ef 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-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2023
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N2VET45W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TK000AGE
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.11
dmi.modalias:
dmi:bvnLENOVO:bvrN2VET45W(1.30):bd08/29/2023:br1.30:efr1.11:svnLENOVO:pn20TK000AGE:pvrThinkPadX1ExtremeGen3:rvnLENOVO:rn20TK000AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TK_BU_Think_FM_ThinkPadX1ExtremeGen3:
dmi.product.family: ThinkPad X1 Extreme Gen 3
dmi.product.name: 20TK000AGE
dmi.product.sku: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
dmi.product.version: ThinkPad X1 Extreme Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060716/+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
