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

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

Your message dated Fri, 5 Jul 2013 20:15:57 +0200
with message-id <20130705181557.GE8593@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #606994,
regarding DMA error with b43 on HP Mini 1115NR under Debian Testing (Squeeze)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
606994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606994
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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. 999999@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.).

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: