From owner-freebsd-wireless@FreeBSD.ORG  Tue Apr  3 12:12:17 2012
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0CD48106564A;
	Tue,  3 Apr 2012 12:12:17 +0000 (UTC)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from locore.org (ns01.locore.org [218.45.21.227])
	by mx1.freebsd.org (Postfix) with ESMTP id AEC498FC0C;
	Tue,  3 Apr 2012 12:12:16 +0000 (UTC)
Received: from localhost (celeron.v4.locore.org [192.168.0.10])
	by locore.org (8.14.5/8.14.5/iwasaki) with ESMTP/inet id q33CCFFf068596;
	Tue, 3 Apr 2012 21:12:15 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Date: Tue, 03 Apr 2012 21:12:12 +0900 (JST)
Message-Id: <20120403.211212.59463568.iwasaki@jp.FreeBSD.org>
To: bschmidt@freebsd.org
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
In-Reply-To: <CAAgh0_ZuJ_dG-r7QnLRJ-NX8Ejmt1DpBehgYOMv-pt_tT4K0Yg@mail.gmail.com>
References: <20120403.200327.18305192.iwasaki@jp.FreeBSD.org>
	<CAAgh0_ZuJ_dG-r7QnLRJ-NX8Ejmt1DpBehgYOMv-pt_tT4K0Yg@mail.gmail.com>
X-Mailer: Mew version 3.3 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-wireless@freebsd.org
Subject: Re: [patch] iwi(4) watchdog broken
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussions of 802.11 stack,
	tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Apr 2012 12:12:17 -0000

Hi,
> > Suspend/Resume problem was solved (thanks bschmidt!),
> > however problem still remainds after watchdog messages like
> > `device timeout' or `firmware stuck in state 4, resetting'.
> 
> Honestly, I'd rather see the above issues fixed and not the workaround
> for it. ;)
> Do you have a test case to reproduce this?

Yap, ifconfig wlan0 scan on RELENG_8 always reproduce 'firmware stuck
in state 4, resetting'.

> So, if I get that correctly, the only difference is that you added a
> ieee80211_new_state_locked(vap, IEEE80211_S_INIT, -1); call, right?
> Any reason why not calling ieee80211_stop_all()/ieee80211_start_all()
> directly in iwi_restart()? This will call the appropriate
> iwi_init/stop functions.

Yes, I already tried that, wlan0 seems restarted but iwi0 not.
ifconfig show the status like this;
iwi0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290
[snip]
wlan0: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
[snip]

I wonder if only RELENG_8 has this problem because HEAD and RELENG_9
seems to be OK...