SRX

Expand all | Collapse all

SRX 240 won't boot - cpu:0-Trap cause = 2 (TLB miss (load or instr. fetch)

Jump to Best Answer
  • 1.  SRX 240 won't boot - cpu:0-Trap cause = 2 (TLB miss (load or instr. fetch)

    Posted 06-04-2014 02:00

    My srx 240 won't boot anymore at the console I see:

     

    uhub0: 1 port with 1 removable, self powered
    uhub1: vendor 0x0409 product 0x005a, class 9/0, rev 2.00/1.00, addr 2
    uhub1: single transaction translator
    uhub1: 3 ports with 2 removable, self powered
    umass0: STMicroelectronics ST72682  High Speed Mode, rev 2.00/2.10, addr 3
    umass1: Kingston DataTraveler 111, rev 2.10/1.10, addr 4
    dwc1: <Synopsis DWC OTG Controller Driver> on obio0
    usb1: <USB Bus for DWC OTG Controller> on dwc1
    usb1: USB revision 2.0
    uhub2: vendor 0x0000 DWC OTG root hub, class 9/0, rev 2.00/1.00, addr 1
    uhub2: 1 port with 1 removable, self powered
    cpld0 on obio0
    pcib1: <Cavium on-chip PCIe HOST bridge> on obio0
    Disabling Octeon big bar support
    PCIe: Waiting for port 1 to finish reset
    PCIe: Port 1 link active, 1 lanes
    pcib1: Initialized controller
    pci0: <PCI bus> on pcib1
    pcib0: <PCI-PCI bridge> irq 0 at device 0.0 on pci0
    pci1: <PCI bus> on pcib0
    pci1: <serial bus, USB> at device 2.0 (no driver attached)
    pci1: <network> at device 7.0 (no driver attached)
    gblmem0 on obio0
    octpkt0: <Octeon RGMII> on obio0
    cfi0: <AMD/Fujitsu - 4MB> on obio0
    Timecounter "mips" frequency 600000000 Hz quality 0
    ###PCB Group initialized for udppcbgroup
    ###PCB Group initialized for tcppcbgroup
    dwc_otg_nandflash_bulk_flush+0x54 (0x10000,0,0,0x80010700) ra 0x8080e664 sz 64
    dwcshutdown+0x84 (0x10000,0,0,0x80010700) ra 0x808336ac sz 40
    cpld_device_intr+0x2b4 (0x10000,0,0,0x80010700) ra 0x807b1c18 sz 56
    mips_handle_this_interrupt+0x8c (0x10000,0,0,0x80010700) ra 0x807b1cac sz 40
    mips_handle_interrupts+0x60 (0x10000,0,0,0x80010700) ra 0x807b20d8 sz 48
    mips_interrupt+0x22c (0x10000,0,0,0x80010700) ra 0x80a3ce44 sz 32
    MipsKernIntr+0x140 (0x1,0x80d3d848,0xffff8010,0x80d3d848) ra 0x807b1520 sz 368
    spinlock_exit+0x84 (0x1,0x80d3d848,0xffff8010,0x80d3d848) ra 0x801fd2f0 sz 24
    fork_exit+0x250 (0x1,0x80d3d848,0xffff8010,0x80d3d848) ra 0x80a3dad0 sz 48
    MipsNMIException+0x34 (0x1,0x80d3d848,0xffff8010,0x80d3d848) ra 0 sz 0
    pid 10, process: ktrace
    cpu:0-Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode)
    badvaddr = 0, pc = 0x8080efc8, ra = 0x8080ef9c, sr = 0x508008a3
    [thread pid 10 tid 100006 ]
    Stopped at      dwc_otg_nandflash_bulk_flush+0x54:      lw      s4,0(v0)
    db>

     

    I have tried the following to fix this problem.

    loader> install file:///junos-srxsme-12.1X46-D20.5-domestic.tgz --format

    To install a complete new version of junos from a USB stick.

    I did this with multiple version junos, but I got the same error as above.

     

    Is there anyone who has encountered this problem before, and know how to fix this.

     



  • 2.  RE: SRX 240 won't boot - cpu:0-Trap cause = 2 (TLB miss (load or instr. fetch)

     
    Posted 06-04-2014 02:02

    You are seeing this error because of file system or boot loader corruption.

    Can you try installing Junos via TFTP method?

     

    http://www.juniper.net/techpubs/software/junos-security/junos-security10.2/junos-security-admin-guide/section-srx-series-tftp-loader.html

     

    Regards,

    Raveen



  • 3.  RE: SRX 240 won't boot - cpu:0-Trap cause = 2 (TLB miss (load or instr. fetch)

    Posted 06-04-2014 12:30

    Thanks for your response.

    But it is not the solution for my problem.

     

    When the SRX gets the image from my tftp server.

    It loads the kernel and then it crashed with the same error as I had before:

    cpu:0-Trap cause = 2 (TLB miss (load or instr. fetch)
     

    If you need more information, please let me know.



  • 4.  RE: SRX 240 won't boot - cpu:0-Trap cause = 2 (TLB miss (load or instr. fetch)
    Best Answer

     
    Posted 06-04-2014 19:15

    Hello wouter

     

    If neither usb method nor tftp method helped you.

    Then your CF would have gone bad, which is a hardware problem that needs RMA.

    Please open up a case with JTAC and request for replacement device.

     

    Regards,

    Raveen



  • 5.  RE: SRX 240 won't boot - cpu:0-Trap cause = 2 (TLB miss (load or instr. fetch)

    Posted 06-29-2020 14:48

    My vintage 2013 SRX210 recently went offline unexpectedly.  During all reboots, the kernel startup halts at the same point:

    ...

    PCI Status: PCI 32-bit: 0xc041b
    pcib0: Initialized controller
    pci0: <PCI bus> on pcib0
    pci0: <simple comms> at device 1.0 (no driver attached)
    pci0: <serial bus, USB> at device 2.0 (no driver attached)
    pci0: <serial bus, USB> at device 2.1 (no driver attached)
    pci0: <serial bus, USB> at device 2.2 (no driver attached)
    gblmem0 on obio0
    octpkt0: <Octeon RGMII> on obio0
    cfi0: <AMD/Fujitsu - 4MB> on obio0
    Timecounter "mips" frequency 600000000 Hz quality 0
    ###PCB Group initialized for udppcbgroup
    ###PCB Group initialized for tcppcbgroup
    dwc_otg_nandflash_bulk_flush+0x54 (0x10000,0,0,0x80010700) ra 0x80872f10 sz 64
    dwcshutdown+0x84 (0x10000,0,0,0x80010700) ra 0x80893820 sz 40
    gpio_srx210_poweroff_intr_handler+0xa0 (0x10000,0,0,0x80010700) ra 0x808151dc sz 24
    mips_handle_this_interrupt+0x8c (0x10000,0,0,0x80010700) ra 0x80815268 sz 40
    mips_handle_interrupts+0x58 (0x10000,0,0,0x80010700) ra 0x8081568c sz 48
    mips_interrupt+0x224 (0x10000,0,0,0x80010700) ra 0x80aaf4c4 sz 32
    MipsKernIntr+0x140 (0x1,0x80da89e8,0xffff8010,0x80da89e8) ra 0x80814ab4 sz 368
    spinlock_exit+0x84 (0x1,0x80da89e8,0xffff8010,0x80da89e8) ra 0x801ffee0 sz 24
    fork_exit+0x24c (0x1,0x80da89e8,0xffff8010,0x80da89e8) ra 0x80ab0150 sz 48
    MipsNMIException+0x34 (0x1,0x80da89e8,0xffff8010,0x80da89e8) ra 0 sz 0
    pid 23, process: swi7: clock
    cpu:0-Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode)
    badvaddr = 0, pc = 0x8087389c, ra = 0x80873870, sr = 0x508008a3
    ###Not a panic, mastership retained
    [thread pid 23 tid 100007 ]
    Stopped at dwc_otg_nandflash_bulk_flush+0x54: lw s4,0(v0)

    db>

     

    Dumping all of the processes shows that pid 23 is failing in the clock(3) kernel call.

     

    db> alltrace

    Tracing command swi1: ipfwd pid 37 tid 100043 td 0xc380e440
    SP 0: not in kernel
    uart_sab82532_class+0x0 (0,0,0,0) ra 0 sz 0
    pid 37, process: swi1: ipfwd

    Tracing command swi4: ip6mismatch+ pid 36 tid 100044 td 0xc380e220
    SP 0: not in kernel
    uart_sab82532_class+0x0 (0,0,0,0) ra 0 sz 0
    pid 36, process: swi4: ip6mismatch+

    ...

    Tracing command swi2: netisr 0 pid 25 tid 100022 td 0xc36cd000
    SP 0: not in kernel
    uart_sab82532_class+0x0 (0,0,0,0) ra 0 sz 0
    pid 25, process: swi2: netisr 0

    Tracing command swi6: vm pid 24 tid 100023 td 0xc36bfcc0
    SP 0: not in kernel
    uart_sab82532_class+0x0 (0,0,0,0) ra 0 sz 0
    pid 24, process: swi6: vm

    Tracing command swi7: clock pid 23 tid 100007 td 0xc36ba000
    dwc_otg_nandflash_bulk_flush+0x54 (0,0,0,0) ra 0x808757c0 sz 64
    dwcshutdown+0x84 (0,0,0,0) ra 0x808960d0 sz 40
    gpio_srx210_poweroff_intr_handler+0xa0 (0,0,0,0) ra 0x80817a8c sz 24
    mips_handle_this_interrupt+0x8c (0,0,0,0) ra 0x80817b18 sz 40
    mips_handle_interrupts+0x58 (0,0,0,0) ra 0x80817f3c sz 48
    mips_interrupt+0x224 (0,0,0,0) ra 0x80ab1d44 sz 32
    MipsKernIntr+0x140 (0x1,0x80dab9e8,0xffff8010,0x80dab9e8) ra 0x80817364 sz 368
    spinlock_exit+0x84 (0x1,0x80dab9e8,0xffff8010,0x80dab9e8) ra 0x801ffee0 sz 24
    fork_exit+0x24c (0x1,0x80dab9e8,0xffff8010,0x80dab9e8) ra 0x80ab29d0 sz 48
    MipsNMIException+0x34 (0x1,0x80dab9e8,0xffff8010,0x80dab9e8) ra 0 sz 0
    pid 23, process: swi7: clock

    Tracing command idle: cpu0 pid 22 tid 100008 td 0xc36bf440
    SP 0: not in kernel
    uart_sab82532_class+0x0 (0,0,0,0) ra 0 sz 0
    pid 22, process: idle: cpu0

    Tracing command idle: cpu1 pid 21 tid 100009 td 0xc36bf220
    SP 0: not in kernel
    uart_sab82532_class+0x0 (0,0,0,0) ra 0 sz 0
    pid 21, process: idle: cpu1

     

    The mention of clock, combined with the age of the machine and the fact that is had been switched off for an extended period time led me to suspect the CMOS battery was flat.

     

    Replacing the CMOS battery - a standard CR2032 coin cell - brought the machine fully back to life.