ExtremeSwitching (EXOS)

Expand all | Collapse all

Kern.Alert>CPU 1 Unable to handle kernel paging request at virtual address 0000000000000000, epc == 0000000000000000, ra == ffffffffc057a1b0

  • 1.  Kern.Alert>CPU 1 Unable to handle kernel paging request at virtual address 0000000000000000, epc == 0000000000000000, ra == ffffffffc057a1b0

    Posted 03-16-2017 15:48
    Crit:Kern.Alert> CPU 1 Unable to handle kernel paging request at virtual address 0000000000000000, epc == 0000000000000000, ra == ffffffffc057a1b0

    We have an X480-48X switch , we have changed the hardware by RMA and upgraded the code to the advised level ( previous 16.1.3.6-patch1-11 ), we have had a TAC case open, even with this we are still seeing ramdom reboots.

    Full version :

    xpctRebootDtect> Booting after System Failure.03/15/2017 15:41:41.84


  • 2.  RE: Kern.Alert>CPU 1 Unable to handle kernel paging request at virtual address 0000000000000000, epc == 0000000000000000, ra == ffffffffc057a1b0

    Posted 03-16-2017 16:25
    Hello Rod,

    What switch and version?


  • 3.  RE: Kern.Alert>CPU 1 Unable to handle kernel paging request at virtual address 0000000000000000, epc == 0000000000000000, ra == ffffffffc057a1b0

    Posted 03-16-2017 17:05
    Sorry Rod,

    I missed this information...my bad.

    Let me look into it for you.


  • 4.  RE: Kern.Alert>CPU 1 Unable to handle kernel paging request at virtual address 0000000000000000, epc == 0000000000000000, ra == ffffffffc057a1b0

    Posted 03-16-2017 21:18
    Rod, I think you should share the dmesg o/p with TAC engineer to further troubleshoot issue. It seems the issue you were facing in old version is not resolved in new version tool

    Looking at above o/p it's difficult to understand why code is referencing at VA 0000000000000000, epc == 0000000000000000



  • 5.  RE: Kern.Alert>CPU 1 Unable to handle kernel paging request at virtual address 0000000000000000, epc == 0000000000000000, ra == ffffffffc057a1b0

    Posted 03-16-2017 21:32
    Note to TAC:

    TAC needs to check if there is any invalid pointer present in SuperVlan's code that is trying to access invalid address. In the error message there is also the stack, take a look at it in order to identify where is the error.


  • 6.  RE: Kern.Alert>CPU 1 Unable to handle kernel paging request at virtual address 0000000000000000, epc == 0000000000000000, ra == ffffffffc057a1b0

    Posted 03-21-2017 15:39
    We do have a basic miss configured Supervlan ( in different VR's ) its historical , and we are trying to address this .. the swicth was stable for years ( well 2 ) then we started to see these random reboots ..



  • 7.  RE: Kern.Alert>CPU 1 Unable to handle kernel paging request at virtual address 0000000000000000, epc == 0000000000000000, ra == ffffffffc057a1b0

    Posted 03-31-2017 08:01
    The switch configuration has now been modified so that all sub vlans are in the same VR as the super vlan .. we will continue to monitor and see if the switch reboots again without warning.



  • 8.  RE: Kern.Alert>CPU 1 Unable to handle kernel paging request at virtual address 0000000000000000, epc == 0000000000000000, ra == ffffffffc057a1b0

    Posted 05-29-2017 19:41
    Could this also happen with EAPS config's ?


  • 9.  RE: Kern.Alert>CPU 1 Unable to handle kernel paging request at virtual address 0000000000000000, epc == 0000000000000000, ra == ffffffffc057a1b0

    Posted 03-16-2017 16:25
    Sorry for the delay X480-48X

    16.1.3.6-patch1-11 ( as advised by original TAC case )