b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: linville@tuxdriver.com, zajec5@gmail.com,
	b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
	brcm80211-dev-list@broadcom.com
Subject: REGRESSION: [PATCH v2 0/9] bcma misc updates
Date: Tue, 3 Jul 2012 08:51:29 +0200	[thread overview]
Message-ID: <4FF29671.1020406@broadcom.com> (raw)
In-Reply-To: <1341013486-2520-1-git-send-email-hauke@hauke-m.de>

On 06/30/2012 01:44 AM, Hauke Mehrtens wrote:
> These are some updates for bcma. Some are extending or completing some 
> workarounds for PCIe based wireless cards. A patch adds 
> bcma_pmu_spuravoid_pllupdate, used by brcmsmac and an other patch adds 
> constants for the chip ids. This code is mostly based on code from 
> brcmsmac and the Broadcom SDK for BCM47XX SoCs.
> 
> This was tested on a BCM4718 SoC with a BCM43224 PCIe and a BCM5357.
> The Wifi part of the BCM4718 and BCM43224 is more or less working with 
> brcmsmac, which need some more patches for that, but it has low speed 
> and some times or with some access points I still get errors. The wifi 
> of the BCM5357 does not work.
> 

Hi Hauke,

This patch series caused a regression in one of our smoketest machines
last night. I have not looked at the exact patch causing it (suspect
2/9). The failure happens on a BCM43224 chip with external SPROM. Here
is the log info:

[317752.101665] bcma: Found chip with id 0xA8D8, rev 0x01 and package 0x08
[317752.101809] bcma: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800,
rev 0x22, class 0x0)
[317752.101827] bcma: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812,
rev 0x17, class 0x0)
[317752.101870] bcma: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev
0x0F, class 0x0)
[317752.171926] bcma: Failed to get SPROM: -71 <== -EPROTO (crc failed).
[317752.171982] bcma: Bus registered
[317753.184455] brcmsmac bcma0:0: mfg 4bf core 812 rev 23 class 0 irq 16
[317753.191868] brcmsmac: Applying 43224B0+ WARs
[317753.193918] ieee80211 phy0: wl0: brcms_b_attach: bad macaddr
[317753.193924] ieee80211 phy0: wl0: brcms_b_attach: failed with err 22
[317753.193928] ieee80211 phy0: wl0: brcms_c_attach: failed with err 22
[317753.193959] ieee80211 phy0: brcmsmac: attach() failed with code 22
[317753.193966] brcmsmac: brcms_bcma_probe: brcms_attach failed!

I suspect it tries reading OTP instead of the external SPROM.

Gr. AvS

  parent reply	other threads:[~2012-07-03  6:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 23:44 [PATCH v2 0/9] bcma misc updates Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 1/9] bcma: extend workaround for bcm4331 Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 2/9] bcma: add constants for chip ids Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 3/9] bcma: remove fix for 4329b0 bad LPOM is detection Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 4/9] bcma: add PCI ID for BCM43224 Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 5/9] bcma: complete workaround for BCMA43224 and BCM4313 Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 6/9] bcma: remove bcma_pmu_{pll,swreg}_init() Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 7/9] bcma: remove chip ids doing nothing from PMU initialization Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 8/9] bcma: add bcma_pmu_spuravoid_pllupdate() Hauke Mehrtens
2012-06-29 23:44 ` [PATCH v2 9/9] bcma: add mdelay bcma_pmu_resources_init() Hauke Mehrtens
2012-06-30  9:19 ` [PATCH v2 0/9] bcma misc updates Rafał Miłecki
2012-07-03  6:51 ` Arend van Spriel [this message]
2012-07-03  7:44   ` REGRESSION: " Hauke Mehrtens
2012-07-03  8:22     ` Arend van Spriel
2012-07-16 21:44       ` Hauke Mehrtens
2012-07-17  7:31         ` 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=4FF29671.1020406@broadcom.com \
    --to=arend@broadcom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=zajec5@gmail.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 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).