From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Vine Date: Wed, 1 Jun 2011 13:08:42 +0100 Subject: b43 error under heavy load In-Reply-To: References: <4CEAB969.20702@lwfinger.net> <1290451982.20888.2.camel@maggie> <4CEAC095.7020706@lwfinger.net> <4DC9853A.1090508@lwfinger.net> <20110601114839.433ae42d@boulder.homenet> Message-ID: <20110601130842.077da1c3@boulder.homenet> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Cc: Larry Finger , wireless , Michael =?ISO-8859-1?B?QvxzY2g=?= , b43-dev On Wed, 1 Jun 2011 12:56:22 +0200 Rafa? Mi?ecki wrote: > 2011/6/1 Chris Vine : > > On Wed, 1 Jun 2011 11:23:45 +0200 > > Rafa? Mi?ecki wrote: > >> AFAIK to enable this debugging you only need to: > >> echo 1 > /sys/kernel/debug/b43/phy0/debug_dmaverbose > > > > I don't have a /sys/kernel/debug directory with a running 3.0.0-rc1 > > kernel, so it appears that b43 debugging (which I do have enabled) > > doesn't use it. > > mount -t debugfs none /sys/kernel/debug/ Ah, so I need to compile in debugfs. That isn't/wasn't necessary for the DMA error debugging. I am surprised that debugfs enables you to alter kernel debugging levels on the fly (I thought it was a passive logging mechanism for kernel state), but you live and learn. I will compile in debugfs, but I don't expect to have any rapid results for you. With 3 and a half hours of streaming yesterday it happened once. I won't be able to do much testing by way of transferring files over the LAN for a while either (I imagine that would provide greater stress testing). Chris