* b43 with 14e4 gives DMA error
@ 2009-11-01 12:51 Thomas Wiecki
2009-11-01 15:30 ` Gábor Stefanik
0 siblings, 1 reply; 9+ messages in thread
From: Thomas Wiecki @ 2009-11-01 12:51 UTC (permalink / raw)
To: linux-wireless
0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312
802.11b/g [14e4:4315] (rev 01)
Subsystem: Dell Device [1028:000c]
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at f1ffc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: wl
Kernel modules: wl, ssb
A variable delay after loading the most recent b43 driver I get a lot
of (I hope last nights patches would have fixed the problems, but they
didn't):
[ 6895.111946] b43-phy0 ERROR: Fatal DMA error: 0x00000800,
0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
[ 6895.111955] b43-phy0: Controller RESET (DMA error) ...
[ 6895.336490] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[ 6900.841372] b43-phy0: Controller restarted
After installing the driver for the first time, I have a few minutes I
can use the wifi card, after that the DMA errors start to occur. Once
they occured after the first loading, they appear immediatly after
each loading.
Ubuntu 9.04 (most recent) with kernel 2.6.31-14-generic
Laptop is Dell E6500.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: b43 with 14e4 gives DMA error
2009-11-01 12:51 b43 with 14e4 gives DMA error Thomas Wiecki
@ 2009-11-01 15:30 ` Gábor Stefanik
2009-11-01 22:01 ` Thomas Wiecki
0 siblings, 1 reply; 9+ messages in thread
From: Gábor Stefanik @ 2009-11-01 15:30 UTC (permalink / raw)
To: Thomas Wiecki; +Cc: linux-wireless
On Sun, Nov 1, 2009 at 1:51 PM, Thomas Wiecki
<thomas.wiecki@googlemail.com> wrote:
> 0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312
> 802.11b/g [14e4:4315] (rev 01)
> Subsystem: Dell Device [1028:000c]
> Flags: bus master, fast devsel, latency 0, IRQ 17
> Memory at f1ffc000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: <access denied>
> Kernel driver in use: wl
> Kernel modules: wl, ssb
>
> A variable delay after loading the most recent b43 driver I get a lot
> of (I hope last nights patches would have fixed the problems, but they
> didn't):
> [ 6895.111946] b43-phy0 ERROR: Fatal DMA error: 0x00000800,
> 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
> [ 6895.111955] b43-phy0: Controller RESET (DMA error) ...
> [ 6895.336490] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> [ 6900.841372] b43-phy0: Controller restarted
>
> After installing the driver for the first time, I have a few minutes I
> can use the wifi card, after that the DMA errors start to occur. Once
> they occured after the first loading, they appear immediatly after
> each loading.
>
> Ubuntu 9.04 (most recent) with kernel 2.6.31-14-generic
>
> Laptop is Dell E6500.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Does noacpi/noapic or blacklisting module "processor" have any effect on this?
Also, is this on PhoenixBIOS?
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: b43 with 14e4 gives DMA error
2009-11-01 15:30 ` Gábor Stefanik
@ 2009-11-01 22:01 ` Thomas Wiecki
2009-11-02 11:26 ` Gábor Stefanik
0 siblings, 1 reply; 9+ messages in thread
From: Thomas Wiecki @ 2009-11-01 22:01 UTC (permalink / raw)
To: Gábor Stefanik; +Cc: linux-wireless
I did:
service acpid stop
service acpi-support stop
(and service dell-laptop stop)
processor was not loaded (I didn't blacklist it though).
Still, after a minute of using the card, DMA errors occured.
BIOS: It wouldn't tell me anything besides A11. It says to be a DELL
bios (do they make their own bioses or just rebrand them?).
2009/11/1 Gábor Stefanik <netrolller.3d@gmail.com>:
> On Sun, Nov 1, 2009 at 1:51 PM, Thomas Wiecki
> <thomas.wiecki@googlemail.com> wrote:
>> 0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312
>> 802.11b/g [14e4:4315] (rev 01)
>> Subsystem: Dell Device [1028:000c]
>> Flags: bus master, fast devsel, latency 0, IRQ 17
>> Memory at f1ffc000 (64-bit, non-prefetchable) [size=16K]
>> Capabilities: <access denied>
>> Kernel driver in use: wl
>> Kernel modules: wl, ssb
>>
>> A variable delay after loading the most recent b43 driver I get a lot
>> of (I hope last nights patches would have fixed the problems, but they
>> didn't):
>> [ 6895.111946] b43-phy0 ERROR: Fatal DMA error: 0x00000800,
>> 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
>> [ 6895.111955] b43-phy0: Controller RESET (DMA error) ...
>> [ 6895.336490] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
>> [ 6900.841372] b43-phy0: Controller restarted
>>
>> After installing the driver for the first time, I have a few minutes I
>> can use the wifi card, after that the DMA errors start to occur. Once
>> they occured after the first loading, they appear immediatly after
>> each loading.
>>
>> Ubuntu 9.04 (most recent) with kernel 2.6.31-14-generic
>>
>> Laptop is Dell E6500.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> Does noacpi/noapic or blacklisting module "processor" have any effect on this?
>
> Also, is this on PhoenixBIOS?
>
> --
> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: b43 with 14e4 gives DMA error
2009-11-01 22:01 ` Thomas Wiecki
@ 2009-11-02 11:26 ` Gábor Stefanik
2009-11-02 13:57 ` Thomas Wiecki
0 siblings, 1 reply; 9+ messages in thread
From: Gábor Stefanik @ 2009-11-02 11:26 UTC (permalink / raw)
To: Thomas Wiecki; +Cc: linux-wireless
2009/11/1 Thomas Wiecki <thomas.wiecki@googlemail.com>:
> I did:
>
> service acpid stop
> service acpi-support stop
> (and service dell-laptop stop)
>
> processor was not loaded (I didn't blacklist it though).
>
> Still, after a minute of using the card, DMA errors occured.
>
> BIOS: It wouldn't tell me anything besides A11. It says to be a DELL
> bios (do they make their own bioses or just rebrand them?).
Dell is infamous for rebranding 3rd-party BIOSes; run this to find out
if it's actually Phoenix:
dmidecode | grep -i phoenix
This should output a line on PhoenixBIOS & Phoenix AwardBIOS, but
nothing on other BIOSes - post the exact output here to see if it's
Phoenix or Award.
>
> 2009/11/1 Gábor Stefanik <netrolller.3d@gmail.com>:
>> On Sun, Nov 1, 2009 at 1:51 PM, Thomas Wiecki
>> <thomas.wiecki@googlemail.com> wrote:
>>> 0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312
>>> 802.11b/g [14e4:4315] (rev 01)
>>> Subsystem: Dell Device [1028:000c]
>>> Flags: bus master, fast devsel, latency 0, IRQ 17
>>> Memory at f1ffc000 (64-bit, non-prefetchable) [size=16K]
>>> Capabilities: <access denied>
>>> Kernel driver in use: wl
>>> Kernel modules: wl, ssb
>>>
>>> A variable delay after loading the most recent b43 driver I get a lot
>>> of (I hope last nights patches would have fixed the problems, but they
>>> didn't):
>>> [ 6895.111946] b43-phy0 ERROR: Fatal DMA error: 0x00000800,
>>> 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
>>> [ 6895.111955] b43-phy0: Controller RESET (DMA error) ...
>>> [ 6895.336490] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
>>> [ 6900.841372] b43-phy0: Controller restarted
>>>
>>> After installing the driver for the first time, I have a few minutes I
>>> can use the wifi card, after that the DMA errors start to occur. Once
>>> they occured after the first loading, they appear immediatly after
>>> each loading.
>>>
>>> Ubuntu 9.04 (most recent) with kernel 2.6.31-14-generic
>>>
>>> Laptop is Dell E6500.
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>
>> Does noacpi/noapic or blacklisting module "processor" have any effect on this?
>>
>> Also, is this on PhoenixBIOS?
>>
>> --
>> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
>>
>
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: b43 with 14e4 gives DMA error
2009-11-02 11:26 ` Gábor Stefanik
@ 2009-11-02 13:57 ` Thomas Wiecki
2009-11-02 14:22 ` Michael Buesch
0 siblings, 1 reply; 9+ messages in thread
From: Thomas Wiecki @ 2009-11-02 13:57 UTC (permalink / raw)
To: Gábor Stefanik; +Cc: linux-wireless
Produces no output. I checked without the grep and it is only listed as Dell...
2009/11/2 Gábor Stefanik <netrolller.3d@gmail.com>:
> 2009/11/1 Thomas Wiecki <thomas.wiecki@googlemail.com>:
>> I did:
>>
>> service acpid stop
>> service acpi-support stop
>> (and service dell-laptop stop)
>>
>> processor was not loaded (I didn't blacklist it though).
>>
>> Still, after a minute of using the card, DMA errors occured.
>>
>> BIOS: It wouldn't tell me anything besides A11. It says to be a DELL
>> bios (do they make their own bioses or just rebrand them?).
>
> Dell is infamous for rebranding 3rd-party BIOSes; run this to find out
> if it's actually Phoenix:
> dmidecode | grep -i phoenix
>
> This should output a line on PhoenixBIOS & Phoenix AwardBIOS, but
> nothing on other BIOSes - post the exact output here to see if it's
> Phoenix or Award.
>
>>
>> 2009/11/1 Gábor Stefanik <netrolller.3d@gmail.com>:
>>> On Sun, Nov 1, 2009 at 1:51 PM, Thomas Wiecki
>>> <thomas.wiecki@googlemail.com> wrote:
>>>> 0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312
>>>> 802.11b/g [14e4:4315] (rev 01)
>>>> Subsystem: Dell Device [1028:000c]
>>>> Flags: bus master, fast devsel, latency 0, IRQ 17
>>>> Memory at f1ffc000 (64-bit, non-prefetchable) [size=16K]
>>>> Capabilities: <access denied>
>>>> Kernel driver in use: wl
>>>> Kernel modules: wl, ssb
>>>>
>>>> A variable delay after loading the most recent b43 driver I get a lot
>>>> of (I hope last nights patches would have fixed the problems, but they
>>>> didn't):
>>>> [ 6895.111946] b43-phy0 ERROR: Fatal DMA error: 0x00000800,
>>>> 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
>>>> [ 6895.111955] b43-phy0: Controller RESET (DMA error) ...
>>>> [ 6895.336490] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
>>>> [ 6900.841372] b43-phy0: Controller restarted
>>>>
>>>> After installing the driver for the first time, I have a few minutes I
>>>> can use the wifi card, after that the DMA errors start to occur. Once
>>>> they occured after the first loading, they appear immediatly after
>>>> each loading.
>>>>
>>>> Ubuntu 9.04 (most recent) with kernel 2.6.31-14-generic
>>>>
>>>> Laptop is Dell E6500.
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>
>>>
>>> Does noacpi/noapic or blacklisting module "processor" have any effect on this?
>>>
>>> Also, is this on PhoenixBIOS?
>>>
>>> --
>>> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
>>>
>>
>
>
>
> --
> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: b43 with 14e4 gives DMA error
2009-11-02 13:57 ` Thomas Wiecki
@ 2009-11-02 14:22 ` Michael Buesch
2009-11-07 14:11 ` Thomas Wiecki
2009-11-14 11:49 ` Thomas Wiecki
0 siblings, 2 replies; 9+ messages in thread
From: Michael Buesch @ 2009-11-02 14:22 UTC (permalink / raw)
To: Thomas Wiecki; +Cc: Gábor Stefanik, linux-wireless
Can we have a full kernel log with b43 debugging enabled, please? (CONFIG_B43_DEBUG)
--
Greetings, Michael.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: b43 with 14e4 gives DMA error
2009-11-02 14:22 ` Michael Buesch
@ 2009-11-07 14:11 ` Thomas Wiecki
2009-11-14 11:49 ` Thomas Wiecki
1 sibling, 0 replies; 9+ messages in thread
From: Thomas Wiecki @ 2009-11-07 14:11 UTC (permalink / raw)
To: Michael Buesch; +Cc: Gábor Stefanik, linux-wireless
Don't know if I did it right, let me know if there is anything else
you need. Here is kern.log (I added CONFIG_B43_DEBUG to config.mk,
also, I am running compat-wireless-2009-11-07 -- I also tried most
recent wireless-testing, however, with the same result):
Nov 7 15:01:30 lateralus kernel: [ 101.013386] cfg80211: Calling
CRDA to update world regulatory domain
Nov 7 15:01:30 lateralus kernel: [ 101.117855] b43-pci-bridge
0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Nov 7 15:01:30 lateralus kernel: [ 101.117878] b43-pci-bridge
0000:0c:00.0: setting latency timer to 64
Nov 7 15:01:30 lateralus kernel: [ 101.184603] ssb: Sonics Silicon
Backplane found on PCI device 0000:0c:00.0
Nov 7 15:01:30 lateralus kernel: [ 101.222674] cfg80211: World
regulatory domain updated:
Nov 7 15:01:30 lateralus kernel: [ 101.222683] (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 7 15:01:30 lateralus kernel: [ 101.222691] (2402000 KHz -
2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 7 15:01:30 lateralus kernel: [ 101.222697] (2457000 KHz -
2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 7 15:01:30 lateralus kernel: [ 101.222704] (2474000 KHz -
2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 7 15:01:30 lateralus kernel: [ 101.222710] (5170000 KHz -
5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 7 15:01:30 lateralus kernel: [ 101.222716] (5735000 KHz -
5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 7 15:01:30 lateralus kernel: [ 101.237106] b43-phy0: Broadcom
4312 WLAN found (core revision 15)
Nov 7 15:01:30 lateralus kernel: [ 101.331600] phy0: Selected rate
control algorithm 'minstrel'
Nov 7 15:01:30 lateralus kernel: [ 101.332296] Registered led
device: b43-phy0::tx
Nov 7 15:01:30 lateralus kernel: [ 101.332309] Registered led
device: b43-phy0::rx
Nov 7 15:01:30 lateralus kernel: [ 101.332322] Registered led
device: b43-phy0::radio
Nov 7 15:01:30 lateralus kernel: [ 101.332368] Broadcom 43xx driver
loaded [ Features: PML, Firmware-ID: FW13 ]
Nov 7 15:01:30 lateralus kernel: [ 101.424508] b43 ssb0:0: firmware:
requesting b43/ucode15.fw
Nov 7 15:01:31 lateralus kernel: [ 101.657129] b43 ssb0:0: firmware:
requesting b43/lp0initvals15.fw
Nov 7 15:01:31 lateralus kernel: [ 101.667660] b43 ssb0:0: firmware:
requesting b43/lp0bsinitvals15.fw
Nov 7 15:01:31 lateralus kernel: [ 101.820518] b43-phy0: Loading
firmware version 478.104 (2008-07-01 00:50:23)
Nov 7 15:01:37 lateralus kernel: [ 107.761441] b43-phy0 ERROR: Fatal
DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000,
0x00000000
Nov 7 15:01:37 lateralus kernel: [ 107.761457] b43-phy0: Controller
RESET (DMA error) ...
Nov 7 15:01:37 lateralus kernel: [ 107.992539] b43-phy0: Loading
firmware version 478.104 (2008-07-01 00:50:23)
Nov 7 15:01:42 lateralus kernel: [ 113.617348] b43-phy0: Controller restarted
On Mon, Nov 2, 2009 at 3:22 PM, Michael Buesch <mb@bu3sch.de> wrote:
> Can we have a full kernel log with b43 debugging enabled, please? (CONFIG_B43_DEBUG)
>
> --
> Greetings, Michael.
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: b43 with 14e4 gives DMA error
2009-11-02 14:22 ` Michael Buesch
2009-11-07 14:11 ` Thomas Wiecki
@ 2009-11-14 11:49 ` Thomas Wiecki
2009-11-14 20:24 ` Michael Buesch
1 sibling, 1 reply; 9+ messages in thread
From: Thomas Wiecki @ 2009-11-14 11:49 UTC (permalink / raw)
To: Michael Buesch; +Cc: Gábor Stefanik, linux-wireless
This is probably what you requested:
[ 144.223547] b43-pci-bridge 0000:0c:00.0: PCI INT A -> GSI 17
(level, low) -> IRQ 17
[ 144.223563] b43-pci-bridge 0000:0c:00.0: setting latency timer to 64
[ 144.297386] ssb: Sonics Silicon Backplane found on PCI device 0000:0c:00.0
[ 144.555613] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
[ 144.613238] b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1
[ 144.613255] b43-phy0 debug: Found Radio: Manuf 0x17F, Version
0x2062, Revision 2
[ 144.732440] phy0: Selected rate control algorithm 'minstrel'
[ 144.735288] Registered led device: b43-phy0::tx
[ 144.735333] Registered led device: b43-phy0::rx
[ 144.735375] Registered led device: b43-phy0::radio
[ 144.735489] Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
[ 144.788270] b43 ssb0:0: firmware: requesting b43/ucode15.fw
[ 145.036087] b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
[ 145.245282] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
[ 145.420475] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[ 145.422895] b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz.
[ 146.943122] __ratelimit: 18 callbacks suppressed
[ 146.943126] type=1503 audit(1258156036.311:48):
operation="truncate" info="Failed name lookup - deleted entry"
error=-2 pid=2488 parent=2275 profile="/usr/lib/firefox-3.5.*/firefox"
requested_mask="w::" denied_mask="w::" fsuid=1000 ouid=1000
name=2F7661722F746D702F6574696C71735F4F52595068314A614B527537437537202864656C6574656429
[ 151.252345] b43-phy0 debug: Chip initialized
[ 151.252611] b43-phy0 debug: 64-bit DMA initialized
[ 151.252899] b43-phy0 debug: QoS enabled
[ 151.274853] b43-phy0 debug: Wireless interface started
[ 151.274870] b43-phy0 debug: Adding Interface type 2
[ 151.286248] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 162.465561] b43-phy0 ERROR: Fatal DMA error: 0x00000800,
0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
[ 162.465577] b43-phy0: Controller RESET (DMA error) ...
[ 162.466070] b43-phy0 debug: Wireless interface stopped
[ 162.466082] b43-phy0 debug: DMA-64 rx_ring: Used slots 1/64, Failed
frames 0/0 = 0.0%, Average tries 0.00
[ 162.466170] b43-phy0 debug: DMA-64 tx_ring_AC_BK: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
[ 162.473232] b43-phy0 debug: DMA-64 tx_ring_AC_BE: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
[ 162.481232] b43-phy0 debug: DMA-64 tx_ring_AC_VI: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
[ 162.489262] b43-phy0 debug: DMA-64 tx_ring_AC_VO: Used slots 2/256,
Failed frames 0/22 = 0.0%, Average tries 1.00
[ 162.497240] b43-phy0 debug: DMA-64 tx_ring_mcast: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
[ 162.692325] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[ 162.694773] b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz.
[ 168.188513] b43-phy0 debug: Chip initialized
[ 168.188776] b43-phy0 debug: 64-bit DMA initialized
[ 168.189087] b43-phy0 debug: QoS enabled
[ 168.209436] b43-phy0 debug: Wireless interface started
[ 168.209449] b43-phy0: Controller restarted
[ 168.218037] b43-phy0 ERROR: Fatal DMA error: 0x00000400,
0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
[ 168.218051] b43-phy0: Controller RESET (DMA error) ...
[ 168.221400] b43-phy0 debug: Wireless interface stopped
[ 168.221415] b43-phy0 debug: DMA-64 rx_ring: Used slots 0/64, Failed
frames 0/0 = 0.0%, Average tries 0.00
[ 168.221503] b43-phy0 debug: DMA-64 tx_ring_AC_BK: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
[ 168.229061] b43-phy0 debug: DMA-64 tx_ring_AC_BE: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
[ 168.237052] b43-phy0 debug: DMA-64 tx_ring_AC_VI: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
[ 168.245036] b43-phy0 debug: DMA-64 tx_ring_AC_VO: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
[ 168.253208] b43-phy0 debug: DMA-64 tx_ring_mcast: Used slots 0/256,
Failed frames 0/0 = 0.0%, Average tries 0.00
Does this help?
On Mon, Nov 2, 2009 at 3:22 PM, Michael Buesch <mb@bu3sch.de> wrote:
> Can we have a full kernel log with b43 debugging enabled, please? (CONFIG_B43_DEBUG)
>
> --
> Greetings, Michael.
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: b43 with 14e4 gives DMA error
2009-11-14 11:49 ` Thomas Wiecki
@ 2009-11-14 20:24 ` Michael Buesch
0 siblings, 0 replies; 9+ messages in thread
From: Michael Buesch @ 2009-11-14 20:24 UTC (permalink / raw)
To: Thomas Wiecki; +Cc: Gábor Stefanik, linux-wireless
On Saturday 14 November 2009 12:49:25 Thomas Wiecki wrote:
> Does this help?
See the "b43-phy0 ERROR: Fatal DMA error: 0x00000400" thread on the b43 mailing list:
https://lists.berlios.de/pipermail/bcm43xx-dev/2009-November/thread.html
We're developing a fix there.
This is a proposed fix, but it does not work on all machines.
Some machines seem to need a lower value then 200. You can try 100, for example.
https://lists.berlios.de/pipermail/bcm43xx-dev/2009-November/006338.html
--
Greetings, Michael.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2009-11-14 20:24 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-11-01 12:51 b43 with 14e4 gives DMA error Thomas Wiecki
2009-11-01 15:30 ` Gábor Stefanik
2009-11-01 22:01 ` Thomas Wiecki
2009-11-02 11:26 ` Gábor Stefanik
2009-11-02 13:57 ` Thomas Wiecki
2009-11-02 14:22 ` Michael Buesch
2009-11-07 14:11 ` Thomas Wiecki
2009-11-14 11:49 ` Thomas Wiecki
2009-11-14 20:24 ` Michael Buesch
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.