[Bug 1975501] [NEW] bfq_deactivate_entity: NULL pointer dereference
Public bug reported: Hello. We meet a kernel panic with next trace: bfq_insert+0x5c/0x70 [bfq] __bfq_deactivate_entity+0xe7/0x1b0 [bfq] bfq_deactivate_entity+0x5d/0xd0 [bfq] bfq_del_bfqq_busy+0xac/0x150 [bfq] __bfq_bfqq_expire+0x64/0xd0 [bfq] bfq_bfqq_expire+0x331/0x930 [bfq] ? try_to_wake_up+0x235/0x5f0 ? bfq_dispatch_request+0xf70/0xf70 [bfq] bfq_idle_slice_timer+0x6d/0xc0 [bfq] __hrtimer_run_queues+0x10f/0x280 hrtimer_interrupt+0xe7/0x230 smp_apic_timer_interrupt+0x6f/0x130 apic_timer_interrupt+0xf/0x20 After little research i found out that bug was reported by Fedora and openSUSE community earlier. https://bugzilla.redhat.com/show_bug.cgi?id=2022819 https://bugzilla.opensuse.org/show_bug.cgi?id=1192714 And patch for this bug already exist https://lore.kernel.org/all/20220401102325.17617-1-j...@suse.cz/ Since there are no similar reports in the Ubuntu community, I decided to make this report. Full dmesg log in attachments. Also have a crash dump file, can attach that file if it necessary. Environment: Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic kernel: 5.4.0-110-generic #124~18.04.1-Ubuntu ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "dmesg_bfq_deactivate_entity" https://bugs.launchpad.net/bugs/1975501/+attachment/5592301/+files/dmesg_bfq_deactivate_entity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975501 Title: bfq_deactivate_entity: NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1975501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949247] Re: kernel: BUG: unable to handle page fault for address (5.4.0-89)
Met same problem with kernel version 5.4.0-81 I have kdump file for that bug, can attach that file if necessary. # lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 dmesg log BUG: unable to handle page fault for address: 003e3898 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI CPU: 12 PID: 17994 Comm: libvirtd Kdump: loaded Tainted: G OE 5.4.0-81-generic #91~18.04.1-Ubuntu Hardware name: Supermicro Super Server/X11DDW-L, BIOS 3.3 02/21/2020 RIP: 0010:native_queued_spin_lock_slowpath+0x192/0x1f0 Code: 8b 02 48 85 c0 74 f6 48 89 c6 eb e5 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 c0 ba 02 00 48 03 04 f5 20 29 64 af <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 74 f7 48 8b 02 RSP: 0018:b11c23af3b88 EFLAGS: 00010202 RAX: 003e3898 RBX: ac60 RCX: 0034 RDX: 9ca100d2bac0 RSI: 3f68 RDI: 9ca0f70c52b0 RBP: b11c23af3b88 R08: 0034 R09: 00031160 R10: 9ca1bffd5000 R11: R12: 9ca0f70c52b0 R13: 0010 R14: b11c23af3cf0 R15: 9cd0f4401a00 FS: 7f939957e700() GS:9ca100d0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 003e3898 CR3: 005de5282002 CR4: 007626e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 Call Trace: _raw_spin_lock+0x1f/0x30 __swap_duplicate+0x5a/0x1a0 swap_duplicate+0x1a/0x40 copy_page_range+0x938/0xdb0 dup_mm+0x3f5/0x5c0 copy_process+0x1b20/0x1b40 _do_fork+0x76/0x370 ? handle_mm_fault+0xcb/0x210 __x64_sys_clone+0x84/0xb0 do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f93a724f8ec Code: c5 45 85 f6 0f 85 b4 01 00 00 64 4c 8b 04 25 10 00 00 00 31 d2 4d 8d 90 d0 02 00 00 31 f6 bf 11 00 20 01 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 f0 00 00 00 85 c0 41 89 c4 0f 85 fd 00 00 RSP: 002b:7f939957d340 EFLAGS: 0246 ORIG_RAX: 0038 RAX: ffda RBX: 7f939957d340 RCX: 7f93a724f8ec RDX: RSI: RDI: 01200011 RBP: 7f939957d430 R08: 7f939957e700 R09: R10: 7f939957e9d0 R11: 0246 R12: R13: 0020 R14: 0001 R15: 7f939957d680 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949247 Title: kernel: BUG: unable to handle page fault for address (5.4.0-89) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952193] Re: NULL pointer dereference at _mod_memcg_state+0x14/0xb0
** Description changed: Hello. We meet a randomly host kernel panics with same RIP and "BUG: kernel NULL pointer dereference". - At current time affected kernel versions was from 5.4.0-53 to 5.4.0-84. + At current time affected kernel versions was from 5.4.0-53 to 5.4.0-87. For now i have a dmesg log and crash file, but no clue where what to do next. Environment: - Distributor ID: Ubuntu - Description:Ubuntu 18.04.6 LTS - Release:18.04 - Codename: bionic - + Distributor ID: Ubuntu + Description:Ubuntu 18.04.6 LTS + Release:18.04 + Codename: bionic Crash report - KERNEL: usr/lib/debug/boot/vmlinux-5.4.0-84-generic - DUMPFILE: dump.202111240900 [PARTIAL DUMP] - CPUS: 24 - DATE: Wed Nov 24 09:00:22 2021 - UPTIME: 15 days, 23:17:07 + KERNEL: usr/lib/debug/boot/vmlinux-5.4.0-84-generic + DUMPFILE: dump.202111240900 [PARTIAL DUMP] + CPUS: 24 + DATE: Wed Nov 24 09:00:22 2021 + UPTIME: 15 days, 23:17:07 LOAD AVERAGE: 46.41, 37.67, 30.39 -TASKS: 3071 - NODENAME: cmp20 - RELEASE: 5.4.0-84-generic - VERSION: #94~18.04.1-Ubuntu SMP Thu Aug 26 23:17:46 UTC 2021 - MACHINE: x86_64 (2299 Mhz) - MEMORY: 255.9 GB -PANIC: "Oops: [#1] SMP PTI" (check log for details) - PID: 2239917 - COMMAND: "CPU 0/KVM" - TASK: 9bbd9662 [THREAD_INFO: 9bbd9662] - CPU: 14 -STATE: TASK_RUNNING (PANIC) + TASKS: 3071 + NODENAME: cmp20 + RELEASE: 5.4.0-84-generic + VERSION: #94~18.04.1-Ubuntu SMP Thu Aug 26 23:17:46 UTC 2021 + MACHINE: x86_64 (2299 Mhz) + MEMORY: 255.9 GB + PANIC: "Oops: [#1] SMP PTI" (check log for details) + PID: 2239917 + COMMAND: "CPU 0/KVM" + TASK: 9bbd9662 [THREAD_INFO: 9bbd9662] + CPU: 14 + STATE: TASK_RUNNING (PANIC) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952193 Title: NULL pointer dereference at _mod_memcg_state+0x14/0xb0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1952193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952193] Re: NULL pointer dereference at _mod_memcg_state+0x14/0xb0
Link to crash dump https://drive.google.com/file/d/14FRxK0RKi7HFRYdkQRhyImnS7ZfNuVla/view -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952193 Title: NULL pointer dereference at _mod_memcg_state+0x14/0xb0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1952193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952193] [NEW] NULL pointer dereference at _mod_memcg_state+0x14/0xb0
Public bug reported: Hello. We meet a randomly host kernel panics with same RIP and "BUG: kernel NULL pointer dereference". At current time affected kernel versions was from 5.4.0-53 to 5.4.0-84. For now i have a dmesg log and crash file, but no clue where what to do next. Environment: Distributor ID: Ubuntu Description:Ubuntu 18.04.6 LTS Release:18.04 Codename: bionic Crash report KERNEL: usr/lib/debug/boot/vmlinux-5.4.0-84-generic DUMPFILE: dump.202111240900 [PARTIAL DUMP] CPUS: 24 DATE: Wed Nov 24 09:00:22 2021 UPTIME: 15 days, 23:17:07 LOAD AVERAGE: 46.41, 37.67, 30.39 TASKS: 3071 NODENAME: cmp20 RELEASE: 5.4.0-84-generic VERSION: #94~18.04.1-Ubuntu SMP Thu Aug 26 23:17:46 UTC 2021 MACHINE: x86_64 (2299 Mhz) MEMORY: 255.9 GB PANIC: "Oops: [#1] SMP PTI" (check log for details) PID: 2239917 COMMAND: "CPU 0/KVM" TASK: 9bbd9662 [THREAD_INFO: 9bbd9662] CPU: 14 STATE: TASK_RUNNING (PANIC) ** Affects: linux-meta-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "dmesg.202111240900" https://bugs.launchpad.net/bugs/1952193/+attachment/5543242/+files/dmesg.202111240900 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952193 Title: NULL pointer dereference at _mod_memcg_state+0x14/0xb0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1952193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935051] Re: systemd pid 1 memory leak
@brian-murray Hi. Tested that build, all seems fine, still no memory leak. # apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.13 Candidate: 245.4-4ubuntu3.13 Version table: *** 245.4-4ubuntu3.13 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status Test was performed like i was describe at original post, i run chef- client and it start checking for all .service and .timers units, and it cause memory leak, after upgrade no mem leak. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935051 Title: systemd pid 1 memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935051] Re: systemd pid 1 memory leak
Yep, i checked on friday and no memory leak since then. Version of package and source repository: # apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.12 Candidate: 245.4-4ubuntu3.12 Version table: *** 245.4-4ubuntu3.12 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages Test was performed like i was describe at original post, i run chef- client and it start checking for all .service and .timers units, and it cause memory leak, after upgrade no mem leak. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935051 Title: systemd pid 1 memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935051] Re: systemd pid 1 memory leak
Thanks for answering! Yep, that build fixed leak for me. # apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.12~202108090622~ubuntu20.04.1 This build will be used for official systemd-245.4-4ubuntu3.12 package ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935051 Title: systemd pid 1 memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935051] Re: systemd pid 1 memory leak
Just checked again, bug still exist for latest systemd package on focal. # apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935051 Title: systemd pid 1 memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935051] Re: systemd pid 1 memory leak
** Attachment added: "pmap_pid1_focal" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+attachment/5509911/+files/pmap_pid1_focal ** Description changed: Hi everybody. We've meet a memory leak of pid1 process on the focal release. When we launch chef-client, several systemd .service and .timers are checked for state. Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on xenial and bionic releases. I straced pid1 when that leak happen and found brk call. On pmap view of pid 1 it's anon memory grow on the same address and all marked as dirty. + All that leak memory can be freed by calling systemctl daemon-reexec. Searching in systemd github repo i found this commit https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d - it may be related to this leak. - + Environment: - Distributor ID: Ubuntu - Description:Ubuntu 20.04.2 LTS - Release:20.04 - Codename: focal - Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 + Distributor ID: Ubuntu + Description:Ubuntu 20.04.2 LTS + Release:20.04 + Codename: focal + Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 Package: - systemd: - Installed: 245.4-4ubuntu3.7 + systemd: + Installed: 245.4-4ubuntu3.7 ** Tags added: pid1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935051 Title: systemd pid 1 memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935051] [NEW] systemd pid 1 memory leak
Public bug reported: Hi everybody. We've meet a memory leak of pid1 process on the focal release. When we launch chef-client, several systemd .service and .timers are checked for state. Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on xenial and bionic releases. I straced pid1 when that leak happen and found brk call. On pmap view of pid 1 it's anon memory grow on the same address and all marked as dirty. All that leak memory can be freed by calling systemctl daemon-reexec. Searching in systemd github repo i found this commit https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d - it may be related to this leak. Environment: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 Package: systemd: Installed: 245.4-4ubuntu3.7 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: pid1 systemd ** Attachment added: "pid1 strace focal" https://bugs.launchpad.net/bugs/1935051/+attachment/5509910/+files/pid1_strace_focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935051 Title: systemd pid 1 memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
