[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

bullseye-installer fails on Cubox-i due to networking issue



Hi,

I tried to run the bullseye installer from

http://ftp2.de.debian.org/debian/dists/bullseye/main/installer-armhf/current/
images/netboot/SD-card-images/

on a cubox-i using a serial console today.

It seems the network interface does not come up properly:

~ # dmesg |grep eth
[    5.009246] fec 2188000.ethernet: Invalid MAC address: 00:00:00:00:00:00
[    5.015982] fec 2188000.ethernet: Using random MAC address: 4a:
0d:a7:66:c1:e6
[    5.028381] mdio_bus 2188000.ethernet-1: MDIO device at address 0 is 
missing.
[  138.479638] fec 2188000.ethernet eth0: Unable to connect to phy
[  139.674014] fec 2188000.ethernet eth0: Unable to connect to phy
[  141.218830] fec 2188000.ethernet eth0: Unable to connect to phy
[  147.400881] fec 2188000.ethernet eth0: Unable to connect to phy
[  199.375688] fec 2188000.ethernet eth0: Unable to connect to phy
[  736.031852] fec 2188000.ethernet eth0: Unable to connect to phy
[  906.069383] fec 2188000.ethernet eth0: Unable to connect to phy
[ 1156.891662] fec 2188000.ethernet eth0: Unable to connect to phy
[ 1266.982998] fec 2188000.ethernet eth0: Unable to connect to phy
~ # 

Not sure if this backtrace is related or even expected:

[    5.626874] Freeing unused kernel memory: 2048K
[    5.632309] ------------[ cut here ]------------
[    5.636982] WARNING: CPU: 0 PID: 1 at arch/arm/mm/dump.c:248 
note_page+0x3d0/0x3dc
[    5.644576] arm/mm: Found insecure W+X mapping at address 0xf0879000
[    5.650947] Modules linked in:                       
[    5.654033] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.9.0-4-armmp #1 
Debian 5.9.11-1
[    5.661953] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
[    5.668483] Backtrace: 
[    5.670946] [<c0c8b8d8>] (dump_backtrace) from [<c0c8bc84>] 
(show_stack+0x20/0x24)
[    5.678522]  r7:000000f8 r6:60000013 r5:00000000 r4:c136910c
[    5.684192] [<c0c8bc64>] (show_stack) from [<c0c90db4>] 
(dump_stack+0xc8/0xdc)
[    5.691430] [<c0c90cec>] (dump_stack) from [<c034cd78>] (__warn+0xe0/0x148)
[    5.698396]  r7:000000f8 r6:00000009 r5:c031eb6c r4:c0eb24e0
[    5.704062] [<c034cc98>] (__warn) from [<c0c8cba8>] 
(warn_slowpath_fmt+0xa4/0xe4)
[    5.711548]  r7:c031eb6c r6:000000f8 r5:c0eb24e0 r4:c0eb24ac
[    5.717214] [<c0c8cb08>] (warn_slowpath_fmt) from [<c031eb6c>] 
(note_page+0x3d0/0x3dc)
[    5.725135]  r8:00000000 r7:00000000 r6:00000005 r5:c130c440 r4:ee951f28
[    5.731841] [<c031e79c>] (note_page) from [<c031ec60>] 
(walk_pmd+0xe8/0x1a4)
[    5.738895]  r10:ee951f28 r9:c0207c20 r8:ee8c6800 r7:00000000 r6:c0eb2528 
r5:f087b000
[    5.746724]  r4:ee8c61ec
[    5.749263] [<c031eb78>] (walk_pmd) from [<c031ee60>] 
(ptdump_check_wx+0x88/0x104)
[    5.756838]  r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:c0208000 
r5:f0800000
[    5.764667]  r4:c0207c28
[    5.767215] [<c031edd8>] (ptdump_check_wx) from [<c0319200>] 
(mark_rodata_ro+0x3c/0x40)
[    5.775223]  r6:00000000 r5:c0c9ab94 r4:00000000
[    5.779853] [<c03191c4>] (mark_rodata_ro) from [<c0c9abd8>] 
(kernel_init+0x44/0x130)
[    5.787605] [<c0c9ab94>] (kernel_init) from [<c03001a8>] 
(ret_from_fork+0x14/0x2c)
[    5.795176] Exception stack(0xee951fb0 to 0xee951ff8)
[    5.800232] 1fa0:                                     00000000 00000000 
00000000 00000000
[    5.808414] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 
00000000 00000000
[    5.816595] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[    5.823210]  r5:c0c9ab94 r4:00000000
[    5.826848] ---[ end trace eee50453771fe1ab ]---
[    5.831714] Checked W+X mappings: FAILED, 1 W+X pages found
[    5.837378] Run /init as init process


I run in a current xbian image a few days back on the same machine in the same 
issue. This was buster based, but had a recent kernel. This indicates that the 
issue is related with the kernel. 

The same network cable works on a buster x86 system and even with the cubox-i 
with a SD card with and older xbian version without any issues.

Any hint or idea what could be wrong is apprectiated.

If anybody has a way to get debug data (e.g. dmseg output) easier from the 
cubox than copy and paste from minicom, that would also help.

Many thanks
Rainer


-- 
Rainer Dorsch
http://bokomoko.de/



Reply to: