1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

What is this error log?

Discussion in 'Tomato Firmware' started by Sunspark, Sep 6, 2007.

  1. Sunspark

    Sunspark LI Guru Member

    This morning the power was unplugged to the modem and the router. I could log into the router through the web interface via wireless, but it wasn't able to establish a PPPoE to the modem, and when I looked at the log, I saw the below. After I rebooted the router through the web interface it was fine again. But I am wondering if the kernel stuff is a hardware thing, or a software.

    Jan 1 04:59:04 bitflinger daemon.info dnsmasq[958]: DHCPREQUEST(br0) 192.168.1.143 00:13:72:e3:ee:67
    Jan 1 04:59:04 bitflinger daemon.info dnsmasq[958]: DHCPACK(br0) 192.168.1.143 00:13:72:e3:ee:67 scarerin
    Jan 1 05:00:05 bitflinger syslog.info -- MARK --
    Jan 1 05:00:54 bitflinger user.alert kernel: Unable to handle kernel paging request at virtual address 000000e8, epc == 80097c28, ra == 80097c00
    Jan 1 05:00:54 bitflinger user.warn kernel: Oops in fault.c::do_page_fault, line 192:
    Jan 1 05:00:54 bitflinger user.warn kernel: $0 : 00000000 80174ba4 00000001 000000d6 81e62790 00000000 00000000 00000008
    Jan 1 05:00:54 bitflinger user.warn kernel: $8 : 000000d6 ffffffda 00000010 6c76d6d2 3b211b10 00000014 00000000 55d56ae4
    Jan 1 05:00:54 bitflinger user.warn kernel: $16: 801827e8 81a5c9e0 81e62960 00000000 81c89e98 7fff7c30 00000001 7fff70b8
    Jan 1 05:00:54 bitflinger user.warn kernel: $24: 00000010 2ab2bc50 81c88000 81c89e58 00000000 80097c00
    Jan 1 05:00:54 bitflinger user.warn kernel: Hi : 00000000
    Jan 1 05:00:54 bitflinger user.warn kernel: Lo : 0000004b
    Jan 1 05:00:54 bitflinger user.warn kernel: epc : 80097c28 Not tainted
    Jan 1 05:00:54 bitflinger user.warn kernel: Status: 1000fc03
    Jan 1 05:00:54 bitflinger user.warn kernel: Cause : 00000008
    Jan 1 05:00:54 bitflinger user.warn kernel: Process pppoecd (pid: 943, stackpage=81c88000)
    Jan 1 05:00:54 bitflinger user.warn kernel: Stack: 819df008 819df008 7fff772d 0000059b 10020680 81a54938 0000001e
    Jan 1 05:00:54 bitflinger user.warn kernel: 0000001a 7fff7e24 7fff7c30 800b0eb4 800b0e70 63880011 00000005 06000001
    Jan 1 05:00:54 bitflinger user.warn kernel: a01a9000 00000018 12090000 a01a9000 6c76d6d2 00316e61 00000000 00000000
    Jan 1 05:00:54 bitflinger user.warn kernel: 00000000 00000001 80049590 81cffb40 00000004 7fff7cb8 00000023 80049720
    Jan 1 05:00:54 bitflinger user.warn kernel: 800497c4 8006c068 10000e80 81c89f00 00000014 81cffb40 81cffb44 81c89f30
    Jan 1 05:00:54 bitflinger user.warn kernel: ffffffff ...
    Jan 1 05:00:54 bitflinger user.warn kernel: Call Trace: [<800b0eb4>] [<800b0e70>] [<80049590>] [<80049720>] [<800497c4>]
    Jan 1 05:00:54 bitflinger user.warn kernel: [<8006c068>] [<80008a64>] [<800085a4>]
    Jan 1 05:00:54 bitflinger user.warn kernel:
    Jan 1 05:00:54 bitflinger user.warn kernel: Code: 00000000 8e450024 24020001 <c0a400e8> 00821823 e0a300e8 1060fffc 00821823 0000000f
     
  2. roadkill

    roadkill Super Moderator Staff Member Member

    I saw this a couple of times the most common reason is that the router is out of memory,
    if you use HOSTS based ad blocking scripts it can be the cause too because it tends to use a lot of ram
    and you can also check how much concurrent connections (Advanced >Conntrack / Netfilter > Connections)
    you have because too much will also give you that result eventually..

    :grin:
     

Share This Page