kern/143874: [wpi] Wireless 3945ABG error. wpi0 could not allocate memory resource

[Bernhard Schmidt]

On Monday 20 December 2010 12:06:24 Patrick Ale wrote:
> Hi,
> 
> Not sure if this is useful information for you but here goes:
> I have exactly the same problem on my Acer Aspire laptop with the same
> network card but then under Solaris 10 and Opensolaris, both 64 bit.
> 
> The only way for me to get rid of this error and get the card working
> is to reduce my memory from 4GB to <= 3GB.
> I got told it has to do with the PCI to PCI-X bridge masquarading some
> memory addresses..
> 
> I am not a kernel/driver/code guru but I thought one of you might get
> some pointers out of this..

There have been a few changes to PCI bridge code lately which might well fix 
that issue. If anyone could give a recent stable/8 or 8.2-BETA a shot, I'd 
really appreciate that.

> On Sun, Dec 19, 2010 at 6:10 PM, Oliver Ebert <oliver.solaris at gmail.com> 
wrote:
> > The following reply was made to PR kern/143874; it has been noted by
> > GNATS.
> > 
> > From: Oliver Ebert <oliver.solaris at gmail.com>
> > To: Bernhard Schmidt <bschmidt at techwires.net>
> > Cc: bug-followup at freebsd.org
> > Subject: Re: kern/143874: [wpi] Wireless 3945ABG error. wpi0 could not
> >  allocate memory resource
> > Date: Sun, 19 Dec 2010 10:39:47 -0600
> > 
> >  On Sun, 19 Dec 2010 11:49:27 +0100
> >  Bernhard Schmidt <bschmidt at techwires.net> wrote:
> > 
> >  > On Sunday 12 September 2010 05:30:10 oliver.solaris at gmail.com wrote:
> >  > > I have the same issue with a Toshiba Satellite P105:
> >  > >
> >  > > Sep 11 21:46:13  kernel: wpi0: <Intel(R) PRO/Wireless 3945ABG> irq
> >  > > 17 at device 0.0 on pci3
> >  > > Sep 11 21:46:13  kernel: wpi0: Driver Revision 20071127
> >  > > Sep 11 21:46:13  kernel: wpi0: 0x1000 bytes of rid 0x10 res 3 failed
> >  > > (0, 0xfffff fff).
> >  > > Sep 11 21:46:13  kernel: wpi0: could not allocate memory resource
> >  > > Sep 11 21:46:13  kernel: device_attach: wpi0 attach returned 6
> >  > >
> >  > > Please let me know if I can help out to track this issue down.
> >  >
> >  > 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.

-- 
Bernhard