From: KeithG <ys3al35l@gmail.com>
To: connman@lists.linux.dev
Subject: Pi5 does not always connect eth0 at boot
Date: Fri, 12 Apr 2024 16:25:14 -0500 [thread overview]
Message-ID: <CAG17S_MphDzOwu5xwqGfD7GeJd+ww9JZ1w77ia-cwyaAYpuqBw@mail.gmail.com> (raw)
I have been using connman for a number of years on my Pis without
problems. The Pi5, though, I notice that it fairly regularly reboots
and does not get a valid IP address even though the cable is connected
and there seems to be no problem on the network. None of the other Pis
(3b+.Zero2W, 2b) fail to grab ab IP at boot. Is there some sort of
race condition that is causing it to not grab an address. If I restart
connman or force the interface down then up, it grabs an IP and all is
well. I have noticed this with the latest connman:
connman-git/now 1.42.r383.g49b16df3-1
Apr 12 12:20:02 pi5 connmand[54339]: Interface eth0 [ ethernet ] state is ready
Apr 12 12:20:02 pi5 connmand[54339]: Interface eth0 [ ethernet ] is the default
Apr 12 12:20:02 pi5 connmand[54339]: Interface eth0 [ ethernet ] IPv4
online check to http://ipv4.connman.net/online/status.html failed:
-22: Invalid argument
Apr 12 12:20:02 pi5 connmand[54339]: eth0 {add} address
169.254.184.199/16 label eth0 family 2
Apr 12 12:20:02 pi5 connmand[54339]: Interface eth0 [ ethernet ] IPv4
online check to http://ipv4.connman.net/online/status.html failed:
-22: Invalid argument
down then up:
Apr 12 12:23:00 pi5 connmand[54339]: eth0 {update} flags 102467
<UP,RUNNING,LOWER_UP>
Apr 12 12:23:00 pi5 connmand[54339]: eth0 {newlink} index 2 address
D8:3A:DD:D2:AE:3A mtu 1500
Apr 12 12:23:00 pi5 connmand[54339]: eth0 {newlink} index 2 operstate 6 <UP>
Apr 12 12:23:00 pi5 connmand[54339]: Interface eth0 [ ethernet ] state
is configuration
Apr 12 12:23:00 pi5 connmand[54339]: ipconfig state 3 ipconfig method 1
Apr 12 12:23:09 pi5 connmand[54339]: Interface eth0 [ ethernet ] state is ready
Apr 12 12:23:09 pi5 connmand[54339]: Interface eth0 [ ethernet ] is the default
Apr 12 12:23:09 pi5 connmand[54339]: Setting domainname to local
Apr 12 12:23:09 pi5 connmand[54339]: eth0 {add} address
192.168.1.128/24 label eth0 family 2
Apr 12 12:23:09 pi5 connmand[54339]: Interface eth0 [ ethernet ] IPv4
online check to http://ipv4.connman.net/online/status.html succeeded
Apr 12 12:23:09 pi5 connmand[54339]: Interface eth0 [ ethernet ] state is online
Is this a problem with connman or the Pi?
Keith
reply other threads:[~2024-04-12 21:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAG17S_MphDzOwu5xwqGfD7GeJd+ww9JZ1w77ia-cwyaAYpuqBw@mail.gmail.com \
--to=ys3al35l@gmail.com \
--cc=connman@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).