linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Hintz <nlhintz@hotmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: brcmsmac: Data bus error in reading tsf_random
Date: Mon, 3 Dec 2012 04:47:38 +0000 (UTC)	[thread overview]
Message-ID: <loom.20121203T054035-582@post.gmane.org> (raw)
In-Reply-To: 50BAB095.2070103@hauke-m.de

Hauke Mehrtens <hauke@...> writes:

> 
> Hi Arend,
> 
> I am getting a Data bus error when brcmsmac tries to read tsf_random in
> brcms_c_wme_setparams. This does not happen when I add a printk
> somewhere near that read of tsf_random or when I replace the read with a
> constant. In b43 this code works, without this error for me, see
> b43_qos_params_upload(). With the BCM4716 I do not have this problem. It
> could be that this is caused by the broken PCIe controller in the BCM4716.
> 
> I am using brcmsmac from compat-wireless 2012-09-07, but I have also
> tried the most recent brcmsmac code from wireless-testing. brcmsmac uses
> the normal firmware from linux-firmware and I have also tried the new
> firmware posted some days ago with the same result.
> 
> I am using a BCM43224 connected to the PCIe controller of the BCM4716.
> 
> Are there any special requirements for reading tsf_random under mips?
> 
> To make my BCM43224 work I use this patch [0], the "printk("dummy\n");"
> is a hack to workaround the problem I am describing here.
> 
> Hauke
> 
> [0]:
>

<snip>

I encountered a similar DBE using the "broadcom-wl" driver (OpenWRT) on a 
Linksys E3000; except that it occurred when reading "ifs_ctl" (offset 0x688).  
I too tried putting in some printk's (in linux_osl.c), which caused the 
problem to go away.  I eventually found that doing a dummy read of 4 bytes 
at that particular address just prior to the actual two byte read caused 
the problem to go away as well (an ugly hack).  I can reproduce it if you 
want a stack trace.

Nathan



  reply	other threads:[~2012-12-03  4:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-02  1:36 brcmsmac: Data bus error in reading tsf_random Hauke Mehrtens
2012-12-03  4:47 ` Nathan Hintz [this message]
2012-12-03 16:19   ` Larry Finger
2012-12-03 20:40 ` Arend van Spriel

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=loom.20121203T054035-582@post.gmane.org \
    --to=nlhintz@hotmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).