Date: Thu, 17 Apr 2008 20:49:32 +0200 From: Pascal Hofstee <caelian@gmail.com> To: Joe Marcus Clarke <marcus@freebsd.org> Cc: gnome@freebsd.org Subject: Re: CURRENT, devbuf memory allocation and hald Message-ID: <20080417204932.587b3314@nebuchadnezzar> In-Reply-To: <48079802.8020505@freebsd.org> References: <d8a0b7620804170403l4f233aben82ff9803aebc33a8@mail.gmail.com> <1208440190.60309.5.camel@shumai.marcuscom.com> <20080417155626.64f13d30@nebuchadnezzar> <1208441073.60309.11.camel@shumai.marcuscom.com> <20080417201652.634dbbe6@nebuchadnezzar> <48079802.8020505@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 17 Apr 2008 14:33:38 -0400 Joe Marcus Clarke <marcus@freebsd.org> wrote: > This could be related to the recent ATA changes in -CURRENT. > Typically, we poll /dev/cd0 using ATAPICAM. You might try removing > any fdi files you've created to use the ATAPI device rather than the > ATAPICAM device to see if it helps. > > On each pass of the poller, we send a TUR command to the device. If > the command returns that the device is ready, we say it has media. > The code for this can be found in libprobe/hfp-cdrom.c. I have not created any fdi files myself but since the problem seems to be cd/dvd related i already went ahead and actually loaded the atapicam kernel module and restarted hald ... unfortunately the problem persists though in a mitigated form ... the increase with atapicam loaded seems to be at 40k/10sec instead of 140k/10s without atapicam loaded. Whether i have inserted or not does not seem to have any impact on the problem whatsoever though. -- Pascal Hofstee
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080417204932.587b3314>