From owner-freebsd-current@freebsd.org Wed Aug 19 01:22:04 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 1A5FD3AD50A for ; Wed, 19 Aug 2020 01:22:04 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: from mail-io1-xd42.google.com (mail-io1-xd42.google.com [IPv6:2607:f8b0:4864:20::d42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BWVPQ6GJqz3y1y for ; Wed, 19 Aug 2020 01:22:02 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: by mail-io1-xd42.google.com with SMTP id z6so23134874iow.6 for ; Tue, 18 Aug 2020 18:22:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ii5nwrnyGtKq6hD9tzTSScn97OQOcHBTFSQAj2JEK10=; b=qei5uDYToBQOtI4dL4t6V3D9Kg4FsUa2z2ZXoR1QnDj1IGeWq6cwLfRDjxtJPuJEP8 cQU6iLez2qEF9zllj+m/744KuXZNGcS7Rl0LP4K99MV1R++kS7In9RdmPDuCK1Y/DpVc btj7ZEOxFSXGIQ0tVDTdtLeACb7eWpVBgiIWH0XOfmfvEbp5wN+Zy0lZ7m8KVTNbgFjA 48CdY5i1GHETfFt/IV3EaENrOvKdW1KlQqvn5tYizUfJeT+R68e7ULE1LmvG7LhJcWCE r3tQEFqluNklUlshoKUcv0XrmA4fEglL3TN7Z/FRjVn543mduUvSuleDPGA6ReppuWZ8 bk/Q== X-Gm-Message-State: AOAM533m4lM+vXmeMR2RL56SJ7txwL2BuJM15WROwPxDxI9VFAl3Pkjg MWKzxN6kDWaOwIIqHbxL+H3jnL+Et5umSWE166NnnHzC3tVP/g== X-Google-Smtp-Source: ABdhPJyZZZCUs4PgVJfTlnGlAUHv9DDnR/VmF4/vYsWFvIwrtkn8FZE6PEu5w+rKpm+jq2WRiiVXDeWlhlkuOwpqLG4= X-Received: by 2002:a05:6638:2595:: with SMTP id s21mr21341317jat.12.1597800121314; Tue, 18 Aug 2020 18:22:01 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a6b:6107:0:0:0:0:0 with HTTP; Tue, 18 Aug 2020 18:22:00 -0700 (PDT) From: "Lizbeth Mutterhunt, Ph.D" Date: Wed, 19 Aug 2020 03:22:00 +0200 Message-ID: Subject: funny thing with the drm0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4BWVPQ6GJqz3y1y X-Spamd-Bar: - X-Spamd-Result: default: False [-1.45 / 15.00]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::d42:from]; NEURAL_HAM_SHORT(-0.45)[-0.454]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] 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: Wed, 19 Aug 2020 01:22:04 -0000 After having had some near-death-experiences in Greece I'm back to my screens. As horizon arises, BSD gets up --- and if it is 3 a.m.! :-) But this is the experience with my Dell Vostro on 13 current: After finally recompiling the kernel with the drm-module inside and the trick of injecting the device IWNFW I get a *nice* message a bootup: Aug 19 02:51:10 current kernel: info: [drm] Initialized drm 1.1.0 20060810 Aug 19 02:51:10 current kernel: drmn0: on vgapci0 Aug 19 02:51:10 current kernel: info: [drm] Memory usable by graphics device = 2048M Aug 19 02:51:10 current kernel: info: [drm] MTRR allocation failed. Graphics performance may suffer. Aug 19 02:51:10 current kernel: intel_iicbb0 on drmn0 Aug 19 02:51:10 current kernel: iicbus0: on iicbb_nostop0 addr 0x1 Aug 19 02:51:10 current kernel: iic0: on iicbus0 Aug 19 02:51:10 current kernel: iicbus1: on intel_gmbus0 Aug 19 02:51:10 current kernel: iic1: on iicbus1 Aug 19 02:51:10 current kernel: intel_iicbb1 on drmn0 Aug 19 02:51:10 current kernel: iicbus2: on iicbb_nostop1 addr 0x12 Aug 19 02:51:10 current kernel: iic2: on iicbus2 Aug 19 02:51:10 current kernel: iicbus3: on intel_gmbus1 Aug 19 02:51:10 current kernel: iic3: on iicbus3 Aug 19 02:51:10 current kernel: intel_iicbb2 on drmn0 Aug 19 02:51:10 current kernel: iicbus4: on iicbb_nostop2 addr 0x12 Aug 19 02:51:10 current kernel: iic4: on iicbus4 Aug 19 02:51:10 current kernel: iicbus5: on intel_gmbus2 Aug 19 02:51:10 current kernel: iic5: on iicbus5 Aug 19 02:51:10 current kernel: intel_iicbb3 on drmn0 Aug 19 02:51:10 current kernel: iicbus6: on iicbb_nostop3 addr 0x12 Aug 19 02:51:10 current kernel: iic6: on iicbus6 Aug 19 02:51:10 current kernel: iicbus7: on intel_gmbus3 Aug 19 02:51:10 current kernel: iic7: on iicbus7 Aug 19 02:51:10 current kernel: intel_iicbb4 on drmn0 Aug 19 02:51:10 current kernel: iicbus8: on iicbb_nostop4 addr 0x12 Aug 19 02:51:10 current kernel: iic8: on iicbus8 Aug 19 02:51:10 current kernel: iicbus9: on intel_gmbus4 Aug 19 02:51:10 current kernel: iic9: on iicbus9 Aug 19 02:51:10 current kernel: intel_iicbb5 on drmn0 Aug 19 02:51:10 current kernel: iicbus10: on iicbb_nostop5 addr 0x12 And furthermore: Aug 19 02:51:10 current kernel: info: [drm] MSI enabled 1 message(s) Aug 19 02:51:10 current kernel: info: [drm] Supports vblank timestamp caching Rev 1 (10.10.201> Aug 19 02:51:10 current kernel: info: [drm] Driver supports precise vblank timestamp query. Aug 19 02:51:10 current kernel: intel_sdvo_ddc_proxy921920 on drmn0 Aug 19 02:51:10 current kernel: intel_sdvo_ddc_proxy921920: detached Aug 19 02:51:10 current kernel: drm_iic_dp_aux0 on drmn0 Aug 19 02:51:10 current kernel: drmn0: taking over the fictitious range 0xe0000000-0xf0000000 Aug 19 02:51:10 current kernel: info: [drm] Connector LVDS-1: get mode from tunables: Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.modes.LVDS-1 Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.default_mode Aug 19 02:51:10 current kernel: info: [drm] Connector VGA-1: get mode from tunables: Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.modes.VGA-1 Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.default_mode Aug 19 02:51:10 current kernel: info: [drm] Connector HDMI-A-1: get mode from tunables: Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.modes.HDMI-A-1 Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.default_mode Aug 19 02:51:10 current kernel: info: [drm] Connector DP-1: get mode from tunables: Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.modes.DP-1 Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.default_mode Aug 19 02:51:10 current kernel: fbd0 on drmn0 Aug 19 02:51:10 current kernel: WARNING: Device "fb" is Giant locked and may be deleted before> Aug 19 02:51:10 current kernel: VT: Replacing driver "vga" with new "fb". ug 19 02:51:10 current kernel: info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0 so far so good, quality of text in grafics 1368x1024 is perfectly initialized. but now, when starting xinit or lightdm or sddm or whatever I get a kernel panic: Dump header from device: /dev/ada0p4 Architecture: i386 Architecture Version: 4 Dump Length: 97792 Blocksize: 512 Compression: none Dumptime: 2020-08-19 02:49:00 +0200 Hostname: current Magic: FreeBSD Text Dump Version String: FreeBSD 13.0-CURRENT #2 r364350: Tue Aug 18 20:18:40 CEST 2020 root@current:/usr/obj/usr/src/i386.i386/sys/MIRANDA Panic String: vm_page_assert_xbusied: page 0x72bd024 not exclusive busy @ /usr/src/sys/vm/vm> Dump Parity: 2773167169 Bounds: 1 Dump Status: good /var/crash/vmcore.0 not found First thing I think is kern options: options WITNESS_SKIPSPIN options WITNESS I disabled device HYPERV but this can't be the reason, kern is being compiled with clang. To disable WITNESS would be one way I think but this can't be the yellw of the egg, isn't it? Another thing but I guess having nothing to do with bug above is on rather the end of startup: Aug 19 02:51:10 current savecore[1209]: reboot after panic: vm_page_assert_xbusied: page 0x72bd024 not exclusive busy @ /usr/src/sys/vm/vm_page.c:1609 Aug 19 02:51:10 current savecore[1209]: writing core to /var/crash/textdump.tar.1 Aug 19 02:51:10 current kernel: linsysfs: Aug 19 02:51:10 current kernel: Device busy Aug 19 02:51:10 current kernel: lock order reversal: Aug 19 02:51:10 current kernel: 1st 0x3121e870 ufs (ufs, lockmgr) @ /usr/src/sys/kern/vfs_mount.c:1008 Aug 19 02:51:10 current kernel: 2nd 0x3121e744 devfs (devfs, lockmgr) @ /usr/src/sys/kern/vfs_mount.c:1019 Aug 19 02:51:10 current kernel: lock order devfs -> ufs established at: Aug 19 02:51:10 current kernel: #0 0x1027cd5 at witness_checkorder+0x3c5 Aug 19 02:51:10 current kernel: #1 0xf9cca0 at lockmgr_lock_flags+0x140 Aug 19 02:51:10 current kernel: #2 0x123f697 at ffs_lock+0x57 Aug 19 02:51:10 current kernel: #3 0x13a1daf at VOP_LOCK1_APV+0x2f Aug 19 02:51:10 current kernel: #4 0x10a03df at _vn_lock+0x4f Aug 19 02:51:10 current kernel: #5 0x1082d89 at vfs_domount+0xc99 Aug 19 02:51:10 current kernel: #6 0x108178b at vfs_donmount+0x75b Aug 19 02:51:10 current kernel: #7 0x1085017 at kernel_mount+0x57 Aug 19 02:51:10 current kernel: #8 0x10871c2 at parse_mount+0x452 Aug 19 02:51:10 current kernel: #9 0x10859be at vfs_mountroot+0x4ce Aug 19 02:51:10 current kernel: #10 0xf65912 at start_init+0x22 Aug 19 02:51:10 current kernel: #11 0xf8aa18 at fork_exit+0x68 Aug 19 02:51:10 current kernel: #12 0xffc0340e at __stop_set_sysinit_set+0xd0a4199e Aug 19 02:51:10 current kernel: lock order ufs -> devfs attempted at: Aug 19 02:51:10 current kernel: #0 0x1028360 at witness_checkorder+0xa50 Aug 19 02:51:10 current kernel: #1 0xf9e486 at lockmgr_xlock+0x46 Aug 19 02:51:10 current kernel: #2 0x107b21a at vop_lock+0x6a Aug 19 02:51:10 current kernel: #3 0x13a1daf at VOP_LOCK1_APV+0x2f Aug 19 02:51:10 current kernel: #4 0x10a03df at _vn_lock+0x4f Aug 19 02:51:10 current kernel: #5 0x1082d89 at vfs_domount+0xc99 Aug 19 02:51:10 current kernel: #6 0x108178b at vfs_donmount+0x75b Aug 19 02:51:10 current kernel: #7 0x1080ffd at sys_nmount+0x5d Aug 19 02:51:10 current kernel: #8 0x138c895 at syscall+0x195 Aug 19 02:51:10 current kernel: #9 0xffc033f9 at __stop_set_sysinit_set+0xd0a41989 any ideas? Miranda does someone know how to fix it? Miranda