Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Mar 2012 17:27:19 -0800
From:      YongHyeon PYUN <pyunyh@gmail.com>
To:        Kim Culhan <w8hdkim@gmail.com>
Cc:        freebsd-net@freebsd.org
Subject:   Re: msk0: watchdog timeout interface hang
Message-ID:  <20120302012719.GB1685@michelle.cdnetworks.com>
In-Reply-To: <CAKZxVQWxPbbEF2RAL_4zyrh%2B39RqPD1T_FZAQQbGL8NpLVFCxw@mail.gmail.com>
References:  <CAKZxVQVuwyJCVFqfyOjYw=o2zG-%2BZbj1HLUtLZxpB2mcGLdoXw@mail.gmail.com> <CAKZxVQWNQ=YQ2tQ-D2EewCrGYifuzbO6k60o2QNgD-RU6JqcCQ@mail.gmail.com> <20120220235648.GA3537@michelle.cdnetworks.com> <CAKZxVQWNO5XKqF%2B_R7C=HHDVFpKHfNn=Fi4X0vXnxNQmRUEOhQ@mail.gmail.com> <CAKZxVQWxPbbEF2RAL_4zyrh%2B39RqPD1T_FZAQQbGL8NpLVFCxw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 28, 2012 at 06:08:24PM -0500, Kim Culhan wrote:
> On Mon, Feb 20, 2012 at 6:56 PM, YongHyeon PYUN <pyunyh@gmail.com> wrote:
> > On Thu, Jan 26, 2012 at 05:46:23AM -0500, Kim Culhan wrote:
> >> On Wed, Jan 25, 2012 at 3:26 PM, Kim Culhan <w8hdkim@gmail.com> wrote:
> >> > Running 10-curent from 01-20-12
> >> > the msk0 interface hung, on the console:
> >> >
> >> > msk0: watchdog timeout
> >> > msk0: prefetch unit stuck?
> >> > msk0: initialization failed: no memory for Rx buffers
> >> >
> >> > Verbose boot dmesg output attached.
> >>
> >> This additional datapoint found, at boot after the last line in the
> >> verbose dmesg
> >> this line was logged to messages:
> >>
> >> Jan 25 15:21:19 foo kernel: interrupt storm detected on "irq257:";
> >> throttling interrupt source
> >
> > How about disabling MSI?(hw.msk.msi_disable loader tunable)
> 
> Running HEAD from 2-27-12, tested with MSI disabled and
> did not see any problems, this with a network traffic volume comparible to
> that when I had the original problem, which was running -current
> from 01-20-12.
> 
> Then re-enabled MSI and using svn, loaded /usr/src for HEAD
> and did not see any problems there either.
> 
> This traffic volume was also comparible to the earlier time when
> the problem occurred, ?running -current from 1-20-12.
> 
> It appears the problem may have been solved.
> 

Hmm, there was no msk(4) code change during the time window.
Probably the issue came from somewhere else.

> thanks
> -kim



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120302012719.GB1685>