From owner-freebsd-current@freebsd.org Thu Aug 20 06:51:52 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 07C2A3B390A for ; Thu, 20 Aug 2020 06:51:52 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: from mail-wr1-x443.google.com (mail-wr1-x443.google.com [IPv6:2a00:1450:4864:20::443]) (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 4BXFgV6vQ7z40Bf for ; Thu, 20 Aug 2020 06:51:50 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: by mail-wr1-x443.google.com with SMTP id r15so915515wrp.13 for ; Wed, 19 Aug 2020 23:51:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=0glyVBu1+4kHk/AkGlJj4KYkI0qn7n0zTRcq1blNIDY=; b=GfqNzO6E8+4FXUGc077rTswWwVYRFJjOb/lr+P1r8Qn1XFLctl7f4FQN7AHFJFBLxT 9EvoTD5jUrsbWxj/y6jEfAX/uXCDCa+bmI5R7TKuUtPFecJu9CBFXuqRusSC/ficvwTg X35C/sPwPBBnuhJNllEDYQqNppgvoDaHCJIAoU62fb/f8bmxQG14K3JFoelIffoqRZxR bAyeExg5iDHezvetyLfI/mmIIPZGQz9QxLTAWLR5HfhSMC25q5S+ORIonArsxgPHhlb/ Rpq1wCViCet0GWxpCu7HqVocmGmDEeVkBTjBdia+swcmaxXyJy+A1d6pYguqRfU89a12 QXxw== X-Gm-Message-State: AOAM530F0cm/NbrwMgbyTI40sqFjQdFkCcrmjeww5QnZmbTgOGSN+M6h 8hqiNpXac+TCIERtL3mCwaByPrJeZYxgOOe1 X-Google-Smtp-Source: ABdhPJxVE33iOv7/mkixqR+c2moXlIYzETEaX+oTE5t3lB9U7+Ue8H/dV9wKOlDoDvNFsXFT64VRug== X-Received: by 2002:a17:906:1f8b:: with SMTP id t11mr1951444ejr.32.1597905809677; Wed, 19 Aug 2020 23:43:29 -0700 (PDT) Received: from [192.168.8.105] (213162072245.public.t-mobile.at. [213.162.72.245]) by smtp.gmail.com with ESMTPSA id h16sm815294ejf.120.2020.08.19.23.43.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 19 Aug 2020 23:43:29 -0700 (PDT) To: freebsd-current@freebsd.org From: "Vanbreukelingen Ltd." Subject: drn0 - crash dump not in /var/crash Message-ID: Date: Thu, 20 Aug 2020 08:43:28 +0200 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4BXFgV6vQ7z40Bf X-Spamd-Bar: +++++ X-Spamd-Result: default: False [5.40 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; GREYLIST(0.00)[pass,body]; R_SPF_ALLOW(0.00)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(0.00)[gmail.com,none]; RECEIVED_SPAMHAUS_PBL(0.00)[213.162.72.245:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; R_DKIM_ALLOW(0.00)[gmail.com:s=20161025]; RECEIVED_SPAMHAUS_CSS(4.00)[213.162.72.245:received]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.41)[0.412]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_SPAM_MEDIUM(0.99)[0.993]; RCPT_COUNT_ONE(0.00)[1]; BAD_REP_POLICIES(0.10)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::443:from]; RCVD_TLS_ALL(0.00)[]; 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: Thu, 20 Aug 2020 06:51:52 -0000 On Thursday, August 20, 2020 8:12:58 AM CEST Vanbreukelingen Ltd. wrote: > On Wednesday, August 19, 2020 9:43:21 AM CEST you wrote: > > On Wed, Aug 19, 2020 at 3:22 AM Lizbeth Mutterhunt, Ph.D < > > > > lizbethmutterhunt@gmail.com> wrote: > > > 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 > > > > This is not the way to do it. Modern hardware require drm-kmod from ports, > > or if you want the latest drm-devel-kmod. Then add /boot/modules/drm.ko > > and /boot/modules/i915kms.ko to kld_list in /etc/rc.conf wasn't yet finished (c [see] beyond), but I guess I have to disable the whole output with something like hw.*=1 or so. is it possible to make a bootlogo while VEBOSE output = 2 just for the reason some kids try to play with it. > > > device IWNFW >  doesn't install the 6000, btw --- probably can't find FW on device HAL. > > > Again, this is not needed, firmware is autoloaded on module load. Just add > > if_iwn to kld_list in /etc/rc.conf >  built of 15 hours of NanoBSD while finishing the nightly built someone was on Ctrl-C. So _i.w (installworld) is 5MB "thick" and doesn't boot at all but some reason tells me behind this system in system is something to beat beastie in killing KFC forks.  > > > > 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 > > > > Do you have  dumpdev="AUTO" in /etc/rc.conf ? > yes and the directory is /var/crash, but this is all I get as lack of insufficent memory of dump, it says. > > > > 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. > > > > Clang is the default since a long time. > depends on gcc++ development in 4D AIs. > > > > To disable WITNESS would be one way I think but this can't be the > > > yellw of the egg, isn't it? > > > > I use the GENERIC-NODEBUG kernel config which disables WITNESS for some > > performance improvements. > yup. we don't need another debugger. killing insects is murder but when getting better stuff I never resist to lance them. like housecats with flys. > > > 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 > > > > Hope this helps. > It does! > > > Best regards > > Andreas Nilsson > Yours, Miranda van Breukelingen