Re: b43 dma error
On Tue, Sep 8, 2009 at 10:54 PM, Larry Fingerlarry.fin...@lwfinger.net wrote: Michael Buesch wrote: On Tuesday 08 September 2009 15:47:32 Dave Young wrote: I tested wireless-testing b43 driver, but got Fatal DMA error then the controller keep restarting... Please tell what I can provide or test, Thanks. Is this a regression? If so, please bisect. It is something specific to his system as I don't see anything like this. In addition, there are some users on the openSUSE forums that have implemented the latest compat-wireless and switched away from Broadcom wl to b43 on their LP PHY devices. So far, no complaints from them. Please reboot so that we see the ssb output as well. Use the command dmesg | egrep ssb|b43 That way we will be able to see exactly what kind of device you have and what revisions are in it. AFAIK, the testing to date has been limited to Rev 1 PHYs and Rev 2 radios. I use a public pc and I have no lan access for my laptop, so just hand copy something: b43-pci-bridge :0c:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 b43-pci-bridge :0c:00.0: setting latency timer to 64 ssb SInics Silicon Backplane found on PCI device :0c: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 Larry -- Regards dave ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 dma error
2009/9/8 Gábor Stefanik netrolller...@gmail.com: Do you have the threaded-IRQ patches applied? Could you point the url? where can I get them? Also, what card is this? (BCM4312?) Try upgrading your firmare (use v478 or the new v5xx one). Yes, BCM4312, I use the firmware according to the guide in linux-wireless web page, where is the v5xx, could you tell more? -- Regards dave ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 dma error
On Tue, Sep 8, 2009 at 10:38 PM, Michael Bueschm...@bu3sch.de wrote: On Tuesday 08 September 2009 15:47:32 Dave Young wrote: I tested wireless-testing b43 driver, but got Fatal DMA error then the controller keep restarting... Please tell what I can provide or test, Thanks. Is this a regression? If so, please bisect. Not sure, It's the first time for me to use b43 with the lp-phy because I happend to know it is supported now. If it's a regression I can do bisection. -- Greetings, Michael. -- Regards dave ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 dma error
2009/9/9 Larry Finger larry.fin...@lwfinger.net: Gábor Stefanik wrote: On Tue, Sep 8, 2009 at 8:16 PM, Larry Fingerlarry.fin...@lwfinger.net wrote: Your PHY and your radio are the same as mine. In fact, the one thing I noticed is that you are using i386 architecture, whereas mine is x86_64. I have not tested with i386. Has anyone run the LP PHY modifications with 32-bit architecture? Yes, me. (With the exact same card as John.) Is it a maximum memory issue? How much for you? 1G memory for me. John and Dave: Same question. Larry -- Regards dave ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 dma error
On Wed, Sep 9, 2009 at 3:56 PM, Dave Younghidave.darks...@gmail.com wrote: On Tue, Sep 8, 2009 at 10:38 PM, Michael Bueschm...@bu3sch.de wrote: On Tuesday 08 September 2009 15:47:32 Dave Young wrote: I tested wireless-testing b43 driver, but got Fatal DMA error then the controller keep restarting... Please tell what I can provide or test, Thanks. Is this a regression? If so, please bisect. Not sure, It's the first time for me to use b43 with the lp-phy because I happend to know it is supported now. If it's a regression I can do bisection. Add larry/john/Markus to cc-list News: With following config option set to y, b43 works happily now. CONFIG_B43_FORCE_PIO=y -- Greetings, Michael. -- Regards dave -- Regards dave ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 dma error
Do you have the threaded-IRQ patches applied? Also, what card is this? (BCM4312?) Try upgrading your firmare (use v478 or the new v5xx one). ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 dma error
On Tue, Sep 8, 2009 at 7:50 PM, John Daikerdaikerj...@gmail.com wrote: On 09/08/2009 07:54 AM, Larry Finger wrote: Michael Buesch wrote: On Tuesday 08 September 2009 15:47:32 Dave Young wrote: I tested wireless-testing b43 driver, but got Fatal DMA error then the controller keep restarting... Please tell what I can provide or test, Thanks. Is this a regression? If so, please bisect. It is something specific to his system as I don't see anything like this. In addition, there are some users on the openSUSE forums that have implemented the latest compat-wireless and switched away from Broadcom wl to b43 on their LP PHY devices. So far, no complaints from them. Please reboot so that we see the ssb output as well. Use the command dmesg | egrep ssb|b43 That way we will be able to see exactly what kind of device you have and what revisions are in it. AFAIK, the testing to date has been limited to Rev 1 PHYs and Rev 2 radios. Larry I can confirm the same issue. I have a HP Mini 1116NR with a Broadcom 4312. Looks to be a PHY 1, Radio 2: --snip-- [ 456.165296] b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1 [ 456.165364] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2 --snip-- I've attached the output of 'dmesg | egrep ssb|b43', my kernel config, and lspci -vv and lspci -nn Note: With the dmesg output, I had unloaded the b43 module previous 'modprobe -r b43' and then loaded it again with debug output: 'modprobe b43 verbose=3' John Daiker Again, please test with v478 or v5xx firmware. -- 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: b43 dma error
On Tuesday 08 September 2009 19:50:25 John Daiker wrote: On 09/08/2009 07:54 AM, Larry Finger wrote: Michael Buesch wrote: On Tuesday 08 September 2009 15:47:32 Dave Young wrote: I tested wireless-testing b43 driver, but got Fatal DMA error then the controller keep restarting... Please tell what I can provide or test, Thanks. Is this a regression? If so, please bisect. It is something specific to his system as I don't see anything like this. In addition, there are some users on the openSUSE forums that have implemented the latest compat-wireless and switched away from Broadcom wl to b43 on their LP PHY devices. So far, no complaints from them. Please reboot so that we see the ssb output as well. Use the command dmesg | egrep ssb|b43 That way we will be able to see exactly what kind of device you have and what revisions are in it. AFAIK, the testing to date has been limited to Rev 1 PHYs and Rev 2 radios. Larry I can confirm the same issue. I have a HP Mini 1116NR with a Broadcom 4312. Looks to be a PHY 1, Radio 2: --snip-- [ 456.165296] b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1 [ 456.165364] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2 --snip-- I've attached the output of 'dmesg | egrep ssb|b43', my kernel config, and lspci -vv and lspci -nn Note: With the dmesg output, I had unloaded the b43 module previous 'modprobe -r b43' and then loaded it again with debug output: 'modprobe b43 verbose=3' John Daiker To ask the question once again: Is this a regression? This is a critical question to track down the bug. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 dma error
On Tuesday 08 September 2009 20:06:49 Gábor Stefanik wrote: On Tue, Sep 8, 2009 at 7:50 PM, John Daikerdaikerj...@gmail.com wrote: On 09/08/2009 07:54 AM, Larry Finger wrote: Michael Buesch wrote: On Tuesday 08 September 2009 15:47:32 Dave Young wrote: I tested wireless-testing b43 driver, but got Fatal DMA error then the controller keep restarting... Please tell what I can provide or test, Thanks. Is this a regression? If so, please bisect. It is something specific to his system as I don't see anything like this. In addition, there are some users on the openSUSE forums that have implemented the latest compat-wireless and switched away from Broadcom wl to b43 on their LP PHY devices. So far, no complaints from them. Please reboot so that we see the ssb output as well. Use the command dmesg | egrep ssb|b43 That way we will be able to see exactly what kind of device you have and what revisions are in it. AFAIK, the testing to date has been limited to Rev 1 PHYs and Rev 2 radios. Larry I can confirm the same issue. I have a HP Mini 1116NR with a Broadcom 4312. Looks to be a PHY 1, Radio 2: --snip-- [ 456.165296] b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1 [ 456.165364] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2 --snip-- I've attached the output of 'dmesg | egrep ssb|b43', my kernel config, and lspci -vv and lspci -nn Note: With the dmesg output, I had unloaded the b43 module previous 'modprobe -r b43' and then loaded it again with debug output: 'modprobe b43 verbose=3' John Daiker Again, please test with v478 or v5xx firmware. This won't help. The DMA engine reports a descriptor error. That means the device was unable to fetch the control data via DMA. Most of the time this indicates a bug/failure/quirk in the platform DMA implementation. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 dma error
John Daiker wrote: On 09/08/2009 07:54 AM, Larry Finger wrote: Michael Buesch wrote: On Tuesday 08 September 2009 15:47:32 Dave Young wrote: I tested wireless-testing b43 driver, but got Fatal DMA error then the controller keep restarting... Please tell what I can provide or test, Thanks. Is this a regression? If so, please bisect. It is something specific to his system as I don't see anything like this. In addition, there are some users on the openSUSE forums that have implemented the latest compat-wireless and switched away from Broadcom wl to b43 on their LP PHY devices. So far, no complaints from them. Please reboot so that we see the ssb output as well. Use the command dmesg | egrep ssb|b43 That way we will be able to see exactly what kind of device you have and what revisions are in it. AFAIK, the testing to date has been limited to Rev 1 PHYs and Rev 2 radios. Larry I can confirm the same issue. I have a HP Mini 1116NR with a Broadcom 4312. Looks to be a PHY 1, Radio 2: --snip-- [ 456.165296] b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1 [ 456.165364] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2 --snip-- I've attached the output of 'dmesg | egrep ssb|b43', my kernel config, and lspci -vv and lspci -nn Note: With the dmesg output, I had unloaded the b43 module previous 'modprobe -r b43' and then loaded it again with debug output: 'modprobe b43 verbose=3' Your PHY and your radio are the same as mine. In fact, the one thing I noticed is that you are using i386 architecture, whereas mine is x86_64. I have not tested with i386. Has anyone run the LP PHY modifications with 32-bit architecture? Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 dma error
On Tue, Sep 8, 2009 at 8:16 PM, Larry Fingerlarry.fin...@lwfinger.net wrote: John Daiker wrote: On 09/08/2009 07:54 AM, Larry Finger wrote: Michael Buesch wrote: On Tuesday 08 September 2009 15:47:32 Dave Young wrote: I tested wireless-testing b43 driver, but got Fatal DMA error then the controller keep restarting... Please tell what I can provide or test, Thanks. Is this a regression? If so, please bisect. It is something specific to his system as I don't see anything like this. In addition, there are some users on the openSUSE forums that have implemented the latest compat-wireless and switched away from Broadcom wl to b43 on their LP PHY devices. So far, no complaints from them. Please reboot so that we see the ssb output as well. Use the command dmesg | egrep ssb|b43 That way we will be able to see exactly what kind of device you have and what revisions are in it. AFAIK, the testing to date has been limited to Rev 1 PHYs and Rev 2 radios. Larry I can confirm the same issue. I have a HP Mini 1116NR with a Broadcom 4312. Looks to be a PHY 1, Radio 2: --snip-- [ 456.165296] b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1 [ 456.165364] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2 --snip-- I've attached the output of 'dmesg | egrep ssb|b43', my kernel config, and lspci -vv and lspci -nn Note: With the dmesg output, I had unloaded the b43 module previous 'modprobe -r b43' and then loaded it again with debug output: 'modprobe b43 verbose=3' Your PHY and your radio are the same as mine. In fact, the one thing I noticed is that you are using i386 architecture, whereas mine is x86_64. I have not tested with i386. Has anyone run the LP PHY modifications with 32-bit architecture? Yes, me. (With the exact same card as John.) Larry -- To unsubscribe from this list: send the line unsubscribe linux-wireless in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- 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: b43 dma error
Michael Buesch wrote: This won't help. The DMA engine reports a descriptor error. That means the device was unable to fetch the control data via DMA. Most of the time this indicates a bug/failure/quirk in the platform DMA implementation. I can confirm that mine still works on x86_64 with firmware 410. I have a spare partition that I will use to load an i386 version of openSUSE 11.2 M6. That comes with a 2.6.31 kernel and it will be easy to implement compat-wireless. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 dma error
Gábor Stefanik wrote: On Tue, Sep 8, 2009 at 8:16 PM, Larry Fingerlarry.fin...@lwfinger.net wrote: Your PHY and your radio are the same as mine. In fact, the one thing I noticed is that you are using i386 architecture, whereas mine is x86_64. I have not tested with i386. Has anyone run the LP PHY modifications with 32-bit architecture? Yes, me. (With the exact same card as John.) Is it a maximum memory issue? How much for you? John and Dave: Same question. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 dma error
2009/9/8 Larry Finger larry.fin...@lwfinger.net: Gábor Stefanik wrote: On Tue, Sep 8, 2009 at 8:16 PM, Larry Fingerlarry.fin...@lwfinger.net wrote: Your PHY and your radio are the same as mine. In fact, the one thing I noticed is that you are using i386 architecture, whereas mine is x86_64. I have not tested with i386. Has anyone run the LP PHY modifications with 32-bit architecture? Yes, me. (With the exact same card as John.) Is it a maximum memory issue? How much for you? John and Dave: Same question. Larry 2GB here. -- 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: b43 dma error
2009/9/8 Gábor Stefanik netrolller...@gmail.com 2009/9/8 Larry Finger larry.fin...@lwfinger.net: Gábor Stefanik wrote: On Tue, Sep 8, 2009 at 8:16 PM, Larry Fingerlarry.fin...@lwfinger.net wrote: Your PHY and your radio are the same as mine. In fact, the one thing I noticed is that you are using i386 architecture, whereas mine is x86_64. I have not tested with i386. Has anyone run the LP PHY modifications with 32-bit architecture? Yes, me. (With the exact same card as John.) Is it a maximum memory issue? How much for you? John and Dave: Same question. Larry 2GB here. Having 1 or 2 GB shouldn't be a problem. My trial will be with 3 - right on the pae kernel boundary. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 dma error
After some tests with the 32-bit architecture, I'm now thoroughly confused. I tried different memory models including PAE - everything worked. I even generated a 2.6.31-rc9-wl kernel with John's config and it worked. Whatever is happening is not related to his configuration. I'm not sure what the problem is. I'm going to be offline for a few days - I hope the solution will be in my mailbox by the weekend. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
