-
Notifications
You must be signed in to change notification settings - Fork 35
BUG at mm/uksm.c in kernel logs #44
Comments
It may be related to this bug because the proposed fix is still not included in the current release. |
The proposed fix seems to be partially obfuscated by the MD formatting. I guess the suggested patch is like this one I'm going to attach, that I'm going to test. uksm-check-scan-entry-return-value-get_next_rmap_item.patch.txt |
Even with that patch I get the same reports, just changed (rightly because of the introduction of the new code) the line of report, now at: kernel: kernel BUG at mm/uksm.c:3326! |
Also have the similar problem with uksm on a 5.2.21 kernel: |
This is still present in 5.4.5.
|
I've got two of them in a row while taking part in a webinar on zoom.us with Firefox nightly and some of my processes including firefox and htop freezes.
|
Hi. while trying uksm on a 5.0.x kernel, and while doing some intensive I/O on a high loaded host I noticed that sometimes in kernel logs I obtain the following error:
kernel: kernel BUG at mm/uksm.c:3322!
kernel: invalid opcode: 0000 [#1] PREEMPT SMP PTI
kernel: CPU: 1 PID: 218 Comm: uksmd Tainted: P IO 5.0.10-1 #1
...
kernel: RIP: 0010:scan_vma_one_page+0xb52/0x1350
...
kernel: ? sleep_millisecs_store+0x80/0x80
kernel: ? sradix_tree_next+0xcb/0x150
kernel: uksm_do_scan+0x143/0x2170
kernel: ? __next_timer_interrupt+0xc0/0xc0
kernel: ? uksm_do_scan+0x2170/0x2170
kernel: uksm_scan_thread+0x13c/0x170
kernel: ? __kthread_parkme+0x4c/0x70
kernel: kthread+0x113/0x130
kernel: ? kthread_create_on_node+0x60/0x60
kernel: ret_from_fork+0x35/0x40
Poking around into older log with journalctl, I found that this error was sometimes there (also on different hardware), at least since kernel 4.20.3. The lines in mm/uksm.c corresponding to the error above is always the following one:
BUG_ON(addr > slot->vma->vm_end || addr < slot->vma->vm_start);
what exactly this could be related to? Apparently seems something related to transfers out of boundaries?
The text was updated successfully, but these errors were encountered: