Netonix Forums

During a recent setting up of an AC 150 on version 1.47 we received a segmentation fault.

The steps were roughly,

1. Created a second and third address of 3255, and 3210
2. Added IP addresses of it.
3. Tried to figure out how to set the VLAN and get routed to so removed 3210 and put in Management VLAN.
4. Configured it from the console a couple of items specifically
Terminal speed
5. Then figured out the process of how to set the VLAN / and Management IP.
6. Then I decided to add back a VLAN 1 as the third VLAN. Hit Save.
7. Then the ports would come up for a few seconds, and the console read "Segmentation Fault"
At that point rest the machine, it said it was missing kernel files.
After that reset it again and it booted.
Then I have reset the whole thing again doing simpler steps.
My recommendation is that before loading the config it test whether the items are actually consistent and valid with each other.

Seemed like that was off.

I'm not sure what you meant by the first two steps, so I couldn't duplicate your process exactly. It follows, then, that I could not duplicate your results.

Previously it has been assumed that this issue (uncommon, but not rare) is simply flash memory playing its usual tricks, but the percentage I'm seeing is a little bit higher than I would predict. If it does it again, please RMA. I don't believe there is a hardware issue, but I need to grab a memory dump for forensic analysis.

Julian,

I don't think it was flash memory per say, what happened is it was running and then 100% stopped passing traffic. After a few reboots I consoled the reboot.

What I would suggest is that you keep the last 10 logs of reboot somewhere as it would of shown the issue.

bootlog.0
bootlog.1
bootlog.2
bootlog.3 etc.

The procedure I was doing before it went corrupt was the one i wrote in proper steps at the bottom.

viewtopic.php?f=17&t=2951

Jamie

A lot of things have to be perfect in order for any embedded system to boot and function.

Flash memory is known for controller misfires during read/write cycles, which corrupts the block being written or read from - read https://en.wikipedia.org/wiki/Flash_memory#Limitations - "sticky" bits happen all the time. I don't know that storage size will allow previous bootlogs, but I'll ask about a last-config and running-config setup.

Like I said, if it does it again, send it in.