From owner-freebsd-stable@freebsd.org Fri Dec 28 11:08:00 2018 Return-Path: Delivered-To: freebsd-stable@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 777231434EF6 for ; Fri, 28 Dec 2018 11:08:00 +0000 (UTC) (envelope-from jurij.kovacic@ocpea.com) Received: from mail-it1-x136.google.com (mail-it1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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 EEC6385E42 for ; Fri, 28 Dec 2018 11:07:58 +0000 (UTC) (envelope-from jurij.kovacic@ocpea.com) Received: by mail-it1-x136.google.com with SMTP id p197so26770534itp.0 for ; Fri, 28 Dec 2018 03:07:58 -0800 (PST) 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=bZDPOoVLXrsyXi5NPDurnbZJSvf/5qymgBNwImlM6gY=; b=khEWECJr8nROOfG8UlOBZmFeHwmAy1cudfp93QCT9Wta93GLarLrouTNSwyg8S+9We rmb/1qIYiY/YuOSPY0xiKlrJIof9lzneflPDi4xcqq8BX41zBNKlbJJzQw/Ak/gOHGfo j5gPqNcLF5wqd5leKL9lypPHRydiCIkNZAetxPmVWfRKus38ezOUY9IxxRl1h0jfv8rl bVovDRTa3He3YlrV6dUsxeMLHVKWlnfbUUR4Wz0c4Jyk8WGd/jdiC9ljoWOpWpUwouB5 xVwULMY8v0DTPc9CKtfKXP9tcKAm/PHDmPjiuYiu9QBoWPY2arsskNWmOuLbRfNvb+nG QVnw== X-Gm-Message-State: AJcUukeI2QDAgPDlYQ7/veN45uYHIp9RSXAxw7fZMDbQV3va7PxQnsSc FxO3eQMS81FPRrcZJsxx2E4rtcDZpRf8VopvWkSZD7u1v9aBfg== X-Google-Smtp-Source: AFSGD/U672RE1+6NP5OPSnksSfkBkNL8S76B4l9Ta25H9akZKXRUff3wUe2KCyMXFmVGZ9mrnjmTkfVUx2Y9xf/pNZ8= X-Received: by 2002:a24:2c50:: with SMTP id i77mr15411416iti.131.1545995278102; Fri, 28 Dec 2018 03:07:58 -0800 (PST) MIME-Version: 1.0 References: <67af7bf5-5fc7-a697-0055-d3518c93b86e@FreeBSD.org> In-Reply-To: <67af7bf5-5fc7-a697-0055-d3518c93b86e@FreeBSD.org> From: =?UTF-8?B?SnVyaWogS292YcSNacSN?= Date: Fri, 28 Dec 2018 12:07:46 +0100 Message-ID: Subject: Re: Kernel panic on 11.2-RELEASE-p7 To: Andriy Gapon Cc: freebsd-stable@freebsd.org X-Rspamd-Queue-Id: EEC6385E42 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.04 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[ocpea.com:s=google]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[ocpea.com:+]; MX_GOOD(-0.01)[cached: alt1.aspmx.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[6.3.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; DMARC_POLICY_ALLOW(-0.50)[ocpea.com,reject]; IP_SCORE(-2.20)[ip: (-7.52), ipnet: 2607:f8b0::/32(-1.87), asn: 15169(-1.51), country: US(-0.08)]; NEURAL_HAM_SHORT(-0.83)[-0.834,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Dec 2018 11:08:00 -0000 Hi Andriy, Thank you for your reply. Is what you are suggesting I build and install GENERIC kernel WITH debug symbols? I presume I just update the sources to 11.2 release and build and install the GENERIC kernel with added makeoptions DEBUG=3D-g ? Kind regards, Jurij On Fri, Dec 28, 2018 at 11:34 AM Andriy Gapon wrote: > On 28/12/2018 12:07, Jurij Kova=C4=8Di=C4=8D via freebsd-stable wrote: > > Dear list, > > > > This morning the server mentioned in my previous e-mail (Freebsd > > 11.2-RELEASE-p7 with GENERIC kernel, ZFS root) experienced another kern= el > > panic: > > > > Fatal trap 9: general protection fault while in kernel mode > > cpuid =3D 0; apic id =3D 00 > > instruction pointer =3D 0x20:0xffffffff82299013 > > stack pointer =3D 0x28:0xfffffe0352893ad0 > > frame pointer =3D 0x28:0xfffffe0352893b10 > > code segment =3D base 0x0, limit 0xfffff, type 0x1b > > =3D DPL 0, pres 1, long 1, def32 0, gran 1 > > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > > current process =3D 9 (dbuf_evict_thread) > > trap number =3D 9 > > panic: general protection fault > > cpuid =3D 0 > > KDB: stack backtrace: > > #0 0xffffffff80b3d577 at kdb_backtrace+0x67 > > #1 0xffffffff80af6b17 at vpanic+0x177 > > #2 0xffffffff80af6993 at panic+0x43 > > #3 0xffffffff80f77fdf at trap_fatal+0x35f > > #4 0xffffffff80f7759e at trap+0x5e > > #5 0xffffffff80f5808c at calltrap+0x8 > > #6 0xffffffff8229c049 at dbuf_evict_one+0xe9 > > #7 0xffffffff82297a15 at dbuf_evict_thread+0x1a5 > > #8 0xffffffff80aba093 at fork_exit+0x83 > > #9 0xffffffff80f58fae at fork_trampoline+0xe > > > > I have used the "crashinfo" utility to (again) generate the text file > which > > is available at this URL: http://www.ocpea.com/dump/core-2.txt > > > > This is useless because you do not have debug symbols for the kernel. > > > Does anyone have any idea how we can go about discovering the cause for > > this? We would appreciate any suggestion ... > > > > -- > Andriy Gapon >