From owner-freebsd-bugs Mon Jun 12 12: 4: 2 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 5521437B529; Mon, 12 Jun 2000 12:03:58 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id NAA02428; Mon, 12 Jun 2000 13:03:55 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200006121903.NAA02428@pluto.plutotech.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: wpaul@FreeBSD.ORG (Bill Paul) Cc: asmodai@FreeBSD.ORG, gibbs@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: kern/19106: Corruption of xl driver's TX chain during startup In-Reply-To: Your message of "Mon, 12 Jun 2000 11:16:18 PDT." <20000612181618.87A1037B9F8@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Jun 2000 13:04:19 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Hm. In most drivers, I bzero() the softc struct at the start of foo_attach() >just to make sure there isn't any garbage lying around. For some reason, >I'm not doing this in if_xl. It could be a coincidence that this has >never bitten anyone before. The NewBus code bzero's the softc on your behalf. From looking at this with the kernel debugger, it appears that the corruption does not occur until after the return of the attach routine. I'm still trying to narrow down this problem, but my hunch is that it is some other driver that is stomping on th xl card's softc. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message