From owner-freebsd-bugs@freebsd.org Fri Jun 26 03:42:38 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5A39434C57C for ; Fri, 26 Jun 2020 03:42:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 49tN4Z1nGfz41RS for ; Fri, 26 Jun 2020 03:42:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 3D2AC34CD87; Fri, 26 Jun 2020 03:42:38 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3CEFD34CBA2 for ; Fri, 26 Jun 2020 03:42:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49tN4Z0yTHz41PK for ; Fri, 26 Jun 2020 03:42:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 1C107E407 for ; Fri, 26 Jun 2020 03:42:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 05Q3gbit055291 for ; Fri, 26 Jun 2020 03:42:37 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 05Q3gbkX055290 for bugs@FreeBSD.org; Fri, 26 Jun 2020 03:42:37 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 247552] FreeBSD virtual server fatal trap 12: page fault, supervisor read data, page not present Date: Fri, 26 Jun 2020 03:42:37 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: matthew.grice@anca.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2020 03:42:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247552 Bug ID: 247552 Summary: FreeBSD virtual server fatal trap 12: page fault, supervisor read data, page not present Product: Base System Version: 12.1-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: matthew.grice@anca.com I am running FreeBSD 12.1 with the latest update on a vmware vSphere virtual machine. The server is a web server running nginx, uwsgi and mariadb. Twice this morning the machine has had a kernel page fault and dumped core.= The message was as follows: Jun 26 12:58:41 ws-ag-au-17 kernel: Fatal trap 12: page fault while in kern= el mode Jun 26 12:58:41 ws-ag-au-17 kernel: cpuid =3D 1; apic id =3D 02 Jun 26 12:58:41 ws-ag-au-17 kernel: fault virtual address =3D 0x8 Jun 26 12:58:41 ws-ag-au-17 kernel: fault code =3D supervisor read= data, page not present Jun 26 12:58:41 ws-ag-au-17 kernel: instruction pointer =3D 0x20:0xffffffff80c658e0 Jun 26 12:58:41 ws-ag-au-17 kernel: stack pointer =3D 0x28:0xfffffe00005cf7a0 Jun 26 12:58:41 ws-ag-au-17 kernel: frame pointer =3D 0x28:0xfffffe00005cf7d0 Jun 26 12:58:41 ws-ag-au-17 kernel: code segment =3D base 0x= 0, limit 0xfffff, type 0x1b Jun 26 12:58:41 ws-ag-au-17 kernel: =3D DPL 0, pres 1, = long 1, def32 0, gran 1 Jun 26 12:58:41 ws-ag-au-17 kernel: processor eflags =3D interrupt enabl= ed, resume, IOPL =3D 0 Jun 26 12:58:41 ws-ag-au-17 kernel: current process =3D 1330 (n= ginx) Jun 26 12:58:41 ws-ag-au-17 kernel: trap number =3D 12 Jun 26 12:58:41 ws-ag-au-17 kernel: panic: page fault Jun 26 12:58:41 ws-ag-au-17 kernel: cpuid =3D 1 Jun 26 12:58:41 ws-ag-au-17 kernel: time =3D 1593140291 Jun 26 12:58:41 ws-ag-au-17 kernel: KDB: stack backtrace: Jun 26 12:58:41 ws-ag-au-17 kernel: #0 0xffffffff80c1d297 at kdb_backtrace+= 0x67 Jun 26 12:58:41 ws-ag-au-17 kernel: #1 0xffffffff80bd05cd at vpanic+0x19d Jun 26 12:58:41 ws-ag-au-17 kernel: #2 0xffffffff80bd0423 at panic+0x43 Jun 26 12:58:41 ws-ag-au-17 kernel: #3 0xffffffff810a7dcc at trap_fatal+0x3= 9c Jun 26 12:58:41 ws-ag-au-17 kernel: #4 0xffffffff810a7e19 at trap_pfault+0x= 49 Jun 26 12:58:41 ws-ag-au-17 kernel: #5 0xffffffff810a740f at trap+0x29f Jun 26 12:58:41 ws-ag-au-17 kernel: #6 0xffffffff81081a0c at calltrap+0x8 Jun 26 12:58:41 ws-ag-au-17 kernel: #7 0xffffffff80c64a01 at sbdestroy+0x41 Jun 26 12:58:41 ws-ag-au-17 kernel: #8 0xffffffff80c67225 at sofree+0x275 Jun 26 12:58:41 ws-ag-au-17 kernel: #9 0xffffffff80c67d77 at soclose+0x2f7 Jun 26 12:58:41 ws-ag-au-17 kernel: #10 0xffffffff80b7802a at _fdrop+0x1a Jun 26 12:58:41 ws-ag-au-17 kernel: #11 0xffffffff80b7b151 at closef+0x241 Jun 26 12:58:41 ws-ag-au-17 kernel: #12 0xffffffff80b78547 at closefp+0x97 Jun 26 12:58:41 ws-ag-au-17 kernel: #13 0xffffffff810a8984 at amd64_syscall+0x364 Jun 26 12:58:41 ws-ag-au-17 kernel: #14 0xffffffff81082330 at fast_syscall_common+0x101 Jun 26 12:58:41 ws-ag-au-17 kernel: Uptime: 1h33m41s Jun 26 12:58:41 ws-ag-au-17 kernel: Dumping 274 out of 4057 MB:..6%..12%..24%..36%..41%..53%..65%..71%..82%..94% Jun 26 12:58:41 ws-ag-au-17 kernel: Dump complete I have just enabled the writing of core dumps to disk and will post the dump when it happens again. The web server is usually being accessed when the panic occurs, but only lightly (maximum of two users at once). Memory usage is 500Mb out of 4GB and the dual core CPU does not seem to get above 10% while serving pages. At this point I cannot deliberately reproduce the bug as it seems to be spurious. --=20 You are receiving this mail because: You are the assignee for the bug.=