From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] rpi-kernel-5.15.61_1: eth0 link always down on rpi 1 model b+
Date: Sat, 01 Oct 2022 07:36:05 +0200 [thread overview]
Message-ID: <20221001053605.1cpbKDtp7Njn5CBCMxztWyuQwqK2hnnx0wWMnNWxV9U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39129@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2542 bytes --]
Closed issue by akce on void-packages repository
https://github.com/void-linux/void-packages/issues/39129
Description:
### Is this a new report?
Yes
### System Info
Void 5.15.61_1 armv6l Unknown uptodate rFFF
### Package(s) Affected
rpi-kernel-5.15_61_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
eth0 link should be in state UP after startup. Here's how it looks with a working `rpi-kernel-5.10.110_1`:
```shell
$ uname -a
Linux mordor 5.10.110_1 #1 Wed Aug 3 16:47:21 UTC 2022 armv6l GNU/Linux
$ ip addr show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:bc:23:d3 brd ff:ff:ff:ff:ff:ff
inet 192.168.31.254/16 brd 192.168.255.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
inet6 fe80::ba27:ebff:febc:23d3/64 scope link
valid_lft forever preferred_lft forever
```
Here's the tail end of `dmesg` where i unplugged and then re-inserted the network cable:
```dmesg
[ 134.196932] smsc95xx 1-1.1:1.0 eth0: Link is Down
[ 143.525609] smsc95xx 1-1.1:1.0 eth0: Link is Up - 100Mbps/Full - flow control off
```
### Actual behaviour
On my rpi 1 model b+, **eth0** link is always in state DOWN; i haven't been able to bring it up.
With `rpi-kernel-5.15.61_1` i see:
```shell
$ uname -a
Linux mordor 5.15.61_1 #1 Mon Sep 5 02:23:47 UTC 2022 armv6l GNU/Linux
$ ip addr show eth0
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether b8:27:eb:bc:23:d3 brd ff:ff:ff:ff:ff:ff
inet 192.168.31.254/16 brd 192.168.255.255 scope global eth0
valid_lft forever preferred_lft forever
```
Unplugging and re-inserting the network cable shows no activity in dmesg.
Orange and Green ethernet port LEDS are visible on the Raspberry Pi while the network cable is plugged in.
Manually running `ip link set eth0 up` returns success to the shell but has no effect to the link state.
/boot/config.txt has no overlays enabled.
### Steps to reproduce
Upgrade to `rpi-kernel-5.15-61_1` (presumably from [38958](https://github.com/void-linux/void-packages/pull/38958)).
Downgrading kernel to `rpi-kernel-5.10.110_1` restores eth0 to working state.
I did a full upgrade which included new `rpi-firmware` etc, but reverting only `rpi-kernel` was enough to get the network functional again.
prev parent reply other threads:[~2022-10-01 5:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 3:23 [ISSUE] " akce
2022-09-06 3:29 ` akce
2022-09-06 8:14 ` tsjk
2022-09-06 8:16 ` tsjk
2022-09-06 20:23 ` tsjk
2022-09-06 20:30 ` tsjk
2022-09-25 10:35 ` classabbyamp
2022-09-25 11:32 ` classabbyamp
2022-09-25 16:55 ` tsjk
2022-09-25 16:56 ` tsjk
2022-09-25 17:00 ` classabbyamp
2022-09-26 5:28 ` classabbyamp
2022-09-26 5:28 ` classabbyamp
2022-09-27 5:04 ` tsjk
2022-09-30 3:49 ` classabbyamp
2022-09-30 5:28 ` tsjk
2022-09-30 5:30 ` tsjk
2022-10-01 5:36 ` classabbyamp [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=20221001053605.1cpbKDtp7Njn5CBCMxztWyuQwqK2hnnx0wWMnNWxV9U@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).