Skip to contentSkip to conversation

64-bit DMA problems with BCM4312 using b43

DISCUSSION Larry Finger 3 participants 7 messages Nov 13, 2009 – Nov 14, 2009 ACPI

lore
Share & tools
lore
#0 lore raw

A number of users are experiencing DMA descriptor or data errors using 64-bit DMA with the Broadcom BCM4312 wireless device. After careful review and a rewrite of the DMA code in the driver, we have not been able to fix the problem, but we have determined the following:

(1) The problem is much more likely to occur on netbook systems. Several of the developers have this card in regular notebook systems. None of us have the problem. Several brand/model combinations are affected including Dell Inspiron 910 and Acer Aspire One A150. Linus has also reported the same symptoms with a Core 2 ULV CPU. One of our devs questions if the deep-sleep support in the CPU is a problem. It is also believed that affected systems have a Phoenix BIOS.

(2) If CONFIG_ACPI_PROCESSOR is not set on affected systems, the error rate is much lower.

(3) When a DMA descriptor error occurs, a dump of the descriptors does not reveal any obvious problems.

(4) Once the problem occurs, resetting of the device does not restore proper operations. It is not a transient error.

Support for this device was not enabled in mainline until 2.6.32-rc2.

I do not know enough about either the ACPI or DMA code to begin debugging in either of those regions. Any suggestions on debugging strategies, or links to similar problems would be appreciated.

Thanks,

Larry

#1 lore raw
Quoted 3 lines · Larry Finger

I do not know enough about either the ACPI or DMA code to begin debugging in either of those regions. Any suggestions on debugging strategies, or links to similar problems would be appreciated.

Could the hardware be highly sensitive to DMA latencies? Take a look at the pm_qos code in ipw2100.

Signature · 1 line
Matthew Garrett | [email protected]
#2 lore raw
Quoted 8 lines · On Friday 13 November 2009 21:11:12 Matthew Garrett wrote:
Quoted 3 lines · Larry Finger

I do not know enough about either the ACPI or DMA code to begin debugging in either of those regions. Any suggestions on debugging strategies, or links to similar problems would be appreciated.

Could the hardware be highly sensitive to DMA latencies? Take a look at the pm_qos code in ipw2100.

This makes perfect sense, yes. The DMA engine has so many quirks, I wouldn't be surprised if it couldn't handle pm properly.

Signature · 1 line
Greetings, Michael.
#3 lore raw
Quoted 7 lines · Michael Buesch
Quoted 6 lines · On Friday 13 November 2009 21:11:12 Matthew Garrett wrote:
Quoted 3 lines · Larry Finger

I do not know enough about either the ACPI or DMA code to begin debugging in either of those regions. Any suggestions on debugging strategies, or links to similar problems would be appreciated.

Quoted 5 lines
Quoted 2 lines

Could the hardware be highly sensitive to DMA latencies? Take a look at the pm_qos code in ipw2100.

This makes perfect sense, yes. The DMA engine has so many quirks, I wouldn't be surprised if it couldn't handle pm properly.

I'm in the process of creating a patch to set the latency to 200 usec. The default is 2000. On my fast prosessors, it should not be anything nearly that slow. If we determine this to be the problem, then we can try tuning.

Larry

#4 lore raw
Quoted 3 lines · Larry Finger

I'm in the process of creating a patch to set the latency to 200 usec. The default is 2000. On my fast prosessors, it should not be anything nearly that slow. If we determine this to be the problem, then we can try tuning.

The latency is the amount of time it takes to get out of deep C states and into C0. That's a function of the processor design rather than the frequency.

Signature · 1 line
Matthew Garrett | [email protected]
#5 lore raw
Quoted 9 lines · Matthew Garrett
Quoted 3 lines · Larry Finger

I'm in the process of creating a patch to set the latency to 200 usec. The default is 2000. On my fast prosessors, it should not be anything nearly that slow. If we determine this to be the problem, then we can try tuning.

The latency is the amount of time it takes to get out of deep C states and into C0. That's a function of the processor design rather than the frequency.

Thanks for that info. I should have said my Turion 64 X2 is different.

Larry

#6 lore raw
In reply to Matthew Garrett
Quoted 9 lines · Matthew Garrett
Quoted 3 lines · Larry Finger

I'm in the process of creating a patch to set the latency to 200 usec. The default is 2000. On my fast prosessors, it should not be anything nearly that slow. If we determine this to be the problem, then we can try tuning.

The latency is the amount of time it takes to get out of deep C states and into C0. That's a function of the processor design rather than the frequency.

Thanks for your suggestion. The value of 200 fixed one of the two machines and greatly improved the other. He is currently testing with a value of 150, and will try 100 if that still fails.

Larry