public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Warning about dhcpcd-10.5.0 with arm
Date: Wed, 12 Aug 2026 16:37:26 +0200	[thread overview]
Message-ID: <19524079-91de-4ff1-8c5d-b1556978e079@ipfire.org> (raw)
In-Reply-To: <b0a07a61-9284-4379-b481-448c54f827fc@ipfire.org>

On 12.08.2026 12:58, Adolf Belka wrote:
> Hi All,

Hi Adolf,

see comments below... ;-)

> Some information. I have a RPi with Arch Linux installed on it which I 
> use as my dhcp server on my orange network.
> 
> The Arch Linux ARM group are separate from Arch Linux. They had not done 
> an update to 10.4.x so I was still on 10.3.2.
> 
> I ran an update and they updated dhcpcd to 10.5.0
> 
> After the update dhcpcd failed to start and the logs showed it was 
> having a core dump when trying to start.
> 
> I downgraded to 10.2.3 and everything worked fine, Upgraded to 10.5.0 
> again and it had the core dump again and downgrading again made it work.
> 
> So on my arm based rpi with arch linux I am staying with 10.3.2 for the 
> moment.
> 
> It would probably be worth testing the 10.5.0 version on an arm IPFire 
> to see if it is a general issue or only for some hardware/os combinations.

I compiled and pushed dhcpcd 10.5.0 a few days ago and got it running
since then on Core 203 (x86_64). No seen problems so far - its running
now for 5 days 17 hours 6 minutes (watched by 'monit').

...
root@ipfire: / # dhcpcd --version
dhcpcd 10.5.0
Copyright (c) 2006-2025 Roy Marples
Compiled in features: INET ARP ARPing IPv4LL INET6 DHCPv6 AUTH PRIVSEP
...

You can find it here:
=>
https://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=c3df7efed69554c7f83e74c4d3a895cd77045dd4

HTH
Matthias



      reply	other threads:[~2026-08-12 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 10:58 Adolf Belka
2026-08-12 14:37 ` Matthias Fischer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19524079-91de-4ff1-8c5d-b1556978e079@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox