From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ray Lee Subject: Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble? Date: Wed, 15 Nov 2006 11:41:40 -0800 Message-ID: <455B6D74.2020507@madrabbit.org> References: <455B63EC.8070704@madrabbit.org> <200611152015.07844.mb@bu3sch.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Larry Finger , Bcm43xx-dev@lists.berlios.de, LKML , netdev@vger.kernel.org, John Linville , Andrew Morton Return-path: Received: from tapsys.com ([72.36.178.242]:3255 "EHLO tapsys.com") by vger.kernel.org with ESMTP id S1161145AbWKOTmo (ORCPT ); Wed, 15 Nov 2006 14:42:44 -0500 To: Michael Buesch In-Reply-To: <200611152015.07844.mb@bu3sch.de> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Michael Buesch wrote: > On Wednesday 15 November 2006 20:01, Ray Lee wrote: >> Suggestions? Requests for even more info? > > Yeah, enable bcm43xx debugging. Sigh, didn't even think to look for that. Okay, enabled and compiling a new kernel. This will take a few days to trigger, if the pattern holds, so in the meantime, any *other* thoughts?