From owner-freebsd-bugs@FreeBSD.ORG Wed Sep 17 07:30:07 2008 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 007BC106567B for ; Wed, 17 Sep 2008 07:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E4A148FC14 for ; Wed, 17 Sep 2008 07:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8H7U53c045474 for ; Wed, 17 Sep 2008 07:30:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8H7U5il045470; Wed, 17 Sep 2008 07:30:05 GMT (envelope-from gnats) Date: Wed, 17 Sep 2008 07:30:05 GMT Message-Id: <200809170730.m8H7U5il045470@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Matthias Apitz Cc: Subject: Re: kern/122331: panic's on KDE-launches (but only in WPA Wifi area) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2008 07:30:07 -0000 The following reply was made to PR kern/122331; it has been noted by GNATS. From: Matthias Apitz To: John Baldwin Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org, bug-followup@freebsd.org Subject: Re: kern/122331: panic's on KDE-launches (but only in WPA Wifi area) Date: Wed, 17 Sep 2008 09:27:47 +0200 El día Tuesday, September 16, 2008 a las 11:25:44AM -0400, John Baldwin escribió: > Well, fd_ofiles being NULL here is really odd. It's also odd that you have no > current directory. Because fd_nfiles is 20, fd_ofiles should be pointing to > the static file descriptor array. Off the top of my head I don't see how > this is happening. It might help if you can narrow down exactly what WPA > operation you are doing that causes the panic. I'm doing nothing by my own with WPA; the wpa_supplicant is launched at boot time via /etc/rc.conf entry as: ifconfig_iwi0="WPA" i.e. in the moment when I launch the X11+KDE with 'startx' is already running, iwi0 is associated with the AP and IP/routing is up in the interface (I've checked this always with 'ifconfig iwi0'); the difference between my home and the office is WEP (at home where I don't face that problem) and WPA in the office; yesterday and today morning KDE booted fine without causing this panic; could the reason be some inconsistency in the file system? but in this case as well I don't know where this could come from; I have always clean shutdowns before moving from my home to the office: matthias -- Matthias Apitz A computer is like an air conditioner, it stops working when you open Windows Una computadora es como aire acondicionado, deja de funcionar si abres Windows