Date: Thu, 23 Sep 2010 14:17:02 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-stable@freebsd.org Cc: Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no> Subject: Re: wifi issues under -stable Message-ID: <201009231417.02965.jhb@freebsd.org> In-Reply-To: <20100923180840.ac828e05.torfinn.ingolfsen@broadpark.no> References: <4C9A7943.1020806@gmail.com> <20100923180840.ac828e05.torfinn.ingolfsen@broadpark.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, September 23, 2010 12:08:40 pm Torfinn Ingolfsen wrote: > On Wed, 22 Sep 2010 16:46:43 -0500 > Jim Bryant <kc5vdj.freebsd@gmail.com> wrote: > > > One (this one) has an intel pro wireless 3945ABG installed, which returns: > > > > wpi0: <Intel(R) PRO/Wireless 3945ABG> irq 18 at device 0.0 on pci6 > > wpi0: Driver Revision 20071127 > > wpi0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff). > > wpi0: could not allocate memory resource > > device_attach: wpi0 attach returned 6 > > > > and the broadcom used in the other does the exact same thing. > > > > I'm thinking that this isn't really a problem with the wifi, but may be > > a mini-pci-e issue. > > More likelely, it is ACPI-related. Simply put: many laptops have > broken ACPI implementations. Other OS'es might have a workaround for > them, but FreeBSD does not. Well, in this case the breakage is probably that something in the ACPI initialization clears the resource ranges in a PCI-PCI bridge. However, I would not quite say that ACPI is broken in that case as FreeBSD's PCI-PCI bridge driver needs to handle this sort of case anyway in order to truly handle hotplug devices and 'PNP OS == YES', so this is really FreeBSD's fault rather than ACPI or the BIOS. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201009231417.02965.jhb>