From owner-freebsd-current Sat Apr 13 14:55:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id 9B71137B400 for ; Sat, 13 Apr 2002 14:55:16 -0700 (PDT) Received: (qmail 8902 invoked from network); 13 Apr 2002 21:55:15 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 13 Apr 2002 21:55:15 -0000 Received: from laptop.baldwin.cx (john@laptop.baldwin.cx [192.168.0.4]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g3DLuCv67626; Sat, 13 Apr 2002 17:56:12 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020413175429.GA65074@squall.waterspout.com> Date: Sat, 13 Apr 2002 17:54:33 -0400 (EDT) From: John Baldwin To: Will Andrews Subject: Re: plug aue ethernet goes to panic Cc: current@FreeBSD.org, Makoto Matsushita 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 13-Apr-2002 Will Andrews wrote: > On Sat, Apr 13, 2002 at 12:44:36PM -0400, John Baldwin wrote: >> Can you get a backtrace in ddb? It looks like a null pointer dereference, >> and >> knowing where it happened would help. Finding the file and line of the >> instruction pointer using addr2line on kernel.debug would be helpful as >> well. > > It *is* a null pointer deref. Joe and I looked at this problem, > and it seems a function called device_get_ivars() isn't doing > its job in sys/dev/usb/usb_port.h. So the variable is getting > filled with a NULL pointer for the iface element and is later > deref'd. That's the limit of my debugging, and Joe is looking > into the problem actively. Well, if device_get_ivars() is returning a NULL pointer, then it probably means its parent bus device isn't setting up the ivars for the child device properly. As far as I understand, you can think of ivars as being per-device variables or state often used by a parent bus to set bus-specific information for a child device. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message