From owner-freebsd-ppc@freebsd.org  Mon Nov  9 21:44:05 2015
Return-Path: <owner-freebsd-ppc@freebsd.org>
Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3146FA2A89A
 for <freebsd-ppc@mailman.ysv.freebsd.org>;
 Mon,  9 Nov 2015 21:44:05 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com
 [IPv6:2607:f8b0:4001:c06::22b])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id F40AD151B
 for <freebsd-ppc@freebsd.org>; Mon,  9 Nov 2015 21:44:04 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: by iodd200 with SMTP id d200so200948180iod.0
 for <freebsd-ppc@freebsd.org>; Mon, 09 Nov 2015 13:44:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:date:message-id:subject:from:to:cc:content-type;
 bh=JNZ4JAy9Aa+KLFe5Gj0bdDp2W842f5BZGojf7WfY3qQ=;
 b=nfJkWMapzn0pZT9GGbh6IGYS60L8+UDZ48s0fGaUNrjUO3Fo6TzcMvpBFOr2daki56
 MByRc3uqKjVouYm1yA8SwNXLRFRk5zavpltlzV6HQh6KqZ7BmWYoV1t6yZ6LhT3FFOcC
 9FIF06VHWZtZyVLEMjyLjWdGbazkkQIIYxxdmcGHyhCHwP3IQVij4N7Kf0MRny6pqDMa
 zmyuNitVspHDr8klOA8x2rnE5VYmo7VIWaX0mfp0kOMSvv0zE2wvQD2gZjE+Ep++PICo
 ZdMw9O5NHzeX+zeROYKyiwmt3o6Pt1UgkNfsYaVOCkxFp7+NtVLlVSJ6u6LIE8FNzXjR
 yv+g==
MIME-Version: 1.0
X-Received: by 10.107.152.2 with SMTP id a2mr569943ioe.123.1447105444362; Mon,
 09 Nov 2015 13:44:04 -0800 (PST)
Sender: adrian.chadd@gmail.com
Received: by 10.36.217.196 with HTTP; Mon, 9 Nov 2015 13:44:04 -0800 (PST)
Date: Mon, 9 Nov 2015 13:44:04 -0800
X-Google-Sender-Auth: DJ-Agy8tv49OdODgRu80PXRl5Bk
Message-ID: <CAJ-Vmom0qAS6EmWgvMQdLotsVyKfmJuVKt9QTg2OJD6WOiVjrw@mail.gmail.com>
Subject: Re: Airport Extreme WiFi Broken in FreeBSD 10.2
From: Adrian Chadd <adrian@freebsd.org>
To: Curtis Hamilton <hamiltcl@verizon.net>
Cc: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-ppc@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting FreeBSD to the PowerPC <freebsd-ppc.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ppc>,
 <mailto:freebsd-ppc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ppc/>
List-Post: <mailto:freebsd-ppc@freebsd.org>
List-Help: <mailto:freebsd-ppc-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ppc>,
 <mailto:freebsd-ppc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2015 21:44:05 -0000

Hi,

It looks like there's something up with the memory management, not
wifi. ata2 failing and bwi failing in DMA memory allocation is the
hint. :)



-a


On 9 November 2015 at 12:00, Curtis Hamilton <hamiltcl@verizon.net> wrote:
> Has anyone else tried to load the BWI module in 10.2?  I attempted to load
> the kernel module and build a new kernel with the module built-in.  In both
> cases the boot process freezes with the following errors:
>
>
>
> ata2: <ATA channel > at channel0 on atapci0
>
> ata2: WARNING DMA initialization failed, disabling DMA
>
> ata2: FAILURE - alloc sg_map
>
> ata2: WARNING DMA allocation failed, disabling DMA
>
>
>
> A few lines before this the following error is shown:
>
>
>
> bwi0: can't allocate DMA mem
>
> bwi0: 0th TX ring DMA alloc-failed
>
>
>
> Everything works fine in 10.1
>
> _______________________________________________
> freebsd-ppc@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org"