Date: Sat, 13 Jul 2013 13:39:06 +0200 From: Denis D <demonking@hotmail.de> To: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: msk0 watchdog timeout and interrupt storm Message-ID: <DUB121-W3968F2DEA969925529A7B0C9650@phx.gbl> In-Reply-To: <DUB121-W2317468FCB9BDDE7000039C9650@phx.gbl> References: <DUB121-W14E3C010F73C3E77AF11A4C97F0@phx.gbl>, <20130710065701.GD2753@michelle.cdnetworks.com>, <DUB121-W2317468FCB9BDDE7000039C9650@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
> If you use dual-boot=2C please try "cold-boot" it. Other OS may have =0A= =0A= > put the PHY into weird state. Cold-boot shall make firmware restore =0A= =0A= > its PHY configuration. =0A= =0A= >=20 =0A= =0A= =0A= =0A= Hello pyunyh=2C=0A= =0A= =0A= =0A= when i really understand the word coldbootkorrekt=2Cit means=2C that i have= to shutdown my pc. And start it (during he was off) and boot into FreeBSD.=0A= =0A= =0A= =0A= My PC was off for 9 hours because of work=2C but still the same "watchdog t= imeout" error.=0A= =0A= =0A= =0A= Maybe some other solutions? =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DUB121-W3968F2DEA969925529A7B0C9650>