From owner-freebsd-net@FreeBSD.ORG Thu Dec 30 15:00:24 2010 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52005106564A for ; Thu, 30 Dec 2010 15:00:24 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 408E18FC08 for ; Thu, 30 Dec 2010 15:00:24 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBUF0OHY003901 for ; Thu, 30 Dec 2010 15:00:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBUF0OEt003883; Thu, 30 Dec 2010 15:00:24 GMT (envelope-from gnats) Date: Thu, 30 Dec 2010 15:00:24 GMT Message-Id: <201012301500.oBUF0OEt003883@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Oliver Ebert Cc: Subject: Re: kern/143874: [wpi] Wireless 3945ABG error. wpi0 could not allocate memory resource X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Oliver Ebert List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2010 15:00:24 -0000 The following reply was made to PR kern/143874; it has been noted by GNATS. From: Oliver Ebert To: Bernhard Schmidt Cc: bug-followup@freebsd.org Subject: Re: kern/143874: [wpi] Wireless 3945ABG error. wpi0 could not allocate memory resource Date: Thu, 30 Dec 2010 08:55:43 -0600 Too bad but it is interesting that Solaris 10 had exactly the same issue with the wpi driver. Anyway thanks for taking a look to this issue. On Thu, 30 Dec 2010 12:12:43 +0100 Bernhard Schmidt wrote: > On Sunday 19 December 2010 18:10:11 Oliver Ebert wrote: > > Bernhard Schmidt wrote: > > > Is this still an issue on a recent stable/8 or 8.2-BETA1? > > > > With 8.1 it is but I didn't had a chance to check with 8.2 beta. > > According to John Baldwin this is long standing issue within our > {ACPI,PCI}-Bridge code, not directly related to the device driver > itself. Way above my clue level.. sorry for the noise. >