Date: Thu, 17 Apr 2008 15:56:26 +0200 From: Pascal Hofstee <caelian@gmail.com> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: gnome@freebsd.org Subject: Re: CURRENT, devbuf memory allocation and hald Message-ID: <20080417155626.64f13d30@nebuchadnezzar> In-Reply-To: <1208440190.60309.5.camel@shumai.marcuscom.com> References: <d8a0b7620804170403l4f233aben82ff9803aebc33a8@mail.gmail.com> <1208440190.60309.5.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 17 Apr 2008 09:49:49 -0400 Joe Marcus Clarke <marcus@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 ? With kind regards, Pascal Hofstee
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080417155626.64f13d30>