Date: Wed, 14 Apr 2010 19:02:47 -0700 From: Yuri <yuri@rawbw.com> To: Mario Lobo <"lobo@bsd.com.br"@shell0.rawbw.com> Cc: freebsd-emulation@FreeBSD.org Subject: Re: problem with VBOX 3.1.6 on 8stable Message-ID: <4BC673C7.4000405@rawbw.com> In-Reply-To: <201004132008.06643.lobo@bsd.com.br> References: <alpine.BSF.1.10.1004131329370.12775@neu.net> <3e74d40fe494aa6b8fa161e0bb21465b@ringofsaturn.com> <201004132008.06643.lobo@bsd.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
Mario Lobo wrote: > I hope anyone has a suggestion for something I didn't try. > I have been trying before to downgrade the port version back to the time when I know it was working and I still observed the hangs. This vouches for the theory of faulty kernel change. One other thing to try would be to try various kernel versions around the time when instability was introduced and find what change triggered it (svn revision). For example these two revisions can be taken as interval limits (in branch stable-8): r202402 | marius | 2010-01-15 08:54:59 -0800 (Fri, 15 Jan 2010) | 9 lines r203748 | zec | 2010-02-10 00:50:06 -0800 (Wed, 10 Feb 2010) | 13 lines First try both to make sure the problem exists in the latter and not in the former. And then dividing by two you can find the culprit revision. This interval contains ~1200 revisions, and actually much fewer because not all changes go into stable-8. So it should take around 10 tries to figure out. Knowing which change caused the problem can give some insight into what the problem may be. Sorry for offering only such a tedious way, I can't see any better one at this time. I would do this myself, but I can't since I have no space machine to do this. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BC673C7.4000405>