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

bug: kernel timer added twice at c0019d40

Discussion in 'Sveasoft Firmware' started by pkitester, Sep 13, 2004.

  1. pkitester

    pkitester Network Guru Member

    I just loaded up the firmware onto a V1 unit, turned on syslog and telnet, then logged into the box and looked at /var/log/messages

    My log is just littered with:

    Jan 1 00:38:53 (none) user.warn klogd: bug: kernel timer added twice at c0019d40.

    Any ideas? Or just another bug to add to the list? Sure makes the syslog useless since it is just full of these messages and nothing else now...
     
  2. pkitester

    pkitester Network Guru Member

    more info

    I noticed on a reboot that it first starts like this:

    Jan 1 00:26:06 (none) user.warn klogd: ip_conntrack_pptp version 1.9 loaded
    Jan 1 00:26:06 (none) user.warn klogd: ip_nat_pptp version 1.5 loaded
    Jan 1 00:26:06 (none) user.warn klogd: at c0019d40.
    Jan 1 00:26:06 (none) user.warn klogd: bug: kernel timer added twice at c0019d4
    0.
    Jan 1 00:26:06 (none) user.warn klogd: bug: kernel timer added twice at c0019d4
    0.

    I tried removing the ip_nat_pptp stuff, by typing:
    rmmod ip_nat_pptp
    rmmod ip_nat_proto_gre

    But the messages aren't stopping. I assume those modules are only if you were to enable the pptp server on the firmware, right?

    Right now I am more worried this is going to crash the router by filling up all the free ram. What is the limit on the size of the messages file? Since these messages come out twice every 15 seconds, it is going to quickly fill all available ram if it isn't bounded.
     
  3. pkitester

    pkitester Network Guru Member

    i'm guessing it is a bug

    Well poking around I noticed that the AP WATCHDOG, which I don't even have enabled happened to have a 15 second interval.

    So I changed the timer to 86400 (one day in seconds), and sure enough it has shut the stupid thing up.

    I don't have this problem on the V2 unit I am testing.
     
  4. davparker

    davparker Guest

    kernel timer added twice

    I did not have AP WATCHDOG enabled either but was getting the kernel timer messages. I tried your suggestion of changing the timer to 86400 and the messages went away. Thanks,
     

Share This Page