From owner-freebsd-current@FreeBSD.ORG Sun Sep 4 17:56:29 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85A1A106566C for ; Sun, 4 Sep 2011 17:56:29 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 444258FC17 for ; Sun, 4 Sep 2011 17:56:28 +0000 (UTC) Received: by qyk9 with SMTP id 9so2826075qyk.13 for ; Sun, 04 Sep 2011 10:56:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=O/TQoBcdAQeJIFgZRb+oSFZVrFgtFZBlGvmwOJnShF0=; b=r+hUrhI0YqCnrKUY8wK5xtd2wYroLcQL8/jCTCos39JZ6Xkg7QTP+rgchXIIf3NblG 6HdnisGwphL0nc2PDpb9isKBfyXh+NB/b5idTuqQm55QF7tFNFqtDBaYgBCH5jm84V7V NqQRtBJJCPPdrnyADUGU0IbheeUFrccXOUNl0= MIME-Version: 1.0 Received: by 10.224.216.199 with SMTP id hj7mr2304815qab.292.1315158987836; Sun, 04 Sep 2011 10:56:27 -0700 (PDT) Received: by 10.224.37.83 with HTTP; Sun, 4 Sep 2011 10:56:27 -0700 (PDT) In-Reply-To: <09C13664-4FC0-41F3-8849-CE875B3A6CC0@vnode.se> References: <09C13664-4FC0-41F3-8849-CE875B3A6CC0@vnode.se> Date: Sun, 4 Sep 2011 10:56:27 -0700 Message-ID: From: Garrett Cooper To: Joel Dahl Content-Type: text/plain; charset=ISO-8859-1 Cc: Weongyo Jeong , current@freebsd.org Subject: Re: BETA2 panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Sep 2011 17:56:29 -0000 On Sun, Sep 4, 2011 at 10:04 AM, Joel Dahl wrote: > Hi, > > I upgraded my laptop from BETA1 to rev. 225367 today, and now my laptop panics just a few minutes after booting. This is 100% reproducible, it panics every time. > > I've got a pic with the backtrace here: http://www.vnode.se/sc/panic_20110904.jpg Is your wireless turned off? If so, it looks like the state transition code isn't being handled properly between bwn(4) and net80211(4), in particular because your wireless card was still in 'scan' mode. Thanks, -Garrett