From owner-freebsd-bugs@FreeBSD.ORG Mon Mar 31 13:10:05 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 349D3106566C for ; Mon, 31 Mar 2008 13:10: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 283B08FC1E for ; Mon, 31 Mar 2008 13:10: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 m2VDA4CO058056 for ; Mon, 31 Mar 2008 13:10:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2VDA4ce058055; Mon, 31 Mar 2008 13:10:04 GMT (envelope-from gnats) Date: Mon, 31 Mar 2008 13:10:04 GMT Message-Id: <200803311310.m2VDA4ce058055@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Matthias Apitz Cc: Subject: Re: kern/122286: 7.0-RELEASE & & panic's when wpa_supplicant with WPA is used 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: Mon, 31 Mar 2008 13:10:05 -0000 The following reply was made to PR kern/122286; it has been noted by GNATS. From: Matthias Apitz To: bug-followup@FreeBSD.org, guru@sisis.de Cc: Subject: Re: kern/122286: 7.0-RELEASE && panic's when wpa_supplicant with WPA is used Date: Mon, 31 Mar 2008 15:08:25 +0200 Date: Mon, 31 Mar 2008 15:04:04 +0200 To: Kris Kennaway Cc: Sam Leffler , freebsd-mobile@freebsd.org Subject: Re: 7.0-RELEASE && panic after ~4 hours El día Monday, March 31, 2008 a las 12:39:14PM +0200, Kris Kennaway escribió: > This information is confusing. You might be having wifi problems, > but > the panic is in the soft updates code and has no obvious relation to > wifi. > > It is possible you had an initial panic (maybe in wifi) that caused > filesystem corruption that was not repaired by background fsck. > > You should unmount (or boot to single-user mode) and run a full fsck > (fsck -fy). Thanks for your hint and I've done what you have advised and I'm connected through Wifi again now (until next panic :-)) The fsck has indeed correct something where the block count should have been zero but was some decimal number of 20 digits, I think (don't remember that large number); -- Matthias Apitz