From owner-freebsd-current@FreeBSD.ORG Mon Oct 3 15:51:59 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7039116A41F for ; Mon, 3 Oct 2005 15:51:59 +0000 (GMT) (envelope-from freebsd@orchid.homeunix.org) Received: from orchid.homeunix.org (bbb129.neoplus.adsl.tpnet.pl [83.27.191.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44DF843D45 for ; Mon, 3 Oct 2005 15:51:57 +0000 (GMT) (envelope-from freebsd@orchid.homeunix.org) Received: from [192.168.1.66] (blackacidevil.orchid.homeunix.org [192.168.1.66]) (authenticated bits=0) by orchid.homeunix.org (8.13.3/8.13.3) with ESMTP id j93FpoFr085288 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Mon, 3 Oct 2005 17:51:52 +0200 (CEST) (envelope-from freebsd@orchid.homeunix.org) Message-ID: <43415397.9090600@orchid.homeunix.org> Date: Mon, 03 Oct 2005 17:51:51 +0200 From: Karol Kwiatkowski User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050930) X-Accept-Language: en-us, en MIME-Version: 1.0 To: eculp@bafirst.com References: <20050924071340.tr01mijqyocwsgss@mail.bafirst.com> In-Reply-To: <20050924071340.tr01mijqyocwsgss@mail.bafirst.com> X-Enigmail-Version: 0.92.1.0 OpenPGP: id=06E09309; url=http://www.orchid.homeunix.org/carlos/gpg/0x06E09309.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87/1107/Sun Oct 2 10:09:39 2005 on orchid.homeunix.org X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: Weird freeze w/ skype w/kde in current of last 10-15 days. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@orchid.homeunix.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 15:51:59 -0000 eculp@bafirst.com wrote: > This is a really strange problem that even I don't believe;) > I have 7.0-CURRENT FreeBSD 7.0-CURRENT #22: Fri Sep 23 05:39:20 CDT 2005 > skype-1.2.0.11 > kde-3.4.2 > And when I start skype I get a hard lock. No console message, no log > messages, nothing. I have to turn it off and back on. > > The strange part involves the work arounds that are independient of one > another that I have found: > > Kernel compiled prior to around Sept. 9 works fine, zero problems with kde. > Current Kernel and using xdm in place of kde, works fine. > > Now I try to keep my box clean of old libraries and did a portupgrade > -Rruf of skype and kde with no changes and even that doesn't explain why > an older kernel would work unless I had some old libraries around, I > would assume and the working kernels aren't that old. > > To make it even more unusual I have 4 other machines showing the same > symptoms. They are all AMD 32 bit w/ different motherboards and from > 256M to 2M in memory. I don't have anything with an intel chip to test on. > > Any suggestions will be greatly appreciated, I have no idea where else > to look. > > Thanks, > > ed 'Me too' kind of post (no one replied on -current or -ports). As soon as skype's window shows up everything stops - no mouse, no keyboard, no ssh connection from other machine, no nothing. It started in similar period of time (few weeks ago but I don't know exactly). Here's my setup: FreeBSD 6.0-BETA5 #2: Mon Oct 3 14:27:55 CEST 2005 i386 AMD Athlon 2000+, 512MB I upgraded from 5.4-RELEASE (cvsup, make), recompiled all ports as instructed. Software used: skype-1.2.0.17 = up-to-date with port (previously skype-1.2.0.11, same effect) linux-XFree86-libs-4.3.99.902_3 = up-to-date with port linux-expat-1.95.5_3 = up-to-date with port linux-fontconfig-2.1_4 = up-to-date with port linux_base-8-8.0_6 = up-to-date with port linux_dri-4.3.0_3 = up-to-date with port kdebase-3.4.2_2 = up-to-date with port kdehier-1.0_8 = up-to-date with port kdelibs-3.4.2_1 = up-to-date with port kdemultimedia-3.4.2_1 = up-to-date with port kdeutils-3.4.2 = up-to-date with port Linux compatibility module loaded at system boot (linux_enable="YES"). Any help appreciated. Regards, Karol -- Karol Kwiatkowski