From owner-freebsd-stable@FreeBSD.ORG Sat Aug 17 07:38:48 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C1682962 for ; Sat, 17 Aug 2013 07:38:48 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 979AB29FA for ; Sat, 17 Aug 2013 07:38:48 +0000 (UTC) Received: by mail-pb0-f53.google.com with SMTP id up15so2827864pbc.26 for ; Sat, 17 Aug 2013 00:38:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=4Cz4ioHgNKbmmpGh8vfwDFj83tm2JHpkXlodVfRZjIk=; b=HKdION/U2ePNTOEQEtgCVe37tg8D/GIm7fAs4jnES+bFGnbKDb/cTfHItMUf27kNwC bbbC6kbpE20A2Nq0wTFvXFBx4T3xLpQc2qCJ2NGocqObsl37et+aVELjHPhGW11WgU44 uJ32ICwaLhSHvcnICCpoU3DcZB5TJnTc7xqqI3O282xzmVdyPf4rU0XibAMr4UhLhBfA 3zgx9ZsZsXnP+SwvLKncxXyZOtDLhwoMKSWRPx9O7qEg9NYJ5FGQfKwg7T2gJb2CCBrY 3/puYu2m9D82KbqDkfiHlslx341SJg7Y/uxtc+512nWW4XGDN1X74v0bSrkog46B3Mm8 mlOg== MIME-Version: 1.0 X-Received: by 10.68.137.134 with SMTP id qi6mr518589pbb.154.1376725128243; Sat, 17 Aug 2013 00:38:48 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.14.66 with HTTP; Sat, 17 Aug 2013 00:38:48 -0700 (PDT) In-Reply-To: References: <520E2DDD.6050900@zenker.tk> <520E2FC8.7010305@zenker.tk> Date: Sat, 17 Aug 2013 00:38:48 -0700 X-Google-Sender-Auth: e_uFl6e_zzIFNraawET0qpvAk5E Message-ID: Subject: Re: FBSD 9.2 RC crashes running as virtualbox host From: Kevin Oberman To: Warren Block Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-stable@freebsd.org Stable" , Thomas Zenker X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Aug 2013 07:38:48 -0000 On Fri, Aug 16, 2013 at 11:34 PM, Kevin Oberman wrote: > On Fri, Aug 16, 2013 at 10:44 PM, Kevin Oberman wrote: > >> On Fri, Aug 16, 2013 at 2:01 PM, Warren Block wrote: >> >>> On Fri, 16 Aug 2013, Thomas Zenker wrote: >>> >>> On 08/16/13 15:41, Mikhail Tsatsenko wrote: >>>> >>>>> 2013/8/16 Thomas Zenker : >>>>> >>>>>> Hi, >>>>>> >>>>>> after updating my freebsd amd64 box from 9.1 (r250841) to 9.2-RC >>>>>> (r254276) virtualbox crashes the machine. Seconds after starting VBOX >>>>>> >>>>> After starting VBOX gui or guest machine? If first, try to rebuild >>>>> userland portion of vbox too. >>>>> >>>> >>>> After starting a virtual guest machine in the GUI or directly >>>> from cli >>>> leads to the crash. The userland has been rebuild w/ 9.2 also. The same >>>> binaries of the userland portion built with 9.2 work w/o problems in >>>> 9.1. >>>> >>> >>> Updated to 9.2-PRERELEASE #0 r254408 amd64 today, rebuilt and reloaded >>> the VirtualBox kernel module, and just started a couple of guests from the >>> GUI with no problems. >>> >> >> Updated to r254416 today.Two crashes when I tried starting VirtualBox >> 4.16_2. I have both dumps and they ere very different. The first was a >> "spin lock held too long" and the second was a general protection fault. >> Both occurred when I attempted to start a saved Windows 7 VM. >> >> FreeBSD rogue.local 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254416M: >> Fri Aug 16 11:27:20 PDT 2013 root@rogue.local:/usr/obj/usr/src/sys/GENERIC >> amd64 >> >> #0 doadump (textdump=) at pcpu.h:234 >> 234 pcpu.h: No such file or directory. >> in pcpu.h >> (kgdb) #0 doadump (textdump=) at pcpu.h:234 >> #1 0xffffffff80915c66 in kern_reboot (howto=260) >> at /usr/src/sys/kern/kern_shutdown.c:449 >> #2 0xffffffff80916167 in panic (fmt=0x1
) >> at /usr/src/sys/kern/kern_shutdown.c:637 >> #3 0xffffffff80cfae80 in trap_fatal (frame=0x9, eva=> out>) >> at /usr/src/sys/amd64/amd64/trap.c:879 >> #4 0xffffffff80cfb691 in trap (frame=0xffffff8124900830) >> at /usr/src/sys/amd64/amd64/trap.c:605 >> #5 0xffffffff80ce4ac3 in calltrap () >> at /usr/src/sys/amd64/amd64/exception.S:232 >> #6 0xffffffff80b86015 in vm_map_entry_splay (addr=984915968, >> root=0xfffffe002c9af200) at /usr/src/sys/vm/vm_map.c:832 >> #7 0xffffffff80b870f7 in vm_map_lookup_entry (map=0xfffffe007535b640, >> address=984915968, entry=0xffffff8124900970) >> at /usr/src/sys/vm/vm_map.c:1080 >> #8 0xffffffff80b8a5cc in vm_map_madvise (map=0xfffffe007535b640, >> start=984915968, end=985440256, behav=5) at >> /usr/src/sys/vm/vm_map.c:2050 >> #9 0xffffffff80b8d9e3 in sys_madvise (td=0xfffffe000549e920, >> uap=) at /usr/src/sys/vm/vm_mmap.c:760 >> #10 0xffffffff80cfa62a in amd64_syscall (td=0xfffffe000549e920, traced=0) >> at subr_syscall.c:135 >> #11 0xffffffff80ce4da7 in Xfast_syscall () >> at /usr/src/sys/amd64/amd64/exception.S:391 >> #12 0x000000002ce13dcc in ?? () >> Previous frame inner to this frame (corrupt stack?) >> >> I can make the cores and text dumps available. kmod was rebuilt after >> the upgrade. >> > > Just confirmed that 254050 works fine. Trying 354162 and will continue > binary hunt till I find it. > > I am now up to 254270, at the point of the original failure report. I now suspect I may have botched the kmod re-install on my original failure. I am calling it quits of the night now, but will finish tests tomorrow morning. The updates are pretty few and far between between 270 and the present. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com