CURRENT, devbuf memory allocation and hald
Joe Marcus Clarke
marcus at marcuscom.com
Thu Apr 17 14:04:38 UTC 2008
On Thu, 2008-04-17 at 15:56 +0200, Pascal Hofstee wrote:
> On Thu, 17 Apr 2008 09:49:49 -0400
> Joe Marcus Clarke <marcus at marcuscom.com> 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 ?
The easiest way is just to kill them.
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20080417/c60c8dca/attachment.pgp
More information about the freebsd-gnome