[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#606994: DMA error with b43 on HP Mini 1115NR under Debian Testing (Squeeze)



On Mon, 2010-12-13 at 22:48 +0300, Jonathon Anderson wrote:
> Package: linux-image-2.6-686
> Version: 2.6.32+28
> 
> I am experiencing what I believe to be a bug in the b43 driver
> characterized by the following excerpt from my kernel ring buffer:
> 
>    b43-pci-bridge 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>    b43-pci-bridge 0000:01:00.0: setting latency timer to 64
>    b43-phy0: Broadcom 4312 WLAN found (core revision 15)
>    Registered led device: b43-phy0::tx
>    Registered led device: b43-phy0::rx
>    Registered led device: b43-phy0::radio
>    b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
>    b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
>    b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000,
> 0x00000000, 0x00000000, 0x00000000, 0x00000000
>    b43-phy0 ERROR: This device does not support DMA on your system.
> It will now be switched to PIO.
>    b43-phy0: Controller RESET (DMA error) ...
>    b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
>    b43-phy0: Controller restarted

A log with timestamps would be more helpful.

> Once this error occurs, the only way to regain correct operation is to
> power-cycle the device: rebooting the kernel is not sufficient.
> 
> This behavior manifests itself repeatably after short use, and seems
> to be invoked by the transition of the hardware between low- and
> high-power modes.  (I can prevent the behavior by continually playing
> a locally-stored mp3 in the background.  I expect that this keeps my
> CPU throttled up, and prevents the system overall from transitioning
> to a low-power state.)
> 
> I am running Debian Testing (Squeeze).  I first noticed this error
> under Linux 2.6.32, installed by default.  I installed 2.6.36 from
> Experimental thinking that the bug had been fixed in 2.6.34, but the
> behavior persists.  (The preceding log was generated by 2.6.36.
> 2.6.32 generated largely similar logs, except that it recommended PIO
> mode, rather than purporting to switch to it.)

Did this wireless interface work under any previous kernel version?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: