Several segmentation faults during upgrade

[zemanek]

Hello,

during every upgrade I see several segmentation faults like in this extract:

Code Select Expand

[39/104] Installing brotli-1.1.0,1...
[39/104] Extracting brotli-1.1.0,1: .......... done
Segmentation fault
[40/104] Upgrading nspr from 4.35 to 4.36...
[40/104] Extracting nspr-4.36: .......... done
Segmentation fault
[41/104] Upgrading py311-numexpr from 2.10.1 to 2.10.2...
[41/104] Extracting py311-numexpr-2.10.2: .......... done
[42/104] Upgrading libltdl from 2.4.7 to 2.5.4...
[42/104] Extracting libltdl-2.5.4: .......... done
Segmentation fault
[43/104] Upgrading oniguruma from 6.9.9 to 6.9.10...
[43/104] Extracting oniguruma-6.9.10: .......... done
Segmentation fault
[44/104] Upgrading php82-session from 8.2.23 to 8.2.27...
[44/104] Extracting php82-session-8.2.27: .......... done
Should I be worried? Maybe not related but during upgrade to the last 24.x version the upgrade hung during this phase. Subsequent upgrades finished though.

[franco]

> Should I be worried?

Yes, check dmesg output.


Cheers,
Franco

[zemanek]

Code Select Expand

pid 86448 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 98965 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 12770 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 22219 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 31720 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 38510 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 62016 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 75000 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 88570 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 97221 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 7282 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 17994 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 32113 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 31038 (pkg-static), jid 0, uid 0, was killed: failed to reclaim memory
pid 8123 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 16784 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 36473 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 91092 (pkg-static), jid 0, uid 0, was killed: failed to reclaim memory


[Patrick M. Hausen]

Run memtest, check temperatures, check power supply ... almost certainly hardware related issues.

If you are running a fairly modern CPU did you install the microcode update plugin matching your architecture (AMD or Intel)?

[franco]

> was killed: failed to reclaim memory

Looks like RAM was depleted and/or SWAP exhausted.

[Seimus]

Basically what above was said + please provide what HW config do you have?

Regards,
S.

[zemanek]

It's a VM. I do have plugin installed, but

Code Select Expand

CPU microcode: no matching update found
CPU: AMD EPYC 7571 (2199.99-MHz K8-class CPU)

Will try with more RAM.

[franco]

You don't need the microcode in the VM.


Cheers,
Franco

[zemanek]

I added 1GB RAM and removed the microcode plugin. During removal again Segmentation fault and dmesg:

Code Select Expand

pid 61978 (ld-elf32.so.1), jid 0, uid 0: exited on signal 11 (no core dump - bad address)


[Patrick M. Hausen]

So this is a VM? Would have helped if you had stated that in the first post.

Did you install the current microcode update on the hypervisor host? What hypervisor are you using?

[zemanek]

Sorry, I do not have control over the hypervisor. It's a cloud VM.

[Patrick M. Hausen]

Then open a support ticket with the cloud vendor. Obviously at least with the current settings they are not 100% compatible with FreeBSD.

[franco]

How much RAM does it have now, maybe that's a better way to start?

[zemanek]

Now it has 2GB, Lobby dashboard says 31% utilization.

[franco]

The installer minimum requirement is 3 GB (although it can be ignored at one's own peril). 4 GB doesn't hurt, especially if you're doing something with it after installation.


Cheers,
Franco