From owner-freebsd-mobile@FreeBSD.ORG Sat May 27 19:06:42 2006 Return-Path: X-Original-To: mobile@freebsd.org Delivered-To: freebsd-mobile@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9E1016A775 for ; Sat, 27 May 2006 19:06:42 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 31C3343D48 for ; Sat, 27 May 2006 19:06:41 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 88294 invoked from network); 27 May 2006 19:06:41 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 27 May 2006 19:06:41 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sat, 27 May 2006 14:06:39 -0500 (CDT) From: Mike Silbersack To: Makoto Matsushita , Ben Kaduk , "[ISO-8859-1] Mikko Tyljrvi" Message-ID: <20060527135922.C7405@odysseus.silby.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-614941107-1148756799=:7405" Cc: mobile@freebsd.org Subject: Making progress on if_bfe X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 May 2006 19:06:52 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-614941107-1148756799=:7405 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed I started working on if_bfe again, and I am able to reproduce the problems that people with 512MB of ram started to report after I fixed the driver for people with > 1G of ram. I have some ideas on what is going on, but no fix yet. For anyone who has time (no matter what size ram you have), I'd like you to try the attached patch. The patch is very simple - instead of interrupt storming, it tells you why the bfe card is unhappy, and downs the interface instead of continually attempting to restart it. The interrupt storm was a side-effect of the card complaining, and the driver continually trying to restart the card. So, apply the patch, then try with 128 as the values for BFE_TX_LIST_CNT and BFE_RX_LIST_CNT, see what happens, then try with 511 and see what happens. Then e-mail me the results. This will confirm that you are seeing the same errors from the card that I am. Oh, and once you're done with that, go back to using the values for BFE_TX_LIST_CNT and BFE_RX_LIST_CNT that work for you. :) Thanks, Mike "Silby" Silbersack --0-614941107-1148756799=:7405 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=if_bfe.c.errordetect.patch Content-Transfer-Encoding: BASE64 Content-ID: <20060527140639.B7405@odysseus.silby.com> Content-Description: Content-Disposition: attachment; filename=if_bfe.c.errordetect.patch LS0tIGlmX2JmZS5jLmdvb2Rlbm91Z2gJU2F0IE1heSAyNyAwMDoyNToyNCAy MDA2DQorKysgaWZfYmZlLmMuaGFzYWxsZXJyb3JzZGV0ZWN0ZWQJU2F0IE1h eSAyNyAwMToxODozOSAyMDA2DQpAQCAtMTIxNSw2ICsxMjE1LDI4IEBADQog CX0NCiANCiAJaWYoaXN0YXQgJiBCRkVfSVNUQVRfRVJST1JTKSB7DQorDQor CQlpZiAoaXN0YXQgJiBCRkVfSVNUQVRfRFNDRSkgew0KKwkJCXByaW50Zigi aWZfYmZlIERlc2NyaXB0b3IgRXJyb3JcbiIpOw0KKwkJCWJmZV9zdG9wKHNj KTsNCisJCQlCRkVfVU5MT0NLKHNjKTsNCisJCQlyZXR1cm47DQorCQl9DQor DQorCQlpZiAoaXN0YXQgJiBCRkVfSVNUQVRfREFUQUUpIHsNCisJCQlwcmlu dGYoImlmX2JmZSBEYXRhIEVycm9yXG4iKTsNCisJCQliZmVfc3RvcChzYyk7 DQorCQkJQkZFX1VOTE9DSyhzYyk7DQorCQkJcmV0dXJuOw0KKwkJfQ0KKw0K KwkJaWYgKGlzdGF0ICYgQkZFX0lTVEFUX0RQRSkgew0KKwkJCXByaW50Zigi aWZfYmZlIERlc2NyaXB0b3IgUHJvdG9jb2wgRXJyb3JcbiIpOw0KKwkJCWJm ZV9zdG9wKHNjKTsNCisJCQlCRkVfVU5MT0NLKHNjKTsNCisJCQlyZXR1cm47 DQorCQl9DQorCQkNCiAJCWZsYWcgPSBDU1JfUkVBRF80KHNjLCBCRkVfRE1B VFhfU1RBVCk7DQogCQlpZihmbGFnICYgQkZFX1NUQVRfRU1BU0spDQogCQkJ aWZwLT5pZl9vZXJyb3JzKys7DQo= --0-614941107-1148756799=:7405--