Date: Sun, 22 Apr 2007 23:23:30 -0300 From: Alejandro Pulver <alepulver@FreeBSD.org> To: freebsd-hackers@FreeBSD.org Subject: Re: Gaim log writing delays the system Message-ID: <20070422232330.5026cdca@deimos.mars.bsd> In-Reply-To: <20070414191842.15e2f8b1@deimos.mars.bsd> References: <20070414191842.15e2f8b1@deimos.mars.bsd>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sat, 14 Apr 2007 19:18:42 -0300 Alejandro Pulver <alepulver@FreeBSD.org> wrote: > Hello. > > I have enabled logging in Gaim, and when a chat message arrives and it > is logged the disk writing delays (freezes) the system for less than a > second, it can be noticed for example with XMMS which does a strange > sound during that period. > > I think this problem is related to the system and not the port, that's > why I asked here. Also I guess more information is needed about this, > like ktrace/truss output of Gaim together with kernel statistics > (vmstat/iostat). But other than ktrace, I don't use them. What would be > the commands to get the most relevant information about this? > > I am using FreeBSD 6.2-RELEASE, and the boot message is here (the file > dmesg_machine_2.txt): > > http://people.freebsd.org/~alepulver/disk-crash.tar.bz2 > > Thanks and Best Regards, > Ale > > P.S.: please CC me as I'm not subscribed. Hello. The issue only happens with gaim-devel, and seems to be related to the sound system (doesn't happen when disabling sounds). Sorry for the noise, I've been somewhat paranoid with this because it happened when I had a broken NVidia card (or incompatible with my motherboard), and some disk problems (these were apparently fixed in FreeBSD 6.2). So I thought it was a kernel problem (it happened on a machine with an old disk and on a new one so I discarded the possibility of hardware failing). Anyways the system does freeze for less than a second when that happens. I will make a more descriptive thread about this. Best Regards, Ale P.S.: I've also sent this to freebsd-performance@, because I thought that was more appropiate when I thought it was a disk driver problem. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGLBiiiV05EpRcP2ERAtR8AJ0RqGMbsrJmn889XOJ42Y8RfZAtzACfexTj gRQAVDTVV2qOVY2ZIOnW7Wk= =wBnr -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070422232330.5026cdca>