From owner-freebsd-current@freebsd.org Tue Sep 22 16:45:39 2020 Return-Path: Delivered-To: freebsd-current@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 D2B843EF264 for ; Tue, 22 Sep 2020 16:45:39 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from gmailer.gwdg.de (gmailer.gwdg.de [134.76.11.17]) (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 4BwnHR1nJ5z4Hhr for ; Tue, 22 Sep 2020 16:45:38 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from excmbx-03.um.gwdg.de ([134.76.9.218] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (GWDG Mailer) (envelope-from ) id 1kKlQ9-0006ac-8k; Tue, 22 Sep 2020 18:45:37 +0200 Received: from krabat.raven.hur (10.250.9.199) by EXCMBX-03.um.gwdg.de (134.76.9.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2044.4; Tue, 22 Sep 2020 18:45:36 +0200 Subject: Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X From: Rainer Hurling To: Konstantin Belousov CC: Hans Petter Selasky , monochrome , Reply-To: References: <88af31d4-9ed9-172a-d48f-1780f19841e3@twcny.rr.com> <11d27d41-029a-d7f5-eccc-0ba3a3fcfe97@gwdg.de> <2bbfb4b3-92e9-b3ca-9c31-6c513cee2f2d@gwdg.de> <20200920093814.GD94807@kib.kiev.ua> <0249197f-29f6-4df4-eb63-ca786aaea39d@gwdg.de> <20200920195526.GH94807@kib.kiev.ua> <20200920200735.GJ94807@kib.kiev.ua> <1621df05-35a9-92b9-ffee-d93c17110d87@gwdg.de> <2673660d-3a6e-97c9-82a2-17b5ab8b987b@gwdg.de> <20200921221329.GD2570@kib.kiev.ua> <14418f1d-4b3a-7c4d-4cdd-030a00d86383@gwdg.de> Message-ID: <6c5cff68-23d5-c093-7404-a3fed341e5bb@gwdg.de> Date: Tue, 22 Sep 2020 18:45:25 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.3.0 MIME-Version: 1.0 In-Reply-To: <14418f1d-4b3a-7c4d-4cdd-030a00d86383@gwdg.de> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 8bit X-Originating-IP: [10.250.9.199] X-ClientProxiedBy: EXCMBX-12.um.gwdg.de (134.76.9.221) To EXCMBX-03.um.gwdg.de (134.76.9.218) X-Virus-Scanned: (clean) by clamav X-Rspamd-Queue-Id: 4BwnHR1nJ5z4Hhr X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.11 / 15.00]; HAS_REPLYTO(0.00)[rhurlin@freebsd.org]; HAS_XOIP(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:134.76.10.0/23]; RCVD_COUNT_THREE(0.00)[3]; RCVD_IN_DNSWL_MED(-0.20)[134.76.11.17:from]; NEURAL_HAM_SHORT(-0.56)[-0.560]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:680, ipnet:134.76.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.009]; FREEFALL_USER(0.00)[rhurlin]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.04)[-1.041]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; DMARC_NA(0.00)[gwdg.de]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[134.76.11.17:from]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 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: Tue, 22 Sep 2020 16:45:39 -0000 On 22.09.20 07:06, Rainer Hurling wrote: > Am 22.09.20 um 00:13 schrieb Konstantin Belousov: >> On Mon, Sep 21, 2020 at 08:57:46PM +0200, Rainer Hurling wrote: >>> Fatal trap 12: page fault while in kernel mode >>> cpuid = 31; apic id = 1f >>> fault virtual address   = 0x25407efa >> This address is very suspicious. >> >> I cannot claim it as the fact, but most likely cause for such garbage >> pointer value is mismatched ABI between kernel and module.  In other >> words, the module was built against headers from different kernel. > > Hmm, thanks for the pointer. I will double check this evening and > reporting back. > > Normally, this module should have been built and installed with the > kernel build. As I said, the module was rebuild and reinstalled with the kernel build, and I double checked, the module was the patched version. So the boot messages about the page fault should be created by the rebuild, patched module. > >> >>> fault code              = supervisor read data, page not present >>> instruction pointer     = 0x20:0xffffffff80ec0b63 >>> stack pointer           = 0x28:0xffffffff826018b0 >>> frame pointer           = 0x28:0xffffffff82601940 >>> 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         = 0 (swapper) >>> trap number             = 12 >>> panic: page fault >>> cpuid = 31 >>> time = 1 >>> KDB: stack backtrace: >>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >>> 0xffffffff82601560 >>> vpanic() at vpanic+0x182/frame 0xffffffff826015b0 >>> panic() at panic+0x43/frame 0xffffffff82601610 >>> trap_fatal() at trap_fatal+0x387/frame 0xffffffff82601670 >>> trap_pfault() at trap_pfault+0x97/frame 0xffffffff826016d0 >>> trap() at trap+0x2ab/frame 0xffffffff826017e0 >>> calltrap() at calltrap+0x8/frame 0xffffffff826017e0 >>> --- trap 0xc, rip = 0xffffffff80ec0b63, rsp = 0xffffffff826018b0, rbp = >>> 0xffffffff82601940 --- >>> vm_map_insert() at vm_map_insert+0x2f3/framw 0xffffffff82601940 >>> vm_map_find() at vm_map_find+0x4a4/frame 0xffffffff82601a00 >>> rtR0MemObjFreeBSDAllocHelper() at >>> rtR0MemObjFreeBSDAllocHelper+0x96/frame 0xffffffff82601a70 >>> rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame >>> 0xffffffff82601ac0 >>> supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60 >>> supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0 >>> VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame >>> 0xffffffff82601bf0 >>> module_register_init() at module_register_init+0xbd/frame >>> 0xffffffff82601c20 >>> mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70 >>> btext() at btext+0x2c >>> KDB: enter: panic >>> [ thread pid 0 tid 100000 ] >>> Stopped at      kdb_enter+0x37: movq    $0,0x10b5616(%rip) >>> db> >>> >>> >>> Perhaps this gives some more insight into the problem? I can't assess, >>> sorry.