Reply
Highlighted
New Member
Posts: 17
Registered: ‎01-07-2015
Kudos: 2
Accepted Solution

Edgerouter POE crash console dump

my edgerouter POE is crashing every few days (this time it lasted about a week) and I caught the console dump.
I went ahead and included the dump for the reboot and I can provide the config file and syslog console logs prior to the crash if it would be helpful.

 

thanks!

Bill

 

*** NMI Watchdog interrupt on Core 0x00 ***
$0 0x0000000000000000 at 0x0000000050008ce1
v0 0x0000000000000001 v1 0x0000000000010000
a0 0xffffffffc0010ae0 a1 0x000000000000bb95
a2 0x000000000000bb96 a3 0x0000000000000000
a4 0x0000000000000000 a5 0x8000000001790200
a6 0x0000000000000000 a7 0x0000000000000000
t0 0x0000000000000001 t1 0x000000000001c000
t2 0x000000000000000c t3 0xffffffff805a0000
s0 0x0000000000000000 s1 0xffffffffc0010918
s2 0xffffffff805a0000 s3 0x0000000000000001
s4 0x0000000000000000 s5 0xffffffffc0010000
s6 0x0000000000000006 s7 0xffffffffc0010000
t8 0x00000000006d5694 t9 0xffffffff8014e1b8
k0 0x0000000000000000 k1 0x0000000000000001
gp 0x800000041c084000 sp 0x800000041c087c10
s8 0xffffffffc0017c30 ra 0xffffffffc00181c0
err_epc 0xffffffff804b5f10 epc 0xffffffffc007a660
status 0x0000000050488ce4 cause 0x0000000040808c08
sum0 0x000000f100008000 en0 0x0100400500008000
*** Chip soft reset soon ***

Looking for valid bootloader image....
Jumping to start of image at address 0xbfc80000


U-Boot 1.1.1 (UBNT Build ID: 4567941-g15e9b5d) (Build time: Jun 4 2013 - 14:51:00)

BIST check passed.
UBNT_E100 r1:1, r2:22, f:8/135, serial #: 24A43CB39B8B
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM: 512 MB
Clearing DRAM....... done
Flash: 8 MB
Net: octeth0, octeth1, octeth2

USB: (port 0) scanning bus for devices... 1 USB Devices found
scanning bus for storage devices...
Device 0: Vendor: Prod.: USB DISK 2.0 Rev: PMAP
Type: Removable Hard Disk
Capacity: 3824.0 MB = 3.7 GB (7831552 x 512) 0
reading vmlinux.64
............................

5567368 bytes read
argv[2]: coremask=0x3
argv[3]: root=/dev/sda2
argv[4]: rootdelay=15
argv[5]: rw
argv[6]: rootsqimg=squashfs.img
argv[7]: rootsqwdir=w
argv[8]: mtdparts=phys_mapped_flash:512k(boot0),512k(boot1),64k@1024k(eeprom)
ELF file is 64 bit
Allocating memory for ELF segment: addr: 0xffffffff80100000 (adjusted to: 0x100000), size 0x69dfd0
Allocated memory for ELF segment: addr: 0xffffffff80100000, size 0x69dfd0
Processing PHDR 0
Loading 54dd80 bytes at ffffffff80100000
Clearing 150250 bytes at ffffffff8064dd80
## Loading Linux kernel with entry point: 0xffffffff804aeb00 ...
Bootloader: Done loading app on coremask: 0x3
Linux version 3.10.20-UBNT (root@ubnt-builder2) (gcc version 4.7.0 (Cavium Inc. Version: SDK_3_1_0_p2 build 34) ) #1 SMP Thu Oct 16 16:29:39 PDT 2014
CVMSEG size: 2 cache lines (256 bytes)
Cavium Inc. SDK-3.1
bootconsole [early0] enabled
CPU revision is: 000d0601 (Cavium Octeon+)
Checking for the multiply/shift bug... no.
Checking for the daddiu bug... no.
Determined physical RAM map:
memory: 0000000007800000 @ 0000000000800000 (usable)
memory: 0000000007c00000 @ 0000000008200000 (usable)
memory: 000000000fc00000 @ 0000000410000000 (usable)
memory: 000000000050b000 @ 0000000000100000 (usable)
memory: 0000000000045000 @ 000000000060b000 (usable after init)
Wasting 14336 bytes for tracking 256 unused pages
software IO TLB [mem 0x01707000-0x01747000] (0MB) mapped at [8000000001707000-8000000001746fff]
Zone ranges:
DMA32 [mem 0x00100000-0xefffffff]
Normal [mem 0xf0000000-0x41fbfffff]
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x00100000-0x0064ffff]
node 0: [mem 0x00800000-0x07ffffff]
node 0: [mem 0x08200000-0x0fdfffff]
node 0: [mem 0x410000000-0x41fbfffff]
Primary instruction cache 32kB, virtually tagged, 4 way, 64 sets, linesize 128 bytes.
Primary data cache 16kB, 64-way, 2 sets, linesize 128 bytes.
Secondary unified cache 128kB, 8-way, 128 sets, linesize 128 bytes.
PERCPU: Embedded 10 pages/cpu @8000000001784000 s11648 r8192 d21120 u40960
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 126581
Kernel command line: bootoctlinux $loadaddr coremask=0x3 root=/dev/sda2 rootdelay=15 rw rootsqimg=squashfs.img rootsqwdir=w mtdparts=phys_mapped_flash:512k(boot0),512k(boot1),64k@1024k(eeprom) console=ttyS0,115200
PID hash table entries: 2048 (order: 2, 16384 bytes)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 499340k/513344k available (3810k kernel code, 14004k reserved, 1352k data, 276k init, 0k highmem)
Hierarchical RCU implementation.
NR_IRQS:255
Calibrating delay loop (skipped) preset value.. 1000.00 BogoMIPS (lpj=5000000)
pid_max: default: 32768 minimum: 501
Security Framework initialized
Mount-cache hash table entries: 256
Checking for the daddi bug... no.
SMP: Booting CPU01 (CoreId 1)...
CPU revision is: 000d0601 (Cavium Octeon+)
Brought up 2 CPUs
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource OCTEON_CVMCOUNT
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 4, 65536 bytes)
TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
octeon_pci_console: Console not created.
/proc/octeon_perf: Octeon performance counter interface loaded
HugeTLB registered 2 MB page size, pre-allocated 0 pages
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering unionfs 2.5.13 (for 3.10.34)
msgmni has been set to 975
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 6 ports, IRQ sharing disabled
1180000000800.serial: ttyS0 at MMIO 0x1180000000800 (irq = 34) is a OCTEON
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
1180000000c00.serial: ttyS1 at MMIO 0x1180000000c00 (irq = 35) is a OCTEON
loop: module loaded
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
OcteonUSB 16f0010000000.usbc: Octeon Host Controller
OcteonUSB 16f0010000000.usbc: new USB bus registered, assigned bus number 1
OcteonUSB 16f0010000000.usbc: irq 56, io mem 0x00000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
OcteonUSB: Registered HCD for port 0 on irq 56
usbcore: registered new interface driver usb-storage
octeon_wdt: Initial granularity 5 Sec
TCP: cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
L2 lock: TLB refill 256 bytes
L2 lock: General exception 128 bytes
L2 lock: low-level interrupt 128 bytes
L2 lock: interrupt 640 bytes
L2 lock: memcpy 1152 bytes
Bootbus flash: Setting flash for 8MB flash at 0x1f400000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank. Manufacturer ID 0x0000c2 Chip ID 0x0000c9
Amd/Fujitsu Extended Query Table at 0x0040
Amd/Fujitsu Extended Query version 1.1.
phys_mapped_flash: Swapping erase regions for top-boot CFI table.
number of CFI chips: 1
3 cmdlinepart partitions found on MTD device phys_mapped_flash
Creating 3 MTD partitions on "phys_mapped_flash":
0x000000000000-0x000000080000 : "boot0"
0x000000080000-0x000000100000 : "boot1"
0x000000100000-0x000000110000 : "eeprom"
Waiting 15sec before mounting root device...
usb 1-1: new high-speed USB device number 2 using OcteonUSB
usb-storage 1-1:1.0: USB Mass Storage device detected
scsi0 : usb-storage 1-1:1.0
scsi 0:0:0:0: Direct-Access USB DISK 2.0 PMAP PQ: 0 ANSI: 6
sd 0:0:0:0: [sda] 7831552 512-byte logical blocks: (4.00 GB/3.73 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] No Caching mode page found
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] No Caching mode page found
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1 sda2
sd 0:0:0:0: [sda] No Caching mode page found
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk
kjournald starting. Commit interval 3 seconds
EXT3-fs (sda2): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sda2): using internal journal
EXT3-fs (sda2): recovery complete
EXT3-fs (sda2): mounted filesystem with journal data mode
VFS: Mounted root (unionfs filesystem) on device 0:11.
Freeing unused kernel memory: 276K (ffffffff8060b000 - ffffffff80650000)
Algorithmics/MIPS FPU Emulator v1.5
INIT: version 2.88 booting
INIT: Entering runlevel: 2
[ ok ] Starting routing daemon: rib.
[ ok ] Starting EdgeOS router: migrate rl-system configure.

 


Accepted Solutions
Previous Employee
Posts: 13,551
Registered: ‎06-10-2011
Kudos: 5429
Solutions: 1656
Contributions: 2

Re: Edgerouter POE crash console dump

Thanks for providing the information. I have a potential fix that Stig is testing now, and so far so good, so it will probably be included in the next alpha/beta for testing and at that point you might want to give it a try.

View solution in original post


All Replies
Previous Employee
Posts: 13,551
Registered: ‎06-10-2011
Kudos: 5429
Solutions: 1656
Contributions: 2

Re: Edgerouter POE crash console dump

Thanks for providing the information. Could you confirm if there was "Core 0x01" message in addition to the "Core 0x00" shown?

New Member
Posts: 17
Registered: ‎01-07-2015
Kudos: 2

Re: Edgerouter POE crash console dump

there was not. the only thing above what I copied was a login message.

thanks!

Bill

New Member
Posts: 17
Registered: ‎01-07-2015
Kudos: 2

Re: Edgerouter POE crash console dump

 happened again, this time got what you asked for

*** NMI Watchdog interrupt on Core 0x00 ***
        $0      0x0000000000000000      at      0x0000000000000001
        v0      0x0000000000000001      v1      0x0000000000010000
        a0      0xffffffffc0010ae0      a1      0x0000000000000002
        a2      0x000000000000d91e      a3      0x800000000167cff0
        a4      0x8000000081139000      a5      0x0000000000000010
        a6      0x0000000000000000      a7      0x0000000000000000
        t0      0xffffffffffffffff      t1      0x0000000000000000
        t2      0x0000000000000000      t3      0x0000000073494000
        s0      0xffffffffc000da30      s1      0xffffffffc0010000
        s2      0xffffffffc00151c0      s3      0x800000041d891000
        s4      0xfffffffffffffff4      s5      0x0000000000001000
        s6      0x0000000073484000      s7      0xffffffffc000d998
        t8      0x0000000000080000      t9      0x00000000776751a4
        k0      0x0000000073306930      k1      0x0f00000010712847
        gp      0x800000041cf58000      sp      0x800000041cf5bd50
        s8      0xffffffffc00151c0      ra      0xffffffffc00173bc
        err_epc 0xffffffff804b5f04      epc     0xffffffffc0017378
        status  0x0000000010588ce4      cause   0x0000000040808c08
        sum0    0x000000f000008000      en0     0x0100400500008000
*** Chip soft reset soon ***

*** NMI Watchdog interrupt on Core 0x01 ***
        $0      0x0000000000000000      at      0x0000000010108ce1
        v0      0x0000000000000001      v1      0x0000000000010000
        a0      0xffffffffc0010ae0      a1      0x0000000000000000
        a2      0x000000000000d91d      a3      0x0000000000000000
        a4      0x0000000000000000      a5      0x8000000001786200
        a6      0x0000000000000000      a7      0x0000000000000000
        t0      0x0000000000000001      t1      0x000000000001c000
        t2      0x000000000000000c      t3      0x800000041c0ac000
        s0      0x0000000000000000      s1      0xffffffffc0010918
        s2      0xffffffff805a0000      s3      0x0000000000000001
        s4      0x0000000000000000      s5      0xffffffffc0010000
        s6      0x0000000000000006      s7      0xffffffffc0010000
        t8      0x00000000004182b0      t9      0xffffffff8014e1b8
        k0      0x0000000000000000      k1      0x0000000000000009
        gp      0x800000041c280000      sp      0x800000041c283c10
        s8      0xffffffffc0017c30      ra      0xffffffffc00181c0
        err_epc 0xffffffff804b5efc      epc     0xffffffff8014c7a0
        status  0x0000000010588ce4      cause   0x0000000040808800
        sum0    0x000000f000008000      en0     0x0000000100000000
*** Chip soft reset soon ***

Looking for valid bootloader image....
Jumping to start of image at address 0xbfc80000

 

Previous Employee
Posts: 13,551
Registered: ‎06-10-2011
Kudos: 5429
Solutions: 1656
Contributions: 2

Re: Edgerouter POE crash console dump

Thanks for providing the information. I have a potential fix that Stig is testing now, and so far so good, so it will probably be included in the next alpha/beta for testing and at that point you might want to give it a try.

New Member
Posts: 17
Registered: ‎01-07-2015
Kudos: 2

Re: Edgerouter POE crash console dump

three more in last few days.

 

if it helps to know, we stream a LOT of video from Netflix and iTunes and others.

 

thanks!

Bill

 

 

*** NMI Watchdog interrupt on Core 0x00 ***
        $0      0x0000000000000000      at      0x0000000000000001
        v0      0x0000000000000001      v1      0x0000000000010000
        a0      0xffffffffc0010ae0      a1      0x000000000000000d
        a2      0x0000000000007156      a3      0x800000000164a930
        a4      0x8000000081139000      a5      0x0000000000000010
        a6      0x0000000000000000      a7      0x0000000000000000
        t0      0xffffffffffffffff      t1      0x0000000000000000
        t2      0x0000000000000000      t3      0x0000000074145000
        s0      0xffffffffc000da30      s1      0xffffffffc0010000
        s2      0xffffffffc00151c0      s3      0x800000041ca29000
        s4      0xfffffffffffffff4      s5      0x0000000000001000
        s6      0x0000000074135000      s7      0xffffffffc000d998
        t8      0x0000000000080000      t9      0x00000000773261a4
        k0      0x0000000076953a48      k1      0x800000041cf03fe0
        gp      0x800000041cf00000      sp      0x800000041cf03d50
        s8      0xffffffffc00151c0      ra      0xffffffffc00173bc
        err_epc 0xffffffff804b5f04      epc     0x00000000772ff914
        status  0x0000000010588ce4      cause   0x0000000040808c20
        sum0    0x000000f000008000      en0     0x0100400500008000
*** Chip soft reset soon ***

*** NMI Watchdog interrupt on Core 0x01 ***
        $0      0x0000000000000000      at      0x0000000010108ce1
        v0      0x0000000000000001      v1      0x0000000000010000
        a0      0xffffffffc0010ae0      a1      0x0000000000007154
        a2      0x0000000000007155      a3      0x0000000000000000
        a4      0x0000000000000000      a5      0x800000041d14c1c0
        a6      0x0000000000000001      a7      0x0000000000000000
        t0      0x0000000000000400      t1      0x000000000001c000
        t2      0x000000000000000c      t3      0x800000041c0ac000
        s0      0x0000000000000000      s1      0xffffffffc0010918
        s2      0xffffffff805a0000      s3      0x0000000000000001
        s4      0x0000000000000000      s5      0xffffffffc0010000
        s6      0x0000000000000006      s7      0xffffffffc0010000
        t8      0x000000000042657c      t9      0xffffffff801a2b80
        k0      0x0000000000000000      k1      0x0000000000000000
        gp      0x800000041d7c4000      sp      0x800000041d7c7c10
        s8      0xffffffffc0017c30      ra      0xffffffffc00181c0
        err_epc 0xffffffff804b5f10      epc     0xffffffff801afc04
        status  0x0000000010588ce4      cause   0x0000000040808800
        sum0    0x000000f000008000      en0     0x0000000100000000
*** Chip soft reset soon ***

Looking for valid bootloader image....
Jumping to start of image at address 0xbfc80000

 

----------------------------------------------------------------------------

 

*** NMI Watchdog interrupt on Core 0x00 ***
        $0      0x0000000000000000      at      0x0000000050108ce1
        v0      0x0000000000000001      v1      0x0000000000010000
        a0      0xffffffffc0010ae0      a1      0x0000000000000000
        a2      0x00000000000057bc      a3      0x0000000000000000
        a4      0x0000000000000000      a5      0x800000041c0812f0
        a6      0x0000000000000001      a7      0x0000000000000000
        t0      0x0000000000000400      t1      0x000000000001c000
        t2      0x000000000000000c      t3      0xffffffff805a0000
        s0      0x0000000000000000      s1      0xffffffffc0010918
        s2      0xffffffff805a0000      s3      0x0000000000000001
        s4      0x0000000000000000      s5      0xffffffffc0010000
        s6      0x0000000000000006      s7      0xffffffffc0010000
        t8      0x0000000000000000      t9      0xffffffff801a2b80
        k0      0x0000000000000000      k1      0x0000000000000001
        gp      0x800000041c084000      sp      0x800000041c087c10
        s8      0xffffffffc0017c30      ra      0xffffffffc00181c0
        err_epc 0xffffffff804b5f04      epc     0xffffffffc007a660
        status  0x0000000050588ce4      cause   0x0000000040808c08
        sum0    0x000000f100008000      en0     0x0100400500008000
*** Chip soft reset soon ***

Looking for valid bootloader image....
Jumping to start of image at address 0xbfc80000

 

-----------------------------------------------------------------------------------------------

 

*** NMI Watchdog interrupt on Core 0x00 ***
        $0      0x0000000000000000      at      0x0000000000000001
        v0      0x0000000000000001      v1      0x0000000000010000
        a0      0xffffffffc0010ae0      a1      0x0000000000000002
        a2      0x0000000000002eb4      a3      0x8000000001680dd8
        a4      0x8000000081139000      a5      0x0000000000000010
        a6      0x0000000000000000      a7      0x0000000000000000
        t0      0xffffffffffffffff      t1      0x0000000000000000
        t2      0x0000000000000000      t3      0x0000000071780000
        s0      0xffffffffc000da30      s1      0xffffffffc0010000
        s2      0xffffffffc00151c0      s3      0x800000041d9ac000
        s4      0xfffffffffffffff4      s5      0x0000000000001000
        s6      0x0000000071770000      s7      0xffffffffc000d998
        t8      0x0000000000080000      t9      0x00000000771611a4
        k0      0x0000000072f86930      k1      0x0f00000010715747
        gp      0x800000041cf60000      sp      0x800000041cf63d50
        s8      0xffffffffc00151c0      ra      0xffffffffc00173bc
        err_epc 0xffffffff804b5f04      epc     0xffffffff804b5ac4
        status  0x0000000010588ce4      cause   0x0000000040808c08
        sum0    0x000000f000008000      en0     0x0100400500008000
*** Chip soft reset soon ***

*** NMI Watchdog interrupt on Core 0x01 ***
        $0      0x0000000000000000      at      0x0000000010108ce1
        v0      0x0000000000000001      v1      0x0000000000010000
        a0      0xffffffffc0010ae0      a1      0x0000000000000000
        a2      0x0000000000002eb3      a3      0x0000000000000000
        a4      0x0000000000000000      a5      0x800000041cc4b470
        a6      0x0000000000000001      a7      0x0000000000000000
        t0      0x0000000000000400      t1      0x000000000001c000
        t2      0x000000000000000c      t3      0x800000041c0a4000
        s0      0x0000000000000000      s1      0xffffffffc0010918
        s2      0xffffffff805a0000      s3      0x0000000000000001
        s4      0x0000000000000000      s5      0xffffffffc0010000
        s6      0x0000000000000006      s7      0xffffffffc0010000
        t8      0x0000000000000000      t9      0xffffffff801a2b80
        k0      0x0000000000000000      k1      0x0000000000000001
        gp      0x800000041ca10000      sp      0x800000041ca13c10
        s8      0xffffffffc0017c30      ra      0xffffffffc00181c0
        err_epc 0xffffffff804b5f00      epc     0xffffffffc007a660
        status  0x0000000010588ce4      cause   0x0000000040808808
        sum0    0x000000f000008000      en0     0x0000000100000000
*** Chip soft reset soon ***

Looking for valid bootloader image....
Jumping to start of image at address 0xbfc80000

 

 

---------------------------------------------------------------------------------

 

 

Member
Posts: 124
Registered: ‎08-13-2014
Kudos: 164

Re: Edgerouter POE crash console dump

How is people's testing of 1.7.0alpha2 going?

 

I'm at 2.9 days now where my average was running 1.5 days or less between watchdog events

New Member
Posts: 17
Registered: ‎01-07-2015
Kudos: 2

Re: Edgerouter POE crash console dump

I waited a bit to install, I am at 2 days and 18 hours.

Member
Posts: 113
Registered: ‎03-15-2014
Kudos: 65
Solutions: 4

Re: Edgerouter POE crash console dump


UBNT-ancheng wrote:

Thanks for providing the information. I have a potential fix that Stig is testing now, and so far so good, so it will probably be included in the next alpha/beta for testing and at that point you might want to give it a try.


Just to contribute, I read there's a potential fix implemented in version 1.7.0.  I am still running version 1.6.0 and if by any chance the potential fix has something to do with Hardware Offload, I experienced a crash in my ER-PoE having Hardware Offload disabled.  I appreciate the UBNT team looking after the different situations experienced.  Thanks guys!!

Member
Posts: 124
Registered: ‎08-13-2014
Kudos: 164

Re: Edgerouter POE crash console dump

Are people using switch0 directly or are you using 1/2 of switch0 and another port for something else?

 

My config using port 2-3 as switch0, and switch0.vlan and port 4 as another network seem to have crashing issues.

 

However sites with just a switch0 and nothing else, with hardware offload enabled have been stable for 30+ days.

 

1.7.0alpha2 seems to be improving things.  So stay tuned.

Member
Posts: 113
Registered: ‎03-15-2014
Kudos: 65
Solutions: 4

Re: Edgerouter POE crash console dump

[ Edited ]

jclendenan wrote:

Are people using switch0 directly or are you using 1/2 of switch0 and another port for something else?

 

My config using port 2-3 as switch0, and switch0.vlan and port 4 as another network seem to have crashing issues.

 

However sites with just a switch0 and nothing else, with hardware offload enabled have been stable for 30+ days.

 

1.7.0alpha2 seems to be improving things.  So stay tuned.


In my case I have:

 

eth0 - Connected to Cable Modem (Internet)

eth1 - Guest Network

eth2 - Switch0 (My LAN) - Connected to a drop that represents in the second floor, this goes to a switch.

eth3 - Switch0 (My LAN) - Connected to an Access Point in the first floor.

eth4 - Switch0 (My LAN) - Connected to Playstation 3.

 

I am not using vlans.

Previous Employee
Posts: 13,551
Registered: ‎06-10-2011
Kudos: 5429
Solutions: 1656
Contributions: 2

Re: Edgerouter POE crash console dump


mcmpr wrote:

UBNT-ancheng wrote:

Thanks for providing the information. I have a potential fix that Stig is testing now, and so far so good, so it will probably be included in the next alpha/beta for testing and at that point you might want to give it a try.


Just to contribute, I read there's a potential fix implemented in version 1.7.0.  I am still running version 1.6.0 and if by any chance the potential fix has something to do with Hardware Offload, I experienced a crash in my ER-PoE having Hardware Offload disabled.  I appreciate the UBNT team looking after the different situations experienced.  Thanks guys!!


No the fix is not related to offload so it may apply to the issue you observed as well.

New Member
Posts: 17
Registered: ‎01-07-2015
Kudos: 2

Re: Edgerouter POE crash console dump

I'm going to go out on a limb here and say I think the crashes have ceased since I installed v1.7alpha2

I have been up solid for 5 and a half days and was up for almost 5 before that.

(I had to reboot for a configuration change in the middle of that 10 day stretch).

 

crossing fingers and toes and many thanks for the help and support!

 

Bill

Member
Posts: 124
Registered: ‎08-13-2014
Kudos: 164

Re: Edgerouter POE crash console dump

One week,3 days so far for me. Much improved.

Would love to know what the root cause was for this one as it isn't nice and seems to be configuration dependent somehow.
Member
Posts: 113
Registered: ‎03-15-2014
Kudos: 65
Solutions: 4

Re: Edgerouter POE crash console dump

Yeah, +1 over here. It would be interesting what was the approach taken to work this issue.
Member
Posts: 113
Registered: ‎03-15-2014
Kudos: 65
Solutions: 4

Re: Edgerouter POE crash console dump

[ Edited ]

UBNT-ancheng wrote:

mcmpr wrote:

UBNT-ancheng wrote:

Thanks for providing the information. I have a potential fix that Stig is testing now, and so far so good, so it will probably be included in the next alpha/beta for testing and at that point you might want to give it a try.


Just to contribute, I read there's a potential fix implemented in version 1.7.0.  I am still running version 1.6.0 and if by any chance the potential fix has something to do with Hardware Offload, I experienced a crash in my ER-PoE having Hardware Offload disabled.  I appreciate the UBNT team looking after the different situations experienced.  Thanks guys!!


No the fix is not related to offload so it may apply to the issue you observed as well.


 

 

I just installed version 1.7.0 alpha 2 in another ER-PoE router with the same configuration as the ER-PoE I have at home with version 1.6.0 that has the rebooting issues since version 1.4.0.  Both are connected to a different cable modem connection and both were booted at the same time.  I am able to compare how does 1.7.0 alpha 2 device goes when the 1.6.0 device reboots.  Hopefully the router with version 1.7.0 will not reboot.  I'll keep you guys posted.

 

Note:  The router with version 1.7.0 alpha 2 did not get the time via NTP either, I had to manually force the date like I do with version 1.6.0.

Previous Employee
Posts: 13,551
Registered: ‎06-10-2011
Kudos: 5429
Solutions: 1656
Contributions: 2

Re: Edgerouter POE crash console dump

Thanks everyone for testing and confirming that the fix appears to be working. The fix was to rework the locking mechanism in the driver to simplify it which also makes it easier to follow the logic.

New Member
Posts: 17
Registered: ‎01-07-2015
Kudos: 2

Re: Edgerouter POE crash console dump

Uptime:1 month, 4 days, 14 hours

New Member
Posts: 1
Registered: ‎04-27-2015

Re: Edgerouter POE crash console dump

Latest beta, just had a crash.
Didnt read the console output though.

 

Was watching netflix and streaming for a couple of days.

New Member
Posts: 17
Registered: ‎01-07-2015
Kudos: 2

Re: Edgerouter POE crash console dump

I am up to 2 months, 2 weeks, 2 days uptime.

tons and tons and tons of Netflix and iTunes streaming along the more usual network traffic.

 

Bill

Reply