From owner-freebsd-current@freebsd.org Wed Aug 8 21:45:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 516D1106C83F for ; Wed, 8 Aug 2018 21:45:31 +0000 (UTC) (envelope-from danilogondolfo@gmail.com) Received: from mail-ua0-f193.google.com (mail-ua0-f193.google.com [209.85.217.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EDF2C9603B; Wed, 8 Aug 2018 21:45:30 +0000 (UTC) (envelope-from danilogondolfo@gmail.com) Received: by mail-ua0-f193.google.com with SMTP id g18-v6so4083874uam.6; Wed, 08 Aug 2018 14:45:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PXxsPVS4gxqsFi1mPd8P8IO1OO8Av3OpygQZHtyATGE=; b=HtwroB1sp5HICkuiCBAaksG8PTzGjoBcp1JZLnp98HUX5L6u+tuhTqLkKI7GNSlwMo Hit7OIy/RytOIzXjH3HstqaJsy2T8OstICoFsL49tM9RhMZMnKuOUKz2OEODcduSiENU 6u3KJHhgZO/BfQfqtsAVhIOiodEqCPxvww5CV8GuTfwmf6Lv9JaiO8ZhypeBoDiPLYj5 /A2+PMplG189bVG6VcAMZhfIdhw0wc+5IrKbx7cAlO4YMJajWyKVdkhEBJMdjN0q9wFz a8ef7pEOshAPank+G/LVCUf44XkG43Vu4kNfRw4lxorE1dmzKo5floT8b5ZaJDIkoxU/ zk5w== X-Gm-Message-State: AOUpUlHcGXrksFgxoP/4HzgcktqMviIimiIVSNWo4j28/tc8JlMfLfR+ INP2vxpJAierIf1gbOL6cie+R2ut0cWNN+uHMUXJrTNlA9k= X-Google-Smtp-Source: AA+uWPyQyvMruIheWg1EjEx3hkbvoJuEDi4QbhdUaR2xLj2b4ZuH7BMrOpvfFfz0hU3eA+tOJbTWe/l8vYL9mYzpMGk= X-Received: by 2002:a1f:6307:: with SMTP id x7-v6mr2986153vkb.111.1533763163297; Wed, 08 Aug 2018 14:19:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Danilo_Eg=C3=AAa_Gondolfo?= Date: Wed, 8 Aug 2018 18:19:33 -0300 Message-ID: Subject: Re: Vbox causing host crash/reboot on 12-current To: vladimir@kondratyev.su Cc: a.n.us@ieee.org, FreeBSD-current , vbox@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Aug 2018 21:45:31 -0000 On Wed, Aug 8, 2018 at 5:25 PM Vladimir Kondratyev wrote: > Hi > > I am sure that crashes was caused by SMAP as I am faced with them too. > I have made following patch to fix panic (attached) > Apply it to portstree and rebuild emulators/virtualbox-ose-kmod > > P.S. It is POC so no arch/SMAP autodetection > > On 8/7/18 6:14 PM, AN wrote: > > Update: > > > > I found the revision: > > https://svnweb.freebsd.org/base?view=revision&revision=336876 > > > > Use SMAP on amd64. > > > > Could this possibly cause VBox to crash and reboot the system? Is > > there a sysctl to disable? > > > > Thanks > > > > On Tue, Aug 7, 2018 at 10:46 AM, AN wrote: > >> I recently started having severe instability on a workstation with > >> VirtualBox. I'm not sure if it was caused by the recent large ports > >> update, or a recent commit that affected SMAP. I can't seem to find > >> that revision, would someone please post it and also the workaround to > >> disable it, I would like to try it after work and see if disabling it > >> allows VBox to work. Is anyone else seeing this effect with Vbox? > >> > >> What I'm seeing is that as soon as a VM is started it reboots the > >> host, totally reproducible every time. I tried to rebuild VBox and > >> kmod, and also some qt5 ports but still not working. Any help is > >> appreciated, thanks for reading. > >> > >> Regards > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Same problem here, but I'm getting two different panics: Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x28 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80c7e806 stack pointer = 0x28:0xfffffe009ced64c0 frame pointer = 0x28:0xfffffe009ced64f0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 42332 (VBoxNetAdpCtl) and Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 02 fault virtual address = 0x804209ab8 fault code = supervisor read data, protection violation instruction pointer = 0x20:0xffffffff835cc164 stack pointer = 0x28:0xfffffe00b33031f0 frame pointer = 0x28:0xfffffe00b33031f0 code segment = base r x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 21985 (VBoxHeadless)