From owner-freebsd-stable@FreeBSD.ORG Sat Aug 17 06:34:24 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 79B55172 for ; Sat, 17 Aug 2013 06:34:24 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4FFF327F0 for ; Sat, 17 Aug 2013 06:34:24 +0000 (UTC) Received: by mail-pb0-f45.google.com with SMTP id mc17so2798399pbc.18 for ; Fri, 16 Aug 2013 23:34:23 -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=rLpbT7idewdOgi7itWXVfgkF/8aEavAfbvhO54xtohE=; b=Q/hPo9PqPMci65raEfOkYIaMPcpl+phM6MMg3EdqFiCz6DYk46elvjde/OhgEofKwU jq/3VgLDwJ4JbDrTElF9EWOYdebpjo909+OSoEID6zJWiwHKg/LTdNmIUmGXTsjC2Ayf VPottmN8NmjOZKt9+SnKs24PfslYT/S+ssk2jZK82D4VXMk2QZfHg9eimb26Xuw1oJ9O 327G3qTG92doHnxkenWo3HR64Dsh5WRUjXCndrYUjTnEgqkFCTXh2Rq89JaOSQoE0QvF X5b2SFhuSEMmBaWN1Me4T0hX8gEpa817Fgik60/Gs5KcIXeerA5DwFREmeRJyT3DcphQ 9klw== MIME-Version: 1.0 X-Received: by 10.66.149.231 with SMTP id ud7mr1577664pab.8.1376721263713; Fri, 16 Aug 2013 23:34:23 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.14.66 with HTTP; Fri, 16 Aug 2013 23:34:23 -0700 (PDT) In-Reply-To: References: <520E2DDD.6050900@zenker.tk> <520E2FC8.7010305@zenker.tk> Date: Fri, 16 Aug 2013 23:34:23 -0700 X-Google-Sender-Auth: OJTwulquBojW-6M3EFkVNcjfMY0 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 06:34:24 -0000 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=) > 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. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com