From owner-freebsd-current Mon Apr 15 10:35:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from squall.waterspout.com (squall.waterspout.com [208.13.56.12]) by hub.freebsd.org (Postfix) with ESMTP id 0A72637B400; Mon, 15 Apr 2002 10:35:47 -0700 (PDT) Received: by squall.waterspout.com (Postfix, from userid 1050) id 7EE919B19; Mon, 15 Apr 2002 12:35:46 -0500 (EST) Date: Mon, 15 Apr 2002 12:35:46 -0500 From: Will Andrews To: Nick Hibma Cc: "current@FreeBSD.org" , joe@FreeBSD.org Subject: Re: plug aue ethernet goes to panic Message-ID: <20020415173546.GT71498@squall.waterspout.com> Mail-Followup-To: Nick Hibma , "current@FreeBSD.org" , joe@FreeBSD.org References: <20020413175429.GA65074@squall.waterspout.com> <20020415110325.J36693-100000@heather.van-laarhoven.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020415110325.J36693-100000@heather.van-laarhoven.org> User-Agent: Mutt/1.3.26i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Apr 15, 2002 at 11:11:36AM +0200, Nick Hibma wrote: > device_set_ivars is always called (in usbd_probe_and_attach) with as an > argument a stack variable. Also, the ivar is not stored or anything in > the if_aue.c driver. So this problem sounds like a problem in revisions > of various files. > > Please check that your kernel modules kernel are in sync. Do this by > rebuilding the kernel and the modules from scratch. > > Also, after you've installed your kernel check that all your kernel > files have been updated. Do you by any chance have a stale /modules or > /boot/modules directory lying around? You should have only kernel > modules in /boot/kernel*/ and NOT in /modules* or /boot/modules*. > > If the problem persists, please mail me the output of > > ident /sys/dev/usb/*.[ch] > find /modules /boot -type f -ls Nick, You really should talk to Joe Karthauser. He's already confirmed that it *is* an issue in the code (and not any kind of misconfiguration on my part). I've already spent enough time debugging the problem. I recently MFC'd the support for my device to -stable so I could use the machine on the network without it panicking on me. However, when Joe fixes the problem I will give it another shot [same machine has -CURRENT on another partition that I use for occasional hacking]. Thanks for the suggestions, though. Regards, -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message