Date: Fri, 1 Nov 2013 14:05:06 +0900 From: Yonghyeon PYUN <pyunyh@gmail.com> To: Boris Samorodov <bsam@passap.ru> Cc: FreeBSD Stable Users <freebsd-stable@freebsd.org> Subject: Re: regression: msk0 watchdog timeout and interrupt storm Message-ID: <20131101050506.GA1413@michelle.cdnetworks.com> In-Reply-To: <5272AA01.40803@passap.ru> References: <526FBA53.9000208@passap.ru> <20131030021650.GA3106@michelle.cdnetworks.com> <52725C3D.2030602@passap.ru> <5272AA01.40803@passap.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 31, 2013 at 11:05:37PM +0400, Boris Samorodov wrote: > 31.10.2013 17:33, Boris Samorodov пишет: > > 30.10.2013 06:16, Yonghyeon PYUN пишет: > >> On Tue, Oct 29, 2013 at 05:38:27PM +0400, Boris Samorodov wrote: > > > >>> >From time to time I use a notebook and boot FreeBSD from USB > >>> stick. FreeBSD 9.2-i386 works OK. So I tried to use > >>> FreeBSD 10.0-i386 BETA2 and the network adapter works for > >>> some 10-15 seconds and then stops with diagnostic message > >>> "msk0:watchdog timeout". I've found similar case at > >>> freebsd-current@ with no workaround. Yes, there is an > >>> interrupt storm as well. > >> > >> There had been no functional changes for very long time so I'm not > >> sure what's going on here. I've attached local change I have at > >> this moment but I'm afraid it wouldn't address the issue above. > >> > >> I recall jhb also reported interrupt storm in the past but the root > >> cause was not identified yet. Could you change msk_intr() and let > >> me know which interrupt is firing? > > > > I've yet to organize a build. > > Success! The system is up, fetching and uploading for an hour now. > No more watchdog timeouts, storms and freeses (stable/10, i386, > r257422M, modified by your patch). > Committed in r257490. Thanks a lot for reporting and testing!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131101050506.GA1413>