From owner-freebsd-current@freebsd.org Sun Sep 15 01:17:28 2019 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 7C5D2D5F19 for ; Sun, 15 Sep 2019 01:17:28 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46WBLc2fbcz3DCv; Sun, 15 Sep 2019 01:17:28 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (unknown [76.212.85.177]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: truckman) by smtp.freebsd.org (Postfix) with ESMTPSA id 965151C6F0; Sun, 15 Sep 2019 01:17:27 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Date: Sat, 14 Sep 2019 18:17:25 -0700 (PDT) From: Don Lewis Subject: Re: spurious out of swap kills To: Konstantin Belousov cc: Mark Johnston , FreeBSD Current , kib@freebsd.org In-Reply-To: <20190913055332.GN2559@kib.kiev.ua> Message-ID: References: <20190913000635.GG8397@raichu> <20190913055332.GN2559@kib.kiev.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 15 Sep 2019 01:17:28 -0000 On 13 Sep, Konstantin Belousov wrote: > On Thu, Sep 12, 2019 at 05:42:00PM -0700, Don Lewis wrote: >> On 12 Sep, Mark Johnston wrote: >> > On Thu, Sep 12, 2019 at 04:00:17PM -0700, Don Lewis wrote: >> >> My poudriere machine is running 13.0-CURRENT and gets updated to the >> >> latest version of -CURRENT periodically. At least in the last week or >> >> so, I've been seeing occasional port build failures when building my >> >> default set of ports, and I finally had some time to do some >> >> investigation. >> >> >> >> It's a 16-thread Ryzen machine, with 64 GB of RAM and 40 GB of swap. >> >> Poudriere is configured with >> >> USE_TMPFS="wrkdir data localbase" >> >> and I have >> >> .if ${.CURDIR:M*/www/chromium} >> >> MAKE_JOBS_NUMBER=16 >> >> .else >> >> MAKE_JOBS_NUMBER=7 >> >> .endif >> >> in /usr/local/etc/poudriere.d/make.conf, since this gives me the best >> >> overall build time for my set of ports. This hits memory pretty hard, >> >> especially when chromium, firefox, libreoffice, and both versions of >> >> openoffice are all building at the same time. During this time, the >> >> amount of space consumed by tmpfs for /wrkdir gets large when building >> >> these large ports. There is not enough RAM to hold it all, so some of >> >> the older data spills over to swap. Swap usage peaks at about 10 GB, >> >> leaving about 30 GB of free swap. Nevertheless, I see these errors, >> >> with rustc being the usual victim: >> >> >> >> Sep 11 23:21:43 zipper kernel: pid 16581 (rustc), jid 43, uid 65534, was killed: out of swap space >> >> Sep 12 02:48:23 zipper kernel: pid 1209 (rustc), jid 62, uid 65534, was killed: out of swap space >> >> >> >> Top shows the size of rustc being about 2 GB, so I doubt that it >> >> suddenly needs an additional 30 GB of swap. >> >> >> >> I'm wondering if there might be a transient kmem shortage that is >> >> causing a malloc(..., M_NOWAIT) failure in the swap allocation path >> >> that is the cause of the problem. >> > >> > Perhaps this is a consequence of r351114? To confirm this, you might >> > try increasing the value of vm.pfault_oom_wait to a larger value, like >> > 20 or 30, and see if the OOM kills still occur. >> >> I wonder if increasing vm.pfault_oom_attempts might also be a good idea. > If you are sure that you cannot exhaust your swap space, set > attempts to -1 to disable this mechanism. I had success just by increasing vm.pfault_oom_attempts from 3 to 10. > Basically, page fault handler waits for vm.pfault_oom_wait * > vm.pfault_oom_attempts for a page allocation before killing the process. > Default is 30 secs, and if you cannot get a page for 30 secs, there is > something very wrong with the machine. There is nothing really wrong with the machine. The load is just high. Probably pretty bad for interactivity, but throughput is just fine, with CPU %idle pretty much pegged at zero the whole time. I kept an eye on the machine for a while during a run with the new tuning. Most of the time, free memory bounced between 2 and 4 GB, with little page out activity. There were about 60 running processes, most of which were writing to 16 tmpfs filesystems. Sometimes free memory dropped into the 1 to 2 GB range and pageouts spiked. This condition could persist for 30 seconds or more, which is probably the reason for the OOM kills with the default tuning. I sometimes saw free memory drop below 1 GB. The lowest I aaw was 470 MB. I'm guessing that this code fails page allocation when free memmory is below some threshold to avoid potential deadlocks. Swap on this machine consists of a gmirror pair of partitions on a pair of 1 TB WD Green drives, that are now on their third computer. The remainder of the space of the drives are used for the mirrored vdev for the system zpool. Not terribly fast, even in the days when these drives were new, but mostly fast enough to keep all the CPU cores busy other than during poudriere startup and wind down when there isn't enough work to go around. I could spend money on faster storage, but it really wouldn't decrease poudriere run time much. It probably is close enough to the limit that I would need to improve storage speed if I swapped the Ryzen for a Threadripper. From owner-freebsd-current@freebsd.org Sun Sep 15 01:23:11 2019 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 E9B3AD68A7 for ; Sun, 15 Sep 2019 01:23:11 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46WBTC5666z3Dr2; Sun, 15 Sep 2019 01:23:11 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (unknown [76.212.85.177]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: truckman) by smtp.freebsd.org (Postfix) with ESMTPSA id 2C29D1C80A; Sun, 15 Sep 2019 01:23:11 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Date: Sat, 14 Sep 2019 18:23:09 -0700 (PDT) From: Don Lewis Subject: Re: spurious out of swap kills To: Mark Millard cc: FreeBSD Current In-Reply-To: <9A2342FC-D168-485A-9918-0109F9CD1646@yahoo.com> Message-ID: References: <9A2342FC-D168-485A-9918-0109F9CD1646@yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 15 Sep 2019 01:23:12 -0000 On 13 Sep, Mark Millard wrote: > Don Lewis truckman at FreeBSD.org wrote on > Thu Sep 12 23:00:19 UTC 2019 : > > . . . >> Nevertheless, I see these errors, >> with rustc being the usual victim: >> >> Sep 11 23:21:43 zipper kernel: pid 16581 (rustc), jid 43, uid 65534, was killed: out of swap space >> Sep 12 02:48:23 zipper kernel: pid 1209 (rustc), jid 62, uid 65534, was killed: out of swap space > . . . > > Unfortunately, the wording of this type of message is a misnomer for > what drives the kills: it is actually driven by being unable to gain > more free memory but FreeBSD will not swap-out processes that stay > runnable (or are running), only ones that are waiting. Even a single > process that stays runnable and keeps lots of RAM in the active > category can lead to kills when swap is unused or little used. So the > kill-behavior is very workload dependent. > > Real "out of swap" conditions tend to also have messages > similar to: > > Aug 5 17:54:01 sentinel kernel: swap_pager_getswapspace(32): failed > > If you are not seeing such messages, then it is likely that > the mount of swap space still free is not the actual thing > driving the kills. > > Are you seeing "swap_pager_getswapspace(32): failed" messages? > > (It used to be that the system simply leaves the dirty pages in > memory when a swap_pager_getswapspace failed message is produced. > Of itself, it did not cause a kill. I do not know about now.) I'm only getting the "out of swap" error. Yes, it is misleading because there are still tens of GB of free swap. From owner-freebsd-current@freebsd.org Sun Sep 15 01:31:18 2019 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 7B731D7323 for ; Sun, 15 Sep 2019 01:31:18 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46WBfZ2jwcz3FQm; Sun, 15 Sep 2019 01:31:18 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (unknown [76.212.85.177]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: truckman) by smtp.freebsd.org (Postfix) with ESMTPSA id C1F061C925; Sun, 15 Sep 2019 01:31:17 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Date: Sat, 14 Sep 2019 18:31:16 -0700 (PDT) From: Don Lewis Subject: Re: poudriere, swap full and top says memory is free ? To: John-Mark Gurney cc: Kurt Jaeger , FreeBSD Current In-Reply-To: <20190914182857.GM96402@funkthat.com> Message-ID: References: <20190914173805.GC2863@home.opsec.eu> <20190914182857.GM96402@funkthat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 15 Sep 2019 01:31:18 -0000 On 14 Sep, John-Mark Gurney wrote: > Kurt Jaeger wrote this message on Sat, Sep 14, 2019 at 19:38 +0200: >> - a poudriere build >> - of a list of ports >> - on 12.0-RELEASE-p10 >> - on a 4 core+4 hyperthreads CPU, an Intel(R) Xeon(R) CPU E3-1230 v6 >> @ 3.50GHz >> - with 32 GB RAM >> - zpool with 2x 500 GB SSDs as a mirror >> >> and right now, this can be seen: >> >> last pid: 90922; load averages: 5.02, 5.14, 5.73 up 0+03:53:08 19:31:05 >> 82 processes: 6 running, 76 sleeping >> CPU: 60.6% user, 0.0% nice, 2.1% system, 0.0% interrupt, 37.3% idle >> Mem: 4598M Active, 2854M Inact, 11G Laundry, 6409M Wired, 6375M Free >> ARC: 3850M Total, 1721M MFU, 2090M MRU, 665K Anon, 19M Header, 19M Other >> 3406M Compressed, 3942M Uncompressed, 1.16:1 Ratio >> Swap: 18G Total, 18G Used, 396K Free, 99% Inuse, 68K In >> >> So: Swap is full, approx. 6 GB memory is reported as free. >> >> This is surprising. Can I somehow tune this in any way, so that >> the memory available is used for the build ? Or is the problem somewhere >> else ? > > Are you sure that this hasn't just recently completed a large link of > something like Chromium? There are known to be compiles that can take > many GB's of memory and if they recently exited, there hasn't been time > to swap stuff back in... or is this the steady state over the entire > compile? This is sort of an odd case. I suspect that swap filled and then a process that was using a large amount of memory but no swap exited or was killed. That freed a bunch of memory, but no swap. I'm pretty sure that when a memory page is paged back in from swap, that the copy in swap is retained and not deallocated. Under memory pressure, that allowed the page to be stolen without having to write it back out to swap again, unless it was re-dirtied in the meantime. From owner-freebsd-current@freebsd.org Sun Sep 15 07:47:59 2019 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 A4B77E4D54 for ; Sun, 15 Sep 2019 07:47:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46WM1B3H7Vz456B for ; Sun, 15 Sep 2019 07:47:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x82f.google.com with SMTP id j31so12555409qta.5 for ; Sun, 15 Sep 2019 00:47:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=T/uEizpiW/JhsT/BjjfNwBQUM3UEP84ZMM+c/7WmbLQ=; b=mCdyxk2/zf7HBZthAPThq26BohzJrRqbJeUBoCyhWe/6ul1j73Cq2aaT+UYZpKyDae tBtHFJoac3Mo5JK+px4wdnjU6AYJpIVbByCDRIH4ZUd/AsI0FXKFsXdg7Q/eWFT3ipPS N5SqxGG0veSRXHgXi/dOe67+8auz8Q/F3LyMYxqlK2x+idRn3+GChi66fgwGZMRu+rEd rPNICAahyXe3QIjKQ4NO4XLiylTqeKa2oLlUKZCHc6GHDJzWaYaZdSNrJke+NYbxokXB /CEbkoHWyvcMLHgn+60nYMd8SgfcyCxg2KRNz0jr1r9sYY5EwLsrZ/l8H3SJ8rCAbAQF EeFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=T/uEizpiW/JhsT/BjjfNwBQUM3UEP84ZMM+c/7WmbLQ=; b=qR4JCwd+96lCyxq3MK+nTVPFixZHLwSoIeyYVCkWMkhb4v55H0KYN2Akg55WfO9+9f ELGIiZoADCnNwgwdBndcX540ekHzbMI5dYxT397KMHoXsMHBbm2eCWI/4VC3nc3K+CpG WG0x3Nk7TKlhro3F0ZTtaam8H32ED6mTuOafrv/PnMHI8eqC4SNenDrIbzqL/vKISbmD Dxf49xwYljOl3nFBccodNvWbAWzZHGeDv38IIwErSznxiUY7bFQChqXNPLk4QMp3ZuZe p2uGNFfE5MtM4SywmGA/lw09Y+DFy+O6gNC7M1fpDOzkV3BXZ4yMVB0Ufa9CBPZ9HRtv m7hA== X-Gm-Message-State: APjAAAUOLZtsSxDNsLIj/3kBMkfKo1ojxXkiViuzftjA7AASxDmpK9ko leTxTwCwEpZR5VrVzfPjfaN93dYfF9ZPMDCw+fnB0g== X-Google-Smtp-Source: APXvYqxkEfVNF7lqiAr0VMsIAY9hVuZp6ZN4cIXX1pSm2USMfSQUyIhgnaYdNn9LUa0AKnCsGv0AdaLBGl1vSWvCdug= X-Received: by 2002:ac8:1208:: with SMTP id x8mr10880173qti.32.1568533677091; Sun, 15 Sep 2019 00:47:57 -0700 (PDT) MIME-Version: 1.0 References: <20190913000635.GG8397@raichu> <20190913055332.GN2559@kib.kiev.ua> In-Reply-To: From: Warner Losh Date: Sun, 15 Sep 2019 01:47:44 -0600 Message-ID: Subject: Re: spurious out of swap kills To: Don Lewis Cc: Konstantin Belousov , Mark Johnston , FreeBSD Current , kib@freebsd.org X-Rspamd-Queue-Id: 46WM1B3H7Vz456B X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=mCdyxk2/; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::82f) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.87 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; URI_COUNT_ODD(1.00)[3]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[f.2.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.87)[ip: (-9.36), ipnet: 2607:f8b0::/32(-2.70), asn: 15169(-2.24), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; FREEMAIL_CC(0.00)[gmail.com] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 15 Sep 2019 07:47:59 -0000 On Sun, Sep 15, 2019, 3:17 AM Don Lewis wrote: > On 13 Sep, Konstantin Belousov wrote: > > On Thu, Sep 12, 2019 at 05:42:00PM -0700, Don Lewis wrote: > >> On 12 Sep, Mark Johnston wrote: > >> > On Thu, Sep 12, 2019 at 04:00:17PM -0700, Don Lewis wrote: > >> >> My poudriere machine is running 13.0-CURRENT and gets updated to the > >> >> latest version of -CURRENT periodically. At least in the last week > or > >> >> so, I've been seeing occasional port build failures when building my > >> >> default set of ports, and I finally had some time to do some > >> >> investigation. > >> >> > >> >> It's a 16-thread Ryzen machine, with 64 GB of RAM and 40 GB of swap. > >> >> Poudriere is configured with > >> >> USE_TMPFS="wrkdir data localbase" > >> >> and I have > >> >> .if ${.CURDIR:M*/www/chromium} > >> >> MAKE_JOBS_NUMBER=16 > >> >> .else > >> >> MAKE_JOBS_NUMBER=7 > >> >> .endif > >> >> in /usr/local/etc/poudriere.d/make.conf, since this gives me the best > >> >> overall build time for my set of ports. This hits memory pretty > hard, > >> >> especially when chromium, firefox, libreoffice, and both versions of > >> >> openoffice are all building at the same time. During this time, the > >> >> amount of space consumed by tmpfs for /wrkdir gets large when > building > >> >> these large ports. There is not enough RAM to hold it all, so some > of > >> >> the older data spills over to swap. Swap usage peaks at about 10 GB, > >> >> leaving about 30 GB of free swap. Nevertheless, I see these errors, > >> >> with rustc being the usual victim: > >> >> > >> >> Sep 11 23:21:43 zipper kernel: pid 16581 (rustc), jid 43, uid 65534, > was killed: out of swap space > >> >> Sep 12 02:48:23 zipper kernel: pid 1209 (rustc), jid 62, uid 65534, > was killed: out of swap space > >> >> > >> >> Top shows the size of rustc being about 2 GB, so I doubt that it > >> >> suddenly needs an additional 30 GB of swap. > >> >> > >> >> I'm wondering if there might be a transient kmem shortage that is > >> >> causing a malloc(..., M_NOWAIT) failure in the swap allocation path > >> >> that is the cause of the problem. > >> > > >> > Perhaps this is a consequence of r351114? To confirm this, you might > >> > try increasing the value of vm.pfault_oom_wait to a larger value, like > >> > 20 or 30, and see if the OOM kills still occur. > >> > >> I wonder if increasing vm.pfault_oom_attempts might also be a good idea. > > If you are sure that you cannot exhaust your swap space, set > > attempts to -1 to disable this mechanism. > > I had success just by increasing vm.pfault_oom_attempts from 3 to 10. > > > Basically, page fault handler waits for vm.pfault_oom_wait * > > vm.pfault_oom_attempts for a page allocation before killing the process. > > Default is 30 secs, and if you cannot get a page for 30 secs, there is > > something very wrong with the machine. > > There is nothing really wrong with the machine. The load is just high. > Probably pretty bad for interactivity, but throughput is just fine, with > CPU %idle pretty much pegged at zero the whole time. > And many low quality SD cards have extreme write performance cliffs once whatever free NAND pages in the card are exhausted. Especially if there is high fragmentation of its append store and a high write amp kicks in. Swap traffic tends to trigger it because its writes are random and they may be smaller than the internal page size these days... seconds or 10s of seconds in these scenarios are not uncommon... this is why high quality band or spinning media or SSDs make the problem go away. Warner I kept an eye on the machine for a while during a run with the new > tuning. Most of the time, free memory bounced between 2 and 4 GB, with > little page out activity. There were about 60 running processes, most > of which were writing to 16 tmpfs filesystems. Sometimes free memory > dropped into the 1 to 2 GB range and pageouts spiked. This condition > could persist for 30 seconds or more, which is probably the reason for > the OOM kills with the default tuning. I sometimes saw free memory drop > below 1 GB. The lowest I aaw was 470 MB. I'm guessing that this code > fails page allocation when free memmory is below some threshold to avoid > potential deadlocks. > > Swap on this machine consists of a gmirror pair of partitions on a pair > of 1 TB WD Green drives, that are now on their third computer. The > remainder of the space of the drives are used for the mirrored vdev for > the system zpool. Not terribly fast, even in the days when these drives > were new, but mostly fast enough to keep all the CPU cores busy other > than during poudriere startup and wind down when there isn't enough work > to go around. I could spend money on faster storage, but it really > wouldn't decrease poudriere run time much. It probably is close enough > to the limit that I would need to improve storage speed if I swapped the > Ryzen for a Threadripper. > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Sun Sep 15 07:49:04 2019 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 CE630E4EE2 for ; Sun, 15 Sep 2019 07:49:04 +0000 (UTC) (envelope-from freebsd-current@sentry.org) Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "shadow.sentry.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46WM2R2Qpfz45FB for ; Sun, 15 Sep 2019 07:49:02 +0000 (UTC) (envelope-from freebsd-current@sentry.org) Received: from shadow.sentry.org (localhost [127.0.0.1]) by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id x8F7mpp7090548 for ; Sun, 15 Sep 2019 17:48:51 +1000 (AEST) (envelope-from freebsd-current@sentry.org) Subject: Re: poudriere, swap full and top says memory is free ? To: FreeBSD Current References: <20190914173805.GC2863@home.opsec.eu> <20190914182857.GM96402@funkthat.com> From: Trev Message-ID: Date: Sun, 15 Sep 2019 17:48:51 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (shadow.sentry.org [0.0.0.0]); Sun, 15 Sep 2019 17:48:51 +1000 (AEST) X-Rspamd-Queue-Id: 46WM2R2Qpfz45FB X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd-current@sentry.org designates 210.8.237.106 as permitted sender) smtp.mailfrom=freebsd-current@sentry.org X-Spamd-Result: default: False [-4.22 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; DMARC_NA(0.00)[sentry.org]; IP_SCORE(-2.92)[ip: (-8.23), ipnet: 210.8.0.0/15(-4.18), asn: 2764(-2.18), country: AU(0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:2764, ipnet:210.8.0.0/15, country:AU]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 15 Sep 2019 07:49:04 -0000 Don Lewis wrote on 15/09/2019 11:31: > On 14 Sep, John-Mark Gurney wrote: >> Kurt Jaeger wrote this message on Sat, Sep 14, 2019 at 19:38 +0200: >>> - a poudriere build >>> - of a list of ports >>> - on 12.0-RELEASE-p10 >>> - on a 4 core+4 hyperthreads CPU, an Intel(R) Xeon(R) CPU E3-1230 v6 >>> @ 3.50GHz >>> - with 32 GB RAM >>> - zpool with 2x 500 GB SSDs as a mirror >>> >>> and right now, this can be seen: >>> >>> last pid: 90922; load averages: 5.02, 5.14, 5.73 up 0+03:53:08 19:31:05 >>> 82 processes: 6 running, 76 sleeping >>> CPU: 60.6% user, 0.0% nice, 2.1% system, 0.0% interrupt, 37.3% idle >>> Mem: 4598M Active, 2854M Inact, 11G Laundry, 6409M Wired, 6375M Free >>> ARC: 3850M Total, 1721M MFU, 2090M MRU, 665K Anon, 19M Header, 19M Other >>> 3406M Compressed, 3942M Uncompressed, 1.16:1 Ratio >>> Swap: 18G Total, 18G Used, 396K Free, 99% Inuse, 68K In >>> >>> So: Swap is full, approx. 6 GB memory is reported as free. >>> >>> This is surprising. Can I somehow tune this in any way, so that >>> the memory available is used for the build ? Or is the problem somewhere >>> else ? >> >> Are you sure that this hasn't just recently completed a large link of >> something like Chromium? There are known to be compiles that can take >> many GB's of memory and if they recently exited, there hasn't been time >> to swap stuff back in... or is this the steady state over the entire >> compile? > > This is sort of an odd case. I suspect that swap filled and then a > process that was using a large amount of memory but no swap exited or > was killed. That freed a bunch of memory, but no swap. > > I'm pretty sure that when a memory page is paged back in from swap, that > the copy in swap is retained and not deallocated. Under memory > pressure, that allowed the page to be stolen without having to write it > back out to swap again, unless it was re-dirtied in the meantime. Don't forget swap fragmentation could conceivably cause oom even if there is swap appearing to be available. sysctl vm.swap_fragmentation is interesting. From owner-freebsd-current@freebsd.org Sun Sep 15 17:20:14 2019 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 B05EFF2670 for ; Sun, 15 Sep 2019 17:20:14 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46WbjV3L0pz4X2p; Sun, 15 Sep 2019 17:20:14 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x8FHK0Pr027171 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 15 Sep 2019 20:20:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x8FHK0Pr027171 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x8FHK0EG027170; Sun, 15 Sep 2019 20:20:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 15 Sep 2019 20:19:59 +0300 From: Konstantin Belousov To: Don Lewis Cc: Mark Johnston , FreeBSD Current , kib@freebsd.org Subject: Re: spurious out of swap kills Message-ID: <20190915171959.GR2559@kib.kiev.ua> References: <20190913000635.GG8397@raichu> <20190913055332.GN2559@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-Rspamd-Queue-Id: 46WbjV3L0pz4X2p X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.99 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.995,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 15 Sep 2019 17:20:14 -0000 On Sat, Sep 14, 2019 at 06:17:25PM -0700, Don Lewis wrote: > On 13 Sep, Konstantin Belousov wrote: > > On Thu, Sep 12, 2019 at 05:42:00PM -0700, Don Lewis wrote: > >> On 12 Sep, Mark Johnston wrote: > >> > On Thu, Sep 12, 2019 at 04:00:17PM -0700, Don Lewis wrote: > >> >> My poudriere machine is running 13.0-CURRENT and gets updated to the > >> >> latest version of -CURRENT periodically. At least in the last week or > >> >> so, I've been seeing occasional port build failures when building my > >> >> default set of ports, and I finally had some time to do some > >> >> investigation. > >> >> > >> >> It's a 16-thread Ryzen machine, with 64 GB of RAM and 40 GB of swap. > >> >> Poudriere is configured with > >> >> USE_TMPFS="wrkdir data localbase" > >> >> and I have > >> >> .if ${.CURDIR:M*/www/chromium} > >> >> MAKE_JOBS_NUMBER=16 > >> >> .else > >> >> MAKE_JOBS_NUMBER=7 > >> >> .endif > >> >> in /usr/local/etc/poudriere.d/make.conf, since this gives me the best > >> >> overall build time for my set of ports. This hits memory pretty hard, > >> >> especially when chromium, firefox, libreoffice, and both versions of > >> >> openoffice are all building at the same time. During this time, the > >> >> amount of space consumed by tmpfs for /wrkdir gets large when building > >> >> these large ports. There is not enough RAM to hold it all, so some of > >> >> the older data spills over to swap. Swap usage peaks at about 10 GB, > >> >> leaving about 30 GB of free swap. Nevertheless, I see these errors, > >> >> with rustc being the usual victim: > >> >> > >> >> Sep 11 23:21:43 zipper kernel: pid 16581 (rustc), jid 43, uid 65534, was killed: out of swap space > >> >> Sep 12 02:48:23 zipper kernel: pid 1209 (rustc), jid 62, uid 65534, was killed: out of swap space > >> >> > >> >> Top shows the size of rustc being about 2 GB, so I doubt that it > >> >> suddenly needs an additional 30 GB of swap. > >> >> > >> >> I'm wondering if there might be a transient kmem shortage that is > >> >> causing a malloc(..., M_NOWAIT) failure in the swap allocation path > >> >> that is the cause of the problem. > >> > > >> > Perhaps this is a consequence of r351114? To confirm this, you might > >> > try increasing the value of vm.pfault_oom_wait to a larger value, like > >> > 20 or 30, and see if the OOM kills still occur. > >> > >> I wonder if increasing vm.pfault_oom_attempts might also be a good idea. > > If you are sure that you cannot exhaust your swap space, set > > attempts to -1 to disable this mechanism. > > I had success just by increasing vm.pfault_oom_attempts from 3 to 10. I do not mind changing this, but could you do an experiment, please ? Set vm.pfault_oom_attempts to 1, and vm.pfault_oom_wait to 100. In other words, the multiplication of attempts by wait should be the same, but only one wait done. I am curious if it is enough for your config, i.e. it is indeed the pageout speed issue, vs. vm_page_alloc() at fault time does several speedups of pagedaemon during allocation attempts. > > > Basically, page fault handler waits for vm.pfault_oom_wait * > > vm.pfault_oom_attempts for a page allocation before killing the process. > > Default is 30 secs, and if you cannot get a page for 30 secs, there is > > something very wrong with the machine. > > There is nothing really wrong with the machine. The load is just high. > Probably pretty bad for interactivity, but throughput is just fine, with > CPU %idle pretty much pegged at zero the whole time. > > I kept an eye on the machine for a while during a run with the new > tuning. Most of the time, free memory bounced between 2 and 4 GB, with > little page out activity. There were about 60 running processes, most > of which were writing to 16 tmpfs filesystems. Sometimes free memory > dropped into the 1 to 2 GB range and pageouts spiked. This condition > could persist for 30 seconds or more, which is probably the reason for > the OOM kills with the default tuning. I sometimes saw free memory drop > below 1 GB. The lowest I aaw was 470 MB. I'm guessing that this code > fails page allocation when free memmory is below some threshold to avoid > potential deadlocks. This should be vm.v_free_reserved as far as I remember. > > Swap on this machine consists of a gmirror pair of partitions on a pair > of 1 TB WD Green drives, that are now on their third computer. The > remainder of the space of the drives are used for the mirrored vdev for > the system zpool. Not terribly fast, even in the days when these drives > were new, but mostly fast enough to keep all the CPU cores busy other > than during poudriere startup and wind down when there isn't enough work > to go around. I could spend money on faster storage, but it really > wouldn't decrease poudriere run time much. It probably is close enough > to the limit that I would need to improve storage speed if I swapped the > Ryzen for a Threadripper. If you have enough swap, then indeed only the swap speed matters. From owner-freebsd-current@freebsd.org Sun Sep 15 22:29:49 2019 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 9F723E9CC4 for ; Sun, 15 Sep 2019 22:29:49 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: from mail-vs1-xe42.google.com (mail-vs1-xe42.google.com [IPv6:2607:f8b0:4864:20::e42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46WkZh36Mhz3Jvs for ; Sun, 15 Sep 2019 22:29:48 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: by mail-vs1-xe42.google.com with SMTP id m22so22046141vsl.9 for ; Sun, 15 Sep 2019 15:29:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=LpkGnDX3X7ovNvjOK2k/I+RxNKc1sxEi757fTzEonm0=; b=Gy9/mmR0AADgQcLRICD6AVyN1kYB3ZG4jNW42gvyei8bOMgI7T7o8X05qX3VAFBiRw XRCLPhuPC0l863TL9yUtluPhOS0dZEtvV94LuaP8cmoFxu98Dmh4jUZExSXrxS6BixM9 a6DxJzXJFd0w6k/UyE01g6RBDtFBMouB36CTPatVuVOkQwUtqxOZoW7PKt/PKk7om9MT uNzodqkyaJ1cTSlWNaGvufMrtjRkkM1bThxRKqRWv8/1hEXarMAUtGUrYwARvaVRau/I 9/Bp5RPwuIW0OnVBDvew3EoF2pEivqwi6ohIYkMth5K1YQ2bgIQE6mc4Tan+3e7Bk0mb Aq1g== 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=LpkGnDX3X7ovNvjOK2k/I+RxNKc1sxEi757fTzEonm0=; b=PQz7OnVvazuTqFb3+94rYJqY2YmGHBVTJRYezSYJxv3bFRaUKHUBq5rv4Y8Y90ORYO 1/A5CuXTpXX869gBw9uSmummOPFqlAOChidbTpTtXIJjvdEuT84mX8KgSXkr/DBp9xHW TO5qE8yBWkS1EeKdWYOgWkE9r7HmQfSsiZS8pE03jgvYdwW0k3I37l4lA+MMDmddPxgr 5rXIQjOkOe/sAJ6wBNlfpkqjO9LfgS98DtUQSfaK7J3yj163urgx8t6H4VSINx7bfKIS +vm3BQeV4qrIT8OPoYNO6LVSM7VC4Cj2ZiM8ktD0vpPcYZsZvsaxwzDHm1Gh5vDTfkqq 8b3w== X-Gm-Message-State: APjAAAVtsKIxB+6Z5YUJxYl04A6EvipK1ANbGYUIr0nG36Z5K+1tLxsJ 4gGQQmveX9vAAlnpwc3ESVMRXKUAbnNO+YhThYsEOFo= X-Google-Smtp-Source: APXvYqzAacTYbpXQbqPugui1KSChwky9Si/3/5gS+tkHduLeFyyMzBB8p8xowwWomJXntClYXCTtkEof1ySb+WuCwyU= X-Received: by 2002:a67:1bc2:: with SMTP id b185mr21364674vsb.116.1568586586805; Sun, 15 Sep 2019 15:29:46 -0700 (PDT) MIME-Version: 1.0 From: "Clay Daniels Jr." Date: Sun, 15 Sep 2019 17:29:36 -0500 Message-ID: Subject: AMD & 13.0 Current To: "freebsd-current@freebsd.org" X-Rspamd-Queue-Id: 46WkZh36Mhz3Jvs X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Gy9/mmR0; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of claydanielsjr@gmail.com designates 2607:f8b0:4864:20::e42 as permitted sender) smtp.mailfrom=claydanielsjr@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[1]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (2.13), ipnet: 2607:f8b0::/32(-2.70), asn: 15169(-2.24), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2.4.e.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; TO_DN_EQ_ADDR_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 15 Sep 2019 22:29:49 -0000 I have built me a new computer, put it together, and being impatient did not even partition the 2TB WD HD, but just installed last weeks Current. Worked great! Now that I have these two to compare I will share the details and results, particularly if you are using AMD CPR/Radeon Graphics. The older: Per Windows: HP Pavilion23 All-in-one PC Manufactured & bought 2014 AMD E2-3800 APU with Radeon Graphics 1.30GHz CPU - 4.00 GB RAM Per either Linux or FreeBSD13: Graphics: Device-1: AMD Kabini [Radeon HD 8280 / R3 Series]vendor:Hewlett-Packard driver: radeon v: kernel bus ID: 00:01.0 Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD KABINI (DRM 2.50.0 4.19.0-5-amd64 LLVM 7.0.0) v: 4.5 Mesa 18.2.6 direct render: Yes The newer: R7_BSD-13 clay@r7bsd:~ $ uname -a FreeBSD r7bsd 13.0-CURRENT FreeBSD 13.0-CURRENT r352265 GENERIC amd64 clay@r7bsd:~ $ gpart show -p => 34 3907029101 ada0 GPT (1.8T) 34 2014 - free - (1.0M) 2048 1083392 ada0p1 ms-recovery (529M) 1085440 204800 ada0p2 efi (100M) 1290240 32768 ada0p3 ms-reserved (16M) 1323008 1072420864 ada0p4 ms-basic-data (511G) 1073743872 532480 ada0p5 efi (260M) 1074276352 2824331256 ada0p6 freebsd-ufs (1.3T) 3898607608 8388608 ada0p7 freebsd-swap (4.0G) 3906996216 32919 - free - (16M) Hardware: AMD Ryzen7 3700X CPU MSI MSI X570-A PRO Motherboard MSI Radeon RX 570 Video Card G.SKILL Ripjaws V Series 16GB SDRAM DDR4 3200 Memory The good thing is they both use the same drm-kmod "amdgpu". So I can see that a 2014 or later computer will probably use the same, and not the legacy "radeonkms" in /etc/rc.conf. The other thing to note, is that for 13.0 Current they both need a line in /boot/loader.conf: hw.syscons..disable=1 That's basically my report. I am enjoying my new machine. Clay From owner-freebsd-current@freebsd.org Sun Sep 15 23:20:13 2019 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 D293FEB19C for ; Sun, 15 Sep 2019 23:20:13 +0000 (UTC) (envelope-from CSO@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Wlhr2QHKz3MCL for ; Sun, 15 Sep 2019 23:20:12 +0000 (UTC) (envelope-from CSO@riseup.net) Received: from bell.riseup.net (bell-pn.riseup.net [10.0.1.178]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 3B9401A0AC6; Sun, 15 Sep 2019 16:20:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1568589610; bh=Ba55l7Hg/cgexLIUHNHY63rMZZ8MMj3nxoQ+1bCg11k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=JGV+V3nlteBg++pGPsWH2iMrVNhezHNM2luKLH9xeexN2WiD+umwW2Q7WKCMLT2vV iRiI63xeKTKchkU1g3Ln/cnVTA0xkPupfqV9kF6hMUDeQg1krtl+BSb8SJxGX+Fkkn XaPHK9/oESftWUKhxXw2DiZGvnCjZTzvEMq1vaa0= X-Riseup-User-ID: D72CAD3F07F2C0C4AB5DE8B1E1BBA5CEC32945EB24567F16D768770820BB4B19 Received: from [127.0.0.1] (localhost [127.0.0.1]) by bell.riseup.net (Postfix) with ESMTPSA id 74D6F22255D; Sun, 15 Sep 2019 16:20:09 -0700 (PDT) Date: Sun, 15 Sep 2019 23:14:35 +0000 From: CSO@riseup.net To: "Clay Daniels Jr." Cc: "freebsd-current@freebsd.org" Subject: Re: AMD & 13.0 Current Message-ID: <20190915231435.GA27796@whitehouse.gov> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Priority: 1 Importance: high X-Rspamd-Queue-Id: 46Wlhr2QHKz3MCL X-Spamd-Bar: ------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=JGV+V3nl; dmarc=pass (policy=none) header.from=riseup.net; spf=pass (mx1.freebsd.org: domain of CSO@riseup.net designates 198.252.153.129 as permitted sender) smtp.mailfrom=CSO@riseup.net X-Spamd-Result: default: False [-7.51 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; RCVD_VIA_SMTP_AUTH(0.00)[]; IP_SCORE(-3.41)[ip: (-8.94), ipnet: 198.252.153.0/24(-4.47), asn: 16652(-3.58), country: US(-0.05)]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; DWL_DNSWL_LOW(-1.00)[riseup.net.dwl.dnswl.org : 127.0.5.1]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_NO_DN(0.00)[]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_IN_DNSWL_LOW(-0.10)[129.153.252.198.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; RCVD_TLS_ALL(0.00)[]; HAS_X_PRIO_ONE(0.00)[1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 15 Sep 2019 23:20:13 -0000 On Sun, Sep 15, 2019 at 05:29:36PM -0500, Clay Daniels Jr. wrote: > I have built me a new computer, put it together, and being impatient did > not even partition the 2TB WD HD, but just installed last weeks Current. > Worked great! > Now that I have these two to compare I will share the details and results, > particularly if you are using AMD CPR/Radeon Graphics. > > The older: > Per Windows: > HP Pavilion23 All-in-one PC > Manufactured & bought 2014 > AMD E2-3800 APU with Radeon Graphics > 1.30GHz CPU - 4.00 GB RAM > Per either Linux or FreeBSD13: > Graphics: > Device-1: AMD Kabini [Radeon HD 8280 / R3 Series]vendor:Hewlett-Packard > driver: radeon v: kernel bus ID: 00:01.0 > Display: x11 server: X.Org 1.19.2 driver: ati,radeon > unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz > OpenGL: renderer: AMD KABINI (DRM 2.50.0 4.19.0-5-amd64 LLVM 7.0.0) > v: 4.5 Mesa 18.2.6 direct render: Yes > > The newer: > R7_BSD-13 > clay@r7bsd:~ $ uname -a > FreeBSD r7bsd 13.0-CURRENT FreeBSD 13.0-CURRENT r352265 GENERIC amd64 > clay@r7bsd:~ $ gpart show -p > => 34 3907029101 ada0 GPT (1.8T) > 34 2014 - free - (1.0M) > 2048 1083392 ada0p1 ms-recovery (529M) > 1085440 204800 ada0p2 efi (100M) > 1290240 32768 ada0p3 ms-reserved (16M) > 1323008 1072420864 ada0p4 ms-basic-data (511G) > 1073743872 532480 ada0p5 efi (260M) > 1074276352 2824331256 ada0p6 freebsd-ufs (1.3T) > 3898607608 8388608 ada0p7 freebsd-swap (4.0G) > 3906996216 32919 - free - (16M) > Hardware: > AMD Ryzen7 3700X CPU > MSI MSI X570-A PRO Motherboard > MSI Radeon RX 570 Video Card > G.SKILL Ripjaws V Series 16GB SDRAM DDR4 3200 Memory > > The good thing is they both use the same drm-kmod "amdgpu". > So I can see that a 2014 or later computer will probably use the same, and > not the legacy "radeonkms" in /etc/rc.conf. > > The other thing to note, is that for 13.0 Current they both need a line in > /boot/loader.conf: > hw.syscons..disable=1 Why is this line needed and for what purposes? Does the new hardware in this new build also work well in FreeBSD 12 stable branch? The FreeBSD current is for testing purposes so we are very interested in how it the above mentioned new hardware work on stable or production version. Mark > > That's basically my report. I am enjoying my new machine. > Clay > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Mon Sep 16 00:25:15 2019 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 C466BECBCA for ; Mon, 16 Sep 2019 00:25:15 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Wn7s5JXGz3PbN for ; Mon, 16 Sep 2019 00:25:13 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: by mail-vs1-xe34.google.com with SMTP id b1so1266717vsr.10 for ; Sun, 15 Sep 2019 17:25:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/tU/jIfyX/Bbqj2upWrm5BxyFbwU5ZXfNx+8lHnwUFQ=; b=cJ3EnXjnS9Yy2hRF2RcvFBVKUE4r1taHCu6sWjZnjydvJrXpdWVibGuxhQsCzoa/f4 48dwW0kcLeXVJBB8AvsmkE1BEJML48HNY8ak4HdA+kWuIJDu8H1thxDGOSOs+aqksBeJ 7tE7pTcpFOYI7vT3xyoiQCK4HqWKdihLsxvUzRH2HU3m46OlSv2VU8+faIocFbIswA+x CupTzzmIo46bb8sRNRh6y8uMHFLOjXJHeU+bxMs7ba2bzjZfY7nUSudD+88s0LxPybGP +4mAXnLCgd8cypZo/zMgQ9cWRfixQ/gvPFhrD4iqgSMRc5HS97e/e+7YEA95Anz/lXwx /CRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/tU/jIfyX/Bbqj2upWrm5BxyFbwU5ZXfNx+8lHnwUFQ=; b=PNv0wmvrZnr/RuwjxogostWTkuV29RCMRk7C4I1eSuiDBgTvJgTjb1dvSjpYb93AUo JqtrqXhOhS87xdcbsVjamB5tN7KvAjI/JCzCxVxetwIxFU0UWTcamhT/sv8pgUiJAjPa uiDISIC1CUNr4658qagfGVhxI296fR/W9mBFUNITAl9koq0QDuPHIY+OY5a0Ql8+f76/ MmszFYpGRfAPcQTRt39cFFc0ab4jEMRjInONNhZ8npJMHrL0aft4yrtXHoLnnEsHWAqm ZSebgfjaRTjrIyKP31KTFVjwcbwfQpUDO+JQhVdwxTwoJsQlRrW0TSBCbvRiJGg3yjha Psbg== X-Gm-Message-State: APjAAAVZLspRUKF1QFmRc14NHuXDNGyw7MvgHIrudAK+pnKPCsbnn8Ey gPEYkpuATqE05YwYaOSvdn92Phk3fhUSPEqLpg== X-Google-Smtp-Source: APXvYqxFPCllsz+ALyEB/IjvbH4sLVjoZTMlfvzpc/sHbmSgws3or0s7SZnL/AGe7j/65y0g8NLoLR5ObdXTul4qIX4= X-Received: by 2002:a67:31d3:: with SMTP id x202mr33211225vsx.125.1568593511805; Sun, 15 Sep 2019 17:25:11 -0700 (PDT) MIME-Version: 1.0 References: <20190915231435.GA27796@whitehouse.gov> In-Reply-To: <20190915231435.GA27796@whitehouse.gov> From: "Clay Daniels Jr." Date: Sun, 15 Sep 2019 19:25:00 -0500 Message-ID: Subject: Re: AMD & 13.0 Current To: CSO@riseup.net Cc: "freebsd-current@freebsd.org" X-Rspamd-Queue-Id: 46Wn7s5JXGz3PbN X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=cJ3EnXjn; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of claydanielsjr@gmail.com designates 2607:f8b0:4864:20::e34 as permitted sender) smtp.mailfrom=claydanielsjr@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[7]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.61), ipnet: 2607:f8b0::/32(-2.70), asn: 15169(-2.24), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[4.3.e.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 00:25:15 -0000 Mark, the line added in /boot/loader.conf was shared by others on this list in August when I missed my usual install of the weekly 13.0 Current snapshot. Turned out to be what could be called a "framebuffer problem" and by adding this line in loader.conf solved my problem. Later I did more looking and found we have a nice Wiki about graphics at: https://wiki.freebsd.org/Graphics You will see this about mid way down the page: "It is important to note that there is currently a conflict with both AMD drivers and the EFI frambuffer. The current workaround, when booting via UEFI on these systems, is to disable the framebuffer via /boot/loader.conf: hw.syscons.disable=1" As for FreeBSD 12.0 Stable, I have not installed it yet, and probably would have not considered that as I am pretty much into bsd13, but I will now plan to load their snapshot on Friday and give it a try. Clay On Sun, Sep 15, 2019 at 6:20 PM wrote: > On Sun, Sep 15, 2019 at 05:29:36PM -0500, Clay Daniels Jr. wrote: > > I have built me a new computer, put it together, and being impatient did > > not even partition the 2TB WD HD, but just installed last weeks Current. > > Worked great! > > Now that I have these two to compare I will share the details and > results, > > particularly if you are using AMD CPR/Radeon Graphics. > > > > The older: > > Per Windows: > > HP Pavilion23 All-in-one PC > > Manufactured & bought 2014 > > AMD E2-3800 APU with Radeon Graphics > > 1.30GHz CPU - 4.00 GB RAM > > Per either Linux or FreeBSD13: > > Graphics: > > Device-1: AMD Kabini [Radeon HD 8280 / R3 Series]vendor:Hewlett-Packard > > driver: radeon v: kernel bus ID: 00:01.0 > > Display: x11 server: X.Org 1.19.2 driver: ati,radeon > > unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz > > OpenGL: renderer: AMD KABINI (DRM 2.50.0 4.19.0-5-amd64 LLVM 7.0.0) > > v: 4.5 Mesa 18.2.6 direct render: Yes > > > > The newer: > > R7_BSD-13 > > clay@r7bsd:~ $ uname -a > > FreeBSD r7bsd 13.0-CURRENT FreeBSD 13.0-CURRENT r352265 GENERIC amd64 > > clay@r7bsd:~ $ gpart show -p > > => 34 3907029101 ada0 GPT (1.8T) > > 34 2014 - free - (1.0M) > > 2048 1083392 ada0p1 ms-recovery (529M) > > 1085440 204800 ada0p2 efi (100M) > > 1290240 32768 ada0p3 ms-reserved (16M) > > 1323008 1072420864 ada0p4 ms-basic-data (511G) > > 1073743872 532480 ada0p5 efi (260M) > > 1074276352 2824331256 ada0p6 freebsd-ufs (1.3T) > > 3898607608 8388608 ada0p7 freebsd-swap (4.0G) > > 3906996216 32919 - free - (16M) > > Hardware: > > AMD Ryzen7 3700X CPU > > MSI MSI X570-A PRO Motherboard > > MSI Radeon RX 570 Video Card > > G.SKILL Ripjaws V Series 16GB SDRAM DDR4 3200 Memory > > > > The good thing is they both use the same drm-kmod "amdgpu". > > So I can see that a 2014 or later computer will probably use the same, > and > > not the legacy "radeonkms" in /etc/rc.conf. > > > > The other thing to note, is that for 13.0 Current they both need a line > in > > /boot/loader.conf: > > hw.syscons..disable=1 > > Why is this line needed and for what purposes? > > Does the new hardware in this new build also work well in FreeBSD 12 > stable branch? The FreeBSD current is for testing purposes so we are > very interested in how it the above mentioned new hardware work on > stable or production version. > > Mark > > > > > That's basically my report. I am enjoying my new machine. > > Clay > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Mon Sep 16 02:05:59 2019 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 EC0B5EF79A for ; Mon, 16 Sep 2019 02:05:59 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46WqN66fMpz40Ml for ; Mon, 16 Sep 2019 02:05:58 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: by mail-vs1-xe2c.google.com with SMTP id w195so22235834vsw.11 for ; Sun, 15 Sep 2019 19:05:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FGBeTgIDzk+F6Ssr1jN3oA3Q50GAeKQ5Jig+mmfU05k=; b=pzLlEzmORYPRB0B6llL+nLUw1tTYA6EWfHKZ5lI0uyn2sd+Li4vdlsmAChOoRWhOWy bS3uRFsyYsPySx5PASPoJN0jz6v/tLlfuRQD3/8+tDbE1iLE7jLk+hzYpxmkxezuzT9c r25dZPxnkpK56B2e04Bw5Kzxn/iuxRJF2BUUQS76wlJy1FwGSjdegQPGVg+MRWLHC1Dj lM4ciX1YtSzpSgWzjLrTmHCXwxtZj2FwyojVbjcBmAPqSzl5B2o7l7I51U0LAn2huTat axT4Xncaeu58q1VFu4Z0oSZQ19TKBPSAkIijs0I8ZPCS53BTuhVkGxOVJQMD+2rHGxdB sFqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FGBeTgIDzk+F6Ssr1jN3oA3Q50GAeKQ5Jig+mmfU05k=; b=trAXmOPpKLLGAt/P1STSRsVLmfM+qfNO+1N6S5XgpYwSLXS1is8is7icjQgFtbxsi7 Cp+fF+MpnRq2isbgVa0GO74hHJvvyCbQjxqKxHcUSeKdCo4CpAooxvz3Ly6zqKDZg1Uq 01W1ssWpwQ5CUflfsalUqFscftPpjrmtIug9sTjDDsTE9ocq/yCShM3py0tHvjyu2kTg Bs2+xP3azlrcM8eK0QuBdTD4sKBeyr+Ml1xCusPncPM6j7AnWnIIbmi/ekBqDYIqXVg1 udeMSD4NpkSR383KYsQ9rwlvIE6t329OHzm07VV5DAaNFlKHwusgJNGNZFwOOT4v3Hz3 XX3g== X-Gm-Message-State: APjAAAXwM7cNFIIjwWfLGHwMijf2pB2sd9KPQfss0wLUVIw/VEDiu+bP +E1fSjbQBTh3OB+FS2LDJ/wUhd5pBiDSAKglNA== X-Google-Smtp-Source: APXvYqym1jkZzC3gT+KAL9Gd/H14cee83prOJwSilLkeV1UHIy6m6c37nql7v5Yanc2QS45xE1rKUC51V0D8iDYjCzk= X-Received: by 2002:a05:6102:7b2:: with SMTP id x18mr7383049vsg.176.1568599557319; Sun, 15 Sep 2019 19:05:57 -0700 (PDT) MIME-Version: 1.0 References: <20190915231435.GA27796@whitehouse.gov> In-Reply-To: From: "Clay Daniels Jr." Date: Sun, 15 Sep 2019 21:05:46 -0500 Message-ID: Subject: Re: AMD & 13.0 Current To: CSO@riseup.net Cc: "freebsd-current@freebsd.org" X-Rspamd-Queue-Id: 46WqN66fMpz40Ml X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=pzLlEzmO; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of claydanielsjr@gmail.com designates 2607:f8b0:4864:20::e2c as permitted sender) smtp.mailfrom=claydanielsjr@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[7]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.67), ipnet: 2607:f8b0::/32(-2.70), asn: 15169(-2.24), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[c.2.e.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 02:06:00 -0000 I wanted to add that when I installed this weeks 13.0 snapshot, I tried it first with only the kld_list="amdgpu" in /etc/rc.conf AND NO /boot/loader.conf entry. It failed to load startx. I then made the loader.conf entr, rebooted and startx loaded x windows, the nice little screen with 3 xterminals and a clock. On Sun, Sep 15, 2019 at 7:25 PM Clay Daniels Jr. wrote: > Mark, the line added in /boot/loader.conf was shared by others on this > list in August when I missed my usual install of the weekly 13.0 Current > snapshot. Turned out to be what could be called a "framebuffer problem" and > by adding this line in loader.conf solved my problem. Later I did more > looking and found we have a nice Wiki about graphics at: > > https://wiki.freebsd.org/Graphics > > > You will see this about mid way down the page: > > "It is important to note that there is currently a conflict with both AMD > drivers and the EFI frambuffer. The current workaround, when booting via > UEFI on these systems, is to disable the framebuffer via /boot/loader.conf: > > hw.syscons.disable=1" > > As for FreeBSD 12.0 Stable, I have not installed it yet, and probably > would have not considered that as I am pretty much into bsd13, but I will > now plan to load their snapshot on Friday and give it a try. > > Clay > > On Sun, Sep 15, 2019 at 6:20 PM wrote: > >> On Sun, Sep 15, 2019 at 05:29:36PM -0500, Clay Daniels Jr. wrote: >> > I have built me a new computer, put it together, and being impatient did >> > not even partition the 2TB WD HD, but just installed last weeks Current. >> > Worked great! >> > Now that I have these two to compare I will share the details and >> results, >> > particularly if you are using AMD CPR/Radeon Graphics. >> > >> > The older: >> > Per Windows: >> > HP Pavilion23 All-in-one PC >> > Manufactured & bought 2014 >> > AMD E2-3800 APU with Radeon Graphics >> > 1.30GHz CPU - 4.00 GB RAM >> > Per either Linux or FreeBSD13: >> > Graphics: >> > Device-1: AMD Kabini [Radeon HD 8280 / R3 Series]vendor:Hewlett-Packard >> > driver: radeon v: kernel bus ID: 00:01.0 >> > Display: x11 server: X.Org 1.19.2 driver: ati,radeon >> > unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz >> > OpenGL: renderer: AMD KABINI (DRM 2.50.0 4.19.0-5-amd64 LLVM 7.0.0) >> > v: 4.5 Mesa 18.2.6 direct render: Yes >> > >> > The newer: >> > R7_BSD-13 >> > clay@r7bsd:~ $ uname -a >> > FreeBSD r7bsd 13.0-CURRENT FreeBSD 13.0-CURRENT r352265 GENERIC amd64 >> > clay@r7bsd:~ $ gpart show -p >> > => 34 3907029101 ada0 GPT (1.8T) >> > 34 2014 - free - (1.0M) >> > 2048 1083392 ada0p1 ms-recovery (529M) >> > 1085440 204800 ada0p2 efi (100M) >> > 1290240 32768 ada0p3 ms-reserved (16M) >> > 1323008 1072420864 ada0p4 ms-basic-data (511G) >> > 1073743872 532480 ada0p5 efi (260M) >> > 1074276352 2824331256 ada0p6 freebsd-ufs (1.3T) >> > 3898607608 8388608 ada0p7 freebsd-swap (4.0G) >> > 3906996216 32919 - free - (16M) >> > Hardware: >> > AMD Ryzen7 3700X CPU >> > MSI MSI X570-A PRO Motherboard >> > MSI Radeon RX 570 Video Card >> > G.SKILL Ripjaws V Series 16GB SDRAM DDR4 3200 Memory >> > >> > The good thing is they both use the same drm-kmod "amdgpu". >> > So I can see that a 2014 or later computer will probably use the same, >> and >> > not the legacy "radeonkms" in /etc/rc.conf. >> > >> > The other thing to note, is that for 13.0 Current they both need a line >> in >> > /boot/loader.conf: >> > hw.syscons..disable=1 >> >> Why is this line needed and for what purposes? >> >> Does the new hardware in this new build also work well in FreeBSD 12 >> stable branch? The FreeBSD current is for testing purposes so we are >> very interested in how it the above mentioned new hardware work on >> stable or production version. >> >> Mark >> >> > >> > That's basically my report. I am enjoying my new machine. >> > Clay >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to " >> freebsd-current-unsubscribe@freebsd.org" >> > From owner-freebsd-current@freebsd.org Mon Sep 16 02:22:34 2019 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 72266EFE67 for ; Mon, 16 Sep 2019 02:22:34 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46WqlF2dNHz416c for ; Mon, 16 Sep 2019 02:22:33 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.206] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 6f9947ba TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Mon, 16 Sep 2019 02:15:51 +0000 (UTC) Subject: Re: AMD & 13.0 Current To: CSO@riseup.net, "Clay Daniels Jr." Cc: "freebsd-current@freebsd.org" References: <20190915231435.GA27796@whitehouse.gov> From: Pete Wright Message-ID: <8a8de0ac-ad49-3ce6-65f5-ddcbdf6a658f@nomadlogic.org> Date: Sun, 15 Sep 2019 19:15:51 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <20190915231435.GA27796@whitehouse.gov> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 46WqlF2dNHz416c X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 174.136.98.114 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-4.90 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; FROM_HAS_DN(0.00)[]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RECEIVED_SPAMHAUS_PBL(0.00)[239.162.243.23.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-2.60)[ip: (-9.35), ipnet: 174.136.96.0/20(-3.30), asn: 25795(-0.29), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 02:22:34 -0000 On 9/15/19 4:14 PM, CSO@riseup.net wrote: > >> The other thing to note, is that for 13.0 Current they both need a line in >> /boot/loader.conf: >> hw.syscons..disable=1 > Why is this line needed and for what purposes? This issue, and the one it links to, go a bit towards describing the issue: https://github.com/FreeBSDDesktop/kms-drm/issues/127 I have to use the workaround as well, which isn't ideal to be honest, but i just think due to the other higher priority tasks it hasn't been addressed yet. > > Does the new hardware in this new build also work well in FreeBSD 12 > stable branch? The FreeBSD current is for testing purposes so we are > very interested in how it the above mentioned new hardware work on > stable or production version. I run both CURRENT and 12.0-RELEASE on Ryzen with amdgpu graphics and they work fine. I actually use AWS instances that have the AMD Epyc CPU installed and those work great as well - so i def feel like AMD is becoming relevant again on both desktop and servers :) -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Mon Sep 16 06:12:28 2019 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 277CBF4693; Mon, 16 Sep 2019 06:12:28 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vtr.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46WwrW0DwXz4BQj; Mon, 16 Sep 2019 06:12:26 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp239-208.static.internode.on.net [59.167.239.208]) by vtr.rulingia.com (8.15.2/8.15.2) with ESMTPS id x8G6CBe3093769 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 16 Sep 2019 16:12:17 +1000 (AEST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id x8G6C57l031607 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Sep 2019 16:12:05 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id x8G6C54q031606; Mon, 16 Sep 2019 16:12:05 +1000 (AEST) (envelope-from peter) Date: Mon, 16 Sep 2019 16:12:05 +1000 From: Peter Jeremy To: freebsd-current@FreeBSD.org, freebsd-arm@FreeBSD.org Subject: "Sleeping with non-sleepable lock" in NFS on recent -current Message-ID: <20190916061205.GE97181@server.rulingia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6sX45UoQRIJXqkqR" Content-Disposition: inline X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.12.1 (2019-06-15) X-Rspamd-Queue-Id: 46WwrW0DwXz4BQj X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of peter@rulingia.com designates 2001:19f0:5801:ebe:5400:1ff:fe53:30fd as permitted sender) smtp.mailfrom=peter@rulingia.com X-Spamd-Result: default: False [-5.59 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[rulingia.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-1.19)[ipnet: 2001:19f0:5800::/38(-4.94), asn: 20473(-0.93), country: US(-0.05)]; RCPT_COUNT_TWO(0.00)[2]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:20473, ipnet:2001:19f0:5800::/38, country:US]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 06:12:28 -0000 --6sX45UoQRIJXqkqR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm consistently seeing panics in the NFS code on recent -current on aarm64. The panics are one of the following two: Sleeping on "vmopar" with the following non-sleepable locks held: exclusive sleep mutex NEWNFSnode lock (NEWNFSnode lock) r =3D 0 (0xfffffd00= 78b346f0) locked @ /usr/src/sys/fs/nfsclient/nfs_clport.c:432 Sleeping thread (tid 100077, pid 35) owns a non-sleepable lock Both panics have nearly identical backtraces (see below). I'm running diskless on a Rock64 with both filesystem and swap over NFS. The panics can be fairly reliably triggered by any of: * "make -j4 buildworld" * linking the kernel (as part of buildkernel) * "make installworld" Has anyone else seen this? The first panic (sleeping on vmopar) has a backtrace: sched_switch() at mi_switch+0x19c pc =3D 0xffff0000002ab368 lr =3D 0xffff00000028a9f4 sp =3D 0xffff000061192660 fp =3D 0xffff000061192680 mi_switch() at sleepq_switch+0x100 pc =3D 0xffff00000028a9f4 lr =3D 0xffff0000002d56dc sp =3D 0xffff000061192690 fp =3D 0xffff0000611926d0 sleepq_switch() at sleepq_wait+0x48 pc =3D 0xffff0000002d56dc lr =3D 0xffff0000002d5594 sp =3D 0xffff0000611926e0 fp =3D 0xffff000061192700 sleepq_wait() at _sleep+0x2c4 [***] pc =3D 0xffff0000002d5594 lr =3D 0xffff000000289eec sp =3D 0xffff000061192710 fp =3D 0xffff0000611927b0 _sleep() at vm_object_page_remove+0x178 [***] pc =3D 0xffff000000289eec lr =3D 0xffff00000052211c sp =3D 0xffff0000611927c0 fp =3D 0xffff000061192820 vm_object_page_remove() at vnode_pager_setsize+0xc0 pc =3D 0xffff00000052211c lr =3D 0xffff000000539a70 sp =3D 0xffff000061192830 fp =3D 0xffff000061192870 vnode_pager_setsize() at nfscl_loadattrcache+0x2e8 pc =3D 0xffff000000539a70 lr =3D 0xffff0000001ed4b4 sp =3D 0xffff000061192880 fp =3D 0xffff0000611928e0 nfscl_loadattrcache() at ncl_writerpc+0x104 pc =3D 0xffff0000001ed4b4 lr =3D 0xffff0000001e2158 sp =3D 0xffff0000611928f0 fp =3D 0xffff000061192a40 ncl_writerpc() at ncl_doio+0x36c pc =3D 0xffff0000001e2158 lr =3D 0xffff0000001f0370 sp =3D 0xffff000061192a50 fp =3D 0xffff000061192ae0 ncl_doio() at nfssvc_iod+0x228 pc =3D 0xffff0000001f0370 lr =3D 0xffff0000001f1d88 sp =3D 0xffff000061192af0 fp =3D 0xffff000061192b50 nfssvc_iod() at fork_exit+0x7c pc =3D 0xffff0000001f1d88 lr =3D 0xffff00000023ff5c sp =3D 0xffff000061192b60 fp =3D 0xffff000061192b90 fork_exit() at fork_trampoline+0x10 pc =3D 0xffff00000023ff5c lr =3D 0xffff000000562c34 sp =3D 0xffff000061192ba0 fp =3D 0x0000000000000000 For the second panic, the [***] change to: sleepq_wait() at vm_page_sleep_if_busy+0x80 vm_page_sleep_if_busy() at vm_object_page_remove+0xfc --=20 Peter Jeremy --6sX45UoQRIJXqkqR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAl1/J61fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzR4Og/9HqQct7Cnm/MNzuBeWMo7KoA1kvVjD1o863CciBLSf1eUr61MPKwr2ODZ nkHuJwhMGr0wr8LqYmwjQHFlE73kBGlKsFLODQLw/6tXRS2ehkOLIII2StrBujaa Lv5zywwM9+SSYTW9lVf17qlumZjAurPBQ2gC/bJzGx+S9Vp6GWSDH6ibTvG9GMop 7EEQ2yN6fwZ37gCfvh7y8VoTgJa+Drbnrt7YTF5QNiSwk2l0gF9mPDYWp/rjR4nU DjJKiWaH9ZJg9CG5IDY13Ff/Rur6mHYcvSgzDpq5KmFVf9vEgRoS7s3r/JcdcnS8 +vukqy1XJFOzZAP2cPLstwd5QdRPWmOVT/jmVOUQplMtWQLtzEBFks88VmnVFS1n 1Em8qHfbukV6+RBR/dz4u/DiuVlsf7xtZ94BWh84z9rUu6c1KgNRG1b8B3VHiAs9 uiKUSRoCdzBY55GP/ZUinVdCWkbY/60iWIuMFV77IW81kLxmUketjjpst1TWelpN WppJlJSHW4UeTtM0Adbc64BhnhU4TvA01/H9EcmqcS4eSPQk49FSFjJL+RbKqsna XoSoO5Jw+KH9H6MG/sVEi69mJSAj1LsuHvuXrhJdmUOHXJ5gMyz2RWs5ixIGv13J oVdnBHnKkQBWwUGVYP5jLQldy9AtmntgJhJZh7I8lS0h+YvnNo8= =w1bx -----END PGP SIGNATURE----- --6sX45UoQRIJXqkqR-- From owner-freebsd-current@freebsd.org Mon Sep 16 06:33:01 2019 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 F2852F525E; Mon, 16 Sep 2019 06:33:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46WxJD2XL7z4D2N; Mon, 16 Sep 2019 06:32:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x8G6Wqr5025904 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 16 Sep 2019 09:32:55 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x8G6Wqr5025904 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x8G6WqOm025903; Mon, 16 Sep 2019 09:32:52 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 16 Sep 2019 09:32:52 +0300 From: Konstantin Belousov To: Peter Jeremy Cc: freebsd-current@FreeBSD.org, freebsd-arm@FreeBSD.org, rmacklem@freebsd.org Subject: Re: "Sleeping with non-sleepable lock" in NFS on recent -current Message-ID: <20190916063252.GS2559@kib.kiev.ua> References: <20190916061205.GE97181@server.rulingia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190916061205.GE97181@server.rulingia.com> User-Agent: Mutt/1.12.1 (2019-06-15) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-Rspamd-Queue-Id: 46WxJD2XL7z4D2N X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; FREEMAIL_FROM(0.00)[gmail.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; IP_SCORE_FREEMAIL(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.00)[ip: (-2.60), ipnet: 2001:470::/32(-4.46), asn: 6939(-3.21), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 06:33:02 -0000 On Mon, Sep 16, 2019 at 04:12:05PM +1000, Peter Jeremy wrote: > I'm consistently seeing panics in the NFS code on recent -current on aarm64. > The panics are one of the following two: > Sleeping on "vmopar" with the following non-sleepable locks held: > exclusive sleep mutex NEWNFSnode lock (NEWNFSnode lock) r = 0 (0xfffffd0078b346f0) locked @ /usr/src/sys/fs/nfsclient/nfs_clport.c:432 > > Sleeping thread (tid 100077, pid 35) owns a non-sleepable lock > > Both panics have nearly identical backtraces (see below). I'm running > diskless on a Rock64 with both filesystem and swap over NFS. The panics > can be fairly reliably triggered by any of: > * "make -j4 buildworld" > * linking the kernel (as part of buildkernel) > * "make installworld" > > Has anyone else seen this? > > The first panic (sleeping on vmopar) has a backtrace: > sched_switch() at mi_switch+0x19c > pc = 0xffff0000002ab368 lr = 0xffff00000028a9f4 > sp = 0xffff000061192660 fp = 0xffff000061192680 > > mi_switch() at sleepq_switch+0x100 > pc = 0xffff00000028a9f4 lr = 0xffff0000002d56dc > sp = 0xffff000061192690 fp = 0xffff0000611926d0 > > sleepq_switch() at sleepq_wait+0x48 > pc = 0xffff0000002d56dc lr = 0xffff0000002d5594 > sp = 0xffff0000611926e0 fp = 0xffff000061192700 > > sleepq_wait() at _sleep+0x2c4 [***] > pc = 0xffff0000002d5594 lr = 0xffff000000289eec > sp = 0xffff000061192710 fp = 0xffff0000611927b0 > > _sleep() at vm_object_page_remove+0x178 [***] > pc = 0xffff000000289eec lr = 0xffff00000052211c > sp = 0xffff0000611927c0 fp = 0xffff000061192820 > > vm_object_page_remove() at vnode_pager_setsize+0xc0 > pc = 0xffff00000052211c lr = 0xffff000000539a70 > sp = 0xffff000061192830 fp = 0xffff000061192870 > > vnode_pager_setsize() at nfscl_loadattrcache+0x2e8 > pc = 0xffff000000539a70 lr = 0xffff0000001ed4b4 > sp = 0xffff000061192880 fp = 0xffff0000611928e0 > > nfscl_loadattrcache() at ncl_writerpc+0x104 > pc = 0xffff0000001ed4b4 lr = 0xffff0000001e2158 > sp = 0xffff0000611928f0 fp = 0xffff000061192a40 > > ncl_writerpc() at ncl_doio+0x36c > pc = 0xffff0000001e2158 lr = 0xffff0000001f0370 > sp = 0xffff000061192a50 fp = 0xffff000061192ae0 > > ncl_doio() at nfssvc_iod+0x228 > pc = 0xffff0000001f0370 lr = 0xffff0000001f1d88 > sp = 0xffff000061192af0 fp = 0xffff000061192b50 > > nfssvc_iod() at fork_exit+0x7c > pc = 0xffff0000001f1d88 lr = 0xffff00000023ff5c > sp = 0xffff000061192b60 fp = 0xffff000061192b90 > > fork_exit() at fork_trampoline+0x10 > pc = 0xffff00000023ff5c lr = 0xffff000000562c34 > sp = 0xffff000061192ba0 fp = 0x0000000000000000 > > > For the second panic, the [***] change to: > sleepq_wait() at vm_page_sleep_if_busy+0x80 > vm_page_sleep_if_busy() at vm_object_page_remove+0xfc Weird since this should have been fixed long time ago. Anyway, please try the following, it should fix the rest of cases. diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c index 471e029a8b5..098de1ced80 100644 --- a/sys/fs/nfsclient/nfs_clport.c +++ b/sys/fs/nfsclient/nfs_clport.c @@ -511,10 +511,10 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, * zero np->n_attrstamp to indicate that * the attributes are stale. */ - vap->va_size = np->n_size; + nsize = vap->va_size = np->n_size; + setnsize = 1; np->n_attrstamp = 0; KDTRACE_NFS_ATTRCACHE_FLUSH_DONE(vp); - vnode_pager_setsize(vp, np->n_size); } else if (np->n_flag & NMODIFIED) { /* * We've modified the file: Use the larger @@ -526,7 +526,8 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, np->n_size = vap->va_size; np->n_flag |= NSIZECHANGED; } - vnode_pager_setsize(vp, np->n_size); + nsize = np->n_size; + setnsize = 1; } else if (vap->va_size < np->n_size) { /* * When shrinking the size, the call to @@ -540,7 +541,7 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, } else { np->n_size = vap->va_size; np->n_flag |= NSIZECHANGED; - vnode_pager_setsize(vp, np->n_size); + setnsize = 1; } } else { np->n_size = vap->va_size; From owner-freebsd-current@freebsd.org Mon Sep 16 07:20:23 2019 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 3B736F62E9 for ; Mon, 16 Sep 2019 07:20:23 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) Received: from mail2.mands.hu (mail2.mands.hu [93.189.114.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.mands.hu", Issuer "e-Szigno SSL CA 2014" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46WyLt0431z4Ft5 for ; Mon, 16 Sep 2019 07:20:21 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) From: =?iso-8859-2?Q?M=26S_-_Krasznai_Andr=E1s?= To: "freebsd-current@freebsd.org" Subject: error message during "mergemaster" Thread-Topic: error message during "mergemaster" Thread-Index: AdVsXqRDt3rQR8bZQtWStFajNuku/w== Date: Mon, 16 Sep 2019 07:20:18 +0000 Message-ID: <0fb42f2b46084bc3bdbedaaf1a48f62e@MSEXCH13.mands.hu> Accept-Language: en-US, hu-HU Content-Language: hu-HU X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [192.168.6.59] MIME-Version: 1.0 X-Rspamd-Queue-Id: 46WyLt0431z4Ft5 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of Krasznai.Andras@mands.hu designates 93.189.114.146 as permitted sender) smtp.mailfrom=Krasznai.Andras@mands.hu X-Spamd-Result: default: False [-1.59 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.984,0]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/related,multipart/alternative,text/plain]; DMARC_NA(0.00)[mands.hu]; NEURAL_HAM_LONG(-0.31)[-0.311,0]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[146.114.189.93.list.dnswl.org : 127.0.10.0]; TO_DN_EQ_ADDR_ALL(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~,4:~]; ASN(0.00)[asn:47116, ipnet:93.189.112.0/21, country:HU]; IP_SCORE(0.00)[country: HU(0.02)] Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 07:20:23 -0000 In FreeBSD 13.0 when I update the kernel and world I receive the following = error message during mergemaster: ka-freebsd:/usr/src# mergemaster *** Creating the temporary root environment in /var/tmp/temproot *** /var/tmp/temproot ready for use *** Creating and populating directory structure in /var/tmp/temproot make[4]: "/usr/src/lib/libc/net/Makefile.inc" line 130: warning: duplicate = script for target "afterinstallconfig" ignored make[4]: "/usr/src/lib/libc/gen/Makefile.inc" line 554: warning: using prev= ious script for "afterinstallconfig" defined here I looks like the generated kernel correctly works but the error message sho= uld not be there... What can be the cuase and how can I repair it? Best regards Krasznai Andr=E1s rendszerm=E9rn=F6k [M&S_logo] 1136 Budapest, Pann=F3nia utca 11. Tel: +36 1 703 2923 Mobil: +36 30 703 2923 K=F6zpont: +36 1 703 2920 Fax: +36 1 703 2949 email: krasznai.andras@mands.hu From owner-freebsd-current@freebsd.org Mon Sep 16 07:44:45 2019 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 530C1F6B35; Mon, 16 Sep 2019 07:44:45 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vtr.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Wyv03C8gz4H4d; Mon, 16 Sep 2019 07:44:43 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp239-208.static.internode.on.net [59.167.239.208]) by vtr.rulingia.com (8.15.2/8.15.2) with ESMTPS id x8G7iXlF094371 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 16 Sep 2019 17:44:39 +1000 (AEST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id x8G7iS1w034837 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Sep 2019 17:44:28 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id x8G7iSRj034836; Mon, 16 Sep 2019 17:44:28 +1000 (AEST) (envelope-from peter) Date: Mon, 16 Sep 2019 17:44:28 +1000 From: Peter Jeremy To: Konstantin Belousov Cc: freebsd-current@FreeBSD.org, freebsd-arm@FreeBSD.org, rmacklem@freebsd.org Subject: Re: "Sleeping with non-sleepable lock" in NFS on recent -current Message-ID: <20190916074428.GF97181@server.rulingia.com> References: <20190916061205.GE97181@server.rulingia.com> <20190916063252.GS2559@kib.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="yLVHuoLXiP9kZBkt" Content-Disposition: inline In-Reply-To: <20190916063252.GS2559@kib.kiev.ua> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.12.1 (2019-06-15) X-Rspamd-Queue-Id: 46Wyv03C8gz4H4d X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of peter@rulingia.com designates 2001:19f0:5801:ebe:5400:1ff:fe53:30fd as permitted sender) smtp.mailfrom=peter@rulingia.com X-Spamd-Result: default: False [-5.59 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_NA(0.00)[rulingia.com]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; SIGNED_PGP(-2.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:20473, ipnet:2001:19f0:5800::/38, country:US]; RCVD_TLS_ALL(0.00)[]; IP_SCORE(-1.19)[ipnet: 2001:19f0:5800::/38(-4.94), asn: 20473(-0.95), country: US(-0.05)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 07:44:45 -0000 --yLVHuoLXiP9kZBkt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2019-Sep-16 09:32:52 +0300, Konstantin Belousov wr= ote: >On Mon, Sep 16, 2019 at 04:12:05PM +1000, Peter Jeremy wrote: >> I'm consistently seeing panics in the NFS code on recent -current on aar= m64. >> The panics are one of the following two: >> Sleeping on "vmopar" with the following non-sleepable locks held: >> exclusive sleep mutex NEWNFSnode lock (NEWNFSnode lock) r =3D 0 (0xfffff= d0078b346f0) locked @ /usr/src/sys/fs/nfsclient/nfs_clport.c:432 >>=20 >> Sleeping thread (tid 100077, pid 35) owns a non-sleepable lock >>=20 >> Both panics have nearly identical backtraces (see below). I'm running >> diskless on a Rock64 with both filesystem and swap over NFS. The panics >> can be fairly reliably triggered by any of: >> * "make -j4 buildworld" >> * linking the kernel (as part of buildkernel) >> * "make installworld" >>=20 >> Has anyone else seen this? =2E.. >Weird since this should have been fixed long time ago. Anyway, please >try the following, it should fix the rest of cases. > >diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c =2E.. >@@ -540,7 +541,7 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvatt= r *nap, void *nvaper, > } else { > np->n_size =3D vap->va_size; > np->n_flag |=3D NSIZECHANGED; >- vnode_pager_setsize(vp, np->n_size); >+ setnsize =3D 1; Should this else block include a "nsize =3D np->n_size;"? Without it, nsize will remain set to 0, which looks wrong. --=20 Peter Jeremy --yLVHuoLXiP9kZBkt Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAl1/PVZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzQn5A/+KCn/0VbEW0fEq2sWUBEYU7yKurDXKhvlcVYn2QCsBwgzi/PW1TJPUg6X AGuq/dg4wLRxPVVvtRN42x4x8nxCe2A+hxFtH1bq1JY61sBQZFhCqf+aewA4U2in oP1cJEbxSuMyZxBHz7RsW/788PNk/Y0gJIvX2GGR3zAc4fnxRCLlRePcQ7MZV1qW IPyEz1P2jOW5VA6azFQerKe2Qg8K2ZYv+ph589CmdNk66+sSb63DXe2lhA1JPDzV B3Pgf1oPMjJP4CabpEl+7Q8gQdr5h8kTE1IfRhgXcsdJdukLFCpN/jAzBeBRDf3j wgsmYoiZ7qLMWnElaC1B9K+wFWwoqmD4E3ljBUi7l0/P8DEbQfht3UY0UBqEZ7XF HYiSQm5OdPfLzg8SaVVthBNSgh6+fhVE3x7nAXSUlGXQUE5lMjCoYOI7TOPrzSkK WHbTRStCJSVK7E+uK+kZW5aVNkidnsl/bcre7joJ5FVZqSUHlSuFTA0sEgtUhQ5O V0xNviITAhlovqFIQD27EiFXjqTqsCHMjZPpEHclSgUrd2fV/ZaNvcSN972sS1j+ e9rxbxCJ+51xKcUyS0C1sHp5qy1xgPuCLb8pSTOeR1+w3D8ZxXpcE0u/msOmycGS GsuZkpjvGQ9RqEQ5NwPtMffI876TVL4Mos5eKvq0ewTWn5tsbQg= =cyFK -----END PGP SIGNATURE----- --yLVHuoLXiP9kZBkt-- From owner-freebsd-current@freebsd.org Mon Sep 16 08:19:11 2019 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 B31C6F8380; Mon, 16 Sep 2019 08:19:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46Wzfk4z4lz4JxH; Mon, 16 Sep 2019 08:19:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x8G8J2sb050233 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 16 Sep 2019 11:19:06 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x8G8J2sb050233 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x8G8J2VX050232; Mon, 16 Sep 2019 11:19:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 16 Sep 2019 11:19:02 +0300 From: Konstantin Belousov To: Peter Jeremy Cc: freebsd-current@FreeBSD.org, freebsd-arm@FreeBSD.org, rmacklem@freebsd.org Subject: Re: "Sleeping with non-sleepable lock" in NFS on recent -current Message-ID: <20190916081902.GU2559@kib.kiev.ua> References: <20190916061205.GE97181@server.rulingia.com> <20190916063252.GS2559@kib.kiev.ua> <20190916074428.GF97181@server.rulingia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190916074428.GF97181@server.rulingia.com> User-Agent: Mutt/1.12.1 (2019-06-15) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-Rspamd-Queue-Id: 46Wzfk4z4lz4JxH X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; FREEMAIL_FROM(0.00)[gmail.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; IP_SCORE_FREEMAIL(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.00)[ip: (-2.72), ipnet: 2001:470::/32(-4.46), asn: 6939(-3.22), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 08:19:11 -0000 On Mon, Sep 16, 2019 at 05:44:28PM +1000, Peter Jeremy wrote: > On 2019-Sep-16 09:32:52 +0300, Konstantin Belousov wrote: > >On Mon, Sep 16, 2019 at 04:12:05PM +1000, Peter Jeremy wrote: > >> I'm consistently seeing panics in the NFS code on recent -current on aarm64. > >> The panics are one of the following two: > >> Sleeping on "vmopar" with the following non-sleepable locks held: > >> exclusive sleep mutex NEWNFSnode lock (NEWNFSnode lock) r = 0 (0xfffffd0078b346f0) locked @ /usr/src/sys/fs/nfsclient/nfs_clport.c:432 > >> > >> Sleeping thread (tid 100077, pid 35) owns a non-sleepable lock > >> > >> Both panics have nearly identical backtraces (see below). I'm running > >> diskless on a Rock64 with both filesystem and swap over NFS. The panics > >> can be fairly reliably triggered by any of: > >> * "make -j4 buildworld" > >> * linking the kernel (as part of buildkernel) > >> * "make installworld" > >> > >> Has anyone else seen this? > ... > > >Weird since this should have been fixed long time ago. Anyway, please > >try the following, it should fix the rest of cases. > > > >diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c > ... > >@@ -540,7 +541,7 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, > > } else { > > np->n_size = vap->va_size; > > np->n_flag |= NSIZECHANGED; > >- vnode_pager_setsize(vp, np->n_size); > >+ setnsize = 1; > > Should this else block include a "nsize = np->n_size;"? Without it, > nsize will remain set to 0, which looks wrong. Yes, you are right. diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c index 471e029a8b5..63ea4736707 100644 --- a/sys/fs/nfsclient/nfs_clport.c +++ b/sys/fs/nfsclient/nfs_clport.c @@ -511,10 +511,10 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, * zero np->n_attrstamp to indicate that * the attributes are stale. */ - vap->va_size = np->n_size; + nsize = vap->va_size = np->n_size; + setnsize = 1; np->n_attrstamp = 0; KDTRACE_NFS_ATTRCACHE_FLUSH_DONE(vp); - vnode_pager_setsize(vp, np->n_size); } else if (np->n_flag & NMODIFIED) { /* * We've modified the file: Use the larger @@ -526,7 +526,8 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, np->n_size = vap->va_size; np->n_flag |= NSIZECHANGED; } - vnode_pager_setsize(vp, np->n_size); + nsize = np->n_size; + setnsize = 1; } else if (vap->va_size < np->n_size) { /* * When shrinking the size, the call to @@ -538,9 +539,9 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, np->n_flag |= NSIZECHANGED; setnsize = 1; } else { - np->n_size = vap->va_size; + nsize = np->n_size = vap->va_size; np->n_flag |= NSIZECHANGED; - vnode_pager_setsize(vp, np->n_size); + setnsize = 1; } } else { np->n_size = vap->va_size; From owner-freebsd-current@freebsd.org Mon Sep 16 10:57:48 2019 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 BC58AFC372; Mon, 16 Sep 2019 10:57:48 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vtr.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46X39l4cDTz4SsC; Mon, 16 Sep 2019 10:57:47 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp239-208.static.internode.on.net [59.167.239.208]) by vtr.rulingia.com (8.15.2/8.15.2) with ESMTPS id x8GAvaEk095455 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 16 Sep 2019 20:57:42 +1000 (AEST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id x8GAvVMt041377 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Sep 2019 20:57:31 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id x8GAvVIt041376; Mon, 16 Sep 2019 20:57:31 +1000 (AEST) (envelope-from peter) Date: Mon, 16 Sep 2019 20:57:31 +1000 From: Peter Jeremy To: Konstantin Belousov Cc: freebsd-current@FreeBSD.org, freebsd-arm@FreeBSD.org, rmacklem@freebsd.org Subject: Re: "Sleeping with non-sleepable lock" in NFS on recent -current Message-ID: <20190916105731.GG97181@server.rulingia.com> References: <20190916061205.GE97181@server.rulingia.com> <20190916063252.GS2559@kib.kiev.ua> <20190916074428.GF97181@server.rulingia.com> <20190916081902.GU2559@kib.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="SO98HVl1bnMOfKZd" Content-Disposition: inline In-Reply-To: <20190916081902.GU2559@kib.kiev.ua> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.12.1 (2019-06-15) X-Rspamd-Queue-Id: 46X39l4cDTz4SsC X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of peter@rulingia.com designates 2001:19f0:5801:ebe:5400:1ff:fe53:30fd as permitted sender) smtp.mailfrom=peter@rulingia.com X-Spamd-Result: default: False [-5.59 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_NA(0.00)[rulingia.com]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; SIGNED_PGP(-2.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:20473, ipnet:2001:19f0:5800::/38, country:US]; RCVD_TLS_ALL(0.00)[]; IP_SCORE(-1.19)[ipnet: 2001:19f0:5800::/38(-4.94), asn: 20473(-0.96), country: US(-0.05)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 10:57:48 -0000 --SO98HVl1bnMOfKZd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2019-Sep-16 11:19:02 +0300, Konstantin Belousov wr= ote: >diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c >index 471e029a8b5..63ea4736707 100644 =2E.. Thanks, that patch seems much more stable. --=20 Peter Jeremy --SO98HVl1bnMOfKZd Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAl1/apNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzSMNg//TNkl8K0zq1no+e3Bdp6/D1oM257DVJIIrU/UqDpPwgXrki+kMwsW/0TL eNhc/W92cHDr59uTh3zvSIuseezV/kkbgN05e4BUBCFb+L1+0cYJnlZqYVYUHroP KVla8UpQsmu6VI8UbcLSMaripwjKGgUvDZpGAb3FGHt2vkUrILoTNd+9kLsp7Joe RdVGveGb7PIdmd305TJEgkuya9CnzTtJHz8mgPAa0xsBI7OjS/sW2PA8Kx1K0gu4 A5OUC2Te6QJORdit10DaRmLSpXVvGPFkDzCLx9+Aoz+vTNNuVYFX/WvsKMpQYbLf ke/uxeu7VxXLcOwnSHHLh5DWwkAc+bq4aSFxP2Eh7rOUwN9Qj1ooraBs3MKyaigY fArXA3kW7W278dYMWqJ2eHi2shBRBGZRVgYV6EBPEfb5LQyhfDoGPEflnpvrIjWq s43tMc6qKIawtf2isPnzUKCkXggInmhjyaej//+qeZuRFic30/LvGrTcy3R4BcCh hEohj0oJHj13Xm+fJFuZCPka+k6zRMlVMHZ56lRYX2v7XduuVXkfdhhNW/vEnGOv WEC04rAPbEqPDp9Rdd8trqdVtOBkIV5qVW5q8i2ivhYdLAA5clvyz9BEksjUgQ20 pGqu408OQGfkqmwl28Zd+kjqFoo1ba03sLKRLXSdHkXJTw13a5c= =zQki -----END PGP SIGNATURE----- --SO98HVl1bnMOfKZd-- From owner-freebsd-current@freebsd.org Mon Sep 16 11:09:38 2019 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 03DF7FC7D0 for ; Mon, 16 Sep 2019 11:09:38 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [60.36.166.23]) by mx1.freebsd.org (Postfix) with ESMTP id 46X3RL4B4dz4TNS for ; Mon, 16 Sep 2019 11:09:33 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc13.plala.or.jp with ESMTP id <20190916110929.XZPO18269.msc13.plala.or.jp@localhost> for ; Mon, 16 Sep 2019 20:09:29 +0900 Date: Mon, 16 Sep 2019 20:09:21 +0900 (JST) Message-Id: <20190916.200921.794188770284180789.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: hang up with r352239 and r352386 with i5-7500 From: Masachika ISHIZUKA X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac13; Mon, 16 Sep 2019 20:09:29 +0900 X-Rspamd-Queue-Id: 46X3RL4B4dz4TNS X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ish@amail.plala.or.jp designates 60.36.166.23 as permitted sender) smtp.mailfrom=ish@amail.plala.or.jp X-Spamd-Result: default: False [0.44 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.65)[-0.651,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:60.36.166.0/24]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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]; NEURAL_HAM_LONG(-0.51)[-0.508,0]; DMARC_NA(0.00)[plala.or.jp]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.39)[ip: (-1.24), ipnet: 60.32.0.0/12(3.00), asn: 4713(0.23), country: JP(-0.02)]; RCVD_NO_TLS_LAST(0.10)[]; RCVD_IN_DNSWL_LOW(-0.10)[23.166.36.60.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4713, ipnet:60.32.0.0/12, country:JP]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 11:09:38 -0000 Hi. My machine (with core i5-7500) is hangup when loading i915kms.ko on r352239 and r352386 (1300047). This machine was working good with r351728 (1300044). /etc/rc.conf has the following line. kld_list="i915kms.ko" It is good wowking with core i7-4500U on r352239 (1300047). -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Mon Sep 16 11:24:22 2019 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 6A1F2FCFB2 for ; Mon, 16 Sep 2019 11:24:22 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::25]) (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 46X3mQ0mZkz4Vr6 for ; Mon, 16 Sep 2019 11:24:22 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 46X3mG54LXz3c7b for ; Mon, 16 Sep 2019 11:24:14 +0000 (UTC) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([IPv6:::1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [IPv6:::1]) (amavisd-new, port 10587) with ESMTPS id At0yc0vCEJux for ; Mon, 16 Sep 2019 11:24:13 +0000 (UTC) Received: from garnet.daemonic.se (host-90-233-140-120.mobileonline.telia.com [90.233.140.120]) by mail.daemonic.se (Postfix) with ESMTPSA id 46X3mF4bWQz3c7Z for ; Mon, 16 Sep 2019 11:24:13 +0000 (UTC) Subject: Re: hang up with r352239 and r352386 with i5-7500 To: freebsd-current@freebsd.org References: <20190916.200921.794188770284180789.ish@amail.plala.or.jp> From: Niclas Zeising Message-ID: Date: Mon, 16 Sep 2019 13:24:12 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.0 MIME-Version: 1.0 In-Reply-To: <20190916.200921.794188770284180789.ish@amail.plala.or.jp> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46X3mQ0mZkz4Vr6 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-2.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:36236, ipnet:2607:f740:d::/48, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 11:24:22 -0000 On 2019-09-16 13:09, Masachika ISHIZUKA wrote: > Hi. > > My machine (with core i5-7500) is hangup when loading i915kms.ko > on r352239 and r352386 (1300047). > This machine was working good with r351728 (1300044). > > /etc/rc.conf has the following line. > kld_list="i915kms.ko" > > It is good wowking with core i7-4500U on r352239 (1300047). > Hi! Which version of drm-current are you using? Have you recompiled it after updating the kernel? What happens if you change to kld_list="/boot/modules/i915kms.ko"? There is a patch here: https://github.com/FreeBSDDesktop/kms-drm/pull/175/commits/7b8fab2461262b22f64425146b60608bb0e0240d that might solve the issue, can you apply that and recompile drm-current-kmod and see if it works? Thanks! Regards -- Niclas Zeising From owner-freebsd-current@freebsd.org Mon Sep 16 11:55:50 2019 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 86CC1FDF34 for ; Mon, 16 Sep 2019 11:55:50 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [60.36.166.23]) by mx1.freebsd.org (Postfix) with ESMTP id 46X4Sg6BMqz4XqY for ; Mon, 16 Sep 2019 11:55:46 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc13.plala.or.jp with ESMTP id <20190916115544.YBOK18269.msc13.plala.or.jp@localhost> for ; Mon, 16 Sep 2019 20:55:44 +0900 Date: Mon, 16 Sep 2019 20:55:32 +0900 (JST) Message-Id: <20190916.205532.1314832713594158104.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: panic: sleeping thread on r352386 From: Masachika ISHIZUKA X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac13; Mon, 16 Sep 2019 20:55:44 +0900 X-Rspamd-Queue-Id: 46X4Sg6BMqz4XqY X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ish@amail.plala.or.jp designates 60.36.166.23 as permitted sender) smtp.mailfrom=ish@amail.plala.or.jp X-Spamd-Result: default: False [0.75 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.51)[-0.506,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:60.36.166.0/24]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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]; NEURAL_HAM_LONG(-0.36)[-0.355,0]; DMARC_NA(0.00)[plala.or.jp]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.41)[ip: (-1.16), ipnet: 60.32.0.0/12(3.00), asn: 4713(0.23), country: JP(-0.02)]; RCVD_NO_TLS_LAST(0.10)[]; RCVD_IN_DNSWL_LOW(-0.10)[23.166.36.60.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4713, ipnet:60.32.0.0/12, country:JP]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 11:55:50 -0000 Hi. This panic happens on 1300047 (both r352239 and r352386) with core i5-7500 as follows. This panic dose not happen on r351728 (1300044). (The following lines were typed by hand so they might have some miss typed letters.) == Sleeping thread (tid 100177, pid 1814) owns a non-sleepable lock KDB: stack backtrace of thread 100177: sched_switch() at sched_switch+0x3f0/frame 0xfffffe008bc0e590 mi_switch() at mi_switch+0x172/frame 0xfffffe008bc0e5c0 sleepq_switch() at sleepq_switch+0x110/frame 0xfffffe008bc0e600 sleepQ-wait() at sleepq_wait+0x43/frame 0xfffffe008bc0e630 vm_page_sleep_if_busy() at (snip) vm_object_page_remove() at (snip) vnode_pager_setsize() at (snip) nfscl_loadattrcache() at (snip) ncl_writerpc() at (snip) ncl_doio() at (snip) nfssvc_iod() at (snip) fork_exit() at (snip) fork_trampoline() at (snip) --- trap 0, rip = 0, rsp = 0, rbp = 0 --- panic: sleeping thread cpuid = 3 time = 1568633100 KBD: stack backtrace: db_trace_self_wrapper() at (snip) vpanic() at (snip) (snip) --- trap 0, rip = 0, rsp = 0, rbp = 0 --- KDB: enter : panic [ thread pid 2108 tid 100236 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db> -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Mon Sep 16 12:26:20 2019 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 F108FFF063 for ; Mon, 16 Sep 2019 12:26:20 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [60.36.166.23]) by mx1.freebsd.org (Postfix) with ESMTP id 46X57t0gkRz4ZQt for ; Mon, 16 Sep 2019 12:26:17 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc13.plala.or.jp with ESMTP id <20190916122614.YCMF18269.msc13.plala.or.jp@localhost> for ; Mon, 16 Sep 2019 21:26:14 +0900 Date: Mon, 16 Sep 2019 21:26:08 +0900 (JST) Message-Id: <20190916.212608.705565847837928740.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: hang up with r352239 and r352386 with i5-7500 From: Masachika ISHIZUKA In-Reply-To: References: <20190916.200921.794188770284180789.ish@amail.plala.or.jp> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac13; Mon, 16 Sep 2019 21:26:14 +0900 X-Rspamd-Queue-Id: 46X57t0gkRz4ZQt X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ish@amail.plala.or.jp designates 60.36.166.23 as permitted sender) smtp.mailfrom=ish@amail.plala.or.jp X-Spamd-Result: default: False [0.66 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.56)[-0.557,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:60.36.166.0/24]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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]; NEURAL_HAM_LONG(-0.41)[-0.410,0]; DMARC_NA(0.00)[plala.or.jp]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.42)[ip: (-1.09), ipnet: 60.32.0.0/12(3.00), asn: 4713(0.23), country: JP(-0.02)]; RCVD_NO_TLS_LAST(0.10)[]; RCVD_IN_DNSWL_LOW(-0.10)[23.166.36.60.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4713, ipnet:60.32.0.0/12, country:JP]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 12:26:21 -0000 >> My machine (with core i5-7500) is hangup when loading i915kms.ko >> on r352239 and r352386 (1300047). >> This machine was working good with r351728 (1300044). >> /etc/rc.conf has the following line. >> kld_list="i915kms.ko" >> It is good wowking with core i7-4500U on r352239 (1300047). >> > > Hi! > Which version of drm-current are you using? Thank you for reply. % pkg info drm-current-kmod drm-current-kmod-4.16.g20190828 Name : drm-current-kmod Version : 4.16.g20190828 Installed on : Mon Sep 2 14:42:56 2019 JST Origin : graphics/drm-current-kmod Architecture : FreeBSD:13:amd64 Prefix : /usr/local Categories : graphics kld Licenses : BSD2CLAUSE, MIT, GPLv2 Maintainer : x11@FreeBSD.org WWW : https://github.com/FreeBSDDesktop/kms-drm Comment : DRM modules for the linuxkpi-based KMS components Options : DEBUG : off SOURCE : on Annotations : FreeBSD_version: 1300042 repo_type : binary repository : FreeBSD Flat size : 122MiB Description : amdgpu, i915, and radeon DRM modules for the linuxkpi-based KMS components. Currently corresponding to Linux 4.16 DRM. This version is for FreeBSD CURRENT. amdgpu and radeonkms are known to fail with EFI boot. WWW: https://github.com/FreeBSDDesktop/kms-drm > Have you recompiled it after updating the kernel? No. > What happens if you change to kld_list="/boot/modules/i915kms.ko"? The same hangup has occured. > There is a patch here: > https://github.com/FreeBSDDesktop/kms-drm/pull/175/commits/7b8fab2461262b22f64425146b60608bb0e0240d > that might solve the issue, can you apply that and recompile > drm-current-kmod and see if it works? Thank you. I did the following. # portsnap fetch # portsnap update # cd /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/linux # vi pagevec.h (comment out line 49) # cd /usr/ports/graphics/drm-current-kmod # make # make deinstall # make install # reboot But, it hangs up. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Mon Sep 16 12:41:25 2019 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 583D7FF8C9 for ; Mon, 16 Sep 2019 12:41:25 +0000 (UTC) (envelope-from trond.endrestol@ximalas.info) Received: from enterprise.ximalas.info (enterprise.ximalas.info [IPv6:2001:700:1100:1::8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ximalas.info", Issuer "Hostmaster ximalas.info" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46X5TJ1CX1z4bTt for ; Mon, 16 Sep 2019 12:41:23 +0000 (UTC) (envelope-from trond.endrestol@ximalas.info) Received: from enterprise.ximalas.info (Ximalas@localhost [127.0.0.1]) by enterprise.ximalas.info (8.15.2/8.15.2) with ESMTPS id x8GCfBST020391 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 16 Sep 2019 14:41:11 +0200 (CEST) (envelope-from trond.endrestol@ximalas.info) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ximalas.info; s=default; t=1568637671; bh=nGg1qLTWJ0I/4nD2yhkbMutbQ1moyaDhiTrtrOxGaUk=; h=Date:From:To:Subject:In-Reply-To:References; b=L7AoylqGA9O8urpy1isItIDNHMJQiBsKPahuJYDqD7mdkORlQ3sqUXzQJIj5dRH+6 PFb8JZuDmzltno6B0nBc/7u8Q3Wm1cPf0ligK2co82uMgKk1YKYzKTwve/vBXog5Qs HMHVOWf65qIPK9Hhz+jvxj9j4zZhtn8eATO2mKuKLwleJdNcce3ANfayaCz3DJPKc0 wRcmFFBboc1I3HNdIRGSsPQUxqwZxrTSzNCPrZ8UanHZJKp/5odsMgu0BAFFVwj3/Q Zw38mpGAOxPkZLUmn15yCFNxs1iokDYE6hdYRfQrRU2NyaNTk2rDOz+lhCwMfueY6E gDDEIShE68+Gw== Received: from localhost (trond@localhost) by enterprise.ximalas.info (8.15.2/8.15.2/Submit) with ESMTP id x8GCfBrU020388 for ; Mon, 16 Sep 2019 14:41:11 +0200 (CEST) (envelope-from trond.endrestol@ximalas.info) X-Authentication-Warning: enterprise.ximalas.info: trond owned process doing -bs Date: Mon, 16 Sep 2019 14:41:11 +0200 (CEST) From: =?UTF-8?Q?Trond_Endrest=C3=B8l?= Sender: Trond.Endrestol@ximalas.info To: freebsd-current@freebsd.org Subject: Re: hang up with r352239 and r352386 with i5-7500 In-Reply-To: <20190916.200921.794188770284180789.ish@amail.plala.or.jp> Message-ID: References: <20190916.200921.794188770284180789.ish@amail.plala.or.jp> User-Agent: Alpine 2.21.99999 (BSF 352 2019-06-22) OpenPGP: url=http://ximalas.info/about/tronds-openpgp-public-key MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-1.2 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on enterprise.ximalas.info X-Rspamd-Queue-Id: 46X5TJ1CX1z4bTt X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ximalas.info header.s=default header.b=L7AoylqG; dmarc=pass (policy=none) header.from=ximalas.info; spf=pass (mx1.freebsd.org: domain of trond.endrestol@ximalas.info designates 2001:700:1100:1::8 as permitted sender) smtp.mailfrom=trond.endrestol@ximalas.info X-Spamd-Result: default: False [-4.75 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[ximalas.info:s=default]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[ximalas.info:+]; DMARC_POLICY_ALLOW(-0.50)[ximalas.info,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:224, ipnet:2001:700::/32, country:NO]; IP_SCORE(-1.75)[ip: (-7.44), ipnet: 2001:700::/32(-0.76), asn: 224(-0.52), country: NO(-0.01)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 12:41:25 -0000 On Mon, 16 Sep 2019 20:09+0900, Masachika ISHIZUKA wrote: > My machine (with core i5-7500) is hangup when loading i915kms.ko > on r352239 and r352386 (1300047). > This machine was working good with r351728 (1300044). > > /etc/rc.conf has the following line. > kld_list="i915kms.ko" Pardon the intrusion. What happens if you add drm2.ko and/or switch to absolute paths? This is what I had to put in my /etc/rc.conf for a Dell Latitude E5530 to get rid of the message of drm2 being deprecated: kld_list="/boot/modules/drm2.ko /boot/modules/i915kms.ko" -- Trond. From owner-freebsd-current@freebsd.org Mon Sep 16 12:59:20 2019 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 E58CD12126E; Mon, 16 Sep 2019 12:59:20 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46X5sz1ghQz4cp0; Mon, 16 Sep 2019 12:59:18 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id eba026e8; Mon, 16 Sep 2019 14:52:37 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=230sT31NTO66+F+rpwyc5quFteY=; b=T5kY7PtP/8Efq8IEGwIer5JXI+X/ C05Or10dxq+xhsfvNmhnF8YHbUUn1s6IaGz3wGMTJ2K7HVZ9jdo0TDd9B3ZzsKyp skxkRrMqvRiG06Rp9hMR6VBwzZxFrbGY+ghxhN3+QtsNFjW85bfzoRqgVGm0NEWV a6yQG3eBGLY/6ZI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=S0+SMl/c2Oo3mFRG7o+8AMwC/2wBz1Jv1YTZpDOq10ML3iwLLYirACMo 43Mypm5oxUEBOaeEV4t5YAYBCPgQhr4VKX/Tvbv3DhMAEMLpl9Br8XRr16spKevN wIyOSPtjedEqtSyJZsSSLZEjMqkgP2F0Cne6QjjZeMHLzIxB48I= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id b5ea77a6 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 16 Sep 2019 14:52:37 +0200 (CEST) Date: Mon, 16 Sep 2019 14:52:37 +0200 From: Emmanuel Vadot To: mj-mailinglist@gmx.de Cc: manu@FreeBSD.org, freebsd-current@freebsd.org, freebsd-pkgbase@freebsd.org Subject: Re: svn commit: r351858 - in head: bin/uuidgen ... Message-Id: <20190916145237.f478506d1064b1349ca59376@bidouilliste.com> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46X5sz1ghQz4cp0 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mail header.b=T5kY7PtP; dmarc=none; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.177.182 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [-1.43 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mail]; NEURAL_HAM_MEDIUM(-0.90)[-0.904,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:212.83.177.182/32]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[bidouilliste.com]; NEURAL_HAM_LONG(-0.99)[-0.994,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; FREEMAIL_TO(0.00)[gmx.de]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.37)[ip: (-0.81), ipnet: 212.83.160.0/19(2.52), asn: 12876(0.13), country: FR(-0.00)]; ASN(0.00)[asn:12876, ipnet:212.83.160.0/19, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 12:59:21 -0000 On Sat, 14 Sep 2019 19:41:06 +0200 mj-mailinglist@gmx.de wrote: > Building a jail from pkgbase packages after base r351858 shows this cap_mkdb message: > > to create the jail this command is used: > > pkg --rootdir /jails/test01 -o 'ASSUME_ALWAYS_YES=true' -o 'ABI=FreeBSD:13:amd64' install --repository FreeBSD-base FreeBSD-utilities FreeBSD-rc > (note: FreeBSD-base is the repository name, not a package) > > ... > Checking integrity... done (0 conflicting) > [1/20] Installing FreeBSD-clibs-13.0.s20190914152450... > [1/20] Extracting FreeBSD-clibs-13.0.s20190914152450: .......... done > [2/20] Installing FreeBSD-runtime-13.0.s20190914152450... > [2/20] Extracting FreeBSD-runtime-13.0.s20190914152450: .......... done > cap_mkdb: file argument: No such file or directory > [3/20] Installing FreeBSD-utilities-13.0.s20190914152450... > [3/20] Extracting FreeBSD-utilities-13.0.s20190914152450: .......... done > [4/20] Installing FreeBSD-rc-13.0.s20190914152450... > [4/20] Extracting FreeBSD-rc-13.0.s20190914152450: .......... done > ... > > This happens, after the login.conf file was moved into the Freebsd-utilities package. > The order in which the packages are installed is problematic, since cap_mkdb is executed in step 2, the FreeBSD-runtime package installation, > but the login.conf file is installed in step 3, the FreeBSD-utilities. > > > I opened a bugreport: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240582 > > -- > Martin Hi, thanks for the report, it's now fixed in r352389. -- Emmanuel Vadot From owner-freebsd-current@freebsd.org Mon Sep 16 13:13:38 2019 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 D6BA81218D4 for ; Mon, 16 Sep 2019 13:13:38 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc12.plala.or.jp (msc12.plala.or.jp [60.36.166.22]) by mx1.freebsd.org (Postfix) with ESMTP id 46X6BS4JFmz4dp3 for ; Mon, 16 Sep 2019 13:13:35 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc12.plala.or.jp with ESMTP id <20190916131333.ULZR7266.msc12.plala.or.jp@localhost> for ; Mon, 16 Sep 2019 22:13:33 +0900 Date: Mon, 16 Sep 2019 22:13:25 +0900 (JST) Message-Id: <20190916.221325.337673385995140028.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: hang up with r352239 and r352386 with i5-7500 From: Masachika ISHIZUKA In-Reply-To: References: <20190916.200921.794188770284180789.ish@amail.plala.or.jp> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac12; Mon, 16 Sep 2019 22:13:33 +0900 X-Rspamd-Queue-Id: 46X6BS4JFmz4dp3 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ish@amail.plala.or.jp designates 60.36.166.22 as permitted sender) smtp.mailfrom=ish@amail.plala.or.jp X-Spamd-Result: default: False [2.03 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.07)[-0.067,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:60.36.166.0/24]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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]; DMARC_NA(0.00)[plala.or.jp]; MV_CASE(0.50)[]; NEURAL_SPAM_LONG(0.26)[0.261,0]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.64)[ipnet: 60.32.0.0/12(2.99), asn: 4713(0.23), country: JP(-0.02)]; RCVD_NO_TLS_LAST(0.10)[]; RCVD_IN_DNSWL_LOW(-0.10)[22.166.36.60.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4713, ipnet:60.32.0.0/12, country:JP]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 13:13:38 -0000 >> My machine (with core i5-7500) is hangup when loading i915kms.ko >> on r352239 and r352386 (1300047). >> This machine was working good with r351728 (1300044). >> >> /etc/rc.conf has the following line. >> kld_list="i915kms.ko" > > Pardon the intrusion. > What happens if you add drm2.ko and/or switch to absolute paths? > > This is what I had to put in my /etc/rc.conf for a Dell Latitude > E5530 to get rid of the message of drm2 being deprecated: > > kld_list="/boot/modules/drm2.ko /boot/modules/i915kms.ko" Hi. Thank you for mail. I'm using 13-current and it has no longer drm2.ko. This machine was working good on r351728 as follows. r351728% kldstat Id Refs Address Size Name 1 90 0xffffffff80200000 2336bb0 kernel 2 1 0xffffffff82537000 7278 ums.ko 3 1 0xffffffff82ef9000 aa70 tmpfs.ko 4 1 0xffffffff82f04000 4fb8 linprocfs.ko 5 4 0xffffffff82f09000 3d70 linux_common.ko 6 1 0xffffffff82f0d000 24fe linsysfs.ko 7 1 0xffffffff82f10000 12eb90 i915kms.ko 8 1 0xffffffff8303f000 77e90 drm.ko 9 4 0xffffffff830b7000 125f0 linuxkpi.ko 10 2 0xffffffff830ca000 13f30 linuxkpi_gplv2.ko 11 2 0xffffffff830de000 8e0 lindebugfs.ko 12 1 0xffffffff830df000 240d i915_kbl_dmc_ver1_04_bin.ko 13 1 0xffffffff830e2000 a218 if_lagg.ko 14 1 0xffffffff830ed000 3f00 ng_ubt.ko 15 6 0xffffffff830f1000 a998 netgraph.ko 16 2 0xffffffff830fc000 9378 ng_hci.ko 17 3 0xffffffff83106000 9c0 ng_bluetooth.ko 18 1 0xffffffff83107000 c890 snd_uaudio.ko 19 1 0xffffffff83114000 1840 uhid.ko 20 1 0xffffffff83116000 1b00 wmt.ko 21 1 0xffffffff83118000 d560 ng_l2cap.ko 22 1 0xffffffff83126000 19900 ng_btsocket.ko 23 1 0xffffffff83140000 2100 ng_socket.ko 24 1 0xffffffff83143000 263b0 ipfw.ko 25 1 0xffffffff8316a000 3c960 linux.ko 26 1 0xffffffff831a7000 34b70 linux64.ko 27 1 0xffffffff831dc000 45a0 autofs.ko 28 1 0xffffffff831e1000 acf mac_ntpd.ko -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Mon Sep 16 14:03:05 2019 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 4B240122D93 for ; Mon, 16 Sep 2019 14:03:05 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::25]) (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 46X7HX6hdQz3Cmp for ; Mon, 16 Sep 2019 14:03:04 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 46X7HT3HpHz3lBR; Mon, 16 Sep 2019 14:03:01 +0000 (UTC) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([IPv6:::1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [IPv6:::1]) (amavisd-new, port 10587) with ESMTPS id aF00mdcoWcyl; Mon, 16 Sep 2019 14:03:00 +0000 (UTC) Received: from garnet.daemonic.se (host-90-233-140-120.mobileonline.telia.com [90.233.140.120]) by mail.daemonic.se (Postfix) with ESMTPSA id 46X7HS2BQbz3lBP; Mon, 16 Sep 2019 14:03:00 +0000 (UTC) Subject: Re: hang up with r352239 and r352386 with i5-7500 To: Masachika ISHIZUKA , freebsd-current@freebsd.org References: <20190916.200921.794188770284180789.ish@amail.plala.or.jp> <20190916.221325.337673385995140028.ish@amail.plala.or.jp> From: Niclas Zeising Message-ID: <3a5c3efe-4598-66ae-7e3f-a54c1dc8c2e8@freebsd.org> Date: Mon, 16 Sep 2019 16:02:56 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.0 MIME-Version: 1.0 In-Reply-To: <20190916.221325.337673385995140028.ish@amail.plala.or.jp> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46X7HX6hdQz3Cmp X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-2.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:36236, ipnet:2607:f740:d::/48, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 14:03:05 -0000 On 2019-09-16 15:13, Masachika ISHIZUKA wrote: >>> My machine (with core i5-7500) is hangup when loading i915kms.ko >>> on r352239 and r352386 (1300047). >>> This machine was working good with r351728 (1300044). >>> >>> /etc/rc.conf has the following line. >>> kld_list="i915kms.ko" >> >> Pardon the intrusion. >> What happens if you add drm2.ko and/or switch to absolute paths? >> >> This is what I had to put in my /etc/rc.conf for a Dell Latitude >> E5530 to get rid of the message of drm2 being deprecated: >> >> kld_list="/boot/modules/drm2.ko /boot/modules/i915kms.ko" > > Hi. > > Thank you for mail. > I'm using 13-current and it has no longer drm2.ko. > This machine was working good on r351728 as follows. > > r351728% kldstat > Id Refs Address Size Name > 1 90 0xffffffff80200000 2336bb0 kernel > 2 1 0xffffffff82537000 7278 ums.ko > 3 1 0xffffffff82ef9000 aa70 tmpfs.ko > 4 1 0xffffffff82f04000 4fb8 linprocfs.ko > 5 4 0xffffffff82f09000 3d70 linux_common.ko > 6 1 0xffffffff82f0d000 24fe linsysfs.ko > 7 1 0xffffffff82f10000 12eb90 i915kms.ko > 8 1 0xffffffff8303f000 77e90 drm.ko > 9 4 0xffffffff830b7000 125f0 linuxkpi.ko > 10 2 0xffffffff830ca000 13f30 linuxkpi_gplv2.ko > 11 2 0xffffffff830de000 8e0 lindebugfs.ko > 12 1 0xffffffff830df000 240d i915_kbl_dmc_ver1_04_bin.ko > 13 1 0xffffffff830e2000 a218 if_lagg.ko > 14 1 0xffffffff830ed000 3f00 ng_ubt.ko > 15 6 0xffffffff830f1000 a998 netgraph.ko > 16 2 0xffffffff830fc000 9378 ng_hci.ko > 17 3 0xffffffff83106000 9c0 ng_bluetooth.ko > 18 1 0xffffffff83107000 c890 snd_uaudio.ko > 19 1 0xffffffff83114000 1840 uhid.ko > 20 1 0xffffffff83116000 1b00 wmt.ko > 21 1 0xffffffff83118000 d560 ng_l2cap.ko > 22 1 0xffffffff83126000 19900 ng_btsocket.ko > 23 1 0xffffffff83140000 2100 ng_socket.ko > 24 1 0xffffffff83143000 263b0 ipfw.ko > 25 1 0xffffffff8316a000 3c960 linux.ko > 26 1 0xffffffff831a7000 34b70 linux64.ko > 27 1 0xffffffff831dc000 45a0 autofs.ko > 28 1 0xffffffff831e1000 acf mac_ntpd.ko > Hi! Can you please use absolute paths to i915kms.ko anyway, just to test? Thanks! Regards -- Niclas Zeising From owner-freebsd-current@freebsd.org Mon Sep 16 14:07:10 2019 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 9EE8B1230D5 for ; Mon, 16 Sep 2019 14:07:10 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [IPv6:2400:7800:0:502e::23]) by mx1.freebsd.org (Postfix) with ESMTP id 46X7NC1kb5z3D7Y for ; Mon, 16 Sep 2019 14:07:06 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc13.plala.or.jp with ESMTP id <20190916140656.YGHL18269.msc13.plala.or.jp@localhost> for ; Mon, 16 Sep 2019 23:06:56 +0900 Date: Mon, 16 Sep 2019 23:06:42 +0900 (JST) Message-Id: <20190916.230642.762794847379060930.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: hang up with r352239 and r352386 with i5-7500 From: Masachika ISHIZUKA In-Reply-To: <3a5c3efe-4598-66ae-7e3f-a54c1dc8c2e8@freebsd.org> References: <20190916.221325.337673385995140028.ish@amail.plala.or.jp> <3a5c3efe-4598-66ae-7e3f-a54c1dc8c2e8@freebsd.org> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac13; Mon, 16 Sep 2019 23:06:56 +0900 X-Rspamd-Queue-Id: 46X7NC1kb5z3D7Y X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ish@amail.plala.or.jp designates 2400:7800:0:502e::23 as permitted sender) smtp.mailfrom=ish@amail.plala.or.jp X-Spamd-Result: default: False [-0.56 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.94)[-0.936,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2400:7800:0:502e::/60]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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]; NEURAL_HAM_LONG(-0.94)[-0.943,0]; DMARC_NA(0.00)[plala.or.jp]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.01)[ipnet: 2400:7800::/32(-0.14), asn: 4713(0.23), country: JP(-0.02)]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4713, ipnet:2400:7800::/32, country:JP]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 14:07:10 -0000 > Can you please use absolute paths to i915kms.ko anyway, just to test? The same hang up occure with kld_list="/boot/modules/i915kms.ko" in /etc/rc.conf. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Mon Sep 16 14:08:17 2019 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 6550212321D for ; Mon, 16 Sep 2019 14:08:17 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::25]) (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 46X7PY246yz3DPt for ; Mon, 16 Sep 2019 14:08:17 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 46X7PW6sd6z3c7b; Mon, 16 Sep 2019 14:08:15 +0000 (UTC) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([127.0.0.1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [127.0.0.1]) (amavisd-new, port 10587) with ESMTPS id cK9R_H0dr9UD; Mon, 16 Sep 2019 14:08:15 +0000 (UTC) Received: from garnet.daemonic.se (host-90-233-140-120.mobileonline.telia.com [90.233.140.120]) by mail.daemonic.se (Postfix) with ESMTPSA id 46X7PW0H4gz3c7Z; Mon, 16 Sep 2019 14:08:14 +0000 (UTC) Subject: Re: hang up with r352239 and r352386 with i5-7500 To: Masachika ISHIZUKA , freebsd-current@freebsd.org References: <20190916.221325.337673385995140028.ish@amail.plala.or.jp> <3a5c3efe-4598-66ae-7e3f-a54c1dc8c2e8@freebsd.org> <20190916.230642.762794847379060930.ish@amail.plala.or.jp> From: Niclas Zeising Message-ID: <746a0593-3dad-e3f5-53db-994c9a058233@freebsd.org> Date: Mon, 16 Sep 2019 16:08:14 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.0 MIME-Version: 1.0 In-Reply-To: <20190916.230642.762794847379060930.ish@amail.plala.or.jp> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46X7PY246yz3DPt X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-2.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:36236, ipnet:2607:f740:d::/48, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 14:08:17 -0000 On 2019-09-16 16:06, Masachika ISHIZUKA wrote: >> Can you please use absolute paths to i915kms.ko anyway, just to test? > > The same hang up occure with kld_list="/boot/modules/i915kms.ko" > in /etc/rc.conf. > Even after applying the patch I suggested? Regards -- Niclas Zeising From owner-freebsd-current@freebsd.org Mon Sep 16 14:41:33 2019 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 334C41241C9 for ; Mon, 16 Sep 2019 14:41:33 +0000 (UTC) (envelope-from agh@fastmail.fm) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 46X87v5l04z3Gg4 for ; Mon, 16 Sep 2019 14:41:31 +0000 (UTC) (envelope-from agh@fastmail.fm) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 8A6A92067B; Mon, 16 Sep 2019 10:41:30 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 16 Sep 2019 10:41:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= from:to:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm1; bh= 9ROdt0LP2LwaNx5Ru2BqMuf1sHjadRqgEnPZa/ZJp7w=; b=WjzcPWJv9eG/VIoi pXZZOSS+zqvguFsWSgTxgEZMKWoWFsXreQ1kkKPL9tX2GdkhRW0jm2EzVP5hyiBA jpWZA4nGb6Z4vcSHVpynoqx3sYQTj+wgUWSAnFXDgRRkoG2EVr84hUUkS7+younP F1WKyn8z8c2BKNyWp5RxQ5engDrIrLe/QSS46eJ41QwbAGP/ui/swHNJDkC0rBMY bFhUvsvAUgean4pLDpVczDH7n5JZPM6cKesUMz9z5qYWE9UVkdZL02z8/maeIY21 r/n1XID2JKlvfBPlo3evmBwCkN588liNdK+Q6ShUR7xa2ZMKsPmNq3/RVDh9+Nuz XdBj/w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=9ROdt0LP2LwaNx5Ru2BqMuf1sHjadRqgEnPZa/ZJp 7w=; b=T2s1Wx2AeTkK2lArqHr18WCx+lrPEA2Fd2mKUCW/mHF7g5s9Z+InZFIHO SdPiLrg+4at0o6Xks8eQ2Ir2vn7Zh1kKR69RyBmPcjMJ5QCljkQZkI8dYTiiG+Rc k727lCxi2eAakQE1GFUVwy56rVKYBky09aQIwaCLLhzsT0gk0cTdQ8+c9ezs7pKA rdV7Sy0sSSLRq6wWD1NJweejka53mfIqL5Mk2m24O7hiPNFQ7C0pWXA+NBSdfvll R4UmPIuxyZvHEpMd+d2tDK6eFgw82gVQztj5Ksw0yaQ7qAmUmvZEitPG764nGooL q9kk4uLY00q5COaV5m6qlwtY62ZiQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudefgdektdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhgggfgtsehtufertd dttddvnecuhfhrohhmpeetlhgrshhtrghirhcujfhoghhgvgcuoegrghhhsehfrghsthhm rghilhdrfhhmqeenucffohhmrghinhepfhhrvggvsghsugdrohhrghenucfkphepudduhe drjedtrdeltddrudelleenucfrrghrrghmpehmrghilhhfrhhomheprghghhesfhgrshht mhgrihhlrdhfmhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from direwolf.local. (199.90.70.115.static.exetel.com.au [115.70.90.199]) by mail.messagingengine.com (Postfix) with ESMTPA id 98E8CD60057 for ; Mon, 16 Sep 2019 10:41:29 -0400 (EDT) From: Alastair Hogge To: freebsd-current@freebsd.org Subject: Re: panic: sleeping thread on r352386 Date: Mon, 16 Sep 2019 22:41:11 +0800 Message-ID: <16601631.sFgvYJuXru@direwolf.local.> In-Reply-To: <20190916.205532.1314832713594158104.ish@amail.plala.or.jp> References: <20190916.205532.1314832713594158104.ish@amail.plala.or.jp> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 46X87v5l04z3Gg4 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=fastmail.fm header.s=fm1 header.b=WjzcPWJv; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=T2s1Wx2A; dmarc=pass (policy=none) header.from=fastmail.fm; spf=pass (mx1.freebsd.org: domain of agh@fastmail.fm designates 66.111.4.25 as permitted sender) smtp.mailfrom=agh@fastmail.fm X-Spamd-Result: default: False [-3.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.25]; FREEMAIL_FROM(0.00)[fastmail.fm]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[fastmail.fm:+,messagingengine.com:+]; DMARC_POLICY_ALLOW(-0.50)[fastmail.fm,none]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_LOW(-0.10)[25.4.111.66.list.dnswl.org : 127.0.5.1]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; CTE_CASE(0.50)[]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[fastmail.fm]; R_DKIM_ALLOW(-0.20)[fastmail.fm:s=fm1,messagingengine.com:s=fm3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[fastmail.fm.dwl.dnswl.org : 127.0.5.1]; IP_SCORE(0.00)[ip: (-9.75), ipnet: 66.111.4.0/24(-4.85), asn: 11403(-2.68), country: US(-0.05)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 14:41:33 -0000 On Monday, 16 September 2019 7:55:32 PM AWST Masachika ISHIZUKA wrote: > Hi. > > This panic happens on 1300047 (both r352239 and r352386) with core > i5-7500 as follows. This panic dose not happen on r351728 (1300044). > (The following lines were typed by hand so they might have some miss > typed letters.) > > == > Sleeping thread (tid 100177, pid 1814) owns a non-sleepable lock > KDB: stack backtrace of thread 100177: [removed backtrace] https://svnweb.freebsd.org/base?view=revision&revision=352393 From owner-freebsd-current@freebsd.org Mon Sep 16 22:20:55 2019 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 41059EE3D0 for ; Mon, 16 Sep 2019 22:20:55 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [IPv6:2400:7800:0:502e::23]) by mx1.freebsd.org (Postfix) with ESMTP id 46XLKw1CTNz4DSw for ; Mon, 16 Sep 2019 22:20:51 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc13.plala.or.jp with ESMTP id <20190916222047.ZKPN18269.msc13.plala.or.jp@localhost> for ; Tue, 17 Sep 2019 07:20:47 +0900 Date: Tue, 17 Sep 2019 07:20:41 +0900 (JST) Message-Id: <20190917.072041.480458056274937279.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: hang up with r352239 and r352386 with i5-7500 From: Masachika ISHIZUKA In-Reply-To: <746a0593-3dad-e3f5-53db-994c9a058233@freebsd.org> References: <3a5c3efe-4598-66ae-7e3f-a54c1dc8c2e8@freebsd.org> <20190916.230642.762794847379060930.ish@amail.plala.or.jp> <746a0593-3dad-e3f5-53db-994c9a058233@freebsd.org> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac13; Tue, 17 Sep 2019 07:20:47 +0900 X-Rspamd-Queue-Id: 46XLKw1CTNz4DSw X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ish@amail.plala.or.jp designates 2400:7800:0:502e::23 as permitted sender) smtp.mailfrom=ish@amail.plala.or.jp X-Spamd-Result: default: False [-0.55 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.92)[-0.922,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2400:7800:0:502e::/60]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.95)[-0.947,0]; DMARC_NA(0.00)[plala.or.jp]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.01)[ipnet: 2400:7800::/32(-0.14), asn: 4713(0.23), country: JP(-0.02)]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4713, ipnet:2400:7800::/32, country:JP]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 16 Sep 2019 22:20:55 -0000 > On 2019-09-16 16:06, Masachika ISHIZUKA wrote: >>> Can you please use absolute paths to i915kms.ko anyway, just to test? >> The same hang up occure with kld_list="/boot/modules/i915kms.ko" >> in /etc/rc.conf. >> > > Even after applying the patch I suggested? Yes. kld_list="/boot/modules/drm.ko /boot/modules/i915kms.ko" will hang as well. /boot/modules/{drm,i915kms}.ko is patched modules. # /boot/kernel.r352239/{drm,i915kms}.ko is not patched. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Tue Sep 17 05:30:20 2019 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 510C5F7C31 for ; Tue, 17 Sep 2019 05:30:20 +0000 (UTC) (envelope-from kiri@truefc.org) Received: from kx.truefc.org (flets-sg1026.kamome.or.jp [202.216.24.26]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp", Issuer "smtp" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46XWsR3PrCz4XbN for ; Tue, 17 Sep 2019 05:30:18 +0000 (UTC) (envelope-from kiri@truefc.org) Received: from kx.truefc.org (kx.truefc.org [202.216.24.26]) by kx.truefc.org (8.15.2/8.15.2) with ESMTP id x8H5UGxo012419; Tue, 17 Sep 2019 14:30:16 +0900 (JST) (envelope-from kiri@kx.truefc.org) Message-Id: <201909170530.x8H5UGxo012419@kx.truefc.org> Date: Tue, 17 Sep 2019 14:30:16 +0900 From: KIRIYAMA Kazuhiko To: freebsd-current@FreeBSD.org Cc: KIRIYAMA Kazuhiko Subject: r352368 can't boot User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 MULE XEmacs/21.4 (patch 24) (Standard C) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 46XWsR3PrCz4XbN X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of kiri@truefc.org has no SPF policy when checking 202.216.24.26) smtp.mailfrom=kiri@truefc.org X-Spamd-Result: default: False [0.03 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.40)[-0.396,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.67)[-0.673,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[truefc.org]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4704, ipnet:202.216.0.0/19, country:JP]; IP_SCORE(-0.00)[country: JP(-0.02)]; ONCE_RECEIVED(0.10)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 05:30:20 -0000 Hi,all Yesterday I've updated latest head (r352368) and rebuild 13.0-CURRENT. All went fine, but when I boot, it's stopped at boot stage. Then I typed `boot', booted normally and put login prompt and login go ahead. But `shutdown -r now', stopped at loader prompt same as login case. What happened? All I've done is whithin bhyve VM. root@vm:~ # vm start tbedfc Starting tbedfc * found guest in /vm/tbedfc * booting... root@vm:~ # vm console tbedfc Connected OK boot /boot/kernel/kernel text=0x16d7bdc data=0x1c8af8+0x64e118 syms=[0x8+0x182778+0x8+0x19fc7a] /boot/entropy size=0x1000 Booting... GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb ---<>--- Copyright (c) 1992-2019 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 13.0-CURRENT #0 r352368: Mon Sep 16 13:37:27 JST 2019 root@tbedfc:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1) WARNING: WITNESS option enabled, expect reduced performance. VT: init without driver. CPU: Intel(R) Xeon(R) CPU E3-1230 v6 @ 3.50GHz (3503.56-MHz K8-class CPU) Origin="GenuineIntel" Id=0x906e9 Family=0x6 Model=0x9e Stepping=9 Features=0x9f83fbff Features2=0xfeda7a17 AMD Features=0x24100800 AMD Features2=0x121 Structured Extended Features=0xf39 XSAVE Features=0x1 TSC: P-state invariant Hypervisor: Origin = "bhyve bhyve " real memory = 5368709120 (5120 MB) avail memory = 4090740736 (3901 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" random: unblocking device. ioapic0 irqs 0-31 Timecounter "TSC-low" frequency 1751779076 Hz quality 1000 random: entropy device external interface kbd1 at kbdmux0 000.000042 [4335] netmap_init netmap: loaded module module_register_init: MOD_LOAD (vesa, 0xffffffff811bcfa0, 0) error 19 [ath_hal] loaded nexus0 cryptosoft0: acpi0: acpi0: Power Button (fixed) atrtc0: port 0x70-0x71 irq 8 on acpi0 atrtc0: registered as a time-of-day clock, resolution 1.000000s Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 16777216 Hz quality 950 Event timer "HPET" frequency 16777216 Hz quality 550 Event timer "HPET1" frequency 16777216 Hz quality 450 Event timer "HPET2" frequency 16777216 Hz quality 450 Event timer "HPET3" frequency 16777216 Hz quality 450 Event timer "HPET4" frequency 16777216 Hz quality 450 Event timer "HPET5" frequency 16777216 Hz quality 450 Event timer "HPET6" frequency 16777216 Hz quality 450 Event timer "HPET7" frequency 16777216 Hz quality 450 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 virtio_pci0: port 0x2000-0x203f mem 0xc0000000-0xc0001fff irq 16 at device 4.0 on pci0 vtblk0: on virtio_pci0 vtblk0: 8192MB (16777216 512 byte sectors) virtio_pci1: port 0x2040-0x205f mem 0xc0002000-0xc0003fff irq 17 at device 5.0 on pci0 vtnet0: on virtio_pci1 vtnet0: Ethernet address: 58:9c:fc:0c:10:58 vtnet0: netmap queues/slots: TX 1/1024, RX 1/512 000.000150 [ 503] vtnet_netmap_attach vtnet attached txq=1, txd=1024 rxq=1, rxd=512 isab0: at device 31.0 on pci0 isa0: on isab0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] driver bug: Unable to set devclass (class: atkbdc devname: (unknown)) psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (9600,n,8,1) uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 vga0: at port 0x3b0-0x3bb iomem 0xb0000-0xb7fff pnpid PNP0900 on isa0 Timecounters tick every 10.000 msec usb_needs_explore_all: no devclass WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/vtbd0p2 [rw]... Setting hostuuid: fd03833b-4ce8-11e8-a966-589cfc0c1058. Setting hostid: 0x13d7974a. Starting file system checks: /dev/vtbd0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/vtbd0p2: clean, 376431 free (7015 frags, 46177 blocks, 0.6% fragmentation) Mounting local filesystems:. ELF ldconfig path: /lib /usr/lib /usr/lib/compat 32-bit compatibility ldconfig path: /usr/lib32 Setting hostname: tbedfc. Setting up harvesting: PURE_RDRAND,[UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,[NET_ETHER],NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED Feeding entropy: . lo0: link state changed to UP vtnet0: link state changed to UP Starting Network: lo0 vtnet0. lo0: flags=8049 metric 0 mtu 16384 options=680003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=21 vtnet0: flags=8943 metric 0 mtu 1500 options=80028 ether 58:9c:fc:0c:10:58 inet 192.168.1.193 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet 10Gbase-T status: active nd6 options=29 Starting devd. add host 127.0.0.1: gateway lo0 fib 0: route already in table add net default: gateway 192.168.1.254 add host ::1: gateway lo0 fib 0: route already in table add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 Mounting NFS filesystems:. ELF ldconfig path: /lib /usr/lib /usr/lib/compat 32-bit compatibility ldconfig path: /usr/lib32 Creating and/or trimming log files. Starting syslogd. No core dumps found. NFS access cache time=60 Clearing /tmp (X related). Starting rpcbind. Starting statd. Starting lockd. Updating motd:. Mounting late filesystems:. Security policy loaded: MAC/ntpd (mac_ntpd) Starting ntpd. Sep 17 06:47:13 tbedfc ntpd[584]: Cannot set RLIMIT_MEMLOCK: Operation not permitted Performing sanity check on sshd configuration. Starting sshd. Starting sendmail_submit. Starting sendmail_msp_queue. Starting cron. Starting default moused. eval: cannot open /dev/ttyv*: No such file or directory Starting background file system checks in 60 seconds. Tue Sep 17 06:47:13 JST 2019 FreeBSD/amd64 (tbedfc) (ttyu0) login: admin Password: Last login: Tue Sep 17 06:42:06 from smtp.tfc FreeBSD 13.0-CURRENT r350968 GENERIC Welcome to FreeBSD! Release Notes, Errata: https://www.FreeBSD.org/releases/ Security Advisories: https://www.FreeBSD.org/security/ FreeBSD Handbook: https://www.FreeBSD.org/handbook/ FreeBSD FAQ: https://www.FreeBSD.org/faq/ Questions List: https://lists.FreeBSD.org/mailman/listinfo/freebsd-questions/ FreeBSD Forums: https://forums.FreeBSD.org/ Documents installed with the system are in the /usr/local/share/doc/freebsd/ directory, or can be installed later with: pkg install en-freebsd-doc For other languages, replace "en" with a language code like de or fr. Show the version of FreeBSD installed: freebsd-version ; uname -a Please include that output and any error messages when posting questions. Introduction to manual pages: man man FreeBSD directory layout: man hier Edit /etc/motd to change this login announcement. "man ports" gives many useful hints about installing FreeBSD ports. admin@tbedfc:~ % df -h Filesystem Size Used Avail Capacity Mounted on /dev/vtbd0p2 4.8G 3.4G 1.0G 76% / devfs 1.0K 1.0K 0B 100% /dev vm.tfc:/.dake 13T 242G 13T 2% /.dake vm.tfc:/ds/src/current/13.0/r352368 13T 111G 13T 1% /usr/src vm.tfc:/ds/obj/current/13.0/r352368 13T 487G 13T 4% /usr/obj admin@tbedfc:~ % cat /etc/rc.conf hostname="tbedfc" ifconfig_vtnet0="inet 192.168.1.193 netmask 255.255.255.0" defaultrouter="192.168.1.254" sshd_enable="YES" nfs_client_enable="YES" rpc_lockd_enable="YES" rpc_statd_enable="YES" moused_enable="YES" ntpd_enable="YES" #powerd_enable="YES" dumpdev="AUTO" admin@tbedfc:~ % cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/vtbd0p2 / ufs rw 1 1 /dev/vtbd0p3 none swap sw 0 0 vm.tfc:/.dake /.dake nfs rw 0 0 vm.tfc:/ds/src/current/13.0/r352368 /usr/src nfs ro,nolockd 0 0 vm.tfc:/ds/obj/current/13.0/r352368 /usr/obj nfs rw 0 0 admin@tbedfc:~ % uname -a FreeBSD tbedfc 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r352368: Mon Sep 16 13:37:27 JST 2019 root@tbedfc:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 admin@tbedfc:~ % shutdown -r now Shutdown NOW! shutdown: [pid 685] admin@tbedfc:~ % *** FINAL System shutdown message from admin@tbedfc *** System going down IMMEDIATELY System shutdown time has arrived Sep 17 06:52:01 tbedfc shutdown[685]: reboot by admin: Stopping moused. Stopping cron. Stopping sshd. Stopping ntpd. Stopping lockd. Stopping statd. Stopping rpcbind. Stopping devd. Writing entropy file: . Writing early boot entropy file: . Terminated . Sep 17 06:52:01 tbedfc syslogd: exiting on signal 15 Waiting (max 60 seconds) for system process `vnlru' to stop... done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining... 2 0 0 done Waiting (max 60 seconds) for system thread `bufdaemon' to stop... done Waiting (max 60 seconds) for system thread `bufspacedaemon-0' to stop... done Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop... done All buffers synced. lock order reversal: 1st 0xfffff80003bc8248 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1354 2nd 0xfffff80008121ba8 syncer (syncer) @ /usr/src/sys/kern/vfs_subr.c:3015 stack backtrace: #0 0xffffffff80c3f383 at witness_debugger+0x73 #1 0xffffffff80c3f0ce at witness_checkorder+0xa9e #2 0xffffffff80ba57df at lockmgr_lock_fast_path+0x18f #3 0xffffffff812326d3 at VOP_LOCK1_APV+0x63 #4 0xffffffff80cbc495 at _vn_lock+0x65 #5 0xffffffff80caaa25 at vputx+0x1e5 #6 0xffffffff80ca2773 at dounmount+0x4c3 #7 0xffffffff80cac1bb at vfs_unmountall+0x6b #8 0xffffffff80c87db6 at bufshutdown+0x2c6 #9 0xffffffff80bd2685 at kern_reboot+0x215 #10 0xffffffff80bd2415 at sys_reboot+0x3a5 #11 0xffffffff81195759 at amd64_syscall+0x2b9 #12 0xffffffff8116c140 at fast_syscall_common+0x101 lock order reversal: 1st 0xfffff80003869d88 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1354 2nd 0xfffff80003868608 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2744 stack backtrace: #0 0xffffffff80c3f383 at witness_debugger+0x73 #1 0xffffffff80c3f0ce at witness_checkorder+0xa9e #2 0xffffffff80ba57df at lockmgr_lock_fast_path+0x18f #3 0xffffffff812326d3 at VOP_LOCK1_APV+0x63 #4 0xffffffff80cbc495 at _vn_lock+0x65 #5 0xffffffff80caa13d at vget_finish+0x5d #6 0xffffffff80a8993c at devfs_allocv+0xdc #7 0xffffffff80a89463 at devfs_root+0x43 #8 0xffffffff80caadc8 at vflush+0x48 #9 0xffffffff80a8935e at devfs_unmount+0x3e #10 0xffffffff80ca2790 at dounmount+0x4e0 #11 0xffffffff80cac213 at vfs_unmountall+0xc3 #12 0xffffffff80c87db6 at bufshutdown+0x2c6 #13 0xffffffff80bd2685 at kern_reboot+0x215 #14 0xffffffff80bd2415 at sys_reboot+0x3a5 #15 0xffffffff81195759 at amd64_syscall+0x2b9 #16 0xffffffff8116c140 at fast_syscall_common+0x101 Uptime: 4m56s Consoles: userboot FreeBSD/amd64 User boot, Revision 1.1 (Mon Jun 18 16:11:55 UTC 2018 root@releng3.nyi.freebsd.org) Loading /boot/defaults/loader.conf xemit not found Error while including /boot/frames.4th, in the line: h_el @ xemit can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK Regards --- KIRIYAMA Kazuhiko From owner-freebsd-current@freebsd.org Tue Sep 17 05:43:05 2019 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 5C9C8F8336 for ; Tue, 17 Sep 2019 05:43:05 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [IPv6:2400:7800:0:502e::23]) by mx1.freebsd.org (Postfix) with ESMTP id 46XX866qjjz4YNk for ; Tue, 17 Sep 2019 05:43:01 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc13.plala.or.jp with ESMTP id <20190917054258.GSC18269.msc13.plala.or.jp@localhost> for ; Tue, 17 Sep 2019 14:42:58 +0900 Date: Tue, 17 Sep 2019 14:42:51 +0900 (JST) Message-Id: <20190917.144251.30337396601444833.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: panic: sleeping thread on r352386 From: Masachika ISHIZUKA In-Reply-To: <16601631.sFgvYJuXru@direwolf.local.> References: <20190916.205532.1314832713594158104.ish@amail.plala.or.jp> <16601631.sFgvYJuXru@direwolf.local.> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac13; Tue, 17 Sep 2019 14:42:58 +0900 X-Rspamd-Queue-Id: 46XX866qjjz4YNk X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ish@amail.plala.or.jp designates 2400:7800:0:502e::23 as permitted sender) smtp.mailfrom=ish@amail.plala.or.jp X-Spamd-Result: default: False [-0.56 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.89)[-0.895,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2400:7800:0:502e::/60]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.98)[-0.980,0]; DMARC_NA(0.00)[plala.or.jp]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.02)[ipnet: 2400:7800::/32(-0.13), asn: 4713(0.23), country: JP(-0.02)]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4713, ipnet:2400:7800::/32, country:JP]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 05:43:05 -0000 >> This panic happens on 1300047 (both r352239 and r352386) with core >> i5-7500 as follows. This panic dose not happen on r351728 (1300044). >> (The following lines were typed by hand so they might have some miss >> typed letters.) >> >> == >> Sleeping thread (tid 100177, pid 1814) owns a non-sleepable lock >> KDB: stack backtrace of thread 100177: > > > https://svnweb.freebsd.org/base?view=revision&revision=352393 Thank you for reply. I updated to r352431 and this does not panic. Thank you very much. But 'make buildworld' fails by segment fault like below. (buildworld is running over the nfs file system.) --- modules-all --- --- ath_hal_ar5211.ko.debug --- objcopy --only-keep-debug ath_hal_ar5211.ko.full ath_hal_ar5211.ko.debug Segmentation fault (core dumped) *** [ath_hal_ar5211.ko.debug] Error code 139 make[4]: stopped in /usr/altlocal/freebsd-current/src/sys/modules/ath_hal_ar52111 error The position of segment fault is diffrent each time. The below is output of another 'make buildworld'. --- kernel.full --- Segmentation fault (core dumped) *** [kernel.full] Error code 139 make[2]: stopped in /usr/altlocal/freebsd-current/obj/usr/altlocal/freebsd-current/src/amd64.amd64/sys/GENERIC /var/log/messages is shown as bellow. Sep 17 11:22:56 okra kernel: Failed to fully fault in a core file segment at VA 0x800a00000 with size 0x163000 to be written at offset 0x84a000 for process nm Sep 17 11:22:56 okra kernel: pid 53593 (nm), jid 0, uid 16220: exited on signal 11 (core dumped) Sep 17 11:22:57 okra kernel: Failed to fully fault in a core file segment at VA 0x800a00000 with size 0x163000 to be written at offset 0x88b000 for process objcopy Sep 17 11:22:57 okra kernel: pid 53603 (objcopy), jid 0, uid 16220: exited on signal 11 (core dumped) Retry 'make buildworld' Sep 17 12:24:05 okra kernel: Failed to fully fault in a core file segment at VA 0x8002f6000 with size 0x93000 to be written at offset 0x239000 for process nm Sep 17 12:24:05 okra kernel: pid 96873 (nm), jid 0, uid 16220: exited on signal 11 (core dumped) Sep 17 12:24:05 okra kernel: Failed to fully fault in a core file segment at VA 0x80035f000 with size 0x93000 to be written at offset 0x281000 for process objcopy Sep 17 12:24:06 okra kernel: pid 96889 (objcopy), jid 0, uid 16220: exited on signal 11 (core dumped) Retry 'make buildworld' Sep 17 14:01:39 okra kernel: Failed to fully fault in a core file segment at VA 0x8048da000 with size 0x112000 to be written at offset 0x1a33000 for process ld.lld Sep 17 14:01:51 okra kernel: Failed to fully fault in a core file segment at VA 0x8117cc000 with size 0x1e7000 to be written at offset 0xe925000 for process ld.lld Sep 17 14:01:53 okra kernel: pid 50292 (ld.lld), jid 0, uid 16220: exited on signal 11 (core dumped) I can 'make buildworld' successfully on r351728(1300044). -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Tue Sep 17 05:47:09 2019 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 4A9AAF8483 for ; Tue, 17 Sep 2019 05:47:09 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-tydg10021701.me.com (pv50p00im-tydg10021701.me.com [17.58.6.54]) (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 46XXDr2FQJz4YXc for ; Tue, 17 Sep 2019 05:47:08 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-tydg10021701.me.com (Postfix) with ESMTPSA id 102D5840C10; Tue, 17 Sep 2019 05:47:05 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: r352368 can't boot From: Toomas Soome In-Reply-To: <201909170530.x8H5UGxo012419@kx.truefc.org> Date: Tue, 17 Sep 2019 08:47:03 +0300 Cc: "freebsd-current@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <5E929415-319A-490D-AB9A-2F8259391B13@me.com> References: <201909170530.x8H5UGxo012419@kx.truefc.org> To: KIRIYAMA Kazuhiko X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-17_03:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0 mlxlogscore=974 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909170065 X-Rspamd-Queue-Id: 46XXDr2FQJz4YXc X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.60 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.00)[ip: (-9.21), ipnet: 17.58.0.0/20(-3.31), asn: 714(-2.91), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[54.6.58.17.list.dnswl.org : 127.0.5.1]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 05:47:09 -0000 > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko wrote: >=20 > Hi,all >=20 > Yesterday I've updated latest head (r352368) and rebuild > 13.0-CURRENT. All went fine, but when I boot, it's stopped > at boot stage. Then I typed `boot', booted normally and put > login prompt and login go ahead. But `shutdown -r now', > stopped at loader prompt same as login case. What happened? > All I've done is whithin bhyve VM. >=20 >=20 > Consoles: userboot =20 >=20 > FreeBSD/amd64 User boot, Revision 1.1 > (Mon Jun 18 16:11:55 UTC 2018 root@releng3.nyi.freebsd.org) > Loading /boot/defaults/loader.conf > xemit not found > Error while including /boot/frames.4th, in the line: > h_el @ xemit >=20 > can't load 'kernel' >=20 > Type '?' for a list of commands, 'help' for more detailed help. > OK=20 >=20 This is unfortunate case where the guest image has more recent boot = scripts than hosts /boot/userboot.so has. I did push the fix for that = issue to stable/11 and stable/12. The patch does introduce xemit word. Such situation is unfortunate, but accident waiting to happen with this = method where we are attempting to use bootloader (userboot.so) from = older system to load guest vm.=20 rgds, toomas From owner-freebsd-current@freebsd.org Tue Sep 17 08:07:19 2019 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 E0B2BFB54A for ; Tue, 17 Sep 2019 08:07:19 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46XbLZ4Fl6z3BqL; Tue, 17 Sep 2019 08:07:18 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x8H8706W083680 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 17 Sep 2019 11:07:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x8H8706W083680 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x8H86w4H083679; Tue, 17 Sep 2019 11:06:58 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 17 Sep 2019 11:06:58 +0300 From: Konstantin Belousov To: Masachika ISHIZUKA Cc: freebsd-current@freebsd.org, Rick Macklem , peterj@freebsd.org Subject: Re: panic: sleeping thread on r352386 Message-ID: <20190917080658.GW2559@kib.kiev.ua> References: <20190916.205532.1314832713594158104.ish@amail.plala.or.jp> <16601631.sFgvYJuXru@direwolf.local.> <20190917.144251.30337396601444833.ish@amail.plala.or.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190917.144251.30337396601444833.ish@amail.plala.or.jp> User-Agent: Mutt/1.12.1 (2019-06-15) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-Rspamd-Queue-Id: 46XbLZ4Fl6z3BqL X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; FREEMAIL_FROM(0.00)[gmail.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all:c]; IP_SCORE_FREEMAIL(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.00)[ip: (-2.69), ipnet: 2001:470::/32(-4.46), asn: 6939(-3.22), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 08:07:19 -0000 On Tue, Sep 17, 2019 at 02:42:51PM +0900, Masachika ISHIZUKA wrote: > >> This panic happens on 1300047 (both r352239 and r352386) with core > >> i5-7500 as follows. This panic dose not happen on r351728 (1300044). > >> (The following lines were typed by hand so they might have some miss > >> typed letters.) > >> > >> == > >> Sleeping thread (tid 100177, pid 1814) owns a non-sleepable lock > >> KDB: stack backtrace of thread 100177: > > > > > > https://svnweb.freebsd.org/base?view=revision&revision=352393 > > Thank you for reply. > > I updated to r352431 and this does not panic. Thank you very much. > But 'make buildworld' fails by segment fault like below. > (buildworld is running over the nfs file system.) > > --- modules-all --- > --- ath_hal_ar5211.ko.debug --- > objcopy --only-keep-debug ath_hal_ar5211.ko.full ath_hal_ar5211.ko.debug > Segmentation fault (core dumped) > *** [ath_hal_ar5211.ko.debug] Error code 139 > make[4]: stopped in /usr/altlocal/freebsd-current/src/sys/modules/ath_hal_ar52111 error > > The position of segment fault is diffrent each time. > The below is output of another 'make buildworld'. > > --- kernel.full --- > Segmentation fault (core dumped) > *** [kernel.full] Error code 139 > make[2]: stopped in /usr/altlocal/freebsd-current/obj/usr/altlocal/freebsd-current/src/amd64.amd64/sys/GENERIC > > /var/log/messages is shown as bellow. > > Sep 17 11:22:56 okra kernel: Failed to fully fault in a core file segment at VA > 0x800a00000 with size 0x163000 to be written at offset 0x84a000 for process nm > Sep 17 11:22:56 okra kernel: pid 53593 (nm), jid 0, uid 16220: exited on signal > 11 (core dumped) > Sep 17 11:22:57 okra kernel: Failed to fully fault in a core file segment at VA > 0x800a00000 with size 0x163000 to be written at offset 0x88b000 for process objcopy > Sep 17 11:22:57 okra kernel: pid 53603 (objcopy), jid 0, uid 16220: exited on signal 11 (core dumped) > > Retry 'make buildworld' > > Sep 17 12:24:05 okra kernel: Failed to fully fault in a core file segment at VA > 0x8002f6000 with size 0x93000 to be written at offset 0x239000 for process nm > Sep 17 12:24:05 okra kernel: pid 96873 (nm), jid 0, uid 16220: exited on signal > 11 (core dumped) > Sep 17 12:24:05 okra kernel: Failed to fully fault in a core file segment at VA > 0x80035f000 with size 0x93000 to be written at offset 0x281000 for process objcopy > Sep 17 12:24:06 okra kernel: pid 96889 (objcopy), jid 0, uid 16220: exited on signal 11 (core dumped) > > Retry 'make buildworld' > > Sep 17 14:01:39 okra kernel: Failed to fully fault in a core file segment at VA > 0x8048da000 with size 0x112000 to be written at offset 0x1a33000 for process ld.lld > Sep 17 14:01:51 okra kernel: Failed to fully fault in a core file segment at VA > 0x8117cc000 with size 0x1e7000 to be written at offset 0xe925000 for process ld.lld > Sep 17 14:01:53 okra kernel: pid 50292 (ld.lld), jid 0, uid 16220: exited on signal 11 (core dumped) > > I can 'make buildworld' successfully on r351728(1300044). Try the following change, which more accurately tries to avoid vnode_pager_setsize(). The real cause requires much more extensive changes. diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c index 63ea4736707..16dc7745c77 100644 --- a/sys/fs/nfsclient/nfs_clport.c +++ b/sys/fs/nfsclient/nfs_clport.c @@ -414,12 +414,11 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, struct nfsnode *np; struct nfsmount *nmp; struct timespec mtime_save; - u_quad_t nsize; - int setnsize, error, force_fid_err; + u_quad_t nsize, osize; + int error, force_fid_err; + bool setnsize; error = 0; - setnsize = 0; - nsize = 0; /* * If v_type == VNON it is a new node, so fill in the v_type, @@ -439,6 +438,7 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, nmp = VFSTONFS(vp->v_mount); vap = &np->n_vattr.na_vattr; mtime_save = vap->va_mtime; + osize = vap->va_size; if (writeattr) { np->n_vattr.na_filerev = nap->na_filerev; np->n_vattr.na_size = nap->na_size; @@ -511,8 +511,7 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, * zero np->n_attrstamp to indicate that * the attributes are stale. */ - nsize = vap->va_size = np->n_size; - setnsize = 1; + vap->va_size = np->n_size; np->n_attrstamp = 0; KDTRACE_NFS_ATTRCACHE_FLUSH_DONE(vp); } else if (np->n_flag & NMODIFIED) { @@ -526,22 +525,9 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, np->n_size = vap->va_size; np->n_flag |= NSIZECHANGED; } - nsize = np->n_size; - setnsize = 1; - } else if (vap->va_size < np->n_size) { - /* - * When shrinking the size, the call to - * vnode_pager_setsize() cannot be done - * with the mutex held, so delay it until - * after the mtx_unlock call. - */ - nsize = np->n_size = vap->va_size; - np->n_flag |= NSIZECHANGED; - setnsize = 1; } else { - nsize = np->n_size = vap->va_size; + np->n_size = vap->va_size; np->n_flag |= NSIZECHANGED; - setnsize = 1; } } else { np->n_size = vap->va_size; @@ -579,6 +565,21 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, if (np->n_attrstamp != 0) KDTRACE_NFS_ATTRCACHE_LOAD_DONE(vp, vap, error); #endif + nsize = vap->va_size; + if (nsize == osize) { + setnsize = false; + } else if (nsize > osize) { + vnode_pager_setsize(vp, nsize); + setnsize = false; + } else { + /* + * When shrinking the size, the call to + * vnode_pager_setsize() cannot be done with the mutex + * held, because we might need to wait for a busy + * page. Delay it until after the node is unlocked. + */ + setnsize = true; + } NFSUNLOCKNODE(np); if (setnsize) vnode_pager_setsize(vp, nsize); From owner-freebsd-current@freebsd.org Tue Sep 17 10:09:49 2019 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 3F683FDC58 for ; Tue, 17 Sep 2019 10:09:49 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Xf3w3t4Xz3Jx7 for ; Tue, 17 Sep 2019 10:09:48 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x729.google.com with SMTP id s18so3342612qkj.3 for ; Tue, 17 Sep 2019 03:09:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZvXTlQHS0Y3naF+TdV7redsUziCa/FLC9+Ku6zXjIjA=; b=KUAGkYLmkBysC9UHTxgVSOCSofacvA5ew5MO7zmghl5EbXASsJb/mPPHYXgTiIsY9u m6CswCUsOP5zFq9evBEQC6UE/W+wKBmoG+8dXp7JjeauF4gprj5uyytKWKMfrr6hSqig 6Qcq44x/WpeWIGc6eD4ts4MZIyudXEgpWMg5I+K3e3ZESz9b6j7eKXjQcBgt5Hr1Uw2D RTM+RdZgr8YaVHdH0DjCBnTGl0ddWHp7BShOR+oxEzP2Xz4txyPQRGQnhJeXwhrFmcJx Y4tWFTZn9MCib7U3WIDfcTr/8+ZxzXx4MID1C/cfRQvS2rAN+ApxWU+xi0t5+/mDytAa 5bWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZvXTlQHS0Y3naF+TdV7redsUziCa/FLC9+Ku6zXjIjA=; b=psh2JQcQTa97pLuTSOGd6J2RsMJOkdPY/m6fPYfv5LhL1CoVQ+HhRA+jFUWFsxGlDk JGPo0M1OkaE6Gv8n4YwCmjvNfKgaFevPJdi5KQwOrmibl4UkqB+CgnqOLOc3dkyzn0ST pEvbYLJ0RraY1P/XZyIQsx5TsxQigbvcJ11HcMO38IOU+gn+/clY3e24lfEKPSEV7Ooq vCiM+QKW6FWjQnTDDNCqeoa8TRBAeoJDLgkgyPGlqOWf1uSWqdrgdg+9bksr2dGL+1cq VRYJ4V+Ch2+0j91NkJFG/kPX4EyYZaOXFKbd5GP0LeufgXmQF9PsIAHPs30nqnJ4aVAF 3PfQ== X-Gm-Message-State: APjAAAU07Et58RhKtiF8YJhBEB2Ji9SYns2isssGD//k/xZuW+JoLuaO OWlWXx0kzDIvJwI6gDVMKBf5mAXhaHU8iF060c2nWlJdA6Y= X-Google-Smtp-Source: APXvYqzxO3jwZ8qorLy1NuTqX7UFM2Y8ZnQDDROjXKr1UctJ4l934t0SMbiBsdQLgPqq+Ky8YATQqTi0ErwOrsgDZ0s= X-Received: by 2002:a37:6787:: with SMTP id b129mr2899053qkc.60.1568714986731; Tue, 17 Sep 2019 03:09:46 -0700 (PDT) MIME-Version: 1.0 References: <201909170530.x8H5UGxo012419@kx.truefc.org> <5E929415-319A-490D-AB9A-2F8259391B13@me.com> In-Reply-To: <5E929415-319A-490D-AB9A-2F8259391B13@me.com> From: Warner Losh Date: Tue, 17 Sep 2019 11:09:34 +0100 Message-ID: Subject: Re: r352368 can't boot To: Toomas Soome Cc: KIRIYAMA Kazuhiko , FreeBSD Current X-Rspamd-Queue-Id: 46Xf3w3t4Xz3Jx7 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=KUAGkYLm; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::729) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-4.85 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[9.2.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; FREEMAIL_TO(0.00)[me.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.85)[ip: (-9.29), ipnet: 2607:f8b0::/32(-2.69), asn: 15169(-2.24), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 10:09:49 -0000 On Tue, Sep 17, 2019, 6:47 AM Toomas Soome wrote: > > > > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko wrote: > > > > Hi,all > > > > Yesterday I've updated latest head (r352368) and rebuild > > 13.0-CURRENT. All went fine, but when I boot, it's stopped > > at boot stage. Then I typed `boot', booted normally and put > > login prompt and login go ahead. But `shutdown -r now', > > stopped at loader prompt same as login case. What happened? > > All I've done is whithin bhyve VM. > > > > > > > > Consoles: userboot > > > > FreeBSD/amd64 User boot, Revision 1.1 > > (Mon Jun 18 16:11:55 UTC 2018 root@releng3.nyi.freebsd.org) > > Loading /boot/defaults/loader.conf > > xemit not found > > Error while including /boot/frames.4th, in the line: > > h_el @ xemit > > > > can't load 'kernel' > > > > Type '?' for a list of commands, 'help' for more detailed help. > > OK > > > > This is unfortunate case where the guest image has more recent boot > scripts than hosts /boot/userboot.so has. I did push the fix for that issue > to stable/11 and stable/12. The patch does introduce xemit word. > > Such situation is unfortunate, but accident waiting to happen with this > method where we are attempting to use bootloader (userboot.so) from older > system to load guest vm. > Can we provide a fallback to xemit builtin for old systems without it? I believe we did this for other things as a transition. Forth has a way to do this, though we need to make sure we properly constrain what we pass to emit... Warner P.s. I'm at legoland this week, so I can't look at it for a bit. rgds, > toomas > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Tue Sep 17 10:18:52 2019 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 1F386FE07C for ; Tue, 17 Sep 2019 10:18:52 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vtr.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46XfGL72z6z3KYV for ; Tue, 17 Sep 2019 10:18:50 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp239-208.static.internode.on.net [59.167.239.208]) by vtr.rulingia.com (8.15.2/8.15.2) with ESMTPS id x8HAIVjs006689 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 17 Sep 2019 20:18:37 +1000 (AEST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id x8HAIQRD047031 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 17 Sep 2019 20:18:26 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id x8HAIQt6047030; Tue, 17 Sep 2019 20:18:26 +1000 (AEST) (envelope-from peter) Date: Tue, 17 Sep 2019 20:18:26 +1000 From: Peter Jeremy To: Konstantin Belousov Cc: Masachika ISHIZUKA , freebsd-current@freebsd.org, Rick Macklem Subject: Re: panic: sleeping thread on r352386 Message-ID: <20190917101826.GJ97181@server.rulingia.com> References: <20190916.205532.1314832713594158104.ish@amail.plala.or.jp> <16601631.sFgvYJuXru@direwolf.local.> <20190917.144251.30337396601444833.ish@amail.plala.or.jp> <20190917080658.GW2559@kib.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ExXT7PjY8AI4Hyfa" Content-Disposition: inline In-Reply-To: <20190917080658.GW2559@kib.kiev.ua> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.12.1 (2019-06-15) X-Rspamd-Queue-Id: 46XfGL72z6z3KYV X-Spamd-Bar: ------- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of peter@rulingia.com designates 2001:19f0:5801:ebe:5400:1ff:fe53:30fd as permitted sender) smtp.mailfrom=peter@rulingia.com X-Spamd-Result: default: False [-7.58 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_NA(0.00)[rulingia.com]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; SIGNED_PGP(-2.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:20473, ipnet:2001:19f0:5800::/38, country:US]; RCVD_TLS_ALL(0.00)[]; IP_SCORE(-3.18)[ip: (-9.91), ipnet: 2001:19f0:5800::/38(-4.94), asn: 20473(-0.98), country: US(-0.05)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 10:18:52 -0000 --ExXT7PjY8AI4Hyfa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2019-Sep-17 11:06:58 +0300, Konstantin Belousov wr= ote: >Try the following change, which more accurately tries to avoid >vnode_pager_setsize(). The real cause requires much more extensive >changes. > >diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c >index 63ea4736707..16dc7745c77 100644 >--- a/sys/fs/nfsclient/nfs_clport.c >+++ b/sys/fs/nfsclient/nfs_clport.c =2E.. With that patch, I'm back to "Sleeping thread (...) owns a non-sleepable lock" panics. --=20 Peter Jeremy --ExXT7PjY8AI4Hyfa Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAl2AsudfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzTTVQ/7Bv2VTeIBvamRB8b34qvVnOqsGmt4CtQgzzHXvZF1A/NhyT3oUEoSV72B r4t1TTTe3deySUcFfcconN+RfMjlfjpqA2IkvjkVIf16QSfVqxM8TtRbZZh5P1Kw SN6btr1LxdAKQKIy+TAelut6Qqb6SGFF3l69J0ufinXhHf1IJxG+mcnA3/YbN7q7 Hc13CtoxZ+ZV3ZnyuwIHrLonf3UTHpj8aY1g7e054dl/n+YU9jSmHeinTvEWeN3v Q4O/fjhl+Q9UdzDHka4CLRJuDEjtJN33JgTajdf8v+jk6gpI9fdVwhVl2yICxEWN pFCpmKm8x8KuMQ4BkqCsndBl3krpFMMLUjx/VZowZ34xLsmpMltK26v1CMCxed6j zFo6QlUIddJaUBJ81fnHC0bdEWqI+8mvgoLd+duLIIQmizeb9PNhkt8yyeQuJGPG ZDLOZF8ArezkaaVmPxScpUMCqpK88po7FdhuM4nKlksnWfix6HtnF8+urtElqUG1 wwA6o0uSxnGRgs1xztfTv/QlY4GetNHFeRB5e+auMFbjFnUl0ou7cu4qu7Xeld3i cZWkgA0751n1naX2DTw/e2IPbMDFGeoXX8+7txkv0Y7Exl31DWNiu88WUvM+N8Ce 5Rc2tVxqLNP8CwLN2NjvQGw0EByoftM9ypqEwZ/bOoBtyjxC02o= =Z11W -----END PGP SIGNATURE----- --ExXT7PjY8AI4Hyfa-- From owner-freebsd-current@freebsd.org Tue Sep 17 10:24:47 2019 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 13B8BFE3B1 for ; Tue, 17 Sep 2019 10:24:47 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-zteg10011501.me.com (pv50p00im-zteg10011501.me.com [17.58.6.42]) (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 46XfPB23Ysz3L2L for ; Tue, 17 Sep 2019 10:24:46 +0000 (UTC) (envelope-from tsoome@me.com) Received: from [192.168.150.41] (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-zteg10011501.me.com (Postfix) with ESMTPSA id E94BFB006C1; Tue, 17 Sep 2019 10:24:41 +0000 (UTC) From: Toomas Soome Message-Id: <8A9627B9-8190-490C-8D76-6F2A9D00E059@me.com> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: r352368 can't boot Date: Tue, 17 Sep 2019 13:24:38 +0300 In-Reply-To: Cc: KIRIYAMA Kazuhiko , FreeBSD Current To: Warner Losh References: <201909170530.x8H5UGxo012419@kx.truefc.org> <5E929415-319A-490D-AB9A-2F8259391B13@me.com> X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-17_05:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909170106 X-Rspamd-Queue-Id: 46XfPB23Ysz3L2L X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.20 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; URI_COUNT_ODD(1.00)[3]; TO_DN_ALL(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[42.6.58.17.list.dnswl.org : 127.0.5.2]; DKIM_TRACE(0.00)[me.com:+]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-4.57), ipnet: 17.58.0.0/20(-3.34), asn: 714(-2.91), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[me.com]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 10:24:47 -0000 > On 17 Sep 2019, at 13:09, Warner Losh wrote: >=20 >=20 >=20 > On Tue, Sep 17, 2019, 6:47 AM Toomas Soome > wrote: >=20 >=20 > > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko > wrote: > >=20 > > Hi,all > >=20 > > Yesterday I've updated latest head (r352368) and rebuild > > 13.0-CURRENT. All went fine, but when I boot, it's stopped > > at boot stage. Then I typed `boot', booted normally and put > > login prompt and login go ahead. But `shutdown -r now', > > stopped at loader prompt same as login case. What happened? > > All I've done is whithin bhyve VM. > >=20 > >=20 >=20 >=20 > > Consoles: userboot =20 > >=20 > > FreeBSD/amd64 User boot, Revision 1.1 > > (Mon Jun 18 16:11:55 UTC 2018 root@releng3.nyi.freebsd.org = ) > > Loading /boot/defaults/loader.conf > > xemit not found > > Error while including /boot/frames.4th, in the line: > > h_el @ xemit > >=20 > > can't load 'kernel' > >=20 > > Type '?' for a list of commands, 'help' for more detailed help. > > OK=20 > >=20 >=20 > This is unfortunate case where the guest image has more recent boot = scripts than hosts /boot/userboot.so has. I did push the fix for that = issue to stable/11 and stable/12. The patch does introduce xemit word. >=20 > Such situation is unfortunate, but accident waiting to happen with = this method where we are attempting to use bootloader (userboot.so) from = older system to load guest vm.=20 >=20 > Can we provide a fallback to xemit builtin for old systems without it? = I believe we did this for other things as a transition. Forth has a way = to do this, though we need to make sure we properly constrain what we = pass to emit... >=20 > Warner >=20 > P.s. I'm at legoland this week, so I can't look at it for a bit. >=20 Well, the only way to avoid such issue is to make sure the guest = environment is providing all the needed bits, but since we do have = interpreter inside the userboot.so and userboot.so is in host, this does = set rather unfortunate limits what we can do. rgds, toomas= From owner-freebsd-current@freebsd.org Tue Sep 17 11:08:55 2019 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 61245FF520 for ; Tue, 17 Sep 2019 11:08:55 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [60.36.166.23]) by mx1.freebsd.org (Postfix) with ESMTP id 46XgN50bdDz3NJy for ; Tue, 17 Sep 2019 11:08:52 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc13.plala.or.jp with ESMTP id <20190917110849.WKX18269.msc13.plala.or.jp@localhost> for ; Tue, 17 Sep 2019 20:08:49 +0900 Date: Tue, 17 Sep 2019 20:08:40 +0900 (JST) Message-Id: <20190917.200840.719612001913306081.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: panic: sleeping thread on r352386 From: Masachika ISHIZUKA In-Reply-To: <20190917101826.GJ97181@server.rulingia.com> References: <20190917.144251.30337396601444833.ish@amail.plala.or.jp> <20190917080658.GW2559@kib.kiev.ua> <20190917101826.GJ97181@server.rulingia.com> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac13; Tue, 17 Sep 2019 20:08:49 +0900 X-Rspamd-Queue-Id: 46XgN50bdDz3NJy X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ish@amail.plala.or.jp designates 60.36.166.23 as permitted sender) smtp.mailfrom=ish@amail.plala.or.jp X-Spamd-Result: default: False [1.12 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.34)[-0.340,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:60.36.166.0/24]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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]; NEURAL_HAM_LONG(-0.18)[-0.176,0]; DMARC_NA(0.00)[plala.or.jp]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.43)[ip: (-1.03), ipnet: 60.32.0.0/12(2.99), asn: 4713(0.23), country: JP(-0.02)]; RCVD_NO_TLS_LAST(0.10)[]; RCVD_IN_DNSWL_LOW(-0.10)[23.166.36.60.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4713, ipnet:60.32.0.0/12, country:JP]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 11:08:55 -0000 >>Try the following change, which more accurately tries to avoid >>vnode_pager_setsize(). The real cause requires much more extensive >>changes. >> >>diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c >>index 63ea4736707..16dc7745c77 100644 >>--- a/sys/fs/nfsclient/nfs_clport.c >>+++ b/sys/fs/nfsclient/nfs_clport.c > ... > > With that patch, I'm back to "Sleeping thread (...) owns a non-sleepable > lock" panics. Me too. I applied this patch to r352432 and rebuild/install kernel/world. As the result, 'make buildworld' stopped with a panic that "sleeping thread (...) owns a non-sleepable lock". -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Tue Sep 17 11:21:32 2019 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 534C6FFC4B for ; Tue, 17 Sep 2019 11:21:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Xgfg295jz3PCR for ; Tue, 17 Sep 2019 11:21:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x72c.google.com with SMTP id q203so3557604qke.1 for ; Tue, 17 Sep 2019 04:21:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kHt7VcD0iW8zyVXvbdohmR2gb1eZyyWqskOOAJkNXTo=; b=NJijQMLaa/HPEZB5TL1X07+AXL5hOvucnaPO46lUDmiKTVIoS7IyqV25UTRCCVavPm TaZwqrxp+EML96zB38sjefnmYMO8Zg4CTrnICFRAT7WvGhnnepZiDWIHWQECaDfuFPEa Ktx6x4k1aZ4JPv8XsMnKopfJ0prr4s+sKCiWVLexoBZ4gDYsZUvkGFMM7ODNnf7JbH+v qhuzFPCWI1LD1vjfwrXk2Mcuvraft93r92NshzoCcdkVwpqCPN/EP0kKpcGbLgY8Vnbs 2CqsdW3g0BweLvsYuDyILhgJxlyljuO/ENotu7ZEXyHT9jf7dhyb7hwNho/S0rmB7zN3 EdVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kHt7VcD0iW8zyVXvbdohmR2gb1eZyyWqskOOAJkNXTo=; b=NjWPt3aZF3WjZokAa8BJit0q9RkuJCmd7dAH2bm2eKQYb9R44rHyVSHaUxpWlMZydM XlAAZ4dMrZHcqJ1rW7ICobm6R+1a4X4OKDAFkp4vA1id4NWJXoQ7pFtkfbqjWRah3rIe 8/z++/fJcMXRnTilvBfLpOFwzFdvvqRFXzd/NEZfoCx3S+SHcXMb5+d+8C32urU4xkLL 4JdiaOTXN+OQJms+0wpbzyXUaL48/Vd+nkheGdSB9Jympgo1PaO5sybR1ItxaGiPFiTo oiUCveoIxBbpulDt99AbuEsK60GaIqRuXMNI9Oi7JMBP6NB/QMQcYCIY1f+x7yLIc+Qw FHQA== X-Gm-Message-State: APjAAAUTUFc6hJFKgHcqFttYE0m4q7Vu9y8lllACmwzT9z67cMwO058M e+izr3421nJOGwfVtH6V9l/13TDUT5+LF7hx4shp2A== X-Google-Smtp-Source: APXvYqyklzxh7VSfFDHRD9PZs5YpRMubEsxQjxbH0IvhF0eqQzkFRnjElwRI78aCYvILM9XR5mXe8pIw+3LVXXbCNMI= X-Received: by 2002:a37:30f:: with SMTP id 15mr2820362qkd.240.1568719289861; Tue, 17 Sep 2019 04:21:29 -0700 (PDT) MIME-Version: 1.0 References: <201909170530.x8H5UGxo012419@kx.truefc.org> <5E929415-319A-490D-AB9A-2F8259391B13@me.com> <8A9627B9-8190-490C-8D76-6F2A9D00E059@me.com> In-Reply-To: <8A9627B9-8190-490C-8D76-6F2A9D00E059@me.com> From: Warner Losh Date: Tue, 17 Sep 2019 12:21:17 +0100 Message-ID: Subject: Re: r352368 can't boot To: Toomas Soome Cc: KIRIYAMA Kazuhiko , FreeBSD Current X-Rspamd-Queue-Id: 46Xgfg295jz3PCR X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=NJijQMLa; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::72c) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.86 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; URI_COUNT_ODD(1.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[c.2.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; FREEMAIL_TO(0.00)[me.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.86)[ip: (-9.32), ipnet: 2607:f8b0::/32(-2.69), asn: 15169(-2.23), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 11:21:32 -0000 On Tue, Sep 17, 2019, 11:24 AM Toomas Soome wrote: > > > On 17 Sep 2019, at 13:09, Warner Losh wrote: > > > > On Tue, Sep 17, 2019, 6:47 AM Toomas Soome wrote: > >> >> >> > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko wrote: >> > >> > Hi,all >> > >> > Yesterday I've updated latest head (r352368) and rebuild >> > 13.0-CURRENT. All went fine, but when I boot, it's stopped >> > at boot stage. Then I typed `boot', booted normally and put >> > login prompt and login go ahead. But `shutdown -r now', >> > stopped at loader prompt same as login case. What happened? >> > All I've done is whithin bhyve VM. >> > >> > >> >> >> > Consoles: userboot >> > >> > FreeBSD/amd64 User boot, Revision 1.1 >> > (Mon Jun 18 16:11:55 UTC 2018 root@releng3.nyi.freebsd.org) >> > Loading /boot/defaults/loader.conf >> > xemit not found >> > Error while including /boot/frames.4th, in the line: >> > h_el @ xemit >> > >> > can't load 'kernel' >> > >> > Type '?' for a list of commands, 'help' for more detailed help. >> > OK >> > >> >> This is unfortunate case where the guest image has more recent boot >> scripts than hosts /boot/userboot.so has. I did push the fix for that issue >> to stable/11 and stable/12. The patch does introduce xemit word. >> >> Such situation is unfortunate, but accident waiting to happen with this >> method where we are attempting to use bootloader (userboot.so) from older >> system to load guest vm. >> > > Can we provide a fallback to xemit builtin for old systems without it? I > believe we did this for other things as a transition. Forth has a way to do > this, though we need to make sure we properly constrain what we pass to > emit... > > Warner > > P.s. I'm at legoland this week, so I can't look at it for a bit. > > > Well, the only way to avoid such issue is to make sure the guest > environment is providing all the needed bits, but since we do have > interpreter inside the userboot.so and userboot.so is in host, this does > set rather unfortunate limits what we can do. > Yes. I understand that we are limited in our scripts to somehow testing if xemit is a forth word and if not providing a fallback implementation of it in forth using emit. Warner rgds, > toomas > From owner-freebsd-current@freebsd.org Tue Sep 17 12:24:46 2019 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 8CCBF122884 for ; Tue, 17 Sep 2019 12:24:46 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46Xj3d2sGfz3xN1 for ; Tue, 17 Sep 2019 12:24:45 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x8HCOX72042860 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 17 Sep 2019 15:24:36 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x8HCOX72042860 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x8HCOU5J042858; Tue, 17 Sep 2019 15:24:30 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 17 Sep 2019 15:24:30 +0300 From: Konstantin Belousov To: Peter Jeremy Cc: Masachika ISHIZUKA , freebsd-current@freebsd.org, Rick Macklem Subject: Re: panic: sleeping thread on r352386 Message-ID: <20190917122430.GZ2559@kib.kiev.ua> References: <20190916.205532.1314832713594158104.ish@amail.plala.or.jp> <16601631.sFgvYJuXru@direwolf.local.> <20190917.144251.30337396601444833.ish@amail.plala.or.jp> <20190917080658.GW2559@kib.kiev.ua> <20190917101826.GJ97181@server.rulingia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190917101826.GJ97181@server.rulingia.com> User-Agent: Mutt/1.12.1 (2019-06-15) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-Rspamd-Queue-Id: 46Xj3d2sGfz3xN1 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; FREEMAIL_FROM(0.00)[gmail.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; IP_SCORE_FREEMAIL(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.00)[ip: (-2.67), ipnet: 2001:470::/32(-4.46), asn: 6939(-3.22), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 12:24:46 -0000 On Tue, Sep 17, 2019 at 08:18:26PM +1000, Peter Jeremy wrote: > On 2019-Sep-17 11:06:58 +0300, Konstantin Belousov wrote: > >Try the following change, which more accurately tries to avoid > >vnode_pager_setsize(). The real cause requires much more extensive > >changes. > > > >diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c > >index 63ea4736707..16dc7745c77 100644 > >--- a/sys/fs/nfsclient/nfs_clport.c > >+++ b/sys/fs/nfsclient/nfs_clport.c > ... > > With that patch, I'm back to "Sleeping thread (...) owns a non-sleepable > lock" panics. Try this. diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c index 63ea4736707..a23b4ba4efa 100644 --- a/sys/fs/nfsclient/nfs_clport.c +++ b/sys/fs/nfsclient/nfs_clport.c @@ -414,12 +414,12 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, struct nfsnode *np; struct nfsmount *nmp; struct timespec mtime_save; + vm_object_t object; u_quad_t nsize; - int setnsize, error, force_fid_err; + int error, force_fid_err; + bool setnsize; error = 0; - setnsize = 0; - nsize = 0; /* * If v_type == VNON it is a new node, so fill in the v_type, @@ -511,8 +511,7 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, * zero np->n_attrstamp to indicate that * the attributes are stale. */ - nsize = vap->va_size = np->n_size; - setnsize = 1; + vap->va_size = np->n_size; np->n_attrstamp = 0; KDTRACE_NFS_ATTRCACHE_FLUSH_DONE(vp); } else if (np->n_flag & NMODIFIED) { @@ -526,22 +525,9 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, np->n_size = vap->va_size; np->n_flag |= NSIZECHANGED; } - nsize = np->n_size; - setnsize = 1; - } else if (vap->va_size < np->n_size) { - /* - * When shrinking the size, the call to - * vnode_pager_setsize() cannot be done - * with the mutex held, so delay it until - * after the mtx_unlock call. - */ - nsize = np->n_size = vap->va_size; - np->n_flag |= NSIZECHANGED; - setnsize = 1; } else { - nsize = np->n_size = vap->va_size; + np->n_size = vap->va_size; np->n_flag |= NSIZECHANGED; - setnsize = 1; } } else { np->n_size = vap->va_size; @@ -579,6 +565,23 @@ nfscl_loadattrcache(struct vnode **vpp, struct nfsvattr *nap, void *nvaper, if (np->n_attrstamp != 0) KDTRACE_NFS_ATTRCACHE_LOAD_DONE(vp, vap, error); #endif + nsize = vap->va_size; + object = vp->v_object; + setnsize = false; + if (object != NULL) { + if (OFF_TO_IDX(nsize + PAGE_MASK) < object->size) { + /* + * When shrinking the size, the call to + * vnode_pager_setsize() cannot be done with + * the mutex held, because we might need to + * wait for a busy page. Delay it until after + * the node is unlocked. + */ + setnsize = true; + } else { + vnode_pager_setsize(vp, nsize); + } + } NFSUNLOCKNODE(np); if (setnsize) vnode_pager_setsize(vp, nsize); From owner-freebsd-current@freebsd.org Tue Sep 17 14:09:18 2019 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 6BFC7125131 for ; Tue, 17 Sep 2019 14:09:18 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io1-xd43.google.com (mail-io1-xd43.google.com [IPv6:2607:f8b0:4864:20::d43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46XlNF5T5Yz43g5 for ; Tue, 17 Sep 2019 14:09:17 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-io1-xd43.google.com with SMTP id j4so7812364iog.11 for ; Tue, 17 Sep 2019 07:09:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=rUduJWDnrCxHeqtKtLw9J9pdMnBIH83tuJ4FmcfFVjk=; b=YLgWWKgQTcC1qyVk0sCypAm8gehvro0XLzZnNnPjwOlKjlxWF+y7W+ldkyy4Mtd4VO 6I5oLVCh0UsMYmk1JtThoc3SayecFhcmQmHA7Od+wz4Dv9vhwe/9jmro1ujASldJ5h14 NVmHzfAaSHKc3DXBmETB3XYqHpeFVcaYyVWDUHz07tMM90tWp8uiaBaesk1v7R3DcDwa I7HbfeLAjlsvYe+IG0jl2/LcilVHxvIEiKKSr0QMzJuxqpu/8KapJACoSuEXslpjBweo Ym1ynA4Qni6PAl5uUCEfTGJEowlIoUY/tZvTtSjabEcMQ5SiIpXbBfielZ7OiIepEqLf dPHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=rUduJWDnrCxHeqtKtLw9J9pdMnBIH83tuJ4FmcfFVjk=; b=aN7id02WmV7oWQF/R4+HasTHZvHmg03fFjeuNBk2msP73yU9fyg3DwnfY/RegDY5FG RVbkAfqv4X7i7Ok59qzgTFMaE+cazrm4naxLNf3qlLl7p3GhFMp/2njCgpI3KQmILf5s R/m2szpT2x6QFmFnlNsDKaFbAKdF9IWeP7erJiOlcLUaGHW7gA+Aq/fZipdSh6/9siU/ c9IMKknxHZ0ofi671Pogt4nxcJygo/rwEcXZXSbdALPEaR3mceXLKsnXljaB+/M8pwC2 H1g0OGwLWsqsffVpNrR7RApRroRmuOxKgrp3pO1ldsKfitc0o/cTHPJeSbDbOTt+vd1J 4R/w== X-Gm-Message-State: APjAAAVb/d0HGoUVWvKkAUqcbucwIokqVGKdeVLx8XuJ77iQd2yFl3kY /PUjkTDLdskDEgSczB46ZsZF+63U X-Google-Smtp-Source: APXvYqyydN5N0LKPPmyuukPcvqFWpc+Pckf0bDDasSHKtXcl1zAmZ5ZrEtNA650gMenokO7eKEDtnA== X-Received: by 2002:a02:5585:: with SMTP id e127mr4347434jab.25.1568729355220; Tue, 17 Sep 2019 07:09:15 -0700 (PDT) Received: from raichu (toroon0560w-lp140-01-69-159-39-167.dsl.bell.ca. [69.159.39.167]) by smtp.gmail.com with ESMTPSA id i18sm3436086ioj.81.2019.09.17.07.09.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Sep 2019 07:09:14 -0700 (PDT) Sender: Mark Johnston Date: Tue, 17 Sep 2019 10:09:12 -0400 From: Mark Johnston To: Masachika ISHIZUKA Cc: freebsd-current@freebsd.org Subject: Re: hang up with r352239 and r352386 with i5-7500 Message-ID: <20190917140912.GC35245@raichu> References: <3a5c3efe-4598-66ae-7e3f-a54c1dc8c2e8@freebsd.org> <20190916.230642.762794847379060930.ish@amail.plala.or.jp> <746a0593-3dad-e3f5-53db-994c9a058233@freebsd.org> <20190917.072041.480458056274937279.ish@amail.plala.or.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190917.072041.480458056274937279.ish@amail.plala.or.jp> User-Agent: Mutt/1.12.1 (2019-06-15) X-Rspamd-Queue-Id: 46XlNF5T5Yz43g5 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=YLgWWKgQ; dmarc=none; spf=pass (mx1.freebsd.org: domain of markjdb@gmail.com designates 2607:f8b0:4864:20::d43 as permitted sender) smtp.mailfrom=markjdb@gmail.com X-Spamd-Result: default: False [-2.28 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[3.4.d.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-0.58)[ip: (2.07), ipnet: 2607:f8b0::/32(-2.69), asn: 15169(-2.23), country: US(-0.05)]; FORGED_SENDER(0.30)[markj@freebsd.org,markjdb@gmail.com]; MID_RHS_NOT_FQDN(0.50)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[markj@freebsd.org,markjdb@gmail.com]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 14:09:18 -0000 On Tue, Sep 17, 2019 at 07:20:41AM +0900, Masachika ISHIZUKA wrote: > > On 2019-09-16 16:06, Masachika ISHIZUKA wrote: > >>> Can you please use absolute paths to i915kms.ko anyway, just to test? > >> The same hang up occure with kld_list="/boot/modules/i915kms.ko" > >> in /etc/rc.conf. > >> > > > > Even after applying the patch I suggested? > > Yes. > > kld_list="/boot/modules/drm.ko /boot/modules/i915kms.ko" > will hang as well. > > /boot/modules/{drm,i915kms}.ko is patched modules. > > # /boot/kernel.r352239/{drm,i915kms}.ko is not patched. Are you able to collect a kernel dump? If so, remove the kld_list setting and set debug.debugger_on_panic=0 and dev.drm.skip_ddb=1. Then manually kldload /boot/modules/i915kms.ko. If you are running an INVARIANTS kernel you might be hitting an assertion failure; having the vmcore would help us debug. From owner-freebsd-current@freebsd.org Tue Sep 17 15:17:36 2019 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 D1D19126979; Tue, 17 Sep 2019 15:17:36 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Xmv457lWz47VD; Tue, 17 Sep 2019 15:17:36 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1129) id A85DDF128; Tue, 17 Sep 2019 15:17:36 +0000 (UTC) Date: Tue, 17 Sep 2019 15:17:36 +0000 From: Li-Wen Hsu To: freebsd-testing@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD CI Weekly Report 2019-09-15 Message-ID: <20190917151736.GA52902@freefall.freebsd.org> Reply-To: freebsd-testing@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.11.4 (2019-03-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 15:17:36 -0000 (Please send the followup to freebsd-testing@ and note Reply-To is set.) FreeBSD CI Weekly Report 2019-09-15 =================================== Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-09-09 to 2019-09-15. During this period, we have: * 2095 builds (95.3% (-4.1) passed, 4.7% (+4.1) failed) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * 358 test runs (58.4% (-1.2) passed, 31.0% (-8.1) unstable, 10.6% (+9.3) exception) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 32 doc builds (100% (0) passed) Test case status (on 2019-09-15 23:59): | Branch/Architecture | Total | Pass | Fail | Skipped | | ------------------- | ---------- | ---------- | ------- | ------- | | head/amd64 | 7563 (+7) | 7501 (+6) | 0 (0) | 62 (+1) | | head/i386 | 7561 (+7) | 7490 (+6) | 2 (0) | 69 (+1) | | 12-STABLE/amd64 | 7433 (+40) | 7389 (+48) | 0 (-11) | 44 (+3) | | 12-STABLE/i386 | 7431 (+40) | 7380 (+51) | 0 (-11) | 51 (0) | | 11-STABLE/amd64 | 6846 (0) | 6802 (0) | 0 (0) | 44 (0) | | 11-STABLE/i386 | 6844 (0) | 6767 (0) | 34 (0) | 43 (0) | (The statistics from experimental jobs are omitted) If any of the issues found by CI are in your area of interest or expertise please investigate the PRs listed below. The latest web version of this report is available at https://hackmd.io/@FreeBSD-CI/report-20190915 and archive is available at https://hackmd.io/@FreeBSD-CI/, any help is welcome. ## News * [FCP 20190401-ci_policy: CI policy](https://github.com/freebsd/fcp/blob/master/fcp-20190401-ci_policy.md) is in "feedback" state, please check and provide comments on -fcp@ and -hackers@ mailing lists. ## Fixed Tests * https://ci.freebsd.org/job/FreeBSD-stable-12-amd64-test/ * https://ci.freebsd.org/job/FreeBSD-stable-12-i386-test/ * sys.netipsec.tunnel.aes_cbc_128_hmac_sha1.v6 * sys.netipsec.tunnel.aes_cbc_256_hmac_sha2_256.v6 * sys.netipsec.tunnel.aes_gcm_128.v6 * sys.netipsec.tunnel.aes_gcm_256.v6 * sys.netipsec.tunnel.aesni_aes_cbc_128_hmac_sha1.v6 * sys.netipsec.tunnel.aesni_aes_cbc_256_hmac_sha2_256.v6 * sys.netipsec.tunnel.aesni_aes_gcm_128.v6 * sys.netipsec.tunnel.aesni_aes_gcm_256.v6 * sys.netipsec.tunnel.empty.v6 * sys.netpfil.pf.fragmentation.v6 * sys.netpfil.pf.pass_block.v6 * https://bugs.freebsd.org/240437 ## Failing Tests * https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/ * local.kyua.* (31 cases) * local.lutok.* (3 cases) ## Failing and Flaky Tests (from experimental jobs) * https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/ * cddl.usr.sbin.dtrace.common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237641 * cddl.usr.sbin.dtrace.amd64.arrays.t_dtrace_contrib.tst_uregsarray_d * https://bugs.freebsd.org/240358 * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/ * There are ~60 failing cases, including flakey ones, see https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/ for more details ## Disabled Tests * lib.libc.sys.mmap_test.mmap_truncate_signal https://bugs.freebsd.org/211924 Patch available: https://reviews.freebsd.org/D21566 * sys.fs.tmpfs.mount_test.large https://bugs.freebsd.org/212862 * sys.fs.tmpfs.link_test.kqueue https://bugs.freebsd.org/213662 * sys.kqueue.libkqueue.kqueue_test.main https://bugs.freebsd.org/233586 * sys.kern.ptrace_test.ptrace__PT_KILL_competing_stop https://bugs.freebsd.org/220841 * lib.libc.regex.exhaust_test.regcomp_too_big (i386 only) https://bugs.freebsd.org/237450 * sys.netinet.socket_afinet.socket_afinet_bind_zero (new) https://bugs.freebsd.org/238781 * sys.netpfil.pf.names.names * sys.netpfil.pf.synproxy.synproxy https://bugs.freebsd.org/238870 * sys.kern.ptrace_test.ptrace__follow_fork_child_detached_unrelated_debugger https://bugs.freebsd.org/239292 * sys.netpfil.pf.forward.v4 (i386 only) * sys.netpfil.pf.forward.v6 (i386 only) * sys.netpfil.pf.set_tos.v4 (i386 only) https://bugs.freebsd.org/239380 (updating net/scapy to 2.4.3 may fix this) * sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger https://bugs.freebsd.org/239397 * sys.kern.ptrace_test.ptrace__parent_sees_exit_after_child_debugger https://bugs.freebsd.org/239399 * sys.kern.ptrace_test.ptrace__follow_fork_parent_detached_unrelated_debugger https://bugs.freebsd.org/239425 * lib.libc.gen.getmntinfo_test.getmntinfo_test https://bugs.freebsd.org/240049 * sys.sys.qmath_test.qdivq_s64q https://bugs.freebsd.org/240219 * (new) sys.kern.ptrace_test.ptrace__getppid https://bugs.freebsd.org/240510 ## Issues ### Cause build fails * https://bugs.freebsd.org/233735 Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory * https://bugs.freebsd.org/233769 Possible build race: ld: error: unable to find library -lgcc_s ### Cause kernel panics * https://bugs.freebsd.org/238870 sys.netpfil.pf.names.names and sys.netpfil.pf.synproxy.synproxy cause panic Patch exists: * https://reviews.freebsd.org/D20868 * https://reviews.freebsd.org/D20869 ### Open * https://bugs.freebsd.org/237403 Tests in sys/opencrypto should be converted to Python3 * https://bugs.freebsd.org/237641 Flakey test case: common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237656 "Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of memory." seen when running sys/netipsec tests * https://bugs.freebsd.org/238781 sys.netinet.socket_afinet.socket_afinet_bind_zero does not work when mac_portacl(4) loaded * https://bugs.freebsd.org/239292 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_child_detached_unrelated_debugger * https://bugs.freebsd.org/239380 sys.netpfil.pf.forward.{v4,v6} and sys.netpfil.pf.set_tos.v4 fail on i386 * https://bugs.freebsd.org/239397 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger * https://bugs.freebsd.org/239399 Flakey test case: sys.kern.ptrace_test.ptrace__parent_sees_exit_after_child_debugger * https://bugs.freebsd.org/239425 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_parent_detached_unrelated_debugger * https://bugs.freebsd.org/240085 Failing test: sys.netpfil.common.forward.pf_v4 on i386 * https://bugs.freebsd.org/240086 Failing test: sys.netpfil.common.tos.pf_tos on i386 ### Others * [Tickets related to testing@](https://preview.tinyurl.com/y9maauwg) From owner-freebsd-current@freebsd.org Tue Sep 17 15:29:10 2019 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 7F51A127034 for ; Tue, 17 Sep 2019 15:29:10 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [60.36.166.23]) by mx1.freebsd.org (Postfix) with ESMTP id 46Xn8M3q0Xz48JP for ; Tue, 17 Sep 2019 15:29:06 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc13.plala.or.jp with ESMTP id <20190917152901.BEOB18269.msc13.plala.or.jp@localhost> for ; Wed, 18 Sep 2019 00:29:01 +0900 Date: Wed, 18 Sep 2019 00:28:53 +0900 (JST) Message-Id: <20190918.002853.935521658808754450.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: panic: sleeping thread on r352386 From: Masachika ISHIZUKA In-Reply-To: <20190917122430.GZ2559@kib.kiev.ua> References: <20190917080658.GW2559@kib.kiev.ua> <20190917101826.GJ97181@server.rulingia.com> <20190917122430.GZ2559@kib.kiev.ua> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac13; Wed, 18 Sep 2019 00:29:01 +0900 X-Rspamd-Queue-Id: 46Xn8M3q0Xz48JP X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ish@amail.plala.or.jp designates 60.36.166.23 as permitted sender) smtp.mailfrom=ish@amail.plala.or.jp X-Spamd-Result: default: False [0.54 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.35)[-0.350,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:60.36.166.0/24]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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]; NEURAL_HAM_LONG(-0.75)[-0.751,0]; DMARC_NA(0.00)[plala.or.jp]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.44)[ip: (-0.98), ipnet: 60.32.0.0/12(2.99), asn: 4713(0.23), country: JP(-0.02)]; RCVD_NO_TLS_LAST(0.10)[]; RCVD_IN_DNSWL_LOW(-0.10)[23.166.36.60.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4713, ipnet:60.32.0.0/12, country:JP]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 15:29:10 -0000 >> >Try the following change, which more accurately tries to avoid >> >vnode_pager_setsize(). The real cause requires much more extensive >> >changes. >> > >> >diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c >> >index 63ea4736707..16dc7745c77 100644 >> >--- a/sys/fs/nfsclient/nfs_clport.c >> >+++ b/sys/fs/nfsclient/nfs_clport.c >> ... >> >> With that patch, I'm back to "Sleeping thread (...) owns a non-sleepable >> lock" panics. > > Try this. > > diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c > index 63ea4736707..a23b4ba4efa 100644 Thank you for new patch. It seems that this patch works fine. I patched to r352432(src) and 'make buildkernel && make installkernel && reboot' on r351728(kernel)/r352432(user land). After that, 'make -j4 buildworld && make -j4 buildkernel' on r352432M(patched kernel)/ r352432(user land) with the nfs file system was done successfully. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Tue Sep 17 15:29:57 2019 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 4D3BC1270FF for ; Tue, 17 Sep 2019 15:29:57 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [IPv6:2400:7800:0:502e::23]) by mx1.freebsd.org (Postfix) with ESMTP id 46Xn9H4ZSXz48R6 for ; Tue, 17 Sep 2019 15:29:55 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc13.plala.or.jp with ESMTP id <20190917152945.BEOR18269.msc13.plala.or.jp@localhost> for ; Wed, 18 Sep 2019 00:29:45 +0900 Date: Tue, 17 Sep 2019 23:59:30 +0900 (JST) Message-Id: <20190917.235930.528406816270492485.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: hang up with r352239 and r352386 with i5-7500 From: Masachika ISHIZUKA In-Reply-To: <20190917140912.GC35245@raichu> References: <746a0593-3dad-e3f5-53db-994c9a058233@freebsd.org> <20190917.072041.480458056274937279.ish@amail.plala.or.jp> <20190917140912.GC35245@raichu> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac13; Wed, 18 Sep 2019 00:29:45 +0900 X-Rspamd-Queue-Id: 46Xn9H4ZSXz48R6 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ish@amail.plala.or.jp designates 2400:7800:0:502e::23 as permitted sender) smtp.mailfrom=ish@amail.plala.or.jp X-Spamd-Result: default: False [-0.56 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.91)[-0.910,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2400:7800:0:502e::/60:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.96)[-0.963,0]; DMARC_NA(0.00)[plala.or.jp]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.02)[ipnet: 2400:7800::/32(-0.13), asn: 4713(0.23), country: JP(-0.02)]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4713, ipnet:2400:7800::/32, country:JP]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 15:29:57 -0000 >> >>> Can you please use absolute paths to i915kms.ko anyway, just to test? >> >> The same hang up occure with kld_list="/boot/modules/i915kms.ko" >> >> in /etc/rc.conf. >> >> >> > >> > Even after applying the patch I suggested? >> >> Yes. >> >> kld_list="/boot/modules/drm.ko /boot/modules/i915kms.ko" >> will hang as well. >> >> /boot/modules/{drm,i915kms}.ko is patched modules. >> >> # /boot/kernel.r352239/{drm,i915kms}.ko is not patched. > > Are you able to collect a kernel dump? If so, remove the kld_list > setting and set debug.debugger_on_panic=0 and dev.drm.skip_ddb=1. Then > manually kldload /boot/modules/i915kms.ko. If you are running an > INVARIANTS kernel you might be hitting an assertion failure; having the > vmcore would help us debug. Thank you for mail. As I'm busy now, I'll try to get kernel dump about 1 day after. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Tue Sep 17 16:25:02 2019 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 2E8A8128AEE for ; Tue, 17 Sep 2019 16:25:02 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46XpNt07LBz4D4j for ; Tue, 17 Sep 2019 16:25:02 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from [10.50.6.171] (wsip-184-181-13-226.ph.ph.cox.net [184.181.13.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: johalun) by smtp.freebsd.org (Postfix) with ESMTPSA id AD45E178AB for ; Tue, 17 Sep 2019 16:25:01 +0000 (UTC) (envelope-from johalun@FreeBSD.org) To: FreeBSD Current From: Johannes Lundberg Subject: wlan can't discover known networks after relocating Message-ID: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> Date: Tue, 17 Sep 2019 09:25:00 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 16:25:02 -0000 Hi For a long time now I have had this problem with iwm and wlan0. Whenever I move between work and home it won't reconnect automatically and I have to do wlan0 scan manually for it to pick up the different network. Anyone have a solution for this? For now I think I'll put a 'ifconfig wlan0 scan' in crontab to run every minute. Dell laptop, 13-CURRENT, always fairly recent. Also, I'm using lagg wifi failover but I'm pretty sure it's the same if I configure only wifi. Cheers! From owner-freebsd-current@freebsd.org Tue Sep 17 16:36:41 2019 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 1951C128E3C for ; Tue, 17 Sep 2019 16:36:41 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46XpfH1994z4Ddg; Tue, 17 Sep 2019 16:36:38 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (v-critter.freebsd.dk [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 0F6AB1AF3C5; Tue, 17 Sep 2019 16:36:29 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id x8HGaSiJ006987 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 17 Sep 2019 16:36:28 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id x8HGaSw6006986; Tue, 17 Sep 2019 16:36:28 GMT (envelope-from phk) To: Johannes Lundberg cc: FreeBSD Current Subject: Re: wlan can't discover known networks after relocating In-reply-to: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> From: "Poul-Henning Kamp" References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6984.1568738188.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Tue, 17 Sep 2019 16:36:28 +0000 Message-ID: <6985.1568738188@critter.freebsd.dk> X-Rspamd-Queue-Id: 46XpfH1994z4Ddg X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of phk@critter.freebsd.dk designates 130.225.244.222 as permitted sender) smtp.mailfrom=phk@critter.freebsd.dk X-Spamd-Result: default: False [-1.88 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.96)[-0.955,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.dk]; NEURAL_HAM_LONG(-1.00)[-0.996,0]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(0.07)[ip: (0.08), ipnet: 130.225.0.0/16(0.13), asn: 1835(0.13), country: EU(-0.01)]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FORGED_SENDER(0.30)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU]; FROM_NEQ_ENVFROM(0.00)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 17 Sep 2019 16:36:41 -0000 -------- In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org>, Johannes Lu= ndber g writes: >For a long time now I have had this problem with iwm and wlan0. Whenever >I move between work and home it won't reconnect automatically and I have >to do wlan0 scan manually for it to pick up the different network. I suffer from the dreaded "reason=3D0" when I move inside my house: > scan OK <3>CTRL-EVENT-SCAN-RESULTS = <3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID=3D'Palombia' freq=3D2= 452 MHz) <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:3d:a2:e9 reason=3D0 <3>CTRL-EVENT-SCAN-RESULTS = <3>Trying to associate with 6c:3b:6b:ab:ce:d4 (SSID=3D'Palombia' freq=3D2= 412 MHz) <3>Associated with 6c:3b:6b:ab:ce:d4 a2:e9 is the loudest AP here in my office, but my I have been in the other end of the house iwn consistently fails to associate with it and and keeps picking the weaker AP in the far end. Eventually (hours!) it disconnects from the weaker ap, also with "reason=3D0" and gets it right: <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 [GTK=3DCCMP] <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:ab:ce:d4 reason=3D0 <3>CTRL-EVENT-SCAN-RESULTS = <3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID=3D'Palombia' freq=3D2= 452 MHz) <3>Associated with 6c:3b:6b:3d:a2:e9 <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 [PTK=3DCCMP GTK=3D= CCMP] <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 completed [id=3D= 3 id_str=3D] <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 [GTK=3DCCMP] And yes, working roaming would be nice too... -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-current@freebsd.org Wed Sep 18 06:37:48 2019 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 EC2BAF32CD for ; Wed, 18 Sep 2019 06:37:48 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-zteg10011401.me.com (pv50p00im-zteg10011401.me.com [17.58.6.41]) (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 46Y9Jr0lQKz3Pm5 for ; Wed, 18 Sep 2019 06:37:47 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-zteg10011401.me.com (Postfix) with ESMTPSA id 3066D900D01; Wed, 18 Sep 2019 06:37:43 +0000 (UTC) From: Toomas Soome Message-Id: Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: r352368 can't boot Date: Wed, 18 Sep 2019 09:37:39 +0300 In-Reply-To: Cc: KIRIYAMA Kazuhiko , FreeBSD Current To: Warner Losh References: <201909170530.x8H5UGxo012419@kx.truefc.org> <5E929415-319A-490D-AB9A-2F8259391B13@me.com> <8A9627B9-8190-490C-8D76-6F2A9D00E059@me.com> X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-18_04:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909180070 X-Rspamd-Queue-Id: 46Y9Jr0lQKz3Pm5 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.20 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; URI_COUNT_ODD(1.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[me.com:+]; RCVD_IN_DNSWL_MED(-0.20)[41.6.58.17.list.dnswl.org : 127.0.5.2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-6.07), ipnet: 17.58.0.0/20(-3.36), asn: 714(-2.91), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[me.com]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 06:37:49 -0000 > On 17 Sep 2019, at 14:21, Warner Losh wrote: >=20 >=20 >=20 > On Tue, Sep 17, 2019, 11:24 AM Toomas Soome > wrote: >=20 >=20 >> On 17 Sep 2019, at 13:09, Warner Losh > wrote: >>=20 >>=20 >>=20 >> On Tue, Sep 17, 2019, 6:47 AM Toomas Soome > wrote: >>=20 >>=20 >> > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko > wrote: >> >=20 >> > Hi,all >> >=20 >> > Yesterday I've updated latest head (r352368) and rebuild >> > 13.0-CURRENT. All went fine, but when I boot, it's stopped >> > at boot stage. Then I typed `boot', booted normally and put >> > login prompt and login go ahead. But `shutdown -r now', >> > stopped at loader prompt same as login case. What happened? >> > All I've done is whithin bhyve VM. >> >=20 >> >=20 >>=20 >>=20 >> > Consoles: userboot =20 >> >=20 >> > FreeBSD/amd64 User boot, Revision 1.1 >> > (Mon Jun 18 16:11:55 UTC 2018 root@releng3.nyi.freebsd.org = ) >> > Loading /boot/defaults/loader.conf >> > xemit not found >> > Error while including /boot/frames.4th, in the line: >> > h_el @ xemit >> >=20 >> > can't load 'kernel' >> >=20 >> > Type '?' for a list of commands, 'help' for more detailed help. >> > OK=20 >> >=20 >>=20 >> This is unfortunate case where the guest image has more recent boot = scripts than hosts /boot/userboot.so has. I did push the fix for that = issue to stable/11 and stable/12. The patch does introduce xemit word. >>=20 >> Such situation is unfortunate, but accident waiting to happen with = this method where we are attempting to use bootloader (userboot.so) from = older system to load guest vm.=20 >>=20 >> Can we provide a fallback to xemit builtin for old systems without = it? I believe we did this for other things as a transition. Forth has a = way to do this, though we need to make sure we properly constrain what = we pass to emit... >>=20 >> Warner >>=20 >> P.s. I'm at legoland this week, so I can't look at it for a bit. >>=20 >=20 > Well, the only way to avoid such issue is to make sure the guest = environment is providing all the needed bits, but since we do have = interpreter inside the userboot.so and userboot.so is in host, this does = set rather unfortunate limits what we can do. >=20 > Yes. I understand that we are limited in our scripts to somehow = testing if xemit is a forth word and if not providing a fallback = implementation of it in forth using emit. >=20 >=20 done:) rgds, toomas From owner-freebsd-current@freebsd.org Wed Sep 18 08:15:32 2019 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 70F34F6F50 for ; Wed, 18 Sep 2019 08:15:32 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [60.36.166.23]) by mx1.freebsd.org (Postfix) with ESMTP id 46YCTY3W3Bz42n6 for ; Wed, 18 Sep 2019 08:15:28 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc13.plala.or.jp with ESMTP id <20190918081526.DHKT18269.msc13.plala.or.jp@localhost> for ; Wed, 18 Sep 2019 17:15:26 +0900 Date: Wed, 18 Sep 2019 17:15:20 +0900 (JST) Message-Id: <20190918.171520.1850897233083712866.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: hang up with r352239 and r352386 with i5-7500 From: Masachika ISHIZUKA In-Reply-To: <20190917.235930.528406816270492485.ish@amail.plala.or.jp> References: <20190917.072041.480458056274937279.ish@amail.plala.or.jp> <20190917140912.GC35245@raichu> <20190917.235930.528406816270492485.ish@amail.plala.or.jp> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac13; Wed, 18 Sep 2019 17:15:26 +0900 X-Rspamd-Queue-Id: 46YCTY3W3Bz42n6 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ish@amail.plala.or.jp designates 60.36.166.23 as permitted sender) smtp.mailfrom=ish@amail.plala.or.jp X-Spamd-Result: default: False [0.37 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.57)[-0.572,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:60.36.166.0/24]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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]; NEURAL_HAM_LONG(-0.71)[-0.708,0]; DMARC_NA(0.00)[plala.or.jp]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.45)[ip: (-0.93), ipnet: 60.32.0.0/12(2.99), asn: 4713(0.23), country: JP(-0.02)]; RCVD_NO_TLS_LAST(0.10)[]; RCVD_IN_DNSWL_LOW(-0.10)[23.166.36.60.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4713, ipnet:60.32.0.0/12, country:JP]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 08:15:32 -0000 >>> >>> Can you please use absolute paths to i915kms.ko anyway, just to test? >>> >> The same hang up occure with kld_list="/boot/modules/i915kms.ko" >>> >> in /etc/rc.conf. >>> >> >>> > >>> > Even after applying the patch I suggested? >>> >>> Yes. >>> >>> kld_list="/boot/modules/drm.ko /boot/modules/i915kms.ko" >>> will hang as well. >>> >>> /boot/modules/{drm,i915kms}.ko is patched modules. >>> >>> # /boot/kernel.r352239/{drm,i915kms}.ko is not patched. >> >> Are you able to collect a kernel dump? If so, remove the kld_list >> setting and set debug.debugger_on_panic=0 and dev.drm.skip_ddb=1. Then >> manually kldload /boot/modules/i915kms.ko. If you are running an >> INVARIANTS kernel you might be hitting an assertion failure; having the >> vmcore would help us debug. > > Thank you for mail. > > As I'm busy now, I'll try to get kernel dump about 1 day after. I'm very sorry. The patch you suggested is work fine. The reason why it didn't work was because the patch was applied to the wrong file. Now, drm-current-kmod is working fine on r352467 by your patch. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Wed Sep 18 08:31:14 2019 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 EDEF4F7590 for ; Wed, 18 Sep 2019 08:31:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46YCqk01Kkz43KJ for ; Wed, 18 Sep 2019 08:31:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x72e.google.com with SMTP id f16so7124324qkl.9 for ; Wed, 18 Sep 2019 01:31:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XhH3GUE4t5uQsDge1g6agrawubXE8qlIDObn6eQO6j8=; b=rST/rgzEfvEqLJTz500wHQh85NEuuMObxjWmY8Z3YK4LR0QMhoftMyBH7yre284ZXP YIe4nPr+ZzTLCozw5Iy/x3Uu/dFYg0aYIoCVcXe628pQ3HKsGiGs8KGY1m9zxhUsDgC3 y/e6XL4ZOr+n9uGuK1YRH9O+hecagvyrn9Jws5bp4SRUSvksnmsnDXceUGopKTXgATCt +VF88QNsDHDw8QRyKFGYRmFL/Mp5mw19UJUvWHBvd1lQ54+kgTsa1ufRoTMsZhbqzEGr kA46J3TmZzq+gTRrONwrGPdztmyw/UtDqb5wNR2dg/QLL6hgsxvIfWIFmcaLpBHur+wo W4DA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XhH3GUE4t5uQsDge1g6agrawubXE8qlIDObn6eQO6j8=; b=pfOkzQnZ0JHw01eUJBiXRWQVQ9OGBFJH5uFI+sfu1t5KHyshSMGukce+O2Fr0YfcUy o6ir/Nt/pV292UUfm0kqluIO5E1lEkGMx1e2jsZqAJSxq32c6+56vR+wNopiRspRuZ03 ZbZn91U/CcqNQdUnbm+mfI88a9x3kBmRhlAOApGebl4HxZkMADtSIGoQthrQ5pCHAemo xNAAX0/p4oCFkjeapf92aGTx2cDWLjK/2VWHOoo0NGnEd9N1ol+0Gd6NmF1gwvARDgD9 gFP+EUKsp+U+x37viAAs7OU++gov4G0XzQZzVvK0w9WvzgPs6bqJJBriTlBG5tvDJqYe JpLQ== X-Gm-Message-State: APjAAAVBqIQHJrMXpRB24Ij5jXxBif10Y+hKYJhplwQotvdVYIFciaB/ TL1/G0JNpY+ew6qK3Ikf6QEY+KhgjNBL/3Et+3IGJA== X-Google-Smtp-Source: APXvYqyeC8HGD6QxKuFyDGe1O8dBmMIz972xZFuvlqijBrgrocNOTaeK2pyJ5euBKRMMXuLlEaP9vhYtCA+/GHDw1XU= X-Received: by 2002:a37:30f:: with SMTP id 15mr2519790qkd.240.1568795472689; Wed, 18 Sep 2019 01:31:12 -0700 (PDT) MIME-Version: 1.0 References: <201909170530.x8H5UGxo012419@kx.truefc.org> <5E929415-319A-490D-AB9A-2F8259391B13@me.com> <8A9627B9-8190-490C-8D76-6F2A9D00E059@me.com> In-Reply-To: From: Warner Losh Date: Wed, 18 Sep 2019 09:31:00 +0100 Message-ID: Subject: Re: r352368 can't boot To: Toomas Soome Cc: KIRIYAMA Kazuhiko , FreeBSD Current X-Rspamd-Queue-Id: 46YCqk01Kkz43KJ X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=rST/rgzE; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::72e) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.86 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; URI_COUNT_ODD(1.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[e.2.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; FREEMAIL_TO(0.00)[me.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.86)[ip: (-9.33), ipnet: 2607:f8b0::/32(-2.68), asn: 15169(-2.23), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 08:31:15 -0000 On Wed, Sep 18, 2019, 7:37 AM Toomas Soome wrote: > > > On 17 Sep 2019, at 14:21, Warner Losh wrote: > > > > On Tue, Sep 17, 2019, 11:24 AM Toomas Soome wrote: > >> >> >> On 17 Sep 2019, at 13:09, Warner Losh wrote: >> >> >> >> On Tue, Sep 17, 2019, 6:47 AM Toomas Soome wrote: >> >>> >>> >>> > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko wrote: >>> > >>> > Hi,all >>> > >>> > Yesterday I've updated latest head (r352368) and rebuild >>> > 13.0-CURRENT. All went fine, but when I boot, it's stopped >>> > at boot stage. Then I typed `boot', booted normally and put >>> > login prompt and login go ahead. But `shutdown -r now', >>> > stopped at loader prompt same as login case. What happened? >>> > All I've done is whithin bhyve VM. >>> > >>> > >>> >>> >>> > Consoles: userboot >>> > >>> > FreeBSD/amd64 User boot, Revision 1.1 >>> > (Mon Jun 18 16:11:55 UTC 2018 root@releng3.nyi.freebsd.org) >>> > Loading /boot/defaults/loader.conf >>> > xemit not found >>> > Error while including /boot/frames.4th, in the line: >>> > h_el @ xemit >>> > >>> > can't load 'kernel' >>> > >>> > Type '?' for a list of commands, 'help' for more detailed help. >>> > OK >>> > >>> >>> This is unfortunate case where the guest image has more recent boot >>> scripts than hosts /boot/userboot.so has. I did push the fix for that issue >>> to stable/11 and stable/12. The patch does introduce xemit word. >>> >>> Such situation is unfortunate, but accident waiting to happen with this >>> method where we are attempting to use bootloader (userboot.so) from older >>> system to load guest vm. >>> >> >> Can we provide a fallback to xemit builtin for old systems without it? I >> believe we did this for other things as a transition. Forth has a way to do >> this, though we need to make sure we properly constrain what we pass to >> emit... >> >> Warner >> >> P.s. I'm at legoland this week, so I can't look at it for a bit. >> >> >> Well, the only way to avoid such issue is to make sure the guest >> environment is providing all the needed bits, but since we do have >> interpreter inside the userboot.so and userboot.so is in host, this does >> set rather unfortunate limits what we can do. >> > > Yes. I understand that we are limited in our scripts to somehow testing if > xemit is a forth word and if not providing a fallback implementation of it > in forth using emit. > > > > done:) > Thanks Warner rgds, > toomas > > > > From owner-freebsd-current@freebsd.org Wed Sep 18 09:37:06 2019 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 7F311F8E02 for ; Wed, 18 Sep 2019 09:37:06 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46YFHj4Vkkz478w for ; Wed, 18 Sep 2019 09:37:05 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-lj1-x22e.google.com with SMTP id q64so6469838ljb.12 for ; Wed, 18 Sep 2019 02:37:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=1+7UoBdBgIuVy9xOhNyx70cokyrnB3HqTZsR+WyG63E=; b=g53HR9gTWJ5MaG5VOAOpyul/9UHZRftYB+MBJ++9fVqj9hf+zvBnp+yqS9a9ZfQnUx ZwikubQG6R1OLToJ/KmQqBVmyQ+NGlWQkPCN2fIJt/mJb4F7Gz2MafqLYT1yqKzD6Lyj 5FHZ0wC7/SWIXedE6theYMk+r+31wQsKhq+vu4lQh9Y1Rd21s7ekdrHqcY2+kM0BgBh3 zSqsIdKrDKD7dJEzkLQG2f7oNXf7ZNurqyFkCupxzkXrYmn2sFQeq3yDUZI06mERSQXY BEnKEWy7ruvBPAOviHREC5HAe+O9fHP/8DYBve390qsPb3LJwGe72fR99+HZx/O4PFdP LGeA== 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=1+7UoBdBgIuVy9xOhNyx70cokyrnB3HqTZsR+WyG63E=; b=l6Yq2GbWcoGBwBxLaCCqCoaW9y+s1+iZE1Y424bq/wMb8XNnD+DXfryUhv1mgLVcD2 7b389ru1M9XIjlJkjdLuVqC6kLfnbZoPwey5pGlz5sPXW1F4OH41HYDPWYEIelK96dLI FdTk21zgC1XTgYtp88pKGnDpEB0RuDIOrIYUVJN0cU8J2tpVfZj5dZMSlwuKPgWkyqfA OcB44Zs59HQvktnV3mtTSbtFruNIJEAsrwoaoCvNZKwsDN0Wp0SMqt5twdVlbjXvQLtB 8Xx7CdKatJo0QCWlDvXvjMJztSu0m0CPcrm9wc9F3sBV3TWatNSSo4kKB8WNsS8e3FEM j4AQ== X-Gm-Message-State: APjAAAWHeOpjde6Jrl4MJsNbXMu6nXLKJnHUnGIowPtytq7vlrC5CSL6 8GHc/IlUsAg/DQWlyH16/lh+3/jd33JQE8HQ0yC3zwMBz2c= X-Google-Smtp-Source: APXvYqzk1auTOdiO5Z86GxlhSVHhEoW/l6xSFWttW/JxiRUwH9UlxLEqs8T0YhDymXd4YqsHOCWdvsAyYyEAQB8QXBM= X-Received: by 2002:a2e:87cb:: with SMTP id v11mr1623263ljj.31.1568799422706; Wed, 18 Sep 2019 02:37:02 -0700 (PDT) MIME-Version: 1.0 From: Andreas Nilsson Date: Wed, 18 Sep 2019 11:36:51 +0200 Message-ID: Subject: Problems upgrading -current with pkgbase To: Current FreeBSD X-Rspamd-Queue-Id: 46YFHj4Vkkz478w X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=g53HR9gT; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of andrnils@gmail.com designates 2a00:1450:4864:20::22e as permitted sender) smtp.mailfrom=andrnils@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(0.00)[ip: (-9.40), ipnet: 2a00:1450::/32(-2.95), asn: 15169(-2.23), country: US(-0.05)]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[e.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 09:37:06 -0000 Hello, I'm trying to upgrade my -current with pkgbase, using boot environments: $ bectl list BE Active Mountpoint Space Created 13C-20190902 NR / 72.3G 2019-09-02 13:43 13C-20190916 - /tmp/be_mount.JZ2z 127M 2019-09-18 11:21 Trying to go from a checkout 20190902 to 20190916, and it seems there have been some reorganization as how packages are created, quite a few smaller utilities like FreeBSD-libutil-13.0.s20190902093212 FreeBSD-libcom_err-13.0.s20190902093212 FreeBSD-libz-13.0.s20190902093212 seems to have been merged into FreeBSD-utilities: 13.0.s20190916114708 However, after upgrading all packages and installing FreeBSD-runtime, I notice that my /etc/passwd is reset to what is found on a new install. How to go about doing this upgrade without having important files reset to "factory default"? Best regards Andreas From owner-freebsd-current@freebsd.org Wed Sep 18 12:46:44 2019 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 7E482FCB53 for ; Wed, 18 Sep 2019 12:46:44 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46YKVX2gCDz4Gxd for ; Wed, 18 Sep 2019 12:46:44 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f181.google.com (mail-qk1-f181.google.com [209.85.222.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 2EFB2C4F for ; Wed, 18 Sep 2019 12:46:44 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f181.google.com with SMTP id u186so7860452qkc.5 for ; Wed, 18 Sep 2019 05:46:44 -0700 (PDT) X-Gm-Message-State: APjAAAXLbHNaWWhJ/ZXUj7af1Uu/kcj12c0EurkJlLWnoqvRXhM1YyMa GDRXcZCspui5FG/WlsgT95h1qE7kjMMI2NwYoGM= X-Google-Smtp-Source: APXvYqw1mutgJ6bpZw3NuNiIyXm1PZwT1mncJ/Grvl/PbNh6rJJ0FGVCuJhKf1RUviZVkv4G3PQRVYWdisjaQ8SLfkA= X-Received: by 2002:ae9:dd81:: with SMTP id r123mr3714336qkf.103.1568810803617; Wed, 18 Sep 2019 05:46:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kyle Evans Date: Wed, 18 Sep 2019 07:46:31 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Problems upgrading -current with pkgbase To: Andreas Nilsson Cc: Current FreeBSD Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 12:46:44 -0000 On Wed, Sep 18, 2019 at 4:37 AM Andreas Nilsson wrote: > > Hello, > > I'm trying to upgrade my -current with pkgbase, using boot environments: > $ bectl list > BE Active Mountpoint Space Created > 13C-20190902 NR / 72.3G 2019-09-02 13:43 > 13C-20190916 - /tmp/be_mount.JZ2z 127M 2019-09-18 11:21 > > Trying to go from a checkout 20190902 to 20190916, and it seems there have > been some reorganization as how packages are created, quite a few smaller > utilities like > > FreeBSD-libutil-13.0.s20190902093212 > FreeBSD-libcom_err-13.0.s20190902093212 > FreeBSD-libz-13.0.s20190902093212 > > seems to have been merged into > FreeBSD-utilities: 13.0.s20190916114708 > > However, after upgrading all packages and installing FreeBSD-runtime, I > notice that my /etc/passwd is reset to what is found on a new install. > > How to go about doing this upgrade without having important files reset to > "factory default"? > Hi, I filed a pkg PR about this a couple days ago: https://github.com/freebsd/pkg/issues/1781 -- we can enumerate the files that are being reset with those that manu's recently tagged for inclusion into a package to backup-and-restore manually around the upgrade for the time being, but the PR will be resolved in due time. Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Wed Sep 18 13:27:37 2019 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 D9458FD863 for ; Wed, 18 Sep 2019 13:27:37 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46YLPj5Qwrz4KDC; Wed, 18 Sep 2019 13:27:37 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-lj1-x22b.google.com with SMTP id f5so7218318ljg.8; Wed, 18 Sep 2019 06:27:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZEip8z/HZgsQPLf3SZGZUn9zHyDhYHaJbJWSYKNUr50=; b=agSWbUSeysxFhRct1SThw/UQcNeYPFRSDW68OmCHrkegKQmv+qEovwrVhC3iHVVdYN w1czytnpck5uhlRW2rkoBPAwPI0eMqXh/R3GCe3qDZqtE1fX8KDq1Qw95VFSb1bO5ccS +hTyYQ2xKMk48Vw4kd0NMTSYZT+MEFnaGvIz8Y8TbUPEUeypNGEmaE9byF0eN7VRhgwZ Rs5QQpGgSQ1K5hC1qJVAkM2LJQ2EdL5VgruizNvw6yyA4//QzOEKDAxiN2SwzkOz7TPW yR1utWdu210MEO1DlIEjGeqgn7lH0AhzAX44Bd6DdFQE5mbCJ5nV6TXNaxWwfIcdaB2q jCMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZEip8z/HZgsQPLf3SZGZUn9zHyDhYHaJbJWSYKNUr50=; b=KGI60frxyfhCHzjV8a+M8TKEUJdC8vnhAwSTHzigjxRg+QFFZ9oKAFkCmYA8r9u7gd h5AfBdfQYvTpHs7pK3q2YBoM40Y/1Q7+goUmvgN2FhNZNxlLgFJr6F/hVvqBWJx4+kV8 RHOgyplrrfVlpHNfNfbxRvWZ/L6taGDhJtrJ/ylgiLDz9hTconckjSxw13ReVyfPr552 bDxjc2CbWN6CRMKg9xDbLfD8Q+aGnzVJ1llKnbvugqpE+ADV5tUzwq6mGVoyVtYknKgf YVCxvK+g/BrtNGCdtE/vlslfVXe+jbBi2RFgTMxL8D/HN7koCA5lxGA3Kq8OIJfoNO3h LGBw== X-Gm-Message-State: APjAAAWShNkVH4YPq30eByjVO0C0vmHXwd2W3GnH/bawkoWk46BhvSJK Fliagau8ydE93dITqEzKz9VGhDYOUNuWzw6bk0WC5+6k X-Google-Smtp-Source: APXvYqxnQh2Rt3HERooik5Bi2aQ249xCJSoWWbv1DkcL9/NTsrBpt/i7L3tUegUhzDVKs4ys+SeXX72bGNp5/MZNU/c= X-Received: by 2002:a2e:924d:: with SMTP id v13mr2214365ljg.226.1568813254820; Wed, 18 Sep 2019 06:27:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Andreas Nilsson Date: Wed, 18 Sep 2019 15:27:23 +0200 Message-ID: Subject: Re: Problems upgrading -current with pkgbase To: Kyle Evans Cc: Current FreeBSD X-Rspamd-Queue-Id: 46YLPj5Qwrz4KDC X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 13:27:37 -0000 On Wed, Sep 18, 2019 at 2:46 PM Kyle Evans wrote: > On Wed, Sep 18, 2019 at 4:37 AM Andreas Nilsson > wrote: > > > > Hello, > > > > I'm trying to upgrade my -current with pkgbase, using boot environments: > > $ bectl list > > BE Active Mountpoint Space Created > > 13C-20190902 NR / 72.3G 2019-09-02 13:43 > > 13C-20190916 - /tmp/be_mount.JZ2z 127M 2019-09-18 11:21 > > > > Trying to go from a checkout 20190902 to 20190916, and it seems there > have > > been some reorganization as how packages are created, quite a few smaller > > utilities like > > > > FreeBSD-libutil-13.0.s20190902093212 > > FreeBSD-libcom_err-13.0.s20190902093212 > > FreeBSD-libz-13.0.s20190902093212 > > > > seems to have been merged into > > FreeBSD-utilities: 13.0.s20190916114708 > > > > However, after upgrading all packages and installing FreeBSD-runtime, I > > notice that my /etc/passwd is reset to what is found on a new install. > > > > How to go about doing this upgrade without having important files reset > to > > "factory default"? > > > > Hi, > > I filed a pkg PR about this a couple days ago: > https://github.com/freebsd/pkg/issues/1781 -- we can enumerate the > files that are being reset with those that manu's recently tagged for > inclusion into a package to backup-and-restore manually around the > upgrade for the time being, but the PR will be resolved in due time. > > Thanks, > > Kyle Evans > Hello, thanks for the information! Best regards Andreas From owner-freebsd-current@freebsd.org Wed Sep 18 15:01:22 2019 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 519E7FFB53 for ; Wed, 18 Sep 2019 15:01:22 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 46YNTs0TpPz4Qgy for ; Wed, 18 Sep 2019 15:01:20 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 7B6C521FE6 for ; Wed, 18 Sep 2019 11:01:19 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 18 Sep 2019 11:01:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h=to :from:subject:message-id:date:mime-version:content-type :content-transfer-encoding; s=fm1; bh=qgkDnDm2JEzTFOClFf4dnxMY+4 yMXMHNUlKVAe8ix7M=; b=YhIiM57lHKMo5W9f70tx9+fk7jNLSO83RhsQAjl8Id 8HGYJJd+xM6m2BnN2b42afx5G3dP5bWmtenpiWAtszyGLM77uzrRpT28GVqvOm8r a0/foCr1DUUIEEvqhuSghTyJhcW6lwrA2wLb4G24wFj1sO5znZp9Qzu58X6Pcahb JxyxNPbmfU1tH3DdUB7RbiJZMCVv4Ilq1WLHWwyWAh3kIj2XoTT+qt3vSemXmvNo ECG9dlUFOWtzUf7P7BQ9MRcnj+RgDMA5ledHFzRzFtqnKuqKh+ElRbmckYeCtwI9 gIsA2i9J2mmU+FGoaCVZWtn+motw+D+ExLBIQraDOC/g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=qgkDnD m2JEzTFOClFf4dnxMY+4yMXMHNUlKVAe8ix7M=; b=onmZUhPOs+5xMWkyMpAGJu yIcA89iey/HZTwc+Fi/oYgiLq61u91ckAYCF6SW5hB494vh2TiLRilnfcIDf8xz7 l/xXDEszTfFWQrGxQE81tjZmnQDQhGZzT2EMAXHsasbPLo/3sQCF4ROmA+3ww28g tbQGBwaqSvMPjq0318DIUzC0tRN5+8k+BHkZhNGUfFibv3arHkEOilv6+JBopi19 b5nIsRG4LuhOz8xeKEcHvfnxn5vZjxnLJIHVookRr5N/4OCRQJsC2C9kUOy8QFlQ csNsc6LGhIWMH79vlmNns9OXl6Tl9IaAXTkqH3tbJIGeenmmfLM5zLuMA8TLPf1A == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudekgdekvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepvffhuffkffgfgggtgfesthejredttd efjeenucfhrhhomhepjghurhhiucfrrghnkhhovhcuoeihuhhrihhpvheshihurhhiphhv rdhnvghtqeenucfkphepkeehrddujedvrdehgedruddugeenucfrrghrrghmpehmrghilh hfrhhomhephihurhhiphhvseihuhhrihhpvhdrnhgvthenucevlhhushhtvghrufhiiigv pedt X-ME-Proxy: Received: from [192.168.1.11] (unknown [85.172.54.114]) by mail.messagingengine.com (Postfix) with ESMTPA id A20A6D6006C for ; Wed, 18 Sep 2019 11:01:18 -0400 (EDT) To: freebsd-current From: Yuri Pankov Subject: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO Message-ID: Date: Wed, 18 Sep 2019 18:01:16 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46YNTs0TpPz4Qgy X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yuripv.net header.s=fm1 header.b=YhIiM57l; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=onmZUhPO; dmarc=none; spf=pass (mx1.freebsd.org: domain of yuripv@yuripv.net designates 66.111.4.25 as permitted sender) smtp.mailfrom=yuripv@yuripv.net X-Spamd-Result: default: False [-6.07 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[yuripv.net:s=fm1,messagingengine.com:s=fm3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.25]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[yuripv.net]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yuripv.net:+,messagingengine.com:+]; IP_SCORE(-3.47)[ip: (-9.75), ipnet: 66.111.4.0/24(-4.85), asn: 11403(-2.68), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[25.4.111.66.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[114.54.172.85.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 15:01:22 -0000 I have tested several snapshot ISOs available for download: FreeBSD-13.0-CURRENT-amd64-20190822-r351363-disc1.iso - OK FreeBSD-13.0-CURRENT-amd64-20190829-r351591-disc1.iso - OK FreeBSD-13.0-CURRENT-amd64-20190906-r351901-disc1.iso - FAIL FreeBSD-13.0-CURRENT-amd64-20190913-r352265-disc1.iso - FAIL FAIL being VM shutdown after loading kernel/modules and displaying "EFI framebuffer information". Relevant messages in the VM log are rather unhelpful: 2019-09-18T14:47:12.397Z| vcpu-0| I125: Guest: Firmware has transitioned to runtime. 2019-09-18T14:47:12.434Z| vcpu-0| I125: Msg_Post: Error 2019-09-18T14:47:12.434Z| vcpu-0| I125: [msg.efi.exception] The firmware encountered an unexpected exception. The virtual machine cannot boot. Any hints on debugging this further? From owner-freebsd-current@freebsd.org Wed Sep 18 15:30:56 2019 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 52A0412130E for ; Wed, 18 Sep 2019 15:30:56 +0000 (UTC) (envelope-from tsoome@me.com) Received: from mr85p00im-ztdg06011801.me.com (mr85p00im-ztdg06011801.me.com [17.58.23.199]) (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 46YP7z4gvGz4SQ2 for ; Wed, 18 Sep 2019 15:30:55 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by mr85p00im-ztdg06011801.me.com (Postfix) with ESMTPSA id BC6FCC1448 for ; Wed, 18 Sep 2019 15:30:53 +0000 (UTC) From: Toomas Soome Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO Date: Wed, 18 Sep 2019 18:30:50 +0300 References: To: freebsd-current In-Reply-To: Message-Id: <3978E5B5-CAB1-4214-AF9B-757BE1BEA923@me.com> X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-18_08:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=992 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909180152 X-Rspamd-Queue-Id: 46YP7z4gvGz4SQ2 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[me.com:+]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; RCVD_IN_DNSWL_LOW(-0.10)[199.23.58.17.list.dnswl.org : 127.0.5.1]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:714, ipnet:17.58.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; IP_SCORE(0.00)[ip: (-8.98), ipnet: 17.58.16.0/20(-2.37), asn: 714(-2.91), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 15:30:56 -0000 > On 18 Sep 2019, at 18:01, Yuri Pankov wrote: >=20 > I have tested several snapshot ISOs available for download: >=20 > FreeBSD-13.0-CURRENT-amd64-20190822-r351363-disc1.iso - OK > FreeBSD-13.0-CURRENT-amd64-20190829-r351591-disc1.iso - OK > FreeBSD-13.0-CURRENT-amd64-20190906-r351901-disc1.iso - FAIL > FreeBSD-13.0-CURRENT-amd64-20190913-r352265-disc1.iso - FAIL >=20 > FAIL being VM shutdown after loading kernel/modules and displaying = "EFI framebuffer information". Relevant messages in the VM log are = rather unhelpful: >=20 > 2019-09-18T14:47:12.397Z| vcpu-0| I125: Guest: Firmware has = transitioned to runtime. > 2019-09-18T14:47:12.434Z| vcpu-0| I125: Msg_Post: Error > 2019-09-18T14:47:12.434Z| vcpu-0| I125: [msg.efi.exception] The = firmware encountered an unexpected exception. The virtual machine cannot = boot. >=20 > Any hints on debugging this further? Im not really sure about debugging; I can not tell about early kernel, = but I=E2=80=99d check if the kernel/module locations conflict with efi = memory map items=E2=80=A6=20 The same issue can be seen with vmware fusion, it is not 100% repeatable = but I=E2=80=99d say, 95%, starting grab_faults, perhaps ls or some other = random command, and boot -v may actually start the system up.=20 rgds, toomas From owner-freebsd-current@freebsd.org Wed Sep 18 15:33:00 2019 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 232A9121521 for ; Wed, 18 Sep 2019 15:33:00 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::25]) (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 46YPBM5t5Tz4SlW for ; Wed, 18 Sep 2019 15:32:59 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 46YPBJ0n0jz3c7b for ; Wed, 18 Sep 2019 15:32:56 +0000 (UTC) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([127.0.0.1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [127.0.0.1]) (amavisd-new, port 10587) with ESMTPS id D2O8ldcn1N7z for ; Wed, 18 Sep 2019 15:32:55 +0000 (UTC) Received: from garnet.daemonic.se (host-90-232-139-242.mobileonline.telia.com [90.232.139.242]) by mail.daemonic.se (Postfix) with ESMTPSA id 46YPBH2z6Pz3c7Z for ; Wed, 18 Sep 2019 15:32:55 +0000 (UTC) Subject: Re: hang up with r352239 and r352386 with i5-7500 To: freebsd-current@freebsd.org References: <20190917.072041.480458056274937279.ish@amail.plala.or.jp> <20190917140912.GC35245@raichu> <20190917.235930.528406816270492485.ish@amail.plala.or.jp> <20190918.171520.1850897233083712866.ish@amail.plala.or.jp> From: Niclas Zeising Message-ID: <5fa15ee8-a1cb-37e7-b954-c50b1cd0a8d9@freebsd.org> Date: Wed, 18 Sep 2019 17:32:54 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <20190918.171520.1850897233083712866.ish@amail.plala.or.jp> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46YPBM5t5Tz4SlW X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-2.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; ASN(0.00)[asn:36236, ipnet:2607:f740:d::/48, country:US]; NEURAL_HAM_LONG(-1.00)[-0.999,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 15:33:00 -0000 On 2019-09-18 10:15, Masachika ISHIZUKA wrote: >>>>>>> Can you please use absolute paths to i915kms.ko anyway, just to test? >>>>>> The same hang up occure with kld_list="/boot/modules/i915kms.ko" >>>>>> in /etc/rc.conf. >>>>>> >>>>> >>>>> Even after applying the patch I suggested? >>>> >>>> Yes. >>>> >>>> kld_list="/boot/modules/drm.ko /boot/modules/i915kms.ko" >>>> will hang as well. >>>> >>>> /boot/modules/{drm,i915kms}.ko is patched modules. >>>> >>>> # /boot/kernel.r352239/{drm,i915kms}.ko is not patched. >>> >>> Are you able to collect a kernel dump? If so, remove the kld_list >>> setting and set debug.debugger_on_panic=0 and dev.drm.skip_ddb=1. Then >>> manually kldload /boot/modules/i915kms.ko. If you are running an >>> INVARIANTS kernel you might be hitting an assertion failure; having the >>> vmcore would help us debug. >> >> Thank you for mail. >> >> As I'm busy now, I'll try to get kernel dump about 1 day after. > > I'm very sorry. > > The patch you suggested is work fine. > The reason why it didn't work was because the patch was applied > to the wrong file. > > Now, drm-current-kmod is working fine on r352467 by your patch. > Hi! I just updated the port with the fix I suggested earlier, hopefully it works. It will take some time before it shows up as packages, but there is no problems building drm-current-kmod from ports even if packages are used for the rest of the system. Regards -- Niclas Zeising From owner-freebsd-current@freebsd.org Wed Sep 18 15:45:15 2019 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 D3EDB12199C for ; Wed, 18 Sep 2019 15:45:15 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 46YPSV6Y6fz4TLq for ; Wed, 18 Sep 2019 15:45:14 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 4B28D21FF3 for ; Wed, 18 Sep 2019 11:45:14 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 18 Sep 2019 11:45:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=B VDrx2DI+9Q8LA17tgBYwJaeCUq/TyiGpmiYetTrYf4=; b=h7vLJKor/BuuqIoTL Q8mVwDEV7VWwrjxoDVhitBHfrx5Pj6dmY5V3m55X54JNuaiHSr1uFB2qpZYpfGa0 MJqt7hz6m6T2xojsdcQyRxklh41QU1L2pIzUL934OJArgE8d7JvWFlyKtIYYrdif vqUghf6B/lL1l/+oYVKDB1KwqEA+bO3YadZOWWhcXJyyczo5aChuWey7axNwT8sD gO7dJ2WM7QPMQ6pmh6jtE8caQ4lpEIqB+KovYNm6KYT/kcwakE9LsE05QDi2mL/u Cj/nawtc9gap7fOEuTrsY1cMwJCRjP5TfNFYWQoUszo7iItRJTL/9X/vKvlMokws 9Go9A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=BVDrx2DI+9Q8LA17tgBYwJaeCUq/TyiGpmiYetTrY f4=; b=D/+1dSn95nd5AsACrwUZOoCjOmy7mdbZCmm2UgQT7jBw11kn+v4Nzyv5V qU5MXUJE0DN0WKB1rQ+ocLLXPJZeeR1M9UDcMnzHCjC6V/EFQ5rKH+cM6X9T1+mF fPAubXsFu6kIkmhdo4c6Pw5TsRIVHZV1ROe15XMJZWdUNMjwSKDlwXkd4DogXzJe dmLTOWrL7luH9Oq9ACYY7+D7hMNEy8S01yO7oCciJEXzNgPrM8B/SYtAWUeas26I F50aqWoCuz1J2qLOoZoLhvMcUh92BH3kIKs+wDUCMpenzayJmRbyhgcd4OqlphTA M40mVIP0BW+3LmZfrdCxTLTRWt+Ag== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudekgdeludcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepjghurhhiucfrrghnkhhovhcuoeihuhhrihhpvheshihurhhi phhvrdhnvghtqeenucfkphepkeehrddujedvrdehgedruddugeenucfrrghrrghmpehmrg hilhhfrhhomhephihurhhiphhvseihuhhrihhpvhdrnhgvthenucevlhhushhtvghrufhi iigvpedt X-ME-Proxy: Received: from [192.168.1.11] (unknown [85.172.54.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 70984D60062 for ; Wed, 18 Sep 2019 11:45:13 -0400 (EDT) Subject: Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO To: freebsd-current References: <3978E5B5-CAB1-4214-AF9B-757BE1BEA923@me.com> From: Yuri Pankov Message-ID: Date: Wed, 18 Sep 2019 18:45:11 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <3978E5B5-CAB1-4214-AF9B-757BE1BEA923@me.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 46YPSV6Y6fz4TLq X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yuripv.net header.s=fm1 header.b=h7vLJKor; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=D/+1dSn9; dmarc=none; spf=pass (mx1.freebsd.org: domain of yuripv@yuripv.net designates 66.111.4.26 as permitted sender) smtp.mailfrom=yuripv@yuripv.net X-Spamd-Result: default: False [-6.06 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[yuripv.net:s=fm1,messagingengine.com:s=fm3]; RECEIVED_SPAMHAUS_PBL(0.00)[114.54.172.85.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[yuripv.net]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(-3.46)[ip: (-9.73), ipnet: 66.111.4.0/24(-4.85), asn: 11403(-2.68), country: US(-0.05)]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yuripv.net:+,messagingengine.com:+]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[26.4.111.66.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 15:45:15 -0000 Toomas Soome wrote: > > >> On 18 Sep 2019, at 18:01, Yuri Pankov wrote: >> >> I have tested several snapshot ISOs available for download: >> >> FreeBSD-13.0-CURRENT-amd64-20190822-r351363-disc1.iso - OK >> FreeBSD-13.0-CURRENT-amd64-20190829-r351591-disc1.iso - OK >> FreeBSD-13.0-CURRENT-amd64-20190906-r351901-disc1.iso - FAIL >> FreeBSD-13.0-CURRENT-amd64-20190913-r352265-disc1.iso - FAIL >> >> FAIL being VM shutdown after loading kernel/modules and displaying "EFI framebuffer information". Relevant messages in the VM log are rather unhelpful: >> >> 2019-09-18T14:47:12.397Z| vcpu-0| I125: Guest: Firmware has transitioned to runtime. >> 2019-09-18T14:47:12.434Z| vcpu-0| I125: Msg_Post: Error >> 2019-09-18T14:47:12.434Z| vcpu-0| I125: [msg.efi.exception] The firmware encountered an unexpected exception. The virtual machine cannot boot. >> >> Any hints on debugging this further? > > Im not really sure about debugging; I can not tell about early kernel, but I’d check if the kernel/module locations conflict with efi memory map items… > > The same issue can be seen with vmware fusion, it is not 100% repeatable but I’d say, 95%, starting grab_faults, perhaps ls or some other random command, and boot -v may actually start the system up. OK. It's 100% reproducible here, going from 20190829 (which works) to 20190906 (which doesn't), so I was wondering if anything in r351591-r351901 range could be pointed at as a likely offender. From owner-freebsd-current@freebsd.org Wed Sep 18 19:54:57 2019 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 11A14125D0C for ; Wed, 18 Sep 2019 19:54:57 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vtr.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46YW0c0VgXz3CmP for ; Wed, 18 Sep 2019 19:54:55 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp239-208.static.internode.on.net [59.167.239.208]) by vtr.rulingia.com (8.15.2/8.15.2) with ESMTPS id x8IJsbgv034163 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 19 Sep 2019 05:54:42 +1000 (AEST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id x8IJsVV2031708 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Sep 2019 05:54:31 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id x8IJsV2k031707; Thu, 19 Sep 2019 05:54:31 +1000 (AEST) (envelope-from peter) Date: Thu, 19 Sep 2019 05:54:31 +1000 From: Peter Jeremy To: Konstantin Belousov Cc: Masachika ISHIZUKA , freebsd-current@freebsd.org, Rick Macklem Subject: Re: panic: sleeping thread on r352386 Message-ID: <20190918195431.GA31411@server.rulingia.com> References: <20190916.205532.1314832713594158104.ish@amail.plala.or.jp> <16601631.sFgvYJuXru@direwolf.local.> <20190917.144251.30337396601444833.ish@amail.plala.or.jp> <20190917080658.GW2559@kib.kiev.ua> <20190917101826.GJ97181@server.rulingia.com> <20190917122430.GZ2559@kib.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="nFreZHaLTZJo0R7j" Content-Disposition: inline In-Reply-To: <20190917122430.GZ2559@kib.kiev.ua> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.12.1 (2019-06-15) X-Rspamd-Queue-Id: 46YW0c0VgXz3CmP X-Spamd-Bar: ------- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of peter@rulingia.com designates 2001:19f0:5801:ebe:5400:1ff:fe53:30fd as permitted sender) smtp.mailfrom=peter@rulingia.com X-Spamd-Result: default: False [-7.58 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_NA(0.00)[rulingia.com]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; SIGNED_PGP(-2.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:20473, ipnet:2001:19f0:5800::/38, country:US]; RCVD_TLS_ALL(0.00)[]; IP_SCORE(-3.18)[ip: (-9.91), ipnet: 2001:19f0:5800::/38(-4.94), asn: 20473(-0.99), country: US(-0.05)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 19:54:57 -0000 --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2019-Sep-17 15:24:30 +0300, Konstantin Belousov wr= ote: >Try this. > >diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c >index 63ea4736707..a23b4ba4efa 100644 Sorry for the delay but I'm not seeing problems with this version of your patch (now r352457) either. Thank you for your efforts. --=20 Peter Jeremy --nFreZHaLTZJo0R7j Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAl2Ci2FfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzRdYw/9F9umf2QioqOTGVgPNVlVTPb4Qm9SLALpTJUM/36uOVTP/naqwPIQVaRd x8B/11R8J3LoWhQzabLPfF/+JzA3XmSsQijwM3ZxXkLiwI/1pAzWUMjRL2LUuUMH 7IkRus36qWhsjjRKZprub6wRZLcdoKpCgDoxJxWEXiUf+OtNYEQ2g65YO743dCwY EcFC8QrE8TFNMC6VYvBCJy+SJnQefatKswgENzt1/3l1yrwrkeoqUcQhjJg1lYCG N5098ZRZtkBSMSfb3AB/JlQMsdlZqLCpus6gJqYpqbkKke6LQwa6clHRQh85Btrl MTuhPzmekm1QPJfyVakTbR2hvJ8WZI8rsFJCP/8/dfHr8uOUPejk4hRAHxzonWww 7mewdHbpI6Giv+mRYKeDZckl8RudZuk01cWZ94m/3glHEvsFIuq9Nbb83j693pdA QsaPHhqlTbeH4IjckeUGmGwYRTQcKt2+07roQgJ0btxf22uYllUK3Je0Lh7kB56E DL4iJ+/w5jb+GhGx+cpM3fOENQoe/vOBMU8CX3Gd0DmNrap9QQ6UnAJpz2WpYhH9 Asj7f31Ty3JRA1kV7HPLLD4DRL+UPchh5aoSGt5GFyWfwEQDHqNqmTJx+0PEYEih WWIzmQVt6dPSr8M4wyykzqOI4im8ouhKFPJjXtg9oLsG4HLpz4w= =ahiA -----END PGP SIGNATURE----- --nFreZHaLTZJo0R7j-- From owner-freebsd-current@freebsd.org Wed Sep 18 22:28:18 2019 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 4B3ADE84F0 for ; Wed, 18 Sep 2019 22:28:18 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from muon.bsdio.com (muon.bluestop.org [65.103.231.193]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46YZPX52Shz3LXm for ; Wed, 18 Sep 2019 22:28:16 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from muon.bsdio.com (localhost [127.0.0.1]) by muon.bsdio.com (Postfix) with ESMTP id 16585890D3; Wed, 18 Sep 2019 16:28:17 -0600 (MDT) Received: from muon.bsdio.com ([127.0.0.1]) by muon.bsdio.com (muon.bsdio.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 6lpUolLbtZoO; Wed, 18 Sep 2019 16:28:16 -0600 (MDT) Received: from photon.int.bluestop.org (unknown [10.0.10.150]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by muon.bsdio.com (Postfix) with ESMTPSA; Wed, 18 Sep 2019 16:28:16 -0600 (MDT) Subject: Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO To: Yuri Pankov , freebsd-current References: From: Rebecca Cran Autocrypt: addr=rebecca@bsdio.com; keydata= mQINBFrUMZ4BEADI1yUEGeZeXeTCPay1ZpTBdDEpGPAw1dq2VCSTc1VhsnrEBa1iZxAfaeSv Uu5Ti7jlhQ/3sQMl0bJMKGB/RtmIW7k8h2w476oZmG8gChk8su5ZEx/pV1gdqInyFmmJKTYc gabJz8pL+m82w07qPv+oalepZ4dbj+HF++RAK/iEju+q9UHlsjj8e3mMNsvtrOz1K6bnpveO jZ+ms/2H3Hs5a4k8y6buwe2RvwhJQaXa13cR3LhzL+nwj4B9PHZZEa2WpEyYpw/bI0V9YSQN QgC1CYRzDyakZge6BCM6wHOgZSUzRPufGilrNKUwIVbRoIBR9/85+0wR+PlFUOUOfOc6ox7T dWcIx6PuPhek48rh4uwmmwsPtPiH4Z3T5p+GmWQ9NLFZKA1YnEdaSkWtYZsDxwVZZeYG2plt MfhXP0Hj4rf9Y3eoUenCaGioxAbUOBCtXdTGNAhNjz1g5NGDBVyhjKkzwJQvt9UrYTseERit 5dX2CMTy8hYLvSXd/Ivy+HylUS5IslfZxW5z9LgWX7Z97kILgkH3N0ewtLkygkG+Y+x7uaAV dFqp9ASOyzaiwKbJdeOI+WxRSh+AqeCR0S+bpkcLudLmbjrPmaFwjKycy1H85Z5R2J3YHyXY oT6OYjD8vLbUU2GWp6Onkcy1Pu8EMbRuzKil6HnpYg3BexbPFwARAQABtCNSZWJlY2NhIENy YW4gPHJlYmVjY2FAYmx1ZXN0b3Aub3JnPokCVwQTAQgAQQIbIwUJCWYBgAULCQgHAgYVCgkI CwIEFgIDAQIeAQIXgBYhBB+5fZtkTdO940Yr4g0CK1MRvhAgBQJa2B9zAhkBAAoJEA0CK1MR vhAgzJEQAJUqVmTRO9OqCSS2CVKjrqnEWJMvyo0K8B+WiXo0nSQg9+uyoVU7h2s/kkWVGy4u IWbGy2Qe8LiXzBJjHC3TadGvOvakfdMeKKXcgxgX6KlhA9hA2LW6tg22aHUk7Flr/8diHpgf qIwrXhqJXZmK72GR1QfhgoHsOsTJ9GWPswo1kUMc0cJowq0qP1RDdua6BwvDHHPJwu9OmC/i oQlMNm9gkBDq8H2B+m125ANwCnqBizXaiTTLQdewTMbCSuxbsni2icDqwBfFXzEgcJGaYYfB cQeFsfCmtXQK3JUd4Myx128Dxk9P3X64I93SB7QzB0nmWlyvmCFBNoCp0PCLA4qbwbw2sMRX Wx4BqYa8nI/jg+Nqo+Ut2BfltNZIlsHxK+XhxejfLqAjRCZeLnu1otvFnFuGLaAVYx9x1Y1q J8VizZxq6ujio62Qpultp6KNhlkJ+OKoGwA0k4NHh26SxvlsNxlfg/2v9b1LqWRzNujnwbcF 8g4902XjyBLxV+9YpXZEa8H6zzEHxpeDPWT3QfvrT8JuoHa1IyYnUKvG674UKW5zEGEwkQc9 cuQwR1RHd1ZrKtH1duXzaLr/caMp8ZDfGDDxFpenJTRxNRlg4+K7HSdhpac7sBVMUA8uVdE+ iuTThOmdf0c4DorL3BIh6Yv3FV4/NSqT1Wn3CG2fgG1guQINBFrUMZ4BEADkc4mvMcMcDF1t dNxNQuIBE1F243oZamG3LACCKfc1Yur3CPzHwIk5LXCUmbq23iE5bowxMWw3mlVT0p5xM0Wn UidIBwCKu4kRyy/fY4NyWWBuwy9srpTdmUcKRBRNB8zEZE8xIlidD1ijjgqLBfeM7n9ylawA xHLxwU96sdpdHFzb7Z0yKY2e/bzDaHiG0fUvcCmkgLf+uwKKZid1j8zR5PzKpgPqfy/PF01e KyGV3MNu8Y90xMoiEMWfCI2IB1m+hTuzZoboFvGV54SiMuvfWK/VMQjhsL6K2ddOqwVuy2nI MI4G3xDQW/v8KVyn43OSIAyW1eaklhzu0Ir2sO60PXRkvbTUrouvmSvpJfIQS49rU0M/X6FS DgXQLKrZ3my94+g8ptz9KoVml6s4OAwYVz+sb49nuSxipFKkU5FwhKOLmzbsBxCtytcUJoLm juJPJPDQue6YJiIXyc86GVY2pH3DjemKdbB4dSgqAJIp+lCzKSJzz7bgueh2Ox8vzx1tSxKj 7V8Nal+UTKKbkxPmMh+e20YZ4esAVifO3bS6IJP/aDnfagghB71vA7+aWGXPbjPlc2UHpCBi RSsl+IgoQXvdvZBsKRyfBx8neODa2C6JIE5vcaCjilSeKF8SzsFXvimnndhQNhAPU/DwQwSX dCl4gTsFVi5d8Oxq1sce+wARAQABiQI8BBgBCAAmFiEEH7l9m2RN073jRiviDQIrUxG+ECAF AlrUMZ4CGwwFCQlmAYAACgkQDQIrUxG+ECAWnRAAsmZX+KgNxW3v7R/76Tz4Wjmh4AGeE+Ji 3p5QsdTYny1B6vYBL9vCzPJ/AK8pgKMDRaweUP5eZQpfrdWC8Q7SNGgi4Q+97KEs+i2xZLQ+ WJb8a+WEEIc716u0y4ITiHfOgM5jWcFO4MXQATbJgv0drLLesa+LQCvZgPBqupt307EsCubQ s+Sxt+RVjf6rOUolp1GJXEQYwGsKklVd6yqLC8M1BSG53/WE5tSv5GzBZ8fp6EtmjT7leuid FtEvKYHQz4DqG9ELpHUF0X0UUCBK/MgXe3kCVLKE060UrJ4M6uPSx57rmVFA2MvwQR8M7GsW C5UsSM4PYwPWBhwxE7vcx0691YKAHT/5q8LxRVBdUyzPSprMhSQFttsBt+ygm6wRi3Pi3TuC EARNubPkQefyeC34yr40SAUCkOl3eWxSXPF4NfXFQb4AAzZSE5hv3qbDuwo3lrL0LqpIpEQP Az+JZ1QZ6mMFQ5/JD9Gukj54kZc0X8w3sQt0a8vyE/qrJg8vKgv2rCHrPc5MeDkEUEFiiJiC EDdkJtMyoRlU3S4NrnbyLOLEcHE8fGe3hStPX8hY62id2ecdQ5WZ7vLZW5SFeLarbUciuHIk VL6MHnUjbV7XlY50N7ebeFCIdlCWhdum2FJs/Ni+SSxbZC564vrokwlBBGSo6WTPQTa8IWx1 DtU= Message-ID: <2c2da4f1-052e-d8e7-a10e-079879975f92@bsdio.com> Date: Wed, 18 Sep 2019 16:28:07 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 46YZPX52Shz3LXm X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of rebecca@bsdio.com has no SPF policy when checking 65.103.231.193) smtp.mailfrom=rebecca@bsdio.com X-Spamd-Result: default: False [-3.90 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[bsdio.com]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:209, ipnet:65.100.0.0/14, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.81)[ip: (-9.05), ipnet: 65.100.0.0/14(-4.86), asn: 209(-0.06), country: US(-0.05)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 22:28:18 -0000 On 2019-09-18 09:01, Yuri Pankov wrote: > > Any hints on debugging this further? Are you running ESXi 6.7 Update 2? Or, what version of ESXi are you using that has the problem? -- Rebecca Cran From owner-freebsd-current@freebsd.org Wed Sep 18 22:29:34 2019 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 1170AE8607 for ; Wed, 18 Sep 2019 22:29:34 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 46YZR11CbSz3Lgn for ; Wed, 18 Sep 2019 22:29:32 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id F0ADF216CA; Wed, 18 Sep 2019 18:29:30 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 18 Sep 2019 18:29:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=i prd7iLAJHIToo4YN7xMU/r3MoZIgcbqKmH2X5OQ37I=; b=Oiqs+lPKqR1F5WO6+ CqapqpVZUaE6lUqijo6oOvohseJpn4TUKpcq0EOqn9pyQkfaRQfstxqN0mFbID1t KfRzBPCtIR9R5uGvsjKdfRDvQXjC/LTXpdl5qOAoMAsf1tML8amq1KT7eCKZEIYa D8O2gns8312HwwrLXWBNfYtJpB/2+2FidFfEjgEzyGiBIp1PYpRQBijaMOqsH/L1 I3YiSx6Qj1W96b9u/0L0Gx/gUNOnOi6Bk8Pk74nelyzADpCIfhqRMfynj91ndR7T /bhCgjx4rwqhZoPQYn57trY2UvX1UkoEVMXGQbRrOAwJpWu3mY4KBrIzRVq97sXb JXY7w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=iprd7iLAJHIToo4YN7xMU/r3MoZIgcbqKmH2X5OQ3 7I=; b=jSYMIkmrQhjGsnRQDva0rAlQnBDSUsWwIOn0R16wBW/PzhR+jf6Tt8TfK gdgivzWbU5kpz5nUvq7JtQtIu6rrVuS5EujQTr6xmiz8xo3nFWGvpXDdqJCF6Rak ro0cuI5UzanURBD/jGIIz9M48LV2rHTf3apiOEF1igc51GH+KgE7PQ+R8imi5Pm2 JE8NAiF5d486t56RWOw/dlcMuJkCKftH9wWmwt9+tX411qZnNsZHobLs+cNXKrZC eTpiPNb0rNCbLO15XbboiEmqHffoMhGp3TcInGJYjzxzQIq+NTkE4AKxfnIpO5jZ QXWHPxUqs+yfb1fpr4VOOZPaz1oHQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudelgdduvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhffkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpegjuhhrihcu rfgrnhhkohhvuceohihurhhiphhvseihuhhrihhpvhdrnhgvtheqnecukfhppeekhedrud ejvddrheegrdduudegnecurfgrrhgrmhepmhgrihhlfhhrohhmpeihuhhrihhpvheshihu rhhiphhvrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from [192.168.1.11] (unknown [85.172.54.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 12FE9D6005B; Wed, 18 Sep 2019 18:29:29 -0400 (EDT) Subject: Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO To: Rebecca Cran , freebsd-current References: <2c2da4f1-052e-d8e7-a10e-079879975f92@bsdio.com> From: Yuri Pankov Message-ID: <58d44015-3b59-659b-607a-e056ad45607f@yuripv.net> Date: Thu, 19 Sep 2019 01:29:27 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <2c2da4f1-052e-d8e7-a10e-079879975f92@bsdio.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46YZR11CbSz3Lgn X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yuripv.net header.s=fm1 header.b=Oiqs+lPK; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=jSYMIkmr; dmarc=none; spf=pass (mx1.freebsd.org: domain of yuripv@yuripv.net designates 66.111.4.29 as permitted sender) smtp.mailfrom=yuripv@yuripv.net X-Spamd-Result: default: False [-6.08 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[yuripv.net:s=fm1,messagingengine.com:s=fm3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[yuripv.net]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yuripv.net:+,messagingengine.com:+]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-3.48)[ip: (-9.81), ipnet: 66.111.4.0/24(-4.85), asn: 11403(-2.68), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[29.4.111.66.list.dnswl.org : 127.0.5.1]; RECEIVED_SPAMHAUS_PBL(0.00)[114.54.172.85.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 22:29:34 -0000 Rebecca Cran wrote: > On 2019-09-18 09:01, Yuri Pankov wrote: >> >> Any hints on debugging this further? > > Are you running ESXi 6.7 Update 2? Or, what version of ESXi are you > using that has the problem? Yes, exactly, sorry for not mentioning it. ESXi version: 6.7.0 ESXi build number: 13006603 From owner-freebsd-current@freebsd.org Wed Sep 18 22:56:47 2019 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 44B8DE9024 for ; Wed, 18 Sep 2019 22:56:47 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [IPv6:2400:7800:0:502e::23]) by mx1.freebsd.org (Postfix) with ESMTP id 46Yb2Q38cfz3NB1; Wed, 18 Sep 2019 22:56:45 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc12.plala.or.jp with ESMTP id <20190918225124.BQZW7266.msc12.plala.or.jp@localhost>; Thu, 19 Sep 2019 07:51:24 +0900 Date: Thu, 19 Sep 2019 07:50:38 +0900 (JST) Message-Id: <20190919.075038.1687549947501964479.ish@amail.plala.or.jp> To: zeising@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: hang up with r352239 and r352386 with i5-7500 From: Masachika ISHIZUKA In-Reply-To: <5fa15ee8-a1cb-37e7-b954-c50b1cd0a8d9@freebsd.org> References: <20190917.235930.528406816270492485.ish@amail.plala.or.jp> <20190918.171520.1850897233083712866.ish@amail.plala.or.jp> <5fa15ee8-a1cb-37e7-b954-c50b1cd0a8d9@freebsd.org> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac12; Thu, 19 Sep 2019 07:51:24 +0900 X-Rspamd-Queue-Id: 46Yb2Q38cfz3NB1 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.99 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.995,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Sep 2019 22:56:47 -0000 >>>>>>>> Can you please use absolute paths to i915kms.ko anyway, just to test? >> [snip] >> >> Now, drm-current-kmod is working fine on r352467 by your patch. >> > > Hi! > I just updated the port with the fix I suggested earlier, hopefully it > works. It will take some time before it shows up as packages, but > there is no problems building drm-current-kmod from ports even if > packages are used for the rest of the system. It is good working drm-current-kmod-4.16.g20190918 in port tree. Thank you very much. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Thu Sep 19 00:36:42 2019 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 9DE9BEB4B8 for ; Thu, 19 Sep 2019 00:36:42 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from muon.bsdio.com (muon.bluestop.org [65.103.231.193]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46YdFj4NqFz3xyj for ; Thu, 19 Sep 2019 00:36:41 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from muon.bsdio.com (localhost [127.0.0.1]) by muon.bsdio.com (Postfix) with ESMTP id E7FEA892FE; Wed, 18 Sep 2019 18:36:47 -0600 (MDT) Received: from muon.bsdio.com ([127.0.0.1]) by muon.bsdio.com (muon.bsdio.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id e0HQ2TtgRb8s; Wed, 18 Sep 2019 18:36:47 -0600 (MDT) Received: from photon.int.bluestop.org (unknown [10.0.10.150]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by muon.bsdio.com (Postfix) with ESMTPSA; Wed, 18 Sep 2019 18:36:47 -0600 (MDT) Subject: Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO To: Yuri Pankov , freebsd-current References: <2c2da4f1-052e-d8e7-a10e-079879975f92@bsdio.com> <58d44015-3b59-659b-607a-e056ad45607f@yuripv.net> From: Rebecca Cran Autocrypt: addr=rebecca@bsdio.com; keydata= mQINBFrUMZ4BEADI1yUEGeZeXeTCPay1ZpTBdDEpGPAw1dq2VCSTc1VhsnrEBa1iZxAfaeSv Uu5Ti7jlhQ/3sQMl0bJMKGB/RtmIW7k8h2w476oZmG8gChk8su5ZEx/pV1gdqInyFmmJKTYc gabJz8pL+m82w07qPv+oalepZ4dbj+HF++RAK/iEju+q9UHlsjj8e3mMNsvtrOz1K6bnpveO jZ+ms/2H3Hs5a4k8y6buwe2RvwhJQaXa13cR3LhzL+nwj4B9PHZZEa2WpEyYpw/bI0V9YSQN QgC1CYRzDyakZge6BCM6wHOgZSUzRPufGilrNKUwIVbRoIBR9/85+0wR+PlFUOUOfOc6ox7T dWcIx6PuPhek48rh4uwmmwsPtPiH4Z3T5p+GmWQ9NLFZKA1YnEdaSkWtYZsDxwVZZeYG2plt MfhXP0Hj4rf9Y3eoUenCaGioxAbUOBCtXdTGNAhNjz1g5NGDBVyhjKkzwJQvt9UrYTseERit 5dX2CMTy8hYLvSXd/Ivy+HylUS5IslfZxW5z9LgWX7Z97kILgkH3N0ewtLkygkG+Y+x7uaAV dFqp9ASOyzaiwKbJdeOI+WxRSh+AqeCR0S+bpkcLudLmbjrPmaFwjKycy1H85Z5R2J3YHyXY oT6OYjD8vLbUU2GWp6Onkcy1Pu8EMbRuzKil6HnpYg3BexbPFwARAQABtCNSZWJlY2NhIENy YW4gPHJlYmVjY2FAYmx1ZXN0b3Aub3JnPokCVwQTAQgAQQIbIwUJCWYBgAULCQgHAgYVCgkI CwIEFgIDAQIeAQIXgBYhBB+5fZtkTdO940Yr4g0CK1MRvhAgBQJa2B9zAhkBAAoJEA0CK1MR vhAgzJEQAJUqVmTRO9OqCSS2CVKjrqnEWJMvyo0K8B+WiXo0nSQg9+uyoVU7h2s/kkWVGy4u IWbGy2Qe8LiXzBJjHC3TadGvOvakfdMeKKXcgxgX6KlhA9hA2LW6tg22aHUk7Flr/8diHpgf qIwrXhqJXZmK72GR1QfhgoHsOsTJ9GWPswo1kUMc0cJowq0qP1RDdua6BwvDHHPJwu9OmC/i oQlMNm9gkBDq8H2B+m125ANwCnqBizXaiTTLQdewTMbCSuxbsni2icDqwBfFXzEgcJGaYYfB cQeFsfCmtXQK3JUd4Myx128Dxk9P3X64I93SB7QzB0nmWlyvmCFBNoCp0PCLA4qbwbw2sMRX Wx4BqYa8nI/jg+Nqo+Ut2BfltNZIlsHxK+XhxejfLqAjRCZeLnu1otvFnFuGLaAVYx9x1Y1q J8VizZxq6ujio62Qpultp6KNhlkJ+OKoGwA0k4NHh26SxvlsNxlfg/2v9b1LqWRzNujnwbcF 8g4902XjyBLxV+9YpXZEa8H6zzEHxpeDPWT3QfvrT8JuoHa1IyYnUKvG674UKW5zEGEwkQc9 cuQwR1RHd1ZrKtH1duXzaLr/caMp8ZDfGDDxFpenJTRxNRlg4+K7HSdhpac7sBVMUA8uVdE+ iuTThOmdf0c4DorL3BIh6Yv3FV4/NSqT1Wn3CG2fgG1guQINBFrUMZ4BEADkc4mvMcMcDF1t dNxNQuIBE1F243oZamG3LACCKfc1Yur3CPzHwIk5LXCUmbq23iE5bowxMWw3mlVT0p5xM0Wn UidIBwCKu4kRyy/fY4NyWWBuwy9srpTdmUcKRBRNB8zEZE8xIlidD1ijjgqLBfeM7n9ylawA xHLxwU96sdpdHFzb7Z0yKY2e/bzDaHiG0fUvcCmkgLf+uwKKZid1j8zR5PzKpgPqfy/PF01e KyGV3MNu8Y90xMoiEMWfCI2IB1m+hTuzZoboFvGV54SiMuvfWK/VMQjhsL6K2ddOqwVuy2nI MI4G3xDQW/v8KVyn43OSIAyW1eaklhzu0Ir2sO60PXRkvbTUrouvmSvpJfIQS49rU0M/X6FS DgXQLKrZ3my94+g8ptz9KoVml6s4OAwYVz+sb49nuSxipFKkU5FwhKOLmzbsBxCtytcUJoLm juJPJPDQue6YJiIXyc86GVY2pH3DjemKdbB4dSgqAJIp+lCzKSJzz7bgueh2Ox8vzx1tSxKj 7V8Nal+UTKKbkxPmMh+e20YZ4esAVifO3bS6IJP/aDnfagghB71vA7+aWGXPbjPlc2UHpCBi RSsl+IgoQXvdvZBsKRyfBx8neODa2C6JIE5vcaCjilSeKF8SzsFXvimnndhQNhAPU/DwQwSX dCl4gTsFVi5d8Oxq1sce+wARAQABiQI8BBgBCAAmFiEEH7l9m2RN073jRiviDQIrUxG+ECAF AlrUMZ4CGwwFCQlmAYAACgkQDQIrUxG+ECAWnRAAsmZX+KgNxW3v7R/76Tz4Wjmh4AGeE+Ji 3p5QsdTYny1B6vYBL9vCzPJ/AK8pgKMDRaweUP5eZQpfrdWC8Q7SNGgi4Q+97KEs+i2xZLQ+ WJb8a+WEEIc716u0y4ITiHfOgM5jWcFO4MXQATbJgv0drLLesa+LQCvZgPBqupt307EsCubQ s+Sxt+RVjf6rOUolp1GJXEQYwGsKklVd6yqLC8M1BSG53/WE5tSv5GzBZ8fp6EtmjT7leuid FtEvKYHQz4DqG9ELpHUF0X0UUCBK/MgXe3kCVLKE060UrJ4M6uPSx57rmVFA2MvwQR8M7GsW C5UsSM4PYwPWBhwxE7vcx0691YKAHT/5q8LxRVBdUyzPSprMhSQFttsBt+ygm6wRi3Pi3TuC EARNubPkQefyeC34yr40SAUCkOl3eWxSXPF4NfXFQb4AAzZSE5hv3qbDuwo3lrL0LqpIpEQP Az+JZ1QZ6mMFQ5/JD9Gukj54kZc0X8w3sQt0a8vyE/qrJg8vKgv2rCHrPc5MeDkEUEFiiJiC EDdkJtMyoRlU3S4NrnbyLOLEcHE8fGe3hStPX8hY62id2ecdQ5WZ7vLZW5SFeLarbUciuHIk VL6MHnUjbV7XlY50N7ebeFCIdlCWhdum2FJs/Ni+SSxbZC564vrokwlBBGSo6WTPQTa8IWx1 DtU= Message-ID: Date: Wed, 18 Sep 2019 18:36:38 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <58d44015-3b59-659b-607a-e056ad45607f@yuripv.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 46YdFj4NqFz3xyj X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of rebecca@bsdio.com has no SPF policy when checking 65.103.231.193) smtp.mailfrom=rebecca@bsdio.com X-Spamd-Result: default: False [-3.89 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[bsdio.com]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:209, ipnet:65.100.0.0/14, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.80)[ip: (-9.00), ipnet: 65.100.0.0/14(-4.86), asn: 209(-0.06), country: US(-0.05)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 00:36:42 -0000 On 2019-09-18 16:29, Yuri Pankov wrote: > > Yes, exactly, sorry for not mentioning it. > > ESXi version: 6.7.0 > ESXi build number: 13006603 Thanks. I've been able to replicate the problem, and am currently debugging it. So far, it looks to be a problem with the GetMemoryMap/ExitBootServices loop in bi_load_efi_data. -- Rebecca Cran From owner-freebsd-current@freebsd.org Thu Sep 19 01:39:25 2019 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 03A79EE250 for ; Thu, 19 Sep 2019 01:39:25 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from muon.bsdio.com (muon.bluestop.org [65.103.231.193]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46Yff41kWKz43Hh for ; Thu, 19 Sep 2019 01:39:23 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from muon.bsdio.com (localhost [127.0.0.1]) by muon.bsdio.com (Postfix) with ESMTP id 9E9B7894E6; Wed, 18 Sep 2019 19:39:30 -0600 (MDT) Received: from muon.bsdio.com ([127.0.0.1]) by muon.bsdio.com (muon.bsdio.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id DmmaXBtepro1; Wed, 18 Sep 2019 19:39:30 -0600 (MDT) Received: from photon.int.bluestop.org (unknown [10.0.10.150]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits)) (No client certificate requested) by muon.bsdio.com (Postfix) with ESMTPSA; Wed, 18 Sep 2019 19:39:30 -0600 (MDT) Subject: Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO From: Rebecca Cran To: Yuri Pankov , freebsd-current References: <2c2da4f1-052e-d8e7-a10e-079879975f92@bsdio.com> <58d44015-3b59-659b-607a-e056ad45607f@yuripv.net> Autocrypt: addr=rebecca@bsdio.com; keydata= mQINBFrUMZ4BEADI1yUEGeZeXeTCPay1ZpTBdDEpGPAw1dq2VCSTc1VhsnrEBa1iZxAfaeSv Uu5Ti7jlhQ/3sQMl0bJMKGB/RtmIW7k8h2w476oZmG8gChk8su5ZEx/pV1gdqInyFmmJKTYc gabJz8pL+m82w07qPv+oalepZ4dbj+HF++RAK/iEju+q9UHlsjj8e3mMNsvtrOz1K6bnpveO jZ+ms/2H3Hs5a4k8y6buwe2RvwhJQaXa13cR3LhzL+nwj4B9PHZZEa2WpEyYpw/bI0V9YSQN QgC1CYRzDyakZge6BCM6wHOgZSUzRPufGilrNKUwIVbRoIBR9/85+0wR+PlFUOUOfOc6ox7T dWcIx6PuPhek48rh4uwmmwsPtPiH4Z3T5p+GmWQ9NLFZKA1YnEdaSkWtYZsDxwVZZeYG2plt MfhXP0Hj4rf9Y3eoUenCaGioxAbUOBCtXdTGNAhNjz1g5NGDBVyhjKkzwJQvt9UrYTseERit 5dX2CMTy8hYLvSXd/Ivy+HylUS5IslfZxW5z9LgWX7Z97kILgkH3N0ewtLkygkG+Y+x7uaAV dFqp9ASOyzaiwKbJdeOI+WxRSh+AqeCR0S+bpkcLudLmbjrPmaFwjKycy1H85Z5R2J3YHyXY oT6OYjD8vLbUU2GWp6Onkcy1Pu8EMbRuzKil6HnpYg3BexbPFwARAQABtCNSZWJlY2NhIENy YW4gPHJlYmVjY2FAYmx1ZXN0b3Aub3JnPokCVwQTAQgAQQIbIwUJCWYBgAULCQgHAgYVCgkI CwIEFgIDAQIeAQIXgBYhBB+5fZtkTdO940Yr4g0CK1MRvhAgBQJa2B9zAhkBAAoJEA0CK1MR vhAgzJEQAJUqVmTRO9OqCSS2CVKjrqnEWJMvyo0K8B+WiXo0nSQg9+uyoVU7h2s/kkWVGy4u IWbGy2Qe8LiXzBJjHC3TadGvOvakfdMeKKXcgxgX6KlhA9hA2LW6tg22aHUk7Flr/8diHpgf qIwrXhqJXZmK72GR1QfhgoHsOsTJ9GWPswo1kUMc0cJowq0qP1RDdua6BwvDHHPJwu9OmC/i oQlMNm9gkBDq8H2B+m125ANwCnqBizXaiTTLQdewTMbCSuxbsni2icDqwBfFXzEgcJGaYYfB cQeFsfCmtXQK3JUd4Myx128Dxk9P3X64I93SB7QzB0nmWlyvmCFBNoCp0PCLA4qbwbw2sMRX Wx4BqYa8nI/jg+Nqo+Ut2BfltNZIlsHxK+XhxejfLqAjRCZeLnu1otvFnFuGLaAVYx9x1Y1q J8VizZxq6ujio62Qpultp6KNhlkJ+OKoGwA0k4NHh26SxvlsNxlfg/2v9b1LqWRzNujnwbcF 8g4902XjyBLxV+9YpXZEa8H6zzEHxpeDPWT3QfvrT8JuoHa1IyYnUKvG674UKW5zEGEwkQc9 cuQwR1RHd1ZrKtH1duXzaLr/caMp8ZDfGDDxFpenJTRxNRlg4+K7HSdhpac7sBVMUA8uVdE+ iuTThOmdf0c4DorL3BIh6Yv3FV4/NSqT1Wn3CG2fgG1guQINBFrUMZ4BEADkc4mvMcMcDF1t dNxNQuIBE1F243oZamG3LACCKfc1Yur3CPzHwIk5LXCUmbq23iE5bowxMWw3mlVT0p5xM0Wn UidIBwCKu4kRyy/fY4NyWWBuwy9srpTdmUcKRBRNB8zEZE8xIlidD1ijjgqLBfeM7n9ylawA xHLxwU96sdpdHFzb7Z0yKY2e/bzDaHiG0fUvcCmkgLf+uwKKZid1j8zR5PzKpgPqfy/PF01e KyGV3MNu8Y90xMoiEMWfCI2IB1m+hTuzZoboFvGV54SiMuvfWK/VMQjhsL6K2ddOqwVuy2nI MI4G3xDQW/v8KVyn43OSIAyW1eaklhzu0Ir2sO60PXRkvbTUrouvmSvpJfIQS49rU0M/X6FS DgXQLKrZ3my94+g8ptz9KoVml6s4OAwYVz+sb49nuSxipFKkU5FwhKOLmzbsBxCtytcUJoLm juJPJPDQue6YJiIXyc86GVY2pH3DjemKdbB4dSgqAJIp+lCzKSJzz7bgueh2Ox8vzx1tSxKj 7V8Nal+UTKKbkxPmMh+e20YZ4esAVifO3bS6IJP/aDnfagghB71vA7+aWGXPbjPlc2UHpCBi RSsl+IgoQXvdvZBsKRyfBx8neODa2C6JIE5vcaCjilSeKF8SzsFXvimnndhQNhAPU/DwQwSX dCl4gTsFVi5d8Oxq1sce+wARAQABiQI8BBgBCAAmFiEEH7l9m2RN073jRiviDQIrUxG+ECAF AlrUMZ4CGwwFCQlmAYAACgkQDQIrUxG+ECAWnRAAsmZX+KgNxW3v7R/76Tz4Wjmh4AGeE+Ji 3p5QsdTYny1B6vYBL9vCzPJ/AK8pgKMDRaweUP5eZQpfrdWC8Q7SNGgi4Q+97KEs+i2xZLQ+ WJb8a+WEEIc716u0y4ITiHfOgM5jWcFO4MXQATbJgv0drLLesa+LQCvZgPBqupt307EsCubQ s+Sxt+RVjf6rOUolp1GJXEQYwGsKklVd6yqLC8M1BSG53/WE5tSv5GzBZ8fp6EtmjT7leuid FtEvKYHQz4DqG9ELpHUF0X0UUCBK/MgXe3kCVLKE060UrJ4M6uPSx57rmVFA2MvwQR8M7GsW C5UsSM4PYwPWBhwxE7vcx0691YKAHT/5q8LxRVBdUyzPSprMhSQFttsBt+ygm6wRi3Pi3TuC EARNubPkQefyeC34yr40SAUCkOl3eWxSXPF4NfXFQb4AAzZSE5hv3qbDuwo3lrL0LqpIpEQP Az+JZ1QZ6mMFQ5/JD9Gukj54kZc0X8w3sQt0a8vyE/qrJg8vKgv2rCHrPc5MeDkEUEFiiJiC EDdkJtMyoRlU3S4NrnbyLOLEcHE8fGe3hStPX8hY62id2ecdQ5WZ7vLZW5SFeLarbUciuHIk VL6MHnUjbV7XlY50N7ebeFCIdlCWhdum2FJs/Ni+SSxbZC564vrokwlBBGSo6WTPQTa8IWx1 DtU= Message-ID: Date: Wed, 18 Sep 2019 19:39:21 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 46Yff41kWKz43Hh X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of rebecca@bsdio.com has no SPF policy when checking 65.103.231.193) smtp.mailfrom=rebecca@bsdio.com X-Spamd-Result: default: False [-3.88 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[bsdio.com]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:209, ipnet:65.100.0.0/14, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.79)[ip: (-8.96), ipnet: 65.100.0.0/14(-4.85), asn: 209(-0.06), country: US(-0.05)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 01:39:25 -0000 On 2019-09-18 18:36, Rebecca Cran wrote: > > So far, it looks to be a problem with the GetMemoryMap/ExitBootServices > loop in bi_load_efi_data. So, it's crashing when we call BS->ExitBootServices. Of course, the problem isn't really _in_ that code (it hasn't changed since March), but that's just where it ends up crashing. I'll look through the rest of the loader and see if I can spot any problems. -- Rebecca Cran From owner-freebsd-current@freebsd.org Thu Sep 19 10:59:56 2019 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 A9D75FE3D7 for ; Thu, 19 Sep 2019 10:59:56 +0000 (UTC) (envelope-from mms.vanbreukelingen@gmail.com) Received: from mail-pl1-x642.google.com (mail-pl1-x642.google.com [IPv6:2607:f8b0:4864:20::642]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Yv4q1qf4z4Ydw for ; Thu, 19 Sep 2019 10:59:55 +0000 (UTC) (envelope-from mms.vanbreukelingen@gmail.com) Received: by mail-pl1-x642.google.com with SMTP id u12so1409752pls.12 for ; Thu, 19 Sep 2019 03:59:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:organization:mime-version :content-transfer-encoding; bh=aFgEf33wD1IPJAGAL49Wfnpz5nJQspBnLkn7F/VQbTQ=; b=Nx4M173jmXLnqpa8r0hlqNuqIfe+8X5sQNOgBHl5LzV8rR3FVHYlZfN/GB+3vDsFKw MovWpu4B1atM/P+kVsAAwBFgCnvTsyVIBCDNoymv4ezRVBvmGVZ/F+rw85wTqNNDMNt5 SmUIyizSVE9u85YAF41cwJrdfbF2iTpLpsfj4J6Ev62cs82BEYVAT8jNt00Wj8Xj/4ME uQ6BmiIBr0tNLiuDdeI0sUGwttInpECgfdxN3tc9/dI6KWQgOfSmw9G0ax8fVBkpnaq7 ELpOfmD77sRmhkaiaHg7jTvXSRYnrL4KaDXvoh5roPmghfJNaNEKU8+7BXXa6O5HCBvp 1Jlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:organization :mime-version:content-transfer-encoding; bh=aFgEf33wD1IPJAGAL49Wfnpz5nJQspBnLkn7F/VQbTQ=; b=OSGayN0LE0Y/j8NRARX4FqVNpcfB770IuxjnhcHgWDhCGNsyA7s2F9dr3ml/i2Wbb9 BsSb/tj9TDKwigSq4VhJiclwiiUstFEYCT7uFPSCxdTdwhEG16wol/CBp/nnn7RE5RxF +amy5FWnOObqfv4D4MwdkpRpFPUyBZvj4zVNok6rMuRh5kx7Ok0xtkBAwLCr6MoPhVTq r+3oQEvas92fKngGSE4FXxnLWLtsYUt7kVqrpSne33HxZixfhbhBzmLK7/9onMWLJoKh UJVnoZLFDWL2BktWPyUsyefp6bTfik5c1JiFEbScFHCSDoehJwpZmpulhYkPWJZj3yl9 u3Xw== X-Gm-Message-State: APjAAAXnCksTpgivMNDxO607YlnPEZRxAE+bohMZiuZcK1kwMTwOkFhc kKXC389lL/24TD49SVTnOGT8bA5KY3Y= X-Google-Smtp-Source: APXvYqyMi4PDE2RLxe4BC21YvIyMEznP0vCFspjZo4Nn5seewsEbmiKDBjs48/l508kKPGu448IuPQ== X-Received: by 2002:a17:902:820f:: with SMTP id x15mr9653334pln.130.1568890432432; Thu, 19 Sep 2019 03:53:52 -0700 (PDT) Received: from archlaptop.localnet ([221.125.108.128]) by smtp.gmail.com with ESMTPSA id e4sm506131pff.22.2019.09.19.03.53.50 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 19 Sep 2019 03:53:51 -0700 (PDT) From: mms.vanbreukelingen@gmail.com To: "FreeBSD Current freebsd-x11@greebsd.org" Subject: Another X server start failure Date: Thu, 19 Sep 2019 12:53:44 +0200 Message-ID: <20919778.WRJvlOerET@archlaptop> Organization: Vanbreukelingen, Ltd. X-Face: ,JUImV31kt3a,Ku@0&alEp98=v~qV`I6q#(@6QCGD6I$a&N; @qQ; p+AJM8HY@$EUh} Zs8X'IBu-b~Ahuv620rfHU.(|ln3[SM?d3j+bPfp; QzDKOWSq@hux2Fg=P[n}Fa8p MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 46Yv4q1qf4z4Ydw X-Spamd-Bar: ++++++ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Nx4M173j; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mmsvanbreukelingen@gmail.com designates 2607:f8b0:4864:20::642 as permitted sender) smtp.mailfrom=mmsvanbreukelingen@gmail.com X-Spamd-Result: default: False [6.81 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(0.00)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(0.00)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; CTE_CASE(0.50)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; RECEIVED_SPAMHAUS_XBL(5.00)[128.108.125.221.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.4]; R_DKIM_ALLOW(0.00)[gmail.com:s=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[128.108.125.221.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; IP_SCORE(0.00)[ip: (-0.33), ipnet: 2607:f8b0::/32(-2.68), asn: 15169(-2.23), country: US(-0.05)]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_SPAM_MEDIUM(0.41)[0.411,0]; RCPT_COUNT_ONE(0.00)[1]; BAD_REP_POLICIES(0.10)[]; IP_SCORE_FREEMAIL(0.00)[]; NEURAL_SPAM_LONG(0.39)[0.395,0]; RCVD_IN_DNSWL_NONE(0.00)[2.4.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; FROM_NO_DN(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_TLS_ALL(0.00)[]; GREYLIST(0.00)[pass,body] X-Spam: Yes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 10:59:56 -0000 Having a Raden 240 (sometimes 250) and an older AMDGPU. The older card is deactivated in BIOS but it is been found by the X -configure problem. X server did start one time with -config /root/xorg.conf.new, copied to /etc/X11/ xorg.conf, never got back any "blank black grafic" screen. Rebuilt new world and the kern with WITNESS option on and option LOCK_PROFILING. Using llvm- devel is useless in that case, if it doesn't with the 8.0.X. Can't enter framebuffer mode, tells /var/log/x11_*.log, no VESA, no xfcb. sddm tells: xauth: bad add command line, bad delete command line, bad add commandline. It used to work with even X -configure fatal error and sddm, so what to xrite in xauth; normally sddm autoconfigs. I guess it's the recognization from both cards, what is the option to really and finally deactivate this on-board card on an ASUS PRIME 350 board (I just mean NOT to cut the part of the board where grafics situatiated with a laser- cutter :-) )? This one has never been used as it been too old for good 3D- Gaming what has been a topic a year ago - not for me, but for a user. What's the state of art for 3D-virutal-glasses and gloves? I guess the same as with the AI! I guess freeBSD has other functions to do than beeing a desktop OS! Thx for help in advance, Yours, Miranda From owner-freebsd-current@freebsd.org Thu Sep 19 12:30:33 2019 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 E1A15121C7F for ; Thu, 19 Sep 2019 12:30:33 +0000 (UTC) (envelope-from thj@freebsd.org) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (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 46Yx5P4n7Kz4fN0; Thu, 19 Sep 2019 12:30:33 +0000 (UTC) (envelope-from thj@freebsd.org) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id DFE10823; Thu, 19 Sep 2019 08:30:31 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 19 Sep 2019 08:30:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=kIjXZ8 +z+CEEOdaRI1IOgIPAlr2rN9nV86c6977xdjY=; b=lDQkakjPymrlhDz+7xXnxm 8/XpFNkcr8zm5O2RVISr+Oej7g78/01qa90u/gebf5AJy6AZlahZ/emIehZiI5nS nluMoc7qGfiQz0IpykHTbKOk7DbvwDSG4RC+bPWZHOLH4q/TJ92DEiFpYl/XiMNX 6NaQJgXCJeL0YXZTXdpbt+o6X37Z2KqRC1Ms9E+mPzFQCIqPU0YQkq1h2X02OHP3 PYUyrI5RfxLYxVNxM7fGwV9Vmkp4Nk4OePWYaX2b8hirb4Vg1lMcS6bHPIAcHklr z4N9lgdaaMRjac0JTBb7thBPy3LOcEE7Lrkzn38TOUufDvU+HzFyGKlE3tQLsjTg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvddtgdehhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefvohhmucfl ohhnvghsuceothhhjhesfhhrvggvsghsugdrohhrgheqnecukfhppedufeejrdehtddrud ejrdduvdenucfrrghrrghmpehmrghilhhfrhhomhepthhhjhesfhhrvggvsghsugdrohhr ghenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from tom-desk.erg.abdn.ac.uk (tom-desk.erg.abdn.ac.uk [137.50.17.12]) by mail.messagingengine.com (Postfix) with ESMTPA id 8B61480069; Thu, 19 Sep 2019 08:30:30 -0400 (EDT) Date: Thu, 19 Sep 2019 13:28:04 +0100 From: Tom Jones To: Poul-Henning Kamp Cc: Johannes Lundberg , FreeBSD Current Subject: Re: wlan can't discover known networks after relocating Message-ID: <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> <6985.1568738188@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6985.1568738188@critter.freebsd.dk> User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: 46Yx5P4n7Kz4fN0 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-2.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 12:30:33 -0000 On Tue, Sep 17, 2019 at 04:36:28PM +0000, Poul-Henning Kamp wrote: > -------- > In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org>, Johannes Lundber > g writes: > > >For a long time now I have had this problem with iwm and wlan0. Whenever > >I move between work and home it won't reconnect automatically and I have > >to do wlan0 scan manually for it to pick up the different network. > > I suffer from the dreaded "reason=0" when I move inside my house: > > > scan > OK > <3>CTRL-EVENT-SCAN-RESULTS > <3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID='Palombia' freq=2452 MHz) > <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0 > <3>CTRL-EVENT-SCAN-RESULTS > <3>Trying to associate with 6c:3b:6b:ab:ce:d4 (SSID='Palombia' freq=2412 MHz) > <3>Associated with 6c:3b:6b:ab:ce:d4 > > a2:e9 is the loudest AP here in my office, but my I have been in the > other end of the house iwn consistently fails to associate with it and > and keeps picking the weaker AP in the far end. > > Eventually (hours!) it disconnects from the weaker ap, also with > "reason=0" and gets it right: > > <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 [GTK=CCMP] > <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0 > <3>CTRL-EVENT-SCAN-RESULTS > <3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID='Palombia' freq=2452 MHz) > <3>Associated with 6c:3b:6b:3d:a2:e9 > <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 [PTK=CCMP GTK=CCMP] > <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 completed [id=3 id_str=] > <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 [GTK=CCMP] > > And yes, working roaming would be nice too... I have the problem that when roaming networks become disabled $ wpa_cli Selected interface 'wlan0' Interactive mode > list_networks network id / ssid / bssid / flags 0 network1 any [CURRENT] 1 network2 any [DISABLED] 2 network3 any [DISABLED] 3 network4 any [DISABLED] 4 network5 any [DISABLED] Selected interface 'wlan0' I address this by doing network_enable x in wpa_cli and it all comes back. I asked Adrian about this in the past, but it needs some debugging to pin down. - [tj] From owner-freebsd-current@freebsd.org Thu Sep 19 12:44:17 2019 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 C01B7122294; Thu, 19 Sep 2019 12:44:17 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46YxPD6Pybz3C1Q; Thu, 19 Sep 2019 12:44:16 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 166E88D4A157; Thu, 19 Sep 2019 12:38:41 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 81EC7C24B96; Thu, 19 Sep 2019 12:38:40 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id BzdmCNNerqUF; Thu, 19 Sep 2019 12:38:38 +0000 (UTC) Received: from [192.168.2.110] (unknown [IPv6:fde9:577b:c1a9:31:5caf:95d2:ddd1:d63e]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id D95E3C24A04; Thu, 19 Sep 2019 12:38:37 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Tom Jones" , freebsd-wireless@freebsd.org Cc: "Poul-Henning Kamp" , "Johannes Lundberg" , "FreeBSD Current" Subject: Re: wlan can't discover known networks after relocating Date: Thu, 19 Sep 2019 12:38:36 +0000 Reply-To: freebsd-wireless@freebsd.org X-Mailer: MailMate (2.0BETAr6137) Message-ID: In-Reply-To: <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> <6985.1568738188@critter.freebsd.dk> <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: 46YxPD6Pybz3C1Q X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 2a01:4f8:13b:39f::9f:25 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net X-Spamd-Result: default: False [-4.73 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; HAS_REPLYTO(0.00)[freebsd-wireless@freebsd.org]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a01:4f8:13b:39f::9f:25]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[zabbadoz.net]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-2.43)[ip: (-8.33), ipnet: 2a01:4f8::/29(-2.02), asn: 24940(-1.79), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 12:44:17 -0000 On 19 Sep 2019, at 12:28, Tom Jones wrote: Hi, freebsd-wireless might be a better list for all this .. > On Tue, Sep 17, 2019 at 04:36:28PM +0000, Poul-Henning Kamp wrote: >> -------- >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org>, >> Johannes Lundber >> g writes: >> >>> For a long time now I have had this problem with iwm and wlan0. >>> Whenever >>> I move between work and home it won't reconnect automatically and I >>> have >>> to do wlan0 scan manually for it to pick up the different network. >> >> I suffer from the dreaded "reason=0" when I move inside my house: >> >> > scan >> OK >> <3>CTRL-EVENT-SCAN-RESULTS >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID='Palombia' >> freq=2452 MHz) >> <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0 >> <3>CTRL-EVENT-SCAN-RESULTS >> <3>Trying to associate with 6c:3b:6b:ab:ce:d4 (SSID='Palombia' >> freq=2412 MHz) >> <3>Associated with 6c:3b:6b:ab:ce:d4 >> >> a2:e9 is the loudest AP here in my office, but my I have been in the >> other end of the house iwn consistently fails to associate with it >> and >> and keeps picking the weaker AP in the far end. >> >> Eventually (hours!) it disconnects from the weaker ap, also with >> "reason=0" and gets it right: >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 [GTK=CCMP] >> <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0 >> <3>CTRL-EVENT-SCAN-RESULTS >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID='Palombia' >> freq=2452 MHz) >> <3>Associated with 6c:3b:6b:3d:a2:e9 >> <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 [PTK=CCMP >> GTK=CCMP] >> <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 completed >> [id=3 id_str=] >> <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 [GTK=CCMP] >> >> And yes, working roaming would be nice too... > > I have the problem that when roaming networks become disabled > > $ wpa_cli > Selected interface 'wlan0' > > Interactive mode > > > list_networks > network id / ssid / bssid / flags > 0 network1 any [CURRENT] > 1 network2 any [DISABLED] > 2 network3 any [DISABLED] > 3 network4 any [DISABLED] > 4 network5 any [DISABLED] > Selected interface 'wlan0' > > > I address this by doing network_enable x in wpa_cli and it all comes > back. I asked Adrian about this in the past, but it needs some > debugging > to pin down. Is this iwm(4) as well in your case or another card? /bz From owner-freebsd-current@freebsd.org Thu Sep 19 14:02:31 2019 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 3DFB412440D for ; Thu, 19 Sep 2019 14:02:31 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46Yz7V189Rz3HN0 for ; Thu, 19 Sep 2019 14:02:29 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.92.2 (FreeBSD)) (envelope-from ) id 1iAx0l-000Enm-Gb; Thu, 19 Sep 2019 16:02:19 +0200 Date: Thu, 19 Sep 2019 16:02:19 +0200 From: Kurt Jaeger To: freebsd-current@freebsd.org Subject: Lockdown adaX numbers to allow booting ? Message-ID: <20190919140219.GE2863@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 46Yz7V189Rz3HN0 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of lists@opsec.eu designates 2001:14f8:200::1 as permitted sender) smtp.mailfrom=lists@opsec.eu X-Spamd-Result: default: False [-4.85 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[opsec.eu]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-3.55)[ip: (-9.31), ipnet: 2001:14f8::/32(-4.69), asn: 12502(-3.75), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 14:02:31 -0000 Hi! We have a system with 10 SATA disks. 2 disks are for the system, 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: bck 72.8T 38.7T 34.1T - - 1% 53% 1.00x ONLINE - The problem is that if all 10 disks are connected, the system looses track from where it should boot and fails to boot (serial boot log): -------------------- /boot/config: -Dh -S115200 Consoles: internal video/keyboard serial port BTX loader 1.00 BTX version is 1.02 Consoles: internal video/keyboard serial port BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS drive E: is disk2 BIOS drive F: is disk3 BIOS drive G: is disk4 BIOS drive H: is disk5 BIOS drive I: is disk6 BIOS drive J: is disk7 BIOS drive K: is disk8 BIOS drive L: is disk9 // / -------------------- The system disks are detected as ada4 and ada5, when all disks are plugged in. The solution right now is this to unplug all disks of the 'bck' pool, reboot, and re-insert the data disks after the boot is finished. I looked into the output to kenv(1), but did not find inspiration on how to fix this. Now my questions: - Shuffeling around SATA cables seems the wrong approach to fix this. - Can we somehow lock down the disk numbering so that the system disks are detected as ada0 and ada1 ? - Would rootdev="disk4s1a" in /boot/loader.conf work or is that the wrong approach ? - How could we configure two drivers as root devices in loader.conf ? -- pi@opsec.eu +49 171 3101372 One year to go ! From owner-freebsd-current@freebsd.org Thu Sep 19 15:18:44 2019 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 AD1C1126160 for ; Thu, 19 Sep 2019 15:18:44 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-zteg10021301.me.com (pv50p00im-zteg10021301.me.com [17.58.6.46]) (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 46Z0qQ6zttz3N26 for ; Thu, 19 Sep 2019 15:18:42 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-zteg10021301.me.com (Postfix) with ESMTPSA id 33D00580F53; Thu, 19 Sep 2019 15:18:40 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Lockdown adaX numbers to allow booting ? From: Toomas Soome In-Reply-To: <20190919140219.GE2863@home.opsec.eu> Date: Thu, 19 Sep 2019 18:18:37 +0300 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> References: <20190919140219.GE2863@home.opsec.eu> To: Kurt Jaeger X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-19_05:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909190143 X-Rspamd-Queue-Id: 46Z0qQ6zttz3N26 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.20 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCVD_IN_DNSWL_MED(-0.20)[46.6.58.17.list.dnswl.org : 127.0.5.2]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (-5.25), ipnet: 17.58.0.0/20(-3.39), asn: 714(-2.92), country: US(-0.05)]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 15:18:44 -0000 > On 19 Sep 2019, at 17:02, Kurt Jaeger wrote: >=20 > Hi! >=20 > We have a system with 10 SATA disks. 2 disks are for the system, > 8 disks drive a data pool 'bck', configured as raidz2, for backup = purposes: >=20 > bck 72.8T 38.7T 34.1T - - 1% 53% 1.00x = ONLINE - >=20 > The problem is that if all 10 disks are connected, the system > looses track from where it should boot and fails to boot (serial boot = log): >=20 > -------------------- > /boot/config: -Dh -S115200 >=20 > Consoles: internal video/keyboard serial port > BTX loader 1.00 BTX version is 1.02 > Consoles: internal video/keyboard serial port > BIOS drive C: is disk0 > BIOS drive D: is disk1 > BIOS drive E: is disk2 > BIOS drive F: is disk3 > BIOS drive G: is disk4 > BIOS drive H: is disk5 > BIOS drive I: is disk6 > BIOS drive J: is disk7 > BIOS drive K: is disk8 > BIOS drive L: is disk9 > // > / > -------------------- >=20 > The system disks are detected as ada4 and ada5, when all disks are > plugged in. >=20 > The solution right now is this to unplug all disks of the 'bck' pool, > reboot, and re-insert the data disks after the boot is finished. >=20 > I looked into the output to kenv(1), but did not find inspiration > on how to fix this. >=20 > Now my questions: >=20 > - Shuffeling around SATA cables seems the wrong approach to fix this. > - Can we somehow lock down the disk numbering so that the system disks > are detected as ada0 and ada1 ? Why this order does change? One would expect disks 0 and 1 to be OS = disks and the rest for data=E2=80=A6 Also the question is, what you mean with =E2=80=9Csystem looses = track=E2=80=9D? disk4 becomes adaX? why it matters, are you using ufs on = boot disks? rgds, toomas > - Would > rootdev=3D"disk4s1a" > in /boot/loader.conf work or is that the wrong approach ? > - How could we configure two drivers as root devices in loader.conf ? >=20 > --=20 > pi@opsec.eu +49 171 3101372 One year to = go ! > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Thu Sep 19 15:20:22 2019 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 B0AB012638B; Thu, 19 Sep 2019 15:20:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yw1-xc2c.google.com (mail-yw1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Z0sL4FGCz3NF7; Thu, 19 Sep 2019 15:20:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-yw1-xc2c.google.com with SMTP id i207so1349750ywc.9; Thu, 19 Sep 2019 08:20:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=b4Gg2r8nIvlJweC8jmNIDMlju1VzEbEn1U1gMInOowY=; b=MHiaH1jueYI65apHvR5Y3VcM+lMfulIN9S0zRZMzY0B2kGhM/+W5IdpBrZZjH5Pghz zzGJ66/7m5XG+ZyFnfQU1ocS8mF6z8ots0XRUQBuA0Crla0wRWJ9RfDA7gqfQpGf1CVx axDHoGISj2gYKzQ4oqdsPTr/9SX2ain3Lv7a5TOrF9rSvQjsZebWR6cAD+aUp+Kv/M/d 2jiLXLj/7IFhFl2b3J6n45s0y7gQJWXXI0rU2EQB1QT5uO5hRPb5dK2J+Y2fuhQlGSgk kJ1A2THhI6Pk9CO2RIajh7pRKrbrqUpdnnAaBgafvRSc3/x6uaMHpMTe9eXHSQy1wb8u dg2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=b4Gg2r8nIvlJweC8jmNIDMlju1VzEbEn1U1gMInOowY=; b=AMZQMcRtWY1KQOjBs4SsPECAd2Y9KHHh6qZUcr+APJDcSILKj2P3udCStcyvvlL/eX J9f2wcFQBG1aoxIcFfP6P8+j7jT12exqgGiDr7EkPXQULc6qO+7SHYb9+gwLKt9stMYx cldT/pwxPXiIycfDDQAqoXHRS8Gk70wIYi1gYTbrBXP3NNjvK45ukJq+C3bPP1Xgn4jy RjdsnVjzHZ0nUSYYUa7TGYGtH0ftU70E1Zu713+IWy4/SmnPlUAJyMZ2RgLFp8/c7piL 31PZEAyGlfDRPQyIPzdoC+JsGS9n7wjDCFKGse+rCZaSXnWwAPqhleNqKktbXN40z5IS JXTA== X-Gm-Message-State: APjAAAWWE8wTa0nE5OIzeczAtFxF6vOEXDLz5OeyrZ4iaZBV/xcYhZwu nCYp6sSfbquZr3pJEx8iuhKLYTl5mcn3SJMo1NXimA== X-Google-Smtp-Source: APXvYqzkAx1sSlJDFUzQ3oxX7S7uXnrjfXzMPmtdJ9TQScrAywP8ILBY63F9BzLd9oj7n9qKKMDV/K93NYDV2hXvifE= X-Received: by 2002:a81:4fc4:: with SMTP id d187mr8667157ywb.386.1568906419456; Thu, 19 Sep 2019 08:20:19 -0700 (PDT) MIME-Version: 1.0 References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> <6985.1568738188@critter.freebsd.dk> <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> In-Reply-To: From: Adrian Chadd Date: Thu, 19 Sep 2019 08:20:07 -0700 Message-ID: Subject: Re: wlan can't discover known networks after relocating To: "freebsd-wireless@freebsd.org" Cc: Tom Jones , Poul-Henning Kamp , FreeBSD Current , Johannes Lundberg X-Rspamd-Queue-Id: 46Z0sL4FGCz3NF7 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 15:20:22 -0000 Roaming is done in wpa_supplicant when it's running.That's where the smarts need to be. :( -adrian On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb wrote: > On 19 Sep 2019, at 12:28, Tom Jones wrote: > > Hi, > > freebsd-wireless might be a better list for all this .. > > > > On Tue, Sep 17, 2019 at 04:36:28PM +0000, Poul-Henning Kamp wrote: > >> -------- > >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org>, > >> Johannes Lundber > >> g writes: > >> > >>> For a long time now I have had this problem with iwm and wlan0. > >>> Whenever > >>> I move between work and home it won't reconnect automatically and I > >>> have > >>> to do wlan0 scan manually for it to pick up the different network. > >> > >> I suffer from the dreaded "reason=0" when I move inside my house: > >> > >> > scan > >> OK > >> <3>CTRL-EVENT-SCAN-RESULTS > >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID='Palombia' > >> freq=2452 MHz) > >> <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0 > >> <3>CTRL-EVENT-SCAN-RESULTS > >> <3>Trying to associate with 6c:3b:6b:ab:ce:d4 (SSID='Palombia' > >> freq=2412 MHz) > >> <3>Associated with 6c:3b:6b:ab:ce:d4 > >> > >> a2:e9 is the loudest AP here in my office, but my I have been in the > >> other end of the house iwn consistently fails to associate with it > >> and > >> and keeps picking the weaker AP in the far end. > >> > >> Eventually (hours!) it disconnects from the weaker ap, also with > >> "reason=0" and gets it right: > >> > >> <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 [GTK=CCMP] > >> <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0 > >> <3>CTRL-EVENT-SCAN-RESULTS > >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID='Palombia' > >> freq=2452 MHz) > >> <3>Associated with 6c:3b:6b:3d:a2:e9 > >> <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 [PTK=CCMP > >> GTK=CCMP] > >> <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 > completed > >> [id=3 id_str=] > >> <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 [GTK=CCMP] > >> > >> And yes, working roaming would be nice too... > > > > I have the problem that when roaming networks become disabled > > > > $ wpa_cli > > Selected interface 'wlan0' > > > > Interactive mode > > > > > list_networks > > network id / ssid / bssid / flags > > 0 network1 any [CURRENT] > > 1 network2 any [DISABLED] > > 2 network3 any [DISABLED] > > 3 network4 any [DISABLED] > > 4 network5 any [DISABLED] > > Selected interface 'wlan0' > > > > > > I address this by doing network_enable x in wpa_cli and it all comes > > back. I asked Adrian about this in the past, but it needs some > > debugging > > to pin down. > > > Is this iwm(4) as well in your case or another card? > > /bz > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org > " > From owner-freebsd-current@freebsd.org Thu Sep 19 15:57:18 2019 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 7F14D127157 for ; Thu, 19 Sep 2019 15:57:18 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z1gx40ytz3QDH for ; Thu, 19 Sep 2019 15:57:17 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.92.2 (FreeBSD)) (envelope-from ) id 1iAynx-000FEh-68; Thu, 19 Sep 2019 17:57:13 +0200 Date: Thu, 19 Sep 2019 17:57:13 +0200 From: Kurt Jaeger To: Toomas Soome Cc: freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190919155713.GG2863@home.opsec.eu> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> X-Rspamd-Queue-Id: 46Z1gx40ytz3QDH X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of lists@opsec.eu designates 2001:14f8:200::1 as permitted sender) smtp.mailfrom=lists@opsec.eu X-Spamd-Result: default: False [-4.80 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx:c]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[opsec.eu]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_TO(0.00)[me.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-3.50)[ip: (-9.14), ipnet: 2001:14f8::/32(-4.65), asn: 12502(-3.72), country: DE(-0.01)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 15:57:18 -0000 Hi! > > We have a system with 10 SATA disks. 2 disks are for the system, > > 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: > > > > bck 72.8T 38.7T 34.1T - - 1% 53% 1.00x ONLINE - > > The problem is that if all 10 disks are connected, the system > > looses track from where it should boot and fails to boot (serial boot log): > Why this order does change? One would expect disks 0 and 1 to be OS disks and the rest for data??? 0+1 are 2.5", and the initial setup was: - we installed system disks as zroot - shipped the box to the housing facility - booted and added the drives At that time we did not do additional tests about the disk/boot sequence etc. > Also the question is, what you mean with ???system looses track???? I interpret the hang during boot as 'it looses track'. So I guess it tries to read the kernel from the wrong drives. > disk4 becomes adaX? why it matters, are you using ufs on boot disks? No, zpool only. I've made a few more details available here: https://people.freebsd.org/~pi/host/dmesg.txt https://people.freebsd.org/~pi/host/devlist.txt https://people.freebsd.org/~pi/host/gpart.txt https://people.freebsd.org/~pi/host/pciconf.txt https://people.freebsd.org/~pi/host/zpool.txt -- pi@opsec.eu +49 171 3101372 One year to go ! From owner-freebsd-current@freebsd.org Thu Sep 19 16:05:01 2019 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 B53CE12743A for ; Thu, 19 Sep 2019 16:05:01 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.evolve.de (mail.evolve.de [213.239.217.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.evolve.de", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z1rs1Gmsz3QlZ; Thu, 19 Sep 2019 16:05:00 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: by mail.evolve.de (OpenSMTPD) with ESMTP id 89c1c41e; Thu, 19 Sep 2019 16:04:58 +0000 (UTC) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id baa283a7 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 19 Sep 2019 16:04:55 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Lockdown adaX numbers to allow booting ? From: Michael Gmelin X-Mailer: iPhone Mail (16G102) In-Reply-To: <20190919155713.GG2863@home.opsec.eu> Date: Thu, 19 Sep 2019 18:04:54 +0200 Cc: Toomas Soome , freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> To: Kurt Jaeger X-Rspamd-Queue-Id: 46Z1rs1Gmsz3QlZ X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-2.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; ASN(0.00)[asn:24940, ipnet:213.239.192.0/18, country:DE]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 16:05:01 -0000 > On 19. Sep 2019, at 17:57, Kurt Jaeger wrote: >=20 > Hi! >=20 >>> We have a system with 10 SATA disks. 2 disks are for the system, >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purpos= es: >>>=20 >>> bck 72.8T 38.7T 34.1T - - 1% 53% 1.00x ONLI= NE - >=20 >>> The problem is that if all 10 disks are connected, the system >>> looses track from where it should boot and fails to boot (serial boot lo= g): >=20 >> Why this order does change? One would expect disks 0 and 1 to be OS disk= s and the rest for data??? >=20 > 0+1 are 2.5", and the initial setup was: > - we installed system disks as zroot=20 > - shipped the box to the housing facility > - booted and added the drives >=20 > At that time we did not do additional tests about the disk/boot sequence > etc. >=20 >> Also the question is, what you mean with ???system looses track???? >=20 > I interpret the hang during boot as 'it looses track'. So I guess > it tries to read the kernel from the wrong drives. >=20 >> disk4 becomes adaX? why it matters, are you using ufs on boot disks? >=20 > No, zpool only. >=20 > I've made a few more details available here: >=20 > https://people.freebsd.org/~pi/host/dmesg.txt > https://people.freebsd.org/~pi/host/devlist.txt > https://people.freebsd.org/~pi/host/gpart.txt > https://people.freebsd.org/~pi/host/pciconf.txt > https://people.freebsd.org/~pi/host/zpool.txt What about gpart output of the pool drives? In general you would create zpools using gptids or gpt labels, not the devic= es, so you=E2=80=99re independent of device numbering. The boot loader shoul= d only be installed on drives that contain the boot pool (maybe you have old= boot loaders on data drives?). -m > --=20 > pi@opsec.eu +49 171 3101372 One year to go != > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"= From owner-freebsd-current@freebsd.org Thu Sep 19 16:27:39 2019 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 0EC60127BA5 for ; Thu, 19 Sep 2019 16:27:39 +0000 (UTC) (envelope-from tsoome@me.com) Received: from mr85p00im-ztdg06011901.me.com (mr85p00im-ztdg06011901.me.com [17.58.23.198]) (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 46Z2Ly18QCz3xTt for ; Thu, 19 Sep 2019 16:27:37 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by mr85p00im-ztdg06011901.me.com (Postfix) with ESMTPSA id BAC2BA60A03; Thu, 19 Sep 2019 16:27:34 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Lockdown adaX numbers to allow booting ? From: Toomas Soome In-Reply-To: <20190919155713.GG2863@home.opsec.eu> Date: Thu, 19 Sep 2019 19:27:31 +0300 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> To: Kurt Jaeger X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-19_05:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909190146 X-Rspamd-Queue-Id: 46Z2Ly18QCz3xTt X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; RCVD_IN_DNSWL_LOW(-0.10)[198.23.58.17.list.dnswl.org : 127.0.5.1]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; ASN(0.00)[asn:714, ipnet:17.58.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.00)[ip: (-7.11), ipnet: 17.58.16.0/20(-2.39), asn: 714(-2.92), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 16:27:39 -0000 > On 19 Sep 2019, at 18:57, Kurt Jaeger wrote: >=20 > Hi! >=20 >>> We have a system with 10 SATA disks. 2 disks are for the system, >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup = purposes: >>>=20 >>> bck 72.8T 38.7T 34.1T - - 1% 53% 1.00x = ONLINE - >=20 >>> The problem is that if all 10 disks are connected, the system >>> looses track from where it should boot and fails to boot (serial = boot log): >=20 >> Why this order does change? One would expect disks 0 and 1 to be OS = disks and the rest for data??? >=20 > 0+1 are 2.5", and the initial setup was: > - we installed system disks as zroot=20 > - shipped the box to the housing facility > - booted and added the drives >=20 > At that time we did not do additional tests about the disk/boot = sequence > etc. >=20 >> Also the question is, what you mean with ???system looses track???? >=20 > I interpret the hang during boot as 'it looses track'. So I guess > it tries to read the kernel from the wrong drives. no, loader does probe disks to see which devices make up the pool and = hung system is not about reading the kernel from wrong place. I bet it is BIOS system? Since the raidz seems to be created = partitionless, what version of freebsd are you using? BIOS up to date? = can you test pool visibility in loader with latest current usb/cd start = - like press esc in menu and check lasdev -v (assuming you get to = menu)=E2=80=A6 the same with uefi? rgds, toomas >=20 >> disk4 becomes adaX? why it matters, are you using ufs on boot disks? >=20 > No, zpool only. >=20 > I've made a few more details available here: >=20 > https://people.freebsd.org/~pi/host/dmesg.txt > https://people.freebsd.org/~pi/host/devlist.txt > https://people.freebsd.org/~pi/host/gpart.txt > https://people.freebsd.org/~pi/host/pciconf.txt > https://people.freebsd.org/~pi/host/zpool.txt >=20 > --=20 > pi@opsec.eu +49 171 3101372 One year to = go ! > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Thu Sep 19 16:47:38 2019 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 234E71284C2 for ; Thu, 19 Sep 2019 16:47:38 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z2p10xNVz3yp7; Thu, 19 Sep 2019 16:47:36 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 46Z2nr4s5cz6dXp; Thu, 19 Sep 2019 18:47:28 +0200 (CEST) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026) with ESMTP id fq2qUw6MqATX; Thu, 19 Sep 2019 18:47:26 +0200 (CEST) Subject: Re: Lockdown adaX numbers to allow booting ? To: Michael Gmelin , Kurt Jaeger Cc: Toomas Soome , freebsd-current@freebsd.org References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> From: Guido Falsi Autocrypt: addr=mad@madpilot.net; keydata= mQENBE+G+l0BCADi/WBQ0aRJfnE7LBPsM0G3m/m3Yx7OPu4iYFvS84xawmRHtCNjWIntsxuX fptkmEo3Rsw816WUrek8dxoUAYdHd+EcpBcnnDzfDH5LW/TZ4gbrFezrHPdRp7wdxi23GN80 qPwHEwXuF0X4Wy5V0OO8B6VT/nA0ADYnBDhXS52HGIJ/GCUjgqJn+phDTdCFLvrSFdmgx4Wl c0W5Z1p5cmDF9l8L/hc959AeyNf7I9dXnjekGM9gVv7UDUYzCifR3U8T0fnfdMmS8NeI9NC+ wuREpRO4lKOkTnj9TtQJRiptlhcHQiAlG1cFqs7EQo57Tqq6cxD1FycZJLuC32bGbgalABEB AAG0Hkd1aWRvIEZhbHNpIDxtYWRAbWFkcGlsb3QubmV0PokBOQQTAQgAIwIbAwIeAQIXgAUL CQgHAwUVCgkICwQWAgMBBQJS79AgAhkBAAoJEBrmhg5Wy9KTc0kH/RO64ORBlTbTHaUaOj8F Je5O5NU2Pt9Cyt5ZWBRvxntr1zPTJGKRPS9ihlIfqT4ZvEngQGp57EUyFbCpI0UWasTerImM tt5WACnGmCzUTB39UXx8Oy4b1EgWeTJQ747e/F1mQLXTNa6ijRBE9fYlTb4gAkPN88/wVV9v 3PZozKLTg16ghBzHM/P7Lk8L7clPEZChX1FTa/6eSt3nvzfCuTMZbBPJF/ph+q1KyPqRgVfh tyhu5dvgMoPz/ni41IfeSrkJTD5RXzdyGR9q4Z1NYeBsLkRjC4LxKAP5KqUsvlOUjKvO1byj ApYdMarol+IGkaSk9e3zVYAJkWKjn/ni8Xa5Ag0EUxB7QQEQAKFhrDceoPdK/IHDSmoj6SQY isvM7VdhcleS7E9DoEAVt7yMbf6HbbMVTTY6ckvwTWQssywLBXNVqxgc4WLJjzfUhgef+WE7 5M3+WFYlOVQLGZY/zEVgma1raYnOHNAOzeHLDmEXjbZP6vGAeDyBbGfQPpE7qGYZ7ubeT3Xw QO+PklcCrvOPj2ZPcAxGNS2xVU/LzONqCrJqLMJSIcCdsbiSP4G5PnDFHtMokaTY6OEr8OEQ fOAerhcHUa/z7Uu8YtmaqKH+QGkE/WEgaRqSiTnv0JOTD+DxehaqvoKPPZ++2NpCZMHB2i6A /xifmQwEiIjEXtcueBRzkNUQkxhqZyS13SrhocL9ydtaVPBzZatAEjUDDEJmAMLVFs45qfyh MiNapHJo2n3MW/E5omqCvEkDdWX/en3P7CK2TemeaDghMsgkNKax/z0wNo5UZCkOPOz0xpNi UilOVbkuezZZNg65741qee2lfXhQIaZ66yT7hphc/N/z3PIAtLeze4u1VR2EXAuZ2sWAdlKC NTlJMsaU/x70BV11Wd/ypnVzM68dfdQIIAj1iMFAD/lXGlEUmKXg5Ov2VQDlTntQoanCYrAg +8CttPzjrydgLZFq3hrtQmfc0se5yv1WHS69+BsUOG09RvvawUDZxUjW19kyeN9THaNRgow3 kSuArUp6zSmJABEBAAGJAR8EGAEIAAkFAlMQe0ECGwwACgkQGuaGDlbL0pMN5wgA4bCkX/qw EVC06ToeR6C2putmSWQMgpDaqrv65Hubo+QGmg2P4ewTYQQ4g6oYWS03qHxqVVWhKz7FjfrV +dH8qbCLfSgIcvdBha7ayGZVrsiuMLKGbw36fcmkZPpSDOfHcP0XH8Z+u9CWj0xUkTxAlZ/7 i6gYSUpG2JWNtdmE/X8VVEyXusCLwy0K0BI60A/4dRTIX3C4QKrJ3ZbUXegz70ynjHf+lQMZ 9IZKASoRMuS5FozPQh6abvmwZEPdf5I9riUElzvHrqJ8Bx0t3Pujdoth+yNHpnBxrtO8LkQd rQ58P0SwcaIX33T2U9pG8bhu5YVR88FQ8OQ0cEsPBpDncrkBDQRPhvpdAQgAsd6mrOq1GSZw lzRscNQa9W2WB/3Tj4ON4PL2e9B+hc9lT/ny2zB3agXu5wbsXTzwxgJpQT7hNHkCSckW98h3 HRjFfhZPNCgInuUGsjcNyVguQh+/47ckhph0s7U+6B4yNuIiqQZk4mo8WgCNj1YIihVmGWEs gDOwMaajbDYZ0r1/3GkKlYjOXeUuT/WgourrSR5oZJVNA/k4X2H7M3JUr1BSc32L7BJt8M7A ntul6k17J0L8GmkvLvTUtQTO+p+DYQMna2ngD3PbAvQRcbEGnkg9ABrdEF0Wp4Gx+gGGWsyF KlHvPdMtgWAy3JsS+rQapG6LoW3yUJpwpEpA86KdBwARAQABiQEfBCgBCAAJBQJTEH0NAh0B AAoJEBrmhg5Wy9KTMZcIAMSsidGF4KpjGcKzhkNK0sEpevcelQ6DzgT7kcXuq6LQ6YOrbof2 /KPgGie9/ToFZfJXH8zE5GefqkKvHZbYssWilFvkI90F9n138kG205NB/2zlaQb74/v9ZMXJ XcipnIx+T2tOMCBgHJU41IMJmB+NfRt5A6CDytJdhWxqppsEo5jjy/7tJM1Nn47G87tAV8qV NUtzbS6zdnbHB4W2BJwCObbVv8epL3hu/L5efV2j2tSbVTmyvK/ClYMBqdtUo3uPX75GF/Ku YDCOP1BTA5zzmzp4PMVd+gmHcMgCZKY6lvcEtdi5FLI0we2kcY8ffPvM2d6MNhFsGLaVI95J 0oqJAR8EGAECAAkFAk+G+l0CGwwACgkQGuaGDlbL0pM18Qf9HTNNhu8N0ISKtmR8lgPhJuu8 9rOEa8KKEatr4fQ7gL+hmYOEqZ/yHLcPQvGxbAlLR7F0SheKvAEk4B1aFwGULPo0SzuO0d/W tVMEbGa95JTm/6mfiymWMlWf8UifD1MDKzzPR7Om0ybeoPM8S/RQTboUU1WLpwd4mg9pVJlK 0xr55GOSHNf4m7S+P1kvl3xgmEj14zVMq9yJBNWFlsQK5ciifh7sFpfuxWdEVbtgIdxpzImK LXSLA0vOroKAvxFTGBrBq3vxV6eUmaKyd5HbbWejmafY1ua5dcnew9lxpWKLdqkC27Vt0Cku +LtTY3325V+BChncwNcJJS7IMmBz6w== Message-ID: <2cadfea9-e3da-f672-e12f-35109f11ad34@madpilot.net> Date: Thu, 19 Sep 2019 18:47:26 +0200 In-Reply-To: <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 46Z2p10xNVz3yp7 X-Spamd-Bar: - X-Spamd-Result: default: False [-1.83 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; MISSING_MIME_VERSION(2.00)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[madpilot.net:+]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; IP_SCORE(-1.83)[ip: (-9.06), ipnet: 159.69.0.0/16(1.72), asn: 24940(-1.79), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; FREEMAIL_CC(0.00)[me.com]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 16:47:38 -0000 On 19/09/19 18:04, Michael Gmelin wrote: > > What about gpart output of the pool drives? > > In general you would create zpools using gptids or gpt labels, not the devices, so you’re independent of device numbering. The boot loader should only be installed on drives that contain the boot pool (maybe you have old boot loaders on data drives?). > Actually the installer will at least some times use the adaX device to create ZFS pools. At least it did for me when I recently rebuilt a machine after a (multiple) disk crash. So it could not be Kurt fault if he has a pool with adaX devices in it. I installed the system on one disk and the installed used adaX to create the pool. I added the second disk to the mirror a few days later. Now I have: pool: zroot state: ONLINE scan: resilvered 24.6G in 0 days 00:09:41 with 0 errors on Tue Sep 3 16:10:08 2019 config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada0p4 ONLINE 0 0 0 gpt/zfs1 ONLINE 0 0 0 errors: No known data errors Now, in the case of a mirror (or a zraid) this could be fixed by detaching adaX devices and reattaching them using the label. Disvantage is the cluster will need to resilver, causing some degraded time and extra disk load. -- Guido Falsi From owner-freebsd-current@freebsd.org Thu Sep 19 16:54:17 2019 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 7C67D1287AB for ; Thu, 19 Sep 2019 16:54:17 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Z2xh35KSz40NK; Thu, 19 Sep 2019 16:54:16 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lf1-x129.google.com with SMTP id r22so2909722lfm.1; Thu, 19 Sep 2019 09:54:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=biCEBS++PDKqNMhNSCiNcHZnwP//i2Aq4zdXaik3s54=; b=FakiIHDMoa3lPgybKLsO7jNxI3HT8r/0BKRA0LJiho2jcyBOjPieKJE7YM+/Bi+ctY NPzP9UiobI+XWcEXoaecOfFmc2qBli6McRVRFfgNn6DNhZOSeUycVb0eEZhy8HmO9qnN JQ+DLbDH3EzOzVZoB5tcpMsQDZzbxPz/wKXc4rhxPlni8mbjTx2ePX6AjeJvB726PXNU xXCo9DJk9MAVenKIvPIUjVWmU9H6tfHCFsEg0hKoY5uc8ksaXMley4xY6UjLAML7mdYP EaNBN3L78Y1bu2MHc6wfKCdBLpb1UXDolv/w6DrmNdSi7Lx6DtET5Q4JzokErrwdqoIV DgWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=biCEBS++PDKqNMhNSCiNcHZnwP//i2Aq4zdXaik3s54=; b=jX7SakK/3o0DqRcgdOkacWkoF15ajCRE0kmFW5b1EeO0L9RufYBzVKxIaAG/embBsO mqfHgBwYTyY1M1/IaTY0zAS3qSJXzXnALXh3osr5UZOvWeB/PeWy7KlrlZbt4KFnJx7D DrhpKCSGqdLpQHam+dMj1B/bBTAInAyoabyyCrMaTPgmWGXf7zXYo43+bjKC5NVOK2oZ 3I0nNBt2SzLu+jgUoowqK2Jae/MXQ6aFyBbll0dC8y4f7S7J4ck9E7o3iDn9XzlWMPJO dGXGKvqQOvKwydMhA28qDC7AHIpD6jSeoeEZ587p+rZ3iwvxLuyNI+s5o/0DmharcbNt qFow== X-Gm-Message-State: APjAAAXl/pBMotWhVtVYmWmkeTK2BXblbkYgTfF0RshHPibvSr+D9008 5xA9nYmuJ1g12ZdwOjHHmquwDSZ+Tqhsm0bOoNJnTQ== X-Google-Smtp-Source: APXvYqxcB2QopGXrV5gSQkxxOIA17vgB/h96FrEhw/rTXv8hGK9eGIcwx7dHy4t8gqCm7GJURg1BpAzYIY5YwE0/wlo= X-Received: by 2002:ac2:43cb:: with SMTP id u11mr5631278lfl.38.1568912054510; Thu, 19 Sep 2019 09:54:14 -0700 (PDT) MIME-Version: 1.0 References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> <2cadfea9-e3da-f672-e12f-35109f11ad34@madpilot.net> In-Reply-To: <2cadfea9-e3da-f672-e12f-35109f11ad34@madpilot.net> From: Freddie Cash Date: Thu, 19 Sep 2019 09:54:03 -0700 Message-ID: Subject: Re: Lockdown adaX numbers to allow booting ? To: Guido Falsi Cc: Michael Gmelin , Kurt Jaeger , Toomas Soome , FreeBSD-Current X-Rspamd-Queue-Id: 46Z2xh35KSz40NK X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=FakiIHDM; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of fjwcash@gmail.com designates 2a00:1450:4864:20::129 as permitted sender) smtp.mailfrom=fjwcash@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[9.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (-9.11), ipnet: 2a00:1450::/32(-2.94), asn: 15169(-2.22), country: US(-0.05)]; 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]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 16:54:17 -0000 On Thu, Sep 19, 2019 at 9:47 AM Guido Falsi wrote: > On 19/09/19 18:04, Michael Gmelin wrote: > > > > What about gpart output of the pool drives? > > > > In general you would create zpools using gptids or gpt labels, not the > devices, so you=E2=80=99re independent of device numbering. The boot load= er should > only be installed on drives that contain the boot pool (maybe you have ol= d > boot loaders on data drives?). > > > > Actually the installer will at least some times use the adaX device to > create ZFS pools. At least it did for me when I recently rebuilt a > machine after a (multiple) disk crash. > > So it could not be Kurt fault if he has a pool with adaX devices in it. > > I installed the system on one disk and the installed used adaX to create > the pool. I added the second disk to the mirror a few days later. > > Now I have: > > pool: zroot > state: ONLINE > scan: resilvered 24.6G in 0 days 00:09:41 with 0 errors on Tue Sep 3 > 16:10:08 2019 > config: > > NAME STATE READ WRITE CKSUM > zroot ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > ada0p4 ONLINE 0 0 0 > gpt/zfs1 ONLINE 0 0 0 > > errors: No known data errors > > Now, in the case of a mirror (or a zraid) this could be fixed by > detaching adaX devices and reattaching them using the label. Disvantage > is the cluster will need to resilver, causing some degraded time and > extra disk load. > Boot off a LiveCD/USB stick. Export the pool. Import the pool with -d /dev/gpt and it will use the GPT labels instead. Reboot into the system, and it should continue to use the GPT labels. No resilvering required. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-current@freebsd.org Thu Sep 19 16:57:12 2019 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 4EAF712895C for ; Thu, 19 Sep 2019 16:57:12 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm1-x341.google.com (mail-wm1-x341.google.com [IPv6:2a00:1450:4864:20::341]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Z3141RW2z40fN; Thu, 19 Sep 2019 16:57:11 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm1-x341.google.com with SMTP id b24so4770207wmj.5; Thu, 19 Sep 2019 09:57:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=HXTb6GmlOnOKZz1NXq/gjbIHOHFklQijxHl2IEHg2PY=; b=hXNDiO1kQtcke1nVp+vr++3R6m3CVmyxoWcAiMvyjBgumaeUzRQsQwsnSaE5qEW1jA pcmx9Jd0BflXAnKrkwTwpljSiPSuZeorLjPAR5XzNY8h480F0uGr4UOsx+lo1CKHUJmY g7qJw7Y/j4eJ0ZtC2Up8Z6TVQKhOUKCQzGhGfmzoUHlAQE9OmiZe5VsV6i/GPS5JAeLx 4DsxbJzGFnihQ4cCZrKI94HtCy6mJRcGjlAC4Rge3Sq8PwHLdiNlEL0CoZQFf0y0jtuN epWdxgN/m0ZmWiIbVpTIZjTBoDdDImDYYyEcQK6Q59eV8GXw88d1Aikjb/F1yIJagnmr FV2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=HXTb6GmlOnOKZz1NXq/gjbIHOHFklQijxHl2IEHg2PY=; b=cKenIokoMfWS30GCcmyn3lesocrLAGSdyAypm9zzGhRIAOAN3rGKg9ZkC4YqZnQiKJ qkvuRTQkf2GtZl7P3455fQZ/AX6jkDmhyMH7Lpy4gVM0ubTiLgxaiOM9xit3pIQvkuqL YvMr7sJhIcnKFtL9RPrZm6U4S0Q2rhJ59qZqRSCsqlBwU+Y4f5DW5Uk1IzG+3IE+gOUE wVOGX72t5DHXuJ4BRNdOCgmbW69cvpkLj2zlWhZ3fcc174wRdV1pMr+EUyVpDUKnAjQE vXEIWhMn3FzblhMyVpS7LsM7XXqhOXMqZhL92uj2tke4dCUsYoICBqNKOEirfdn0rb8A Nq7g== X-Gm-Message-State: APjAAAVzbuoT0iQOuJJHJQgxPdYGuwSiPi//GTOhMqRo+eew7Kl0BlbA Gmhp5q0uSsBRUp+/ayiBJ0HUZtUo X-Google-Smtp-Source: APXvYqyL481r/N98RuZANBdqsoKor4IJ0yAQZMkP3Aa+haqvmnjthRruq87xop/s75THZglckAnyyA== X-Received: by 2002:a05:600c:2059:: with SMTP id p25mr3921915wmg.50.1568912230474; Thu, 19 Sep 2019 09:57:10 -0700 (PDT) Received: from ernst.home (p5B3BEE6F.dip0.t-ipconnect.de. [91.59.238.111]) by smtp.gmail.com with ESMTPSA id o9sm14971669wrh.46.2019.09.19.09.57.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 19 Sep 2019 09:57:09 -0700 (PDT) Date: Thu, 19 Sep 2019 18:57:06 +0200 From: Gary Jennejohn To: Michael Gmelin Cc: Kurt Jaeger , Toomas Soome , freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190919185706.41988cfc@ernst.home> In-Reply-To: <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46Z3141RW2z40fN X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 16:57:12 -0000 On Thu, 19 Sep 2019 18:04:54 +0200 Michael Gmelin wrote: > > On 19. Sep 2019, at 17:57, Kurt Jaeger wrote: > > > > Hi! > > > >>> We have a system with 10 SATA disks. 2 disks are for the system, > >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: > >>> > >>> bck 72.8T 38.7T 34.1T - - 1% 53% 1.00x ONLINE - > > > >>> The problem is that if all 10 disks are connected, the system > >>> looses track from where it should boot and fails to boot (serial boot log): > > > >> Why this order does change? One would expect disks 0 and 1 to be OS disks and the rest for data??? > > > > 0+1 are 2.5", and the initial setup was: > > - we installed system disks as zroot > > - shipped the box to the housing facility > > - booted and added the drives > > > > At that time we did not do additional tests about the disk/boot sequence > > etc. > > > >> Also the question is, what you mean with ???system looses track???? > > > > I interpret the hang during boot as 'it looses track'. So I guess > > it tries to read the kernel from the wrong drives. > > > >> disk4 becomes adaX? why it matters, are you using ufs on boot disks? > > > > No, zpool only. > > > > I've made a few more details available here: > > > > https://people.freebsd.org/~pi/host/dmesg.txt > > https://people.freebsd.org/~pi/host/devlist.txt > > https://people.freebsd.org/~pi/host/gpart.txt > > https://people.freebsd.org/~pi/host/pciconf.txt > > https://people.freebsd.org/~pi/host/zpool.txt > > What about gpart output of the pool drives? > > In general you would create zpools using gptids or gpt labels, > not the devices, so you___re independent of device numbering. > The boot loader should only be installed on drives that contain > the boot pool (maybe you have old boot loaders on data > drives?). > Maybe the cam(4) hint settings could help in your case. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Thu Sep 19 17:01:27 2019 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 E02A7128B37 for ; Thu, 19 Sep 2019 17:01:27 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z35z16x6z40wm; Thu, 19 Sep 2019 17:01:26 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 46Z35x5JfTz6dXs; Thu, 19 Sep 2019 19:01:25 +0200 (CEST) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026) with ESMTP id mjgoA03JCPZa; Thu, 19 Sep 2019 19:01:23 +0200 (CEST) Subject: Re: Lockdown adaX numbers to allow booting ? To: Freddie Cash Cc: Michael Gmelin , Kurt Jaeger , Toomas Soome , FreeBSD-Current References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> <2cadfea9-e3da-f672-e12f-35109f11ad34@madpilot.net> From: Guido Falsi Autocrypt: addr=mad@madpilot.net; prefer-encrypt=mutual; keydata= mQENBE+G+l0BCADi/WBQ0aRJfnE7LBPsM0G3m/m3Yx7OPu4iYFvS84xawmRHtCNjWIntsxuX fptkmEo3Rsw816WUrek8dxoUAYdHd+EcpBcnnDzfDH5LW/TZ4gbrFezrHPdRp7wdxi23GN80 qPwHEwXuF0X4Wy5V0OO8B6VT/nA0ADYnBDhXS52HGIJ/GCUjgqJn+phDTdCFLvrSFdmgx4Wl c0W5Z1p5cmDF9l8L/hc959AeyNf7I9dXnjekGM9gVv7UDUYzCifR3U8T0fnfdMmS8NeI9NC+ wuREpRO4lKOkTnj9TtQJRiptlhcHQiAlG1cFqs7EQo57Tqq6cxD1FycZJLuC32bGbgalABEB AAG0Hkd1aWRvIEZhbHNpIDxtYWRAbWFkcGlsb3QubmV0PokBOQQTAQgAIwIbAwIeAQIXgAUL CQgHAwUVCgkICwQWAgMBBQJS79AgAhkBAAoJEBrmhg5Wy9KTc0kH/RO64ORBlTbTHaUaOj8F Je5O5NU2Pt9Cyt5ZWBRvxntr1zPTJGKRPS9ihlIfqT4ZvEngQGp57EUyFbCpI0UWasTerImM tt5WACnGmCzUTB39UXx8Oy4b1EgWeTJQ747e/F1mQLXTNa6ijRBE9fYlTb4gAkPN88/wVV9v 3PZozKLTg16ghBzHM/P7Lk8L7clPEZChX1FTa/6eSt3nvzfCuTMZbBPJF/ph+q1KyPqRgVfh tyhu5dvgMoPz/ni41IfeSrkJTD5RXzdyGR9q4Z1NYeBsLkRjC4LxKAP5KqUsvlOUjKvO1byj ApYdMarol+IGkaSk9e3zVYAJkWKjn/ni8Xa5Ag0EUxB7QQEQAKFhrDceoPdK/IHDSmoj6SQY isvM7VdhcleS7E9DoEAVt7yMbf6HbbMVTTY6ckvwTWQssywLBXNVqxgc4WLJjzfUhgef+WE7 5M3+WFYlOVQLGZY/zEVgma1raYnOHNAOzeHLDmEXjbZP6vGAeDyBbGfQPpE7qGYZ7ubeT3Xw QO+PklcCrvOPj2ZPcAxGNS2xVU/LzONqCrJqLMJSIcCdsbiSP4G5PnDFHtMokaTY6OEr8OEQ fOAerhcHUa/z7Uu8YtmaqKH+QGkE/WEgaRqSiTnv0JOTD+DxehaqvoKPPZ++2NpCZMHB2i6A /xifmQwEiIjEXtcueBRzkNUQkxhqZyS13SrhocL9ydtaVPBzZatAEjUDDEJmAMLVFs45qfyh MiNapHJo2n3MW/E5omqCvEkDdWX/en3P7CK2TemeaDghMsgkNKax/z0wNo5UZCkOPOz0xpNi UilOVbkuezZZNg65741qee2lfXhQIaZ66yT7hphc/N/z3PIAtLeze4u1VR2EXAuZ2sWAdlKC NTlJMsaU/x70BV11Wd/ypnVzM68dfdQIIAj1iMFAD/lXGlEUmKXg5Ov2VQDlTntQoanCYrAg +8CttPzjrydgLZFq3hrtQmfc0se5yv1WHS69+BsUOG09RvvawUDZxUjW19kyeN9THaNRgow3 kSuArUp6zSmJABEBAAGJAR8EGAEIAAkFAlMQe0ECGwwACgkQGuaGDlbL0pMN5wgA4bCkX/qw EVC06ToeR6C2putmSWQMgpDaqrv65Hubo+QGmg2P4ewTYQQ4g6oYWS03qHxqVVWhKz7FjfrV +dH8qbCLfSgIcvdBha7ayGZVrsiuMLKGbw36fcmkZPpSDOfHcP0XH8Z+u9CWj0xUkTxAlZ/7 i6gYSUpG2JWNtdmE/X8VVEyXusCLwy0K0BI60A/4dRTIX3C4QKrJ3ZbUXegz70ynjHf+lQMZ 9IZKASoRMuS5FozPQh6abvmwZEPdf5I9riUElzvHrqJ8Bx0t3Pujdoth+yNHpnBxrtO8LkQd rQ58P0SwcaIX33T2U9pG8bhu5YVR88FQ8OQ0cEsPBpDncrkBDQRPhvpdAQgAsd6mrOq1GSZw lzRscNQa9W2WB/3Tj4ON4PL2e9B+hc9lT/ny2zB3agXu5wbsXTzwxgJpQT7hNHkCSckW98h3 HRjFfhZPNCgInuUGsjcNyVguQh+/47ckhph0s7U+6B4yNuIiqQZk4mo8WgCNj1YIihVmGWEs gDOwMaajbDYZ0r1/3GkKlYjOXeUuT/WgourrSR5oZJVNA/k4X2H7M3JUr1BSc32L7BJt8M7A ntul6k17J0L8GmkvLvTUtQTO+p+DYQMna2ngD3PbAvQRcbEGnkg9ABrdEF0Wp4Gx+gGGWsyF KlHvPdMtgWAy3JsS+rQapG6LoW3yUJpwpEpA86KdBwARAQABiQEfBCgBCAAJBQJTEH0NAh0B AAoJEBrmhg5Wy9KTMZcIAMSsidGF4KpjGcKzhkNK0sEpevcelQ6DzgT7kcXuq6LQ6YOrbof2 /KPgGie9/ToFZfJXH8zE5GefqkKvHZbYssWilFvkI90F9n138kG205NB/2zlaQb74/v9ZMXJ XcipnIx+T2tOMCBgHJU41IMJmB+NfRt5A6CDytJdhWxqppsEo5jjy/7tJM1Nn47G87tAV8qV NUtzbS6zdnbHB4W2BJwCObbVv8epL3hu/L5efV2j2tSbVTmyvK/ClYMBqdtUo3uPX75GF/Ku YDCOP1BTA5zzmzp4PMVd+gmHcMgCZKY6lvcEtdi5FLI0we2kcY8ffPvM2d6MNhFsGLaVI95J 0oqJAR8EGAECAAkFAk+G+l0CGwwACgkQGuaGDlbL0pM18Qf9HTNNhu8N0ISKtmR8lgPhJuu8 9rOEa8KKEatr4fQ7gL+hmYOEqZ/yHLcPQvGxbAlLR7F0SheKvAEk4B1aFwGULPo0SzuO0d/W tVMEbGa95JTm/6mfiymWMlWf8UifD1MDKzzPR7Om0ybeoPM8S/RQTboUU1WLpwd4mg9pVJlK 0xr55GOSHNf4m7S+P1kvl3xgmEj14zVMq9yJBNWFlsQK5ciifh7sFpfuxWdEVbtgIdxpzImK LXSLA0vOroKAvxFTGBrBq3vxV6eUmaKyd5HbbWejmafY1ua5dcnew9lxpWKLdqkC27Vt0Cku +LtTY3325V+BChncwNcJJS7IMmBz6w== Message-ID: <9cc6e486-a0e5-50aa-1273-3987f7b6ad5e@madpilot.net> Date: Thu, 19 Sep 2019 19:01:22 +0200 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 46Z35z16x6z40wm X-Spamd-Bar: - X-Spamd-Result: default: False [-1.81 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx:c]; MISSING_MIME_VERSION(2.00)[]; MIME_GOOD(-0.10)[text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[madpilot.net:+]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; IP_SCORE(-1.81)[ip: (-8.97), ipnet: 159.69.0.0/16(1.72), asn: 24940(-1.79), country: DE(-0.01)]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 17:01:27 -0000 On 19/09/19 18:54, Freddie Cash wrote: > On Thu, Sep 19, 2019 at 9:47 AM Guido Falsi > wrote: > > On 19/09/19 18:04, Michael Gmelin wrote: > > > > What about gpart output of the pool drives? > > > > In general you would create zpools using gptids or gpt labels, not > the devices, so you’re independent of device numbering. The boot > loader should only be installed on drives that contain the boot pool > (maybe you have old boot loaders on data drives?). > > > > Actually the installer will at least some times use the adaX device to > create ZFS pools. At least it did for me when I recently rebuilt a > machine after a (multiple) disk crash. > > So it could not be Kurt fault if he has a pool with adaX devices in it. > > I installed the system on one disk and the installed used adaX to create > the pool. I added the second disk to the mirror a few days later. > > Now I have: > >   pool: zroot >  state: ONLINE >   scan: resilvered 24.6G in 0 days 00:09:41 with 0 errors on Tue Sep  3 > 16:10:08 2019 > config: > >         NAME          STATE     READ WRITE CKSUM >         zroot         ONLINE       0     0     0 >           mirror-0    ONLINE       0     0     0 >             ada0p4    ONLINE       0     0     0 >             gpt/zfs1  ONLINE       0     0     0 > > errors: No known data errors > > Now, in the case of a mirror (or a zraid) this could be fixed by > detaching adaX devices and reattaching them using the label. Disvantage > is the cluster will need to resilver, causing some degraded time and > extra disk load. > > > Boot off a LiveCD/USB stick.  Export the pool.  Import the pool with -d > /dev/gpt and it will use the GPT labels instead.  Reboot into the > system, and it should continue to use the GPT labels.  No resilvering > required. Good suggestion. I did not think about it. I'll try that once I can reboot the machine. -- Guido Falsi From owner-freebsd-current@freebsd.org Thu Sep 19 17:02:39 2019 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 E749E128D7C for ; Thu, 19 Sep 2019 17:02:39 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Z37M136cz41H4 for ; Thu, 19 Sep 2019 17:02:39 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x42a.google.com with SMTP id v8so3912924wrt.2 for ; Thu, 19 Sep 2019 10:02:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=se3fK1mp/0CZpPRyCQRtkSNnAtvyd4JOM3SaqYbqf+Q=; b=Gtz52pUc6Q4Vi8xBgac7KckTuUzzV86GBQMMjsFR7VR7jA/Vbejtf3RPngGhyG3Vf8 +Wyyi0DBPJN5882ca9CG1K5ysC9UOo8YxEULN2MRlqIhqKd7Qe1XbjgbLBQhgoiALajI jQGF0tGMzgVPsBirayn3rgdYOGIDxJOIm2/Z8wBdp6o8q9FvPwAGsjMIOmYETwM2Lq8e F1RLMbkh3niwQL6sPD3TIR8V2Bhqzr3audOLs0YIY1xfuW9rTS795MvP4ewaPcTEiQFd hItp4g0RRySPTYYr1/7bkCJg58UqUFEJwHD4/uEe8UeafAYJEgwRvWhxhJYiYVadd1HI 7Rdg== 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=se3fK1mp/0CZpPRyCQRtkSNnAtvyd4JOM3SaqYbqf+Q=; b=pbgOl7x6sZc+M7CvkeUztWoV/J9t1hhT86GBPVX76pUGKZI8xbY7Rm04rZEvwc9ziO vJRqUKax1ElCWeSNsKqiIVacIwjKUbsvHFnBOShGUL5f+erx5wQ0cgxUMKZ6uHbrrlmh xQ8AehGxtuYe7/mBuCy1aFeDn5A/NEwsj4mhNxzSesmnJdkOeOCtPa59rLu4NZw4kkOJ p+a3c5w/PEN/VTToUiXkhW8MCIJi61Jb1Jd3dObdY30IVmcBiVaIloWSOhhTP1Txjfz1 ZEJCmED1lusE/vdbfUOUuQM9oNUd0QKvOUXEmrCzNFk7O1HAqwDZgLACyqA/OJUVcuO3 QzLg== X-Gm-Message-State: APjAAAWZNUavtyo+i/zXYnk7HEh0dZEWsiiUXcLkojXxXj/hoc9MxNVG urxA0w2UX0fVfuQgKqCZbTp5iRZqf9EHzw== X-Google-Smtp-Source: APXvYqzjzyikYlHau+5g6YaXCjExnroL67dMj/4sDywui5aRuO8sDU62+Gtcsk6KDljJxUhkutxpow== X-Received: by 2002:a05:6000:12c9:: with SMTP id l9mr7892659wrx.163.1568912557126; Thu, 19 Sep 2019 10:02:37 -0700 (PDT) Received: from [192.168.1.7] (80-42-66-83.dynamic.dsl.as9105.com. [80.42.66.83]) by smtp.gmail.com with ESMTPSA id d10sm6273706wma.42.2019.09.19.10.02.36 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 19 Sep 2019 10:02:36 -0700 (PDT) To: freebsd-current@freebsd.org From: Graham Perrin Subject: =?UTF-8?Q?Firefox_=e2=80=93_GtkFileChooserNative_=e2=80=93_file_sel?= =?UTF-8?Q?ection_dialogues?= Message-ID: <8a98a3d4-ab1c-b5b4-f670-007560e8ee84@gmail.com> Date: Thu, 19 Sep 2019 18:02:35 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.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: 46Z37M136cz41H4 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Gtz52pUc; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of grahamperrin@gmail.com designates 2a00:1450:4864:20::42a as permitted sender) smtp.mailfrom=grahamperrin@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; 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.50)[gmail.com,none]; RECEIVED_SPAMHAUS_PBL(0.00)[83.66.42.80.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; 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.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(0.00)[ip: (-9.26), ipnet: 2a00:1450::/32(-2.94), asn: 15169(-2.22), country: US(-0.05)]; RCVD_IN_DNSWL_NONE(0.00)[a.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 17:02:40 -0000 Firefox does not use xdg-desktop-portal for file selection dialogs > This patch makes Firefox's GTK3 platform support use > GtkFileChooserNative when available. GtkFileChooserNative > transparently uses the desktop portals interface, which > enables Firefox to use native Qt file dialogs on KDE, or > sandboxed file dialogs in Flatpak. – RESOLVED FIXED, mozilla64 Can I benefit from this patch on FreeBSD? (What am I missing?) TIA From owner-freebsd-current@freebsd.org Thu Sep 19 17:15:36 2019 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 07D89129112 for ; Thu, 19 Sep 2019 17:15:36 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z3QH6LRFz41lQ; Thu, 19 Sep 2019 17:15:35 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.92.2 (FreeBSD)) (envelope-from ) id 1iB01h-000FXP-17; Thu, 19 Sep 2019 19:15:29 +0200 Date: Thu, 19 Sep 2019 19:15:29 +0200 From: Kurt Jaeger To: Michael Gmelin Cc: freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190919171529.GH2863@home.opsec.eu> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> X-Rspamd-Queue-Id: 46Z3QH6LRFz41lQ X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.99 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.991,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 17:15:36 -0000 > > I've made a few more details available here: > > https://people.freebsd.org/~pi/host/gpart.txt > What about gpart output of the pool drives? No gpart on the bck pool, raw drives. > In general you would create zpools using gptids or gpt labels, not the devices, so you???re independent of device numbering. The boot loader should only be installed on drives that contain the boot pool (maybe you have old boot loaders on data drives?). I think not, because they are used as raw drives. Maybe that decision was an error in hindsight. -- pi@opsec.eu +49 171 3101372 One year to go ! From owner-freebsd-current@freebsd.org Thu Sep 19 18:48:08 2019 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 9770512B3BC for ; Thu, 19 Sep 2019 18:48:08 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z5T359bxz47d7 for ; Thu, 19 Sep 2019 18:48:07 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.92.2 (FreeBSD)) (envelope-from ) id 1iB1TH-000Fod-DY; Thu, 19 Sep 2019 20:48:03 +0200 Date: Thu, 19 Sep 2019 20:48:03 +0200 From: Kurt Jaeger To: Toomas Soome Cc: freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190919184803.GI2863@home.opsec.eu> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 46Z5T359bxz47d7 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of lists@opsec.eu designates 2001:14f8:200::1 as permitted sender) smtp.mailfrom=lists@opsec.eu X-Spamd-Result: default: False [-4.75 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx:c]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[opsec.eu]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_TO(0.00)[me.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-3.45)[ip: (-8.95), ipnet: 2001:14f8::/32(-4.61), asn: 12502(-3.68), country: DE(-0.01)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 18:48:08 -0000 Hi! > >> Also the question is, what you mean with ???system looses track???? > > I interpret the hang during boot as 'it looses track'. So I guess > > it tries to read the kernel from the wrong drives. > no, loader does probe disks to see which devices make up the pool and hung system is not about reading the kernel from wrong place. > I bet it is BIOS system? If you mean: no UEFI boot ? Yes, it boots via BIOS, not UEFI. > Since the raidz seems to be created partitionless, what version > of freebsd are you using? FreeBSD 12.0p10, amd64. > BIOS up to date? The board is an X10SRi-F. dmidecode reports BIOS 3.1, supermicro has 3.1c, but the release notes do not mention things like that (or at least I don't understand them that way). https://www.supermicro.com/en/products/motherboard/X10SRi-F > can you test pool visibility in loader with latest current > usb/cd start - like press esc in menu and check lsdev -v > (assuming you get to menu) ? the same with uefi? I will test this when I'm at the facility. Will take some time. Thanks for the pointers! -- pi@opsec.eu +49 171 3101372 One year to go ! From owner-freebsd-current@freebsd.org Thu Sep 19 18:56:17 2019 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 9612C12B9D9 for ; Thu, 19 Sep 2019 18:56:17 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.evolve.de (mail.evolve.de [213.239.217.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.evolve.de", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z5fS5FDdz48HR; Thu, 19 Sep 2019 18:56:16 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: by mail.evolve.de (OpenSMTPD) with ESMTP id 7f131086; Thu, 19 Sep 2019 18:56:13 +0000 (UTC) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id d1c99d3a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 19 Sep 2019 18:56:11 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Lockdown adaX numbers to allow booting ? From: Michael Gmelin X-Mailer: iPhone Mail (16G102) In-Reply-To: <20190919171529.GH2863@home.opsec.eu> Date: Thu, 19 Sep 2019 20:56:10 +0200 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> <20190919171529.GH2863@home.opsec.eu> To: Kurt Jaeger X-Rspamd-Queue-Id: 46Z5fS5FDdz48HR X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-2.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:24940, ipnet:213.239.192.0/18, country:DE] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 18:56:17 -0000 On 19. Sep 2019, at 19:15, Kurt Jaeger wrote: >>> I've made a few more details available here: >=20 >>> https://people.freebsd.org/~pi/host/gpart.txt >=20 >> What about gpart output of the pool drives? >=20 > No gpart on the bck pool, raw drives. >=20 >> In general you would create zpools using gptids or gpt labels, not the de= vices, so you???re independent of device numbering. The boot loader should o= nly be installed on drives that contain the boot pool (maybe you have old bo= ot loaders on data drives?). >=20 > I think not, because they are used as raw drives. >=20 > Maybe that decision was an error in hindsight. Yeah, it=E2=80=99s not optimal that way. I made it a habit to use GPT on all= pools and label partitions with the enclosure slots they=E2=80=99re in (mak= es it easier to not make mistakes in case of emergency). I also leave a bit o= f space at the beginning and end of the drive (allows adding in a boot parti= tion later or more flexibility when replacing the drive). Anyway, I=E2=80=99m curious what the exact problem will turn out to be. Cheers, Michael >=20 > --=20 > pi@opsec.eu +49 171 3101372 One year to go != From owner-freebsd-current@freebsd.org Thu Sep 19 19:01:18 2019 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 C9AB512BB87 for ; Thu, 19 Sep 2019 19:01:18 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Z5mG510yz48cX; Thu, 19 Sep 2019 19:01:18 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-lf1-x131.google.com with SMTP id d17so3163819lfa.7; Thu, 19 Sep 2019 12:01:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Q6ighlTD3H/CpsdNqY/gObZ3ktLq+N9XYD5CRRLdAPc=; b=GkeG6uo2+rt4yDj2WpOTrRT2OLJfid/u87ZUVvqo90GYK31YZQ5wbjtUldscRB8DYb KCyFhjcq5u8bfUyIJSCuNhJ0yXamduXFIrF+iO7AB6JpACS6wtrJK+hace0Q/G15JeTa sVTGqKkLh5U942Jl+N2knPMrFDOy0MUIyxdBYPEpXsNuNmZAET756BRH4UUVu2LGd5x+ JOsLvus1F2AWeKXv9eeSLh8FjccE7RHszCql4963zlwk9YgZ5ZFmJ9+joDFUq5X8loML 4xPwW2aNBdIr3i5ehQuk/hJwY1z8Npf8gt5zg3MqfR1nfxJfYHSGUyH6jlPooN277o0V aV8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Q6ighlTD3H/CpsdNqY/gObZ3ktLq+N9XYD5CRRLdAPc=; b=M3cQ7Nx/JliBNwFsHpkSivEMosAKPRDXhM22AqWorGZQQuYWEwMhm49gIA1aU70aoH SZjlJl2fYGYyD9ESOt5QeFSEa9hlVzCOF+HW9vG3co5h9ds6eTzVrh8nDoB6tCIo2cYr YTVMfEDJmBkpAWO2gAmpI7+gPzlomT5j6hhJR4+hLXKjkV9qBCDsE16BElwx0eybTZbO 0kJCztUqjuGdt5liXLPC64MFJCUjavy30Xjav28zKW1G8lbUJJSYXyzNcu/9hU+emum5 yptFHKjseLQGak43QMSaCZraHoBGgIsa5sZnYM0ed3q8twJvKdAXOJFqZw5dzRZOlJju 2S/A== X-Gm-Message-State: APjAAAV7NQPw91JpV83EAMT5ezOmP1xDtXEETgTgh+urXLwKVBoS6Zbf fah1C8zom2VrstqiH8hbb3JzR4zcyo7VFoMyGyesGfkx X-Google-Smtp-Source: APXvYqwTVYQdB5alcsWIObuPsyqkQ+CKcca7npE5Re1J8DHXdtmkmN3m25xhkmmEv7wW8sjBc5qDKq8WZCfzBDel848= X-Received: by 2002:a19:495b:: with SMTP id l27mr5367598lfj.45.1568919676666; Thu, 19 Sep 2019 12:01:16 -0700 (PDT) MIME-Version: 1.0 References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> <20190919171529.GH2863@home.opsec.eu> In-Reply-To: From: Andreas Nilsson Date: Thu, 19 Sep 2019 21:01:06 +0200 Message-ID: Subject: Re: Lockdown adaX numbers to allow booting ? To: Michael Gmelin Cc: Kurt Jaeger , Current FreeBSD X-Rspamd-Queue-Id: 46Z5mG510yz48cX X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 19:01:18 -0000 On Thu, Sep 19, 2019, 20:56 Michael Gmelin wrote: > > > On 19. Sep 2019, at 19:15, Kurt Jaeger wrote: > > >>> I've made a few more details available here: > > > >>> https://people.freebsd.org/~pi/host/gpart.txt > > > >> What about gpart output of the pool drives? > > > > No gpart on the bck pool, raw drives. > > > >> In general you would create zpools using gptids or gpt labels, not the > devices, so you???re independent of device numbering. The boot loader > should only be installed on drives that contain the boot pool (maybe you > have old boot loaders on data drives?). > > > > I think not, because they are used as raw drives. > > > > Maybe that decision was an error in hindsight. > > Yeah, it=E2=80=99s not optimal that way. I made it a habit to use GPT on = all pools > and label partitions with the enclosure slots they=E2=80=99re in (makes i= t easier > to not make mistakes in case of emergency). I also leave a bit of space a= t > the beginning and end of the drive (allows adding in a boot partition lat= er > or more flexibility when replacing the drive). > > Anyway, I=E2=80=99m curious what the exact problem will turn out to be. > > Cheers, > Michael > > > > > -- > > pi@opsec.eu +49 171 3101372 One year to > go ! > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > Seems like more of a bios enumeration issue. You should be able to set a boot order better suited for your setup there. And if that does not work, just move the sata cables around seems like the most straight forward solution. Although I think I've heard it is bad practice to use raw devices for zfs, especially if need to replace a drive, which day happens to be a different revision, with a few fewer blocks available. Then you will not be able to do the replace. Best regards Andreas > From owner-freebsd-current@freebsd.org Thu Sep 19 19:15:45 2019 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 B080B12C17E for ; Thu, 19 Sep 2019 19:15:45 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztdg10012001.me.com (pv50p00im-ztdg10012001.me.com [17.58.6.51]) (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 46Z64w5f2Mz49CF for ; Thu, 19 Sep 2019 19:15:44 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-ztdg10012001.me.com (Postfix) with ESMTPSA id 9424628123A; Thu, 19 Sep 2019 19:15:41 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Lockdown adaX numbers to allow booting ? From: Toomas Soome In-Reply-To: <20190919184803.GI2863@home.opsec.eu> Date: Thu, 19 Sep 2019 22:15:38 +0300 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <87545E27-F860-416C-8A94-B3647C476AB4@me.com> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <20190919184803.GI2863@home.opsec.eu> To: Kurt Jaeger X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-19_05:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909190161 X-Rspamd-Queue-Id: 46Z64w5f2Mz49CF X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; RCVD_IN_DNSWL_LOW(-0.10)[51.6.58.17.list.dnswl.org : 127.0.5.1]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.00)[ip: (-9.52), ipnet: 17.58.0.0/20(-3.41), asn: 714(-2.92), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 19:15:45 -0000 > On 19 Sep 2019, at 21:48, Kurt Jaeger wrote: >=20 > Hi! >=20 >>>> Also the question is, what you mean with ???system looses track???? >=20 >>> I interpret the hang during boot as 'it looses track'. So I guess >>> it tries to read the kernel from the wrong drives. >=20 >> no, loader does probe disks to see which devices make up the pool and = hung system is not about reading the kernel from wrong place. >=20 >> I bet it is BIOS system? >=20 > If you mean: no UEFI boot ? Yes, it boots via BIOS, not UEFI. >=20 >> Since the raidz seems to be created partitionless, what version >> of freebsd are you using? >=20 > FreeBSD 12.0p10, amd64. >=20 >> BIOS up to date? >=20 > The board is an X10SRi-F. dmidecode reports BIOS 3.1, supermicro > has 3.1c, but the release notes do not mention things like that > (or at least I don't understand them that way). >=20 > https://www.supermicro.com/en/products/motherboard/X10SRi-F >=20 >> can you test pool visibility in loader with latest current >> usb/cd start - like press esc in menu and check lsdev -v >> (assuming you get to menu) ? the same with uefi? >=20 > I will test this when I'm at the facility. Will take some time. >=20 Those data disks are 10TB 512e, I can not recall if loader in 12.0p10 = does ignore partitionless disks in pools or not, if the bios is buggy = about large disks, that does explain the hung system=E2=80=A6 in that = case, the loader in current should be fine. rgds, toomas From owner-freebsd-current@freebsd.org Thu Sep 19 20:10:18 2019 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 F214312D6B1 for ; Thu, 19 Sep 2019 20:10:18 +0000 (UTC) (envelope-from daniel.engberg.lists@pyret.net) Received: from relay8-d.mail.gandi.net (relay8-d.mail.gandi.net [217.70.183.201]) (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 46Z7Ht1dBPz4DXX for ; Thu, 19 Sep 2019 20:10:17 +0000 (UTC) (envelope-from daniel.engberg.lists@pyret.net) Received: from webmail.gandi.net (webmail23.sd4.0x35.net [10.200.201.23]) (Authenticated sender: daniel.engberg@pyret.net) by relay8-d.mail.gandi.net (Postfix) with ESMTPA id 73B811BF209; Thu, 19 Sep 2019 20:10:16 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 19 Sep 2019 22:10:16 +0200 From: Daniel Engberg To: freebsd-current@freebsd.org Cc: lists@opsec.eu Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: X-Sender: daniel.engberg.lists@pyret.net User-Agent: Roundcube Webmail/1.3.8 X-Rspamd-Queue-Id: 46Z7Ht1dBPz4DXX X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of daniel.engberg.lists@pyret.net designates 217.70.183.201 as permitted sender) smtp.mailfrom=daniel.engberg.lists@pyret.net X-Spamd-Result: default: False [-1.38 / 15.00]; ARC_NA(0.00)[]; FAKE_REPLY(1.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:217.70.183.192/28:c]; IP_SCORE(-0.98)[ip: (-2.53), ipnet: 217.70.176.0/20(-1.33), asn: 29169(-1.05), country: FR(-0.00)]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[pyret.net]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_IN_DNSWL_LOW(-0.10)[201.183.70.217.list.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RWL_MAILSPIKE_POSSIBLE(0.00)[201.183.70.217.rep.mailspike.net : 127.0.0.17]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:29169, ipnet:217.70.176.0/20, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 20:10:19 -0000 Hi Kurt! You're probably looking for this: https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html Best regards, Daniel From owner-freebsd-current@freebsd.org Thu Sep 19 21:06:50 2019 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 823DE12E758 for ; Thu, 19 Sep 2019 21:06:50 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Z8Y55v8vz4HJj for ; Thu, 19 Sep 2019 21:06:49 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: by mail-vs1-xe2b.google.com with SMTP id f15so3258772vsq.6 for ; Thu, 19 Sep 2019 14:06:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vG4kIz4wMH083N6RRWlYTExdQYQ9E9I3GTTJzQr2N8w=; b=cl1gMA4qGMPNgSTUCTOJlnUS/tzvLdDASgyJciiJVtyKaEbFa77kQNnS1QG6Jl7h89 MANI1pVKtgMzlrOmxTFpcjJY88WMMUbj1LMpNZZsKylug2UVmSX6onalgU4NIYThGM4Q NTKjzJpTjXz/CqPmywmUeMMGoSm7U7uw8YJrMh+tSvHKCvpGNp4QfcyCWKLhp/Q7ynlA MG89yp14O5xtPnKJGkBgQmgKRdFo6lb+9XlcYN3AYAjv9N7BMC7ABESVukjoMzA/A8gu l/xNHgkxtnTBVYXMZrjeugz3chsF538DJ/0+YC9x8AxF+g/vymLukyKghtQ/EBiLDn8J hcLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=vG4kIz4wMH083N6RRWlYTExdQYQ9E9I3GTTJzQr2N8w=; b=Iwn7SzE214JZFhW3f+EaPnra3d7907UA4+dBp2YBy0cocf3xFaYdxnd9spPt1gDzGA FxZDuBX6MbCUZ5UbYWVslgODOpSw5HcLjByz19WRbA45Hs2gldqrd0Q1CxhV5ocfF2+q PYgqrqOZt+YXPVIdbog6hGCKCDz5L+9QwNAHBBEuFAUorktAw/oZ5zmI6OG0UL1gbsW/ kVG4FiKMsydEmOFo95mVC7VDnng0X4hepkORP++r3YayiZJVwhED1oqW3KOlYK6bd7f1 ObevSO3wQ8ibIi0e1tQ3AUUdyqogEaE3zMqxe2+lic2tCnsXixnZtuAr+wuM4kv7jlJ4 1s0Q== X-Gm-Message-State: APjAAAX5YHXtAuGGwLa8Wbji3MG1lo7/VaRS3V3TvRcXbzxvWYtcvNxc gDC3Tt3gTLnH8TRK214BYuh3LVs31zaO8FHedQ== X-Google-Smtp-Source: APXvYqz54QN8UnmnbLDLsQswVzTve2jjKc9C3yaJWXrqW0FbDes70Vmg4xVauwsPU6JomAEsgNNj1ZhTv89Jyn0uggY= X-Received: by 2002:a67:1bc2:: with SMTP id b185mr47451vsb.116.1568927208568; Thu, 19 Sep 2019 14:06:48 -0700 (PDT) MIME-Version: 1.0 References: <20919778.WRJvlOerET@archlaptop> In-Reply-To: <20919778.WRJvlOerET@archlaptop> From: "Clay Daniels Jr." Date: Thu, 19 Sep 2019 16:06:36 -0500 Message-ID: Subject: Re: Another X server start failure To: mms.vanbreukelingen@gmail.com Cc: "FreeBSD Current freebsd-x11@greebsd.org" X-Rspamd-Queue-Id: 46Z8Y55v8vz4HJj X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=cl1gMA4q; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of claydanielsjr@gmail.com designates 2607:f8b0:4864:20::e2b as permitted sender) smtp.mailfrom=claydanielsjr@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.64), ipnet: 2607:f8b0::/32(-2.66), asn: 15169(-2.22), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[b.2.e.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 21:06:50 -0000 Assuming you are running 13.0 Current, and already put the entry in /etc/rc.conf: kld_list="amdgpu" #Yes, no path needed, just "amdgpu" Having done that, try this in /boot/loader.conf hw.syscons.disable=1 # then reboot I'm not the expert here, but the cause is what I might call a "framebuffer problem" with AMD graphics and drm-kmod. There were changes in August to drm-current-kmod that took me a while to overcome myself, but thanks to the folks on this list, I'm back online with 13.0 Current. Good luck, Clay On Thu, Sep 19, 2019 at 6:00 AM wrote: > Having a Raden 240 (sometimes 250) and an older AMDGPU. The older card is > deactivated in BIOS but it is been found by the X -configure problem. X > server > did start one time with -config /root/xorg.conf.new, copied to /etc/X11/ > xorg.conf, never got back any "blank black grafic" screen. Rebuilt new > world > and the kern with WITNESS option on and option LOCK_PROFILING. Using llvm- > devel is useless in that case, if it doesn't with the 8.0.X. > > Can't enter framebuffer mode, tells /var/log/x11_*.log, no VESA, no xfcb. > sddm tells: xauth: bad add command line, bad delete command line, bad add > commandline. It used to work with even X -configure fatal error and sddm, > so > what to xrite in xauth; normally sddm autoconfigs. > > I guess it's the recognization from both cards, what is the option to > really > and finally deactivate this on-board card on an ASUS PRIME 350 board (I > just > mean NOT to cut the part of the board where grafics situatiated with a > laser- > cutter :-) )? This one has never been used as it been too old for good 3D- > Gaming what has been a topic a year ago - not for me, but for a user. > > What's the state of art for 3D-virutal-glasses and gloves? I guess the > same as > with the AI! I guess freeBSD has other functions to do than beeing a > desktop > OS! > > Thx for help in advance, > Yours, Miranda > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Thu Sep 19 21:46:18 2019 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 1602C12F555 for ; Thu, 19 Sep 2019 21:46:18 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Z9Qd2TN2z4KWv; Thu, 19 Sep 2019 21:46:17 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lf1-x12d.google.com with SMTP id c195so3456396lfg.9; Thu, 19 Sep 2019 14:46:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DZL3Qs0S9R13Zp5T+/yJ73RGQmXLvq85Q3a87kVegis=; b=qSlz6aS1UXlsJa32bQwP7wqFaj0rXUJSA2W5ojlZxa97/n7bWlnyJjJSqGwX8TNyaW HZEewoBR039VVO+N8TvJWsIPxsMO0c8IKRXULX5H/s2sSSqdtmrRYnR4xqUDKG3ZC/nV Hy7ND8Za0IZaRadEhvRoXlHLqWcDCitDdrtRN1T4v/x/n85YcLIPCq/zChv0PKd9+n3+ p05vOleGhvCYorwXMSHtyf6DdYyxdE+ifNhiDmTWu+cVlf0D/8WxxccPMnCJfow37la0 AgNZhya61LumC87VjgbhNdGHcI4C0PVX6w0T5JsTtpSjYhILQb9kVIziddGNEVRv/Oui BtBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DZL3Qs0S9R13Zp5T+/yJ73RGQmXLvq85Q3a87kVegis=; b=ck4674Ubs8TBE8yrUexMTYCwsqrepXSrc67Cg+LxZlPxGCTixSO8210qAmZ1QBY7vo v6tTqZ1N7juLvVTH62X0me/wNmQXRFaY7bgxgGZvTyzkT0h/dNnkuA/QyRjMQCTzF1ns mw75MA5lB40IXlQ+tO/bmO4bZwBFQ/8RWeQLwF8huglB9llWcB9qxHwLGcQA/8zIMpDN iIjqcHIq6tRQEooJEb/FTyw4bWnaOwoYdpRFUENY5cNuqQMuVd5GCcqyzCJ65Tr0Gqar 5dp4pInWL86P6lfetsisKUMSez0bd6wZCrnfoTzeCn9McWQn3VD/5xYV1Z2yd2LEXvoU Em0A== X-Gm-Message-State: APjAAAUa1cde621yqzyKQBdSVFU0eQBvRgO7NPuI3m2NfI9rn73Q/+By MyPwb2QUdZtbA8Mo9kUxQPtqOHlAfGk8n+sh7nqU3Q== X-Google-Smtp-Source: APXvYqw4TvIiZA3verm7loEeRmucJakzVpBCZCyGLgiBiUgQ9B81FbMCqTgBDa80lO108+5UjwGS0v0dSwEYetA/JyU= X-Received: by 2002:ac2:4149:: with SMTP id c9mr6252695lfi.128.1568929574535; Thu, 19 Sep 2019 14:46:14 -0700 (PDT) MIME-Version: 1.0 References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> <20190919171529.GH2863@home.opsec.eu> In-Reply-To: From: Freddie Cash Date: Thu, 19 Sep 2019 14:46:02 -0700 Message-ID: Subject: Re: Lockdown adaX numbers to allow booting ? To: Andreas Nilsson Cc: Michael Gmelin , Kurt Jaeger , Current FreeBSD X-Rspamd-Queue-Id: 46Z9Qd2TN2z4KWv X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=qSlz6aS1; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of fjwcash@gmail.com designates 2a00:1450:4864:20::12d as permitted sender) smtp.mailfrom=fjwcash@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[d.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (-8.89), ipnet: 2a00:1450::/32(-2.93), asn: 15169(-2.22), country: US(-0.05)]; FREEMAIL_TO(0.00)[gmail.com]; 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]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 21:46:18 -0000 On Thu, Sep 19, 2019 at 12:01 PM Andreas Nilsson wrote: > Seems like more of a bios enumeration issue. You should be able to set a > boot order better suited for your setup there. And if that does not work, > just move the sata cables around seems like the most straight forward > solution. > > Although I think I've heard it is bad practice to use raw devices for zfs, > especially if need to replace a drive, which day happens to be a different > revision, with a few fewer blocks available. Then you will not be able to > do the replace. > > Back in the good ol' days of ZFS versions where everyone was compatible with Solaris, this was an issue. However, the ondisk format (or ZFS label setup?) was changed to leave 1 MB of free space at the end of the drive to allow for this. With ZFSv6, for example, if you used a raw device for the vdev, and that disk died, and the replacement was 1 sector smaller, the replace would fail. Today, with OpenZFS, the replace would succeed. There's also 1 MB or so of reserved space in the pool such that if you fill the pool "100%", you can still do a "zfs destroy" of a dataset to free up space. Previously, this would fail, as you need space in the pool to write the metadata for the destroy before doing the destroy. ZFS of today is much more resilient to these kinds of niggles that bit us all, back in the day. :D -- Freddie Cash fjwcash@gmail.com From owner-freebsd-current@freebsd.org Thu Sep 19 22:04:07 2019 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 C02AE12FABF; Thu, 19 Sep 2019 22:04:07 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z9qB4NR1z4LNY; Thu, 19 Sep 2019 22:04:06 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id B4WuivIsHIhW9B4Wvib1WB; Thu, 19 Sep 2019 16:04:03 -0600 X-Authority-Analysis: v=2.3 cv=FcFJO626 c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=J70Eh1EUuV4A:10 a=pGLkceISAAAA:8 a=9bHR7MVLAAAA:8 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=f7zcvYf-h5ur5gTkv84A:9 a=_m-7wGuwNc3mVfFE:21 a=2YSe1PtFNj0BYo3z:21 a=QEXdDO2ut3YA:10 a=I7KxNEAtLM9g1UmuDjRu:22 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from 5CG5030TVK-N.esitwifi.local (S0106788a207e2972.gv.shawcable.net [70.66.154.233]) by spqr.komquats.com (Postfix) with ESMTPSA id 25F4D16E; Thu, 19 Sep 2019 15:03:59 -0700 (PDT) Date: Thu, 19 Sep 2019 15:03:35 -0700 In-Reply-To: References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> <6985.1568738188@critter.freebsd.dk> <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: wlan can't discover known networks after relocating To: freebsd-current@freebsd.org, Adrian Chadd , "freebsd-wireless@freebsd.org" CC: Tom Jones , Poul-Henning Kamp , FreeBSD Current , Johannes Lundberg From: Cy Schubert Message-ID: X-CMAE-Envelope: MS4wfJGC0FZ51Tg7c36DeNaHMdHKDHHWcTMv9weqzv1sKu2XejnboSWP/OwCwZ2H0ArYfurGgMTFeOq/k6juKT7fCeigKdcW4lE4gJ9JViWSISKPbPVHnDWp ZG28Qw063Bqa+dARFbUYcZ89wtTyttDh80ZC575RHSZEm9U4ALgJpO6VPHtWTgSGgxKBsgJml/xLQhDAMpooErZOME/Y3UdO0XsjZHsvvftfAqItep0AyBoy rPF1dR5B8qghf+GcXP7B95u6q+6OA1R0PlRHvhycAx+dh5XHx+0j0Wp2TRzBPfppn+q+EqeU2UDiBewbtpyDkA== X-Rspamd-Queue-Id: 46Z9qB4NR1z4LNY X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of cy.schubert@cschubert.com has no SPF policy when checking 64.59.136.138) smtp.mailfrom=cy.schubert@cschubert.com X-Spamd-Result: default: False [-2.92 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-2.32)[ip: (-6.02), ipnet: 64.59.128.0/20(-3.08), asn: 6327(-2.40), country: CA(-0.09)]; RCVD_IN_DNSWL_NONE(0.00)[138.136.59.64.list.dnswl.org : 127.0.5.0]; RCPT_COUNT_SEVEN(0.00)[7]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MID_RHS_MATCH_FROM(0.00)[]; SUSPICIOUS_RECIPS(1.50)[]; RECEIVED_SPAMHAUS_PBL(0.00)[233.154.66.70.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11, 17.125.67.70.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 22:04:07 -0000 On September 19, 2019 8:20:07 AM PDT, Adrian Chadd wrote: >Roaming is done in wpa_supplicant when it's running=2EThat's where the >smarts >need to be=2E :( > > > >-adrian > > >On Thu, 19 Sep 2019 at 05:44, Bjoern A=2E Zeeb > >wrote: > >> On 19 Sep 2019, at 12:28, Tom Jones wrote: >> >> Hi, >> >> freebsd-wireless might be a better list for all this =2E=2E >> >> >> > On Tue, Sep 17, 2019 at 04:36:28PM +0000, Poul-Henning Kamp wrote: >> >> -------- >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD=2Eorg>, >> >> Johannes Lundber >> >> g writes: >> >> >> >>> For a long time now I have had this problem with iwm and wlan0=2E >> >>> Whenever >> >>> I move between work and home it won't reconnect automatically and >I >> >>> have >> >>> to do wlan0 scan manually for it to pick up the different >network=2E >> >> >> >> I suffer from the dreaded "reason=3D0" when I move inside my house: >> >> >> >> > scan >> >> OK >> >> <3>CTRL-EVENT-SCAN-RESULTS >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 >(SSID=3D'Palombia' >> >> freq=3D2452 MHz) >> >> <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:3d:a2:e9 reason=3D0 >> >> <3>CTRL-EVENT-SCAN-RESULTS >> >> <3>Trying to associate with 6c:3b:6b:ab:ce:d4 >(SSID=3D'Palombia' >> >> freq=3D2412 MHz) >> >> <3>Associated with 6c:3b:6b:ab:ce:d4 >> >> >> >> a2:e9 is the loudest AP here in my office, but my I have been in >the >> >> other end of the house iwn consistently fails to associate with it >> >> and >> >> and keeps picking the weaker AP in the far end=2E >> >> >> >> Eventually (hours!) it disconnects from the weaker ap, also with >> >> "reason=3D0" and gets it right: >> >> >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 >[GTK=3DCCMP] >> >> <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:ab:ce:d4 reason=3D0 >> >> <3>CTRL-EVENT-SCAN-RESULTS >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 >(SSID=3D'Palombia' >> >> freq=3D2452 MHz) >> >> <3>Associated with 6c:3b:6b:3d:a2:e9 >> >> <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 >[PTK=3DCCMP >> >> GTK=3DCCMP] >> >> <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 >> completed >> >> [id=3D3 id_str=3D] >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 >[GTK=3DCCMP] >> >> >> >> And yes, working roaming would be nice too=2E=2E=2E >> > >> > I have the problem that when roaming networks become disabled >> > >> > $ wpa_cli >> > Selected interface 'wlan0' >> > >> > Interactive mode >> > >> > > list_networks >> > network id / ssid / bssid / flags >> > 0 network1 any [CURRENT] >> > 1 network2 any [DISABLED] >> > 2 network3 any [DISABLED] >> > 3 network4 any [DISABLED] >> > 4 network5 any [DISABLED] >> > Selected interface 'wlan0' >> > >> > >> > I address this by doing network_enable x in wpa_cli and it all >comes >> > back=2E I asked Adrian about this in the past, but it needs some >> > debugging >> > to pin down=2E >> >> >> Is this iwm(4) as well in your case or another card? >> >> /bz >> _______________________________________________ >> freebsd-wireless@freebsd=2Eorg mailing list >> https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to >"freebsd-wireless-unsubscribe@freebsd=2Eorg >> " >> >_______________________________________________ >freebsd-current@freebsd=2Eorg mailing list >https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to >"freebsd-current-unsubscribe@freebsd=2Eorg" With wpa_supplicant running roaming is set to manual=2E Bgscan should be e= nabled=2E =20 At home we have two n (and 2 g) wifi networks=2E When powering off one ap = it connects to the other (in addition to using lagg to failover from ethern= et to wifi and back)=2E Your wpa_supplicant should contain each ssid you intend to use=2E A wildca= rd can be used for open networks=2E It's a while since I've tested this functionality but I can test again whe= n I get home tonight=2E=20 --=20 Pardon the typos and autocorrect, small keyboard in use=2E Cheers, Cy Schubert FreeBSD UNIX: Web: http://www=2EFreeBSD=2Eorg The need of the many outweighs the greed of the few=2E From owner-freebsd-current@freebsd.org Thu Sep 19 22:06:16 2019 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 B1B0512FC3D; Thu, 19 Sep 2019 22:06:16 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Z9sg72Dkz4LbB; Thu, 19 Sep 2019 22:06:15 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-yb1-xb29.google.com with SMTP id t15so1926001ybg.7; Thu, 19 Sep 2019 15:06:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3g8Gg/HJeCzMJUy2vIcp0E6F6jUmAdtDFu9grw/iaOA=; b=dyWbNw5jhDixmva7pZ5/B89glMl1jFDAt+1qaKFPxKTfT5jcBQ1fyniMtXfO1JrsAZ lz4mrgu8LMvyzSD6jtNvBaFaoMNZQ+PredcXr3E6fs/M1kE1DebkPXKjJQgk26EusAX2 OYrRFlrh5kl2v/KluO9V01JbobGyl5Tj09E7waX3MrhWoTapsDPKyEAw/OzuqTrZ+O0h GySz79JPB9ag+MUu+44nmXYzrXWI+U5K1ZMlnomZz7GB7KB8VZJlRYO/e38o2vgXVI7C icootRHlB2u5GLwHtBw7HP9/Kqi7jOWhfeTlhFjqsOy8m04dtrlttHLV0lLYpuk8KF99 3dXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3g8Gg/HJeCzMJUy2vIcp0E6F6jUmAdtDFu9grw/iaOA=; b=NTxy+CWBMXrAlkjSyZwtAYbBmuCAH5MpyRRrChkSSsCBqzrx+pg+XQ6ISnSdhwjb1K 4DWoTfuh6bVCOrZbeIFrCP4B5Wi/X6VfqinqeL6dkl8lwO2roDup7ku+xxfolPRHs3Nn s2EvI2IkDrQ9lY6WtJZMEQzNrAws6bTP3kmCczX2dD4kWo5q8MREu3IVLRgNF9Tytqj+ pghktJF/UKgDrncTXRKqC7hvaJy/iLekCKm4ArBBQF+rMWBY/H0F2+7qBfrajk5K3fhV IUKttEohWE3DPuB1wSR3aSkoNPQgXN39pp1ZWGWyeNZXO+vey7hZT342nAVp6ORo+cdz I/MQ== X-Gm-Message-State: APjAAAVLPMDS/pkp8o5bfaLU7ggGukc7EJqUNEywBIrghjIPG4WfbSpf j/MCZMOtMsekohfeVSVS3ZIMroZT3Wz3bYw6FB8wGg== X-Google-Smtp-Source: APXvYqxoFKbxNd6/EW/F1Gg/BOYNDUbWDow0sKQpSsuopKDL2EK3Dcsd7lLmUYH5mLTt9PS8GjEw4YZYbbLod/Jhgp8= X-Received: by 2002:a25:25ca:: with SMTP id l193mr8518569ybl.193.1568930774463; Thu, 19 Sep 2019 15:06:14 -0700 (PDT) MIME-Version: 1.0 References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> <6985.1568738188@critter.freebsd.dk> <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> In-Reply-To: From: Adrian Chadd Date: Thu, 19 Sep 2019 15:06:00 -0700 Message-ID: Subject: Re: wlan can't discover known networks after relocating To: Cy Schubert Cc: freebsd-current , "freebsd-wireless@freebsd.org" , Tom Jones , Poul-Henning Kamp , Johannes Lundberg X-Rspamd-Queue-Id: 46Z9sg72Dkz4LbB X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=dyWbNw5j; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of adrianchadd@gmail.com designates 2607:f8b0:4864:20::b29 as permitted sender) smtp.mailfrom=adrianchadd@gmail.com X-Spamd-Result: default: False [-0.50 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; URI_COUNT_ODD(1.00)[9]; RCPT_COUNT_FIVE(0.00)[6]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[9.2.b.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (-9.16), ipnet: 2607:f8b0::/32(-2.66), asn: 15169(-2.22), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; SUSPICIOUS_RECIPS(1.50)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 22:06:16 -0000 So roaming in ifconfig/net80211 is what's set to manual. wpa_supplicant right now does RSSI threshold based roaming. All of the roaming and network preferences when wpa_supplicant is running is done in wpa_supplicant. That's where you have to look. Ideally wpa_supplicant would be triggering bgscan too periodically rather than only when the RSSI is low. -adrian On Thu, 19 Sep 2019 at 15:04, Cy Schubert wrote: > On September 19, 2019 8:20:07 AM PDT, Adrian Chadd > wrote: > >Roaming is done in wpa_supplicant when it's running.That's where the > >smarts > >need to be. :( > > > > > > > >-adrian > > > > > >On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb > > > >wrote: > > > >> On 19 Sep 2019, at 12:28, Tom Jones wrote: > >> > >> Hi, > >> > >> freebsd-wireless might be a better list for all this .. > >> > >> > >> > On Tue, Sep 17, 2019 at 04:36:28PM +0000, Poul-Henning Kamp wrote: > >> >> -------- > >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org>, > >> >> Johannes Lundber > >> >> g writes: > >> >> > >> >>> For a long time now I have had this problem with iwm and wlan0. > >> >>> Whenever > >> >>> I move between work and home it won't reconnect automatically and > >I > >> >>> have > >> >>> to do wlan0 scan manually for it to pick up the different > >network. > >> >> > >> >> I suffer from the dreaded "reason=0" when I move inside my house: > >> >> > >> >> > scan > >> >> OK > >> >> <3>CTRL-EVENT-SCAN-RESULTS > >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 > >(SSID='Palombia' > >> >> freq=2452 MHz) > >> >> <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0 > >> >> <3>CTRL-EVENT-SCAN-RESULTS > >> >> <3>Trying to associate with 6c:3b:6b:ab:ce:d4 > >(SSID='Palombia' > >> >> freq=2412 MHz) > >> >> <3>Associated with 6c:3b:6b:ab:ce:d4 > >> >> > >> >> a2:e9 is the loudest AP here in my office, but my I have been in > >the > >> >> other end of the house iwn consistently fails to associate with it > >> >> and > >> >> and keeps picking the weaker AP in the far end. > >> >> > >> >> Eventually (hours!) it disconnects from the weaker ap, also with > >> >> "reason=0" and gets it right: > >> >> > >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 > >[GTK=CCMP] > >> >> <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0 > >> >> <3>CTRL-EVENT-SCAN-RESULTS > >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 > >(SSID='Palombia' > >> >> freq=2452 MHz) > >> >> <3>Associated with 6c:3b:6b:3d:a2:e9 > >> >> <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 > >[PTK=CCMP > >> >> GTK=CCMP] > >> >> <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 > >> completed > >> >> [id=3 id_str=] > >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 > >[GTK=CCMP] > >> >> > >> >> And yes, working roaming would be nice too... > >> > > >> > I have the problem that when roaming networks become disabled > >> > > >> > $ wpa_cli > >> > Selected interface 'wlan0' > >> > > >> > Interactive mode > >> > > >> > > list_networks > >> > network id / ssid / bssid / flags > >> > 0 network1 any [CURRENT] > >> > 1 network2 any [DISABLED] > >> > 2 network3 any [DISABLED] > >> > 3 network4 any [DISABLED] > >> > 4 network5 any [DISABLED] > >> > Selected interface 'wlan0' > >> > > >> > > >> > I address this by doing network_enable x in wpa_cli and it all > >comes > >> > back. I asked Adrian about this in the past, but it needs some > >> > debugging > >> > to pin down. > >> > >> > >> Is this iwm(4) as well in your case or another card? > >> > >> /bz > >> _______________________________________________ > >> freebsd-wireless@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> To unsubscribe, send any mail to > >"freebsd-wireless-unsubscribe@freebsd.org > >> " > >> > >_______________________________________________ > >freebsd-current@freebsd.org mailing list > >https://lists.freebsd.org/mailman/listinfo/freebsd-current > >To unsubscribe, send any mail to > >"freebsd-current-unsubscribe@freebsd.org" > > With wpa_supplicant running roaming is set to manual. Bgscan should be > enabled. > > At home we have two n (and 2 g) wifi networks. When powering off one ap it > connects to the other (in addition to using lagg to failover from ethernet > to wifi and back). > > Your wpa_supplicant should contain each ssid you intend to use. A wildcard > can be used for open networks. > > It's a while since I've tested this functionality but I can test again > when I get home tonight. > > > -- > Pardon the typos and autocorrect, small keyboard in use. > Cheers, > Cy Schubert > FreeBSD UNIX: Web: http://www.FreeBSD.org > > The need of the many outweighs the greed of the few. > From owner-freebsd-current@freebsd.org Thu Sep 19 22:21:18 2019 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 56FEFE821D; Thu, 19 Sep 2019 22:21:18 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46ZBC20CZyz4MZ4; Thu, 19 Sep 2019 22:21:18 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from [10.50.6.171] (wsip-184-181-13-226.ph.ph.cox.net [184.181.13.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: johalun) by smtp.freebsd.org (Postfix) with ESMTPSA id 45B13F185; Thu, 19 Sep 2019 22:21:17 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Subject: Re: wlan can't discover known networks after relocating To: Adrian Chadd , Cy Schubert Cc: freebsd-current , "freebsd-wireless@freebsd.org" , Tom Jones , Poul-Henning Kamp References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> <6985.1568738188@critter.freebsd.dk> <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> From: Johannes Lundberg Message-ID: <7938e5fa-67da-35fa-10d0-ee3004438df7@FreeBSD.org> Date: Thu, 19 Sep 2019 15:21:15 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 22:21:18 -0000 On 9/19/19 3:06 PM, Adrian Chadd wrote: > So roaming in ifconfig/net80211 is what's set to manual. > > wpa_supplicant right now does RSSI threshold based roaming. All of the > roaming and network preferences when wpa_supplicant is running is done > in wpa_supplicant. That's where you have to look. Ideally > wpa_supplicant would be triggering bgscan too periodically rather than > only when the RSSI is low. > > > > -adrian > > > On Thu, 19 Sep 2019 at 15:04, Cy Schubert > wrote: > > On September 19, 2019 8:20:07 AM PDT, Adrian Chadd > > wrote: > >Roaming is done in wpa_supplicant when it's running.That's where the > >smarts > >need to be. :( > > > > > > > >-adrian > > > > > >On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb > > > > >wrote: > > > >> On 19 Sep 2019, at 12:28, Tom Jones wrote: > >> > >> Hi, > >> > >> freebsd-wireless might be a better list for all this .. > >> > >> > >> > On Tue, Sep 17, 2019 at 04:36:28PM +0000, Poul-Henning Kamp > wrote: > >> >> -------- > >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org>, > >> >> Johannes Lundber > >> >> g writes: > >> >> > >> >>> For a long time now I have had this problem with iwm and wlan0. > >> >>> Whenever > >> >>> I move between work and home it won't reconnect > automatically and > >I > >> >>> have > >> >>> to do wlan0 scan manually for it to pick up the different > >network. > >> >> > >> >> I suffer from the dreaded "reason=0" when I move inside my > house: > >> >> > >> >>      > scan > >> >>      OK > >> >>      <3>CTRL-EVENT-SCAN-RESULTS > >> >>      <3>Trying to associate with 6c:3b:6b:3d:a2:e9 > >(SSID='Palombia' > >> >> freq=2452 MHz) > >> >>      <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0 > >> >>      <3>CTRL-EVENT-SCAN-RESULTS > >> >>      <3>Trying to associate with 6c:3b:6b:ab:ce:d4 > >(SSID='Palombia' > >> >> freq=2412 MHz) > >> >>      <3>Associated with 6c:3b:6b:ab:ce:d4 > >> >> > >> >> a2:e9 is the loudest AP here in my office, but my I have been in > >the > >> >> other end of the house iwn consistently fails to associate > with it > >> >> and > >> >> and keeps picking the weaker AP in the far end. > >> >> > >> >> Eventually (hours!) it disconnects from the weaker ap, also with > >> >> "reason=0" and gets it right: > >> >> > >> >>      <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 > >[GTK=CCMP] > >> >>      <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0 > >> >>      <3>CTRL-EVENT-SCAN-RESULTS > >> >>      <3>Trying to associate with 6c:3b:6b:3d:a2:e9 > >(SSID='Palombia' > >> >> freq=2452 MHz) > >> >>      <3>Associated with 6c:3b:6b:3d:a2:e9 > >> >>      <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 > >[PTK=CCMP > >> >> GTK=CCMP] > >> >>      <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 > >> completed > >> >> [id=3 id_str=] > >> >>      <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 > >[GTK=CCMP] > >> >> > >> >> And yes, working roaming would be nice too... > >> > > >> > I have the problem that when roaming networks become disabled > >> > > >> >       $ wpa_cli > >> >       Selected interface 'wlan0' > >> > > >> >       Interactive mode > >> > > >> >       > list_networks > >> >       network id / ssid / bssid / flags > >> >       0       network1        any     [CURRENT] > >> >       1       network2 any    [DISABLED] > >> >       2       network3 any    [DISABLED] > >> >       3       network4 any    [DISABLED] > >> >       4       network5 any    [DISABLED] > >> >       Selected interface 'wlan0' > >> > > >> > > >> > I address this by doing network_enable x in wpa_cli and it all > >comes > >> > back. I asked Adrian about this in the past, but it needs some > >> > debugging > >> > to pin down. > >> > >> > >> Is this iwm(4) as well in your case or another card? > >> > >> /bz > >> _______________________________________________ > >> freebsd-wireless@freebsd.org > mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> To unsubscribe, send any mail to > >"freebsd-wireless-unsubscribe@freebsd.org > > >> " > >> > >_______________________________________________ > >freebsd-current@freebsd.org > mailing list > >https://lists.freebsd.org/mailman/listinfo/freebsd-current > >To unsubscribe, send any mail to > >"freebsd-current-unsubscribe@freebsd.org > " > > With wpa_supplicant running roaming is set to manual. Bgscan > should be enabled.  > > At home we have two n (and 2 g) wifi networks. When powering off > one ap it connects to the other (in addition to using lagg to > failover from ethernet to wifi and back). > > Your wpa_supplicant should contain each ssid you intend to use. A > wildcard can be used for open networks. > > It's a while since I've tested this functionality but I can test > again when I get home tonight. > > > -- > Pardon the typos and autocorrect, small keyboard in use. > Cheers, > Cy Schubert > > FreeBSD UNIX: Web: http://www.FreeBSD.org > >         The need of the many outweighs the greed of the few. > Hmm so in other words, you have to set bgscan for each network entry you want roaming? What are some good values for this? From owner-freebsd-current@freebsd.org Thu Sep 19 22:30:39 2019 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 D80E5E86CF; Thu, 19 Sep 2019 22:30:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46ZBPq5XHhz4NN4; Thu, 19 Sep 2019 22:30:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-yb1-xb33.google.com with SMTP id v5so1951367ybq.4; Thu, 19 Sep 2019 15:30:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NnMB8EGUeHv5eo3FFwzI94GZcZlaEygAHBOzBAcJZVA=; b=PJGYg4atFw2O1d097UA1+UzrHbhv2WxIXn3X5KP6A7Mb/tyEPAehLhCfu2hkJiabel 2prRJQPQ2aJHVnhxWNXMbTNGBFi+t4hjlmFFnFOmRVTydzPjOpQLHEfEFfkowoZw5m9I cEIfWEKn43nez0Y1BNeX+C+jlPcyrn7DLUJsY+xYXwLWRZWeJhbgv/puGkVkYVoG2PQh beyF99Q0OZiRmrvCgBuHhA9jjNglvXepRIfE3zd6FgbZ/o1mbnj9daXojf1VIre/8mAe QSQA5XVIkv/n66+6ptzDE9lqmAktzVXyskbuzAAcpGyhCJ2sdT3VYGTh8epti+Bpuxvg lM+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NnMB8EGUeHv5eo3FFwzI94GZcZlaEygAHBOzBAcJZVA=; b=CRYYp9DRMUVj1r9Ei7dgOQcJHkrx4rd/CQNsCThSe/jVtjScm+EvDcgYDypT2R3GTF cOmdRl28qs3ygjW4wBgKOUvLzEohfauMJGDAcMHGZwir47N9Ipm0bKLVxKV4JypHIc7y KHtXtRp3+IaxNCPU0bkJv9/OQUY1aVi2D5YXqNsypzlanrxy+MClzO1WRgsbyUYKu8Ad Y3qgnTt43VSO4a7cmp+4DtqhwsAf8BSJ3zd0Q8caPXfyoXwVv2wJUM5zdmg5Qk9kv8K1 FVpdK7QHtL5cNz/jDwt5Vml3A5ZgRbGCnu/52CsV0LOCGjgTyCn3v4Y94aoklPtOfvj8 EUzA== X-Gm-Message-State: APjAAAWRXN89iO9C0PD3DihbpohPHYt34jbTUcOf5tf8kA7gAXZzdOmx yjsgHV3EEB0HoHKWSAkFFCQi0r5LrIFNbqxnlv30xw== X-Google-Smtp-Source: APXvYqzweZFDf+63yeWEHmrnOp2qGR4Cr08ICPQVpBdBDY4g46LspcfVAw81CfovSTebwHxQpnZ7NqQNxRhS+/zvPYY= X-Received: by 2002:a25:b682:: with SMTP id s2mr8567095ybj.264.1568932236757; Thu, 19 Sep 2019 15:30:36 -0700 (PDT) MIME-Version: 1.0 References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> <6985.1568738188@critter.freebsd.dk> <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> <7938e5fa-67da-35fa-10d0-ee3004438df7@FreeBSD.org> In-Reply-To: <7938e5fa-67da-35fa-10d0-ee3004438df7@FreeBSD.org> From: Adrian Chadd Date: Thu, 19 Sep 2019 15:30:22 -0700 Message-ID: Subject: Re: wlan can't discover known networks after relocating To: Johannes Lundberg Cc: Cy Schubert , freebsd-current , "freebsd-wireless@freebsd.org" , Tom Jones , Poul-Henning Kamp X-Rspamd-Queue-Id: 46ZBPq5XHhz4NN4 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Sep 2019 22:30:39 -0000 I've no idea, bgscan is broken with atheros NICs because the driver still doesn't do background scan without dropping frames :( (one of many thing I'd love to fix, but life/time.) please do experiment though! I think wpa_supplicant's roaming logic would benefit from a lot more work. -adrian On Thu, 19 Sep 2019 at 15:21, Johannes Lundberg wrote: > > On 9/19/19 3:06 PM, Adrian Chadd wrote: > > So roaming in ifconfig/net80211 is what's set to manual. > > wpa_supplicant right now does RSSI threshold based roaming. All of the > roaming and network preferences when wpa_supplicant is running is done in > wpa_supplicant. That's where you have to look. Ideally wpa_supplicant would > be triggering bgscan too periodically rather than only when the RSSI is low. > > > > -adrian > > > On Thu, 19 Sep 2019 at 15:04, Cy Schubert wrote: > >> On September 19, 2019 8:20:07 AM PDT, Adrian Chadd < >> adrian.chadd@gmail.com> wrote: >> >Roaming is done in wpa_supplicant when it's running.That's where the >> >smarts >> >need to be. :( >> > >> > >> > >> >-adrian >> > >> > >> >On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb >> > >> >wrote: >> > >> >> On 19 Sep 2019, at 12:28, Tom Jones wrote: >> >> >> >> Hi, >> >> >> >> freebsd-wireless might be a better list for all this .. >> >> >> >> >> >> > On Tue, Sep 17, 2019 at 04:36:28PM +0000, Poul-Henning Kamp wrote: >> >> >> -------- >> >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> >> <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org>, >> >> >> Johannes Lundber >> >> >> g writes: >> >> >> >> >> >>> For a long time now I have had this problem with iwm and wlan0. >> >> >>> Whenever >> >> >>> I move between work and home it won't reconnect automatically and >> >I >> >> >>> have >> >> >>> to do wlan0 scan manually for it to pick up the different >> >network. >> >> >> >> >> >> I suffer from the dreaded "reason=0" when I move inside my house: >> >> >> >> >> >> > scan >> >> >> OK >> >> >> <3>CTRL-EVENT-SCAN-RESULTS >> >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 >> >(SSID='Palombia' >> >> >> freq=2452 MHz) >> >> >> <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0 >> >> >> <3>CTRL-EVENT-SCAN-RESULTS >> >> >> <3>Trying to associate with 6c:3b:6b:ab:ce:d4 >> >(SSID='Palombia' >> >> >> freq=2412 MHz) >> >> >> <3>Associated with 6c:3b:6b:ab:ce:d4 >> >> >> >> >> >> a2:e9 is the loudest AP here in my office, but my I have been in >> >the >> >> >> other end of the house iwn consistently fails to associate with it >> >> >> and >> >> >> and keeps picking the weaker AP in the far end. >> >> >> >> >> >> Eventually (hours!) it disconnects from the weaker ap, also with >> >> >> "reason=0" and gets it right: >> >> >> >> >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 >> >[GTK=CCMP] >> >> >> <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0 >> >> >> <3>CTRL-EVENT-SCAN-RESULTS >> >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 >> >(SSID='Palombia' >> >> >> freq=2452 MHz) >> >> >> <3>Associated with 6c:3b:6b:3d:a2:e9 >> >> >> <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 >> >[PTK=CCMP >> >> >> GTK=CCMP] >> >> >> <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 >> >> completed >> >> >> [id=3 id_str=] >> >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 >> >[GTK=CCMP] >> >> >> >> >> >> And yes, working roaming would be nice too... >> >> > >> >> > I have the problem that when roaming networks become disabled >> >> > >> >> > $ wpa_cli >> >> > Selected interface 'wlan0' >> >> > >> >> > Interactive mode >> >> > >> >> > > list_networks >> >> > network id / ssid / bssid / flags >> >> > 0 network1 any [CURRENT] >> >> > 1 network2 any [DISABLED] >> >> > 2 network3 any [DISABLED] >> >> > 3 network4 any [DISABLED] >> >> > 4 network5 any [DISABLED] >> >> > Selected interface 'wlan0' >> >> > >> >> > >> >> > I address this by doing network_enable x in wpa_cli and it all >> >comes >> >> > back. I asked Adrian about this in the past, but it needs some >> >> > debugging >> >> > to pin down. >> >> >> >> >> >> Is this iwm(4) as well in your case or another card? >> >> >> >> /bz >> >> _______________________________________________ >> >> freebsd-wireless@freebsd.org mailing list >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> >> To unsubscribe, send any mail to >> >"freebsd-wireless-unsubscribe@freebsd.org >> >> " >> >> >> >_______________________________________________ >> >freebsd-current@freebsd.org mailing list >> >https://lists.freebsd.org/mailman/listinfo/freebsd-current >> >To unsubscribe, send any mail to >> >"freebsd-current-unsubscribe@freebsd.org" >> >> With wpa_supplicant running roaming is set to manual. Bgscan should be >> enabled. >> >> At home we have two n (and 2 g) wifi networks. When powering off one ap >> it connects to the other (in addition to using lagg to failover from >> ethernet to wifi and back). >> >> Your wpa_supplicant should contain each ssid you intend to use. A >> wildcard can be used for open networks. >> >> It's a while since I've tested this functionality but I can test again >> when I get home tonight. >> >> >> -- >> Pardon the typos and autocorrect, small keyboard in use. >> Cheers, >> Cy Schubert >> FreeBSD UNIX: Web: >> http://www.FreeBSD.org >> >> The need of the many outweighs the greed of the few. >> > > Hmm so in other words, you have to set bgscan for each network entry you > want roaming? What are some good values for this? > > > From owner-freebsd-current@freebsd.org Fri Sep 20 01:25:53 2019 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 DA0D6EC250; Fri, 20 Sep 2019 01:25:53 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46ZGJ04yccz4WQ5; Fri, 20 Sep 2019 01:25:52 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id B7gBiazF9sAGkB7gCi2sVj; Thu, 19 Sep 2019 19:25:50 -0600 X-Authority-Analysis: v=2.3 cv=WeVylHpX c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=8nJEP1OIZ-IA:10 a=J70Eh1EUuV4A:10 a=6I5d2MoRAAAA:8 a=pGLkceISAAAA:8 a=9bHR7MVLAAAA:8 a=YxBL1-UpAAAA:8 a=PCqSUmN0ak2iMDnNgpYA:9 a=rhmp_ibcXPBzh3jT:21 a=LeJL6ysmZIOmxfNn:21 a=wPNLvfGTeEIA:10 a=IjZwj45LgO3ly-622nXo:22 a=I7KxNEAtLM9g1UmuDjRu:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTPS id C56F72B9; Thu, 19 Sep 2019 18:25:42 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id x8K1Pfpb085859; Thu, 19 Sep 2019 18:25:41 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id x8K1Pfhd085841; Thu, 19 Sep 2019 18:25:41 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201909200125.x8K1Pfhd085841@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Johannes Lundberg cc: Adrian Chadd , Cy Schubert , freebsd-current , "freebsd-wireless@freebsd.org" , Tom Jones , Poul-Henning Kamp Subject: Re: wlan can't discover known networks after relocating In-reply-to: <7938e5fa-67da-35fa-10d0-ee3004438df7@FreeBSD.org> References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> <6985.1568738188@critter.freebsd.dk> <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> <7938e5fa-67da-35fa-10d0-ee3004438df7@FreeBSD.org> Comments: In-reply-to Johannes Lundberg message dated "Thu, 19 Sep 2019 15:21:15 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Thu, 19 Sep 2019 18:25:41 -0700 X-CMAE-Envelope: MS4wfPIEwXSRbpa0Mt+RcoUh3R0rgNWSHrs4pSZ8oFcX7GkeG4+9kWeQ3EY8xPGgdZhwFH/OQHzoYf8cbswYHEaISNRMuRJGjEqHmYAQI94SjG3nRu7Nj3uD lgQ3TeU9Fk80OTcYjFPZtG3kMpzk7MbhvDdj2NfSVk6sAZueBM2Gj/GFPpQtrQZ74tzrAJazIyb3Ct63J0jUQ6ORrz+KzU6FcYwljcY5wiBgRN0S98dw3/Wm cv2h6IiJL2dewTqxTYH0Per4WAjOEgLIUbMxRlc7YKjl+M2JHxo9rPZzHPKNASS39/8H8UGDvQf7+Utr6BHuCg== X-Rspamd-Queue-Id: 46ZGJ04yccz4WQ5 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of cy.schubert@cschubert.com has no SPF policy when checking 64.59.134.9) smtp.mailfrom=cy.schubert@cschubert.com X-Spamd-Result: default: False [-2.47 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_XAW(0.00)[]; RCPT_COUNT_SEVEN(0.00)[7]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MIME_TRACE(0.00)[0:+]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; RCVD_COUNT_FIVE(0.00)[5]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[9.134.59.64.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.37)[ip: (-6.27), ipnet: 64.59.128.0/20(-3.08), asn: 6327(-2.39), country: CA(-0.09)]; R_SPF_NA(0.00)[]; FREEMAIL_CC(0.00)[gmail.com]; SUSPICIOUS_RECIPS(1.50)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 20 Sep 2019 01:25:53 -0000 In message <7938e5fa-67da-35fa-10d0-ee3004438df7@FreeBSD.org>, Johannes Lundber g writes: > > On 9/19/19 3:06 PM, Adrian Chadd wrote: > > So roaming in ifconfig/net80211 is what's set to manual. > > > > wpa_supplicant right now does RSSI threshold based roaming. All of the > > roaming and network preferences when wpa_supplicant is running is done > > in wpa_supplicant. That's where you have to look. Ideally > > wpa_supplicant would be triggering bgscan too periodically rather than > > only when the RSSI is low. > > > > > > > > -adrian > > > > > > On Thu, 19 Sep 2019 at 15:04, Cy Schubert > > wrote: > > > > On September 19, 2019 8:20:07 AM PDT, Adrian Chadd > > > wrote: > > >Roaming is done in wpa_supplicant when it's running.That's where the > > >smarts > > >need to be. :( > > > > > > > > > > > >-adrian > > > > > > > > >On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb > > > > > > > >wrote: > > > > > >> On 19 Sep 2019, at 12:28, Tom Jones wrote: > > >> > > >> Hi, > > >> > > >> freebsd-wireless might be a better list for all this .. > > >> > > >> > > >> > On Tue, Sep 17, 2019 at 04:36:28PM +0000, Poul-Henning Kamp > > wrote: > > >> >> -------- > > >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org>, > > >> >> Johannes Lundber > > >> >> g writes: > > >> >> > > >> >>> For a long time now I have had this problem with iwm and wlan0. > > >> >>> Whenever > > >> >>> I move between work and home it won't reconnect > > automatically and > > >I > > >> >>> have > > >> >>> to do wlan0 scan manually for it to pick up the different > > >network. > > >> >> > > >> >> I suffer from the dreaded "reason=0" when I move inside my > > house: > > >> >> > > >> >>      > scan > > >> >>      OK > > >> >>      <3>CTRL-EVENT-SCAN-RESULTS > > >> >>      <3>Trying to associate with 6c:3b:6b:3d:a2:e9 > > >(SSID='Palombia' > > >> >> freq=2452 MHz) > > >> >>      <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason > =0 > > >> >>      <3>CTRL-EVENT-SCAN-RESULTS > > >> >>      <3>Trying to associate with 6c:3b:6b:ab:ce:d4 > > >(SSID='Palombia' > > >> >> freq=2412 MHz) > > >> >>      <3>Associated with 6c:3b:6b:ab:ce:d4 > > >> >> > > >> >> a2:e9 is the loudest AP here in my office, but my I have been in > > >the > > >> >> other end of the house iwn consistently fails to associate > > with it > > >> >> and > > >> >> and keeps picking the weaker AP in the far end. > > >> >> > > >> >> Eventually (hours!) it disconnects from the weaker ap, also with > > >> >> "reason=0" and gets it right: > > >> >> > > >> >>      <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 > > >[GTK=CCMP] > > >> >>      <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason > =0 > > >> >>      <3>CTRL-EVENT-SCAN-RESULTS > > >> >>      <3>Trying to associate with 6c:3b:6b:3d:a2:e9 > > >(SSID='Palombia' > > >> >> freq=2452 MHz) > > >> >>      <3>Associated with 6c:3b:6b:3d:a2:e9 > > >> >>      <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 > > >[PTK=CCMP > > >> >> GTK=CCMP] > > >> >>      <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 > > >> completed > > >> >> [id=3 id_str=] > > >> >>      <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 > > >[GTK=CCMP] > > >> >> > > >> >> And yes, working roaming would be nice too... > > >> > > > >> > I have the problem that when roaming networks become disabled > > >> > > > >> >       $ wpa_cli > > >> >       Selected interface 'wlan0' > > >> > > > >> >       Interactive mode > > >> > > > >> >       > list_networks > > >> >       network id / ssid / bssid / flags > > >> >       0       network1        any     [CURRENT] > > >> >       1       network2 any    [DISABLED] > > >> >       2       network3 any    [DISABLED] > > >> >       3       network4 any    [DISABLED] > > >> >       4       network5 any    [DISABLED] > > >> >       Selected interface 'wlan0' > > >> > > > >> > > > >> > I address this by doing network_enable x in wpa_cli and it all > > >comes > > >> > back. I asked Adrian about this in the past, but it needs some > > >> > debugging > > >> > to pin down. > > >> > > >> > > >> Is this iwm(4) as well in your case or another card? > > >> > > >> /bz > > >> _______________________________________________ > > >> freebsd-wireless@freebsd.org > > mailing list > > >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > >> To unsubscribe, send any mail to > > >"freebsd-wireless-unsubscribe@freebsd.org > > > > >> " > > >> > > >_______________________________________________ > > >freebsd-current@freebsd.org > > mailing list > > >https://lists.freebsd.org/mailman/listinfo/freebsd-current > > >To unsubscribe, send any mail to > > >"freebsd-current-unsubscribe@freebsd.org > > " > > > > With wpa_supplicant running roaming is set to manual. Bgscan > > should be enabled.  > > > > At home we have two n (and 2 g) wifi networks. When powering off > > one ap it connects to the other (in addition to using lagg to > > failover from ethernet to wifi and back). > > > > Your wpa_supplicant should contain each ssid you intend to use. A > > wildcard can be used for open networks. > > > > It's a while since I've tested this functionality but I can test > > again when I get home tonight. > > > > > > -- > > Pardon the typos and autocorrect, small keyboard in use. > > Cheers, > > Cy Schubert > > > > FreeBSD UNIX: Web: http://www.FreeBSD.org > > > >         The need of the many outweighs the greed of the few. > > > > Hmm so in other words, you have to set bgscan for each network entry you > want roaming? What are some good values for this? Just tested here. It worked after a short delay, with a not-so-young laptop with iwn. wlan0: flags=8843 metric 0 mtu 1500 ether 20:NN:NN:NN:NN:NN groups: wlan ssid "BBBBBBBB" channel 1 (2412 MHz 11g ht/20) bssid 78:BB:BB:BB:BB:BB regdomain FCC country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 30 bmiss 120 scanvalid 16959 protmode CTS ampdulimit 64k -amsdutx amsdurx shortgi -stbc -ldpc wme roaming MANUAL media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated nd6 options=29 And the gory details: Sep 19 17:21:35 slippy wpa_supplicant[381]: wlan0: CTRL-EVENT-DISCONNECTED bssid=a6:NN:NN:NN:NN:NN reason=0 Sep 19 17:21:35 slippy wpa_supplicant[381]: wlan0: Trying to associate with a6:NN:NN:NN:NN:NN (SSID='AAA' freq=2462 MHz) Sep 19 17:21:35 slippy wpa_supplicant[381]: Failed to add supported operating classes IE Sep 19 17:21:35 slippy wpa_supplicant[381]: wlan0: Associated with a6:NN:NN:NN:NN:NN Sep 19 17:21:45 slippy wpa_supplicant[381]: wlan0: Authentication with a6:08:ea:9c:a0:84 timed out. Sep 19 17:21:45 slippy wpa_supplicant[381]: wlan0: CTRL-EVENT-DISCONNECTED bssid=a6:NN:NN:NN:NN:NN reason=3 locally_generated=1 Sep 19 17:21:47 slippy wpa_supplicant[381]: wlan0: Trying to associate with 78:NN:NN:NN:NN:NN (SSID='BBBBBBBBB' freq=2412 MHz) Sep 19 17:21:47 slippy wpa_supplicant[381]: Failed to add supported operating classes IE Sep 19 17:21:47 slippy wpa_supplicant[381]: wlan0: Associated with 78:NN:NN:NN:NN:NN Sep 19 17:21:48 slippy wpa_supplicant[381]: wlan0: WPA: Key negotiation completed with 78:NN:NN:NN:NN:NN [PTK=CCMP GTK=CCMP] Sep 19 17:21:48 slippy wpa_supplicant[381]: wlan0: CTRL-EVENT-CONNECTED - Connection to 78:NN:NN:NN:NN:NN completed [id=7 id_str=] AAA is my cell phone. the B's are $JOB. The relevant parts of my wpa_supplicant.conf: network={ ssid="AAA" priority=6 proto=RSN WPA key_mgmt=WPA-PSK pairwise=CCMP group=CCMP psk="x" } network={ ssid="BBBBBBBBB" scan_ssid=1 priority=5 proto=RSN WPA key_mgmt=WPA-PSK pairwise=CCMP TKIP group=CCMP TKIP psk="y" } #Wildcard match for SSID (plaintext APs only). This example select any #open AP regardless of its SSID. network={ priority=0 disabled=1 key_mgmt=NONE } Hope this helps. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Fri Sep 20 02:02:09 2019 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 0BB75ED5F3; Fri, 20 Sep 2019 02:02:09 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-oi1-x236.google.com (mail-oi1-x236.google.com [IPv6:2607:f8b0:4864:20::236]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46ZH5r20RGz4XrQ; Fri, 20 Sep 2019 02:02:08 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-oi1-x236.google.com with SMTP id o205so430156oib.12; Thu, 19 Sep 2019 19:02:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Q/aCeBhy8+CmpGefGBpk4JbCoMGRuLjRSofxb4FTEF4=; b=GaIXjxmbLQfHzjMgRONQ5ubDTaY2cskamB0GwIIyTMJhzI7l0E8IWkChV6ps5DvzHL 7dYYbpmFVa4WnfxWwyXfc2WOswKuhDOsvKS3U08SjNhUra0HHBcHnpnVzmVJY49sRv6g gzyh30V5H++q0ao+x9AINqJgDSa73qx+THiT/aCfdKAjluoSVWZRoz329cYzAkgPkZ9R /g8dB+GuMBkAPE+//qBXN4xN36zJpaO1iCUpTM5VMFa4FebkYRV1X1dFwpgd0g9XioGt zCon4qhHK+/9NGHhlDA2f0sOi0hVcta03wYwmosRta9Y9xK2Bq1d1tyR4s7kaRmC7ga/ Jmag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Q/aCeBhy8+CmpGefGBpk4JbCoMGRuLjRSofxb4FTEF4=; b=Vt5V+4g2gc/b3HqyKboOw5z1PMNvNAptN/WfEokEYZYA1bmIeboSpkdO1+CbWNpCbt /xne3erCjBwDtmP86r1iAuB72fDN+idsJW+7zimAGkkCQruAgT6lm4yd21dj+vmj9bSp taQYLeDcjWf78ppj5ex+HIpdCzViD0wVcgYlxrErJK8snpWlH4umyT9ipNehALIzurdK CuXJOriay1ea2+G5pVIY8qgUUmQTHZkn6fIRxCs4EWkX7e0LtGNdyzeTi7fBn651bk27 rIGG/I4EO1/ecZUXm9opnKnjpq1px6QAT/BFPd743mh52HHy5UndfQIE8TZ9zCX0qll7 AGjw== X-Gm-Message-State: APjAAAWG4nJxq1XakgSVmBXK1bJ1juLQydelGn6Bb2/NV0XikIFgPW6J M454khQhLbDPSRsS2N9zef3lnI2KFx0S2wvFdW4= X-Google-Smtp-Source: APXvYqyWED15FSLq8gSjLbKZTVsO9usNnJnTWqWszoh/u9Oi1LM11Mx5XCSdoK3Eop5gGONcxowH2+ayRXW2rPOs+Hc= X-Received: by 2002:aca:fccb:: with SMTP id a194mr917939oii.52.1568944926781; Thu, 19 Sep 2019 19:02:06 -0700 (PDT) MIME-Version: 1.0 References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> <6985.1568738188@critter.freebsd.dk> <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> <7938e5fa-67da-35fa-10d0-ee3004438df7@FreeBSD.org> <201909200125.x8K1Pfhd085841@slippy.cwsent.com> In-Reply-To: <201909200125.x8K1Pfhd085841@slippy.cwsent.com> From: Johannes Lundberg Date: Thu, 19 Sep 2019 19:01:55 -0700 Message-ID: Subject: Re: wlan can't discover known networks after relocating To: Cy Schubert Cc: Adrian Chadd , Cy Schubert , Johannes Lundberg , Poul-Henning Kamp , Tom Jones , freebsd-current , "freebsd-wireless@freebsd.org" X-Rspamd-Queue-Id: 46ZH5r20RGz4XrQ X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=GaIXjxmb; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of johalun0@gmail.com designates 2607:f8b0:4864:20::236 as permitted sender) smtp.mailfrom=johalun0@gmail.com X-Spamd-Result: default: False [-1.50 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCPT_COUNT_SEVEN(0.00)[8]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-8.86), ipnet: 2607:f8b0::/32(-2.66), asn: 15169(-2.21), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[6.3.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; SUSPICIOUS_RECIPS(1.50)[]; FREEMAIL_CC(0.00)[gmail.com] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 20 Sep 2019 02:02:09 -0000 Tested today with bgscan added. Didn=E2=80=99t connect to home network unti= l I manually run ifconfig wlan0 scan. Again, this is with failover lagg. It did however realize I wasn=E2=80=99t at the office anymore and the ssid = field was empty in ifconfig output. Sometimes it stays the same long after I leave the network. On Thu, Sep 19, 2019 at 18:25 Cy Schubert wrote= : > In message <7938e5fa-67da-35fa-10d0-ee3004438df7@FreeBSD.org>, Johannes > Lundber > g writes: > > > > On 9/19/19 3:06 PM, Adrian Chadd wrote: > > > So roaming in ifconfig/net80211 is what's set to manual. > > > > > > wpa_supplicant right now does RSSI threshold based roaming. All of th= e > > > roaming and network preferences when wpa_supplicant is running is don= e > > > in wpa_supplicant. That's where you have to look. Ideally > > > wpa_supplicant would be triggering bgscan too periodically rather tha= n > > > only when the RSSI is low. > > > > > > > > > > > > -adrian > > > > > > > > > On Thu, 19 Sep 2019 at 15:04, Cy Schubert > > > wrote: > > > > > > On September 19, 2019 8:20:07 AM PDT, Adrian Chadd > > > > wrote: > > > >Roaming is done in wpa_supplicant when it's running.That's where > the > > > >smarts > > > >need to be. :( > > > > > > > > > > > > > > > >-adrian > > > > > > > > > > > >On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb > > > > > > > > > > >wrote: > > > > > > > >> On 19 Sep 2019, at 12:28, Tom Jones wrote: > > > >> > > > >> Hi, > > > >> > > > >> freebsd-wireless might be a better list for all this .. > > > >> > > > >> > > > >> > On Tue, Sep 17, 2019 at 04:36:28PM +0000, Poul-Henning Kamp > > > wrote: > > > >> >> -------- > > > >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.or= g > >, > > > >> >> Johannes Lundber > > > >> >> g writes: > > > >> >> > > > >> >>> For a long time now I have had this problem with iwm and > wlan0. > > > >> >>> Whenever > > > >> >>> I move between work and home it won't reconnect > > > automatically and > > > >I > > > >> >>> have > > > >> >>> to do wlan0 scan manually for it to pick up the different > > > >network. > > > >> >> > > > >> >> I suffer from the dreaded "reason=3D0" when I move inside m= y > > > house: > > > >> >> > > > >> >> > scan > > > >> >> OK > > > >> >> <3>CTRL-EVENT-SCAN-RESULTS > > > >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 > > > >(SSID=3D'Palombia' > > > >> >> freq=3D2452 MHz) > > > >> >> <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:3d:a2:e9 > reason > > =3D0 > > > >> >> <3>CTRL-EVENT-SCAN-RESULTS > > > >> >> <3>Trying to associate with 6c:3b:6b:ab:ce:d4 > > > >(SSID=3D'Palombia' > > > >> >> freq=3D2412 MHz) > > > >> >> <3>Associated with 6c:3b:6b:ab:ce:d4 > > > >> >> > > > >> >> a2:e9 is the loudest AP here in my office, but my I have > been in > > > >the > > > >> >> other end of the house iwn consistently fails to associate > > > with it > > > >> >> and > > > >> >> and keeps picking the weaker AP in the far end. > > > >> >> > > > >> >> Eventually (hours!) it disconnects from the weaker ap, also > with > > > >> >> "reason=3D0" and gets it right: > > > >> >> > > > >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d= 4 > > > >[GTK=3DCCMP] > > > >> >> <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:ab:ce:d4 > reason > > =3D0 > > > >> >> <3>CTRL-EVENT-SCAN-RESULTS > > > >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 > > > >(SSID=3D'Palombia' > > > >> >> freq=3D2452 MHz) > > > >> >> <3>Associated with 6c:3b:6b:3d:a2:e9 > > > >> >> <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:= e9 > > > >[PTK=3DCCMP > > > >> >> GTK=3DCCMP] > > > >> >> <3>CTRL-EVENT-CONNECTED - Connection to > 6c:3b:6b:3d:a2:e9 > > > >> completed > > > >> >> [id=3D3 id_str=3D] > > > >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e= 9 > > > >[GTK=3DCCMP] > > > >> >> > > > >> >> And yes, working roaming would be nice too... > > > >> > > > > >> > I have the problem that when roaming networks become disable= d > > > >> > > > > >> > $ wpa_cli > > > >> > Selected interface 'wlan0' > > > >> > > > > >> > Interactive mode > > > >> > > > > >> > > list_networks > > > >> > network id / ssid / bssid / flags > > > >> > 0 network1 any [CURRENT] > > > >> > 1 network2 any [DISABLED] > > > >> > 2 network3 any [DISABLED] > > > >> > 3 network4 any [DISABLED] > > > >> > 4 network5 any [DISABLED] > > > >> > Selected interface 'wlan0' > > > >> > > > > >> > > > > >> > I address this by doing network_enable x in wpa_cli and it a= ll > > > >comes > > > >> > back. I asked Adrian about this in the past, but it needs so= me > > > >> > debugging > > > >> > to pin down. > > > >> > > > >> > > > >> Is this iwm(4) as well in your case or another card? > > > >> > > > >> /bz > > > >> _______________________________________________ > > > >> freebsd-wireless@freebsd.org > > > mailing list > > > >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > > >> To unsubscribe, send any mail to > > > >"freebsd-wireless-unsubscribe@freebsd.org > > > > > > >> " > > > >> > > > >_______________________________________________ > > > >freebsd-current@freebsd.org > > > mailing list > > > >https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > >To unsubscribe, send any mail to > > > >"freebsd-current-unsubscribe@freebsd.org > > > " > > > > > > With wpa_supplicant running roaming is set to manual. Bgscan > > > should be enabled. > > > > > > At home we have two n (and 2 g) wifi networks. When powering off > > > one ap it connects to the other (in addition to using lagg to > > > failover from ethernet to wifi and back). > > > > > > Your wpa_supplicant should contain each ssid you intend to use. A > > > wildcard can be used for open networks. > > > > > > It's a while since I've tested this functionality but I can test > > > again when I get home tonight. > > > > > > > > > -- > > > Pardon the typos and autocorrect, small keyboard in use. > > > Cheers, > > > Cy Schubert > > > > > > FreeBSD UNIX: Web: http://www.FreeBSD.org > > > > > > The need of the many outweighs the greed of the few. > > > > > > > Hmm so in other words, you have to set bgscan for each network entry yo= u > > want roaming? What are some good values for this? > > Just tested here. It worked after a short delay, with a not-so-young > laptop > with iwn. > > wlan0: flags=3D8843 metric 0 mtu = 1500 > ether 20:NN:NN:NN:NN:NN > groups: wlan > ssid "BBBBBBBB" channel 1 (2412 MHz 11g ht/20) bssid > 78:BB:BB:BB:BB:BB > regdomain FCC country US authmode WPA2/802.11i privacy ON > deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 30 > bmiss 120 scanvalid 16959 protmode CTS ampdulimit 64k -amsdutx > amsdurx > shortgi -stbc -ldpc wme roaming MANUAL > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > status: associated > nd6 options=3D29 > > And the gory details: > > Sep 19 17:21:35 slippy wpa_supplicant[381]: wlan0: CTRL-EVENT-DISCONNECTE= D > bssid=3Da6:NN:NN:NN:NN:NN reason=3D0 > Sep 19 17:21:35 slippy wpa_supplicant[381]: wlan0: Trying to associate > with > a6:NN:NN:NN:NN:NN (SSID=3D'AAA' freq=3D2462 MHz) > Sep 19 17:21:35 slippy wpa_supplicant[381]: Failed to add supported > operating classes IE > Sep 19 17:21:35 slippy wpa_supplicant[381]: wlan0: Associated with > a6:NN:NN:NN:NN:NN > Sep 19 17:21:45 slippy wpa_supplicant[381]: wlan0: Authentication with > a6:08:ea:9c:a0:84 timed out. > Sep 19 17:21:45 slippy wpa_supplicant[381]: wlan0: CTRL-EVENT-DISCONNECTE= D > bssid=3Da6:NN:NN:NN:NN:NN reason=3D3 locally_generated=3D1 > Sep 19 17:21:47 slippy wpa_supplicant[381]: wlan0: Trying to associate > with > 78:NN:NN:NN:NN:NN (SSID=3D'BBBBBBBBB' freq=3D2412 MHz) > Sep 19 17:21:47 slippy wpa_supplicant[381]: Failed to add supported > operating classes IE > Sep 19 17:21:47 slippy wpa_supplicant[381]: wlan0: Associated with > 78:NN:NN:NN:NN:NN > Sep 19 17:21:48 slippy wpa_supplicant[381]: wlan0: WPA: Key negotiation > completed with 78:NN:NN:NN:NN:NN [PTK=3DCCMP GTK=3DCCMP] > Sep 19 17:21:48 slippy wpa_supplicant[381]: wlan0: CTRL-EVENT-CONNECTED - > Connection to 78:NN:NN:NN:NN:NN completed [id=3D7 id_str=3D] > > AAA is my cell phone. the B's are $JOB. > > The relevant parts of my wpa_supplicant.conf: > > network=3D{ > ssid=3D"AAA" > priority=3D6 > proto=3DRSN WPA > key_mgmt=3DWPA-PSK > pairwise=3DCCMP > group=3DCCMP > psk=3D"x" > } > > network=3D{ > ssid=3D"BBBBBBBBB" > scan_ssid=3D1 > priority=3D5 > proto=3DRSN WPA > key_mgmt=3DWPA-PSK > pairwise=3DCCMP TKIP > group=3DCCMP TKIP > psk=3D"y" > } > > #Wildcard match for SSID (plaintext APs only). This example select any > #open AP regardless of its SSID. > network=3D{ > priority=3D0 > disabled=3D1 > key_mgmt=3DNONE > } > > Hope this helps. > > > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: http://www.FreeBSD.org > > The need of the many outweighs the greed of the few. > > > From owner-freebsd-current@freebsd.org Fri Sep 20 02:30:11 2019 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 C504FEDECD; Fri, 20 Sep 2019 02:30:11 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46ZHkB0qXLz4YkN; Fri, 20 Sep 2019 02:30:09 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id B8gQix0CGIhW9B8gRibiLE; Thu, 19 Sep 2019 20:30:08 -0600 X-Authority-Analysis: v=2.3 cv=FcFJO626 c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=J70Eh1EUuV4A:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=pGLkceISAAAA:8 a=9bHR7MVLAAAA:8 a=o4W7w11LAAAA:8 a=kUCByv9wAAAA:8 a=IIX2BFdiAAAA:8 a=NMM7OKYrAAAA:8 a=0VOg8hKvAAAA:8 a=vUPWEWiMAAAA:8 a=SLG1KRGDAAAA:8 a=xdb5K4IfAAAA:8 a=dliLc1HNdIQPMY3R8XkA:9 a=-4mYsfVcJZb0LWw9:21 a=SqWaXOqbkYc2v_37:21 a=ifW8yVZGP7kgUp4i:21 a=CjuIK1q_8ugA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=I7KxNEAtLM9g1UmuDjRu:22 a=PaFTRifc8KBnsvTAljXf:22 a=bu_5hG6eGWxBxPYBRUjp:22 a=rHg00LAlvzXsuODty-Nv:22 a=isrg6BwTYk6I_F0B0DtW:22 a=I-efbNKAaAt4Mg394dr-:22 a=s3Yi14Of9AgBIP63TAoC:22 a=-TBaU1e9WpdkKBzYXnwo:22 a=AuRjBy9VhmoZW1Pfxjoc:22 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTPS id A8BFCD5; Thu, 19 Sep 2019 19:30:05 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id x8K2U5uA074059; Thu, 19 Sep 2019 19:30:05 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id x8K2U4DS074056; Thu, 19 Sep 2019 19:30:04 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201909200230.x8K2U4DS074056@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Johannes Lundberg cc: Cy Schubert , Adrian Chadd , Cy Schubert , Johannes Lundberg , Poul-Henning Kamp , Tom Jones , freebsd-current , "freebsd-wireless@freebsd.org" Subject: Re: wlan can't discover known networks after relocating In-reply-to: References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> <6985.1568738188@critter.freebsd.dk> <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> <7938e5fa-67da-35fa-10d0-ee3004438df7@FreeBSD.org> <201909200125.x8K1Pfhd085841@slippy.cwsent.com> Comments: In-reply-to Johannes Lundberg message dated "Thu, 19 Sep 2019 19:01:55 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Sep 2019 19:30:04 -0700 X-CMAE-Envelope: MS4wfKjwzbhwGK7BKtKIJgBKb/6GU6P6ZaUxpQVa8isNDoIPLqLsdUwNTBLriCPLhbFiNnJ+Znleic2vxo9d/IaSIdmjBjMRuJ/kE57uljvgjVCEm85aAzd4 PJWt8NSu6UbUrJhL7olP/uNkuAxrLYjQbEou2okpnKICY76EFIJwrA0/ik4kaaqrYc1liNM4idW+0YzZqJklHBjfbr7b1peKLZpR31+z3oYCCzdQQQ4D7FiL 8I9omKy60D1Nkw4qDTYSTkeGMd1gRmfh/C9ROvJQzbCYeoI2+9u93b+YBQ0QSfof8hHwDgFP/oHdK3WHqtqPHA== X-Rspamd-Queue-Id: 46ZHkB0qXLz4YkN X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of cy.schubert@cschubert.com has no SPF policy when checking 64.59.136.137) smtp.mailfrom=cy.schubert@cschubert.com X-Spamd-Result: default: False [-2.38 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_XAW(0.00)[]; RCPT_COUNT_SEVEN(0.00)[9]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-2.28)[ip: (-5.86), ipnet: 64.59.128.0/20(-3.08), asn: 6327(-2.39), country: CA(-0.09)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_COUNT_FIVE(0.00)[5]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[137.136.59.64.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; SUSPICIOUS_RECIPS(1.50)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 20 Sep 2019 02:30:11 -0000 In message , Johannes Lundberg writes: > --0000000000000875960592f275a3 > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > Tested today with bgscan added. Didn=E2=80=99t connect to home network unti= > l I > manually run ifconfig wlan0 scan. > Again, this is with failover lagg. I use failover lagg too. I'm still at $JOB so no ethernet for my personal FreeBSD laptop here, but that works as well, at home. > > It did however realize I wasn't at the office anymore and the ssid = > field > was empty in ifconfig output. Sometimes it stays the same long after I > leave the network. Do you suspend/resume your laptop? -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. > > > On Thu, Sep 19, 2019 at 18:25 Cy Schubert wrote= > : > > > In message <7938e5fa-67da-35fa-10d0-ee3004438df7@FreeBSD.org>, Johannes > > Lundber > > g writes: > > > > > > On 9/19/19 3:06 PM, Adrian Chadd wrote: > > > > So roaming in ifconfig/net80211 is what's set to manual. > > > > > > > > wpa_supplicant right now does RSSI threshold based roaming. All of th= > e > > > > roaming and network preferences when wpa_supplicant is running is don= > e > > > > in wpa_supplicant. That's where you have to look. Ideally > > > > wpa_supplicant would be triggering bgscan too periodically rather tha= > n > > > > only when the RSSI is low. > > > > > > > > > > > > > > > > -adrian > > > > > > > > > > > > On Thu, 19 Sep 2019 at 15:04, Cy Schubert > > > > wrote: > > > > > > > > On September 19, 2019 8:20:07 AM PDT, Adrian Chadd > > > > > wrote: > > > > >Roaming is done in wpa_supplicant when it's running.That's where > > the > > > > >smarts > > > > >need to be. :( > > > > > > > > > > > > > > > > > > > >-adrian > > > > > > > > > > > > > > >On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb > > > > > > > > > > > > > >wrote: > > > > > > > > > >> On 19 Sep 2019, at 12:28, Tom Jones wrote: > > > > >> > > > > >> Hi, > > > > >> > > > > >> freebsd-wireless might be a better list for all this .. > > > > >> > > > > >> > > > > >> > On Tue, Sep 17, 2019 at 04:36:28PM +0000, Poul-Henning Kamp > > > > wrote: > > > > >> >> -------- > > > > >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.or= > g > > >, > > > > >> >> Johannes Lundber > > > > >> >> g writes: > > > > >> >> > > > > >> >>> For a long time now I have had this problem with iwm and > > wlan0. > > > > >> >>> Whenever > > > > >> >>> I move between work and home it won't reconnect > > > > automatically and > > > > >I > > > > >> >>> have > > > > >> >>> to do wlan0 scan manually for it to pick up the different > > > > >network. > > > > >> >> > > > > >> >> I suffer from the dreaded "reason=3D0" when I move inside m= > y > > > > house: > > > > >> >> > > > > >> >> > scan > > > > >> >> OK > > > > >> >> <3>CTRL-EVENT-SCAN-RESULTS > > > > >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 > > > > >(SSID=3D'Palombia' > > > > >> >> freq=3D2452 MHz) > > > > >> >> <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:3d:a2:e9 > > reason > > > =3D0 > > > > >> >> <3>CTRL-EVENT-SCAN-RESULTS > > > > >> >> <3>Trying to associate with 6c:3b:6b:ab:ce:d4 > > > > >(SSID=3D'Palombia' > > > > >> >> freq=3D2412 MHz) > > > > >> >> <3>Associated with 6c:3b:6b:ab:ce:d4 > > > > >> >> > > > > >> >> a2:e9 is the loudest AP here in my office, but my I have > > been in > > > > >the > > > > >> >> other end of the house iwn consistently fails to associate > > > > with it > > > > >> >> and > > > > >> >> and keeps picking the weaker AP in the far end. > > > > >> >> > > > > >> >> Eventually (hours!) it disconnects from the weaker ap, also > > with > > > > >> >> "reason=3D0" and gets it right: > > > > >> >> > > > > >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d= > 4 > > > > >[GTK=3DCCMP] > > > > >> >> <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:ab:ce:d4 > > reason > > > =3D0 > > > > >> >> <3>CTRL-EVENT-SCAN-RESULTS > > > > >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 > > > > >(SSID=3D'Palombia' > > > > >> >> freq=3D2452 MHz) > > > > >> >> <3>Associated with 6c:3b:6b:3d:a2:e9 > > > > >> >> <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:= > e9 > > > > >[PTK=3DCCMP > > > > >> >> GTK=3DCCMP] > > > > >> >> <3>CTRL-EVENT-CONNECTED - Connection to > > 6c:3b:6b:3d:a2:e9 > > > > >> completed > > > > >> >> [id=3D3 id_str=3D] > > > > >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e= > 9 > > > > >[GTK=3DCCMP] > > > > >> >> > > > > >> >> And yes, working roaming would be nice too... > > > > >> > > > > > >> > I have the problem that when roaming networks become disable= > d > > > > >> > > > > > >> > $ wpa_cli > > > > >> > Selected interface 'wlan0' > > > > >> > > > > > >> > Interactive mode > > > > >> > > > > > >> > > list_networks > > > > >> > network id / ssid / bssid / flags > > > > >> > 0 network1 any [CURRENT] > > > > >> > 1 network2 any [DISABLED] > > > > >> > 2 network3 any [DISABLED] > > > > >> > 3 network4 any [DISABLED] > > > > >> > 4 network5 any [DISABLED] > > > > >> > Selected interface 'wlan0' > > > > >> > > > > > >> > > > > > >> > I address this by doing network_enable x in wpa_cli and it a= > ll > > > > >comes > > > > >> > back. I asked Adrian about this in the past, but it needs so= > me > > > > >> > debugging > > > > >> > to pin down. > > > > >> > > > > >> > > > > >> Is this iwm(4) as well in your case or another card? > > > > >> > > > > >> /bz > > > > >> _______________________________________________ > > > > >> freebsd-wireless@freebsd.org > > > > mailing list > > > > >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > > > >> To unsubscribe, send any mail to > > > > >"freebsd-wireless-unsubscribe@freebsd.org > > > > > > > > >> " > > > > >> > > > > >_______________________________________________ > > > > >freebsd-current@freebsd.org > > > > mailing list > > > > >https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > >To unsubscribe, send any mail to > > > > >"freebsd-current-unsubscribe@freebsd.org > > > > " > > > > > > > > With wpa_supplicant running roaming is set to manual. Bgscan > > > > should be enabled. > > > > > > > > At home we have two n (and 2 g) wifi networks. When powering off > > > > one ap it connects to the other (in addition to using lagg to > > > > failover from ethernet to wifi and back). > > > > > > > > Your wpa_supplicant should contain each ssid you intend to use. A > > > > wildcard can be used for open networks. > > > > > > > > It's a while since I've tested this functionality but I can test > > > > again when I get home tonight. > > > > > > > > > > > > -- > > > > Pardon the typos and autocorrect, small keyboard in use. > > > > Cheers, > > > > Cy Schubert > > > > > > > > FreeBSD UNIX: Web: http://www.FreeBSD.org > > > > > > > > The need of the many outweighs the greed of the few. > > > > > > > > > > Hmm so in other words, you have to set bgscan for each network entry yo= > u > > > want roaming? What are some good values for this? > > > > Just tested here. It worked after a short delay, with a not-so-young > > laptop > > with iwn. > > > > wlan0: flags=3D8843 metric 0 mtu = > 1500 > > ether 20:NN:NN:NN:NN:NN > > groups: wlan > > ssid "BBBBBBBB" channel 1 (2412 MHz 11g ht/20) bssid > > 78:BB:BB:BB:BB:BB > > regdomain FCC country US authmode WPA2/802.11i privacy ON > > deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 30 > > bmiss 120 scanvalid 16959 protmode CTS ampdulimit 64k -amsdutx > > amsdurx > > shortgi -stbc -ldpc wme roaming MANUAL > > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > > status: associated > > nd6 options=3D29 > > > > And the gory details: > > > > Sep 19 17:21:35 slippy wpa_supplicant[381]: wlan0: CTRL-EVENT-DISCONNECTE= > D > > bssid=3Da6:NN:NN:NN:NN:NN reason=3D0 > > Sep 19 17:21:35 slippy wpa_supplicant[381]: wlan0: Trying to associate > > with > > a6:NN:NN:NN:NN:NN (SSID=3D'AAA' freq=3D2462 MHz) > > Sep 19 17:21:35 slippy wpa_supplicant[381]: Failed to add supported > > operating classes IE > > Sep 19 17:21:35 slippy wpa_supplicant[381]: wlan0: Associated with > > a6:NN:NN:NN:NN:NN > > Sep 19 17:21:45 slippy wpa_supplicant[381]: wlan0: Authentication with > > a6:08:ea:9c:a0:84 timed out. > > Sep 19 17:21:45 slippy wpa_supplicant[381]: wlan0: CTRL-EVENT-DISCONNECTE= > D > > bssid=3Da6:NN:NN:NN:NN:NN reason=3D3 locally_generated=3D1 > > Sep 19 17:21:47 slippy wpa_supplicant[381]: wlan0: Trying to associate > > with > > 78:NN:NN:NN:NN:NN (SSID=3D'BBBBBBBBB' freq=3D2412 MHz) > > Sep 19 17:21:47 slippy wpa_supplicant[381]: Failed to add supported > > operating classes IE > > Sep 19 17:21:47 slippy wpa_supplicant[381]: wlan0: Associated with > > 78:NN:NN:NN:NN:NN > > Sep 19 17:21:48 slippy wpa_supplicant[381]: wlan0: WPA: Key negotiation > > completed with 78:NN:NN:NN:NN:NN [PTK=3DCCMP GTK=3DCCMP] > > Sep 19 17:21:48 slippy wpa_supplicant[381]: wlan0: CTRL-EVENT-CONNECTED - > > Connection to 78:NN:NN:NN:NN:NN completed [id=3D7 id_str=3D] > > > > AAA is my cell phone. the B's are $JOB. > > > > The relevant parts of my wpa_supplicant.conf: > > > > network=3D{ > > ssid=3D"AAA" > > priority=3D6 > > proto=3DRSN WPA > > key_mgmt=3DWPA-PSK > > pairwise=3DCCMP > > group=3DCCMP > > psk=3D"x" > > } > > > > network=3D{ > > ssid=3D"BBBBBBBBB" > > scan_ssid=3D1 > > priority=3D5 > > proto=3DRSN WPA > > key_mgmt=3DWPA-PSK > > pairwise=3DCCMP TKIP > > group=3DCCMP TKIP > > psk=3D"y" > > } > > > > #Wildcard match for SSID (plaintext APs only). This example select any > > #open AP regardless of its SSID. > > network=3D{ > > priority=3D0 > > disabled=3D1 > > key_mgmt=3DNONE > > } > > > > Hope this helps. > > > > > > -- > > Cheers, > > Cy Schubert > > FreeBSD UNIX: Web: http://www.FreeBSD.org > > > > The need of the many outweighs the greed of the few. > > > > > > > > --0000000000000875960592f275a3 > Content-Type: text/html; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > >
Tested today with bgscan added. Didn=E2=80=99t conne= > ct to home network until I manually run ifconfig wlan0 scan.=C2=A0
iv>
Again, this is with failover lagg.=C2=A0
=3D"auto">
It did however realize I wasn=E2=80= > =99t at the office anymore and the ssid field was empty in ifconfig output.= > Sometimes it stays the same long after I leave the network.=C2=A0
v dir=3D"auto">

r" class=3D"gmail_attr">On Thu, Sep 19, 2019 at 18:25 Cy Schubert < ef=3D"mailto:Cy.Schubert@cschubert.com">Cy.Schubert@cschubert.com> w= > rote:
;border-left:1px #ccc solid;padding-left:1ex">In message <7938e5fa-67da-= > 35fa-10d0-ee3004438df7@FreeBSD.org>, Johannes
> Lundber
> g writes:
> >
> > On 9/19/19 3:06 PM, Adrian Chadd wrote:
> > > So roaming in ifconfig/net80211 is what's set to manual.
> > >
> > > wpa_supplicant right now does RSSI threshold based roaming. All o= > f the
> > > roaming and network preferences when wpa_supplicant is running is= > done
> > > in wpa_supplicant. That's where you have to look. Ideally
> > > wpa_supplicant would be triggering bgscan too periodically rather= > than
> > > only when the RSSI is low.
> > >
> > >
> > >
> > > -adrian
> > >
> > >
> > > On Thu, 19 Sep 2019 at 15:04, Cy Schubert < y.schubert@gmail.com" target=3D"_blank">cy.schubert@gmail.com
> > > <mailto: ank">cy.schubert@gmail.com>> wrote:
> > >
> > >=C2=A0 =C2=A0 =C2=A0On September 19, 2019 8:20:07 AM PDT, Adrian C= > hadd
> > >=C2=A0 =C2=A0 =C2=A0< target=3D"_blank">adrian.chadd@gmail.com <mailto: drian.chadd@gmail.com" target=3D"_blank">adrian.chadd@gmail.com>>= > wrote:
> > >=C2=A0 =C2=A0 =C2=A0>Roaming is done in wpa_supplicant when it&= > #39;s running.That's where the
> > >=C2=A0 =C2=A0 =C2=A0>smarts
> > >=C2=A0 =C2=A0 =C2=A0>need to be. :(
> > >=C2=A0 =C2=A0 =C2=A0>
> > >=C2=A0 =C2=A0 =C2=A0>
> > >=C2=A0 =C2=A0 =C2=A0>
> > >=C2=A0 =C2=A0 =C2=A0>-adrian
> > >=C2=A0 =C2=A0 =C2=A0>
> > >=C2=A0 =C2=A0 =C2=A0>
> > >=C2=A0 =C2=A0 =C2=A0>On Thu, 19 Sep 2019 at 05:44, Bjoern A. Ze= > eb
> > >=C2=A0 =C2=A0 =C2=A0>< bbadoz.net" target=3D"_blank">bzeeb-lists@lists.zabbadoz.net
> > >=C2=A0 =C2=A0 =C2=A0<mailto: .zabbadoz.net" target=3D"_blank">bzeeb-lists@lists.zabbadoz.net>>= >
> > >=C2=A0 =C2=A0 =C2=A0>wrote:
> > >=C2=A0 =C2=A0 =C2=A0>
> > >=C2=A0 =C2=A0 =C2=A0>> On 19 Sep 2019, at 12:28, Tom Jones w= > rote:
> > >=C2=A0 =C2=A0 =C2=A0>>
> > >=C2=A0 =C2=A0 =C2=A0>> Hi,
> > >=C2=A0 =C2=A0 =C2=A0>>
> > >=C2=A0 =C2=A0 =C2=A0>> freebsd-wireless might be a better li= > st for all this ..
> > >=C2=A0 =C2=A0 =C2=A0>>
> > >=C2=A0 =C2=A0 =C2=A0>>
> > >=C2=A0 =C2=A0 =C2=A0>> > On Tue, Sep 17, 2019 at 04:36:28= > PM +0000, Poul-Henning Kamp
> > >=C2=A0 =C2=A0 =C2=A0wrote:
> > >=C2=A0 =C2=A0 =C2=A0>> >> --------
> > >=C2=A0 =C2=A0 =C2=A0>> >> In message <707bcd3f-fa6b= > -82eb-fa8f-09c4b800f477@FreeBSD.org>,
> > >=C2=A0 =C2=A0 =C2=A0>> >> Johannes Lundber
> > >=C2=A0 =C2=A0 =C2=A0>> >> g writes:
> > >=C2=A0 =C2=A0 =C2=A0>> >>
> > >=C2=A0 =C2=A0 =C2=A0>> >>> For a long time now I ha= > ve had this problem with iwm and wlan0.
> > >=C2=A0 =C2=A0 =C2=A0>> >>> Whenever
> > >=C2=A0 =C2=A0 =C2=A0>> >>> I move between work and = > home it won't reconnect
> > >=C2=A0 =C2=A0 =C2=A0automatically and
> > >=C2=A0 =C2=A0 =C2=A0>I
> > >=C2=A0 =C2=A0 =C2=A0>> >>> have
> > >=C2=A0 =C2=A0 =C2=A0>> >>> to do wlan0 scan manuall= > y for it to pick up the different
> > >=C2=A0 =C2=A0 =C2=A0>network.
> > >=C2=A0 =C2=A0 =C2=A0>> >>
> > >=C2=A0 =C2=A0 =C2=A0>> >> I suffer from the dreaded &q= > uot;reason=3D0" when I move inside my
> > >=C2=A0 =C2=A0 =C2=A0house:
> > >=C2=A0 =C2=A0 =C2=A0>> >>
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 > sca= > n
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 OK
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;CTRL-EVENT-SCAN-RESULTS
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;Trying to associate with 6c:3b:6b:3d:a2:e9
> > >=C2=A0 =C2=A0 =C2=A0>(SSID=3D'Palombia'
> > >=C2=A0 =C2=A0 =C2=A0>> >> freq=3D2452 MHz)
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:3d:a2:e9 reason
> > =3D0
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;CTRL-EVENT-SCAN-RESULTS
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;Trying to associate with 6c:3b:6b:ab:ce:d4
> > >=C2=A0 =C2=A0 =C2=A0>(SSID=3D'Palombia'
> > >=C2=A0 =C2=A0 =C2=A0>> >> freq=3D2412 MHz)
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;Associated with 6c:3b:6b:ab:ce:d4
> > >=C2=A0 =C2=A0 =C2=A0>> >>
> > >=C2=A0 =C2=A0 =C2=A0>> >> a2:e9 is the loudest AP here= > in my office, but my I have been in
> > >=C2=A0 =C2=A0 =C2=A0>the
> > >=C2=A0 =C2=A0 =C2=A0>> >> other end of the house iwn c= > onsistently fails to associate
> > >=C2=A0 =C2=A0 =C2=A0with it
> > >=C2=A0 =C2=A0 =C2=A0>> >> and
> > >=C2=A0 =C2=A0 =C2=A0>> >> and keeps picking the weaker= > AP in the far end.
> > >=C2=A0 =C2=A0 =C2=A0>> >>
> > >=C2=A0 =C2=A0 =C2=A0>> >> Eventually (hours!) it disco= > nnects from the weaker ap, also with
> > >=C2=A0 =C2=A0 =C2=A0>> >> "reason=3D0" and g= > ets it right:
> > >=C2=A0 =C2=A0 =C2=A0>> >>
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4
> > >=C2=A0 =C2=A0 =C2=A0>[GTK=3DCCMP]
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:ab:ce:d4 reason
> > =3D0
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;CTRL-EVENT-SCAN-RESULTS
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;Trying to associate with 6c:3b:6b:3d:a2:e9
> > >=C2=A0 =C2=A0 =C2=A0>(SSID=3D'Palombia'
> > >=C2=A0 =C2=A0 =C2=A0>> >> freq=3D2452 MHz)
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;Associated with 6c:3b:6b:3d:a2:e9
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9
> > >=C2=A0 =C2=A0 =C2=A0>[PTK=3DCCMP
> > >=C2=A0 =C2=A0 =C2=A0>> >> GTK=3DCCMP]
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9
> > >=C2=A0 =C2=A0 =C2=A0>> completed
> > >=C2=A0 =C2=A0 =C2=A0>> >> [id=3D3 id_str=3D]
> > >=C2=A0 =C2=A0 =C2=A0>> >>=C2=A0 =C2=A0 =C2=A0 <3>= > ;WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9
> > >=C2=A0 =C2=A0 =C2=A0>[GTK=3DCCMP]
> > >=C2=A0 =C2=A0 =C2=A0>> >>
> > >=C2=A0 =C2=A0 =C2=A0>> >> And yes, working roaming wou= > ld be nice too...
> > >=C2=A0 =C2=A0 =C2=A0>> >
> > >=C2=A0 =C2=A0 =C2=A0>> > I have the problem that when roa= > ming networks become disabled
> > >=C2=A0 =C2=A0 =C2=A0>> >
> > >=C2=A0 =C2=A0 =C2=A0>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0$ wpa_= > cli
> > >=C2=A0 =C2=A0 =C2=A0>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0Select= > ed interface 'wlan0'
> > >=C2=A0 =C2=A0 =C2=A0>> >
> > >=C2=A0 =C2=A0 =C2=A0>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0Intera= > ctive mode
> > >=C2=A0 =C2=A0 =C2=A0>> >
> > >=C2=A0 =C2=A0 =C2=A0>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0> l= > ist_networks
> > >=C2=A0 =C2=A0 =C2=A0>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0networ= > k id / ssid / bssid / flags
> > >=C2=A0 =C2=A0 =C2=A0>> >=C2=A0 =C2=A0 =C2=A0 =C2=A00=C2= > =A0 =C2=A0 =C2=A0 =C2=A0network1=C2=A0 =C2=A0 =C2=A0 =C2=A0 any=C2=A0 =C2= > =A0 =C2=A0[CURRENT]
> > >=C2=A0 =C2=A0 =C2=A0>> >=C2=A0 =C2=A0 =C2=A0 =C2=A01=C2= > =A0 =C2=A0 =C2=A0 =C2=A0network2 any=C2=A0 =C2=A0 [DISABLED]
> > >=C2=A0 =C2=A0 =C2=A0>> >=C2=A0 =C2=A0 =C2=A0 =C2=A02=C2= > =A0 =C2=A0 =C2=A0 =C2=A0network3 any=C2=A0 =C2=A0 [DISABLED]
> > >=C2=A0 =C2=A0 =C2=A0>> >=C2=A0 =C2=A0 =C2=A0 =C2=A03=C2= > =A0 =C2=A0 =C2=A0 =C2=A0network4 any=C2=A0 =C2=A0 [DISABLED]
> > >=C2=A0 =C2=A0 =C2=A0>> >=C2=A0 =C2=A0 =C2=A0 =C2=A04=C2= > =A0 =C2=A0 =C2=A0 =C2=A0network5 any=C2=A0 =C2=A0 [DISABLED]
> > >=C2=A0 =C2=A0 =C2=A0>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0Select= > ed interface 'wlan0'
> > >=C2=A0 =C2=A0 =C2=A0>> >
> > >=C2=A0 =C2=A0 =C2=A0>> >
> > >=C2=A0 =C2=A0 =C2=A0>> > I address this by doing network_= > enable x in wpa_cli and it all
> > >=C2=A0 =C2=A0 =C2=A0>comes
> > >=C2=A0 =C2=A0 =C2=A0>> > back. I asked Adrian about this = > in the past, but it needs some
> > >=C2=A0 =C2=A0 =C2=A0>> > debugging
> > >=C2=A0 =C2=A0 =C2=A0>> > to pin down.
> > >=C2=A0 =C2=A0 =C2=A0>>
> > >=C2=A0 =C2=A0 =C2=A0>>
> > >=C2=A0 =C2=A0 =C2=A0>> Is this iwm(4) as well in your case o= > r another card?
> > >=C2=A0 =C2=A0 =C2=A0>>
> > >=C2=A0 =C2=A0 =C2=A0>> /bz
> > >=C2=A0 =C2=A0 =C2=A0>> _____________________________________= > __________
> > >=C2=A0 =C2=A0 =C2=A0>> eebsd.org" target=3D"_blank">freebsd-wireless@freebsd.org
> > >=C2=A0 =C2=A0 =C2=A0<mailto: freebsd.org" target=3D"_blank">freebsd-wireless@freebsd.org> mailing= > list
> > >=C2=A0 =C2=A0 =C2=A0>> mailman/listinfo/freebsd-wireless" rel=3D"noreferrer" target=3D"_blank">htt= > ps://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> > >=C2=A0 =C2=A0 =C2=A0>> To unsubscribe, send any mail to
> > >=C2=A0 =C2=A0 =C2=A0>" nsubscribe@freebsd.org" target=3D"_blank">freebsd-wireless-unsubscribe@free= > bsd.org
> > >=C2=A0 =C2=A0 =C2=A0<mailto: unsubscribe@freebsd.org" target=3D"_blank">freebsd-wireless-unsubscribe@fre= > ebsd.org>
> > >=C2=A0 =C2=A0 =C2=A0>> "
> > >=C2=A0 =C2=A0 =C2=A0>>
> > >=C2=A0 =C2=A0 =C2=A0>__________________________________________= > _____
> > >=C2=A0 =C2=A0 =C2=A0> org" target=3D"_blank">freebsd-current@freebsd.org <mailto: =3D"mailto:freebsd-current@freebsd.org" target=3D"_blank">freebsd-current@f= > reebsd.org>
> > >=C2=A0 =C2=A0 =C2=A0mailing list
> > >=C2=A0 =C2=A0 =C2=A0> an/listinfo/freebsd-current" rel=3D"noreferrer" target=3D"_blank">https://l= > ists.freebsd.org/mailman/listinfo/freebsd-current
> > >=C2=A0 =C2=A0 =C2=A0>To unsubscribe, send any mail to
> > >=C2=A0 =C2=A0 =C2=A0>" subscribe@freebsd.org" target=3D"_blank">freebsd-current-unsubscribe@freebs= > d.org
> > >=C2=A0 =C2=A0 =C2=A0<mailto: nsubscribe@freebsd.org" target=3D"_blank">freebsd-current-unsubscribe@freeb= > sd.org>"
> > >
> > >=C2=A0 =C2=A0 =C2=A0With wpa_supplicant running roaming is set to = > manual. Bgscan
> > >=C2=A0 =C2=A0 =C2=A0should be enabled.=C2=A0
> > >
> > >=C2=A0 =C2=A0 =C2=A0At home we have two n (and 2 g) wifi networks.= > When powering off
> > >=C2=A0 =C2=A0 =C2=A0one ap it connects to the other (in addition t= > o using lagg to
> > >=C2=A0 =C2=A0 =C2=A0failover from ethernet to wifi and back).
> > >
> > >=C2=A0 =C2=A0 =C2=A0Your wpa_supplicant should contain each ssid y= > ou intend to use. A
> > >=C2=A0 =C2=A0 =C2=A0wildcard can be used for open networks.
> > >
> > >=C2=A0 =C2=A0 =C2=A0It's a while since I've tested this fu= > nctionality but I can test
> > >=C2=A0 =C2=A0 =C2=A0again when I get home tonight.
> > >
> > >
> > >=C2=A0 =C2=A0 =C2=A0--
> > >=C2=A0 =C2=A0 =C2=A0Pardon the typos and autocorrect, small keyboa= > rd in use.
> > >=C2=A0 =C2=A0 =C2=A0Cheers,
> > >=C2=A0 =C2=A0 =C2=A0Cy Schubert < cschubert.com" target=3D"_blank">Cy.Schubert@cschubert.com
> > >=C2=A0 =C2=A0 =C2=A0<mailto: bert.com" target=3D"_blank">Cy.Schubert@cschubert.com>>
> > >=C2=A0 =C2=A0 =C2=A0FreeBSD UNIX: <cy@FreeBSD.org> Web: ref=3D"http://www.FreeBSD.org" rel=3D"noreferrer" target=3D"_blank">http://= > www.FreeBSD.org
> > >
> > >=C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 The need of the ma= > ny outweighs the greed of the few.
> > >
> >
> > Hmm so in other words, you have to set bgscan for each network entry y= > ou
> > want roaming? What are some good values for this?
>
> Just tested here. It worked after a short delay, with a not-so-young laptop= >
> with iwn.
>
> wlan0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 = > mtu 1500
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 ether 20:NN:NN:NN:NN:NN
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 groups: wlan
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 ssid "BBBBBBBB" channel 1 (2412 MHz 1= > 1g ht/20) bssid 78:BB:BB:BB:BB:BB
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 regdomain FCC country US authmode WPA2/802.11i = > privacy ON
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-= > bit txpower 30
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 bmiss 120 scanvalid 16959 protmode CTS ampdulim= > it 64k -amsdutx amsdurx
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 shortgi -stbc -ldpc wme roaming MANUAL
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 media: IEEE 802.11 Wireless Ethernet MCS mode 1= > 1ng
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 status: associated
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_= > LINKLOCAL>
>
> And the gory details:
>
> Sep 19 17:21:35 slippy wpa_supplicant[381]: wlan0: CTRL-EVENT-DISCONNECTED = >
> bssid=3Da6:NN:NN:NN:NN:NN reason=3D0
> Sep 19 17:21:35 slippy wpa_supplicant[381]: wlan0: Trying to associate with= >
> a6:NN:NN:NN:NN:NN (SSID=3D'AAA' freq=3D2462 MHz)
> Sep 19 17:21:35 slippy wpa_supplicant[381]: Failed to add supported
> operating classes IE
> Sep 19 17:21:35 slippy wpa_supplicant[381]: wlan0: Associated with
> a6:NN:NN:NN:NN:NN
> Sep 19 17:21:45 slippy wpa_supplicant[381]: wlan0: Authentication with
> a6:08:ea:9c:a0:84 timed out.
> Sep 19 17:21:45 slippy wpa_supplicant[381]: wlan0: CTRL-EVENT-DISCONNECTED = >
> bssid=3Da6:NN:NN:NN:NN:NN reason=3D3 locally_generated=3D1
> Sep 19 17:21:47 slippy wpa_supplicant[381]: wlan0: Trying to associate with= >
> 78:NN:NN:NN:NN:NN (SSID=3D'BBBBBBBBB' freq=3D2412 MHz)
> Sep 19 17:21:47 slippy wpa_supplicant[381]: Failed to add supported
> operating classes IE
> Sep 19 17:21:47 slippy wpa_supplicant[381]: wlan0: Associated with
> 78:NN:NN:NN:NN:NN
> Sep 19 17:21:48 slippy wpa_supplicant[381]: wlan0: WPA: Key negotiation > > completed with 78:NN:NN:NN:NN:NN [PTK=3DCCMP GTK=3DCCMP]
> Sep 19 17:21:48 slippy wpa_supplicant[381]: wlan0: CTRL-EVENT-CONNECTED - <= > br> > Connection to 78:NN:NN:NN:NN:NN completed [id=3D7 id_str=3D]
>
> AAA is my cell phone. the B's are $JOB.
>
> The relevant parts of my wpa_supplicant.conf:
>
> network=3D{
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 ssid=3D"AAA"
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 priority=3D6
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 proto=3DRSN WPA
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 key_mgmt=3DWPA-PSK
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 pairwise=3DCCMP
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 group=3DCCMP
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 psk=3D"x"
> }
>
> network=3D{
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 ssid=3D"BBBBBBBBB"
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 scan_ssid=3D1
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 priority=3D5
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 proto=3DRSN WPA
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 key_mgmt=3DWPA-PSK
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 pairwise=3DCCMP TKIP
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 group=3DCCMP TKIP
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 psk=3D"y"
> }
>
> #Wildcard match for SSID (plaintext APs only). This example select any
> #open AP regardless of its SSID.
> network=3D{
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 priority=3D0
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 disabled=3D1
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 key_mgmt=3DNONE
> }
>
> Hope this helps.
>
>
> --
> Cheers,
> Cy Schubert < nk">Cy.Schubert@cschubert.com>
> FreeBSD UNIX:=C2=A0 <cy@FreeBSD.org>=C2=A0 =C2=A0Web:=C2=A0 =3D"http://www.FreeBSD.org" rel=3D"noreferrer" target=3D"_blank">http://www= > .FreeBSD.org
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 The need of the many outweighs the greed of the= > few.
>
>
>
> > --0000000000000875960592f275a3-- From owner-freebsd-current@freebsd.org Fri Sep 20 02:59:40 2019 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 EA1F6EED94; Fri, 20 Sep 2019 02:59:40 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46ZJNC6sTSz4b3k; Fri, 20 Sep 2019 02:59:39 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-pg1-x52d.google.com with SMTP id z12so2970392pgp.9; Thu, 19 Sep 2019 19:59:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:autocrypt:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=7tT/GJDXE0sg6HSexgW4C6ioi9cs9IfUqcxwllUy/sM=; b=aQlTdRbkffrkeU7SYWlAGCqV5zR5Sc4EU8bkqLPDeSqiTsQ5/tSd7rpBpJmvmkAURG xoAG2Z5uvOjp0UoWHMr5PaQu9oAp7GWdUGd/50o7L907qC+JPm7BWbpKeOj6YdwgGhyT FskzNXBG0Wo+hkuUAgQj8D9UHY6zKLHflbmJz2yogHYxW06/+nsLbr2kj3ABbSxYNUEx pzMAxZR+9AcbBl1R3m9gOwsjP3fX/OZORo6cqhSTPnae32VGmZVMe8MhX9GV7aZ0rdjm nvwRfqTMR4UwlZ9ku5ddwmNbCdwnrUSCxp0cYB5IvyOcJnZtil/bxGbmlOuyW9B2PcKQ iysQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding:content-language; bh=7tT/GJDXE0sg6HSexgW4C6ioi9cs9IfUqcxwllUy/sM=; b=IyIZfWHf47RIOEnOtmYiivzG+PnnekZ7NUoV+gckjpOEuD9LSeNwL330xHxeVT4n6v sBEMXZLJFjAtftJDLA1HoUA4F/Qkd8oZ60dEAB4WPc7dzvT1BPhAZ7goGDGtTv/dGawk RlMXw4iTwLZTDo2q54zTPKZUWepA14qlnaNSd3PLq1Rmw41QyzDYCykx5A0X7kc/zxeY 3waW9wtXdc+hTkFEbRcWS7uMeBJi7Fymrwm0dAtcRUsGl72yS+Xsou6/uPKw1NuDXKVd joJMF9MZKx8N91JgT6J49DWpWNtjqh7VycxY79695AUJ/ZsFIssGKWeoHKtXnMc1m+Ia SI3A== X-Gm-Message-State: APjAAAVJndKTf2cdPqD9R+4b4xasx+9p1ZLvOP1F/9EbQw5uSFiNGr6k H52NiH94QqIXf6XqPHk9u9aGGhPO80I= X-Google-Smtp-Source: APXvYqzHKJbAAayHb/6SXtnPMJrBMzlPcvhIqvuGiBLj9UjVzxuugMv1b/knZ0No6pnCaNxuWqcM9g== X-Received: by 2002:a63:d608:: with SMTP id q8mr12726696pgg.422.1568948377759; Thu, 19 Sep 2019 19:59:37 -0700 (PDT) Received: from [192.168.0.83] (ip24-251-216-143.ph.ph.cox.net. [24.251.216.143]) by smtp.gmail.com with ESMTPSA id k127sm325322pga.54.2019.09.19.19.59.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 19 Sep 2019 19:59:37 -0700 (PDT) Subject: Re: wlan can't discover known networks after relocating To: Cy Schubert Cc: Adrian Chadd , Cy Schubert , Johannes Lundberg , Poul-Henning Kamp , Tom Jones , freebsd-current , "freebsd-wireless@freebsd.org" References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> <6985.1568738188@critter.freebsd.dk> <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> <7938e5fa-67da-35fa-10d0-ee3004438df7@FreeBSD.org> <201909200125.x8K1Pfhd085841@slippy.cwsent.com> <201909200230.x8K2U4DS074056@slippy.cwsent.com> From: Johannes Lundberg Autocrypt: addr=johalun0@gmail.com; keydata= mQINBFxFmoIBEADoFO5jY+Fmsg44KiZjufEmpEf4kt7nCOfxNG9SruWpoXUaq0B296F+fIZC hNZqv1v7lGTsfoWRusxJmLd5CQgHHxEyruZbbPpNsQ/JKoDY3GGmrmWfN/SX3y0t0kdB9HsW mJcvZhK7we52f4gxddIVBS9nQoVoONX+hzXf8zwOAa0ik0EPgEwpIKS4j9lLq4bU+mqVKdRR bPeDujEA/qbsCKhaFJkPzXZtzEe6srq4RK1doEztwnKz02b+8gs642TRkWDQeTRZputrAaoN Un4R76A1QpXWyrFG1dQu48IGHi3KbkrvNyq6R1aUBIA0+CG1npIbxmc2mtSjoyvdipmDRbBD +mhECIxmYfBT6818zuj91XjrfOyfVdV2BryBvqFkJLkS3N3QElBIiVdDgdrqiNFWiOlDMxNI tdP16oQBNo8IB27/0YHpnQEw1MafZv5gG5DO0zLtLy88ASAfL7BYf90JP19rT4JIwnxsXxyv kEJnzhsXf0QVObEiAu1MqeFyWfZ8PpunmvEmJ0VChOL+v/kIx1E9cxhhzMZhqiMXfyM4zx2+ BF1FwAwJYPuJLu2B3L0uVBu+M1YvSOmKAbXPDP8PsqPjgSBTYI51MUjuuxN6jSsHDuK6G5k4 pUWR8axa+wafhd6Vz8zVwdTJZ9LdxgLLVg0kprBgccPHhPAZVQARAQABtCZKb2hhbm5lcyBM dW5kYmVyZyA8am9oYWx1bjBAZ21haWwuY29tPokCVAQTAQgAPhYhBIl1Pb3+hI60ivmRSULn yG4BGvSeBQJcRZqCAhsjBQkJZgGABQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJEELnyG4B GvSe9O0P/RzeQAu1R37RlONZTXNn+qIAHvHbZEhzrCibzaZnwYdC31wGrYmXNDyiQIqOngFf QJuufQtH/+95OESJsjR+42L/pNfFdaEWxiI003qE7uCMzLK5UWUXd/5d5vYY0CaPyNCj1tyM ZIq7x4CaR3QLTh/Fw4zMUI/ZPH2S5SxVFGv0ZZFAdNYILD3qCkAS/9HmXsqufBWbfutA8TTf wyJfywmvf7ENjlZ4QOjb242ZY9NndqbmqTgWVAws+PN5e9AT8HkadscCTCSkYnxJyYG2El27 DpAAkekYplb/C0j82KSz2fy9RgwD+tTqt88DJOeFbIbrYt44u7KLHpzaZeqyUtn0reHCkE0W lnKH2kXXbuswFB4sONxI/J5+qSmOsAm5ItO3voyjm/swpmFR1yBlxo4th26gbO5NfBOK9YsY zHKgiRDv6ZdnHo+htphRxcCDHsFPzkQe5jouI25dvMZYl1LaTS/09lwYVwVIB2SFmMtFZ7rB N4NBSzPlpsg+g4dJNqiw6Rfa2Q/wUv+MzTJgLtHjDccXlpm33Nc09UytHFtNn26PO/zrM39r TwzdLu1mg0x2WWEWTIqe4CaczQU9SIg49BSyJNoPSZx3V7nMhTKbOeQKR5aV3dXI66aENw86 pa1tipuUKCPmope/GTJatUgPiD3JkyiD+7c1zQX2UAGmuQINBFxFmoIBEACb55RAkM59huAx 4Ddd8WBjsw25qf7rzxeRKAQ7or/8LvJBYQDPXZy0RhkRiu+P+MjxwGb6HVh+LDyAYDn9d8Mt ZqCP/dOGNcl7pkb6IhfRc3i5neckXCYfbm0cigiX9JkqZSt3KT96zbjCxsFZKyIyEFsMl46q 7wKWK5Irj3zxV/Z51JNTJyMLcIRWhY8G6qlMNFgZkz2Hv63w6BRekKVImOmOdThLAscy5ybq 2CIUeAwPG7lMYG9rgcPdn3tMPeWlLmUmi5pSwOQ3AKg3xFrW3WfegjRHdqpeuXoeTjYPPCW4 gyl59uv6E12a6eivItCxj67vlBXgOr4um+zoPyXG/WfidIFtWaEgyBrlGR1Klk7SIcqjEHUA FdiM+PweY4opHXXKn60NOZCqBJ59K43drOQgRouz8E2T3yEoYg40xAfY3lhJV/Vx5+kSTjmy sT2xotlPn/GzfaAEvNuJDK+Mec3LvfbbDoOWFolNyEvoMQqF5Q3A8eGqYsoVGBPxyzNvF2iY LkymxiXpgrSN0Q/LOK7pFlWwbVC8Z6g5I0J9ecgD55dGLoX2luLir787XX/JxGffzbRnP9NE ifenJGrQmx4CyEaz/CHQqSbROm5Uo/YFUX9J7OfUO4mtu90j773j32I3psey/Fz3EC/A2PHv Ghb0KsWYpS3Pj5TV1gGyswARAQABiQI8BBgBCAAmFiEEiXU9vf6EjrSK+ZFJQufIbgEa9J4F AlxFmoICGwwFCQlmAYAACgkQQufIbgEa9J7qOQ//YG/4e69YTSjtiYLXzBI8tRU2Sx+NFByx zx+C/r0EBThLtgRwCqEUZRB7iIDSO8aZ0Qa3vwWRohlD1tn/LBdDFfMmuQkNVdLIrjBoGBB9 B5xHdZJ9xnTZEwpTtk6IWolT4j+8rpGemGKKiFo3X6l02On4Qb4iM7h6rcDb76mfwooNYzB3 8PPcLvyOWb/9iCXAb5N7doo5zmOl15DVwvIF04eXU0q1FFj/iS1zNmtZ5Got82O1TQFV+de4 Rb3YA80IZhhhCiHHJqkMKeKQogRqU+UNDBARUBxfUtKsJtQzTQ2JUGwkb6X6bx53FTLP6O9q hDoODVweE1LdB1k1H5Nn+gawPdRMBqj43Y2amK7KEgoTBrwU04CLpKiaAC0S+EcJFfJcwtpK k3F+uTtP/hnhFnWbn8SgRkHKXKWqSCt63NstXhMzAJut1gEzV+CcPNKqa/sFgQaYEvzCS5Kl F/PXj0++f3TIFqT+2ZNNp8Bz8dT7gh8RPPg5oYQiCHH8K1RAmq7gKqmwyg0qgOazHnped+od X4f3qx320JAP6NP9wglDm6eht48NJzb0sffN8z34wrP66oz8oPKtS5CFV0m/384hEg0lmi3W wo2Hno7rA1etTPJX0dI6/GLlQDtNTHvKQ077HQdWVOMQVWC9j7YH7Zr9NjtOvxcNVRX3fxpJ 6CE= Message-ID: <5ade24b7-88a7-db75-59dd-ad5a04467b1e@gmail.com> Date: Thu, 19 Sep 2019 19:59:35 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.0 MIME-Version: 1.0 In-Reply-To: <201909200230.x8K2U4DS074056@slippy.cwsent.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 46ZJNC6sTSz4b3k X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=aQlTdRbk; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of johalun0@gmail.com designates 2607:f8b0:4864:20::52d as permitted sender) smtp.mailfrom=johalun0@gmail.com X-Spamd-Result: default: False [-1.50 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCPT_COUNT_SEVEN(0.00)[8]; 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]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[d.2.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (-8.79), ipnet: 2607:f8b0::/32(-2.66), asn: 15169(-2.21), country: US(-0.05)]; FREEMAIL_CC(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[]; SUSPICIOUS_RECIPS(1.50)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 20 Sep 2019 02:59:41 -0000 On 9/19/19 7:30 PM, Cy Schubert wrote: > In message om> > , Johannes Lundberg writes: >> --0000000000000875960592f275a3 >> Content-Type: text/plain; charset="UTF-8" >> Content-Transfer-Encoding: quoted-printable >> >> Tested today with bgscan added. Didn=E2=80=99t connect to home network unti= >> l I >> manually run ifconfig wlan0 scan. >> Again, this is with failover lagg. > I use failover lagg too. I'm still at $JOB so no ethernet for my personal > FreeBSD laptop here, but that works as well, at home. > >> It did however realize I wasn't at the office anymore and the ssid = >> field >> was empty in ifconfig output. Sometimes it stays the same long after I >> leave the network. > Do you suspend/resume your laptop? Not the last few months because iichid doesn't support it yet. I just leave it on while going between work/home. > From owner-freebsd-current@freebsd.org Fri Sep 20 05:24:23 2019 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 BEF83F2AB4 for ; Fri, 20 Sep 2019 05:24:23 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46ZMbB6c6Yz3FQ0 for ; Fri, 20 Sep 2019 05:24:22 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.92.2 (FreeBSD)) (envelope-from ) id 1iBBP1-000HY7-I8; Fri, 20 Sep 2019 07:24:19 +0200 Date: Fri, 20 Sep 2019 07:24:19 +0200 From: Kurt Jaeger To: Daniel Engberg Cc: freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190920052419.GJ2863@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 46ZMbB6c6Yz3FQ0 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of lists@opsec.eu designates 2001:14f8:200::1 as permitted sender) smtp.mailfrom=lists@opsec.eu X-Spamd-Result: default: False [-4.69 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[opsec.eu]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-3.39)[ip: (-8.75), ipnet: 2001:14f8::/32(-4.56), asn: 12502(-3.65), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 20 Sep 2019 05:24:23 -0000 Hi! > You're probably looking for this: > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html Thanks, that looks like a very useful approach. Will test that when I'm in the housing facility, and report back. -- pi@opsec.eu +49 171 3101372 One year to go ! From owner-freebsd-current@freebsd.org Fri Sep 20 08:28:27 2019 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 8D782F6DCB for ; Fri, 20 Sep 2019 08:28:27 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out.migadu.com (out.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.migadu.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46ZRgY6J1Zz3Nsk for ; Fri, 20 Sep 2019 08:28:25 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Fri, 20 Sep 2019 08:28:23 +0000 Received: from [100.82.217.116] ([185.211.159.155]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id 8E7F02E3-8407-491F-BD41-D6A49DA14705.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Fri, 20 Sep 2019 08:28:22 +0000 Date: Fri, 20 Sep 2019 11:28:04 +0300 User-Agent: K-9 Mail for Android In-Reply-To: <8a98a3d4-ab1c-b5b4-f670-007560e8ee84@gmail.com> References: <8a98a3d4-ab1c-b5b4-f670-007560e8ee84@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: =?UTF-8?Q?Re=3A_Firefox_=E2=80=93_GtkFileChooserNa?= =?UTF-8?Q?tive_=E2=80=93_file_selection_dialogues?= To: freebsd-current@freebsd.org,Graham Perrin From: Greg V Message-ID: <7B4F2D0F-7DA3-4F6D-A024-934BCC64A142@unrelenting.technology> DKIM-Signature: v=1; a=rsa-sha256; bh=YB8mT0VTuZXv2lZZB3urlklwvBCrqyj5Du18wyDHSn0=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; s=default; b=cQsgGjWEtWpj75ayl8PNb2sftZKvqE5HbHsY7SPMDGPNAxBEFkfUEcltEgHcXWEpMuxDa5IJBQxRPuR+WD7pKu3nyoCKOD9tQ9Wota8GoCmNp1JtWB9fmb1fFrSJ310huEbg3kU1cLmZ4uel+oBzwlxCz6BYHp6eGfB4xmQzf9c= X-Rspamd-Queue-Id: 46ZRgY6J1Zz3Nsk X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=cQsgGjWE; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 91.121.223.63 as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-5.55 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:91.121.223.63]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[63.223.121.91.list.dnswl.org : 127.0.10.0]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-2.55)[ip: (-9.84), ipnet: 91.121.0.0/16(-4.32), asn: 16276(1.43), country: FR(-0.00)]; ASN(0.00)[asn:16276, ipnet:91.121.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 20 Sep 2019 08:28:27 -0000 On September 19, 2019 8:02:35 PM GMT+03:00, Graham Perrin wrote: >Firefox does not use xdg-desktop-portal for file selection dialogs > > > > This patch makes Firefox's GTK3 platform support use > > GtkFileChooserNative when available=2E GtkFileChooserNative > > transparently uses the desktop portals interface, which > > enables Firefox to use native Qt file dialogs on KDE, or > > sandboxed file dialogs in Flatpak=2E > >=E2=80=93 RESOLVED FIXED, mozilla64 > >Can I benefit from this patch on FreeBSD? > >(What am I missing?) The dbus portal implementation itself, most likely=2E From owner-freebsd-current@freebsd.org Fri Sep 20 14:35:44 2019 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 0765AFEB3B for ; Fri, 20 Sep 2019 14:35:44 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 46ZbqM5tqPz4GJL; Fri, 20 Sep 2019 14:35:43 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1iBK0R-0002BF-Qf; Fri, 20 Sep 2019 17:35:31 +0300 Date: Fri, 20 Sep 2019 17:35:31 +0300 From: Slawa Olhovchenkov To: Michael Gmelin Cc: Kurt Jaeger , Toomas Soome , freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190920143531.GB38096@zxy.spb.ru> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-Rspamd-Queue-Id: 46ZbqM5tqPz4GJL X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.99 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.993,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 20 Sep 2019 14:35:44 -0000 On Thu, Sep 19, 2019 at 06:04:54PM +0200, Michael Gmelin wrote: > > > > On 19. Sep 2019, at 17:57, Kurt Jaeger wrote: > > > > Hi! > > > >>> We have a system with 10 SATA disks. 2 disks are for the system, > >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: > >>> > >>> bck 72.8T 38.7T 34.1T - - 1% 53% 1.00x ONLINE - > > > >>> The problem is that if all 10 disks are connected, the system > >>> looses track from where it should boot and fails to boot (serial boot log): > > > >> Why this order does change? One would expect disks 0 and 1 to be OS disks and the rest for data??? > > > > 0+1 are 2.5", and the initial setup was: > > - we installed system disks as zroot > > - shipped the box to the housing facility > > - booted and added the drives > > > > At that time we did not do additional tests about the disk/boot sequence > > etc. > > > >> Also the question is, what you mean with ???system looses track???? > > > > I interpret the hang during boot as 'it looses track'. So I guess > > it tries to read the kernel from the wrong drives. > > > >> disk4 becomes adaX? why it matters, are you using ufs on boot disks? > > > > No, zpool only. > > > > I've made a few more details available here: > > > > https://people.freebsd.org/~pi/host/dmesg.txt > > https://people.freebsd.org/~pi/host/devlist.txt > > https://people.freebsd.org/~pi/host/gpart.txt > > https://people.freebsd.org/~pi/host/pciconf.txt > > https://people.freebsd.org/~pi/host/zpool.txt > > What about gpart output of the pool drives? > > In general you would create zpools using gptids or gpt labels, not the devices, so you’re independent of device numbering. The boot loader should only be installed on drives that contain the boot pool (maybe you have old boot loaders on data drives?). ZFS work w/ ZFS labels, not w/ device names/gptids/gpt labels. You don't worry about changed device names aroud reboots. From owner-freebsd-current@freebsd.org Fri Sep 20 15:27:54 2019 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 D5BCDFFB49 for ; Fri, 20 Sep 2019 15:27:54 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (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 46ZczY4lrLz4Jvy for ; Fri, 20 Sep 2019 15:27:53 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 46ZczT0jPbzr4D for ; Fri, 20 Sep 2019 17:27:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:references:in-reply-to:organization :subject:subject:from:from:date:date:content-transfer-encoding :content-type:content-type:mime-version:received:received :received:received; s=jakla4; t=1568993265; x=1571585266; bh=3xW pXTcRBN4wLwkYiue71UzGLEeLYTfK0Im4pdxNV1g=; b=fk2A9q6lpwpZvUZhwgl Qw1NG5KjGjDttUnEtnTDAgP6CppEOzXHQxfWYJDhSIzF5SoJnvu5A9vFkNJ1nnCL lbPOlp62Zhe1WyAQsu7Z+p30OU5j2GdZ/449cYoU088AFHn5rok1Z/utGTOF+2h+ 15n/UFQA6+SONFHWyR91sVqA= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id g7gH-QCuig96 for ; Fri, 20 Sep 2019 17:27:45 +0200 (CEST) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 46ZczP2DjPzr4C for ; Fri, 20 Sep 2019 17:27:45 +0200 (CEST) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 46ZczN6y4czkp for ; Fri, 20 Sep 2019 17:27:44 +0200 (CEST) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by webmail.ijs.si with HTTP (HTTP/2.0 POST); Fri, 20 Sep 2019 17:27:44 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 20 Sep 2019 17:27:44 +0200 From: Mark Martinec To: freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Organization: Jozef Stefan Institute In-Reply-To: <20190920143531.GB38096@zxy.spb.ru> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> <20190920143531.GB38096@zxy.spb.ru> Message-ID: <9ba9867986faac1ce5068b481669d5f8@ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.3.1 X-Rspamd-Queue-Id: 46ZczY4lrLz4Jvy X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ijs.si header.s=jakla4 header.b=fk2A9q6l; dmarc=pass (policy=none) header.from=ijs.si; spf=pass (mx1.freebsd.org: domain of Mark.Martinec@ijs.si designates 2001:1470:ff80::25 as permitted sender) smtp.mailfrom=Mark.Martinec@ijs.si X-Spamd-Result: default: False [-2.46 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[ijs.si:s=jakla4]; RCVD_COUNT_FIVE(0.00)[6]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:1470:ff80::25]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[ijs.si:+]; DMARC_POLICY_ALLOW(-0.50)[ijs.si,none]; RCVD_IN_DNSWL_NONE(0.00)[5.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.f.f.0.7.4.1.1.0.0.2.list.dnswl.org : 127.0.11.0]; IP_SCORE(-0.46)[asn: 2107(-2.30), country: SI(0.01)]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:2107, ipnet:2001:1470::/32, country:SI]; TAGGED_FROM(0.00)[freebsd]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[ijs.si.dwl.dnswl.org : 127.0.11.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 20 Sep 2019 15:27:54 -0000 Kurt Jaeger writes: > The problem is that if all 10 disks are connected, the system > looses track from where it should boot and fails to boot (serial boot > log): > > Consoles: internal video/keyboard serial port > BTX loader 1.00 BTX version is 1.02 > Consoles: internal video/keyboard serial port > BIOS drive C: is disk0 > BIOS drive D: is disk1 > BIOS drive E: is disk2 > BIOS drive F: is disk3 > BIOS drive G: is disk4 > BIOS drive H: is disk5 > BIOS drive I: is disk6 > BIOS drive J: is disk7 > BIOS drive K: is disk8 > BIOS drive L: is disk9 > // > [...] > The solution right now is this to unplug all disks of the 'bck' pool, > reboot, and re-insert the data disks after the boot is finished. > [...] > No gpart on the bck pool, raw drives. This sounds very much like my experience: 2018-11-29, Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2 https://lists.freebsd.org/pipermail/freebsd-stable/2018-November/090129.html https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090159.html I now have three SuperMicro machines which are unable to boot after upgrading 11.2 to 12.0. After unsuccessfully fiddling with boot loaders, I have reverted two back to 11.2 (which boots and works fine again), and the third one is now at 12.0 but needs the boot hack as described by Kurt, i.e. pull out half the disks (of the 'data' pool), boot the system, plug the disks back in and zfs mount the remaining pool. Considering that the 11.2 boots and works fine on these machines, I consider it a btx loader failure and not a BIOS issue. What is common with these three machines is that they have one pool on raw devices for historical reasons (not on gpt partitions). My guess is that the new loader gets confused by these raw disks. Mark From owner-freebsd-current@freebsd.org Fri Sep 20 15:29:22 2019 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 1D0D4FFC89 for ; Fri, 20 Sep 2019 15:29:22 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46Zd1F37zCz4K4k; Fri, 20 Sep 2019 15:29:21 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lj1-x22e.google.com with SMTP id 7so7489675ljw.7; Fri, 20 Sep 2019 08:29:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pXyqJiy2sixYawfIxl/xR7pki39rJY+5pD1DAkSeYbg=; b=QiHs9zJVKtweCaFQGIZkZGvP4me7fxEdiYj7Ada2792uF8uonmarDcVbU2tQ7R4Miy r9GGY8Ip8c5JkNkzTxuXzFp5cWGyeNnENB6TIw/fJ9vQPPU+MXUkS5mYlA5WImO8zipb vecDRdTJSDWlXeAWXRPs7h3cte1cFVp6L935ak9ia0PTUEPG7oYJu8n24VLD2mcvzzqE h2VkaoccoEk4TZaePiLASQo5RybR1pxs3JVFSQODfsm2ykIo2RI/wu7bS6vEDq4Hu1Mj i3iAOVVWpGeP8UmI5rlGnZ2WpBKaEhN9oDU2fLdJw+CGULwxR9PPahJKcHWI8SM3IB3i UjHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pXyqJiy2sixYawfIxl/xR7pki39rJY+5pD1DAkSeYbg=; b=HEmzb05ddUAR92F1TSDAURNOofvsCLAj3z7FSbgurgypvImjIIF+TTDfHoivPD+ZL6 tlporWooFDoXfXFQaBQUp0pZxX8rcasx59qboubj4zLPVkfpwdsPEVdayM5vYq0Q65c8 P9KPoiQU03lR5qlTchegVaQ+7v1Bvc4NeLvSnt+5n9cqUjpBprbvCGiDV6nmJysWh/T9 IQx3HhAVp0hpg+LObcOfjvy4a1muVxzq1oP7G47V+F4Toy/uCm4TaEL1F9VPEl/jz+Wz zetlbRzHzOBoWJqMrd4HE03bIRYG3w0YFLyVQPNvL5osH3YEp5zE2rxXoiciICWTOGje rHUA== X-Gm-Message-State: APjAAAWajac61WmZ8WpDvajmY0Sgj8RkOMzDRuFhwvz1OMehEZmCOlNh 91VsbWYvbTp2wLjrBfblUjGR6D0Fs+mWWSosw/tdqQ== X-Google-Smtp-Source: APXvYqzRfgBXxiwjJ97HaXuW0T2eLc87ZnKzA0VAguNQutIHS5jgUXVOPDNBqVXGaiFwXCIdx10OY2cK5EGn8a6hjjg= X-Received: by 2002:a2e:9ac1:: with SMTP id p1mr3308424ljj.179.1568993359556; Fri, 20 Sep 2019 08:29:19 -0700 (PDT) MIME-Version: 1.0 References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> <20190920143531.GB38096@zxy.spb.ru> In-Reply-To: <20190920143531.GB38096@zxy.spb.ru> From: Freddie Cash Date: Fri, 20 Sep 2019 08:29:08 -0700 Message-ID: Subject: Re: Lockdown adaX numbers to allow booting ? To: Slawa Olhovchenkov Cc: Michael Gmelin , Kurt Jaeger , Toomas Soome , FreeBSD-Current X-Rspamd-Queue-Id: 46Zd1F37zCz4K4k X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=QiHs9zJV; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of fjwcash@gmail.com designates 2a00:1450:4864:20::22e as permitted sender) smtp.mailfrom=fjwcash@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[e.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (-9.38), ipnet: 2a00:1450::/32(-2.92), asn: 15169(-2.20), country: US(-0.05)]; 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]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 20 Sep 2019 15:29:22 -0000 On Fri, Sep 20, 2019 at 7:35 AM Slawa Olhovchenkov wrote: > On Thu, Sep 19, 2019 at 06:04:54PM +0200, Michael Gmelin wrote: > > What about gpart output of the pool drives? > > > > In general you would create zpools using gptids or gpt labels, not the > devices, so you=E2=80=99re independent of device numbering. The boot load= er should > only be installed on drives that contain the boot pool (maybe you have ol= d > boot loaders on data drives?). > > ZFS work w/ ZFS labels, not w/ device names/gptids/gpt labels. > You don't worry about changed device names aroud reboots. > Very true, from ZFS' point of view. It writes a ZFS label to whichever GEOM provider you hand it (file, iSCSI device, raw device, MBR partition, GPT partition, etc), and it will find it's pool members based on those labels. ZFS doesn't care where the device is physically connected in the system, just that it is connected. But the ZFS labels aren't what it will display in "zpool list -v" or "zpool status" output. That will show the GEOM provider you gave it (and, depending on the order that GEOM tastes the devices, and what's enabled/disabled in loader.conf, that output can change). That's where it's useful to have human-readable, descriptive labels (like GPT partition labels), and to disable all the GEOM ID systems you won't be using via loader.conf. So that when things go sideways, and a disk dies, you can find it quickly and easily. Much easier to replace "gpt/jbod3-a6" in a multi-chassis storage system with 100+ drives than to figure out which bay corresponds to "ada73" after a couple of reboots that may or may not have changed the PCI bus enumeration direction, or after replacing an HBA that enumerates drives a different way (da vs ada), or after a BIOS/EFI upgrade that renumbers things, or any other number of situations. (We've run into most of these, and have come to rely on GPT partition labels for just this reason; and we stick the drive serial number on the outside of the bay, just in case). It's not a ZFS requirement. It just makes things easier for the admin down the road. Especially if the admin team changes or inherits systems. :) --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-current@freebsd.org Fri Sep 20 15:53:10 2019 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 35BEA121537 for ; Fri, 20 Sep 2019 15:53:10 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 46ZdXj17Ktz4LXC; Fri, 20 Sep 2019 15:53:08 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1iBLDU-0002cV-9C; Fri, 20 Sep 2019 18:53:04 +0300 Date: Fri, 20 Sep 2019 18:53:04 +0300 From: Slawa Olhovchenkov To: Freddie Cash Cc: Michael Gmelin , Kurt Jaeger , Toomas Soome , FreeBSD-Current Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190920155304.GN3953@zxy.spb.ru> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> <20190920143531.GB38096@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-Rspamd-Queue-Id: 46ZdXj17Ktz4LXC X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of slw@zxy.spb.ru has no SPF policy when checking 195.70.199.98) smtp.mailfrom=slw@zxy.spb.ru X-Spamd-Result: default: False [2.84 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; IP_SCORE(0.00)[country: RU(0.01)]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[zxy.spb.ru]; AUTH_NA(1.00)[]; RCPT_COUNT_FIVE(0.00)[5]; NEURAL_SPAM_MEDIUM(0.50)[0.500,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(0.43)[0.434,0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:5495, ipnet:195.70.192.0/19, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 20 Sep 2019 15:53:10 -0000 On Fri, Sep 20, 2019 at 08:29:08AM -0700, Freddie Cash wrote: > On Fri, Sep 20, 2019 at 7:35 AM Slawa Olhovchenkov wrote: > > > On Thu, Sep 19, 2019 at 06:04:54PM +0200, Michael Gmelin wrote: > > > What about gpart output of the pool drives? > > > > > > In general you would create zpools using gptids or gpt labels, not the > > devices, so you’re independent of device numbering. The boot loader should > > only be installed on drives that contain the boot pool (maybe you have old > > boot loaders on data drives?). > > > > ZFS work w/ ZFS labels, not w/ device names/gptids/gpt labels. > > You don't worry about changed device names aroud reboots. > > > > Very true, from ZFS' point of view. It writes a ZFS label to whichever > GEOM provider you hand it (file, iSCSI device, raw device, MBR partition, > GPT partition, etc), and it will find it's pool members based on those > labels. ZFS doesn't care where the device is physically connected in the > system, just that it is connected. > > But the ZFS labels aren't what it will display in "zpool list -v" or "zpool > status" output. That will show the GEOM provider you gave it (and, > depending on the order that GEOM tastes the devices, and what's > enabled/disabled in loader.conf, that output can change). That's where > it's useful to have human-readable, descriptive labels (like GPT partition > labels), and to disable all the GEOM ID systems you won't be using via > loader.conf. So that when things go sideways, and a disk dies, you can > find it quickly and easily. Much easier to replace "gpt/jbod3-a6" in a > multi-chassis storage system with 100+ drives than to figure out which bay > corresponds to "ada73" after a couple of reboots that may or may not have > changed the PCI bus enumeration direction, or after replacing an HBA that Location of device in multi-chassis storage system is different story. I am don't know how to field engineer insert disks in chassis. For me simple is find in /var/run/dmesg.boot S/N <=> daXY mapping and turn ON led by sas2ircu. > enumerates drives a different way (da vs ada), or after a BIOS/EFI upgrade > that renumbers things, or any other number of situations. (We've run into > most of these, and have come to rely on GPT partition labels for just this > reason; and we stick the drive serial number on the outside of the bay, > just in case). > It's not a ZFS requirement. It just makes things easier for the admin down > the road. Especially if the admin team changes or inherits systems. :) This is need many manual work at setup and build time. DC field engineer make servers for me and don't do this work for me. From owner-freebsd-current@freebsd.org Fri Sep 20 21:06:49 2019 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 5F966127A47 for ; Fri, 20 Sep 2019 21:06:49 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 46ZmVc349Mz4dx7 for ; Fri, 20 Sep 2019 21:06:48 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1iBQ73-0004BV-I8; Sat, 21 Sep 2019 00:06:45 +0300 Date: Sat, 21 Sep 2019 00:06:45 +0300 From: Slawa Olhovchenkov To: Garrett Wollman Cc: freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190920210645.GO3953@zxy.spb.ru> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> <20190920143531.GB38096@zxy.spb.ru> <20190920155304.GN3953@zxy.spb.ru> <201909201706.x8KH6Tov048682@hergotha.csail.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201909201706.x8KH6Tov048682@hergotha.csail.mit.edu> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-Rspamd-Queue-Id: 46ZmVc349Mz4dx7 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of slw@zxy.spb.ru has no SPF policy when checking 195.70.199.98) smtp.mailfrom=slw@zxy.spb.ru X-Spamd-Result: default: False [2.83 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.00)[country: RU(0.01)]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[zxy.spb.ru]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.41)[0.406,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.52)[0.524,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:5495, ipnet:195.70.192.0/19, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 20 Sep 2019 21:06:49 -0000 On Fri, Sep 20, 2019 at 01:06:29PM -0400, Garrett Wollman wrote: > In article <20190920155304.GN3953@zxy.spb.ru>, slw@zxy.spb.ru writes: > > >Location of device in multi-chassis storage system is different story. > >I am don't know how to field engineer insert disks in chassis. > >For me simple is find in /var/run/dmesg.boot S/N <=> daXY mapping and > >turn ON led by sas2ircu. > > sesutil does this for you! > > # sesutil locate daXY on > # sesutil locate daXY off > > So long as your enclosure supports SES (all the modern ones I've seen > do) and is enumerable by ses(4). In theory there is no difference between theory and practice. But, in practice, there is. # sesutil map ses0: Enclosure Name: AHCI SGPIO Enclosure Enclosure ID: 0 Element 0, Type: Array Device Slot Status: Unsupported (0x00 0x00 0x00 0x00) Element 1, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 000 Element 2, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 001 Element 3, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 002 Element 4, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 003 ses1: Enclosure Name: AHCI SGPIO Enclosure Enclosure ID: 0 Element 0, Type: Array Device Slot Status: Unsupported (0x00 0x00 0x00 0x00) Element 1, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 000 Element 2, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 001 Element 3, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 002 Element 4, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 003 Element 5, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 004 Element 6, Type: Array Device Slot Status: Unknown (0x06 0x00 0x00 0x00) Description: SLOT 005 # sesutil locate ada0 on sesutil: Count not find the SES id of device 'ada0' # sesutil locate da0 on sesutil: Count not find the SES id of device 'da0' # sas2ircu 0 DISPLAY LSI Corporation SAS2 IR Configuration Utility. Version 20.00.00.00 (2014.09.18) Copyright (c) 2008-2014 LSI Corporation. All rights reserved. Read configuration has been initiated for controller 0 ------------------------------------------------------------------------ Controller information ------------------------------------------------------------------------ Controller type : SAS2308_1 BIOS version : 7.39.02.00 Firmware version : 20.00.07.00 Channel description : 1 Serial Attached SCSI Initiator ID : 0 Maximum physical devices : 255 Concurrent commands supported : 8192 Slot : 1 Segment : 0 Bus : 1 Device : 0 Function : 0 RAID Support : No ------------------------------------------------------------------------ IR Volume information ------------------------------------------------------------------------ ------------------------------------------------------------------------ Physical device information ------------------------------------------------------------------------ Initiator at ID #0 Device is a Hard disk Enclosure # : 1 Slot # : 0 SAS Address : 4433221-1-0300-0000 State : Ready (RDY) Size (in MB)/(in sectors) : 7630885/15628053167 Manufacturer : ATA Model Number : TOSHIBA HDWN180 Firmware Revision : GX2M Serial No : 79HSK0PHFAVG GUID : N/A Protocol : SATA Drive Type : SATA_HDD Device is a Hard disk Enclosure # : 1 Slot # : 1 SAS Address : 4433221-1-0200-0000 State : Ready (RDY) Size (in MB)/(in sectors) : 7630885/15628053167 Manufacturer : ATA Model Number : TOSHIBA HDWN180 Firmware Revision : GX2M Serial No : 79CVK0OEFAVG GUID : N/A Protocol : SATA Drive Type : SATA_HDD .... From owner-freebsd-current@freebsd.org Sat Sep 21 05:56:04 2019 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 3A8B1F74B8 for ; Sat, 21 Sep 2019 05:56:04 +0000 (UTC) (envelope-from kiri@truefc.org) Received: from kx.truefc.org (flets-sg1026.kamome.or.jp [202.216.24.26]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp", Issuer "smtp" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46b0FG5yYgz47s2 for ; Sat, 21 Sep 2019 05:56:02 +0000 (UTC) (envelope-from kiri@truefc.org) Received: from kx.truefc.org (kx.truefc.org [202.216.24.26]) by kx.truefc.org (8.15.2/8.15.2) with ESMTP id x8L5tw5U000784; Sat, 21 Sep 2019 14:55:58 +0900 (JST) (envelope-from kiri@kx.truefc.org) Message-Id: <201909210555.x8L5tw5U000784@kx.truefc.org> Date: Sat, 21 Sep 2019 14:55:58 +0900 From: KIRIYAMA Kazuhiko To: freebsd-current@freebsd.org Cc: kiri@truefc.org Subject: r351680 kernel panic in login User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 MULE XEmacs/21.4 (patch 24) (Standard C) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 46b0FG5yYgz47s2 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of kiri@truefc.org has no SPF policy when checking 202.216.24.26) smtp.mailfrom=kiri@truefc.org X-Spamd-Result: default: False [0.10 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.29)[-0.294,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-0.70)[-0.700,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[truefc.org]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4704, ipnet:202.216.0.0/19, country:JP]; IP_SCORE(-0.00)[country: JP(-0.02)]; ONCE_RECEIVED(0.10)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sat, 21 Sep 2019 05:56:04 -0000 Hi, I've installed r351680 in my note PC. But kernel panic at login: Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex axe0 (axe0) r = (0xfffff80003989ea0) locked 0 /usr/src/sys/dev/usb/usb_transfer.c:2266 stack backtrace: #0 0xffffffff80c3dac3 at winess_debugger+0x73 #1 0xffffffff80c3eae2 at winess_warn+0x442 #2 0xffffffff81191943 at trap_pfault+0x53 #3 0xffffffff81198f42 at trap+0x2b2 #4 0xffffffff8116886c at caltrap+0x8 #5 0xffffffff82f0dd82 at axe_bulk_read_callback+0x142 #6 0xffffffff80a1e52a at usbd_callback_wrapoer+0x7aa #7 0xffffffff80a1c273 at usb_command_wrapper+0xb3 #8 0xffffffff80a1b0ae at usb_callback_proc+0x8e #9 0xffffffff80a15dd5 at usb_process+0xe5 #10 0xffffffff80b8f794 at fork_exit+0x84 #11 0xffffffff811698ae at gork_trampoline+0xe Fatal trap12: page fault while in kernel mode cpuid = 3; apic id = 86 fault virtual address = 0x0 fault code = supervisor write data,page not present instruction pointer = 0x20:0xffffffff82f0df41 stack pointer = 0x28:0xfffffe0000513a40 frame pointer = 0x28:0xfffffe0000513a80 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 = 15 (usbus0) trap number = 12 panic: page fault cpuid = 3 time = 1568969574 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0000513700 vpanic() at vpanic+0x19d/frame 0xfffffe0000513750 panic() at panic+0x43/frame 0xfffffe00005137b0 trap_fatal() at trap_fatal+0x39c/frame 0xfffffe0000513810 trap_pfault() at trap_pfault+0x62/frame 0xfffffe0000513860 trap() at trap+0x2b2/frame 0xfffffe0000513970 calltrap() at calltrap+0x8/frame 0xfffffe0000513970 --- trap 0xc, rip = 0xffffffff82f0d41, rsp = 0xfffffe0000513a40, rbp = 0xfffffe0000513a80 --- axe_rxeof() at axa_rxeof+0x151/frame 0xfffffe0000513a80 axe_bulk_read_callback() at axe_bulk_read_callback+0x142/frame 0xfffffe0000513af0 usbd_callback_wrapper() at usbd_callback_wrapper+0x7aa/fram 0xfffffe0000513b30 usb_command_wrapper() at usb_command_wrapper+0xb3/frame 0xfffffe0000513b50 usb_callback_proc() at usb_callback_proc+0x8e/frame 0xfffffe0000513b70 usb_process() at usb_process+0xe5/frame 0xfffffe0000513bb0 fork_exit() at fork_exit+0x84/frame 0xfffffe0000513bf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000513bf0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- KBD: enter: panic [ thread pid 15 tid 100047 ] Stopped at kbd_enter+0x3b: movq $0,kbd_why db> I've rebooted and at single user mode I saved sevral specs in usb as follows: # umane -a FreeBSD 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r351680: Fri Sep 13 13:37:15 JST 2019 admin@tbedfc:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 # dmesg ---<>--- Copyright (c) 1992-2019 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 13.0-CURRENT #0 r351680: Fri Sep 13 13:37:15 JST 2019 admin@tbedfc:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1) WARNING: WITNESS option enabled, expect reduced performance. VT(efifb): resolution 800x600 CPU: Intel(R) Atom(TM) x5-Z8350 CPU @ 1.44GHz (1439.99-MHz K8-class CPU) Origin="GenuineIntel" Id=0x406c4 Family=0x6 Model=0x4c Stepping=4 Features=0xbfebfbff Features2=0x43d8e3bf AMD Features=0x28100800 AMD Features2=0x101 Structured Extended Features=0x2282 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 4294967296 (4096 MB) avail memory = 3974008832 (3789 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: WARNING: L1 data cache covers fewer APIC IDs than a core (0 < 1) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" random: unblocking device. ioapic0 irqs 0-114 Launching APs: 2 3 1 Timecounter "TSC" frequency 1439990442 Hz quality 1000 random: entropy device external interface [ath_hal] loaded kbd1 at kbdmux0 000.000046 [4335] netmap_init netmap: loaded module module_register_init: MOD_LOAD (vesa, 0xffffffff811b9cc0, 0) error 19 nexus0 efirtc0: efirtc0: registered as a time-of-day clock, resolution 1.000000s cryptosoft0: acpi0: acpi0: Power Button (fixed) unknown: I/O range not supported cpu0: on acpi0 attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x77 on acpi0 atrtc0: Warning: Couldn't map I/O. atrtc0: registered as a time-of-day clock, resolution 1.000000s Event timer "RTC" frequency 32768 Hz quality 0 hpet0: iomem 0xfed00000-0xfed003ff irq 8 on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 450 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0xf000-0xf03f mem 0x90000000-0x90ffffff,0x80000000-0x8fffffff at device 2.0 on pci0 vgapci0: Boot video device pci0: at device 3.0 (no driver attached) xhci0: mem 0x91800000-0x9180ffff at device 20.0 on pci0 xhci0: 32 bytes context size, 64-bit DMA usbus0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 pci0: at device 26.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_acad0: on acpi0 acpi_tz0: on acpi0 sdhci_acpi0: iomem 0x9183a000-0x9183afff irq 45 on acpi0 mmc0: on sdhci_acpi0 sdhci_acpi1: iomem 0x91836000-0x91836fff irq 47 on acpi0 mmc1: on sdhci_acpi1 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12. est0: on cpu0 Timecounters tick every 1.000 msec ugen0.1: <0x8086 XHCI root HUB> at usbus0 uhub0 on usbus0 uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 mmcsd0: 63GB at mmc0 200.0MHz/8bit/8192-block mmcsd0boot0: 4MB partition 1 at mmcsd0 mmcsd0boot1: 4MB partition 2 at mmcsd0 mmcsd0rpmb: 4MB partition 3 at mmcsd0 mmcsd1: 128GB at mmc1 50.0MHz/4bit/65535-block Trying to mount root from ufs:/dev/mmcsd0p2 [rw]... WARNING: WITNESS option enabled, expect reduced performance. uhub0: 13 ports with 13 removable, self powered ugen0.2: at usbus0 ugen0.3: at usbus0 ukbd0 on uhub0 ukbd0: on usbus0 kbd2 at ukbd0 ugen0.4: at usbus0 umass0 on uhub0 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x8100 umass0:0:0: Attached to scbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SCSI device da0: Serial Number 07BA1B081C742B8A da0: 40.000MB/s transfers da0: 1912MB (3915776 512 byte sectors) da0: quirks=0x2 ugen0.5: at usbus0 # df Filesystem 512-blocks Used Avail Capacity Mounted on /dev/mmcsd0p2 111720120 6363664 96418848 6% / devfs 2 2 0 100% /dev /dev/mmcsd1p1 241710968 65672 222308424 0% /work linprocfs 8 8 0 100% /compat/linux/proc tmpfs 7636728 8 7636720 0% /compat/linux/dev/shm /dev/da0s3 1868552 32 1719040 0% /mnt # pciconf -lv hostb0@pci0:0:0:0: class=0x060000 card=0x72708086 chip=0x22808086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x030000 card=0x72708086 chip=0x22b08086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers' class = display subclass = VGA none0@pci0:0:3:0: class=0x048000 card=0x72708086 chip=0x22b88086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit' class = multimedia none1@pci0:0:11:0: class=0x118000 card=0x72708086 chip=0x22dc8086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller' class = dasp xhci0@pci0:0:20:0: class=0x0c0330 card=0x72708086 chip=0x22b58086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller' class = serial bus subclass = USB none2@pci0:0:26:0: class=0x108000 card=0x72708086 chip=0x22988086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine' class = encrypt/decrypt isab0@pci0:0:31:0: class=0x060100 card=0x72708086 chip=0x229c8086 rev=0x36 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU' class = bridge subclass = PCI-ISA # Is there any suggetions? Regards --- KIRIYAMA Kazuhiko From owner-freebsd-current@freebsd.org Sat Sep 21 06:36:18 2019 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 58942F877D for ; Sat, 21 Sep 2019 06:36:18 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46b17j12mNz4BGv for ; Sat, 21 Sep 2019 06:36:16 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 4B7992601E2; Sat, 21 Sep 2019 08:36:08 +0200 (CEST) Subject: Re: r351680 kernel panic in login To: KIRIYAMA Kazuhiko , freebsd-current@freebsd.org References: <201909210555.x8L5tw5U000784@kx.truefc.org> From: Hans Petter Selasky Message-ID: <5db31352-74a5-6945-6597-0b67c2f73f75@selasky.org> Date: Sat, 21 Sep 2019 08:35:21 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <201909210555.x8L5tw5U000784@kx.truefc.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46b17j12mNz4BGv X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of hps@selasky.org designates 88.99.82.50 as permitted sender) smtp.mailfrom=hps@selasky.org X-Spamd-Result: default: False [-5.48 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-3.18)[ip: (-9.36), ipnet: 88.99.0.0/16(-4.75), asn: 24940(-1.79), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sat, 21 Sep 2019 06:36:18 -0000 On 2019-09-21 07:55, KIRIYAMA Kazuhiko wrote: > Hi, > > I've installed r351680 in my note PC. But kernel panic at > login: > > Kernel page fault with the following non-sleepable locks held: > exclusive sleep mutex axe0 (axe0) r = (0xfffff80003989ea0) locked 0 /usr/src/sys/dev/usb/usb_transfer.c:2266 > stack backtrace: > #0 0xffffffff80c3dac3 at winess_debugger+0x73 > #1 0xffffffff80c3eae2 at winess_warn+0x442 > #2 0xffffffff81191943 at trap_pfault+0x53 > #3 0xffffffff81198f42 at trap+0x2b2 > #4 0xffffffff8116886c at caltrap+0x8 > #5 0xffffffff82f0dd82 at axe_bulk_read_callback+0x142 > #6 0xffffffff80a1e52a at usbd_callback_wrapoer+0x7aa > #7 0xffffffff80a1c273 at usb_command_wrapper+0xb3 > #8 0xffffffff80a1b0ae at usb_callback_proc+0x8e > #9 0xffffffff80a15dd5 at usb_process+0xe5 > #10 0xffffffff80b8f794 at fork_exit+0x84 > #11 0xffffffff811698ae at gork_trampoline+0xe > > > Fatal trap12: page fault while in kernel mode > cpuid = 3; apic id = 86 > fault virtual address = 0x0 > fault code = supervisor write data,page not present > instruction pointer = 0x20:0xffffffff82f0df41 > stack pointer = 0x28:0xfffffe0000513a40 > frame pointer = 0x28:0xfffffe0000513a80 > 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 = 15 (usbus0) > trap number = 12 > panic: page fault > cpuid = 3 > time = 1568969574 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0000513700 > vpanic() at vpanic+0x19d/frame 0xfffffe0000513750 > panic() at panic+0x43/frame 0xfffffe00005137b0 > trap_fatal() at trap_fatal+0x39c/frame 0xfffffe0000513810 > trap_pfault() at trap_pfault+0x62/frame 0xfffffe0000513860 > trap() at trap+0x2b2/frame 0xfffffe0000513970 > calltrap() at calltrap+0x8/frame 0xfffffe0000513970 > --- trap 0xc, rip = 0xffffffff82f0d41, rsp = 0xfffffe0000513a40, rbp = 0xfffffe0000513a80 --- > axe_rxeof() at axa_rxeof+0x151/frame 0xfffffe0000513a80 > axe_bulk_read_callback() at axe_bulk_read_callback+0x142/frame 0xfffffe0000513af0 > usbd_callback_wrapper() at usbd_callback_wrapper+0x7aa/fram 0xfffffe0000513b30 > usb_command_wrapper() at usb_command_wrapper+0xb3/frame 0xfffffe0000513b50 > usb_callback_proc() at usb_callback_proc+0x8e/frame 0xfffffe0000513b70 > usb_process() at usb_process+0xe5/frame 0xfffffe0000513bb0 > fork_exit() at fork_exit+0x84/frame 0xfffffe0000513bf0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000513bf0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > KBD: enter: panic > [ thread pid 15 tid 100047 ] > Stopped at kbd_enter+0x3b: movq $0,kbd_why > db> > > I've rebooted and at single user mode I saved sevral specs > in usb as follows: > > # umane -a > FreeBSD 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r351680: Fri Sep 13 13:37:15 JST 2019 admin@tbedfc:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > # dmesg > ---<>--- > Copyright (c) 1992-2019 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 13.0-CURRENT #0 r351680: Fri Sep 13 13:37:15 JST 2019 > admin@tbedfc:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1) > WARNING: WITNESS option enabled, expect reduced performance. > VT(efifb): resolution 800x600 > CPU: Intel(R) Atom(TM) x5-Z8350 CPU @ 1.44GHz (1439.99-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x406c4 Family=0x6 Model=0x4c Stepping=4 > Features=0xbfebfbff > Features2=0x43d8e3bf > AMD Features=0x28100800 > AMD Features2=0x101 > Structured Extended Features=0x2282 > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID > TSC: P-state invariant, performance statistics > real memory = 4294967296 (4096 MB) > avail memory = 3974008832 (3789 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: > WARNING: L1 data cache covers fewer APIC IDs than a core (0 < 1) > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 4 core(s) > random: registering fast source Intel Secure Key RNG > random: fast provider: "Intel Secure Key RNG" > random: unblocking device. > ioapic0 irqs 0-114 > Launching APs: 2 3 1 > Timecounter "TSC" frequency 1439990442 Hz quality 1000 > random: entropy device external interface > [ath_hal] loaded > kbd1 at kbdmux0 > 000.000046 [4335] netmap_init netmap: loaded module > module_register_init: MOD_LOAD (vesa, 0xffffffff811b9cc0, 0) error 19 > nexus0 > efirtc0: > efirtc0: registered as a time-of-day clock, resolution 1.000000s > cryptosoft0: > acpi0: > acpi0: Power Button (fixed) > unknown: I/O range not supported > cpu0: on acpi0 > attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > atrtc0: port 0x70-0x77 on acpi0 > atrtc0: Warning: Couldn't map I/O. > atrtc0: registered as a time-of-day clock, resolution 1.000000s > Event timer "RTC" frequency 32768 Hz quality 0 > hpet0: iomem 0xfed00000-0xfed003ff irq 8 on acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 950 > Event timer "HPET" frequency 14318180 Hz quality 450 > Event timer "HPET1" frequency 14318180 Hz quality 440 > Event timer "HPET2" frequency 14318180 Hz quality 440 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > vgapci0: port 0xf000-0xf03f mem 0x90000000-0x90ffffff,0x80000000-0x8fffffff at device 2.0 on pci0 > vgapci0: Boot video device > pci0: at device 3.0 (no driver attached) > xhci0: mem 0x91800000-0x9180ffff at device 20.0 on pci0 > xhci0: 32 bytes context size, 64-bit DMA > usbus0 on xhci0 > usbus0: 5.0Gbps Super Speed USB v3.0 > pci0: at device 26.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > acpi_button0: on acpi0 > acpi_lid0: on acpi0 > acpi_acad0: on acpi0 > acpi_tz0: on acpi0 > sdhci_acpi0: iomem 0x9183a000-0x9183afff irq 45 on acpi0 > mmc0: on sdhci_acpi0 > sdhci_acpi1: iomem 0x91836000-0x91836fff irq 47 on acpi0 > mmc1: on sdhci_acpi1 > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12. > est0: on cpu0 > Timecounters tick every 1.000 msec > ugen0.1: <0x8086 XHCI root HUB> at usbus0 > uhub0 on usbus0 > uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 > mmcsd0: 63GB at mmc0 200.0MHz/8bit/8192-block > mmcsd0boot0: 4MB partition 1 at mmcsd0 > mmcsd0boot1: 4MB partition 2 at mmcsd0 > mmcsd0rpmb: 4MB partition 3 at mmcsd0 > mmcsd1: 128GB at mmc1 50.0MHz/4bit/65535-block > Trying to mount root from ufs:/dev/mmcsd0p2 [rw]... > WARNING: WITNESS option enabled, expect reduced performance. > uhub0: 13 ports with 13 removable, self powered > ugen0.2: at usbus0 > ugen0.3: at usbus0 > ukbd0 on uhub0 > ukbd0: on usbus0 > kbd2 at ukbd0 > ugen0.4: at usbus0 > umass0 on uhub0 > umass0: on usbus0 > umass0: SCSI over Bulk-Only; quirks = 0x8100 > umass0:0:0: Attached to scbus0 > da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 > da0: Removable Direct Access SCSI device > da0: Serial Number 07BA1B081C742B8A > da0: 40.000MB/s transfers > da0: 1912MB (3915776 512 byte sectors) > da0: quirks=0x2 > ugen0.5: at usbus0 > # df > Filesystem 512-blocks Used Avail Capacity Mounted on > /dev/mmcsd0p2 111720120 6363664 96418848 6% / > devfs 2 2 0 100% /dev > /dev/mmcsd1p1 241710968 65672 222308424 0% /work > linprocfs 8 8 0 100% /compat/linux/proc > tmpfs 7636728 8 7636720 0% /compat/linux/dev/shm > /dev/da0s3 1868552 32 1719040 0% /mnt > # pciconf -lv > hostb0@pci0:0:0:0: class=0x060000 card=0x72708086 chip=0x22808086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register' > class = bridge > subclass = HOST-PCI > vgapci0@pci0:0:2:0: class=0x030000 card=0x72708086 chip=0x22b08086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers' > class = display > subclass = VGA > none0@pci0:0:3:0: class=0x048000 card=0x72708086 chip=0x22b88086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit' > class = multimedia > none1@pci0:0:11:0: class=0x118000 card=0x72708086 chip=0x22dc8086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller' > class = dasp > xhci0@pci0:0:20:0: class=0x0c0330 card=0x72708086 chip=0x22b58086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller' > class = serial bus > subclass = USB > none2@pci0:0:26:0: class=0x108000 card=0x72708086 chip=0x22988086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine' > class = encrypt/decrypt > isab0@pci0:0:31:0: class=0x060100 card=0x72708086 chip=0x229c8086 rev=0x36 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU' > class = bridge > subclass = PCI-ISA > # > > Is there any suggetions? This issue is already fixed in: https://svnweb.freebsd.org/changeset/base/351692 --HPS From owner-freebsd-current@freebsd.org Sat Sep 21 16:19:33 2019 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 DF86B128C18 for ; Sat, 21 Sep 2019 16:19:33 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46bG4j0p46z3DLq for ; Sat, 21 Sep 2019 16:19:32 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qt1-x829.google.com with SMTP id 3so9830116qta.1 for ; Sat, 21 Sep 2019 09:19:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=gRyooJDl1CfzpfmGISk+8oQBKoNKltLUqVxqf+FWtsg=; b=P4dPuMuJ5zNUCKTdOebCC2XINuNNi9o0r89nk6ZJ4iRI7C+c2RjMvRJfzgsIT2jNXl b1sZWZt+n5dA7lrF2woTmlxetqrj/eFIwk9QstWKP7ArdWUzogUsBVxLqD04k8Zo8rhy QtTHMY25FiaOBuMaQr7cL9P89VHy7EskLYGn0LkZSH7WcD5Bn267P0hByoFO2J3Qepy+ DcnO6vI3aOHgHrsj8F/3m676rxhXZpU96lLQvxTnhESG3llh6m4ijg3LnDZYrLem5c0u ZaZgnsEHVveIjDlyxovborAbmRnJj8TlQQZQn675jaVdLNHflG6yosTlgDdcC4ADKNBe prtw== 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=gRyooJDl1CfzpfmGISk+8oQBKoNKltLUqVxqf+FWtsg=; b=HYcP4E4rdxiFIdbGAH28wRPM6/gY7zgMjSmW4YuxqM/dS4t8+PpsC1UgP/f3NA9Pup QGQy2QSNIuz5KL+/TIS3xYQQLnguB9EyispSlT/q7j138dWqz3ToY89VGTifD2QQrXKP AJHEfOnTa7eOMFwf+pydtBTLAPXPL4yjVQcZvcdTvPp0VTlDrkwto3kr+1F/GiZHlLdn RSgtC6jaCyG7DwgnUN/mnjf0nikYVq8v3fb9IMJk4oNAhUuoYQ0Sf/nBvycnJWP77bfn wwjUDHeIuC8wEOViMS2MxoyP2zSMcyhc6i5LfYDiStBQHLoew7JHz2spS+bv6l8hwKKu kWHg== X-Gm-Message-State: APjAAAU5t9nsctJ2jayvXdaoRo0IS7fDducY2fu0mHRBuiAHgvDHjl/Y QQbIqAOstotgi5DiQ5WtpZhzQt2qH4h/jjyNg5GBa/gA X-Google-Smtp-Source: APXvYqyTMaNL4pTMzjsk87AIjWhNmsbfw9FDve1Gl9Qe75morShpDQL77fLDq8/QWXfxhGTyqz1KSaejX/MCMNjpeog= X-Received: by 2002:ac8:34d8:: with SMTP id x24mr9203334qtb.353.1569082769978; Sat, 21 Sep 2019 09:19:29 -0700 (PDT) MIME-Version: 1.0 From: Ryan Stone Date: Sat, 21 Sep 2019 12:19:19 -0400 Message-ID: Subject: Direct exec of /usr/bin/ld fails with "mmap of entire address space failed: Cannot allocate memory" To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 46bG4j0p46z3DLq X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=P4dPuMuJ; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of rysto32@gmail.com designates 2607:f8b0:4864:20::829 as permitted sender) smtp.mailfrom=rysto32@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(0.00)[ip: (-9.36), ipnet: 2607:f8b0::/32(-2.64), asn: 15169(-2.20), country: US(-0.05)]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[9.2.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sat, 21 Sep 2019 16:19:33 -0000 If I try direct exec ld via rtld, I get the following failure: # /libexec/ld-elf.so.1 /usr/bin/ld ld-elf.so.1: /usr/bin/ld: mmap of entire address space failed: Cannot allocate memory Is there some sysctl limit I need to bump up to get around this? I presume that the binary is just too large given that I can direct exec smaller binaries like /bin/cat. From owner-freebsd-current@freebsd.org Sat Sep 21 16:49:10 2019 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 BB16F12999D for ; Sat, 21 Sep 2019 16:49:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46bGks6pCNz3GGF for ; Sat, 21 Sep 2019 16:49:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x8LGn1LU089031 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 21 Sep 2019 19:49:04 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x8LGn1LU089031 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x8LGn1Gw089030; Sat, 21 Sep 2019 19:49:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 21 Sep 2019 19:49:01 +0300 From: Konstantin Belousov To: Ryan Stone Cc: FreeBSD Current Subject: Re: Direct exec of /usr/bin/ld fails with "mmap of entire address space failed: Cannot allocate memory" Message-ID: <20190921164901.GO2559@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-Rspamd-Queue-Id: 46bGks6pCNz3GGF X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all:c]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(0.00)[ip: (-2.62), ipnet: 2001:470::/32(-4.48), asn: 6939(-3.24), country: US(-0.05)]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sat, 21 Sep 2019 16:49:10 -0000 On Sat, Sep 21, 2019 at 12:19:19PM -0400, Ryan Stone wrote: > If I try direct exec ld via rtld, I get the following failure: > > # /libexec/ld-elf.so.1 /usr/bin/ld > ld-elf.so.1: /usr/bin/ld: mmap of entire address space failed: Cannot > allocate memory > > Is there some sysctl limit I need to bump up to get around this? I > presume that the binary is just too large given that I can direct exec > smaller binaries like /bin/cat. No, this is not due to a limit, rather it is some unfortunate consequence of layout and default choices. Non-PIE binaries must be loaded at the fixed address. PIE binaries, which rtld pretends to be, are not. The loading address for PIE in non-ASLR mode is fixed per-arch, and it is not too far away from the default linking address of non-PIE. As result, it is possible for sufficiently large non-PIE binary to extend into already allocated range from rtld. We use MAP_FIXED | MAP_EXCL to avoid destroying existing mappings in linker, which fails when pre-allocating the space for whole future mappings of the object. I believe this is what happens in your case. I think that we finally should make the fixed PIE loading address a tunable. (patch was not tested) diff --git a/sys/kern/imgact_elf.c b/sys/kern/imgact_elf.c index 305e49c2e22..4678d7465b8 100644 --- a/sys/kern/imgact_elf.c +++ b/sys/kern/imgact_elf.c @@ -135,6 +135,11 @@ SYSCTL_INT(_kern_elf32, OID_AUTO, read_exec, CTLFLAG_RW, &i386_read_exec, 0, "enable execution from readable segments"); #endif +static u_long __elfN(pie_base) = ET_DYN_LOAD_ADDR; +SYSCTL_ULONG(__CONCAT(_kern_elf, __ELF_WORD_SIZE), OID_AUTO, pie_base, + CTLFLAG_RWTUN, &__elfN(pie_base), 0, + "PIE load base without randomization"); + SYSCTL_NODE(__CONCAT(_kern_elf, __ELF_WORD_SIZE), OID_AUTO, aslr, CTLFLAG_RW, 0, ""); #define ASLR_NODE_OID __CONCAT(__CONCAT(_kern_elf, __ELF_WORD_SIZE), _aslr) @@ -1146,13 +1151,13 @@ __CONCAT(exec_, __elfN(imgact))(struct image_params *imgp) if (baddr == 0) { if ((sv->sv_flags & SV_ASLR) == 0 || (fctl0 & NT_FREEBSD_FCTL_ASLR_DISABLE) != 0) - et_dyn_addr = ET_DYN_LOAD_ADDR; + et_dyn_addr = __elfN(pie_base); else if ((__elfN(pie_aslr_enabled) && (imgp->proc->p_flag2 & P2_ASLR_DISABLE) == 0) || (imgp->proc->p_flag2 & P2_ASLR_ENABLE) != 0) et_dyn_addr = ET_DYN_ADDR_RAND; else - et_dyn_addr = ET_DYN_LOAD_ADDR; + et_dyn_addr = __elfN(pie_base); } } From owner-freebsd-current@freebsd.org Sat Sep 21 17:14:42 2019 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 51E6C12A315 for ; Sat, 21 Sep 2019 17:14:42 +0000 (UTC) (envelope-from mms.vanbreukelingen@gmail.com) Received: from mail-qk1-x742.google.com (mail-qk1-x742.google.com [IPv6:2607:f8b0:4864:20::742]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46bHJK3xsmz3HVn for ; Sat, 21 Sep 2019 17:14:41 +0000 (UTC) (envelope-from mms.vanbreukelingen@gmail.com) Received: by mail-qk1-x742.google.com with SMTP id 201so10699775qkd.13 for ; Sat, 21 Sep 2019 10:14:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:reply-to:to:message-id:in-reply-to:references:subject :mime-version; bh=icmkHPJETwlFSDDJvXw8Xeb68JNtRxMG7s+t5EUrtho=; b=cruYjNVwPMjjcI9hXaaTaDPp5kvVXt2D8eWxqSpAY9fHW9OfFL0cluTpJgCgixewce yRP/xT8MApZcoN2Y8GTRBEVLWSXALPIVLW6BX4oCW65I5RUeFU4AI6aUZceyd4StBH1v dgt/XjeXCAO+QuEXjuBuz5E+SW0deNzublW3+bTWxuR3FmkDTafuHqxRby69xSb5nsBn aH5E7+m/3Q2xDVRBUPFpve9rV8HDncR07IQy3Av7VCvCyPsqlGS3f7IxAAzsJ4weLNM5 AGqP7mEl5NinWxFeUhDXFOLAcZXl/RkvCYkl8IOPJAUNgdgzwRFhd4+HyXQhgWcfNXsl gKSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:reply-to:to:message-id:in-reply-to :references:subject:mime-version; bh=icmkHPJETwlFSDDJvXw8Xeb68JNtRxMG7s+t5EUrtho=; b=ZJTEgzen+tFX+IvstgRdNHxmYp3vB+ER472ENhoAC2STnl76zXfYbm7ZTZ+hmD5e+g 86c77jBfUiiJEzVo2lIPJZlnIavgg43egl/4Jtz87Wy43O0t7DipVIOZV96xltxqPU2u GX2H4CVqiYdzhJFJliBmOR9XHeKB9t8QLYDiuCNJEvxQhOvSrcScKmqcQhtfa1IWGVJ8 Q57VUh/P6OY9nCGgExDTiTZK74Ut7rHdqiErz8tE/oahSG/35j3cQjW5OV66V8ppH6k7 3359vu4aj7l16I5GXLLQKrMQvnS3V7dDu1sKqu4hHJIv9y9RPgH7roBMkDQoZnTm9Qdr GTMA== X-Gm-Message-State: APjAAAWD9X/kPuIlfG/zLohXZ1K3wimlqmSQniuqKkdjpMbYrWoloiWe 9wLVap46N+xAbLhvOqj1evpEglB9Tpk= X-Google-Smtp-Source: APXvYqxSbt32DvdfZyqLSHzbfcxlGsMoWyzXXnKjYziIYUVqz17u04Z6EXM5mPOeSLbk/mQ3Pp5j2Q== X-Received: by 2002:a37:95c6:: with SMTP id x189mr9393341qkd.323.1569086080583; Sat, 21 Sep 2019 10:14:40 -0700 (PDT) Received: from sonic316-11.consmr.mail.bf2.yahoo.com (sonic316-11.consmr.mail.bf2.yahoo.com. [74.6.130.121]) by smtp.gmail.com with ESMTPSA id f18sm2470138qkl.55.2019.09.21.10.14.39 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 21 Sep 2019 10:14:40 -0700 (PDT) X-YMail-OSG: wMMfku0VM1lftaMT8UdL6i22gUm6ZdfjempAIwxs2Xo2AexNUOwmmhD5kaLnIXX YTlI0caeNo3VDK4hgDJshFNKzLvGQnW.GjljlvYT7BfKSpkQeppy4Gl6qasxfNM25QMZq3VTtz1x 4f4IqqZLxMnChBJd0PK3oIgowZuDyXjXKc9YKmkMqAFtXbmHXAmknu_4OFXwPGJ0w8ocsohr0nQ_ uP6GjR.n25.vgQBY.wptBVofnw7PvpgjdWcl2eS5yIwEq6ge8uXG5rY807lTbNvJWVNkObWjtcIA TWvphlVakwcko0yvMWK.HdtoHHsobJVDDAAESpeZXUJyoDsM49QAkPneh4TrkT.4ohJaFYiJEwbx pFArtdVmZ1ZAWYMRY0c5G0lyUYSHfLx6zBuaJKZLG6BpRLY2d.ze4BgUWU_oFlGb5ZFmRnc3z4Kw 0DZpu3sPWUabUmWo65DebYRiByB6O.03AoYGENQhm.T3IrrNlQt5c7kufRABesT97d9ct3XQRikr vPmdQ_1TRhXer6CnktPzFWTZf64XJ43qG0nFvQrVdAoGuMOzBWAekc.Nrm7ppnQzp19htM5ZQCYK fshYJ7CAUSsgrNenmer7rqy5tGi6RrgHdT.FNz_wnwgotFwCHEYW0DOKtyavhr1HT5IaVOqWcrU0 nx5VLfuuLvm4dQiEWWbhlGHYVAOjATYWLWpcYmQ9A44KO.8.lNjAXEIYASFmKLN5g9KEBsPP65Bo 4cS.XjLa2n1gvvEsshgwePxH96Ish2YVK1vR3M7JCEStMhjrf7qpoVSbOgMjpRwuINeacORIfeQ4 FeeaDU.VPMn_Hgqm.w3FJCxK3SYW8j2szg5EXr.5qdlISuHTG5aIwr4zNFgCGJvckG7kCIKz_F5E zYDGUDShe0yzeW2beL1Ykmmz7BWPiQhu9MFGLTFnfqtlcgpq9MyrunBCn940XjCieLRbciaOG0ms IiUHw9IdYC6liQt1UjS2T2heHGTxyWObneEr8Y70YxHmyn8AqePajdkaMxhPyXddq0p5IoEj5CuW bzf76kyrLNRXXeCxKHeIMpnLaP87NU01S7WB_9Ri7iFU1d9maAStAg_HWFwnbGRHc.sKexQz7Gkb BgmEy5gYdSqhpwPpfbUWm5k6u_UhdYtMMR4M.gCcNqbrASXfN5glTSTgngwg8jW5Y8JJgewz5HBH N4oCICv2yynnRvwPlmQxPzWraBtMLNx4N7.02lrVU5Gkz_Jg5Ml8V5gSbKTxdJRBQ5SUgzoIFKG2 KpwZc3hCinKJ9AiLt1M4fK2m3KcmDd1w4qwPp9PVHzdmlDK6PTuZd6hsyu731H9PkXZU8m5oX4Io 33URL4YACT3deAyIqiZ3wmfO0Z.B2OCCs Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.bf2.yahoo.com with HTTP; Sat, 21 Sep 2019 17:14:39 +0000 Date: Sat, 21 Sep 2019 17:14:33 +0000 (UTC) From: "mms.vanbreukelingen@gmail.com" Reply-To: "mms.vanbreukelingen@gmail.com" To: "freebsd-current@freebsd.org" Message-ID: <1851281215.7243287.1569086073547@mail.yahoo.com> In-Reply-To: <1216052911.7229089.1569071932467@mail.yahoo.com> References: <1216052911.7229089.1569071932467.ref@mail.yahoo.com> <1216052911.7229089.1569071932467@mail.yahoo.com> Subject: The X11 error correction went to a non-booting kernel MIME-Version: 1.0 X-Mailer: WebService/1.1.14303 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/5.43.5; Android/7.0; HUAWEIBLN-L21; hi6250; HUAWEI; HUAWEI BLN-L21; 5.3; 1843x1080; ) X-Rspamd-Queue-Id: 46bHJK3xsmz3HVn X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=cruYjNVw; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mmsvanbreukelingen@gmail.com designates 2607:f8b0:4864:20::742 as permitted sender) smtp.mailfrom=mmsvanbreukelingen@gmail.com X-Spamd-Result: default: False [-2.95 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[mms.vanbreukelingen@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; FREEMAIL_REPLYTO(0.00)[gmail.com]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MANY_INVISIBLE_PARTS(0.05)[1]; IP_SCORE(0.00)[ip: (2.98), ipnet: 2607:f8b0::/32(-2.64), asn: 15169(-2.20), country: US(-0.05)]; RCVD_IN_DNSWL_NONE(0.00)[2.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; TO_DN_EQ_ADDR_ALL(0.00)[] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sat, 21 Sep 2019 17:14:42 -0000 =20 ----- Forwarded message ----- From: "mms.vanbreukelingen@gmail.com" To: "freebsd-current@gmail.com" Cc: Sent: Sat, 21 Sep 2019 at 15:18 Subject: The X11 error co= rrection went to a non-booting kernel @daniel-clay: None of the three kern= s. Boot anymore.=C2=A0 Gotta install zfs-utils and zfs-dkms-rc on Arsch lin= ux to edit it back again.=C2=A0 This besides only if I-Net will be availabl= e at i-node.=C2=A0 =20 From owner-freebsd-current@freebsd.org Sat Sep 21 19:26:10 2019 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 5A75912D3D2 for ; Sat, 21 Sep 2019 19:26:10 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 46bLD11klvz3QBF for ; Sat, 21 Sep 2019 19:26:08 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qk1-x736.google.com with SMTP id u22so7478109qkk.11 for ; Sat, 21 Sep 2019 12:26:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2Y1gYXyyQE8OWvipUsS0sRCH8LWReSxgkBt8csrXPEo=; b=eO1xdrobAX8pq5Vy+2k8oOOFUEtIwQi6rYD1QVkHr6PsVUiY6cEDoBcryGJSnGaW+u t/IpQrKlyRpzjlCmctIv/Ury5/h6XobktPQ5TtmZx17WqoYREnUPCSeedR3CEEYPB2/t GVHA5mYNqaFWDDK230nLlCDBZA6M8eSseGNYIyIoP3P1EdVtNBGwYimvXIX2VJECddW5 61S8wARdf2v8g3k9ZsYtfg/E1Cbw8YHtm0MQX40zL4CMZZDLvuqXS1y/YiqBpP8XpAYw v28ZjxtWxOJk95Gpn2Flyxk7rSm5ilM73I43bUU/vy2p2DGiSjWD3STDXk/PcXYWxLGV fKEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2Y1gYXyyQE8OWvipUsS0sRCH8LWReSxgkBt8csrXPEo=; b=VTNRn/urS8uTYIEIJJA1xiPWzrq1U7XwyqXde6XEQCBC7lgGtiLh9nX22/mg3siRdb FKBYO+sr4CMBsBLzQBchxLlOUbPwSyU6NtI8kWJjXT7irkOPDnCbLsLm8Y62a818YvTj 9vCEl24JlfeRtGMR3Y6M9qGljWo2iK7juYcz/e1ykt3nFmb1Mz4ctJMM0HZ1zFyMV29O Vc5KDC6uvZVYUBCH/RFrXCAQoT1u3vqutWDIWqe6fdv95/czC5x7XkDUNg1eLJHek1PL +Www+iriXHRPfiLxEz+TymRuO+RHadeXgY+VR8XhCjmG64Msz1wJ3JTBNRryFvkqNYVr AcxQ== X-Gm-Message-State: APjAAAVKH/ChVuDAsldw0g6kgO23o4ob5ZjBLc7fE++k3dnQ5xTQcmf5 AVoGgfGTrHLNM4YiCCuuDpLcA5mkAo5x7gl9QbM= X-Google-Smtp-Source: APXvYqydjOSY6VBCHFRUGwg2H/gB5bO2mUnGphl5ZfpluLoArB8RCv1V78dLHW59mxYvIf9qZcIIjJCWTHHREHJE3nY= X-Received: by 2002:a37:a858:: with SMTP id r85mr9822335qke.394.1569093968011; Sat, 21 Sep 2019 12:26:08 -0700 (PDT) MIME-Version: 1.0 References: <20190921164901.GO2559@kib.kiev.ua> In-Reply-To: <20190921164901.GO2559@kib.kiev.ua> From: Ryan Stone Date: Sat, 21 Sep 2019 15:25:57 -0400 Message-ID: Subject: Re: Direct exec of /usr/bin/ld fails with "mmap of entire address space failed: Cannot allocate memory" To: Konstantin Belousov Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 46bLD11klvz3QBF X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=eO1xdrob; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of rysto32@gmail.com designates 2607:f8b0:4864:20::736 as permitted sender) smtp.mailfrom=rysto32@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[6.3.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; IP_SCORE(0.00)[ip: (-9.37), ipnet: 2607:f8b0::/32(-2.64), asn: 15169(-2.20), country: US(-0.05)]; FREEMAIL_TO(0.00)[gmail.com]; 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]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sat, 21 Sep 2019 19:26:10 -0000 Apply the patch and playing with increasing the value does allow direct exec of ld via rtld to work. so thank you. The patch probably shouldn't be applied as-is, though, as executables will just segfault right away if the sysctl is tuned to a non-page aligned value. From owner-freebsd-current@freebsd.org Sat Sep 21 23:26:52 2019 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 47571E9B48 for ; Sat, 21 Sep 2019 23:26:52 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from muon.bsdio.com (muon.bluestop.org [65.103.231.193]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46bRYk3fSTz45Fp for ; Sat, 21 Sep 2019 23:26:49 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from muon.bsdio.com (localhost [127.0.0.1]) by muon.bsdio.com (Postfix) with ESMTP id 0C91BE5C98; Sat, 21 Sep 2019 17:26:52 -0600 (MDT) Received: from muon.bsdio.com ([127.0.0.1]) by muon.bsdio.com (muon.bsdio.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ur82pySun4UF; Sat, 21 Sep 2019 17:26:51 -0600 (MDT) Received: from photon.int.bluestop.org (unknown [10.0.10.150]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by muon.bsdio.com (Postfix) with ESMTPSA; Sat, 21 Sep 2019 17:26:51 -0600 (MDT) Subject: Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO To: Yuri Pankov , freebsd-current References: <2c2da4f1-052e-d8e7-a10e-079879975f92@bsdio.com> <58d44015-3b59-659b-607a-e056ad45607f@yuripv.net> From: Rebecca Cran Autocrypt: addr=rebecca@bsdio.com; keydata= mQINBFrUMZ4BEADI1yUEGeZeXeTCPay1ZpTBdDEpGPAw1dq2VCSTc1VhsnrEBa1iZxAfaeSv Uu5Ti7jlhQ/3sQMl0bJMKGB/RtmIW7k8h2w476oZmG8gChk8su5ZEx/pV1gdqInyFmmJKTYc gabJz8pL+m82w07qPv+oalepZ4dbj+HF++RAK/iEju+q9UHlsjj8e3mMNsvtrOz1K6bnpveO jZ+ms/2H3Hs5a4k8y6buwe2RvwhJQaXa13cR3LhzL+nwj4B9PHZZEa2WpEyYpw/bI0V9YSQN QgC1CYRzDyakZge6BCM6wHOgZSUzRPufGilrNKUwIVbRoIBR9/85+0wR+PlFUOUOfOc6ox7T dWcIx6PuPhek48rh4uwmmwsPtPiH4Z3T5p+GmWQ9NLFZKA1YnEdaSkWtYZsDxwVZZeYG2plt MfhXP0Hj4rf9Y3eoUenCaGioxAbUOBCtXdTGNAhNjz1g5NGDBVyhjKkzwJQvt9UrYTseERit 5dX2CMTy8hYLvSXd/Ivy+HylUS5IslfZxW5z9LgWX7Z97kILgkH3N0ewtLkygkG+Y+x7uaAV dFqp9ASOyzaiwKbJdeOI+WxRSh+AqeCR0S+bpkcLudLmbjrPmaFwjKycy1H85Z5R2J3YHyXY oT6OYjD8vLbUU2GWp6Onkcy1Pu8EMbRuzKil6HnpYg3BexbPFwARAQABtCNSZWJlY2NhIENy YW4gPHJlYmVjY2FAYmx1ZXN0b3Aub3JnPokCVwQTAQgAQQIbIwUJCWYBgAULCQgHAgYVCgkI CwIEFgIDAQIeAQIXgBYhBB+5fZtkTdO940Yr4g0CK1MRvhAgBQJa2B9zAhkBAAoJEA0CK1MR vhAgzJEQAJUqVmTRO9OqCSS2CVKjrqnEWJMvyo0K8B+WiXo0nSQg9+uyoVU7h2s/kkWVGy4u IWbGy2Qe8LiXzBJjHC3TadGvOvakfdMeKKXcgxgX6KlhA9hA2LW6tg22aHUk7Flr/8diHpgf qIwrXhqJXZmK72GR1QfhgoHsOsTJ9GWPswo1kUMc0cJowq0qP1RDdua6BwvDHHPJwu9OmC/i oQlMNm9gkBDq8H2B+m125ANwCnqBizXaiTTLQdewTMbCSuxbsni2icDqwBfFXzEgcJGaYYfB cQeFsfCmtXQK3JUd4Myx128Dxk9P3X64I93SB7QzB0nmWlyvmCFBNoCp0PCLA4qbwbw2sMRX Wx4BqYa8nI/jg+Nqo+Ut2BfltNZIlsHxK+XhxejfLqAjRCZeLnu1otvFnFuGLaAVYx9x1Y1q J8VizZxq6ujio62Qpultp6KNhlkJ+OKoGwA0k4NHh26SxvlsNxlfg/2v9b1LqWRzNujnwbcF 8g4902XjyBLxV+9YpXZEa8H6zzEHxpeDPWT3QfvrT8JuoHa1IyYnUKvG674UKW5zEGEwkQc9 cuQwR1RHd1ZrKtH1duXzaLr/caMp8ZDfGDDxFpenJTRxNRlg4+K7HSdhpac7sBVMUA8uVdE+ iuTThOmdf0c4DorL3BIh6Yv3FV4/NSqT1Wn3CG2fgG1guQINBFrUMZ4BEADkc4mvMcMcDF1t dNxNQuIBE1F243oZamG3LACCKfc1Yur3CPzHwIk5LXCUmbq23iE5bowxMWw3mlVT0p5xM0Wn UidIBwCKu4kRyy/fY4NyWWBuwy9srpTdmUcKRBRNB8zEZE8xIlidD1ijjgqLBfeM7n9ylawA xHLxwU96sdpdHFzb7Z0yKY2e/bzDaHiG0fUvcCmkgLf+uwKKZid1j8zR5PzKpgPqfy/PF01e KyGV3MNu8Y90xMoiEMWfCI2IB1m+hTuzZoboFvGV54SiMuvfWK/VMQjhsL6K2ddOqwVuy2nI MI4G3xDQW/v8KVyn43OSIAyW1eaklhzu0Ir2sO60PXRkvbTUrouvmSvpJfIQS49rU0M/X6FS DgXQLKrZ3my94+g8ptz9KoVml6s4OAwYVz+sb49nuSxipFKkU5FwhKOLmzbsBxCtytcUJoLm juJPJPDQue6YJiIXyc86GVY2pH3DjemKdbB4dSgqAJIp+lCzKSJzz7bgueh2Ox8vzx1tSxKj 7V8Nal+UTKKbkxPmMh+e20YZ4esAVifO3bS6IJP/aDnfagghB71vA7+aWGXPbjPlc2UHpCBi RSsl+IgoQXvdvZBsKRyfBx8neODa2C6JIE5vcaCjilSeKF8SzsFXvimnndhQNhAPU/DwQwSX dCl4gTsFVi5d8Oxq1sce+wARAQABiQI8BBgBCAAmFiEEH7l9m2RN073jRiviDQIrUxG+ECAF AlrUMZ4CGwwFCQlmAYAACgkQDQIrUxG+ECAWnRAAsmZX+KgNxW3v7R/76Tz4Wjmh4AGeE+Ji 3p5QsdTYny1B6vYBL9vCzPJ/AK8pgKMDRaweUP5eZQpfrdWC8Q7SNGgi4Q+97KEs+i2xZLQ+ WJb8a+WEEIc716u0y4ITiHfOgM5jWcFO4MXQATbJgv0drLLesa+LQCvZgPBqupt307EsCubQ s+Sxt+RVjf6rOUolp1GJXEQYwGsKklVd6yqLC8M1BSG53/WE5tSv5GzBZ8fp6EtmjT7leuid FtEvKYHQz4DqG9ELpHUF0X0UUCBK/MgXe3kCVLKE060UrJ4M6uPSx57rmVFA2MvwQR8M7GsW C5UsSM4PYwPWBhwxE7vcx0691YKAHT/5q8LxRVBdUyzPSprMhSQFttsBt+ygm6wRi3Pi3TuC EARNubPkQefyeC34yr40SAUCkOl3eWxSXPF4NfXFQb4AAzZSE5hv3qbDuwo3lrL0LqpIpEQP Az+JZ1QZ6mMFQ5/JD9Gukj54kZc0X8w3sQt0a8vyE/qrJg8vKgv2rCHrPc5MeDkEUEFiiJiC EDdkJtMyoRlU3S4NrnbyLOLEcHE8fGe3hStPX8hY62id2ecdQ5WZ7vLZW5SFeLarbUciuHIk VL6MHnUjbV7XlY50N7ebeFCIdlCWhdum2FJs/Ni+SSxbZC564vrokwlBBGSo6WTPQTa8IWx1 DtU= Message-ID: Date: Sat, 21 Sep 2019 17:26:42 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <58d44015-3b59-659b-607a-e056ad45607f@yuripv.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 46bRYk3fSTz45Fp X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of rebecca@bsdio.com has no SPF policy when checking 65.103.231.193) smtp.mailfrom=rebecca@bsdio.com X-Spamd-Result: default: False [-3.88 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[bsdio.com]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:209, ipnet:65.100.0.0/14, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.78)[ip: (-8.92), ipnet: 65.100.0.0/14(-4.85), asn: 209(-0.07), country: US(-0.05)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sat, 21 Sep 2019 23:26:52 -0000 On 2019-09-18 16:29, Yuri Pankov wrote: > Yes, exactly, sorry for not mentioning it. > > ESXi version: 6.7.0 > ESXi build number: 13006603 Sorry, I've realized it's _not_ crashing when we call ExitBootServices after all: it's just that we can't call printf after that point. I've found it gets to the point of executing the kernel and then crashes. I've had it booting a couple of times by setting console=comconsole, but I'm not sure if that's relevant. -- Rebecca Cran