From owner-freebsd-current@FreeBSD.ORG Sun Jul 14 10:34:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E2DF4730 for ; Sun, 14 Jul 2013 10:34:49 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by mx1.freebsd.org (Postfix) with ESMTP id BD287C71 for ; Sun, 14 Jul 2013 10:34:49 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id ro2so10392061pbb.41 for ; Sun, 14 Jul 2013 03:34:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=KW/rHodNdZwhnv5qp11dSspTJ3gr2bveRy3lpmeu1R4=; b=GsAmmACBBe9gHv6avikVUSqWKmq+5pRJ7L1r/0mLnoXvsmpUqzeJaSej+bMNaGQ25k EYe25RGN0tMeunxnDw+/mQ6Wnsn9QwP9ImSX/qnXYo+rM0W+n+B3gBFhIkQK/b2ijmQr HHe3PuR5n2Hrhy6+Ib/jID2cDnUS2W5kiKeEBKUZ+JeaeCmwejSFAyh8XC0LkYWQ1Kks NtP8SVeRu0p5juuQ+2gaCKOF3vsQlJiiETDXbBNReo6pkwXhukYudO7/1VgI9QzMZ+Wi T90FDGZrSCZzCLkTfKZSdl0kTawr0B/zVB++ufAiyDlj3pFf2skQOU9rMgr4PIAckGJe WJaQ== X-Received: by 10.68.96.229 with SMTP id dv5mr28740713pbb.89.1373798089582; Sun, 14 Jul 2013 03:34:49 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id br1sm54997234pbb.4.2013.07.14.03.34.46 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 14 Jul 2013 03:34:48 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Sun, 14 Jul 2013 19:34:44 +0900 From: Yonghyeon PYUN Date: Sun, 14 Jul 2013 19:34:44 +0900 To: Denis D Subject: Re: msk0 watchdog timeout and interrupt storm Message-ID: <20130714103444.GB1105@michelle.cdnetworks.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jul 2013 10:34:50 -0000 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.