SG3100 - Fatal abort during boot and recovery failure

[radmurdock]

Hello,

I have a 6 month old SG-3100 that failed suddenly during the middle of the day (no power loss, etc.). On the console port I see that it is failing due to a 'Fatal kernel mode data abort: 'Translation Fault (L1)' on read.'

I attempted to restore from a USB recovery image but recovery will not start and is failing with the same message. At this point I suspect a hardware failure but I'm far from a Marvel U-Boot expert. Does anyone have any ideas?

Condensed log output below right before failure:

e6000sw0: <Marvell 88E6141> on mdio0
e6000sw0: single-chip addressing mode
miibus1: <MII bus> on e6000sw0
e1000phy0: <Marvell 88E1000 Gigabit PHY> PHY 17 on miibus1
e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
miibus2: <MII bus> on e6000sw0
e1000phy1: <Marvell 88E1000 Gigabit PHY> PHY 18 on miibus2
e1000phy1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
miibus3: <MII bus> on e6000sw0
e1000phy2: <Marvell 88E1000 Gigabit PHY> PHY 19 on miibus3
e1000phy2: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
miibus4: <MII bus> on e6000sw0
e1000phy3: <Marvell 88E1000 Gigabit PHY> PHY 20 on miibus4
e1000phy3: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
e6000sw0: switch is ready.
etherswitch0: <Switch controller> on e6000sw0
ehci0: <Marvell Integrated USB 2.0 controller> mem 0x58000-0x584ff irq 28 on simplebus1
usbus0: EHCI version 1.0
usbus0 on ehci0
mvneta2: <NETA controller> mem 0x70000-0x73fff irq 29 on simplebus1
mvneta2: version is 10
mvneta2: Ethernet address: 00:08:a2:0f:66:b9
Fatal kernel mode data abort: 'Translation Fault (L1)' on read
trapframe: 0xc1413a90
FSR=00000005, FAR=00000294, spsr=400000d3
r0 =00000000, r1 =00000000, r2 =00000001, r3 =00000001
r4 =c1413b58, r5 =00000000, r6 =c11cf090, r7 =c11cf080
r8 =00000000, r9 =00000000, r10=c11cd920, r11=c1413b80
r12=c114ba2c, ssp=c1413b20, slr=c0568448, pc =c03a36c4

panic: Fatal abort
cpuid = 0
Uptime: 1s
Automatic reboot in 15 seconds - press a key on the console to abort
--> Press a key on the console to reboot,
--> or switch off the system now.

[kiokoman]

it's better if you open a ticket at https://go.netgate.com

[serbus]

@radmurdock said in SG3100 - Fatal abort during boot and recovery failure:

I have a 6 month old SG-3100 that failed suddenly during the middle of the day (no power loss, etc.). On the console port I see that it is failing due to a 'Fatal kernel mode data abort: 'Translation Fault (L1)' on read.'

Hello!

I have a 3 week old sg-3100 experiencing an identical failure.
I have a ticket open with support, but I am wondering how your failure was resolved.
Did you determine what caused it?

Thanks!

John

[radmurdock]

@serbus It was a hardware failure in this case. The unit was RMAed.