[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1286538243.21485.298.camel@constitution.bos.jonmasters.org>
Date: Fri, 08 Oct 2010 07:44:03 -0400
From: Jon Masters <jonathan@...masters.org>
To: linux-wireless@...r.kernel.org
Cc: Brett Rudley <brudley@...adcom.com>,
Henry Ptasinski <henryp@...adcom.com>,
Nohee Ko <noheek@...adcom.com>,
Jon Masters <jcm@...masters.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: PROBLEM: brcm80211 hangs on 2.6.36-0.34.rc6.git3.fc15.x86_64
On Fri, 2010-10-08 at 02:58 -0400, Jon Masters wrote:
> I tried building the new brcm80211 driver from staging-next on Fedora rawhide
> kernel 2.6.36-0.34.rc6.git3.fc15.x86_64. Now, of course, it's not the
> staging-next kernel (I'll try that now this doesn't work) but perhaps this
> report will still be of use to the Broadcom/other wireless folks.
I pulled the latest staging-next onto Linus' latest git tree and still
experience problems with the driver. It seems that the first attempt to
actually transmit results in the system locking hard. Once again, I am
attaching the output from running a netconsole (due to the box I'm on,
it's an attachment this time, sorry about that - don't trust evolution)
where the trace is basically the same as the original trace I posted.
NOTE: in both cases, the driver is loaded with "msglevel=2
phymsglevel=2" which (although not documented) suggests to enable
tracing, and does certainly yield more debugging output.
Jon.
View attachment "netconsole_brcm80211_2.6.32-rc7+_20101008_1.txt" of type "text/plain" (14347 bytes)
Powered by blists - more mailing lists