From owner-freebsd-current@freebsd.org Fri Aug 3 20:43:02 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 E66CD1050397 for ; Fri, 3 Aug 2018 20:43:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4D5057485D for ; Fri, 3 Aug 2018 20:43:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w73Kgo1Y006651 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 3 Aug 2018 23:42:53 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w73Kgo1Y006651 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w73Kgo2P006650; Fri, 3 Aug 2018 23:42:50 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 3 Aug 2018 23:42:50 +0300 From: Konstantin Belousov To: Johannes Lundberg Cc: freebsd-current Subject: Re: Linux process causes kernel panic Message-ID: <20180803204250.GE6049@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home 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: Fri, 03 Aug 2018 20:43:02 -0000 On Fri, Aug 03, 2018 at 09:26:08PM +0100, Johannes Lundberg wrote: > Hi > > After install new kernel+world built from today's checkout I keep getting > the same crash over and over. Never had this problem before. The previous > kernel was from 3 weeks ago. > > Looks familiar to anyone? > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xfffe665c > fault code = supervisor write data, protection violation > instruction pointer = 0x20:0xffffffff82282db3 > stack pointer = 0x0:0xfffffe004c74c8c8 > frame pointer = 0x0:0xfffffe004c74c980 > 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 = 1579 (wcgrid_zika_vina_7.) > trap number = 12 > panic: page fault > cpuid = 0 > time = 1533327428 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe004c74c580 > vpanic() at vpanic+0x1a3/frame 0xfffffe004c74c5e0 > panic() at panic+0x43/frame 0xfffffe004c74c640 > trap_fatal() at trap_fatal+0x35f/frame 0xfffffe004c74c690 > trap_pfault() at trap_pfault+0x62/frame 0xfffffe004c74c6e0 > trap() at trap+0x2ba/frame 0xfffffe004c74c7f0 > calltrap() at calltrap+0x8/frame 0xfffffe004c74c7f0 > --- trap 0xc, rip = 0xffffffff82282db3, rsp = 0xfffffe004c74c8c8, rbp = > 0xfffffe004c74c980 --- > futex_xchgl() at futex_xchgl+0x23/frame 0xfffffe004c74c980 > ia32_syscall() at ia32_syscall+0x29f/frame 0xfffffe004c74cab0 > int0x80_syscall_common() at int0x80_syscall_common+0x9c/frame 0x4000001 > Uptime: 7m29s > Dumping 411 out of 8056 MB:..4%..12%..24%..32%..43%..51%..63%..74%..82%..94% > Dump complete Post first 40 lines from the verbose dmesg boot of your machine. I have a guess what is going on, I need the dmesg to confirm. If my guess is correct, you can use a workaround by setting the "hw.cpu_stdext_disable=0x00100000" tunable at the loader prompt for now.