From owner-freebsd-current@FreeBSD.ORG Wed Dec 24 10:45:06 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 5007C1065673 for ; Wed, 24 Dec 2008 10:45:06 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net [41.161.16.135]) by mx1.freebsd.org (Postfix) with ESMTP id 8EB868FC14 for ; Wed, 24 Dec 2008 10:45:05 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from [41.241.124.20] (helo=clue.co.za) by inbound01.jnb1.gp-online.net with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1LFREc-0005b5-LQ; Wed, 24 Dec 2008 12:45:02 +0200 Received: from [127.0.0.1] (helo=clue.co.za) by clue.co.za with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LFRDn-0000Oi-SK; Wed, 24 Dec 2008 12:44:11 +0200 To: pyunyh@gmail.com From: Ian FREISLICH In-reply-to: <20081224085143.GH95088@cdnetworks.co.kr> References: <20081224085143.GH95088@cdnetworks.co.kr> <11167f520812232229g5ee1d475kdd92fd6511c50c29@mail.gmail.com> <20081224021016.GF95088@cdnetworks.co.kr> X-Attribution: BOFH Date: Wed, 24 Dec 2008 12:43:56 +0200 Message-Id: Cc: current@freebsd.org Subject: Re: msk(4) stops working. 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, 24 Dec 2008 10:45:06 -0000 Pyun YongHyeon wrote: > > On Wed, Dec 24, 2008 at 08:54:26AM +0200, Ian FREISLICH wrote: > > "Sam Fourman Jr." wrote: > > > >> About 2-3 months ago I committed workaround for Yukon silicon bug. > > > >> Do you use latest CURRENT? > > > > > > > > Yes, this is on yesterday's sources. It was better for a month or > > > > so, but over the last month it's been really bad. Now I can provoke > > > > this condition in under 1 minute of uptime. > > > > > > > I have a few msk cards, and I could stand to install -CURRENT on a syste m > > > how do I reproduce your problem? > > > > I induce it by scp-ing a large (several GB) file from one host to > > another. I only have one interface msk interface in my laptop, but > > it's an SMP system. Maybe that has something to do with it. > > > > Would you show me the output of "sysctl dev.msk.0.stats" before and > after the watchdog timeouts after appling attached patch? Before: dev.msk.0.stats.rx.ucast_frames: 0 dev.msk.0.stats.rx.bcast_frames: 4 dev.msk.0.stats.rx.pause_frames: 0 dev.msk.0.stats.rx.mcast_frames: 0 dev.msk.0.stats.rx.crc_errs: 0 dev.msk.0.stats.rx.good_octets: 538 dev.msk.0.stats.rx.bad_octets: 0 dev.msk.0.stats.rx.frames_64: 3 dev.msk.0.stats.rx.frames_65_127: 0 dev.msk.0.stats.rx.frames_128_255: 0 dev.msk.0.stats.rx.frames_256_511: 1 dev.msk.0.stats.rx.frames_512_1023: 0 dev.msk.0.stats.rx.frames_1024_1518: 0 dev.msk.0.stats.rx.frames_1519_max: 0 dev.msk.0.stats.rx.frames_too_long: 0 dev.msk.0.stats.rx.jabbers: 0 dev.msk.0.stats.tx.ucast_frames: 0 dev.msk.0.stats.tx.bcast_frames: 0 dev.msk.0.stats.tx.pause_frames: 0 dev.msk.0.stats.tx.mcast_frames: 0 dev.msk.0.stats.tx.octets: 0 dev.msk.0.stats.tx.frames_64: 0 dev.msk.0.stats.tx.frames_65_127: 0 dev.msk.0.stats.tx.frames_128_255: 0 dev.msk.0.stats.tx.frames_256_511: 0 dev.msk.0.stats.tx.frames_512_1023: 0 dev.msk.0.stats.tx.frames_1024_1518: 0 dev.msk.0.stats.tx.frames_1519_max: 0 dev.msk.0.stats.tx.colls: 0 dev.msk.0.stats.tx.late_colls: 0 dev.msk.0.stats.tx.excess_colls: 0 dev.msk.0.stats.tx.multi_colls: 0 dev.msk.0.stats.tx.single_colls: 0 dev.msk.0.stats.tx.underflows: 0 After: [apple] /usr/home/ianf # sysctl dev.msk.0.stats dev.msk.0.stats.rx.ucast_frames: 8561 dev.msk.0.stats.rx.bcast_frames: 5 dev.msk.0.stats.rx.pause_frames: 0 dev.msk.0.stats.rx.mcast_frames: 0 dev.msk.0.stats.rx.crc_errs: 0 dev.msk.0.stats.rx.good_octets: 12964072 dev.msk.0.stats.rx.bad_octets: 0 dev.msk.0.stats.rx.frames_64: 5 dev.msk.0.stats.rx.frames_65_127: 10 dev.msk.0.stats.rx.frames_128_255: 6 dev.msk.0.stats.rx.frames_256_511: 4 dev.msk.0.stats.rx.frames_512_1023: 6 dev.msk.0.stats.rx.frames_1024_1518: 8535 dev.msk.0.stats.rx.frames_1519_max: 0 dev.msk.0.stats.rx.frames_too_long: 0 dev.msk.0.stats.rx.jabbers: 0 dev.msk.0.stats.tx.ucast_frames: 10050 dev.msk.0.stats.tx.bcast_frames: 5 dev.msk.0.stats.tx.pause_frames: 0 dev.msk.0.stats.tx.mcast_frames: 0 dev.msk.0.stats.tx.octets: 712314 dev.msk.0.stats.tx.frames_64: 2 dev.msk.0.stats.tx.frames_65_127: 10038 dev.msk.0.stats.tx.frames_128_255: 9 dev.msk.0.stats.tx.frames_256_511: 3 dev.msk.0.stats.tx.frames_512_1023: 3 dev.msk.0.stats.tx.frames_1024_1518: 0 dev.msk.0.stats.tx.frames_1519_max: 0 dev.msk.0.stats.tx.colls: 0 dev.msk.0.stats.tx.late_colls: 0 dev.msk.0.stats.tx.excess_colls: 0 dev.msk.0.stats.tx.multi_colls: 0 dev.msk.0.stats.tx.single_colls: 0 dev.msk.0.stats.tx.underflows: 0 > BTW, did you intentionally disable MSI? No, MSI is enabled. Ian -- Ian Freislich