In updating one of my click packages to run under Click 1.6.0 (git
pulled this morning), and after swimming through the Changelogs for the last
year, I got things up and running. However I noticed that the Nic driver, if
the link drops, will not recover unless the click module is removed. My unit
will be handling traffic, but when I pull a network cable, I'll see the
watchdog message for the link going down, but it will not come back up until I
remove the click kernel module.
My production units are running under a ~12/2006 CVS release of 1.5.0
on a 2.6.16.13 kernel, and I *think a 6.x version of the e1000 driver, but they
do not have the problem I described. So, I'm not sure what changes prompted
the problem I'm seeing.
< disconnect network cable cable >
e1000: eth1: e1000_watchdog_1: NIC Link is Down
< restore cable connection, but no further dmesg occurs >
< run click-uninstall >
e1000_poll_off
e1000: eth1: e1000_watchdog_1: NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: None
e1000_poll_off
e1000_poll_off
click: stopping router thread pid 1307
poll e0f7b360: 3684/920934 freed, 1437/460660 allocated
poll e0f7b580: 8779/5325393 freed, 8329/2658970 allocated
click module exiting
click error: 683 outstanding news
Just thought I would post this in case there are some open issues that
I'm not aware of and to get a thread started. I'll be doing some more digging
as well.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thomas Paine [EMAIL PROTECTED])}
University of Wisconsin - Eau Claire
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
click mailing list
[email protected]
https://amsterdam.lcs.mit.edu/mailman/listinfo/click
