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 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.) Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash If you want to provide additional information, please wait to receive the bug tracking number via email; you may then send any extra information to n...@bugs.debian.org (e.g. 999...@bugs.debian.org), where n is the bug number. Normally you will receive an acknowledgement via email including the bug report number within an hour; if you haven't received a confirmation, then the bug reporting process failed at some point (reportbug or MTA failure, BTS maintenance, etc.). -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikpnnadi9npmnze6ibhly5hqf6h-xnhse7ql...@mail.gmail.com
