https://bugzilla.novell.com/show_bug.cgi?id=637183 https://bugzilla.novell.com/show_bug.cgi?id=637183#c7 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@novell.com --- Comment #7 from Marius Tomaschewski <mt@novell.com> 2010-10-08 08:40:16 UTC --- No, as explained by Hong Dan in comment 5, it is normal that the carrier is not readable in several cases, basically when the hw is not (yet) ready to report it. It is even worser, sometime the drivers reports (reported) there is carrier, but drop anything for a "long time": when I remember correctly, bnx2 driver reports/reported carrier, but the hardware still dropped for _30_ secs... No idea if and where this is fixed in the kernel driver in the meantime or not yet. ifplugd-selectif waits 10 secs (40 * 0.25 sec) to get it and gives up, what is IMO fine here. The problem here is the error reporting only -- we may not throw away the read error correctly and should not speak about "cable" in wlan case... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.