Re: b43/BCM4312 fails with DMA errors
On Fri, 23 Oct 2009 08:48:38 -0500 Larry Finger larry.fin...@lwfinger.net wrote: On 10/23/2009 05:46 AM, Chris Vine wrote: I will probably do that (maybe), but nonetheless I have identified the offending ACPI module. If I blacklist the 'processor' module then b43 works. I strongly suspect that kernel ACPI does not at present deal correctly with Atom N270 idle states. Good find. Please file a bugzilla for this problem. I'll send an e-mail to the linux-apci mailing list (probably tomorrow or Monday), and following that if still needed I'll file a kernel bugzilla item. Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Fri, 23 Oct 2009 06:25:33 +0200 Peter Stuge pe...@stuge.se wrote: Chris Vine wrote: The problem is not with b43, but with ACPI. The debugging will need to be done by that set of devs. OK. I may try blacklisting different ACPI modules and see if I can identify which one is causing the problem. I'd suggest to go directly to the ACPI mailing list, do not pass go. :) They will want you to do more, and other, testing in order to track down the problem. I will probably do that (maybe), but nonetheless I have identified the offending ACPI module. If I blacklist the 'processor' module then b43 works. I strongly suspect that kernel ACPI does not at present deal correctly with Atom N270 idle states. As a side note, with kernel 2.6.32 the 'thermal' module is not dependent (so far as loading is concerned) on the 'processor' module and is not troublesome, although I am not certain it actually does anything (cpu temperatures and operation of the fan seems to be controlled by the BIOS on my machine): nonetheless I install 'thermal' out of superstition. Anyway, that appears to be a temporary fix until any ACPI bugs are sorted out. Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On 10/23/2009 05:46 AM, Chris Vine wrote: I will probably do that (maybe), but nonetheless I have identified the offending ACPI module. If I blacklist the 'processor' module then b43 works. I strongly suspect that kernel ACPI does not at present deal correctly with Atom N270 idle states. Good find. Please file a bugzilla for this problem. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Thursday 22 October 2009 01:05:31 Larry Finger wrote: On 10/21/2009 04:16 PM, Chris Vine wrote: On Wed, 21 Oct 2009 14:30:49 -0500 Larry Finger larry.fin...@lwfinger.net wrote: On 10/20/2009 04:56 PM, Chris Vine wrote: On Mon, 19 Oct 2009 16:53:24 -0500 Larry Finger larry.fin...@lwfinger.net wrote: This set of dmesg outputs was better; however, please set CONFIG_B43_DEBUG=y in your configuration and rebuild the kernel. Please post the full dmesg for warm and cold reboot. Thanks for the output. Unfortunately, it all looks normal. On auditing the DMA code for b43, I re-discovered a work-around that was necessary for the first card that had 64-bit DMA, namely a 4311/2. The fix for that is not needed for the 4315 card. Please apply the attached patch (b43_change_dma_flags) to see if it fixes the problem. If this patch does not fix the problem, I am working on a second to try to do further debugging. Hi, It doesn't fix it, I'm afraid. Then try this patch without the previous one. It will generate some warnings but they are harmless. Larry This only prints the lower 32bits of the DMA mapping, so I think it's not that useful for debugging without doing bad assumptions. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
Chris, Michael was right in that my previous debug messages were badly setup. Please try the attached patch as a replacement for the previous one. It will look at the data that is pushed into the DMA descriptors. I also reviewed the thread. Have you tried acpi=off and apic=off? Thanks, Larry Index: wireless-testing/drivers/net/wireless/b43/dma.c === --- wireless-testing.orig/drivers/net/wireless/b43/dma.c +++ wireless-testing/drivers/net/wireless/b43/dma.c @@ -165,6 +165,7 @@ static void op64_fill_descriptor(struct u32 ctl0 = 0, ctl1 = 0; u32 addrlo, addrhi; u32 addrext; + static int count; slot = (int)((desc-dma64) - descbase); B43_WARN_ON(!(slot = 0 slot ring-nr_slots)); @@ -190,6 +191,10 @@ static void op64_fill_descriptor(struct desc-dma64.control1 = cpu_to_le32(ctl1); desc-dma64.address_low = cpu_to_le32(addrlo); desc-dma64.address_high = cpu_to_le32(addrhi); + if (count++ 10) + b43dbg(ring-dev-wl, cntrl0, cntrl1, addrlo, addrhi: 0x%X 0x%X + 0x%X 0x%X\n, desc-dma64.control0, desc-dma64.control1, + desc-dma64.address_low, desc-dma64.address_high); } static void op64_poke_tx(struct b43_dmaring *ring, int slot) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Thu, 22 Oct 2009 17:06:53 -0500 Larry Finger larry.fin...@lwfinger.net wrote: Chris, Michael was right in that my previous debug messages were badly setup. Please try the attached patch as a replacement for the previous one. It will look at the data that is pushed into the DMA descriptors. I also reviewed the thread. Have you tried acpi=off and apic=off? No, I hadn't. But on doing so, booting with acpi=off makes b43 work correctly. In the light of this, do you want me to continue with this debugging? I have to say though that I would be very reluctant to run my netbook without ACPI: amongst other things, the power, lid and thermal events won't work. If this is not resolvable with b43, I think I would probably have to go with the wl driver. Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Do, 2009-10-22 at 17:06 -0500, Larry Finger wrote: + static int count; count is declared, and incremented, but never set to 0. I guess this will work anyway, because it might be magically cleared to 0 by defining it (it is static, and will probably be allocated to some place that is zeroed before), but I'd find it much cleaner if this was declared like static int count = 0; slot = (int)((desc-dma64) - descbase); B43_WARN_ON(!(slot = 0 slot ring-nr_slots)); @@ -190,6 +191,10 @@ static void op64_fill_descriptor(struct desc-dma64.control1 = cpu_to_le32(ctl1); desc-dma64.address_low = cpu_to_le32(addrlo); desc-dma64.address_high = cpu_to_le32(addrhi); + if (count++ 10) + b43dbg(ring-dev-wl, cntrl0, cntrl1, addrlo, addrhi: 0x%X 0x%X + 0x%X 0x%X\n, desc-dma64.control0, desc-dma64.control1, + desc-dma64.address_low, desc-dma64.address_high); } ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On 10/22/2009 05:46 PM, Chris Vine wrote: No, I hadn't. But on doing so, booting with acpi=off makes b43 work correctly. In the light of this, do you want me to continue with this debugging? I have to say though that I would be very reluctant to run my netbook without ACPI: amongst other things, the power, lid and thermal events won't work. If this is not resolvable with b43, I think I would probably have to go with the wl driver. No, do not bother with the most-recent patch. The problem is not with b43, but with ACPI. The debugging will need to be done by that set of devs. If you want to forgo that debug step and switch to wl, then do so. Of course, you will never know when the ACPI bug will hit you again, and what the problem will be. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Thu, 22 Oct 2009 17:55:55 -0500 Larry Finger larry.fin...@lwfinger.net wrote: On 10/22/2009 05:46 PM, Chris Vine wrote: No, I hadn't. But on doing so, booting with acpi=off makes b43 work correctly. In the light of this, do you want me to continue with this debugging? I have to say though that I would be very reluctant to run my netbook without ACPI: amongst other things, the power, lid and thermal events won't work. If this is not resolvable with b43, I think I would probably have to go with the wl driver. No, do not bother with the most-recent patch. The problem is not with b43, but with ACPI. The debugging will need to be done by that set of devs. If you want to forgo that debug step and switch to wl, then do so. Of course, you will never know when the ACPI bug will hit you again, and what the problem will be. OK. I may try blacklisting different ACPI modules and see if I can identify which one is causing the problem. If I find out I will report back because a number of other people seem to be suffering the same problem. Thanks for your help. Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
Chris Vine wrote: The problem is not with b43, but with ACPI. The debugging will need to be done by that set of devs. OK. I may try blacklisting different ACPI modules and see if I can identify which one is causing the problem. I'd suggest to go directly to the ACPI mailing list, do not pass go. :) They will want you to do more, and other, testing in order to track down the problem. //Peter ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On 10/20/2009 04:56 PM, Chris Vine wrote:
On Mon, 19 Oct 2009 16:53:24 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
This set of dmesg outputs was better; however, please set
CONFIG_B43_DEBUG=y in your configuration and rebuild the kernel.
Please post the full dmesg for warm and cold reboot.
Thanks for the output. Unfortunately, it all looks normal.
On auditing the DMA code for b43, I re-discovered a work-around that
was necessary for the first card that had 64-bit DMA, namely a 4311/2.
The fix for that is not needed for the 4315 card. Please apply the
attached patch (b43_change_dma_flags) to see if it fixes the problem.
If this patch does not fix the problem, I am working on a second to
try to do further debugging.
Larry
Index: wireless-testing/drivers/net/wireless/b43/dma.c
===
--- wireless-testing.orig/drivers/net/wireless/b43/dma.c
+++ wireless-testing/drivers/net/wireless/b43/dma.c
@@ -398,7 +398,7 @@ static int alloc_ringmemory(struct b43_d
*
* The flags here must match the flags in free_ringmemory below!
*/
- if (ring-type == B43_DMA_64BIT)
+ if (ring-type == B43_DMA_64BIT ring-dev-phy.type == B43_PHYTYPE_G)
flags |= GFP_DMA;
ring-descbase = ssb_dma_alloc_consistent(ring-dev-dev,
B43_DMA_RINGMEMSIZE,
@@ -416,7 +416,7 @@ static void free_ringmemory(struct b43_d
{
gfp_t flags = GFP_KERNEL;
- if (ring-type == B43_DMA_64BIT)
+ if (ring-type == B43_DMA_64BIT ring-dev-phy.type == B43_PHYTYPE_G)
flags |= GFP_DMA;
ssb_dma_free_consistent(ring-dev-dev, B43_DMA_RINGMEMSIZE,
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Wed, 21 Oct 2009 14:30:49 -0500 Larry Finger larry.fin...@lwfinger.net wrote: On 10/20/2009 04:56 PM, Chris Vine wrote: On Mon, 19 Oct 2009 16:53:24 -0500 Larry Finger larry.fin...@lwfinger.net wrote: This set of dmesg outputs was better; however, please set CONFIG_B43_DEBUG=y in your configuration and rebuild the kernel. Please post the full dmesg for warm and cold reboot. Thanks for the output. Unfortunately, it all looks normal. On auditing the DMA code for b43, I re-discovered a work-around that was necessary for the first card that had 64-bit DMA, namely a 4311/2. The fix for that is not needed for the 4315 card. Please apply the attached patch (b43_change_dma_flags) to see if it fixes the problem. If this patch does not fix the problem, I am working on a second to try to do further debugging. Hi, It doesn't fix it, I'm afraid. Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On 10/21/2009 04:16 PM, Chris Vine wrote:
On Wed, 21 Oct 2009 14:30:49 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
On 10/20/2009 04:56 PM, Chris Vine wrote:
On Mon, 19 Oct 2009 16:53:24 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
This set of dmesg outputs was better; however, please set
CONFIG_B43_DEBUG=y in your configuration and rebuild the kernel.
Please post the full dmesg for warm and cold reboot.
Thanks for the output. Unfortunately, it all looks normal.
On auditing the DMA code for b43, I re-discovered a work-around that
was necessary for the first card that had 64-bit DMA, namely a 4311/2.
The fix for that is not needed for the 4315 card. Please apply the
attached patch (b43_change_dma_flags) to see if it fixes the problem.
If this patch does not fix the problem, I am working on a second to
try to do further debugging.
Hi,
It doesn't fix it, I'm afraid.
Then try this patch without the previous one. It will generate some
warnings but they are harmless.
Larry
Index: wireless-testing/drivers/net/wireless/b43/dma.c
===
--- wireless-testing.orig/drivers/net/wireless/b43/dma.c
+++ wireless-testing/drivers/net/wireless/b43/dma.c
@@ -330,6 +330,7 @@ static inline
unsigned char *buf, size_t len, int tx)
{
dma_addr_t dmaaddr;
+ static int count;
if (tx) {
dmaaddr = ssb_dma_map_single(ring-dev-dev,
@@ -339,6 +340,8 @@ static inline
buf, len, DMA_FROM_DEVICE);
}
+ if (count++ 10)
+ b43dbg(ring-dev-wl, DMA Address in map_descbuffer: 0x%X\n,
dmaaddr);
return dmaaddr;
}
@@ -386,6 +389,7 @@ static inline
static int alloc_ringmemory(struct b43_dmaring *ring)
{
gfp_t flags = GFP_KERNEL;
+ static int count;
/* The specs call for 4K buffers for 30- and 32-bit DMA with 4K
* alignment and 8K buffers for 64-bit DMA with 8K alignment. Testing
@@ -407,6 +411,8 @@ static int alloc_ringmemory(struct b43_d
b43err(ring-dev-wl, DMA ringmemory allocation failed\n);
return -ENOMEM;
}
+ if (count++ 10)
+ b43dbg(ring-dev-wl, DMA ringmemory location: 0x%X\n,
ring-dmabase);
memset(ring-descbase, 0, B43_DMA_RINGMEMSIZE);
return 0;
@@ -593,6 +599,9 @@ static int setup_rx_descbuffer(struct b4
dmaaddr = map_descbuffer(ring, skb-data, ring-rx_buffersize, 0);
if (b43_dma_mapping_error(ring, dmaaddr, ring-rx_buffersize, 0)) {
/* ugh. try to realloc in zone_dma */
+ if (ring-type == B43_DMA_64BIT)
+ b43dbg(ring-dev-wl, b43: DMA mapping error on 64-bit
+ system with dmaaddr: 0x%X\n, dmaaddr);
gfp_flags |= GFP_DMA;
dev_kfree_skb_any(skb);
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Wed, 21 Oct 2009 18:05:31 -0500 Larry Finger larry.fin...@lwfinger.net wrote: Then try this patch without the previous one. It will generate some warnings but they are harmless. Working warm boot: cfg80211: Using static regulatory domain info cfg80211: Regulatory domain: US (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) cfg80211: Calling CRDA for country: US 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: PMLS, Firmware-ID: FW13 ] b43 ssb0:0: firmware: requesting b43/ucode15.fw 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: DMA ringmemory location: 0x309CD000 b43-phy0 debug: DMA ringmemory location: 0x30AC3000 b43-phy0 debug: DMA ringmemory location: 0x30A42000 b43-phy0 debug: DMA ringmemory location: 0x30AB7000 b43-phy0 debug: DMA ringmemory location: 0x30AB3000 b43-phy0 debug: DMA ringmemory location: 0x309DE000 b43-phy0 debug: DMA Address in map_descbuffer: 0x30ACD020 b43-phy0 debug: DMA Address in map_descbuffer: 0x30ACE020 b43-phy0 debug: DMA Address in map_descbuffer: 0x30ACF020 b43-phy0 debug: DMA Address in map_descbuffer: 0x36503020 b43-phy0 debug: DMA Address in map_descbuffer: 0x30A80020 b43-phy0 debug: DMA Address in map_descbuffer: 0x30A81020 b43-phy0 debug: DMA Address in map_descbuffer: 0x30A82020 b43-phy0 debug: DMA Address in map_descbuffer: 0x30A83020 b43-phy0 debug: DMA Address in map_descbuffer: 0x30A84020 b43-phy0 debug: DMA Address in map_descbuffer: 0x30A85020 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 b43-phy0 debug: Removing Interface type 2 b43-phy0 debug: Wireless interface stopped b43-phy0 debug: DMA-64 rx_ring: Used slots 1/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 2/256, Failed frames 0/44 = 0.0%, Average tries 1.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: DMA ringmemory location: 0x2E81A000 b43-phy0 debug: DMA ringmemory location: 0x30A3A000 b43-phy0 debug: DMA ringmemory location: 0x309F8000 b43-phy0 debug: DMA ringmemory location: 0x309BC000 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 wlan0: direct probe to AP 00:08:5c:ca:dc:c3 (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:08:5c:ca:dc:c3 (try 1) wlan0: authenticated wlan0: associate with AP 00:08:5c:ca:dc:c3 (try 1) wlan0: RX AssocResp from 00:08:5c:ca:dc:c3 (capab=0x411 status=0 aid=1) wlan0: associated Cold boot: cfg80211: Using static regulatory domain info cfg80211: Regulatory domain: US (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) cfg80211: Calling CRDA for country: US b43-phy0: Broadcom 4312 WLAN found (core revision 15) b43-phy0 debug: Found
Re: b43/BCM4312 fails with DMA errors
On Mon, 19 Oct 2009 16:53:24 -0500 Larry Finger larry.fin...@lwfinger.net wrote: This set of dmesg outputs was better; however, please set CONFIG_B43_DEBUG=y in your configuration and rebuild the kernel. Please post the full dmesg for warm and cold reboot. For a warm boot it is: cfg80211: Using static regulatory domain info cfg80211: Regulatory domain: US (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) cfg80211: Calling CRDA for country: US 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: PMLS, Firmware-ID: FW13 ] b43 ssb0:0: firmware: requesting b43/ucode15.fw 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 b43-phy0 debug: Removing Interface type 2 b43-phy0 debug: Wireless interface stopped b43-phy0 debug: DMA-64 rx_ring: Used slots 1/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 2/256, Failed frames 0/33 = 0.0%, Average tries 1.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 debug: Adding Interface type 2 wlan0: direct probe to AP 00:08:5c:ca:dc:c3 (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:08:5c:ca:dc:c3 (try 1) wlan0: authenticated wlan0: associate with AP 00:08:5c:ca:dc:c3 (try 1) wlan0: RX AssocResp from 00:08:5c:ca:dc:c3 (capab=0x411 status=0 aid=1) wlan0: associated For a cold boot it is: cfg80211: Using static regulatory domain info cfg80211: Regulatory domain: US (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) cfg80211: Calling CRDA for country: US 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: PMLS, Firmware-ID: FW13 ] b43 ssb0:0: firmware: requesting b43/ucode15.fw 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 b43-phy0 ERROR: Fatal DMA error: 0x0800, 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 1/64, Failed frames 0/0 = 0.0%, Average tries 0.00 b43-phy0 debug: DMA-64
Re: b43/BCM4312 fails with DMA errors
On Monday 19 October 2009 11:37:56 Chris Vine wrote: On Sun, 18 Oct 2009 22:14:31 -0500 Larry Finger larry.fin...@lwfinger.net wrote: I see no difference in the output for the BCM4312 device; however, there was a difference in the memory layout for the BCM5906 wired network device. Please post the dmesg output for the warm and cold reboot. Attached. The dmesg ring buffer truncates at slightly different places because of the reports of DMA errors at the end of the cold boot and there seems to be some re-ordering of the loading of different things, but they appear basically the same. I guess you guys already played with acpi=off and apic=off ? -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Monday 19 October 2009 11:46:00 Michael Buesch wrote: On Monday 19 October 2009 11:37:56 Chris Vine wrote: On Sun, 18 Oct 2009 22:14:31 -0500 Larry Finger larry.fin...@lwfinger.net wrote: I see no difference in the output for the BCM4312 device; however, there was a difference in the memory layout for the BCM5906 wired network device. Please post the dmesg output for the warm and cold reboot. Attached. The dmesg ring buffer truncates at slightly different places because of the reports of DMA errors at the end of the cold boot and there seems to be some re-ordering of the loading of different things, but they appear basically the same. I guess you guys already played with acpi=off and apic=off ? If you look at the diff of those logs, you also see that this is not just reordering of stuff. At the very beginning you see some fairly huge ACPI mapping that's not done for the failure case. So my guess is that the ACPI simply fails to map some important I/O memory. There also are other interesting things in the log, which are probably not the cause of the b43 issue, but related to the root issue. For example the failed TSC calibration smells fishy to me. --- dmesg-2.6.32-rc5.cold.txt 2009-10-19 11:47:53.0 +0200 +++ dmesg-2.6.32-rc5.warm.txt 2009-10-19 11:47:50.0 +0200 @@ -1,4 +1,35 @@ - 0001) +anges enabled: + 0-9 write-back + A-B uncachable + C-C write-protect + D-D uncachable + E-F write-protect +MTRR variable ranges enabled: + 0 base 0 mask 0C000 write-back + 1 base 03F70 mask 0FFF0 uncachable + 2 base 03F80 mask 0FF80 uncachable + 3 disabled + 4 disabled + 5 disabled + 6 disabled + 7 disabled +x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 +initial memory mapped : 0 - 0180 +init_memory_mapping: -377fe000 + 00 - 40 page 4k + 40 - 003740 page 2M + 003740 - 00377fe000 page 4k +kernel direct mapping tables up to 377fe000 @ 7000-c000 +ACPI: RSDP 000f7c70 00024 (v02 LENOVO) +ACPI: XSDT 3f6d9fed 0007C (v01 LENOVO CB-010604 LTP ) +ACPI: FACP 3f6e1c3a 000F4 (v03 INTEL CALISTGA 0604 ALAN 0001) +ACPI: DSDT 3f6dbbf9 05FCD (v01 LENOVO CB-010604 MSFT 0300) +ACPI: FACS 3f6e2fc0 00040 +ACPI: HPET 3f6e1d2e 00038 (v01 INTEL CALISTGA 0604 LOHR 005A) +ACPI: MCFG 3f6e1d66 0003C (v01 INTEL CALISTGA 0604 LOHR 005A) +ACPI: TCPA 3f6e1da2 00032 (v01 PTLTD CALISTGA 0604 PTL 0001) +ACPI: TMOR 3f6e1dd4 00026 (v01 PTLTD 0604 PTL 0003) +ACPI: SLIC 3f6e1dfa 00176 (v01 LENOVO CB-010604 LNVO 0001) ACPI: APIC 3f6e1f70 00068 (v01 PTLTD ? APIC 0604 LTP ) ACPI: BOOT 3f6e1fd8 00028 (v01 PTLTD $SBFTBL$ 0604 LTP 0001) ACPI: SSDT 3f6db5aa 0064F (v01 SataRe SataPri 1000 INTL 20050624) @@ -93,10 +124,9 @@ Console: colour dummy device 80x25 console [tty0] enabled hpet clockevent registered -Fast TSC calibration failed -TSC: PIT calibration matches HPET. 1 loops -Detected 1596.048 MHz processor. -Calibrating delay loop (skipped), value calculated using timer frequency.. 3192.09 BogoMIPS (lpj=6384192) +Fast TSC calibration using PIT +Detected 1595.947 MHz processor. +Calibrating delay loop (skipped), value calculated using timer frequency.. 3191.89 BogoMIPS (lpj=6383788) Security Framework initialized Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 24K @@ -120,7 +150,7 @@ CPU0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz stepping 02 Booting processor 1 APIC 0x1 ip 0x6000 Initializing CPU#1 -Calibrating delay using timer specific routine.. 3191.70 BogoMIPS (lpj=6383401) +Calibrating delay using timer specific routine.. 3191.93 BogoMIPS (lpj=6383871) CPU: L1 I cache: 32K, L1 D cache: 24K CPU: L2 cache: 512K CPU: Physical Processor ID: 0 @@ -130,7 +160,7 @@ CPU1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz stepping 02 checking TSC synchronization [CPU#0 - CPU#1]: passed. Brought up 2 CPUs -Total of 2 processors activated (6383.79 BogoMIPS). +Total of 2 processors activated (6383.82 BogoMIPS). regulator: core version 0.5 NET: Registered protocol family 16 ACPI: bus type pci registered @@ -141,6 +171,7 @@ bio: create slab bio-0 at 0 ACPI: EC: Look up EC in DSDT ACPI: BIOS _OSI(Linux) query ignored +ACPI: EC: GPE storm detected, transactions will use polling mode ACPI: Interpreter enabled ACPI: (supports S0 S3 S4 S5) ACPI: Using IOAPIC for interrupt routing @@ -366,6 +397,14 @@ usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: EHCI Host Controller +ata1.00: ATA-8: Hitachi HTS543216L9A300, FB2OC4DC, max UDMA/133 +ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32) +ata1.00: configured for UDMA/133 +scsi 0:0:0:0: Direct-Access ATA Hitachi HTS54321 FB2O PQ: 0
Re: b43/BCM4312 fails with DMA errors
On Monday 19 October 2009 11:55:01 Michael Buesch wrote: On Monday 19 October 2009 11:46:00 Michael Buesch wrote: On Monday 19 October 2009 11:37:56 Chris Vine wrote: On Sun, 18 Oct 2009 22:14:31 -0500 Larry Finger larry.fin...@lwfinger.net wrote: I see no difference in the output for the BCM4312 device; however, there was a difference in the memory layout for the BCM5906 wired network device. Please post the dmesg output for the warm and cold reboot. Attached. The dmesg ring buffer truncates at slightly different places because of the reports of DMA errors at the end of the cold boot and there seems to be some re-ordering of the loading of different things, but they appear basically the same. I guess you guys already played with acpi=off and apic=off ? If you look at the diff of those logs, you also see that this is not just reordering of stuff. At the very beginning you see some fairly huge ACPI mapping that's not done for the failure case. So my guess is that the ACPI simply fails to map some important I/O memory. There also are other interesting things in the log, which are probably not the cause of the b43 issue, but related to the root issue. For example the failed TSC calibration smells fishy to me. Though, I currently realize that those kernel logs are truncated, so they aren't really of any use... -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Mon, 19 Oct 2009 11:55:01 +0200 Michael Buesch m...@bu3sch.de wrote: On Monday 19 October 2009 11:46:00 Michael Buesch wrote: On Monday 19 October 2009 11:37:56 Chris Vine wrote: On Sun, 18 Oct 2009 22:14:31 -0500 Larry Finger larry.fin...@lwfinger.net wrote: I see no difference in the output for the BCM4312 device; however, there was a difference in the memory layout for the BCM5906 wired network device. Please post the dmesg output for the warm and cold reboot. Attached. The dmesg ring buffer truncates at slightly different places because of the reports of DMA errors at the end of the cold boot and there seems to be some re-ordering of the loading of different things, but they appear basically the same. I guess you guys already played with acpi=off and apic=off ? If you look at the diff of those logs, you also see that this is not just reordering of stuff. At the very beginning you see some fairly huge ACPI mapping that's not done for the failure case. So my guess is that the ACPI simply fails to map some important I/O memory. There also are other interesting things in the log, which are probably not the cause of the b43 issue, but related to the root issue. For example the failed TSC calibration smells fishy to me. On the first point (ACPI mapping), that's just dmesg ring buffer truncation, and irrelevant. Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Monday 19 October 2009 12:03:40 Chris Vine wrote: If you look at the diff of those logs, you also see that this is not just reordering of stuff. At the very beginning you see some fairly huge ACPI mapping that's not done for the failure case. So my guess is that the ACPI simply fails to map some important I/O memory. There also are other interesting things in the log, which are probably not the cause of the b43 issue, but related to the root issue. For example the failed TSC calibration smells fishy to me. On the first point (ACPI mapping), that's just dmesg ring buffer truncation, and irrelevant. Post the full log, please, so we can _verify_ that it's irrelevant. Everything else is just bad guesswork. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Mon, 19 Oct 2009 11:55:01 +0200 Michael Buesch m...@bu3sch.de wrote: On Monday 19 October 2009 11:46:00 Michael Buesch wrote: On Monday 19 October 2009 11:37:56 Chris Vine wrote: On Sun, 18 Oct 2009 22:14:31 -0500 Larry Finger larry.fin...@lwfinger.net wrote: I see no difference in the output for the BCM4312 device; however, there was a difference in the memory layout for the BCM5906 wired network device. Please post the dmesg output for the warm and cold reboot. Attached. The dmesg ring buffer truncates at slightly different places because of the reports of DMA errors at the end of the cold boot and there seems to be some re-ordering of the loading of different things, but they appear basically the same. I guess you guys already played with acpi=off and apic=off ? If you look at the diff of those logs, you also see that this is not just reordering of stuff. At the very beginning you see some fairly huge ACPI mapping that's not done for the failure case. So my guess is that the ACPI simply fails to map some important I/O memory. There also are other interesting things in the log, which are probably not the cause of the b43 issue, but related to the root issue. For example the failed TSC calibration smells fishy to me. On TSC calibration, as I read it, it is only the fast calibration which fails, not slow (regular) calibration. Both have Marking TSC unstable due to TSC halts in idle logged later, and I have no idea whether that is significant, although I suspect not. (Amongst other things, it would not explain why b43 works on a warm boot.) Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Mon, 19 Oct 2009 12:12:59 +0200 Michael Buesch m...@bu3sch.de wrote: Post the full log, please, so we can _verify_ that it's irrelevant. Everything else is just bad guesswork. Full marks for attitude. What do you take, for this purpose, as being the full log? All of /var/log/messages, /var/log/syslog and /var/log/debug? (If you are proposing that I should rebuild dmesg with a larger ring buffer, then no.) Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Monday 19 October 2009 12:58:50 Chris Vine wrote: (If you are proposing that I should rebuild dmesg with a larger ring buffer, then no.) Why not? You want some help, right? So we need your help. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Monday 19 October 2009, Chris Vine wrote: On Mon, 19 Oct 2009 12:12:59 +0200 Michael Buesch m...@bu3sch.de wrote: Post the full log, please, so we can _verify_ that it's irrelevant. Everything else is just bad guesswork. Full marks for attitude. What do you take, for this purpose, as being the full log? All of /var/log/messages, /var/log/syslog and /var/log/debug? (If you are proposing that I should rebuild dmesg with a larger ring buffer, then no.) Chris Chris, if its needed, then yes. Its a single entry in a 'make xconfig' and rebuild reboot. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) The NRA is offering FREE Associate memberships to anyone who wants them. https://www.nrahq.org/nrabonus/accept-membership.asp The cost of feathers has risen, even down is up! ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On 10/19/2009 07:12 AM, Gene Heskett wrote: On Monday 19 October 2009, Chris Vine wrote: (If you are proposing that I should rebuild dmesg with a larger ring buffer, then no.) Chris Chris, if its needed, then yes. Its a single entry in a 'make xconfig' and rebuild reboot. Chris, from the lengths of the logs you posted, it looks as if your kernel is built with CONFIG_LOG_BUF_SHIFT=9. That is way too small for any meaningful debugging. Your computer has 1 GB RAM - it won't hurt to devote a bit more to the ring buffer. On my system with 3 GB RAM, I use 19. I got tired of wrap-arounds when I was trying to see the first oops message. In the short-tern, you can boot your existing kernel with a bigger log buffer by adding 'log_buf_len=131072' to the boot parameter line in GRUB. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On 10/19/2009 01:00 PM, Chris Vine wrote: On Mon, 19 Oct 2009 09:30:28 -0500 Larry Finger larry.fin...@lwfinger.net wrote: Chris, from the lengths of the logs you posted, it looks as if your kernel is built with CONFIG_LOG_BUF_SHIFT=9. That is way too small for any meaningful debugging. Your computer has 1 GB RAM - it won't hurt to devote a bit more to the ring buffer. On my system with 3 GB RAM, I use 19. I got tired of wrap-arounds when I was trying to see the first oops message. In the short-tern, you can boot your existing kernel with a bigger log buffer by adding 'log_buf_len=131072' to the boot parameter line in GRUB. OK. Attached is the dmesg output with that boot parameter. To avoid any false trails, I ought to say that a warm boot of itself achieves nothing. What is required to make b43 succeed is a warm boot from a kernel which has initialised the wireless device by means of the wl kernel module. This set of dmesg outputs was better; however, please set CONFIG_B43_DEBUG=y in your configuration and rebuild the kernel. Please post the full dmesg for warm and cold reboot. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Mon, 19 Oct 2009 16:53:24 -0500 Larry Finger larry.fin...@lwfinger.net wrote: This set of dmesg outputs was better; however, please set CONFIG_B43_DEBUG=y in your configuration and rebuild the kernel. Please post the full dmesg for warm and cold reboot. My original posting (16 October) gave the output for a b43 failure with debugging on. Was this an oversight, or do you really need to compare it with the case of a successful load? If so I can provide you with the output for a successful load, but it won't be until late tomorrow. Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On 10/19/2009 05:48 PM, Chris Vine wrote: On Mon, 19 Oct 2009 16:53:24 -0500 Larry Finger larry.fin...@lwfinger.net wrote: This set of dmesg outputs was better; however, please set CONFIG_B43_DEBUG=y in your configuration and rebuild the kernel. Please post the full dmesg for warm and cold reboot. My original posting (16 October) gave the output for a b43 failure with debugging on. Was this an oversight, or do you really need to compare it with the case of a successful load? If so I can provide you with the output for a successful load, but it won't be until late tomorrow. I want the comparison. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
I have tried the latest wireless-testing and 2.6.32-rc5 and they both still give DMA errors exactly like those I reported earlier. Perhaps it's because the machine only has 1GB of RAM, and is an Atom compiled with -march=core2 -mtune=generic -mfpmath=sse CFLAGS? (At least, that's what I pass to make. I don't know how the kernel build system filters these flags..). Lance PS: And I apologize if this message breaks the thread again. I can't for the life of me figure out how to get gmail to use the extra parameters... ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Sunday 18 October 2009 13:25:14 Lance Hepler wrote: I have tried the latest wireless-testing and 2.6.32-rc5 and they both still give DMA errors exactly like those I reported earlier. Perhaps it's because the machine only has 1GB of RAM, and is an Atom compiled with -march=core2 -mtune=generic -mfpmath=sse CFLAGS? (At least, that's what I pass to make. I don't know how the kernel build system filters these flags..). A simple rule for modifying CFLAGS in the kernel is: Don't! The kernel developers _already_ tuned the CFLAGS to the best possible gain, so by further modifying the flags you just introduce bugs and miscompilations. And besides that, the kernel doesn't use floating point, so the -mfpmath=sse will do no good and has potential for miscompilations. It's unlikely that this causes your issues, but it's a general rule. It's also a good idea to obey the Don't! rule for userspace programs. It's just placebo. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Sat, 17 Oct 2009 20:36:03 +0100 Chris Vine ch...@cvine.freeserve.co.uk wrote: ... get through (and my wife says it isn't true), I add additional simple filters of my own: in particular I delete anything which is not addressed to a known user on the system. As mailing list often don't do that, I put in a further saving rule for my mailing lists. You are usually safe with a From header from the mailing list - that doesn't work with berlios. Why not use the List-Id header? Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Fri, 16 Oct 2009 21:35:54 +0200 Gábor Stefanik netrolller...@gmail.com wrote: Could you please try the real wireless-testing tree (as opposed to compat-wireless)? Also, what I noticed is that everyone with this problem appears to have an Intel Atom CPU... weird. Maybe something weird is going on with the Atom chipset's DMA handling. I get the DMA errors with both the master and linville branches of wireless-testing. Since b43 works correctly after a warm boot from a loaded wl module, I suspect it is more likely to be something amiss with the loading of the firmware or with device initialisation. Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On 10/18/2009 11:35 AM, Chris Vine wrote: On Fri, 16 Oct 2009 21:35:54 +0200 Gábor Stefanik netrolller...@gmail.com wrote: Could you please try the real wireless-testing tree (as opposed to compat-wireless)? Also, what I noticed is that everyone with this problem appears to have an Intel Atom CPU... weird. Maybe something weird is going on with the Atom chipset's DMA handling. I get the DMA errors with both the master and linville branches of wireless-testing. Since b43 works correctly after a warm boot from a loaded wl module, I suspect it is more likely to be something amiss with the loading of the firmware or with device initialisation. Remember that most of us do not get this error. I think that something is amiss with your motherboard, the PCIe bridge, or the interface between the chip and the PCIe buss. Without the error on my machine, it is very difficult to debug. Please post the output of the command 'sudo lspci -nnvvv' for the BCM43XX device in the case of a cold boot (when it fails) and the case of a warm boot from a loaded wl. In addition, please post the particulars of your computer. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On 10/18/2009 04:47 PM, Chris Vine wrote: On Sun, 18 Oct 2009 15:41:17 -0500 Larry Finger larry.fin...@lwfinger.net wrote: Please post the output of the command 'sudo lspci -nnvvv' for the BCM43XX device in the case of a cold boot (when it fails) and the case of a warm boot from a loaded wl. In addition, please post the particulars of your computer. Sure. Attached is the output of lspci -nnvvv with the wl driver loaded under kernel 2.6.27 (2.6.27.txt), for a working loaded b43 driver on a subsequent warm boot to kernel 2.6.32-rc5 (2.6.32-rc5.warm.txt) (wireless-testing, linville branch) and a failed loaded b43 driver on a further cold boot to kernel 2.6.32-rc5 (2.6.32-rc5.cold.txt) (wireless-testing, linville branch). Also attached is a list of loaded modules in the last two cases (2.6.32-rc5.modules). The computer is a Levono S-12 netbook. What further particulars would you like that is not revealed by lspci? I see no difference in the output for the BCM4312 device; however, there was a difference in the memory layout for the BCM5906 wired network device. Please post the dmesg output for the warm and cold reboot. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Fri, 16 Oct 2009 21:35:54 +0200 Gábor Stefanik netrolller...@gmail.com wrote: Could you please try the real wireless-testing tree (as opposed to compat-wireless)? Also, what I noticed is that everyone with this problem appears to have an Intel Atom CPU... weird. Maybe something weird is going on with the Atom chipset's DMA handling. OK, I'll compile wireless-testing it over the weekend. I am struggling to stop my spam filter removing bcm43xx-devel posts. Is there anything in the lists.berlioz.de headers that I can key on? Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Saturday 17 October 2009, Chris Vine wrote: On Fri, 16 Oct 2009 21:35:54 +0200 Gábor Stefanik netrolller...@gmail.com wrote: Could you please try the real wireless-testing tree (as opposed to compat-wireless)? Also, what I noticed is that everyone with this problem appears to have an Intel Atom CPU... weird. Maybe something weird is going on with the Atom chipset's DMA handling. OK, I'll compile wireless-testing it over the weekend. I am struggling to stop my spam filter removing bcm43xx-devel posts. Is there anything in the lists.berlioz.de headers that I can key on? Chris NDI what 'filter' you are using, but I just checked back over a 30 day corpus of this list, and no message in that 30 days even rated above a 0 for spaminess, all were in the -2.3 to -2.5 range according to spamassassin. Is your bayes database poisoned perhaps, or inadequately trained on ham? ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) The NRA is offering FREE Associate memberships to anyone who wants them. https://www.nrahq.org/nrabonus/accept-membership.asp A successful [software] tool is one that was used to do something undreamed of by its author. -- S. C. Johnson ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Fri, 16 Oct 2009 21:35:54 +0200 Gábor Stefanik netrolller...@gmail.com wrote: On Fri, Oct 16, 2009 at 6:01 PM, Chris Vine ch...@cvine.freeserve.co.uk wrote: On Fri, 16 Oct 2009 9:45:40 -0400 fre...@carolina.rr.com wrote: 2.6.32-rc? and wireless-compat was thought to work as well as wireless-testing ... hmmm Ah right. I had been trying 2.6.32-rc4 by itself and compat-wireless with 2.6.31. If I build compat-wireless on top of 2.6.32-rc.4 the dma errors appear to go away but the encryption modules won't load so it is not usable. I think I will try again in a few months time when things have settled down a bit. (Or possibly pull wireless-testing from git once 2.6.32 comes out.) Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev Could you please try the real wireless-testing tree (as opposed to compat-wireless)? Also, what I noticed is that everyone with this problem appears to have an Intel Atom CPU... weird. Maybe something weird is going on with the Atom chipset's DMA handling. No, it's not only Atom. I see it on Intel T4200 (dual core Pentium, 45nm, 800MHz FSB, GL40/GM45 chipset). Lenovo G530 laptop. regards, Charlie ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On 10/17/2009 01:12 PM, Charles Moschel wrote: Also, what I noticed is that everyone with this problem appears to have an Intel Atom CPU... weird. Maybe something weird is going on with the Atom chipset's DMA handling. No, it's not only Atom. I see it on Intel T4200 (dual core Pentium, 45nm, 800MHz FSB, GL40/GM45 chipset). Lenovo G530 laptop. Is this with the same wireless card moved from computer to computer? ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Sat, 17 Oct 2009 08:24:59 -0400 Gene Heskett gene.hesk...@verizon.net wrote: NDI what 'filter' you are using, but I just checked back over a 30 day corpus of this list, and no message in that 30 days even rated above a 0 for spaminess, all were in the -2.3 to -2.5 range according to spamassassin. Is your bayes database poisoned perhaps, or inadequately trained on ham? I just use my ISP's spam filter, which probably uses spamassassin, as a first sift, but delete it here rather than at the ISP as I put various savings in for things it sometimes interprets as spam. Because I get fed up with complaints about my penis size which still get through (and my wife says it isn't true), I add additional simple filters of my own: in particular I delete anything which is not addressed to a known user on the system. As mailing list often don't do that, I put in a further saving rule for my mailing lists. You are usually safe with a From header from the mailing list - that doesn't work with berlios. Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Sat, 17 Oct 2009 14:10:19 -0500 Larry Finger larry.fin...@lwfinger.net wrote: On 10/17/2009 01:12 PM, Charles Moschel wrote: Also, what I noticed is that everyone with this problem appears to have an Intel Atom CPU... weird. Maybe something weird is going on with the Atom chipset's DMA handling. No, it's not only Atom. I see it on Intel T4200 (dual core Pentium, 45nm, 800MHz FSB, GL40/GM45 chipset). Lenovo G530 laptop. Is this with the same wireless card moved from computer to computer? No, it came with the laptop and has never been removed. I reported earlier that it fails with 2.6.31 (Fedora rawhide kernel) + compat-wireless, but works with 2.6.32-rc[12] wireless-testing pulled from git: [https://lists.berlios.de/pipermail/bcm43xx-dev/2009-October/006132.html] ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Sun, Oct 18, 2009 at 1:44 AM, Charles Moschel fre...@carolina.rr.com wrote: On Sat, 17 Oct 2009 14:10:19 -0500 Larry Finger larry.fin...@lwfinger.net wrote: On 10/17/2009 01:12 PM, Charles Moschel wrote: Also, what I noticed is that everyone with this problem appears to have an Intel Atom CPU... weird. Maybe something weird is going on with the Atom chipset's DMA handling. No, it's not only Atom. I see it on Intel T4200 (dual core Pentium, 45nm, 800MHz FSB, GL40/GM45 chipset). Lenovo G530 laptop. Is this with the same wireless card moved from computer to computer? No, it came with the laptop and has never been removed. I reported earlier that it fails with 2.6.31 (Fedora rawhide kernel) + compat-wireless, but works with 2.6.32-rc[12] wireless-testing pulled from git: [https://lists.berlios.de/pipermail/bcm43xx-dev/2009-October/006132.html] What happens with 2.6.31-rc[12] + compat-wireless? And with just 2.6.32-rc[12] (without compat-wireless)? (My guess is that it will fail, but I need to know this before we move on.) -- 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
b43/BCM4312 fails with DMA errors
Hi, I have a Levono S-12 Netbook, which has the Atom N270 processor and a Broadcom 14e4:4315 wireless chip with low power PHY. lspci -vnn | grep 14e4 gives: 02:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express [14e4:1713] (rev 02) 03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01) Subsystem: Broadcom Corporation Unknown device [14e4:04b5] As suggested for this chip on the linux wireless b43 howto web page, I am using firmware extracted from broadcom-wl-4.178.10.4.tar.bz2 using the current b43-fwcutter in git. Although wireless works with the broadcom wl driver provided by Broadcom in their hybrid-portsrc-x86_32-v5.10.91.9.3.tar.gz package up to and including kernel 2.6.28 (but not afterwards, presumably because of the replacement of ieee80211 by lib80211), the b43 driver in both 2.6.32-rc4 and current compat-wireless fails on a cold boot with dma errors (I use cold boot advisedly - see the working case 1 for b43 mentioned at the end). Prior to failure, modprobe b43 dmesg | egrep ssb|b43 gives: b43-pci-bridge :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 b43-pci-bridge :03:00.0: setting latency timer to 64 ssb: Sonics Silicon Backplane found on PCI device :03: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 Registered led device: b43-phy0::tx Registered led device: b43-phy0::rx Registered led device: b43-phy0::radio So far it looks normal. However, bringing up the wlan0 interface and attempting to associate will shortly afterwards trigger DMA errors, and any further use of the interface thereafter will fail. Sometimes failure happens immediately the interface is brought up, usually I can get as far as successfully scanning for APs with 'iwlist scan wlan0', and sometimes it gets as far as negotiating association with the AP, but it always ends at some point with logging output such as this in /var/log/messages (with b43 debugging switched on): 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: PMLS, Firmware-ID: FW13 ] b43 ssb0:0: firmware: requesting b43/ucode15.fw 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 b43-phy0 ERROR: Fatal DMA error: 0x0800, 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 1/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 2/256, Failed frames 0/11 = 0.0%, Average tries 1.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 [ ... and so on ... ] The DMA error message repeats at approximately 5 second intervals (so filling up /var/log/messages quite nicely after a while). Two other points which may help locate the problem, when b43 WILL work: 1. If I boot up ubuntu kernel-2.6.27 with the proprietary wl driver, and then do a warm reboot to kernel 2.6.32-rc4, b43 works normally. No DMA errors are reported. This may point to a firmware loading issue, but see 2 below. 2. If I choose the force PIO debugging option b43 works OK (albeit no doubt not very efficiently). Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
Hi Chris -- Chris Vine ch...@cvine.freeserve.co.uk wrote: Hi, I have a Levono S-12 Netbook, which has the Atom N270 processor and a Broadcom 14e4:4315 wireless chip with low power PHY. lspci -vnn | grep 14e4 gives: 02:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express [14e4:1713] (rev 02) 03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01) Subsystem: Broadcom Corporation Unknown device [14e4:04b5] As suggested for this chip on the linux wireless b43 howto web page, I am using firmware extracted from broadcom-wl-4.178.10.4.tar.bz2 using the current b43-fwcutter in git. Although wireless works with the broadcom wl driver provided by Broadcom in their hybrid-portsrc-x86_32-v5.10.91.9.3.tar.gz package up to and including kernel 2.6.28 (but not afterwards, presumably because of the replacement of ieee80211 by lib80211), the b43 driver in both 2.6.32-rc4 and current compat-wireless fails on a cold boot with dma errors (I use cold boot advisedly - see the working case 1 for b43 mentioned at the end). Prior to failure, modprobe b43 dmesg | egrep ssb|b43 gives: b43-pci-bridge :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 b43-pci-bridge :03:00.0: setting latency timer to 64 ssb: Sonics Silicon Backplane found on PCI device :03: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 Registered led device: b43-phy0::tx Registered led device: b43-phy0::rx Registered led device: b43-phy0::radio So far it looks normal. However, bringing up the wlan0 interface and attempting to associate will shortly afterwards trigger DMA errors, and any further use of the interface thereafter will fail. Sometimes failure happens immediately the interface is brought up, usually I can get as far as successfully scanning for APs with 'iwlist scan wlan0', and sometimes it gets as far as negotiating association with the AP, but it always ends at some point with logging output such as this in /var/log/messages (with b43 debugging switched on): 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: PMLS, Firmware-ID: FW13 ] b43 ssb0:0: firmware: requesting b43/ucode15.fw 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 b43-phy0 ERROR: Fatal DMA error: 0x0800, 0x, 0x, 0x, 0x, 0x I had 0x0400, rather than 0x0800 b43-phy0: Controller RESET (DMA error) ... b43-phy0 debug: Wireless interface stopped b43-phy0 debug: DMA-64 rx_ring: Used slots 1/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 2/256, Failed frames 0/11 = 0.0%, Average tries 1.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 [ ... and so on ... ] The DMA error message repeats at approximately 5 second intervals (so filling up /var/log/messages quite nicely after a while). Two other points which may help locate the problem, when b43 WILL work: 1. If I boot up ubuntu kernel-2.6.27 with the proprietary wl driver, and then do a warm reboot to kernel 2.6.32-rc4, b43 works normally. No DMA errors are reported. This may point to a firmware loading issue, but see 2 below. I had similar problems, and was advised to try the full wireless-testing kernel, which worked OK for me (compat-wireless with Fedora 2.6.31 kernel did *not* work).
Re: b43/BCM4312 fails with DMA errors
On Fri, 16 Oct 2009 9:45:40 -0400 fre...@carolina.rr.com wrote: 2.6.32-rc? and wireless-compat was thought to work as well as wireless-testing ... hmmm Ah right. I had been trying 2.6.32-rc4 by itself and compat-wireless with 2.6.31. If I build compat-wireless on top of 2.6.32-rc.4 the dma errors appear to go away but the encryption modules won't load so it is not usable. I think I will try again in a few months time when things have settled down a bit. (Or possibly pull wireless-testing from git once 2.6.32 comes out.) Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43/BCM4312 fails with DMA errors
On Fri, Oct 16, 2009 at 6:01 PM, Chris Vine ch...@cvine.freeserve.co.uk wrote: On Fri, 16 Oct 2009 9:45:40 -0400 fre...@carolina.rr.com wrote: 2.6.32-rc? and wireless-compat was thought to work as well as wireless-testing ... hmmm Ah right. I had been trying 2.6.32-rc4 by itself and compat-wireless with 2.6.31. If I build compat-wireless on top of 2.6.32-rc.4 the dma errors appear to go away but the encryption modules won't load so it is not usable. I think I will try again in a few months time when things have settled down a bit. (Or possibly pull wireless-testing from git once 2.6.32 comes out.) Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev Could you please try the real wireless-testing tree (as opposed to compat-wireless)? Also, what I noticed is that everyone with this problem appears to have an Intel Atom CPU... weird. Maybe something weird is going on with the Atom chipset's DMA handling. -- 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
