Re: 14e4:4315 DMA Errors (still)
Hi Gábor, Charlie, All: I tried wireless-testing commit b4d3a7.. This kernel seems to work more reliably, but only a little. Sometimes, I still get DMA errors on cold boot, and I still always get DMA errors after a suspend/resume cycle. Like Charlie, 'NOHZ: local_softirq_pending 08' shows up when it does manage to connect.. I certainly wish I could report the other successes Charlie has. Perhaps I'll update my wireless-testing tonight and try again. Lance 2009/10/6 Gábor Stefanik : > 2009/10/6 Lance Hepler : >> 2009/10/6 Gábor Stefanik : >>> So, this error happens specifically on suspend/resume? >> >> No, it'll happen pretty frequently the first time I try to connect, >> but always after I suspend+resume. And once the DMA error pops up, It >> just keeps happening.. By far, the rarest occurrence is the device >> actually working. >> >> Lance >> > > One thing I can see from the log is that you have both wl and ssb > (b43's backend) loaded at the same time. Remember to also unload ssb > when you unload b43. > > Also, could you try the real wireless-testing? > > (BTW, your card is a Dell 1397, which was one of the development cards > I used; so the problem is not a "new variant".) > > -- > 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
Re: 14e4:4315 DMA Errors (still)
On Tue, 6 Oct 2009 8:21:21 -0400 wrote: > "Gábor Stefanik" wrote: > > On Fri, Oct 2, 2009 at 11:04 PM, wrote: > > > 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. Still stable for me, ~10GB local and ISP transfers, and survives multiple suspend/resume cycles. Please let me know if I can help testing any way to get 2.6.31 + compat-wireless working. Thanks ! Charlie > 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 > ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 14e4:4315 DMA Errors (still)
2009/10/6 Lance Hepler : > 2009/10/6 Gábor Stefanik : >> So, this error happens specifically on suspend/resume? > > No, it'll happen pretty frequently the first time I try to connect, > but always after I suspend+resume. And once the DMA error pops up, It > just keeps happening.. By far, the rarest occurrence is the device > actually working. > > Lance > One thing I can see from the log is that you have both wl and ssb (b43's backend) loaded at the same time. Remember to also unload ssb when you unload b43. Also, could you try the real wireless-testing? (BTW, your card is a Dell 1397, which was one of the development cards I used; so the problem is not a "new variant".) -- 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
Re: 14e4:4315 DMA Errors (still)
2009/10/6 Gábor Stefanik : > So, this error happens specifically on suspend/resume? No, it'll happen pretty frequently the first time I try to connect, but always after I suspend+resume. And once the DMA error pops up, It just keeps happening.. By far, the rarest occurrence is the device actually working. Lance ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 14e4:4315 DMA Errors (still)
"Gábor Stefanik" wrote: > On Fri, Oct 2, 2009 at 11:04 PM, 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 :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 @ 4 KHz), (300 mBi, 2700 mBm) > >(517 KHz - 525 KHz @ 4 KHz), (300 mBi, 1700 mBm) > >(525 KHz - 533 KHz @ 4 KHz), (300 mBi, 2000 mBm) > >(549 KHz - 571 KHz @ 4 KHz), (300 mBi, 2000 mBm) > >(5735000 KHz - 5835000 KHz @ 4 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: 0x, 0x0400, 0x, > > 0x, > > 0x, 0x > > b43-phy0: Con
Re: 14e4:4315 DMA Errors (still)
On Fri, Oct 2, 2009 at 11:04 PM, 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. > dmesg extract: > > ssb: Sonics Silicon Backplane found on PCI device :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 @ 4 KHz), (300 mBi, 2700 mBm) > (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 1700 mBm) > (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 2000 mBm) > (549 KHz - 571 KHz @ 4 KHz), (300 mBi, 2000 mBm) > (5735000 KHz - 5835000 KHz @ 4 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: 0x, 0x0400, 0x, > 0x, > 0x, 0x > 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: 0x04
14e4:4315 DMA Errors (still)
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) * 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 dmesg extract: ssb: Sonics Silicon Backplane found on PCI device :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 @ 4 KHz), (300 mBi, 2700 mBm) (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 1700 mBm) (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 2000 mBm) (549 KHz - 571 KHz @ 4 KHz), (300 mBi, 2000 mBm) (5735000 KHz - 5835000 KHz @ 4 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: 0x, 0x0400, 0x, 0x, 0x, 0x 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: 0x0400, 0x, 0x, 0x, 0x, 0x 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/
