netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* bcm43xx scan oops!!!
@ 2006-10-10  3:14 Jory A. Pratt
  2006-10-10 10:17 ` Michael Buesch
  0 siblings, 1 reply; 5+ messages in thread
From: Jory A. Pratt @ 2006-10-10  3:14 UTC (permalink / raw)
  To: netdev

(gdb) list *bcm43xx_dma_handle_xmitstatus+0xbd
0x3ad is in bcm43xx_dma_handle_xmitstatus (include/asm/dma-mapping.h:91).
86    static inline void
87    dma_unmap_single(struct device *dev, dma_addr_t addr,size_t size,
88             int direction)
89    {
90        BUG_ON(!valid_dma_direction(direction));
91        dma_ops->unmap_single(dev, addr, size, direction);
92    }
93    
94    #define dma_map_page(dev,page,offset,size,dir) \
95        dma_map_single((dev), page_address(page)+(offset), (size), (dir))


http://home.nctv.com/anarchy/dscape-clean.jpg

bcm43xx causes kernel oops on 4318 with latest wireless-dev git.

Jory



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: bcm43xx scan oops!!!
  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>
  0 siblings, 2 replies; 5+ messages in thread
From: Michael Buesch @ 2006-10-10 10:17 UTC (permalink / raw)
  To: Jory A. Pratt; +Cc: netdev

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?

-- 
Greetings Michael.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: bcm43xx scan oops!!!
  2006-10-10 10:17 ` Michael Buesch
@ 2006-10-10 13:38   ` Jory A. Pratt
       [not found]   ` <452BACF2.60900@nctv.com>
  1 sibling, 0 replies; 5+ messages in thread
From: Jory A. Pratt @ 2006-10-10 13:38 UTC (permalink / raw)
  To: Michael Buesch; +Cc: netdev

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?
>
>   
No that is version 3.x.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: bcm43xx scan oops!!!
       [not found]   ` <452BACF2.60900@nctv.com>
@ 2006-10-10 21:06     ` Michael Buesch
  2006-10-10 21:44       ` Jory A. Pratt
  0 siblings, 1 reply; 5+ messages in thread
From: Michael Buesch @ 2006-10-10 21:06 UTC (permalink / raw)
  To: Jory A. Pratt; +Cc: netdev

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. ;)

-- 
Greetings Michael.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: bcm43xx scan oops!!!
  2006-10-10 21:06     ` Michael Buesch
@ 2006-10-10 21:44       ` Jory A. Pratt
  0 siblings, 0 replies; 5+ messages in thread
From: Jory A. Pratt @ 2006-10-10 21:44 UTC (permalink / raw)
  To: Michael Buesch; +Cc: netdev

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2006-10-10 21:45 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).