From owner-freebsd-current@freebsd.org Thu Aug 20 14:58:31 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 1315F3C0845 for ; Thu, 20 Aug 2020 14:58:31 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) (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 4BXST21P71z4X5s for ; Thu, 20 Aug 2020 14:58:29 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: by mail-ej1-x62f.google.com with SMTP id g19so2853605ejc.9 for ; Thu, 20 Aug 2020 07:58:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=pB97/8yfOEltjQY0hbUna+S1SUQdIw6k/JK/6rEzlRI=; b=ED51rkHFVTqfFYchNjY8A/VVDpnqU1JM7m1Hd2ugk6kLJDRt4MRAbZoe3o3dQO2s+K nQxWw9lX+toJRV8Lw7B8yYjAX6dimlGihLy6UUxDCEl0NL21CUy6wY23v6duox2z3OdH 6cacobCPEIvXnPjmIrWLREby6SLiZRrL4QmYPsg1Cm0DrNAJ8ZUTYzESL4GpQOvV+70/ yNd3sOCVYlso2xTbeXkU4QmYw1thVTiwtyyJi+pkVWqhQrSTdOWnUubOyaHyrKzo/nxL VN4J6Dr62gjtSnqTOImbq9/yTf9ZoHTSOjBdDMvk55In2gBchwQSdYBYUEd5deOuuJ33 vR8Q== X-Gm-Message-State: AOAM530xrrECe1GJb1CjzZBC0s7d/LxPcRvKZkug/3sR8bgYUbWjSWLU RDmS1AikL4gDJbbxYjPkiRchMIqqzv8LFg== X-Google-Smtp-Source: ABdhPJwM4XoyBMXLdy/teRBOOQlFHhDZRgk9+vBdaewfLt+ZO8ChiBXcxz/c798mA5zuJ/q6MCr2ZQ== X-Received: by 2002:a17:906:c10d:: with SMTP id do13mr3596519ejc.109.1597935507234; Thu, 20 Aug 2020 07:58:27 -0700 (PDT) Received: from [192.168.8.105] (213162072245.public.t-mobile.at. [213.162.72.245]) by smtp.gmail.com with ESMTPSA id v13sm1636124ejq.59.2020.08.20.07.58.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 20 Aug 2020 07:58:26 -0700 (PDT) Subject: Re: funny thing with the drm0 To: Andreas Nilsson , freebsd-current@freebsd.org References: <3105850.kTNGU1mI0b@alice> From: "Vanbreukelingen Ltd." Message-ID: Date: Thu, 20 Aug 2020 16:58:25 +0200 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Rspamd-Queue-Id: 4BXST21P71z4X5s X-Spamd-Bar: ++++ X-Spamd-Result: default: False [4.97 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; GREYLIST(0.00)[pass,meta]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(0.00)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(0.00)[gmail.com,none]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; 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)[]; NEURAL_SPAM_SHORT(0.07)[0.073]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_SPAM_MEDIUM(0.90)[0.901]; BAD_REP_POLICIES(0.10)[]; RECEIVED_SPAMHAUS_PBL(0.00)[213.162.72.245:received]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::62f:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.33 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 14:58:31 -0000 On 2020-08-20 16:43, Andreas Nilsson wrote: > > > On Thu, Aug 20, 2020 at 2:48 PM 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. > tried it now: next kernel panic on lightdm and sddm makes a mouse in mouse pointer over a blank screen. the driver is initialised but hungs up like this: Dump header from device: /dev/ada0p4   Architecture: i386   Architecture Version: 4   Dump Length: 97792   Blocksize: 512   Compression: none   Dumptime: 2020-08-20 16:41:45 +0200   Hostname: current   Magic: FreeBSD Text Dump   Version String: FreeBSD 13.0-CURRENT #3 r364372: Wed Aug 19 07:54:57 CEST 2020     root@current:/usr/obj/usr/src/i386.i386/sys/MIRANDA *Panic String: vm_page_assert_xbusied: page 0x6f47814 not exclusive busy @ /usr/src/sys/vm/vm_page.c:1609** **  Dump Parity: 4227235352*   Bounds: 2   Dump Status: good > > > > 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 > > > Here I admit I was wrong, iwn handles it differently than iwm. The man > page lists 3 different firmware versions for the 6000 series, which > can be loaded from loader.conf When compiling DEVICE iwnfb into kern: mine (iwn6000g2bfw) doesn't load probably at bootup but with wpa_supplicant -d BSD -i wlan0 -c /etc/wpa_supplicant.conf it loads correctly and automatically assigns an IP. > built 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. > > Sounds like your swap device is to small. How big is it, and how much > memory do you have? > > > > > > 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. > > Nothing stops you from using gcc for compiling your programs. Clang is > just the default for the OS. > > > > > 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 > > > Best regards > Andreas Nilsson