Hmm, I do not know what this hardware looks like, but its a wired interface, not wireless, so if it has link (and I'm guessing it does) it will have informed the stack its running, and thus will get traffic. Sounds like this is something the Wimax box should handle, at least that's my first take on the matter. This is the first I've encountered a setup like this however. Jack On Tue, Aug 25, 2009 at 2:12 PM, Scott Ullrich <sullrich_at_gmail.com> wrote: > On Tue, Aug 25, 2009 at 5:08 PM, Jack Vogel<jfvogel_at_gmail.com> wrote: > > Well, there's no magic switch, you could change the driver code to remove > > it, > > however its really indicative of some kind of problem, it shouldn't > happen, > > so > > perhaps you want to pursue that. Does it only happen on em2, what is > special > > about that path, etc etc.. > > > > You can look at the debug/stats data of the interface for clues, maybe > its a > > mbuf exhaustion, perhaps descriptor. > > After looking at the interface closer it appears the device it is > plugged into does not have power. In this case it is a Wimax wireless > radio. > > Should a device with NOCARRIER cause this error non-stop in the logs? > Can I get you more information that might help understand why the > watchdog is being tripped? > > Thanks for your help! > > Scott >Received on Tue Aug 25 2009 - 19:17:20 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:54 UTC