Date: 04 Nov 2002 22:00:38 +0100 From: Jan.Stocker@t-online.de (Jan Stocker) To: Terry Lambert <tlambert2@mindspring.com> Cc: Alex Zepeda <zipzippy@sonic.net>, current@FreeBSD.ORG Subject: Re: WIne freezes -current for half a year Message-ID: <1036443639.636.8.camel@twoflower> In-Reply-To: <3DC65310.82F4ED88@mindspring.com> References: <1036347156.634.8.camel@twoflower> <20021103165323.A56468@angelica.unixdaemons.com> <3DC5A4F9.1D61A32F@mindspring.com> <20021104022650.GA654@blarf.homeip.net> <3DC65310.82F4ED88@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> It'd probably be a good idea to try it again before reporting > it as if it were still not working. It may or may not have been > fixed by the signal and FP register state commits, etc., so just > because it was broken doesn't mean it's broken now. > > Even if it *is* still broken, it could be broken in an entirely > different way... 8-). It is broken with the same symtoms for the last months. a) FreeBSD freezes... you've to do a cold start, no keys or anything work b) FreeBSD reboots after a few secs of doing nothin' c) wine / wineserver process hangs in the background, doing nothing, consuming cpu time and cant be killed by kill -9 . My system is from 26. October. Not new enough? Tonight .i'll get the newest one and recompile the newest wine and tomorrow (8.00 CET) you'll get a dmesg / uname -a /sysctl -a for my system, i'm sure with a non-working wine. Jan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1036443639.636.8.camel>