New Member
Posts: 6
Registered: ‎03-07-2013
Kudos: 1

Re: Is it dead?

Unfortunately also my router seems to have died. Previously the router's file system had ended up couple times in read-only mode but reboot always fixed this issue. However, during my holiday trip the router seems to have died and doesn't boot properly anymore. Pressing the reset button has no effect.

 

On the first reboot I got the following terminal output:

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


U-Boot 1.1.1 (UBNT Build ID: 4493936-g009d77b) (Build time: Sep 20 2012 - 15:48:
51)

BIST check passed.
UBNT_E100 r1:2, r2:12, serial #: DC9FDB293E9E
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM:  512 MB
Clearing DRAM....... done
Flash:  4 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 Flash Memory Rev: PMAP                  
            Type: Removable Hard Disk                                           
            Capacity: 3745.0 MB = 3.6 GB (7669824 x 512)                        
 0                                                                              
reading vmlinux.64                                                              
........................................                                        
                                                                                
8081560 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@3072k(eeprom)   
ELF file is 64 bit                                                              
Allocating memory for ELF segment: addr: 0xffffffff81100000 (adjusted to: 0x1100
000), size 0x7f2a90                                                             
Allocated memory for ELF segment: addr: 0xffffffff81100000, size 0x7f2a90       
Processing PHDR 0                                                               
  Loading 79a980 bytes at ffffffff81100000                                      
  Clearing 58110 bytes at ffffffff8189a980                                      
## Loading Linux kernel with entry point: 0xffffffff81105cd0 ...                
Bootloader: Done loading app on coremask: 0x3                                   
Linux version 2.6.32.13-UBNT (ancheng@ubnt-builder2) (gcc version 4.3.3 (Cavium 
Networks Version: 2_0_0 build 99) ) #1 SMP Tue Feb 26 11:01:13 PST 2013         
.
.
.                                           
INIT: version 2.88 booting                                                      
INIT: Entering runlevel: 2                                                      
Starting routing daemon: rib.                                                   
Starting EdgeOS router: migrate rl-system configureusb 1-1: device descriptor re
ad/64, error -71                                                                
usb 1-1: device descriptor read/all, error -71                                  
usb 1-1: device descriptor read/all, error -71                                  
end_request: I/O error, dev sda, sector 601088                                  
Aborting journal on device sda2.                                                
SQUASHFS error: squashfs_read_data failed to read block 0x2c8a05d               
SQUASHFS error: Unable to read data cache entry [2c8a05d]                       
SQUASHFS error: Unable to read page, block 2c8a05d, size 9b1c                   
...                
EXT3-fs error (device sda2): ext3_find_entry: reading directory #91591 offset 0 
...
SQUASHFS error: Unable to read data cache entry [2c8a05d]                       
SQUASHFS error: Unable to read page, block 2c8a05d, size 9b1c                   
...                 
EXT3-fs error (device sda2): ext3_find_entry: reading directory #91618 offset 0 
...
SQUASHFS error: Unable to read fragment cache entry [1e1e80f]                   
SQUASHFS error: Unable to read page, block 1e1e80f, size 79eb                   
SQUASHFS error: Unable to read fragment cache entry [1e1e80f]                   
SQUASHFS error: Unable to read page, block 1e1e80f, size 79eb                   
SQUASHFS error: squashfs_read_data failed to read block 0x2ce6f02               
SQUASHFS error: Unable to read data cache entry [2ce6f02]                       
SQUASHFS error: Unable to read page, block 2ce6f02, size 6be4                   
...                 
ext3_abort called.                                                              
EXT3-fs error (device sda2): ext3_journal_start_sb: Detected aborted journal    
Remounting filesystem read-only                                                 
EXT3-fs error (device sda2): ext3_find_entry: reading directory #91591 offset 0 
...
CPU 0 Unable to handle kernel paging request at virtual address 00000000000000b0
, epc == ffffffff8110ad6c, ra == ffffffff81242140                               
Oops[#1]:                                                                       
Cpu 0                                                                           
$ 0   : 0000000000000000 0000000000000000 0000000000010000 a80000041d302828     
$ 4   : 00000000000000b0 a80000041f423080 0000000000002109 a80000041d302780     
$ 8   : 0000000000000000 a80000041f5b9b80 0000000000000000 0000000000000001     
$12   : 0000000000000000 ffffffff81105b7c ffffffff81280490 0000000000000000     
$16   : 0000000000000000 a80000041d13c080 0000000000000000 a80000041f423080     
$20   : a80000041f0fa740 0000000000000000 a80000041f5b9b80 0000000000000000     
$24   : fffffffff0000000 ffffffff812fc690                                       
$28   : a80000041d384000 a80000041d387c10 0000000000000001 ffffffff81242140     
Hi    : 0000000000000000                                                        
Lo    : 0000000000000020                                                        
epc   : ffffffff8110ad6c 0xffffffff8110ad6c                                     
    Tainted: P        W                                                         
ra    : ffffffff81242140 0xffffffff81242140                                     
Status: 10008ce3    KX SX UX KERNEL EXL IE                                      
Cause : 00800008                                                                
BadVA : 00000000000000b0                                                        
PrId  : 000d0601 (Cavium Octeon+)                                               
Modules linked in: ip6table_mangle ip6table_filter ip6table_raw ip6_tables iptab
le_nat iptable_mangle xt_NOTRACK iptable_raw nf_nat_pptp nf_conntrack_pptp nf_co
nntrack_proto_gre nf_nat_h323 nf_conntrack_h323 nf_nat_sip nf_conntrack_sip nf_n
at_proto_gre nf_nat_tftp nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_c
onntrack_tftp nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables cv
m_ipsec_kame ipv6 cavium_ip_offload(P) octeon_rng rng_core octeon_ethernet mdio_
octeon ubnt_platform(P) libphy                                                  
Process sh (pid: 749, threadinfo=a80000041d384000, task=a80000041d0fcac0, tls=00
0000002ae02510)                                                                 
Stack : a80000041d302780 ffffffff812358b8 a80000041d265780 a80000041d13c080     
        a80000041a910370 0000000000000000 a80000041f061980 a80000041f328e00     
        0000000000000000 ffffffff812eb93c a80000041a910370 000000000000002a     
        a80000041d13c080 0000000000000000 a80000041a910370 a80000041f522d80     
        a80000041f328e00 ffffffff812eb4a0 a80000041f5b9b80 0000000000000000     
        00000000000001b6 ffffffff81235728 0000000000000000 a80000041f061980     
        000000000000210a ffffffffffffff9c 000000000000002a a80000041d387d20     
        0000000000002109 ffffffff81247194 a80000041f522d80 a80000041f328e00     
        0000000000000000 00000000811ad504 a80000041f522d80 a80000041f328e00     
        5e5079a000000008 a80000041d3b7005 a80000041f522d80 a80000041f0062c0     
        ...                                                                     
Call Trace:[<ffffffff812358b8>] 0xffffffff812358b8                              
[<ffffffff812eb93c>] 0xffffffff812eb93c                                         
[<ffffffff812eb4a0>] 0xffffffff812eb4a0                                         
[<ffffffff81235728>] 0xffffffff81235728                                         
[<ffffffff81247194>] 0xffffffff81247194                                         
[<ffffffff811acb08>] 0xffffffff811acb08                                         
[<ffffffff812354f4>] 0xffffffff812354f4                                         
[<ffffffff811042ec>] 0xffffffff811042ec                                         
[<ffffffff811a4ec8>] 0xffffffff811a4ec8                                         
                                                                                
                                                                                
Code: 00000000  00000000  3c020001 <c0830000> 00622821  e0850000  10a0fffc  0003
2c02  3063ffff                                                                  
Fatal exception: panic in 5 seconds                                             
scsi 2:0:0:0: Direct-Access              USB Flash Memory PMAP PQ: 0 ANSI: 0 CCS
sd 2:0:0:0: [sdb] 7669824 512-byte logical blocks: (3.92 GB/3.65 GiB)           
sd 2:0:0:0: [sdb] Write Protect is off                                          
usb-storage: device scan complete                                               
sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00                                       
sd 2:0:0:0: [sdb] Assuming drive cache: write through                           
sd 2:0:0:0: [sdb] Assuming drive cache: write through                           
 sdb:                                                                           
usb 1-1: reset high speed USB device using OcteonUSB and address 4              
 sdb1 sdb2                                                                      
sd 2:0:0:0: [sdb] Assuming drive cache: write through                           
sd 2:0:0:0: [sdb] Attached SCSI removable disk                                  
Kernel panic - not syncing: Fatal exception                                     
Rebooting in 60 seconds..                                                       
*** NMI Watchdog interrupt on Core 0x1 ***                                      
        $0      0x0000000000000000      at      0xffffffff818d0008              
        v0      0xffffffff81100b60      v1      0x0000000000000001              
        a0      0xfffffffffffffffd      a1      0x0000000000000000              
        a2      0xffffffff818e5aa8      a3      0xa800000080830000              
        a4      0x0000000000000001      a5      0xa8000000020ba100              
        a6      0x0000000000000000      a7      0x00000000000000bd              
        t0      0x0000000000000000      t1      0x000000001000001f              
        t2      0xa80000041f47c000      t3      0x0000000000000001              
        s0      0xffffffff818d0000      s1      0xa8000000020b94d0              
        s2      0x0000000000200000      s3      0x0000000000100100              
        s4      0xffffffff817ea680      s5      0x0000000000000002              
        s6      0xffffffffffffffff      s7      0x0000000000000038              
        t8      0x0000000000000000      t9      0xffffffff811dc010              
        k0      0x0000000000000000      k1      0x0000000000000000              
        gp      0xa80000041f46c000      sp      0xa80000041f46fbc0              
        s8      0xffffffff817eae88      ra      0xffffffff811a3398              
        err_epc 0xffffffff81100b80      epc     0xffffffff81100b80              
        status  0x00000000104888e4      cause   0x0000000040808c00              
        sum0    0x000000f100000000      en0     0x0000000300000000              
*** 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: 4493936-g009d77b) (Build time: Sep 20 2012 - 15:48:
51)                                                                             
                                                                                
BIST check passed.                                                              
UBNT_E100 r1:2, r2:12, serial #: DC9FDB293E9E                                   
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)                     
DRAM:  512 MB                                                                   
Clearing DRAM....... done                                                       
Flash:  4 MB                                                                    
Net:   octeth0, octeth1, octeth2                                                
                                                                                
USB:   (port 0) scanning bus for devices... USB device descriptor short read (ex
pected 18, got 0)                                                               
1 USB Devices found                                                             
       scanning bus for storage devices...                                      
No device found. Not initialized?                                               
 0                                                                              
** Can't read from device 0 **                                                  
                                                                                
** Unable to use usb 0:1 for fatload **                                         
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@3072k(eeprom)   
## No elf image at address 0x09f00000

 

 On the second attempt the router got stuck earlier:

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


U-Boot 1.1.1 (UBNT Build ID: 4493936-g009d77b) (Build time: Sep 20 2012 - 15:48:
51)

BIST check passed.
UBNT_E100 r1:2, r2:12, serial #: DC9FDB293E9E
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM:  512 MB

 Is there anything I can do to fix this?

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

Re: Is it dead?

Since you have access to the serial console, we can try some low-level tests to determine the issue. Please check your PM. Thanks.

New Member
Posts: 3
Registered: ‎04-02-2013

Re: Is it dead?

Hi

I also have the same problem

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


U-Boot 1.1.1 (UBNT Build ID: 4493936-g009d77b) (Build time: Sep 20 2012 - 15:48:51)

BIST check passed.
UBNT_E100 r1:2, r2:12, serial #: DC9FDB291B64
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM:  512 MB
"

can someone help?

thanks in advance

 

02-04-2013 19-06-31.jpg
New Member
Posts: 14
Registered: ‎03-30-2013

Re: Is it dead?

does this issue occur with only a handful of units? Or do they all suffer from this problem?

 

New Member
Posts: 3
Registered: ‎04-02-2013

Re: Is it dead?

the issue occur with only on one unit. i've only one!

New Member
Posts: 14
Registered: ‎03-30-2013

Re: Is it dead?

ah sorry it was meant as a global reply. Not a reply to your question. I'm just afraid to receive another faulty unit ...

Man Happy 

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

Re: Is it dead?


@Portugal wrote:

can someone help?

thanks in advance

 


Since you have access to the serial console, we can try some low-level tests to determine the issue. Please check your PM. Thanks.

New Member
Posts: 3
Registered: ‎04-02-2013

Re: Is it dead?

sorry but the only answer was and then only once, every other time stands still after DRAM:  512 MB

"

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


U-Boot 1.1.1 (UBNT Build ID: 4493936-g009d77b) (Build time: Sep 20 2012 - 15:48:51)

BIST check passed.
UBNT_E100 r1:2, r2:12, serial #: DC9FDB291B64
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM:  512 MB
Reg: 0x0 0x0
Reg: 0x1 0x1
Reg: 0x2 0xFFFFFFFFC00D9EF8
Reg: 0x3 0xFFFFFFFFFFFF99E9
Reg: 0x4 0xFFFFFFFFFFFFFFC3
Reg: 0x5 0xFFFFFFFFC00008E4
Reg: 0x6 0x80000
Reg: 0x7 0x3F
Reg: 0x8 0x10000000
Reg: 0x9 0x64814
Reg: 0xA 0xFFFFFFFFC0000AEC
Reg: 0xB 0x0
Reg: 0xC 0x48
Reg: 0xD 0x10000000000000
Reg: 0xE 0x20
Reg: 0xF 0x0
Reg: 0x10 0xFFFFFFFFFFFFFFFF
Reg: 0x11 0x41FFD9EF8
Reg: 0x12 0xFFFFFFFFFFFF99E8
Reg: 0x13 0x41FFD9FB8
Reg: 0x14 0x41FF00000
Reg: 0x15 0x800000041FF00000
Reg: 0x16 0x41FFD5EE0
Reg: 0x17 0x80000
Reg: 0x18 0xFFFFFFFFC0065300
Reg: 0x19 0xBDECCC0
Reg: 0x1A 0xFFFFFFFFFFFF8000
Reg: 0x1B 0x30
Reg: 0x1C 0xFFFFFFFFBFC65300
Reg: 0x1D 0xFFFFFFFFFFFF97F8
Reg: 0x1E 0xA89C196F513832DE
Reg: 0x1F 0xFFFFFFFFBFC00B80
sta0x504000E7
0aus-:  0x4000801C
e-c: 0x10000000
bvadr: 0x0
"

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

Re: Is it dead?

Did you see my PM about low-level testing? Thanks.

New Member
Posts: 6
Registered: ‎04-04-2013
Kudos: 3
Solutions: 1

Re: Is it dead?

Hello, i have the same issue. I managed to run the router twice, each time spending a couple of hours to configure it and then it would crash during the next few hours. Booting hangs after outputing this on the serial port:

 

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


U-Boot 1.1.1 (UBNT Build ID: 4493936-g009d77b) (Build time: Sep 20 2012 - 15:48:51)

BIST check passed.
UBNT_E100 r1:2, r2:12, serial #: DC9FDB2937A5
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM:  512 MB

 

The reset button doesn't do much. Probably the memory then. What can i do now?

Cheers.

 

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

Re: Is it dead?

Since you have access to the serial console, we can try some low-level tests to determine the issue. Please check your PM. Thanks.

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

EdgeRouter Bricked / Memory Issue Problem

[ Edited ]

Just want to provide an update on the DDR memory cases that some people have reported here:

 

  • Out of thousands of units that have been shipped so far, we have seen a small number of confirmed cases of DDR memory issue. Note that almost all confirmed cases were reported on the forum, so you are basically seeing all of them here (plus unconfirmed/unrelated ones).

  • The current number of confirmed cases is well below 1% of shipped units. We have received returned units back from some of these cases, and analysis shows that these units were damaged during the final assembly process. We expect this number to be limited.

  • We have already taken extra steps to address this in the assembly/manufacturing process. If you think your device may be affected (for example if it experiences random reboots), please contact support@ubnt.com and we can provide test instructions to help determine if your device has any issues.
Established Member
Posts: 901
Registered: ‎10-12-2012
Kudos: 893
Solutions: 39
Contributions: 1

Re: Is it dead?

Thanks for the update! Good to know that you are aware of what caused the issue and are correcting it.

New Member
Posts: 1
Registered: ‎04-09-2013

Re: Is it dead?

i think i got a dead one 2....

 


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


U-Boot 1.1.1 (UBNT Build ID: 4493936-g009d77b) (Build time: Sep 20 2012 - 15:48:51)

BIST check passed.
UBNT_E100 r1:2, r2:12, serial #: DC9FDB299B7C
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM: 512 MB
Clearing DRAM....... done
Flash: 4 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 Flash Memory Rev: PMAP
Type: Removable Hard Disk
Capacity: 3745.0 MB = 3.6 GB (7669824 x 512) 0
reading vmlinux.64
........................................

8081560 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@3072k(eeprom)
ELF file is 64 bit
Allocating memory for ELF segment: addr: 0xffffffff81100000 (adjusted to: 0x1100000), size 0x7f2a90
Allocated memory for ELF segment: addr: 0xffffffff81100000, size 0x7f2a90
Processing PHDR 0
Loading 79a980 bytes at ffffffff81100000
Clearing 58110 bytes at ffffffff8189a980
## Loading Linux kernel with entry point: 0xffffffff81105cd0 ...
Bootloader: Done loading app on coremask: 0x3
Linux version 2.6.32.13-UBNT (ancheng@ubnt-builder2) (gcc version 4.3.3 (Cavium Networks Version: 2_0_0 build 99) ) #1 SMP Wed Oct 24 01:08:06 PDT 2012
CVMSEG size: 2 cache lines (256 bytes)
Cavium Networks SDK-2.0
CPU revision is: 000d0601 (Cavium Octeon+)
Checking for the multiply/shift bug... no.
Checking for the daddiu bug... no.
Determined physical RAM map:
memory: 0000000000034000 @ 000000000186c000 (usable after init)
memory: 0000000006800000 @ 0000000001900000 (usable)
memory: 0000000007c00000 @ 0000000008200000 (usable)
memory: 000000000fc00000 @ 0000000410000000 (usable)
Wasting 350112 bytes for tracking 6252 unused pages
Zone PFN ranges:
DMA32 0x0000186c -> 0x00100000
Normal 0x00100000 -> 0x0041fc00
Movable zone start PFN for each node
early_node_map[4] active PFN ranges
0: 0x0000186c -> 0x000018a0
0: 0x00001900 -> 0x00008100
0: 0x00008200 -> 0x0000fe00
0: 0x00410000 -> 0x0041fc00
Cavium Hotplug: Available coremask 0x0
PERCPU: Embedded 10 pages/cpu @a8000000020b8000 s10624 r8192 d22144 u65536
pcpu-alloc: s10624 r8192 d22144 u65536 alloc=16*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 63895
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@3072k(eeprom) console=ttyS0,115200
PID hash table entries: 1024 (order: 1, 8192 bytes)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
Primary instruction cache 32kB, virtually tagged, 4 way, 64 sets, linesize 128 bytes.
Primary data cache 16kB, 64-way, 2 sets, linesize 128 bytes.
Memory: 483444k/491728k available (3478k kernel code, 8064k reserved, 4118k data, 208k init, 0k highmem)
Hierarchical RCU implementation.
NR_IRQS:152
Calibrating delay loop (skipped) preset value.. 1000.00 BogoMIPS (lpj=5000000)
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
IP route cache hash table entries: 2048 (order: 2, 16384 bytes)
TCP established hash table entries: 8192 (order: 5, 131072 bytes)
TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
/proc/octeon_perf: Octeon performace counter interface loaded
octeon_wdt: Initial granularity 5 Sec.
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering unionfs 2.5.11 (for 2.6.32.55)
msgmni has been set to 944
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1180000000800 (irq = 58) is a OCTEON
console [ttyS0] enabled
loop: module loaded
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
OcteonUSB: Detected 1 ports
OcteonUSB OcteonUSB.0: Octeon Host Controller
OcteonUSB OcteonUSB.0: new USB bus registered, assigned bus number 1
OcteonUSB OcteonUSB.0: irq 80, io mem 0x00000000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
OcteonUSB: Registered HCD for port 0 on irq 80
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver libusual
Probing USB hub...
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
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 4MB flash at 0x1f800000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
phys_mapped_flash: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
3 cmdlinepart partitions found on MTD device phys_mapped_flash
Creating 3 MTD partitions on "phys_mapped_flash":
0x000000000000-0x000000080000 : "boot0"
0x000000080000-0x000000100000 : "boot1"
0x000000300000-0x000000310000 : "eeprom"
Waiting 15sec before mounting root device...
hub 1-0:1.0: activate --> -22
usb 1-1: new high speed USB device using OcteonUSB and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
scsi 0:0:0:0: Direct-Access USB Flash Memory PMAP PQ: 0 ANSI: 0 CCS
sd 0:0:0:0: [sda] 7669824 512-byte logical blocks: (3.92 GB/3.65 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1 sda2
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 5 seconds
EXT3 FS on sda2, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with writeback data mode.
VFS: Mounted root (unionfs filesystem) on device 0:12.
Freeing unused kernel memory: 208k freed
Algorithmics/MIPS FPU Emulator v1.5
INIT: version 2.88 booting
INIT: Entering runlevel: 2
Starting routing daemon: rib.
Starting EdgeOS router: migrate rl-system configure.

Welcome to EdgeOS ubnt ttyS0

By logging in, accessing, or using the Ubiquiti product, you
acknowledge that you have read and understood the Ubiquiti
License Agreement (available in the Web UI at, by default,
http://192.168.1.1) and agree to be bound by its terms.

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


U-Boot 1.1.1 (UBNT Build ID: 4493936-g009d77b) (Build time: Sep 20 2012 - 15:48:51)

BIST check passed.
UBNT_E100 r1:2, r2:12, serial #: DC9FDB299B7C
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM: 512 MB

 

 

then noting happends...

 

an no respond on ip or console

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

Re: Is it dead?

As mentioned above, if you think your device may be affected, please contact support@ubnt.com and we can help you troubleshoot. Thanks.

New Member
Posts: 1
Registered: ‎04-10-2013

Re: Is it dead?

Got similar problem as ppl in this thread. Router boots up and then crashes after a minute uptime.

 

fw01 login: Trap instruction in kernel code[#1]:
Cpu 0
$ 0   : 0000000000000000 0000000000000018 ffffffffa8000000 ffffffff811bb110
$ 4   : a8000000020ba100 a800000080820000 0000000000000000 0000000000000000
$ 8   : 0000000000000000 a8000000020ca100 0000000000000000 0000000000000001
$12   : 0000000000000000 ffffffff81105b64 ffffffff811f87d8 0000000000000000
$16   : 000001a800000002 0000000000000000 a8000000020ba100 0000000000000000
$20   : a80000041f4cd540 0000000000000000 0000000000000000 000000007fc9c600
$24   : 0000000000000000 000000002ad4be28                                  
$28   : a80000041e400000 a80000041e403c48 000000007fc9c60c ffffffff811081a8
Hi    : 000000000000000a
Lo    : 000000000000000f
epc   : ffffffff811bb15c 0xffffffff811bb15c
    Tainted: P          
ra    : ffffffff811081a8 0xffffffff811081a8
Status: 10108ce2    KX SX UX KERNEL EXL 
Cause : 80800034
PrId  : 000d0601 (Cavium Octeon+)
Modules linked in: 8021q garp stp llc ipt_MASQUERADE xt_iprange ipt_LOG xt_tcpudp xt_state xt_comment ip6table_mangle ip6table_filter ip6table_raw ip6_tables iptable_nat iptable_mangle xt_NOTRACK iptable_raw nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_h323 nf_conntrack_h323 nf_nat_sip nf_conntrack_sip nf_nat_proto_gre nf_nat_tftp nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables cvm_ipsec_kame ipv6 cavium_ip_offload(P) octeon_rng rng_core octeon_ethernet mdio_octeon ubnt_platform(P) libphy
Process ubnt-daemon (pid: 382, threadinfo=a80000041e400000, task=a80000041f4cd540, tls=000000002ac7b5d0)
Stack : 0000000000000000 0000000000000000 a80000041e403cf0 0000000000000002
        a80000041e403ce0 a8000000020b90c8 0000000000000000 000000001dab4090
        a80000041f4cd540 0000000000000000 0000000000000001 a8000000020ba100
        0000000000000000 a80000041f4cd540 0000000000000000 0000000000000000
        0000000000000001 a8000000020ba100 ffffffff811083f0 0000000000000000
        a8000000020b9338 0000000000000000 a8000000020b9338 0000000000000001
        00000000ffffb679 a80000041f4cd7b8 a8000000020b90c8 0000000000000000
        ffffffff811e4434 a80000041f4cd7b8 ffffffff818de380 ffffffff818990c8
        a80000041e403dc0 a80000041e403dc0 0000000000000001 0000000000000001
        0000000000000000 0000000000410000 0000000000043a00 000000007fc9c604
        ...
Call Trace:[<ffffffff811083f0>] 0xffffffff811083f0
[<ffffffff811e4434>] 0xffffffff811e4434
[<ffffffff81109d94>] 0xffffffff81109d94
[<ffffffff811e4728>] 0xffffffff811e4728
[<ffffffff811e35b0>] 0xffffffff811e35b0
[<ffffffff811f8868>] 0xffffffff811f8868
[<ffffffff811042ec>] 0xffffffff811042ec
[<ffffffffc0000000>] 0xffffffffc0000000
 
 
Looking for valid bootloader image....
Jumping to start of image at address 0xbfc80000
 
 
U-Boot 1.1.1 (UBNT Build ID: 4493936-g009d77b) (Build time: Sep 20 2012 - 15:48:51)
 
BIST check passed.
UBNT_E100 r1:2, r2:12, serial #: DC9FDB29A443
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM:  512 MB
Previous Employee
Posts: 13,551
Registered: ‎06-10-2011
Kudos: 5479
Solutions: 1656
Contributions: 2

Re: Is it dead?

As mentioned above, if you think your device may be affected, please contact support@ubnt.com and we can help you troubleshoot. Thanks.

New Member
Posts: 1
Registered: ‎05-06-2013

Re: Is it dead?

Hello!

 

It's seems that I'm also have the same issue.

My ERL frequently restarting and hangs while loading.

 

Log attached to this post.

Also I open ticket at support@ubnt.com.

 

Regards, Eugene.

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

Re: Is it dead?

Yes, support will be able to help you troubleshoot. Thanks.

New Member
Posts: 1
Registered: ‎06-13-2013

Re: Is it dead?

Same problem here. A couple of nights ago EdgeRouter simply froze. I tried the reset, it didn't blink, so I am stuck as soon as the power starts with console right led on, with no cable attached and when I attach an Ethernet cable on any port it only activates the right led. I obviously have no response from the router.

I will try to get my hands on a Cisco cable, I am sure I have one somewhere. Ill get back with more details.