segfault at boot (dhcpd bug?)

1st Official Post

    I get 2 segfaults when booting since i changed my motherboard to Asus Prime n100i-d d4.


    What i dont really understand is the hardware references here. I have a reference to CPU 1 core 4 and a reference to CPU 0 core 5


    I have only 1 CPU on the board with 4 cores in total. So is this a wrong hardware reference and possibly an incompatibility with dhcpd and my mainboard?


    Code
    dhcpcd[844]: segfault at 8 ip 000055f0fea8c2e0 sp 00007ffef96bf058 error 4 in dhcpcd[55f0fea89000+32000] likely on CPU 0 (core 4, socket 0)

dhcpcd[4574]: segfault at 8 ip 00005650c9e8b2e0 sp 00007fff822c0818 error 4 in dhcpcd[5650c9e88000+32000] likely on CPU 1 (core 5, socket 0)


    what i also see are some weird log entries regarding network interfaces.

    I am not sure why the system is renaming network interfaces forth and back at boot time to eth0.

    I do not have any eth0 interface on this system (formerly did). My current NIC is labeled enp2s0.

    So somewhere there is a leftover of eth0 by my motherboard migration, but i do not know where.

    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    latest proxmox kernel

    Edited 2 times, last by monsen ().

  • monsen

    Added the Label OMV 6.x
    • Official Post

    Just for comparison, I just did a reset on a motherboard just like yours and the syslog is clean, there are no relevant errors of any kind.

    Version 6.9.13-1 (Shaitan)

    Linux Kernel 6.2.16-11-bpo11-pve

    • Official Post

    Sorry no. If I had any idea I would have said it already :)

    In my syslog the cores appear correctly named from 0 to 3, by the way.


    Code
    ~# grep -E 'processor|core id' /proc/cpuinfo
processor       : 0
core id         : 0
processor       : 1
core id         : 1
processor       : 2
core id         : 2
processor       : 3
core id         : 3
    Quote from chente

    Sorry no. If I had any idea I would have said it already :)

    makes sense :P


    My cores although are not. Damn:



    Code
    root@debnas:~# grep -E 'processor|core id' /proc/cpuinfo
processor       : 0
core id         : 4
processor       : 1
core id         : 5
processor       : 2
core id         : 6
processor       : 3
core id         : 7

    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    latest proxmox kernel

    Damn i am completely lost here. I am not sure if the core numbering is even an issue.

    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    latest proxmox kernel

    Edited 2 times, last by monsen ().

    Some more info on eth0 in dmesg:


    Code
    [   11.382030] r8169 0000:02:00.0 eth0: RTL8168h/8111h, 10:7c:61:46:c5:d6, XID 541, IRQ 128
[   11.382036] r8169 0000:02:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
[   11.382701] r8169 0000:02:00.0 enp2s0: renamed from eth0


    EDIT: ok, this might be just normal due to new interface naming conventions and old names still being mapped in the underlying OS.

    Here is some comment on it: https://www.reddit.com/r/archl…_was_eth0_interface_name/

    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    latest proxmox kernel

    Ok I solved it by upgrading to OMV7 which includes a newer version of dhcpcd.

    As expected the error just disappeared then.

    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    latest proxmox kernel

  • monsen

    Added the Label resolved

  • monsen

    Set the Label from OMV 6.x to OMV 7.x (RC1)

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login