Results 1 to 5 of 5

Thread: -7c strange syslog entries

  1. #1

    -7c strange syslog entries

    Hi Oleg

    I have put the latest -7c version on a WL-HDD.

    I get a lot of theese entries in the syslog, and also see syslogd and klogd useing huge amounts of CPU :

    Jan 1 00:00:24 kernel: et1: et_reset
    Jan 1 00:00:24 kernel: et1: etc_reset
    Jan 1 00:00:24 kernel: et1: chipreset
    Jan 1 00:00:24 kernel: et1: chiptxreclaim
    Jan 1 00:00:24 kernel: et1: chiprxreclaim
    Jan 1 00:00:24 kernel: et1: etc_init
    Jan 1 00:00:24 kernel: et1: chipinit
    Jan 1 00:00:25 kernel: et1: et_start: len 54
    Jan 1 00:00:25 kernel: et1: et_sendnext
    Jan 1 00:00:25 kernel: et1: chiptx
    Jan 1 00:00:25 kernel: et1: et_isr: events 0x11
    Jan 1 00:00:25 kernel: et0: et_start: len 54
    Jan 1 00:00:25 kernel: et0: et_sendnext
    Jan 1 00:00:25 kernel: et0: chiptx

    I see it all over the syslog....also in between mount information and so on.
    macsat
    http://www.macsat.com - Tutorials and information on using ASUS WL-500G and family.

  2. #2
    Bump!

    Could it really be that no one else have seen the above log entries....anyone?

    Oleg?

    It really kills performance totally, since klogd and syslogd eats the CPU :-/
    macsat
    http://www.macsat.com - Tutorials and information on using ASUS WL-500G and family.

  3. #3
    Join Date
    Jun 2005
    Location
    Slovenia
    Posts
    736
    Never And I mean never. What bugs me is
    Code:
    sending pkt_too_big (len[1492] pmtu[1466]) to self
    sending pkt_too_big (len[1492] pmtu[1466]) to self
    sending pkt_too_big (len[1492] pmtu[1466]) to self
    sending pkt_too_big (len[1492] pmtu[1466]) to self

  4. #4
    Join Date
    Dec 2003
    Location
    Russian Federation
    Posts
    8,353
    Quote Originally Posted by macsat
    Hi Oleg

    I have put the latest -7c version on a WL-HDD.

    I get a lot of theese entries in the syslog, and also see syslogd and klogd useing huge amounts of CPU :

    Jan 1 00:00:24 kernel: et1: et_reset
    Jan 1 00:00:24 kernel: et1: etc_reset
    Jan 1 00:00:24 kernel: et1: chipreset
    Jan 1 00:00:24 kernel: et1: chiptxreclaim
    Jan 1 00:00:24 kernel: et1: chiprxreclaim
    Jan 1 00:00:24 kernel: et1: etc_init
    Jan 1 00:00:24 kernel: et1: chipinit
    Jan 1 00:00:25 kernel: et1: et_start: len 54
    Jan 1 00:00:25 kernel: et1: et_sendnext
    Jan 1 00:00:25 kernel: et1: chiptx
    Jan 1 00:00:25 kernel: et1: et_isr: events 0x11
    Jan 1 00:00:25 kernel: et0: et_start: len 54
    Jan 1 00:00:25 kernel: et0: et_sendnext
    Jan 1 00:00:25 kernel: et0: chiptx

    I see it all over the syslog....also in between mount information and so on.
    These messages are get activated with et msglevel. It's disabled by default.
    Perhaps something in your system is accessing et driver in the wrong way.

  5. #5
    How could I disable this?

    ...and what do you suspect can trigger it ?

    All that is running besides the standard firmware from you, is the TwonkyVision mediaserver....
    macsat
    http://www.macsat.com - Tutorials and information on using ASUS WL-500G and family.

Similar Threads

  1. strange traffic on br0
    By fero_hora in forum WL-500g Q&A
    Replies: 0
    Last Post: 25-03-2006, 13:27
  2. Replies: 6
    Last Post: 26-02-2006, 04:11
  3. WL500g Deluxe+HP5550 - strange behavior!
    By Snowii in forum WL-500g Q&A
    Replies: 0
    Last Post: 10-12-2005, 16:05
  4. enable syslog in AP mode
    By init_{} in forum WL-500g Q&A
    Replies: 1
    Last Post: 09-06-2004, 13:04

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •