Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #73070 > unrolled thread

Bug#983818: linux-image-5.10.0-3-arm64: often fails to bring up eth0 / dwmac_rk module

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#983818: linux-image-5.10.0-3-arm64: often fails to bring up eth0 / dwmac_rk module Salvatore Bonaccorso <carnil@debian.org> - 2021-09-26 09:00 +0200
    Processed: Re: Bug#983818: linux-image-5.10.0-3-arm64: often  fails to bring up eth0 / dwmac_rk module "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-09-26 09:00 +0200
    Bug#983818: linux-image-5.10.0-3-arm64: often fails to bring up eth0 / dwmac_rk module Forest <forestix@sonic.net> - 2021-09-27 03:00 +0200
      Processed: Re: Bug#983818: linux-image-5.10.0-3-arm64: often  fails to bring up eth0 / dwmac_rk module "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-09-27 03:00 +0200

#73070 — Bug#983818: linux-image-5.10.0-3-arm64: often fails to bring up eth0 / dwmac_rk module

Control: tags -1 + moreinfo

On Mon, Mar 01, 2021 at 03:33:27PM -0800, Forest wrote:
> Package: src:linux
> Version: 5.10.13-1
> Severity: critical
> Justification: breaks unrelated software
> 
> Dear Maintainer,
> 
> When booting recent kernels on a RockPro64 board (rk3399), eth0 often fails
> to come up, leaving this headless box practically unusable without serial
> console intervention. Logging in on the console and using rmmod/modprobe to
> reload dwmac_rk revives the network interface and allows normal operation
> until the next reboot.
> 
> Logs are included below, but the last relevant dmesg errors seem to be:
> rk_gmac-dwmac fe300000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed
> rk_gmac-dwmac fe300000.ethernet eth0: stmmac_open: Hw setup failed
> 
> The problem doesn't occur on every boot. I haven't determined what conditions
> make it more likely. It's possible that scheduling an fsck makes it happen
> less frequently (perhaps there's a timing issue?) but it's hard to say; it
> still happens fairly often even when I fsck on every boot.
> 
> The problem appeared some time in the past two or three months. I keep up
> with unstable kernel updates, so maybe a semi-recent change in the unstable
> kernel caused it? Or maybe I was just lucky until recently.
> 
> Curiously, when dropbear ssh launches from initramfs, it never has trouble
> with eth0. The problem doesn't show up until after dropbear has run and I
> have unlocked my root filesystem over ssh and boot continues. I am using an
> initramfs-tools tweak to make dropbear work around #968519, so I suppose that
> bug and the present problem could be related but merely avoided by dropbear.
> However, #968519 was present long before the present problem appeared.
> 
> Here's someone else experiencing this problem:
> https://forum.pine64.org/showthread.php?tid=9351&pid=87304#pid87304

Could you try with the current kernel in unstable? We are at 5.14.6-2,
which had some rk3399 related changes. If you still can reproduce the
issue my best guess would be to make a report upstream, presumably
something around contacting 

Giuseppe Cavallaro <peppe.cavallaro@st.com> (supporter:STMMAC ETHERNET DRIVER)
Alexandre Torgue <alexandre.torgue@foss.st.com> (supporter:STMMAC ETHERNET DRIVER)
Jose Abreu <joabreu@synopsys.com> (supporter:STMMAC ETHERNET DRIVER)
"David S. Miller" <davem@davemloft.net> (maintainer:NETWORKING DRIVERS)
Jakub Kicinski <kuba@kernel.org> (maintainer:NETWORKING DRIVERS)
Maxime Coquelin <mcoquelin.stm32@gmail.com> (maintainer:ARM/STM32 ARCHITECTURE)
Philipp Zabel <p.zabel@pengutronix.de> (maintainer:RESET CONTROLLER FRAMEWORK)
Liam Girdwood <lgirdwood@gmail.com> (supporter:VOLTAGE AND CURRENT REGULATOR FRAMEWORK)
Mark Brown <broonie@kernel.org> (supporter:VOLTAGE AND CURRENT REGULATOR FRAMEWORK)
netdev@vger.kernel.org (open list:STMMAC ETHERNET DRIVER)
linux-stm32@st-md-mailman.stormreply.com (moderated list:ARM/STM32 ARCHITECTURE)
linux-arm-kernel@lists.infradead.org (moderated list:ARM/STM32 ARCHITECTURE)
linux-kernel@vger.kernel.org (open list)

(and keeping us downstream in the loop).

Regards,
Salvatore

[toc] | [next] | [standalone]

#73071 — Processed: Re: Bug#983818: linux-image-5.10.0-3-arm64: often fails to bring up eth0 / dwmac_rk module

Processing control commands:

> tags -1 + moreinfo
Bug #983818 [src:linux] linux-image-5.10.0-3-arm64: often fails to bring up ethernet / dwmac_rk module on rockpro64
Added tag(s) moreinfo.

-- 
983818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983818
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#73078

Control: tags -1 - moreinfo

>Could you try with the current kernel in unstable?
>We are at 5.14.6-2, which had some rk3399 related changes. 

Did any of those changes arrive after 5.14.0-1?  If so, I suppose I would
have to wait for a newer debian kernel to appear before I could test it.

With 5.14.0-1 (the version in unstable), the results are worse:

Dropbear no longer works.  Error message:
/scripts/init-premount/dropbear: .: line 333: can't open '/run/net-*.conf': No such file or directory

Using a serial console for LUKS unlock and then running rmmod dwmac_rk / 
modprobe dwmac_rk no longer brings up eth0.

The dmesg output has changed a bit:
$ egrep 'mac|eth0' dmesg.linux-image-5.14.0-1-arm64 
[    5.708873] rk_gmac-dwmac fe300000.ethernet: IRQ eth_wake_irq not found
[    5.709470] rk_gmac-dwmac fe300000.ethernet: IRQ eth_lpi not found
[    5.710965] rk_gmac-dwmac fe300000.ethernet: PTP uses main clock
[    5.712133] rk_gmac-dwmac fe300000.ethernet: clock input or output? (input).
[    5.713263] rk_gmac-dwmac fe300000.ethernet: TX delay(0x28).
[    5.714418] rk_gmac-dwmac fe300000.ethernet: RX delay(0x11).
[    5.716512] rk_gmac-dwmac fe300000.ethernet: integrated PHY? (no).
[    5.717492] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed
[    5.719275] rk_gmac-dwmac fe300000.ethernet: clock input from PHY
[    5.724825] rk_gmac-dwmac fe300000.ethernet: init for RGMII
[    5.725658] rk_gmac-dwmac fe300000.ethernet: User ID: 0x10, Synopsys ID: 0x35
[    5.726328] rk_gmac-dwmac fe300000.ethernet: 	DWMAC1000
[    5.726802] rk_gmac-dwmac fe300000.ethernet: DMA HW capability register supported
[    5.727511] rk_gmac-dwmac fe300000.ethernet: RX Checksum Offload Engine supported
[    5.728183] rk_gmac-dwmac fe300000.ethernet: COE Type 2
[    5.728652] rk_gmac-dwmac fe300000.ethernet: TX Checksum insertion supported
[    5.729275] rk_gmac-dwmac fe300000.ethernet: Wake-Up On Lan supported
[    5.731134] rk_gmac-dwmac fe300000.ethernet: Normal descriptors
[    5.731674] rk_gmac-dwmac fe300000.ethernet: Ring mode enabled
[    5.732192] rk_gmac-dwmac fe300000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    5.851291] libphy: stmmac: probed
[    5.851612] RTL8211F Gigabit Ethernet stmmac-0:00: attached PHY driver (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[    5.852504] RTL8211F Gigabit Ethernet stmmac-0:01: attached PHY driver (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
[    6.639085] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=POLL)
[    6.641458] rk_gmac-dwmac fe300000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
[    6.653320] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found
[    6.653364] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW
[    6.654183] rk_gmac-dwmac fe300000.ethernet eth0: configuring for phy/rgmii link mode
[    9.760371] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[    9.760429] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  199.685064] rk_gmac-dwmac fe300000.ethernet eth0: Link is Down
[  207.195113] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=POLL)
[  207.197673] rk_gmac-dwmac fe300000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
[  207.206976] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found
[  207.207681] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW
[  207.208307] rk_gmac-dwmac fe300000.ethernet eth0: configuring for phy/rgmii link mode
[  210.304576] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[  210.305423] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

[toc] | [prev] | [next] | [standalone]

#73079 — Processed: Re: Bug#983818: linux-image-5.10.0-3-arm64: often fails to bring up eth0 / dwmac_rk module

Processing control commands:

> tags -1 - moreinfo
Bug #983818 [src:linux] linux-image-5.10.0-3-arm64: often fails to bring up ethernet / dwmac_rk module on rockpro64
Removed tag(s) moreinfo.

-- 
983818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983818
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web