From: Larry Finger <Larry.Finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Your netbook
Date: Tue, 30 Mar 2010 16:30:42 -0500 [thread overview]
Message-ID: <4BB26D82.6020805@lwfinger.net> (raw)
In-Reply-To: <20100330202848.GO13120@tuxdriver.com>
On 03/30/2010 03:28 PM, John W. Linville wrote:
> On Tue, Mar 30, 2010 at 10:23:51AM -0500, Larry Finger wrote:
>
>> If possible, I would like you to do one more test on that troublesome netbook.
>> Please build a kernel with CONFIG_MMIOTRACE=y and build the Broadcom wl driver
>> for it. Starting with wl unloaded, issue the following commands (as root):
>>
>> echo 10000 > /sys/kernel/debug/tracing/buffer_size_kb
>> echo mmiotrace > /sys/kernel/debug/tracing/current_tracer
>> cat /sys/kernel/debug/tracing/trace_pipe > wl_dump.txt &
>> modprobe -v wl
>>
>> After the wireless network device gets created, etc., then
>>
>> echo nop > /sys/kernel/debug/tracing/current_tracer
>> sleep 1
>> killproc cat
>>
>> and send me the file wl_dump.txt. With it, I will be able to see if the Broadcom
>> driver is actually finding an SPROM that b43 is missing.
>
> Done:
>
> http://www.kernel.org/pub/linux/kernel/people/linville/ssb-debug/wl_dump.txt.gz
>
> Hth!
It has already. The clue was in the fragment I sent you earlier. Every other
BCM43XX card that we have seen had its SPROM starting at offset 0x1000 relative
to the start of the MMIO mapping. Yours is at 0x0800! I would have hoped for an
"incorrect CRC" message, but we got the hang instead. I now have to find the
hidden flag that lets us know about the different location. I wonder what else
has moved.
As a warning to users of wl. I tried to run it from the 2.6.34-rc3 on Linus's
tree. Broadcom (I really like the other variation of that name!) has not (yet)
discovered the change in the DMA API in 2.6.34. As a result, I got a few "tries
to free DMA memory it has not allocated" warnings followed by a lot of other
stuff concluding in a kernel panic - the first I've had for a long time. Note: I
will not be debugging this problem. I have enough to do already.
Larry
prev parent reply other threads:[~2010-03-30 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 15:23 Your netbook Larry Finger
2010-03-30 20:28 ` John W. Linville
2010-03-30 20:50 ` Larry Finger
2010-03-30 21:30 ` Larry Finger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BB26D82.6020805@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.