From owner-freebsd-current@FreeBSD.ORG Wed Sep 17 19:00:34 2008 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 113B01065682 for ; Wed, 17 Sep 2008 19:00:34 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (ZIM.MIT.EDU [18.95.3.101]) by mx1.freebsd.org (Postfix) with ESMTP id C84CF8FC0C for ; Wed, 17 Sep 2008 19:00:33 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (localhost [127.0.0.1]) by zim.MIT.EDU (8.14.3/8.14.2) with ESMTP id m8HJ3b4M066454; Wed, 17 Sep 2008 15:03:37 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by zim.MIT.EDU (8.14.3/8.14.2/Submit) id m8HJ3aDq066453; Wed, 17 Sep 2008 15:03:36 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Date: Wed, 17 Sep 2008 15:03:36 -0400 From: David Schultz To: Ian Freislich Message-ID: <20080917190336.GA66407@zim.MIT.EDU> Mail-Followup-To: Ian Freislich , current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: current@FreeBSD.ORG Subject: Re: msk(4) issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2008 19:00:34 -0000 On Wed, Sep 17, 2008, Ian Freislich wrote: > Hi > > I'm having an issue with the msk hardware in my laptop. It stops > transmitting or recieving sometimes, always triggered by periods > of intense network load. > > Sep 16 18:39:31 apple kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering > Sep 16 18:40:35 apple kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering > Sep 16 18:41:41 apple kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering > > But it never recovers. I have the same problem. Disabling MSI reduces the frequency with which it occurs from once a day to once a month or so. You can recover the card without rebooting by loading the msk driver as a kld, then unloading and reloading it to reset the card. Of course this is a hack, but I haven't bothered to look into anything better yet.