[Bug 250361] Kernel trap #9 in sys_semop

2020-10-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 Ed Maste changed: What|Removed |Added Assignee|b...@freebsd.org|k...@freebsd.org -- You are receiving

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 Konstantin Belousov changed: What|Removed |Added Status|New |In Progress -- You are rece

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #14 from commit-h...@freebsd.org --- A commit references this bug: Author: kib Date: Thu Oct 22 09:28:12 UTC 2020 New revision: 366932 URL: https://svnweb.freebsd.org/changeset/base/366932 Log: sysv_sem: semusz depends on sem

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #13 from Konstantin Belousov --- (In reply to Olef from comment #12) Yes increasing kern.ipc.semusz would also help, but you need to carefully calculate how large to set it. For instance, it is arch-dependent. -- You are rece

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #12 from Olef --- Hi, So, in 12.2 RC2 I indeed still got the kernel panics after initial upgrade. After patching the kernel I've not received this anymore in the last 3 days so all seems to work fine. Thanks for your help! PS

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #11 from Konstantin Belousov --- (In reply to Olef from comment #10) The issue that patch fixes is in HEAD, stable/12, and all 12.x releases. But since it is memory corruption, specific manifestation of it can be arbitrary, for

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #10 from Olef --- I will, would it also manifest itself in 12.2 or shall I create a new VM ? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bug

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #9 from Konstantin Belousov --- (In reply to Olef from comment #8) I am quite sure that there is the issue I described in the review, and since it is a memory corruption kind of bug, it is quite specific to the kernel/machine/ l

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #8 from Olef --- Hi, Thanks, though I did not receive the panic this morning after upgrading to 12.2, will check again tomorrow. If this fault still persists I'll patch in your suggestion. I needed to increase SEMUME as some p

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #7 from Konstantin Belousov --- I suspect I figured it out, please try the patch from https://reviews.freebsd.org/D26826 That said, I am curious why do you need to adjust semume. -- You are receiving this mail because: You ar

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #6 from Olef --- I can reproduce it with relative ease, i'm on 7 vmcore files so far. Updating now to 12.2-RC2 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #5 from Konstantin Belousov --- You can try to do something with e.g. ktrace, but this would be hard because system panics and records are not written. Might be sync NFS mount from other machine help, but I do not expect it. S

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #4 from Olef --- Fair enough. Is there a way to find out what the calling process was actually doing to cause this? kgdb only gives me the kernel fault, but doesn't give me anything on the state of the calling process. -- You

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #3 from Konstantin Belousov --- Without reproducer I cannot say anything. Perhaps try on 12.2, there were a fix that might be relevant, r358242 MFC of r357984. -- You are receiving this mail because: You are the assignee for

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 --- Comment #2 from Olef --- Hi, I've tried to create something that replicates the behavior, but unfortunately I dont have any luck with it... What happens internally is that a main process forks off 50 ish smaller processes that need to

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 Mark Linimon changed: What|Removed |Added Keywords||panic -- You are receiving this ma

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 Konstantin Belousov changed: What|Removed |Added CC||k...@freebsd.org --- Comment

[Bug 250361] Kernel trap #9 in sys_semop

2020-10-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250361 Bug ID: 250361 Summary: Kernel trap #9 in sys_semop Product: Base System Version: 12.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects