[Kernel-packages] [Bug 1987269] Re: [5.18.0 mainline] mlx5 deadlock
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1987269 Title: [5.18.0 mainline] mlx5 deadlock Status in linux package in Ubuntu: Expired Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy $ uname -a Linux pc1-rb3-n3 5.18.0-051800-generic #202205222030 SMP PREEMPT_DYNAMIC Sun May 22 20:33:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.735461] INFO: task ovn-controller:30439 blocked for more than 120 seconds. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.742835] Not tainted 5.18.0-051800-generic #202205222030 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.749051] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757010] task:ovn-controller state:D stack:0 pid:30439 ppid: 1 flags:0x0002 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757019] Call Trace: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757024] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757031] __schedule+0x246/0x5c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757045] schedule+0x55/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757050] schedule_preempt_disabled+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757057] __mutex_lock.constprop.0+0x2f3/0x4c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757064] __mutex_lock_slowpath+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757069] mutex_lock+0x35/0x40 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757073] rtnetlink_rcv_msg+0x114/0x3f0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757082] ? rtnl_calcit.isra.0+0x140/0x140 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757087] netlink_rcv_skb+0x56/0x100 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757095] rtnetlink_rcv+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757099] netlink_unicast+0x236/0x350 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757104] netlink_sendmsg+0x25e/0x4d0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757109] sock_sendmsg+0x66/0x70 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757117] sys_sendmsg+0x24f/0x290 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757123] ? import_iovec+0x1b/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757130] ? sendmsg_copy_msghdr+0x7c/0xa0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757137] ___sys_sendmsg+0x81/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757143] ? ___sys_recvmsg+0x99/0x110 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757148] ? netdev_name_node_lookup_rcu+0x6b/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757155] ? fput+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757161] ? __sys_sendmsg+0x98/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757166] ? __fget_light+0xa7/0x130 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757174] __sys_sendmsg+0x62/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757180] __x64_sys_sendmsg+0x1d/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757186] do_syscall_64+0x5c/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757191] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757194] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757200] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757203] ? exit_to_user_mode_prepare+0x37/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757210] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757214] ? __x64_sys_write+0x19/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757220] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757224] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757227] entry_SYSCALL_64_after_hwframe+0x44/0xae Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757232] RIP: 0033:0x7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757239] RSP: 002b:7ffd50fa8ec0 EFLAGS: 0293 ORIG_RAX: 002e Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757246] RAX: ffda RBX: 0001 RCX: 7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757252] RDX: RSI: 7ffd50fa8f50 RDI: 0020 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757255] RBP: 7ffd50fa9c40 R08: R09: 55e1a6a66f60 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757260] R10: 0001 R11: 0293 R12: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757264] R13: 55e1a53bc510 R14: 00074f30 R15: 7ffd50fa8f50 Aug 22 01:15:02 pc1-rb3-n3
[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
Same laptop same issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in linux package in Ubuntu: Confirmed Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+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 1995320] Re: [amdgpu] intermittent green static
A couple more data points. I installed and booted a 5.19.17 mainline kernel (from the ubuntu mainline kernel archive) and the static started immediately. I booted the 5.15.0-52-generic kernel left over from ubuntu 20.04 and haven't had any problems with static or full screen video after 30 minutes. This seems to point toward a kernel/driver issue rather than gnome- shell. ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) -- 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/1995320 Title: [amdgpu] intermittent green static Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995320/+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 1995320] [NEW] [amdgpu] intermittent green static
You have been subscribed to a public bug: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug apport-collected kinetic third-party-packages wayland-session -- [amdgpu] intermittent green static https://bugs.launchpad.net/bugs/1995320 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995408] Re: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks
** Description changed: - Running fio on NVME SSD can cause CPU soft locks. + SRU Justification + + [Impact] + + Hypervisor only allocates interrupts to happen on a single physical GPU, + which can lead to CPU soft locks when using PCI NVME under heavy load. + + Kinetic will get this patch via stable updates. + + [Test Case] + + Microsoft tested + + [Where things could go wrong] + + Hypervisor PCI driver may not load correctly. Patch did not apply + cleanly and could lead to merge conflicts once the upstream patch is + pulled in. + + [Other Info] + + SF: #00346549 -- 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/1995408 Title: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. Kinetic will get this patch via stable updates. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00346549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995408/+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 1990690] Re: Users belonging to video group may trigger a deadlock WARN
This bug is awaiting verification that the linux/4.15.0-197.208 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-bionic' to 'verification-done-bionic'. If the
problem still exists, change the tag 'verification-needed-bionic' to
'verification-failed-bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
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/1990690
Title:
Users belonging to video group may trigger a deadlock WARN
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
One of the fixing commits for CVE-2021-33655, commit 159a96b199b4
("fbcon: Prevent that screen size is smaller than font size") introduced
an extraneous lock_fb_info line into the ioctl flow in fbmem.c.
This line only exists in bionic tree.
Users belonging to video group may trigger a deadlock and potentially
lock the system.
WARNING: possible recursive locking detected
4.15.0-195-generic #206 Not tainted
refresh/1248 is trying to acquire lock:
(_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
but task is already holding lock:
(_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
lock(_info->lock);
lock(_info->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 locks held by refresh/1248:
#0: (console_lock){+.+.}, at: [<8000aa2b>] do_fb_ioctl+0x435/0x5e0
#1: (_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
stack backtrace:
CPU: 0 PID: 1248 Comm: refresh Not tainted 4.15.0-195-generic #206
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
Call Trace:
dump_stack+0x98/0xd2
__lock_acquire+0x736/0x1480
? sched_clock_local+0x17/0x90
? sched_clock+0x9/0x10
? sched_clock_local+0x17/0x90
lock_acquire+0xa3/0x1e0
? lock_acquire+0xa3/0x1e0
? lock_fb_info+0x1d/0x40
? lock_fb_info+0x1d/0x40
__mutex_lock+0x65/0x970
? lock_fb_info+0x1d/0x40
? sched_clock_local+0x17/0x90
? lock_acquire+0xa3/0x1e0
mutex_lock_nested+0x1b/0x20
? mutex_lock_nested+0x1b/0x20
lock_fb_info+0x1d/0x40
do_fb_ioctl+0x57a/0x5e0
? __fd_install+0x5/0x250
fb_ioctl+0x33/0x40
? fb_ioctl+0x33/0x40
do_vfs_ioctl+0xa9/0x6d0
? putname+0x4c/0x60
? do_sys_open+0x13d/0x370
SyS_ioctl+0x79/0x90
do_syscall_64+0x7b/0x1e0
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f22acca7217
RSP: 002b:7ffe2a930b48 EFLAGS: 0213 ORIG_RAX: 0010
RAX: ffda RBX: RCX: 7f22acca7217
RDX: 7ffe2a930c30 RSI: 4601 RDI: 0003
RBP: 7ffe2a930d40 R08: R09:
R10: R11: 0213 R12: 5624ac8fc7c0
R13: 7ffe2a930e20 R14: R15:
[Test case]
Run a sample framebuffer userspace test to call FBIOPUT_VSCREENINFO
and verified with LOCKDEP.
[Potential regressions]
There are no new potential regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990690/+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 1989144] Re: unprivileged users may trigger page cache invalidation WARN
This bug is awaiting verification that the linux/4.15.0-197.208 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1989144 Title: unprivileged users may trigger page cache invalidation WARN Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Unprivileged users may trigger a page cache invalidation failure when doing parallel direct I/O and buffered I/O. On some kernels, that may lead to a WARN. [ 22.415082] WARNING: CPU: 3 PID: 3404 at /build/linux-GtMq7R/linux-4.15.0/fs/iomap.c:903 iomap_dio_actor+0xbd/0x460 [ 22.415083] Modules linked in: xfs isofs kvm_intel kvm irqbypass joydev input_leds serio_raw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse ahci libahci virtio_blk virtio_net [ 22.415099] CPU: 3 PID: 3404 Comm: xfs_io Not tainted 4.15.0-192-generic #203-Ubuntu [ 22.415100] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 [ 22.415103] RIP: 0010:iomap_dio_actor+0xbd/0x460 [ 22.415104] RSP: 0018:b7c782fe7bf0 EFLAGS: 00010202 [ 22.415104] RAX: 0002 RBX: RCX: 0009 [ 22.415105] RDX: 01ff RSI: RDI: b7c782fe7e20 [ 22.415105] RBP: b7c782fe7c68 R08: b7c782fe7c88 R09: 9bbc9f48fba0 [ 22.415106] R10: 0001 R11: R12: 0009 [ 22.415106] R13: 9bbc9f48fba0 R14: b7c782fe7c88 R15: 1000 [ 22.415107] FS: 7f2b802ed700() GS:9bbcbfd8() knlGS: [ 22.415107] CS: 0010 DS: ES: CR0: 80050033 [ 22.415108] CR2: 01639000 CR3: 1e6b0003 CR4: 00760ee0 [ 22.415110] PKRU: 5554 [ 22.415110] Call Trace: [ 22.415122] ? iomap_dio_zero+0x130/0x130 [ 22.415123] iomap_apply+0xa5/0x120 [ 22.415124] ? iomap_dio_zero+0x130/0x130 [ 22.415125] iomap_dio_rw+0x2f3/0x430 [ 22.415126] ? iomap_dio_zero+0x130/0x130 [ 22.415148] xfs_file_dio_aio_read+0x68/0xf0 [xfs] [ 22.415157] ? xfs_file_dio_aio_read+0x68/0xf0 [xfs] [ 22.415165] xfs_file_read_iter+0xbf/0xe0 [xfs] [ 22.415170] new_sync_read+0xe4/0x130 [ 22.415171] __vfs_read+0x29/0x40 [ 22.415172] vfs_read+0x8e/0x130 [ 22.415173] SyS_pread64+0x95/0xb0 [ 22.415176] do_syscall_64+0x73/0x130 [ 22.415183] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 22.415184] RIP: 0033:0x7f2b7fbc0b73 [ 22.415185] RSP: 002b:7ffc134e1a58 EFLAGS: 0246 ORIG_RAX: 0011 [ 22.415186] RAX: ffda RBX: RCX: 7f2b7fbc0b73 [ 22.415186] RDX: 1000 RSI: 01639000 RDI: 0003 [ 22.415186] RBP: R08: R09: [ 22.415187] R10: R11: 0246 R12: 7ffc134e1b00 [ 22.415187] R13: 0002 R14: R15: [ 22.415188] Code: 21 d0 48 89 45 a0 0f 85 aa 03 00 00 41 0f b7 46 18 66 83 f8 03 0f 84 7e 02 00 00 66 83 f8 04 74 52 66 83 f8 01 0f 84 c8 02 00 00 <0f> 0b 48 c7 45 a0 fb ff ff ff 48 8b 5d d0 65 48 33 1c 25 28 00 [Test case] Run xfstests generic/446 test. [Potential regressions] Data corruption could be caused, though it is expected to be caused in such scenarions anyway. That should affecte direct I/O. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989144/+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 1978133] Re: System freeze followed by kernel panic or blank screen
I can no longer reproduce. Running Xubuntu 22.10. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1978133 Title: System freeze followed by kernel panic or blank screen Status in Linux: Incomplete Status in linux package in Ubuntu: Invalid Bug description: System keeps freezing in many different circumstances. I don't know how to reproduce this. Only happens on Ubuntu 22.04. Earlier versions were fine - tested Ubuntu impish and Debian bullseye. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 1593 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 12:22:34 2022 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0DC2CG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1978133/+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 1978133] Re: System freeze followed by kernel panic or blank screen
** Changed in: linux 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/1978133 Title: System freeze followed by kernel panic or blank screen Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: System keeps freezing in many different circumstances. I don't know how to reproduce this. Only happens on Ubuntu 22.04. Earlier versions were fine - tested Ubuntu impish and Debian bullseye. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 1593 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 12:22:34 2022 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0DC2CG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1978133/+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 1643922] Re: Network installer fails to detect network on AMD Overdrive (ARM64)
** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1643922 Title: Network installer fails to detect network on AMD Overdrive (ARM64) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Kernel 4.4.0-31.50 used in the newest version of the network installer for Xenial: http://ports.ubuntu.com/dists/xenial-proposed/main/installer- arm64/current/images/MANIFEST.udebs does not contain amd-xgbe module. In result the installer fails to initialize eth0 and can not continue. The lack of module has been addressed by LP#1597573, so that latest available udebs 4.4.0-47.68 now contain the relevant module, but the netboot image doesn't seem to have been regenerated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643922/+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 1995710] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1995710 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995710 Title: 22.10 doesn't boot on arm64 ThunderX2 system Status in linux package in Ubuntu: Incomplete Bug description: After upgrading my arm64 ThunderX2 Workstation (aka Gigabyte W281-T90) from Ubuntu 22.04 to 22.10 I've noticed that the new 5.19.0-23 kernel (linux-image-5.19.0-23-generic) makes the system hang at boot time with [ 82.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 27s! [fsck:3371] [ 82.957315] watchdog: BUG: soft lockup - CPU#20 stuck for 26s! [fsck:3373] [ 106.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 49s! [fsck:3371] [ 106.957315] watchdog: BUG: soft lockup - CPU#20 stuck for 48s! [fsck:3373] [ 115.201313] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 115.207401] rcu: 152-...0: (1 GPs behind) idle=1db/1/0x4000 softirq=287/288 fqs=4700 [ 130.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 71s! [fsck:3371] [ 130.957314] watchdog: BUG: soft lockup - CPU#20 stuck for 70s! [fsck:3373] [ 154.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 94s! [fsck:3371] [ 154.957314] watchdog: BUG: soft lockup - CPU#20 stuck for 93s! [fsck:3373] [ 178.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 116s! [fsck:3371] [ 178.957314] watchdog: BUG: soft lockup - CPU#20 stuck for 115s! [fsck:3373] messages in the console. Full log attached. Booting with: $ uname -a Linux tx2 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:04:57 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux makes everything work again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995710/+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 1995710] [NEW] 22.10 doesn't boot on arm64 ThunderX2 system
Public bug reported: After upgrading my arm64 ThunderX2 Workstation (aka Gigabyte W281-T90) from Ubuntu 22.04 to 22.10 I've noticed that the new 5.19.0-23 kernel (linux-image-5.19.0-23-generic) makes the system hang at boot time with [ 82.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 27s! [fsck:3371] [ 82.957315] watchdog: BUG: soft lockup - CPU#20 stuck for 26s! [fsck:3373] [ 106.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 49s! [fsck:3371] [ 106.957315] watchdog: BUG: soft lockup - CPU#20 stuck for 48s! [fsck:3373] [ 115.201313] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 115.207401] rcu: 152-...0: (1 GPs behind) idle=1db/1/0x4000 softirq=287/288 fqs=4700 [ 130.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 71s! [fsck:3371] [ 130.957314] watchdog: BUG: soft lockup - CPU#20 stuck for 70s! [fsck:3373] [ 154.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 94s! [fsck:3371] [ 154.957314] watchdog: BUG: soft lockup - CPU#20 stuck for 93s! [fsck:3373] [ 178.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 116s! [fsck:3371] [ 178.957314] watchdog: BUG: soft lockup - CPU#20 stuck for 115s! [fsck:3373] messages in the console. Full log attached. Booting with: $ uname -a Linux tx2 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:04:57 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux makes everything work again. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Full boot log" https://bugs.launchpad.net/bugs/1995710/+attachment/5629145/+files/boot_22_10.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995710 Title: 22.10 doesn't boot on arm64 ThunderX2 system Status in linux package in Ubuntu: New Bug description: After upgrading my arm64 ThunderX2 Workstation (aka Gigabyte W281-T90) from Ubuntu 22.04 to 22.10 I've noticed that the new 5.19.0-23 kernel (linux-image-5.19.0-23-generic) makes the system hang at boot time with [ 82.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 27s! [fsck:3371] [ 82.957315] watchdog: BUG: soft lockup - CPU#20 stuck for 26s! [fsck:3373] [ 106.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 49s! [fsck:3371] [ 106.957315] watchdog: BUG: soft lockup - CPU#20 stuck for 48s! [fsck:3373] [ 115.201313] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 115.207401] rcu: 152-...0: (1 GPs behind) idle=1db/1/0x4000 softirq=287/288 fqs=4700 [ 130.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 71s! [fsck:3371] [ 130.957314] watchdog: BUG: soft lockup - CPU#20 stuck for 70s! [fsck:3373] [ 154.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 94s! [fsck:3371] [ 154.957314] watchdog: BUG: soft lockup - CPU#20 stuck for 93s! [fsck:3373] [ 178.701311] watchdog: BUG: soft lockup - CPU#16 stuck for 116s! [fsck:3371] [ 178.957314] watchdog: BUG: soft lockup - CPU#20 stuck for 115s! [fsck:3373] messages in the console. Full log attached. Booting with: $ uname -a Linux tx2 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:04:57 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux makes everything work again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995710/+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 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)
Hi Vicamo, We had a detailed discussion on this. We would suggest to use the patch with below commit id d20ef656f994 net: wwan: t7xx: Add AP CLDMA instead of the earlier shared workaround for resolution of the suspend issue. This patch can be integrated without dependency with any other patch and this would fix the suspend resume issue. Please do not take the other three patches. This patch would not cause any other side effect. Thanks and Best Regards, Murali -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990700 Title: Fibocom WWAN FM350-GL suspend error (notebook not suspend) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Fibocom WWAN FM350-GL equipped platform fails to suspend. [Fix] Full t7xx driver is still under development and some of them have already accepted and merged in mainline kernel. The following commits are once in the mainline and are reverted in v6.0: d20ef656f994 net: wwan: t7xx: Add AP CLDMA 007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration 140424d90165 net: wwan: t7xx: PCIe reset rescan 87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump collection The first patch implemented the other AP-CLDMA, and with that applied, platforms in question may suspend and resume normally as every bits are in position. However, while these patches had been reverted for another revision that is still being worked on by the hardware vendor, a minimum, sauced patch is created to work-around this first to meet project schedules, and will be reverted and superseded with a final, mainline landing revision. [Test Case] Trigger suspend and there should be no more suspend errors from t7xx: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 [Where problems could occur] The t7xx driver is still incomplete and we're staging aforementioned 4 patches in internal experimental kernels for development use. [Other Info] This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0 are nominated for fix. == original bug report == Hi, I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module mtk_t7xx . Power management for this modem is bad. When the notebook goes to sleep/suspend, kernel module mtk_t7xx return an error: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 So power management failed to suspend: PM: Some devices failed to suspend, or early wake event detected And the notebook not suspend and wake up again. It must be this module, because if I remove the module first (modprobe -r), the laptop goes to sleep and wakes up normally. However, after reinserting the module, the modem no longer appears in the system. Expected state: sleep occurs when the device is put to sleep - including the modem. When you wake up, you will wake up, including activating the modem and logging into the operator's network. Description:Ubuntu 20.04.5 LTS Release:20.04 lspci -v: 58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01) Subsystem: Device 1cf8:3500 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 601e80 (64-bit, prefetchable) [size=32K] Memory at 5e80 (64-bit, non-prefetchable) [size=8M] Memory at 601e00 (64-bit, prefetchable) [size=8M] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [d0] MSI-X: Enable+ Count=34 Masked- Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [f8] Power Management version 3 Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 Capabilities: [108] Latency Tolerance Reporting Capabilities: [110] L1 PM Substates Capabilities: [200] Advanced Error
[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1
finish the sru template as we discussed -- 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/1995606 Title: Upgrade thermald to 2.5.1 Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: In Progress Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+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 1995606] Re: Upgrade thermald to 2.5.1
** Description changed: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. - 6. check if system would be throttled even the temperature is under the thrip-poits. + 6. check if system would be throttled even the temperature is under the trip-points. + + [ Where problems could occur ] -- 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/1995606 Title: Upgrade thermald to 2.5.1 Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: In Progress Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+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 1995606] Re: Upgrade thermald to 2.5.1
** Also affects: thermald (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: thermald (Ubuntu) Status: In Progress => Fix Released ** Changed in: thermald (Ubuntu Jammy) Status: New => In Progress -- 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/1995606 Title: Upgrade thermald to 2.5.1 Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: In Progress Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the thrip-poits. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+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 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
My report for Linux 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux [40840.919330] [ cut here ] [40840.919343] NETDEV WATCHDOG: enxf8e43b8c4f74 (ax88179_178a): transmit queue 0 timed out [40840.919402] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:477 dev_watchdog+0x277/0x280 [40840.919426] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp mei_hdcp intel_rapl_msr kvm_intel kvm binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi dell_laptop dell_smm_hwmon snd_soc_skl snd_ctl_led snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_hda_codec_generic rapl snd_compress ac97_bus snd_pcm_dmaengine rtsx_usb_ms snd_hda_intel snd_intel_dspcfg memstick snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep intel_cstate iwlmvm snd_pcm dell_wmi mac80211 snd_seq_midi ledtrig_audio snd_seq_midi_event libarc4 snd_rawmidi dell_smbios snd_seq iwlwifi snd_seq_device input_leds dcdbas snd_timer serio_raw sparse_keymap uvcvideo snd cfg80211 joydev dell_wmi_descriptor videobuf2_vmalloc mxm_wmi wmi_bmof videobuf2_memops soundcore videobuf2_v4l2 videobuf2_common videodev btusb btrtl btbcm mc btintel bluetooth [40840.919640] processor_thermal_device_pci_legacy ecdh_generic processor_thermal_device processor_thermal_rfim ecc processor_thermal_mbox processor_thermal_rapl intel_rapl_common mei_me hid_multitouch intel_pch_thermal mei intel_xhci_usb_role_switch intel_soc_dts_iosf int3403_thermal int3402_thermal int340x_thermal_zone int3400_thermal acpi_thermal_rel mac_hid dell_rbtn acpi_pad sch_fq_codel msr parport_pc ppdev lp parport ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables autofs4 ax88179_178a rtsx_usb_sdmmc usbnet mii usbhid rtsx_usb i915 i2c_algo_bit ttm hid_generic drm_kms_helper syscopyarea crct10dif_pclmul sysfillrect sysimgblt crc32_pclmul fb_sys_fops ghash_clmulni_intel cec aesni_intel rc_core crypto_simd i2c_i801 cryptd psmouse i2c_smbus r8169 i2c_hid_acpi i2c_hid drm realtek intel_lpss_pci ahci intel_lpss libahci xhci_pci idma64 xhci_pci_renesas hid pinctrl_sunrisepoint video wmi [40840.919836] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G I 5.15.0-52-generic #58-Ubuntu [40840.919846] Hardware name: Dell Inc. Inspiron 7560/07T996, BIOS 1.15.0 07/23/2021 [40840.919851] RIP: 0010:dev_watchdog+0x277/0x280 [40840.919866] Code: eb 97 48 8b 5d d0 c6 05 44 33 69 01 01 48 89 df e8 9e 67 f9 ff 44 89 e1 48 89 de 48 c7 c7 18 59 cd b7 48 89 c2 e8 0a c3 19 00 <0f> 0b eb 80 e9 eb 2d 23 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 [40840.919873] RSP: 0018:a1a6c0194e70 EFLAGS: 00010282 [40840.919883] RAX: RBX: 92d54328c000 RCX: 0027 [40840.919889] RDX: 92d8af5a0588 RSI: 0001 RDI: 92d8af5a0580 [40840.919895] RBP: a1a6c0194ea8 R08: 0003 R09: fffdaa88 [40840.919900] R10: 000a R11: 0001 R12: [40840.919905] R13: 92d54140de80 R14: 0001 R15: 92d54328c4c0 [40840.919911] FS: () GS:92d8af58() knlGS: [40840.919918] CS: 0010 DS: ES: CR0: 80050033 [40840.919924] CR2: 7f2f54bb5000 CR3: 0002bde10005 CR4: 003706e0 [40840.919930] Call Trace: [40840.919935] [40840.919943] ? pfifo_fast_enqueue+0x160/0x160 [40840.919958] call_timer_fn+0x29/0x120 [40840.919970] __run_timers.part.0+0x1e3/0x270 [40840.919979] ? ktime_get+0x43/0xc0 [40840.919991] ? lapic_next_deadline+0x2c/0x40 [40840.920002] ? clockevents_program_event+0xaa/0x130 [40840.920018] run_timer_softirq+0x2a/0x60 [40840.920026] __do_softirq+0xd6/0x2e7 [40840.920039] irq_exit_rcu+0x94/0xc0 [40840.920052] sysvec_apic_timer_interrupt+0x80/0x90 [40840.920064] [40840.920068] [40840.920072] asm_sysvec_apic_timer_interrupt+0x1a/0x20 [40840.920080] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [40840.920093] Code: 3d 84 e9 f9 48 e8 47 d3 68 ff 49 89 c7 0f 1f 44 00 00 31 ff e8 88 e0 68 ff 80 7d d0 00 0f 85 61 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 6d 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e7 03 00 00 [40840.920100] RSP: 0018:a1a6c00efe28 EFLAGS: 0246 [40840.920107] RAX: 92d8af5b0b80 RBX: c1a6bfd8 RCX: [40840.920113] RDX: RSI: 0004 RDI: [40840.920117] RBP: a1a6c00efe78 R08: 2525047ce9dd R09: 004c4b40 [40840.920122] R10: 0009 R11: 071c71c71c71c71c R12: b86d3ee0 [40840.920127] R13: 0006 R14: 0006 R15: 2525047ce9dd [40840.920140] ? cpuidle_enter_state+0xc8/0x620 [40840.920154] cpuidle_enter+0x2e/0x50 [40840.920165] cpuidle_idle_call+0x142/0x1e0 [40840.920177] do_idle+0x83/0xf0 [40840.920185]
[Kernel-packages] [Bug 1989713] Re: Old start4.elf / fixup4.dat in 22.04
Marking linux-firmware-raspi2 invalid for now; will be used if we decide to backport to focal. Currently prepping an upload for ppa:waveform/firmware with a test updated firmware. If that works well, will upload to lunar then start SRU to kinetic and jammy. ** Also affects: linux-firmware-raspi2 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi2 (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Also affects: linux-raspi (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux-firmware-raspi (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Also affects: linux-firmware-raspi2 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-firmware-raspi2 (Ubuntu Lunar) Status: Confirmed => Invalid ** Changed in: linux-firmware-raspi2 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-firmware-raspi2 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-firmware-raspi (Ubuntu Kinetic) Status: New => Confirmed ** Changed in: linux-firmware-raspi (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-firmware-raspi (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware-raspi (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux-firmware-raspi (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux-firmware-raspi (Ubuntu Lunar) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: linux-firmware-raspi (Ubuntu Jammy) Milestone: None => ubuntu-22.04.2 ** Changed in: linux-firmware-raspi (Ubuntu Lunar) Milestone: None => ubuntu-23.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1989713 Title: Old start4.elf / fixup4.dat in 22.04 Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-firmware-raspi2 package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in linux-firmware-raspi source package in Jammy: Confirmed Status in linux-firmware-raspi2 source package in Jammy: Invalid Status in linux-raspi source package in Jammy: Invalid Status in linux-firmware-raspi source package in Kinetic: Confirmed Status in linux-firmware-raspi2 source package in Kinetic: Invalid Status in linux-raspi source package in Kinetic: Invalid Status in linux-firmware-raspi source package in Lunar: Confirmed Status in linux-firmware-raspi2 source package in Lunar: Invalid Status in linux-raspi source package in Lunar: Invalid Bug description: Hi there, there is the issue connected with "Initramfs unpacking failed: Decoding failed" error during Ubuntu boot. See https://github.com/raspberrypi/firmware/issues/1746 and https://github.com/raspberrypi/firmware/issues/1731. The Raspberry Pi have the update for start4.elf / fixup4.dat with fix it. Could you please include update for these files in new ubuntu release ASAP? Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi/+bug/1989713/+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 1958416] Re: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64
** Description changed: - ubuntu_boot log_check fails with: WARNING: CPU: 34 PID: 8648 at - /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 - report_addr+0x33/0x90 + [Impact] + Small SWIOTLB might cause DMA failures during High IO on GCP instances using SEV. + + [Test case] + Boot n2d-standard-2 or n2d-standard-64 instances on GCP, issue a lot of IO, and look for DMA overflow or full swiotlb messages on dmesg. + + [Potential regression] + Boot failures should not be discarded when SWIOTLB cannot be allocated. + + + -- + + + ubuntu_boot log_check fails with: WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 From the serial console: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938685] [ cut here ] Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] Modules linked in: ip6table_filter ip6_tables iptable_filter bpfilter nls_iso8859_1 input_leds pvpanic serio_raw mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper psmouse i2c_piix4 gve Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] CPU: 34 PID: 8648 Comm: apt-check Not tainted 5.4.0-1060-gcp #64~18.04.1-Ubuntu Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938714] RIP: 0010:report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] Code: 48 83 ec 08 48 8b 87 30 02 00 00 48 89 75 f8 48 85 c0 74 26 4c 8b 00 b8 fe ff ff ff 49 39 c0 76 0d 80 3d 47 67 b2 01 00 74 2e <0f> 0b c9 c3 48 83 bf 40 02 00 00 00 75 e9 eb f0 80 3d 2f 67 b2 01 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] RSP: 0018:bd77cf99f4e0 EFLAGS: 00010282 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RAX: RBX: 9773f8b960b0 RCX: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RDX: RSI: 9753ff897448 RDI: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] RBP: bd77cf99f4e8 R08: 0305 R09: 0022 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] R10: 0016dfee R11: bd77cf99f218 R12: 0002 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938720] R13: 9753abfe9000 R14: 0001 R15: 0100 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] FS: 7f55bb523740() GS:9753ff88() knlGS: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] CS: 0010 DS: ES: CR0: 80050033 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938724] CR2: 7f55b41d6000 CR3: 801f6be28000 CR4: 00340ee0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938726] Call Trace: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938730] dma_direct_map_page+0xe2/0xf0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938731] dma_direct_map_sg+0x6c/0xc0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938735] nvme_queue_rq+0x6fb/0xbd0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938738] __blk_mq_try_issue_directly+0x139/0x200 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938741] ? mempool_free_slab+0x1/0x20 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938743] blk_mq_request_issue_directly+0x4b/0xe0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938744] blk_mq_try_issue_list_directly+0x46/0xb0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938746] blk_mq_sched_insert_requests+0xb7/0x100 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938747]
[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1
** Description changed: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: * Run stress-ng, and observe the temperature/frequency/power with s-tui - - Temperatures should stay just below trip values - - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) + - Temperatures should stay just below trip values + - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) * check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - - (TODO: What are the concrete steps to check this?) + - this depends on if acpi_thermal_rel exist. + - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" + could be landed in etc/thermald/. + - run thermald with --loglevel=debug, and compare the log with xml.auto file. + check if the configuration could be parsed correctly. * check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - - (TODO: How do we check this) + - run thermald with --loglevel=debug, and compare the log with xml files. + - if parsed correctly, the configurations from XML files would appear in the log. + * Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - - rapl.sh - - intel_pstate.sh - - powerclamp.sh - - processor.sh + - rapl.sh + - intel_pstate.sh + - powerclamp.sh + - processor.sh * check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. * check if system would be throttled even the temperature is under the thrip-poits. ** Description changed: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: - * Run stress-ng, and observe the temperature/frequency/power with s-tui + 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) - * check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - - this depends on if acpi_thermal_rel exist. - - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" - could be landed in etc/thermald/. - - run thermald with --loglevel=debug, and compare the log with xml.auto file. - check if the configuration could be parsed correctly. - * check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - - run thermald with --loglevel=debug, and compare the log with xml files. - - if parsed correctly, the configurations from XML files would appear in the log. + 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. + - this depends on if acpi_thermal_rel exist. + - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" + could be landed in etc/thermald/. + - if not, the user-defined xml could be created, then jump to (3). + - run thermald with --loglevel=debug, and compare the log with xml.auto file. + check if the configuration could be parsed correctly. + 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. + - run thermald with --loglevel=debug, and compare the log with xml files. + - if parsed correctly, the configurations from XML files would appear in the log. - * Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. + 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh - * check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. - * check if system would be throttled even the temperature is under the thrip-poits. + 5. check if the
[Kernel-packages] [Bug 1995495] Re: rt2800usb module absent from latest Ububtu for Raspberry Pi server versions
That module is provided by the modules extra package: $ sudo apt install linux-modules-extra-raspi $ modinfo rt2800usb | head -10 filename: /lib/modules/5.15.0-1015-raspi/kernel/drivers/net/wireless/ralink/rt2x00/rt2800usb.ko license:GPL firmware: rt2870.bin description:Ralink RT2800 USB Wireless LAN driver. version:2.3.0 author: http://rt2x00.serialmonkey.com srcversion: 3D5448FED7C97CFAE9C26D2 alias: usb:vF201p5370d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v177Fp0254d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v083ApF511d*dc*dsc*dp*ic*isc*ip*in* ** Changed in: linux-meta-raspi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1995495 Title: rt2800usb module absent from latest Ububtu for Raspberry Pi server versions Status in linux-meta-raspi package in Ubuntu: Invalid Bug description: RT2800USB module is supposed to be part of the kernel since version 3. However, latest versions of Ubuntu for Raspberry Pi server don't have this package installed, which makes a large quantity of USB dongles not load on it. Ubuntu Server 22.04.1 LTS kernel is 5.15.0-1017-raspi and architecture is aarch64 Running "find /lib/modules/$(uname -r) -type f -name 'rt2800usb.ko'" returns nothing, when in other ubuntu distributions like Desktop on PC it points to the right driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/1995495/+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 1995606] Re: Upgrade thermald to 2.5.1
** Description changed: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. - Currently, just use stress-ng and observe the temperature/frequency/power manually(e.g. s-tui). - The whole test cases are the followings and run on the platforms, RPL/ADL/TGL/CML/CFL/KBL. - 1. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - 2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - 3. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - a. rapl.sh - b. intel_pstate.sh - c. powerclamp.sh - d. processor.sh + [Test case] + For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: - 4. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. - 5. check if system would be throttled even the temperature is under the thrip-poits. + * Run stress-ng, and observe the temperature/frequency/power with s-tui + - Temperatures should stay just below trip values + - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) + * check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. + - (TODO: What are the concrete steps to check this?) + * check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. + - (TODO: How do we check this) + * Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. + - rapl.sh + - intel_pstate.sh + - powerclamp.sh + - processor.sh + * check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. + * check if system would be throttled even the temperature is under the thrip-poits. -- 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/1995606 Title: Upgrade thermald to 2.5.1 Status in thermald package in Ubuntu: In Progress Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: * Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) * check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - (TODO: What are the concrete steps to check this?) * check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - (TODO: How do we check this) * Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh * check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. * check if system would be throttled even the temperature is under the thrip-poits. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+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 1995684] [NEW] Fail to handle IRQ data in hv_pci and lead to attach 8 VF to VM fail
Public bug reported: [Impact] When creating 8 accelerated network interfaces on Azure and attaching them to a VM from kernel message, it fails to handle IRQ data in hv_pci as below: [ 15.533530] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.539856] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.546261] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.552781] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.560177] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.566631] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 And 2 VFs are consistently missing, only 6 seem to be working [Fix] The fix was merged to upstream hyperv tree: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] 1. Create 8 NICs in azure with accelerated networking enabled 2. Launch a VM with all 8 attached 3. Check the output from VM [Where problems could occur] The patch is to use the correct type for the variables and reviewed by upstream There shouldn't be any problem ** Affects: linux (Ubuntu) Importance: High Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995684 Title: Fail to handle IRQ data in hv_pci and lead to attach 8 VF to VM fail Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: [Impact] When creating 8 accelerated network interfaces on Azure and attaching them to a VM from kernel message, it fails to handle IRQ data in hv_pci as below: [ 15.533530] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.539856] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.546261] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.552781] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.560177] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.566631] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 And 2 VFs are consistently missing, only 6 seem to be working [Fix] The fix was merged to upstream hyperv tree: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] 1. Create 8 NICs in azure with accelerated networking enabled 2. Launch a VM with all 8 attached 3. Check the output from VM [Where problems could occur] The patch is to use the correct type for the variables and reviewed by upstream There shouldn't be any problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995684/+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
