From owner-freebsd-current@freebsd.org Sun Nov 22 22:38:27 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85B9CA34F90 for ; Sun, 22 Nov 2015 22:38:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 50B1A1542 for ; Sun, 22 Nov 2015 22:38:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igvg19 with SMTP id g19so63366998igv.1 for ; Sun, 22 Nov 2015 14:38:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Bh79r86Zj+t7/EnizfGs/l65dcq548rLDpNtFW1sMcc=; b=oa6kGlEYJmUu5cei4ZKJiXaiLvjEGjVJ7AJ29qHONh4/YkON0n4EgQDSH6eOTvZO7y 5NVWPgp6vSQZb/oLwcI8uUFhF0HnZJRb9lFV87yDqxwHHn5dtrQJdIFTUcxLbPKp5OAh NzueP5Inmm8//E/nCWK2RJJx4Bipk96NvPfLPRX1rlT1CJQHYImBEyn1z38cFzJ1F/p2 j7VklVC7k3tZsmdsMYDjMVIsHhKpL3J8rSkzVFcG576pvSa8eiLawoG4dwBfTK4s9DnB mVjQKF4JChiV8gklvT1Ol2JmgEyVDeHgyCitq+agxJ1q7KsJgyYiV6ew/88u54N7RG6q oZ9w== MIME-Version: 1.0 X-Received: by 10.50.6.36 with SMTP id x4mr8879400igx.61.1448231906309; Sun, 22 Nov 2015 14:38:26 -0800 (PST) Received: by 10.36.217.196 with HTTP; Sun, 22 Nov 2015 14:38:26 -0800 (PST) In-Reply-To: <565237C9.10904@passap.ru> References: <564AF74A.2090700@snakeoilproductions.net> <5651B5B6.1010701@snakeoilproductions.net> <20151122195446.GA16398@dendrobates.araler.com> <565237C9.10904@passap.ru> Date: Sun, 22 Nov 2015 14:38:26 -0800 Message-ID: Subject: Re: Panic while waiting on wlan0 From: Adrian Chadd To: Boris Samorodov Cc: Sergey Manucharian , freebsd-current , Florian Limberger Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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, 22 Nov 2015 22:38:27 -0000 hi, iwm needs a maintainer and a lot of work. :) -a On 22 November 2015 at 13:46, Boris Samorodov wrote: > 22.11.15 22:54, Sergey Manucharian =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>> On 22 November 2015 at 04:31, Florian Limberger >>> wrote: >>>> On 17.11.15 17:42, Adrian Chadd wrote: >>>>> >>>>> try updating to head as of today. Some callout issues were fixed. >>>> >>>> The crashes are fixed alright, thank you. I still have a rather diffi= cult >>>> to reproduce issue, where the wpa_supplicant hangs in SCANNING state >>>> indefinitely, even if the Notebook is very near to the AP. I=E2=80=99= ve had this >>>> issue occasionally before, but since the crashes started it has become= more >>>> frequent. Is there anything I can do to debug the behaviour? Until n= ow I >>>> have only observed it in wpa_supplicant and have no idea how I might >>>> proceed. >>>> >>> Excerpts from Adrian Chadd's message from Sun 22-Nov-15 08:52: >>> >>> Do this: >>> >>> * compile in IEEE80211_DEBUG; >>> * do "wlandebug +scan" >>> >>> That way we can see if net80211 is refusing to continue scanning. >> >> I have a similar well-reproducable crash on my ThinkPad with "iwn" >> driver and "iwn6000fw" when I try to restart wlan: >> >> # service netif restart >> >> Otherwise it works fine, no problem at all. > > After upgrade from FreeBSD-amd64-HEAD-r290730 to r291148 I've got a > panic with wlan0 (iwm though): > ftp://ftp.wart.ru/pub/misc/panic-iwn-1.jpg > ftp://ftp.wart.ru/pub/misc/panic-iwn-2.jpg > > % kldstat | grep iwm > 12 1 0xffffffff822c5000 21a18 if_iwm.ko > 13 1 0xffffffff822e7000 ab9e0 iwm7265fw.ko > > -- > WBR, bsam