---- "Gábor Stefanik" <netrolller...@gmail.com> wrote: 
> On Fri, Oct 2, 2009 at 11:04 PM,  <fre...@carolina.rr.com> wrote:
> >
> > Hi Folks --
> >
> > I've read in the archives about DMA errors with the LP-PHY, but there didn't
> > seem to be any conclusion.  Any guidance on what I can test to get it 
> > working?
> > It's reproducable on my Lenovo G530 laptop.  (Yes, I know forcing PIO works 
> > for
> > others, and it works for me too, but I'd like to help testing if I can).
> >
> > Any guidance on which tests would be most likely to work?  AFAIK, options to
> > test include:
> > * 64bit kernel (and userland?)
> > * Hack b43/dma.c to force fallback to 32bit DMA (as a trial datapoint only)
> 
> Won't work - LP-PHY only supports 64bit DMA.
> 
> > * Boot with Mem=2G.  Currently 4G ram is installed.
> > * Firmware 5xx
> >
> > Or is this a HW design error in the laptop, and I should just live with 
> > forcing PIO?
> >
> > My system details:
> > * Compat-wireless-2009-09-30 (and also back to 9-21)
> > * Fedora Rawhide 32-bit, kernel 2.6.31.1-56.fc12.i686
> > * Firmware 478.104
> > * Fatal DMA error soon after heavy traffic starts
> >
> 
> Try installing a proper wireless-testing kernel (not just
> compat-wireless). This issue seems to specifically affect
> 2.6.31+compat-wireless users (probably something needs to be
> backported). 2.6.32-rc1+compat-wireless shoud also work.

Thanks!  I cloned the latest wireless-testing from last night, 2.6.32-rc3 I 
think.  That seems to work so far, with several hundreds of MB FTP transfers 
OK.  Previously DMA errors would show up immediately after starting the 
transfer.  Still get the "NOHZ: local_softirq_pending" stuff.  I will test more 
transfers and a suspend/resume cycle later tonight, as Lance has reported.  

Any chance of finding out what needs to be fixed for 2.6.31?  Fedora is about 
to release F12 with a 2.6.31 kernel, and it would be great to be able to 
backport a fix.  I'm a git noob, but I don't see how to bisect between the 
wireless-testing tree and compat-wireless.

Lance, you wrote that if you cold boot, then 'sometimes' you can connect.  That 
means sometimes it *fails* after a cold boot too?  Same DMA errors?

regards, ......... Charlie

> 
> > dmesg extract:
> >
> > ssb: Sonics Silicon Backplane found on PCI device 0000:04:00.0
> > b43-phy0: Broadcom 4312 WLAN found (core revision 15)
> > b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1
> > b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2
> > phy0: Selected rate control algorithm 'minstrel'
> > Registered led device: b43-phy0::tx
> > Registered led device: b43-phy0::rx
> > Registered led device: b43-phy0::radio
> > Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
> > b43 ssb0:0: firmware: requesting b43/ucode15.fw
> > cfg80211: Calling CRDA for country: US
> > cfg80211: Regulatory domain changed to country: US
> >        (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> >        (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
> >        (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
> >        (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> >        (5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> >        (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
> > b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
> > b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
> > b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> > b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz.
> > b43-phy0 debug: RC calib: Failed to switch to channel 7, error = -5
> > b43-phy0 debug: Chip initialized
> > b43-phy0 debug: 64-bit DMA initialized
> > b43-phy0 debug: QoS enabled
> > b43-phy0 debug: Wireless interface started
> > b43-phy0 debug: Adding Interface type 2
> > ADDRCONF(NETDEV_UP): wlan0: link is not ready
> > wlan0: deauthenticating from 00:0c:41:e2:f9:81 by local choice (reason=3)
> > wlan0: direct probe to AP 00:0c:41:e2:f9:81 (try 1)
> > wlan0: direct probe responded
> > wlan0: authenticate with AP 00:0c:41:e2:f9:81 (try 1)
> > wlan0: authenticated
> > wlan0: associate with AP 00:0c:41:e2:f9:81 (try 1)
> > wlan0: RX AssocResp from 00:0c:41:e2:f9:81 (capab=0x411 status=0 aid=2)
> > wlan0: associated
> > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> > b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac:
> > ff:ff:ff:ff:ff:ff
> > NOHZ: local_softirq_pending 08
> > NOHZ: local_softirq_pending 08
> > NOHZ: local_softirq_pending 08
> > NOHZ: local_softirq_pending 08
> > NOHZ: local_softirq_pending 08
> > NOHZ: local_softirq_pending 08
> > NOHZ: local_softirq_pending 08
> > NOHZ: local_softirq_pending 08
> > NOHZ: local_softirq_pending 08
> > NOHZ: local_softirq_pending 08
> > wlan0: no IPv6 routers present
> > CE: hpet increasing min_delta_ns to 15000 nsec
> > b43-phy0 ERROR: Fatal DMA error: 0x00000000, 0x00000400, 0x00000000, 
> > 0x00000000,
> > 0x00000000, 0x00000000
> > b43-phy0: Controller RESET (DMA error) ...
> > b43-phy0 debug: Wireless interface stopped
> > b43-phy0 debug: DMA-64 rx_ring: Used slots 8/64, Failed frames 0/0 = 0.0%,
> > Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_AC_BK: Used slots 0/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_AC_BE: Used slots 256/256, Failed frames 
> > 0/7742 =
> > 0.0%, Average tries 1.37
> > b43-phy0 debug: DMA-64 tx_ring_AC_VI: Used slots 0/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_AC_VO: Used slots 2/256, Failed frames 0/555 
> > =
> > 0.0%, Average tries 1.01
> > b43-phy0 debug: DMA-64 tx_ring_mcast: Used slots 0/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> > b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz.
> > b43-phy0 debug: Chip initialized
> > b43-phy0 debug: 64-bit DMA initialized
> > b43-phy0 debug: QoS enabled
> > b43-phy0 debug: Wireless interface started
> > b43-phy0: Controller restarted
> > b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 
> > 0x00000000,
> > 0x00000000, 0x00000000
> > b43-phy0: Controller RESET (DMA error) ...
> > b43-phy0 debug: Wireless interface stopped
> > b43-phy0 debug: DMA-64 rx_ring: Used slots 0/64, Failed frames 0/0 = 0.0%,
> > Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_AC_BK: Used slots 0/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_AC_BE: Used slots 1/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_AC_VI: Used slots 0/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_AC_VO: Used slots 2/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_mcast: Used slots 0/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> > b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz.
> > b43-phy0 debug: Chip initialized
> > b43-phy0 debug: 64-bit DMA initialized
> > b43-phy0 debug: QoS enabled
> > b43-phy0 debug: Wireless interface started
> > b43-phy0: Controller restarted
> > b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 
> > 0x00000000,
> > 0x00000000, 0x00000000
> > b43-phy0: Controller RESET (DMA error) ...
> > b43-phy0 debug: Wireless interface stopped
> > b43-phy0 debug: DMA-64 rx_ring: Used slots 0/64, Failed frames 0/0 = 0.0%,
> > Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_AC_BK: Used slots 0/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_AC_BE: Used slots 0/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_AC_VI: Used slots 0/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_AC_VO: Used slots 0/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0 debug: DMA-64 tx_ring_mcast: Used slots 0/256, Failed frames 0/0 =
> > 0.0%, Average tries 0.00
> > b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> > b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz.
> > b43-phy0 debug: Chip initialized
> > b43-phy0 debug: 64-bit DMA initialized
> > b43-phy0 debug: QoS enabled
> >
> > etc etc.
> >
> > regards, .............. Charlie
> >
> > _______________________________________________
> > Bcm43xx-dev mailing list
> > Bcm43xx-dev@lists.berlios.de
> > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
> >
> 
> 
> 
> -- 
> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)

_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to