From owner-freebsd-current@FreeBSD.ORG  Mon Feb 11 11:24:26 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 972E7352;
 Mon, 11 Feb 2013 11:24:26 +0000 (UTC)
 (envelope-from tomek.cedro@gmail.com)
Received: from mail-qa0-f41.google.com (mail-qa0-f41.google.com
 [209.85.216.41])
 by mx1.freebsd.org (Postfix) with ESMTP id 3A8411E84;
 Mon, 11 Feb 2013 11:24:25 +0000 (UTC)
Received: by mail-qa0-f41.google.com with SMTP id hy16so1118048qab.14
 for <multiple recipients>; Mon, 11 Feb 2013 03:24:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
 bh=2SToFvOzxjzrmOACcl8bme32Q8+tbBMEKbARfCw41II=;
 b=Br2agyA42Pz8OV60ouSXrZuAYsLVaf1CajxYhT7ZdsIVcVMH+v1aq7TOrtG17SKM+8
 4wyDEQsRNuWVitqI3ErhzwJC48SEFf4TrPuIwTu31uEcIgVLTzzsncwDwot/QL71PN0u
 kD99JV+8bnYtCNP0mCf9AoqUZLJ08CftC5rWPNQwyBgTZ//dpU6m+sqmhlxeqsxGQh09
 9n9Nt8o4zDenJcMD5d3rXMSuW49DbatF00Rsb3FmJC0MX2smLsRcJNy1WAQ5Nhaa+sQh
 5z/O7RFk7YmNbnF3vbCVT8IjkXHCJdcd0fLdeKGPs6PwIegmfP8lso4xY6U90LP4vvjY
 mghQ==
MIME-Version: 1.0
X-Received: by 10.49.14.202 with SMTP id r10mr6133904qec.10.1360581865366;
 Mon, 11 Feb 2013 03:24:25 -0800 (PST)
Sender: tomek.cedro@gmail.com
Received: by 10.49.71.204 with HTTP; Mon, 11 Feb 2013 03:24:25 -0800 (PST)
In-Reply-To: <201302111118.r1BBIsFH064359@mech-cluster241.men.bris.ac.uk>
References: <CAFYkXjmkcHo7h=a8nKWv3Wx3M3r8PMGoLeGiK6kJ90c9XAACbQ@mail.gmail.com>
 <201302111118.r1BBIsFH064359@mech-cluster241.men.bris.ac.uk>
Date: Mon, 11 Feb 2013 12:24:25 +0100
X-Google-Sender-Auth: P8asst1MdMAs7ch0STvZ2OanLO0
Message-ID: <CAFYkXjkGbs_G2E0j_GB4yJVHUjunPFXM8JJV83XKnWaYESRi+Q@mail.gmail.com>
Subject: Re: on amd64 r246552: iwn0: <Intel Wireless WiFi Link 4965>: fatal
 firmware error
From: CeDeROM <cederom@tlen.pl>
To: mexas@bristol.ac.uk
Content-Type: text/plain; charset=UTF-8
Cc: freebsd-current@freebsd.org, freebsd-mobile@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 11:24:26 -0000

On Mon, Feb 11, 2013 at 12:18 PM, Anton Shterenlikht
<mexas@bristol.ac.uk> wrote:
> Yes, I can reproduce this on amd64 -current.
> I had to flip the switch twice to cause this:
> (..)
> However, in my earlier report I got to this
> error with no flipping the switch at all.

Uhm, on some networks I also very often get information in the dmesg
that "wlan0: link state changed to DOWN" and then  "wlan0: link state
changed to DOWN", maybe this produce issues similar to radio flip
switch..?

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info