Date: Fri, 22 Nov 2002 12:05:23 -0800 From: "Sam Leffler" <sam@errno.com> To: "Juli Mallett" <jmallett@FreeBSD.ORG>, "David W. Chapman Jr." <dwcjr@inethouston.net> Cc: "Kris Kennaway" <kris@obsecurity.org>, <current@FreeBSD.ORG> Subject: Re: Lots of swapping from 'kldload acpi' Message-ID: <1c5901c29262$95b2ab80$52557f42@errno.com> References: <20021122195629.GA26958@rot13.obsecurity.org> <20021122195911.GB40847@leviathan.inethouston.net> <20021122120205.A38536@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> * De: "David W. Chapman Jr." <dwcjr@inethouston.net> [ Data: 2002-11-22 ]
> [ Subjecte: Re: Lots of swapping from 'kldload acpi' ]
> > On Fri, Nov 22, 2002 at 11:56:29AM -0800, Kris Kennaway wrote:
> > > I tried to kldload acpi on a system that has been running for about 3
> > > days, and the kldload process has been sitting there swapping for
> > > about an hour now. Breaking into DDB shows that
> > > acpi_alloc_wakeup_handler() is trying to contigmalloc(), and this is
> > > swapping around presumably trying to find enough space. The kldload
> > > process is unkillable from userland because it's working in the
> > > kernel.
> > >
> > > Can something be done to guard against this?
> >
> > From what I was told you can't kldload acpi after boot or that you
> > shouldn't.
>
> It might make sense to (once we go to user-space) prevent kldloading
> anything that calls contigmalloc().
The ubsec module calls contigmalloc (via the bus_dma routines) and quickly
aborts when it can't get the memory. Something else must be going on in
acpi.
Sam
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1c5901c29262$95b2ab80$52557f42>