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

kernel errors (Oops) related to pppoecd

Discussion in 'Tomato Firmware' started by CrLf, Apr 12, 2007.

  1. CrLf

    CrLf LI Guru Member

    I'm getting these errors on my WRT54G with Tomato 1.06 ocasionally. It doesn't seem to cause any observable problems though...

    Anybody else seeing this?

    Apr 9 18:38:59 gw user.alert kernel: Unable to handle kernel paging request at virtual address 000000e8, epc == 80097c28, ra == 80097c00
    Apr 9 18:38:59 gw user.warn kernel: Oops in fault.c::do_page_fault, line 192:
    Apr 9 18:38:59 gw user.warn kernel: $0 : 00000000 80174ba4 00000001 000000d8 80d1aa10 00000000 00000000 00000008
    Apr 9 18:38:59 gw user.warn kernel: $8 : 000000d8 ffffffbd 00000010 6c76d82b 10011002 00000014 00000000 00000a00
    Apr 9 18:38:59 gw user.warn kernel: $16: 801827e8 80ccd060 80d1ab60 00000000 80e67e98 7fff7c80 00000000 00000000
    Apr 9 18:38:59 gw user.warn kernel: $24: 00000010 2ab2bcf0 80e66000 80e67e58 00000000 80097c00
    Apr 9 18:38:59 gw user.warn kernel: Hi : 00000000
    Apr 9 18:38:59 gw user.warn kernel: Lo : 00000000
    Apr 9 18:38:59 gw user.warn kernel: epc : 80097c28 Not tainted
    Apr 9 18:38:59 gw user.warn kernel: Status: 1000fc03
    Apr 9 18:38:59 gw user.warn kernel: Cause : 00000008
    Apr 9 18:38:59 gw user.warn kernel: Process pppoecd (pid: 14840, stackpage=80e66000)
    Apr 9 18:38:59 gw user.warn kernel: Stack: 8080f008 8080f008 7fff774b 0000059d 10020680 8068f778 0000001e
    Apr 9 18:38:59 gw user.warn kernel: 00000018 7fff7e44 7fff7c80 800b0eb4 800b0e70 63880011 00000005 06000001
    Apr 9 18:38:59 gw user.warn kernel: 3e7f1400 00000018 01000000 3e7f1400 6c76d82b 00316e61 00000000 00000000
    Apr 9 18:38:59 gw user.warn kernel: 00000000 00000001 80049590 80faf7e0 00000004 7fff7cd8 00000023 80049720
    Apr 9 18:38:59 gw user.warn kernel: 800497c4 8006c068 00aecfad 80e67f00 00000014 80faf7e0 80faf7e4 80e67f30
    Apr 9 18:38:59 gw user.warn kernel: ffffffff ...
    Apr 9 18:38:59 gw user.warn kernel: Call Trace: [<800b0eb4>] [<800b0e70>] [<80049590>] [<80049720>] [<800497c4>]
    Apr 9 18:38:59 gw user.warn kernel: [<8006c068>] [<80008a64>] [<800085a4>]
    Apr 9 18:38:59 gw user.warn kernel:
    Apr 9 18:38:59 gw user.warn kernel: Code: 00000000 8e450024 24020001 <c0a400e8> 00821823 e0a300e8 1060fffc 00821823 0000000f
     
  2. der_Kief

    der_Kief Super Moderator Staff Member Member

    Hi,

    i never see this before or even had this problem in my envoirment. Can you reproduce the things you made at the time the error(s) got logged ? Maybe you should email Jon about this.

    der_Kief
     
  3. digitalgeek

    digitalgeek Network Guru Member

    Have you tried a clear nvram and re-conifg manually?
     
  4. CrLf

    CrLf LI Guru Member

    That's just it, I did nothing. Those errors are rare, and they happen while the router is working all by itself, not when changing stuff in the configuration or anything like that.

    I can't reproduce them, that's why I wanted to see if anyone else was seeing this, to maybe get some more information (at least if the oopses are similar or something).

    And yes, I've tried to reset the router (pressing the reset button on the back). The errors became much less frequent (more than one a day at first, but since the reset the one I posted above is the first since the router was booted -- 6 days ago).

    BTW, before the oops I have the following messages (don't know if they are related, but the fact they happened in the very same second makes me suspicious)...

    Apr 9 18:38:58 gw daemon.info dnsmasq[14922]: exiting on receipt of SIGTERM
    Apr 9 18:38:59 gw daemon.info dnsmasq[14941]: started, version 2.38 cachesize 150
    Apr 9 18:38:59 gw daemon.info dnsmasq[14941]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Apr 9 18:38:59 gw daemon.info dnsmasq[14941]: DHCP, IP range 192.168.0.100 -- 192.168.0.128, lease time 3h
    Apr 9 18:38:59 gw daemon.info dnsmasq[14941]: reading /etc/dmresolv.conf
    Apr 9 18:38:59 gw daemon.info dnsmasq[14941]: using nameserver xxx.xxx.xxx.xxx#53
    Apr 9 18:38:59 gw daemon.info dnsmasq[14941]: read /etc/hosts - 0 addresses
    Apr 9 18:38:59 gw daemon.info dnsmasq[14941]: read /etc/dmhosts - 6 addresses
     
  5. digitalgeek

    digitalgeek Network Guru Member

    This all looks normal...
     
  6. LadFromWales85

    LadFromWales85 Network Guru Member

    I've found since 1.06 that pppoecd doesn't always exit cleanly. Viewing the syslog shows similar errors as are shown in the first post. Usually ends up with several copies of pppoecd running, and no connection until a 'killall pppoed' is issued. I cannot reproduce the problem now, as I only noticed it when I had a line fault causing my dsl modem to constantly lose sync.
     
  7. digitalgeek

    digitalgeek Network Guru Member

    How many guys require a 24hr disconnect... I wonder if this problem is related to that and how Crlf is restarting his connection? I have never had any problems with my PPPoE connection (knock on wood) keep alive works very well.
     
  8. Tristanxy

    Tristanxy Guest

    got the same problem here. flashed back to tomato 1.04 ... didn't do the trick.
    anyone got a solution for the prob yet? this constant line dropping really IS anoying. i allready called my ISP cause of the DSL modem beeing out of sync (saphairon AR160E1-B) but all they could do was ... nothing (" yes, i see there is a problem, we will try to fix it ... " never heard of him again ;) ).
    So my WRT45g (v.2) is still losing its con (either "SIGTERM" or "WAN dropped").
    :help:
     
  9. masterbeto

    masterbeto Network Guru Member

    same error

    May 1 19:54:55 turbonet1 user.alert kernel: Unable to handle kernel paging request at virtual address 000000e8, epc == 80097c28, ra == 80097c00
    May 1 19:54:55 turbonet1 user.warn kernel: Oops in fault.c::do_page_fault, line 192:
    May 1 19:54:55 turbonet1 user.warn kernel: $0 : 00000000 80174ba4 00000001 0000002b 80d1e890 00000000 00000000 00000008
    May 1 19:54:55 turbonet1 user.warn kernel: $8 : 0000002b ffffffa6 00000010 6c762b55 30303735 00000017 8075ff08 43373730
    May 1 19:54:55 turbonet1 user.warn kernel: $16: 801827e8 80c29960 80d1e7e0 00000000 8075fe98 7fff7c80 00000000 00000000
    May 1 19:54:55 turbonet1 user.warn kernel: $24: 00000010 2ab2bcf0 8075e000 8075fe58 00000000 80097c00
    May 1 19:54:55 turbonet1 user.warn kernel: Hi : 00000000
    May 1 19:54:55 turbonet1 user.warn kernel: Lo : 0000000c
    May 1 19:54:55 turbonet1 user.warn kernel: epc : 80097c28 Not tainted
    May 1 19:54:55 turbonet1 user.warn kernel: Status: 1000fc03
    May 1 19:54:55 turbonet1 user.warn kernel: Cause : 00000008
    May 1 19:54:55 turbonet1 user.warn kernel: Process pppoecd (pid: 181, stackpage=8075e000)
    May 1 19:54:55 turbonet1 user.warn kernel: Stack: 809df008 809df008 63880011 00000005 10020680 80b6ced8 0000001e
    May 1 19:54:55 turbonet1 user.warn kernel: 0000001a 7fff7e14 7fff7c80 800b0eb4 800b0e70 00000008 80049410 ffffffea
    May 1 19:54:55 turbonet1 user.warn kernel: 00000001 00000018 2c730000 9564b000 6c762b55 00316e61 00000000 00000000
    May 1 19:54:55 turbonet1 user.warn kernel: 00000000 00000000 80049590 80c16340 00000004 7fff7ca8 00000023 80049720
    May 1 19:54:55 turbonet1 user.warn kernel: 800497c4 8006c068 10000e80 8075fe60 00000014 8075ff00 00000001 00000000
    May 1 19:54:55 turbonet1 user.warn kernel: 00000000 ...
    May 1 19:54:55 turbonet1 user.warn kernel: Call Trace: [<800b0eb4>] [<800b0e70>] [<80049410>] [<80049590>] [<80049720>]
    May 1 19:54:55 turbonet1 user.warn kernel: [<800497c4>] [<8006c068>] [<800085a4>]
    May 1 19:54:55 turbonet1 user.warn kernel:
    May 1 19:54:55 turbonet1 user.warn kernel: Code: 00000000 8e450024 24020001 <c0a400e8> 00821823 e0a300e8 1060fffc 00821823 0000000f
     

Share This Page