Date: Sat, 04 Apr 2026 15:15:46 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 294039] databases/postgresql14-server: jemalloc crashes triggered by autovacuum Message-ID: <bug-294039-227-ZYnmsr44IP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-294039-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294039 --- Comment #10 from Peter Much <pmc@citylink.dinoex.sub.org> --- (In reply to Mark Johnston from comment #9) Bad news, Mark. It took almost a day to crash, but it's all the same now: Apr 4 09:28:22 <kern.crit> edge kernel: [48669] PMc: KERNEL ALERT page should be zeroed, but will not Apr 4 11:42:28 <kern.crit> edge kernel: [56716] PMc: KERNEL INFO page would not be zeroed, but will Apr 4 11:48:21 <kern.crit> edge kernel: [57068] PMc: KERNEL ALERT page should be zeroed, but will not Apr 4 14:28:01 <kern.crit> edge kernel: [66648] PMc: KERNEL ALERT page should be zeroed, but will not Apr 4 14:28:01 <kern.info> edge kernel: [66648] pid 34089 (postgres), jid 5, uid 770: exited on signal 11 (core dumped) Sadly, I forgot to put another printf onto Your patch to see if it does anything. This is an ugly issue and I am quite tired after two months of hunting red herrings. It might be helpful to know what specifically are the "rare situations" where this eFix should do anything. Recap: what I found in the postgres coredumps is a memory area used by jemalloc for some tree structure, maybe 4 or 8 MB in total, and it is sparsely populated by pointer structures just as the sourcecode describes them. But within this area are one or two blocks (of exactly 4kB each) which contain some almost random data from an unknown source. And when the pointer is fetched out of this area and then utilized, it results in either SIGSEGV or SIGBUS. I do not grok how this comes to be, but it is certainly not good. I would have agreed that it might be a rare hardware flaw in the memory controller circuitry, but with the PR reporter here showing the same backtrace, that can be ruled out. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-294039-227-ZYnmsr44IP>