From owner-freebsd-current Thu May 3 10:57:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 5589F37B43F for ; Thu, 3 May 2001 10:57:42 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id KAA25784 for ; Thu, 3 May 2001 10:57:41 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpdAAAozaGvY; Thu May 3 10:57:33 2001 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id LAA28955 for current@freebsd.org; Thu, 3 May 2001 11:02:10 -0700 (MST) From: Terry Lambert Message-Id: <200105031802.LAA28955@usr05.primenet.com> Subject: Re: panic in fxp driver To: current@freebsd.org Date: Thu, 3 May 2001 18:02:10 +0000 (GMT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ] I would be quite interested in knowing just how you manage ] to accomplish that, given that all the transmit control buffers ] are arranged in a circular linked list: ] ] fxp_init(void *xsc) ] { ] ... ] for (i = 0; i < FXP_NTXCB; i++) { ] ... ] txp[i].next = &txp[(i + 1) & FXP_TXCB_MASK]; ] } ] ] ] I would suggest actually examining the rest of the code to see ] how it works before making erroneous proclamations based on the ] myopic examination of a single statement. I would suggest a less than myopic examination of the subject line. In particular, I saw a repeatable panic under extremely heavy load. Please consider the case where there are two mbuf chains being transmitted, which look like this: A B header O O \ / \ / \ / data 1 O | data 2 O | data 3 O Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message