There are many ways to go about this
The most obvious way is to get rid of the cause. For example by
installing a small hub where the laptop can connect and thereby provide
a stable link to the bridge for that network segment regardless if the
laptop is connected or not.
Another way to get rid of this is to lessen the amount of kernel logging
in your syslog.conf. The first is logged at priority "info", the second
varies with the actual NIC driver ranging from "notice" to "error".
Problem is that by doing this you may loose other messages you consider
important.
A thrid way is to patch your kernel to not log these messages.
A fourth way is to use a "smart" syslog daemon that can act on message
content, not only on facility and priority, thus allowing you to filter
out the exact messages only.
Or fifth, accept that these get logged, and just ignore them while
reading your kernel logs ("grep -v" is your friend)
--
Henrik Nordstrom
MARA Systems AB
Sweden
Robert Siemer wrote:
> Hi everybody!
>
> My kernellogs are showing
>
> NETDEV WATCHDOG: eth1: transmit timed out
> eth1: Tx timed out, cable problem? TSR=0x0, ISR=0x0, t=33.
>
> when there is no link on eth1. The reason is clear, but how can I
> disable this warning?
>
> What common solution do you use to get rid of it?
>
> Regards,
> Robert
>
> _______________________________________________
> Bridge mailing list
> [EMAIL PROTECTED]
> http://www.math.leidenuniv.nl/mailman/listinfo/bridge
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge
