netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jory A. Pratt" <anarchy@nctv.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: netdev@vger.kernel.org
Subject: Re: bcm43xx scan oops!!!
Date: Tue, 10 Oct 2006 16:44:43 -0500	[thread overview]
Message-ID: <452C144B.9040006@nctv.com> (raw)
In-Reply-To: <200610102306.16143.mb@bu3sch.de>

Michael Buesch wrote:
> On Tuesday 10 October 2006 16:23, Jory A. Pratt wrote:
>   
>> Michael Buesch wrote:
>>     
>>> On Tuesday 10 October 2006 05:14, Jory A. Pratt wrote:
>>>   
>>>       
>>>> http://home.nctv.com/anarchy/dscape-clean.jpg
>>>>     
>>>>         
>>> That's hardly readable.
>>> But which firmware are you running? v4.x by chance?
>>>
>>>   
>>>       
>> Just for completeness I just tested with v4.x firmware and still get the 
>> panic
>>     
>
> 4.x firmware won't work. Make sure to use 3.x.
>
> I am not sure what happens.
> Any chance to get a more complete oops message? I am also interrested
> in the start of the oops message. In particular I would like to see if this
> is a NULL pointer bug, machine check or something else.
> The backtrace is a little big weird. So I am not sure what happens.
>
> And, Please make _really_ sure to use 3.x firmware. ;)
>
>   
alright here are two more pics for you.

http://home.nctv.com/anarchy/dscape-clean1.jpg
http://home.nctv.com/anarchy/dscape-clean2.jpg


Here is a bit of dmesg that you might find useful:

ssb: Core 0 found: cc 0800, rev 0D, vendor 4243
ssb: Core 1 found: cc 0812, rev 09, vendor 4243
ssb: Core 2 found: cc 0804, rev 0C, vendor 4243
ssb: Core 3 found: cc 080D, rev 07, vendor 4243
bcm43xx_d80211: Broadcom 4318 WLAN found
ssb: Switching to core 2
ssb: Switching to core 1
bcm43xx_d80211: PHY connected
bcm43xx_d80211: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx_d80211: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx_d80211: Radio turned off
bcm43xx_d80211: Radio turned off
wmaster0: Selected rate control algorithm 'simple'
bcm43xx_d80211: Virtual interface added (type: 0x00000002, ID: 5, MAC: 
00:90:4b:f2:30:e9)
ssb: Switching to core 0
ssb: Switching to core 1
bcm43xx_d80211: PHY connected
bcm43xx_d80211: firmware revision 127, patchlevel E, date 2005-04-18 
02:36:27
ssb: Switching to core 0
bcm43xx_d80211: InitVals (bcm43xx_initvalXX.fw) file-format error. 
Please fix your bcm43xx firmware files.
bcm43xx_d80211: core_up for active 802.11 core failed (-71)
bcm43xx_d80211: Virtual interface removed (type: 0x00000002, ID: 5, MAC: 
00:90:4b:f2:30:e9)
bcm43xx_d80211: Virtual interface added (type: 0x00000002, ID: 5, MAC: 
00:90:4b:f2:30:e9)
ssb: Switching to core 1
bcm43xx_d80211: firmware revision 127, patchlevel E, date 2005-04-18 
02:36:27
ssb: Switching to core 0
ssb: Switching to core 1
bcm43xx_d80211: Radio turned on
bcm43xx_d80211: ASSERTION FAILED (radio_attenuation < 10) at: 
drivers/net/wireless/d80211/bcm43xx/bcm43xx_phy.c:1490:bcm43xx_find_lopair()
bcm43xx_d80211: ASSERTION FAILED (radio_attenuation < 10) at: 
drivers/net/wireless/d80211/bcm43xx/bcm43xx_phy.c:1490:bcm43xx_find_lopair()
bcm43xx_d80211: ASSERTION FAILED (radio_attenuation < 10) at: 
drivers/net/wireless/d80211/bcm43xx/bcm43xx_phy.c:1490:bcm43xx_find_lopair()
ssb: Switching to core 0
ssb: Switching to core 1
bcm43xx_d80211: Chip initialized
bcm43xx_d80211: 32-bit DMA initialized
bcm43xx_d80211: Keys cleared
bcm43xx_d80211: Selected 802.11 core (phytype 2)
bcm43xx_d80211: ASSERTION FAILED (radio_attenuation < 10) at: 
drivers/net/wireless/d80211/bcm43xx/bcm43xx_phy.c:1490:bcm43xx_find_lopair()
wmaster0: Does not support passive scan, disabled
wlan0: no IPv6 routers present

      reply	other threads:[~2006-10-10 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10  3:14 bcm43xx scan oops!!! Jory A. Pratt
2006-10-10 10:17 ` Michael Buesch
2006-10-10 13:38   ` Jory A. Pratt
     [not found]   ` <452BACF2.60900@nctv.com>
2006-10-10 21:06     ` Michael Buesch
2006-10-10 21:44       ` Jory A. Pratt [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=452C144B.9040006@nctv.com \
    --to=anarchy@nctv.com \
    --cc=mb@bu3sch.de \
    --cc=netdev@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).