From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755326AbWKRTG7 (ORCPT ); Sat, 18 Nov 2006 14:06:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755327AbWKRTG6 (ORCPT ); Sat, 18 Nov 2006 14:06:58 -0500 Received: from ms-smtp-02.rdc-kc.rr.com ([24.94.166.122]:47574 "EHLO ms-smtp-02.rdc-kc.rr.com") by vger.kernel.org with ESMTP id S1755326AbWKRTG5 (ORCPT ); Sat, 18 Nov 2006 14:06:57 -0500 Message-ID: <455F59BB.6060204@lwfinger.net> Date: Sat, 18 Nov 2006 13:06:35 -0600 From: Larry Finger User-Agent: Thunderbird 1.5.0.8 (X11/20061025) MIME-Version: 1.0 To: Chris Wright CC: linux-kernel@vger.kernel.org, stable@kernel.org, Justin Forbes , Zwane Mwaikambo , "Theodore Ts'o" , Randy Dunlap , Dave Jones , Chuck Wolber , Chris Wedgwood , Michael Krufky , torvalds@osdl.org, akpm@osdl.org, alan@lxorguk.ukuu.org.uk, netdev@vger.kernel.org, mb@bu3sch.de, greg@kroah.com, "John W. Linville" Subject: Re: [patch 07/30] bcm43xx: Drain TX status before starting IRQs References: <20061116024332.124753000@sous-sol.org> <20061116024511.458086000@sous-sol.org> In-Reply-To: <20061116024511.458086000@sous-sol.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Chris Wright wrote: > -stable review patch. If anyone has any objections, please let us know. > ------------------ > > From: Michael Buesch > > Drain the Microcode TX-status-FIFO before we enable IRQs. > This is required, because the FIFO may still have entries left > from a previous run. Those would immediately fire after enabling > IRQs and would lead to an oops in the DMA TXstatus handling code. > > Cc: "John W. Linville" > Signed-off-by: Michael Buesch > Signed-off-by: Larry Finger > Signed-off-by: Chris Wright > --- Chris, The regression turns out to be a locking problem involving bcm43xx, wpa_supplicant, and NetworkManager. The exact cause is unknown; however, this patch is clearly not the problem. Please reinstate it for inclusion in -stable. Thanks, Larry