From owner-freebsd-emulation@FreeBSD.ORG Sat Feb 13 14:48:21 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 160F61065694 for ; Sat, 13 Feb 2010 14:48:21 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail.itac.at (mail.itac.at [91.205.172.9]) by mx1.freebsd.org (Postfix) with ESMTP id 72EB08FC1C for ; Sat, 13 Feb 2010 14:48:20 +0000 (UTC) Received: from [91.205.172.21] (helo=webmail.bluelife.at) by mail.itac.at with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1NgJIA-0001Lw-Uy; Sat, 13 Feb 2010 15:48:19 +0100 MIME-Version: 1.0 Date: Sat, 13 Feb 2010 15:48:19 +0100 From: Bernhard Froehlich To: {BBLister} In-Reply-To: <20100212175157.GA62557@bigb3.homeftp.net> References: <20100212112029.GA84672@bigb3.homeftp.net> <6a8155659ea90d729d0068f8ad4d0a1e@bluelife.at> <20100212175157.GA62557@bigb3.homeftp.net> Message-ID: <7865b0c564344ed9a6fcfdad0b425464@bluelife.at> X-Sender: decke@bluelife.at User-Agent: RoundCube Webmail/0.3.1 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 X-Spam-Score: 0.6 (/) X-Spam-Report: Spam detection software, running on the system "mail.itac.at", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Fri, 12 Feb 2010 19:51:57 +0200, {BBLister} wrote: > On Fri, Feb 12, 2010 at 12:53:48PM +0100, Bernhard Froehlich wrote: >> On Fri, 12 Feb 2010 13:20:29 +0200, {BBLister} >> wrote: >> >> Hi there >> >> >> >> 02/02/2010 I had update my workstation from 7.2-STABLE to >> >> 7.3-PRERELEASE. After install new kernel and world all installed >> >> ports >> >> also was rebuilt too by portupgrade -af. Now, I have kernel panic >> >> during attempt starts any virtual machine (Win or BSD) via GUI or >> >> headless. >> >> >> >> Any suggestions are welcome. >> >> >> >> Thanks. >> >> >> >> >> >> Details: >> >> >> >> >> >>I've got additional info with last panic: >> >> >> >>Unread portion of the kernel message buffer: >> >>HHWWAACCCCMMRR00IInniittCCPPUU ccppuu 01 >> >> >> >>HWACCMR0InitCPU failed with rc=-4013 >> >>panic: vm_fault: fault on nofault entry, addr: c19ee000 >> >>cpuid = 0 >> >>Uptime: 28m29s >> >>Physical memory: 2026 MB >> >>Dumping 108 MB: 93 77 61 45 29 13 >> > >> > Hi, >> > >> > I can confirm this. >> > When I upgraded to 7.3-PRELEASE and virtualbox-ose 3.1.2 >> > I couldn't start ANY virtualbox machine, but immediately (in couple of >> > secs) >> > my system panic. >> > >> > I Upgraded to 8.0-STABLE and still my machine panics with >> virtualbox-ose >> > 3.1.2 >> > >> > I upgraded to 8.0-STABLE with Virtualbox-ose-devel (3.1.5) and I still >> > have panics. >> > >> > I downgraded port to virtualbox-3.0.51.r22902_3 and still my >> > 8.0-STABLE >> > machine immediatelly panics. >> > >> > Note that in 7.2-STABLE my virtualbox-3.0.51.r22902_3 run without any >> > problem with many months uptime. >> > >> > How can I find out what were the changes from 7.2-STABLE to >> > 7.3-PRELEASE >> ? >> > >> > I have an "AMD Athlon(tm) Processor (1394.08-MHz 686-class CPU)" >> > >> > >> > I always use the VBoxHeadless (no output on screen). >> >> Could you check out 8-stable at a specific date to narrow down what merge >> causes this problems? At home i use 8-stable from about a month [...] Content analysis details: (0.6 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP 3.4 FH_DATE_PAST_20XX The date is grossly in the future. -1.4 AWL AWL: From: address is in the auto white-list Cc: freebsd-emulation@freebsd.org Subject: Re: virtualbox-ose 3.1.2 and 7.3-PRERELEASE X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Feb 2010 14:48:21 -0000 On Fri, 12 Feb 2010 19:51:57 +0200, {BBLister} wrote: > On Fri, Feb 12, 2010 at 12:53:48PM +0100, Bernhard Froehlich wrote: >> On Fri, 12 Feb 2010 13:20:29 +0200, {BBLister} >> wrote: >> >> Hi there >> >> >> >> 02/02/2010 I had update my workstation from 7.2-STABLE to >> >> 7.3-PRERELEASE. After install new kernel and world all installed >> >> ports >> >> also was rebuilt too by portupgrade -af. Now, I have kernel panic >> >> during attempt starts any virtual machine (Win or BSD) via GUI or >> >> headless. >> >> >> >> Any suggestions are welcome. >> >> >> >> Thanks. >> >> >> >> >> >> Details: >> >> >> >> >> >>I've got additional info with last panic: >> >> >> >>Unread portion of the kernel message buffer: >> >>HHWWAACCCCMMRR00IInniittCCPPUU ccppuu 01 >> >> >> >>HWACCMR0InitCPU failed with rc=-4013 >> >>panic: vm_fault: fault on nofault entry, addr: c19ee000 >> >>cpuid = 0 >> >>Uptime: 28m29s >> >>Physical memory: 2026 MB >> >>Dumping 108 MB: 93 77 61 45 29 13 >> > >> > Hi, >> > >> > I can confirm this. >> > When I upgraded to 7.3-PRELEASE and virtualbox-ose 3.1.2 >> > I couldn't start ANY virtualbox machine, but immediately (in couple of >> > secs) >> > my system panic. >> > >> > I Upgraded to 8.0-STABLE and still my machine panics with >> virtualbox-ose >> > 3.1.2 >> > >> > I upgraded to 8.0-STABLE with Virtualbox-ose-devel (3.1.5) and I still >> > have panics. >> > >> > I downgraded port to virtualbox-3.0.51.r22902_3 and still my >> > 8.0-STABLE >> > machine immediatelly panics. >> > >> > Note that in 7.2-STABLE my virtualbox-3.0.51.r22902_3 run without any >> > problem with many months uptime. >> > >> > How can I find out what were the changes from 7.2-STABLE to >> > 7.3-PRELEASE >> ? >> > >> > I have an "AMD Athlon(tm) Processor (1394.08-MHz 686-class CPU)" >> > >> > >> > I always use the VBoxHeadless (no output on screen). >> >> Could you check out 8-stable at a specific date to narrow down what merge >> causes this problems? At home i use 8-stable from about a month ago and >> could not reproduce that so it should have happened in the last few >> weeks. >> >> So if you do not want to test that but only have virtualbox working again >> then try to check out the sources from about a month ago. >> >> Thanks! >> >> -- >> Bernhard Fr??hlich >> http://www.bluelife.at/ > > > > > Hi, > > I can check out a previous 8-stable version. > A) If I use the following lines in my cvsup will this be ok? I will check > out > 8-stable of 10th of January 2010 of 01:01:01 > ( date=[cc]yy.mm.dd.hh.mm.ss ) > > === > > *default release=cvs tag=RELENG_8 > *default date=2010.01.10.01.01.01 > > === Yeah looks good. I have checked my laptop and have: FreeBSD 8.0-STABLE/amd64 #0: Fri Jan 8 09:39:23 CET 2010 > B) What CPU do you have? Perhaps my AMD Athlon excibits the same behaviour > like AMD64 ? I see in wiki > "Launching virtual machine on 8.0-BETA2/amd64 instantly panic the system" CPU: Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz (2194.52-MHz K8-class CPU) The panic mentioned above was already solved before 8.0-RELEASE. -- Bernhard Fröhlich http://www.bluelife.at/