> 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
