CURRENT, devbuf memory allocation and hald

Pascal Hofstee caelian at
Thu Apr 17 13:56:33 UTC 2008

On Thu, 17 Apr 2008 09:49:49 -0400
Joe Marcus Clarke <marcus at> wrote:

> While hald might be the catalyst, I doubt the problem is there.  The
> fact that you only noticed this after updating -CURRENT leads me to
> think that something bad changed in -CURRENT that is being tickled by
> hald.

I did not mean to imply hald was the cause ... but indeed as you
indicated at least the catalyst :) 

> hald itself is probably not triggering this.  You might try killing of
> the various addons, and see if you can rule out a particular addon,
> or a particular device.

How would i go about disabling individual hald addons ?

With kind regards,
  Pascal Hofstee

More information about the freebsd-gnome mailing list