From owner-freebsd-current@freebsd.org Sat Aug 4 12:12:55 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 7BF751068AF1 for ; Sat, 4 Aug 2018 12:12:55 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (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 EC6627272A for ; Sat, 4 Aug 2018 12:12:54 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr1-x433.google.com with SMTP id g6-v6so7886607wrp.0 for ; Sat, 04 Aug 2018 05:12:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HGpw8Uzep10h2Unw6uCxHBzD+Yfp14+jbcgoudC5ixA=; b=haqTBP0AGh662juDYMei60Ojv6x7Ya67nD7Y84NSNJqfst1AeSd/DEKdpHPZEZoqxX OA/gobDuJx/LMPM7sXrB2KqNG+WcGWe0lWDaXkXfLiHyMT/jIeyYBSySYSasqqp6+VpR T4p+nlwnbHrmRjUEkVc6Ak9HmrecChA/BkrbR0XT+KVka7oTFNptTA0x0kWeUvK+P0V8 UTDsnnV2SQIEHZG2tmLKhpB2LKSyKoCpH9QDhO2BYJgr1/26HypIcqYgAxMHInwhVlGs Fzej78XPUZImPI1RIxxoDkgNvv8XagMdEuxX6swgR0LujCC8SbN5oxYC7L/To7wuIsbO af3g== 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=HGpw8Uzep10h2Unw6uCxHBzD+Yfp14+jbcgoudC5ixA=; b=otv7D5nbN/x4BpWsZgddUcVb60+Zgsfj3NtFphiGOf0ZuCBAknaTFytRoqbvLj9pDF xf9c68bW5yknZvznWxnRbyt/tOFHZzJBO/fyzfV3yTS+cfRwvpKHcI+i4MFylUmrp6aA L5W7+htBKDU4iOjcJ/XMPKqX4GBvqp1pW5F+uOnnQXu7WjJTKyFStKvPJM2NJhyTsRm+ 2N+u/8d2jnFo6rnByecshSeJsVJxQoiGSqkWGdZeYd3mkyt3BHDivlL3+51IcdcFPby6 SockB22IsphaULd5tBWCcIdIZay2a6Qrup0LTkDk3UVQ720jvo5gt365zd5lbCHK+V5N yZnw== X-Gm-Message-State: AOUpUlFi7cczFndZV4buerorqIvgLmecIwE3s4xMAcXsZkgxIUO/r0oT KBE03umEnFD45i+pZnGtmh1jhc7G7RmDExnEqGA= X-Google-Smtp-Source: AAOMgpfWZ2Yt9xolPwEp7scWKuYFg6aV9wSQlI3Io93A2q9/eDN6I2IfdIEvZM5kXyIFtIcCBDXcp4Asv5mlZBAjGUE= X-Received: by 2002:a5d:40c4:: with SMTP id b4-v6mr4499010wrq.133.1533384773636; Sat, 04 Aug 2018 05:12:53 -0700 (PDT) MIME-Version: 1.0 References: <20180803204250.GE6049@kib.kiev.ua> In-Reply-To: <20180803204250.GE6049@kib.kiev.ua> From: Johannes Lundberg Date: Sat, 4 Aug 2018 13:12:17 +0100 Message-ID: Subject: Re: Linux process causes kernel panic To: Konstantin Belousov Cc: freebsd-current 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: Sat, 04 Aug 2018 12:12:55 -0000 On Fri, Aug 3, 2018 at 9:43 PM Konstantin Belousov wrote: > 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. > No panic over night with that tunable so it seems you're on the right track.