On Sat, Jul 13, 2013 at 01:39:06PM +0200, Denis D wrote: > > If you use dual-boot, please try "cold-boot" it. Other OS may have > > > > put the PHY into weird state. Cold-boot shall make firmware restore > > > > its PHY configuration. > > > > > > > > > > Hello pyunyh, > > > > > when i really understand the word coldbootkorrekt,it means, that i have to shutdown my pc. > And start it (during he was off) and boot into FreeBSD. > > > > > My PC was off for 9 hours because of work, but still the same "watchdog timeout" error. Did you completely remove power-cord and wait 1 ~ 2 min. before boot? There are many Yukon II variants and each controller seems to require special handling to work-around silicon bugs. And your controller has a Audio Video Bridging (AVB) feature which may or may not need a special handling in TX/RX path. At least it may need to initialize or disable QoS specific feature of controller, I guess. Unfortunately errata or detailed programming information is not available to open source developers. Interrupt storm seems to indicate one of important event was not properly handled in driver. Not sure what it is. > > > > > Maybe some other solutions? Sorry, have no further idea at this moment. I hoped cold-boot shall put controller into compatible mode but it seems it does not. I'll let you know if I happen to find a clue.Received on Sun Jul 14 2013 - 08:34:49 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:39 UTC