[Bug 214235] [bwi] loading if_bwi fails to create parent DMA tag, causes "kstack allocation failed" errors

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Nov 5 05:50:58 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214235

            Bug ID: 214235
           Summary: [bwi] loading if_bwi fails to create parent DMA tag,
                    causes "kstack allocation failed" errors
           Product: Ports & Packages
           Version: Latest
          Hardware: powerpc
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: 0x5a80 at protonmail.com

Description: 

    Overview: On a PowerBook G4 running FreeBSD 10.3-RELEASE, using kldload to
load the bwi module fails with "could not create parent DMA tag" and running
nearly any process produces "vm_thread_new: kstack allocation failed" errors.
Loading the module at boot makes the computer lose power entirely and begin
booting again. 

    Steps to Reproduce: 

    1. Build and install bwi-firmware-kmod from ports on a Powerbook G4 with a
BCM4306v2 network card.
    2. To trigger the kstack allocation errors, kldload if_bwi.
    3. To trigger the repeated booting, add if_bwi_load="YES" to loader.conf
and reboot the machine.


    Actual Results: After "kldload if_bwi", any application that uses a
significant amount of resources will fail to work -- an easy example is to open
a sizeable number of tmux windows. If if_bwi is loaded at boot time, the
machine will repeatedly switch off and begin booting again midway through the
boot process until the related modules are disabled in OFW.


    Expected Results: Loading if_bwi should create a bwi0 device that can be
used to establish a network connection.

    Build Date & Hardware: Nov 05, 2016. BCM4306 rev2 on 15" Powerbook G4
(Motorola PowerPC 7457).

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list