From owner-freebsd-current@freebsd.org Sun Sep 20 13:11:34 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 A75C63E08EF for ; Sun, 20 Sep 2020 13:11:34 +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 4BvSdK6sHfz4X9m for ; Sun, 20 Sep 2020 13:11:33 +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 1kJz7s-0000qs-1m; Sun, 20 Sep 2020 15:11:32 +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; Sun, 20 Sep 2020 15:11:31 +0200 Subject: Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X To: Konstantin Belousov CC: Hans Petter Selasky , monochrome , References: <69ff9432-fc8f-b0ab-8ad2-8e3daa77f8e1@twcny.rr.com> <1a88773b-d2fa-a790-c7e2-868d3884ba8b@twcny.rr.com> <865D6BF0-9F1E-4125-81D3-FB9A369FED8D@gwdg.de> <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> Reply-To: From: Rainer Hurling Message-ID: <0249197f-29f6-4df4-eb63-ca786aaea39d@gwdg.de> Date: Sun, 20 Sep 2020 15:11:26 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <20200920093814.GD94807@kib.kiev.ua> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.250.9.199] X-ClientProxiedBy: EXCMBX-23.um.gwdg.de (134.76.9.233) To EXCMBX-03.um.gwdg.de (134.76.9.218) X-Virus-Scanned: (clean) by clamav X-Rspamd-Queue-Id: 4BvSdK6sHfz4X9m X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.93 / 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.40)[-0.404]; 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)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[rhurlin]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_MEDIUM(-1.02)[-1.020]; NEURAL_HAM_LONG(-1.00)[-1.003]; MIME_GOOD(-0.10)[text/plain]; 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: Sun, 20 Sep 2020 13:11:34 -0000 Am 20.09.20 um 11:38 schrieb Konstantin Belousov: > On Sun, Sep 20, 2020 at 10:26:11AM +0200, Rainer Hurling wrote: >> Am 20.09.20 um 10:20 schrieb Hans Petter Selasky: >>> On 2020-09-20 10:05, Rainer Hurling wrote: >>>> Hi monochrome, >>>> >>>> back to keyboard, it tried newest CURRENT (r365920) on my box and even >>>> with newest sources the error occurs. >>>> >>>> After looking around somewhat more, I found some hints about Virtualbox >>>> kernel module having problems with r365488. Unfortunately, I am not able >>>> to find the thread again :( >>>> >>>> What seems to help as a workaround is to disable the loading of >>>> VirtualBox in /boot/loader.conf >>>> >>>> #vboxdrv_load="YES" >>>> >>>> and in /etc/rc.conf >>>> >>>> #vboxnet_enable="YES" >>>> #vboxguest_enable="YES" >>>> >>>> >>>> So probably, this page fault is not restricted to AMD Ryzen? >>>> >>> >>> Possibly you need to rebuild that kernel module. Maybe the FreeBSD >>> version was not bumped correctly. >>> >>> --HPS >>> >> >> Thanks for the hint. But I did rebuild all kernel modules before >> rebooting, in my case vbox*.ko, nvidia*.ko. > > Provide backtrace of the panic. > Hi Konstantin, Thanks for your response. After trying several ways to produce a core dump or a working kdb prompt without success, all I can offer is the following screen contents. I built a GENERIC kernel with debugging enabled, enable loading of vboxdrv via /boot/loader.conf and /etc/rc.conf as described above: [..snip..] procfs registered modulte_register_init: MOD_LOAD (tmpfs, 0xffffffff80caa060, 0xffffffff82520a70) error 17 Timecounters tick every 1.000 msec lo0: bpf attached vlan: initialized, using hash tables with chaining Fatal trap 12: page fault while in kernel mode cpuid = 31; apic id = 1f fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80ea889b stack pointer = 0x20:0xffffffff826017e0 frame pointer = 0x20:0xffffffff826017e0 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 0xffffffff82601490 vpanic() at vpanic+0x182/frame 0xffffffff826014e0 panic() at panic+0x43/frame 0xffffffff82601540 trap_fatal() at trap_fatal+0x387/frame 0xffffffff826015a0 trap_pfault() at trap_pfault+0x97/frame 0xffffffff82601600 calltrap() at calltrap+0x8/frame 0xffffffff82601710 --- trap 0xc, rip = 0xffffffff80ea889b, rsp = 0xffffffff826017e0, rbp = 0xffffffff826017e0 --- phys_pager_getpages() at phys_pager_getpages+0xb/frame 0xffffffff826017e0 vm_pager_get_pages() at vm_pager_get_pages+0x4f/frame 0xffffffff82601830 vm_fault() at vm_fault+0x5d6/frame 0xffffffff82601940 vm_map_wire_locked() at vm_map_wire_locked+0x3a6/framw 0xffffffff826019f0 vm_map_wire() at vm_map_wire+0x6b/frame 0xffffffff82601a20 rtR0MemObjFreeBSDAllocHelper() at rtR0MemObjFreeBSDAllocHelper+0xdc/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,0x10b5796(%rip9 db> The system freezes at this point, no core dump is generated ;) This does not happen without loading VBoxDrv. At least, the screen dump shows VBoxDrvFreeBSDModuleEvent(). I hope, this is of some help. Best regards, Rainer