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 :-/
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.
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.
Never And I mean never. What bugs me isCode: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
These messages are get activated with et msglevel. It's disabled by default.Originally Posted by macsat
Perhaps something in your system is accessing et driver in the wrong way.
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.